RE:CZ

CZON 0.8.6 Version Update and SandTable Transformation Progress

Technical Log

👤 Technical developers, AI tool users, content management system users, people interested in software updates and technical transformations
This article introduces the main updates in CZON 0.8.6, including the removal of YAML Front Matter and the switch to AI for extracting Metadata from JSON to resolve formatting errors during translation, along with SEO optimization. Additionally, the author is transforming SandTable to accept real market historical data for testing, but notes that Claude Opus 4.6 performs moderately in long-range refactoring tasks, still requiring manual planning. The article also discusses the cost-effectiveness of translation features, recommending pay-as-you-go AI services.
  • ✨ CZON 0.8.6 removes YAML Front Matter and switches to AI for extracting Metadata from JSON
  • ✨ Optimizes translation processes to avoid formatting errors and supports separate Metadata translation
  • ✨ SandTable is being transformed to support real market historical data testing
  • ✨ Claude Opus 4.6 performs moderately in long-range refactoring tasks, still requiring manual intervention
  • ✨ Recommends using pay-as-you-go AI services, with translation features available at free tiers
📅 2026-02-07 · 350 words · ~2 min read
  • CZON
  • YAML Front Matter
  • AI translation
  • Metadata
  • SandTable
  • SEO
  • Technical debt

It is February 7, 2026, afternoon.

During some free time while guiding AI work, I'll write a little log.

CZON Removed YAML Front Matter

CZON released version 0.8.6.

The main change is the removal of YAML Front Matter. Currently, the AI-powered metadata extraction feature is powerful enough, eliminating the need to manually add this information.

Previously, CZON would first assemble the YAML FrontMatter and then use AI to translate it into the target language. However, if the content format within the YAML was complex, such as containing quotes, the AI translation often failed to maintain the correct format.

The solution is to have the AI translate Metadata directly from JSON to JSON. The JSON format is widely trained on by various AIs, whereas YAML is not.

Furthermore, for scenarios where the original text should not be modified but metadata needs to be re-extracted, separating Metadata and content is beneficial. They are processed separately and merged into the final HTML during the rendering stage. For example, CZON may experimentally support some new Metadata fields in the future, but I don't want users to have to retranslate the entire article; users would only need to translate the Metadata.

When translating Metadata, a per-language, per-file translation approach is used, which might increase the number of AI calls slightly. However, for AI services billed by usage volume, this doesn't have a significant impact.

In other words, it is strongly discouraged to use AI services billed per call. By the way, I believe the translation function can utilize free-tier AI services, as this task is simple and requires almost no reasoning capability.

Additionally, CZON has added more Metadata fields and optimized some SEO-related content.

SandTable Refactoring

Also, I'm currently working hard to refactor SandTable (ST) so it can accept real historical market data for testing. However, some lingering technical debt still needs to be addressed.

Claude Opus 4.6 still performs mediocrely in long-range refactoring tasks. It still comes up with some inexplicable designs, and its judgment on compatibility remains somewhat inaccurate, requiring human planning.

It seems AI still hasn't overcome the dilemma of over-compatible design.

See Also

Referenced By