blog

# Chorus Blog Post Write bilingual (zh/en) release blog posts for the Chorus landing site. ## Prerequisites - You know what version / feature to write about (user will tell you, or check recent CHANGELOG / git log) - Existing blog posts live in `packages/landing/src/content/blog/` - Naming convention: `zh-chorus-vX.Y.Z-release.md` (Chinese), `chorus-vX.Y.Z-release.md` (English) ## Editorial Style These rules come from the project owner. Follow them strictly. ### Narrative structure 1. **Open from the reader's pain point, not the feature.** Don't start with "we released X." Start with the problem the reader is living with. Describe the scenario vividly so they recognize themselves in it. 2. **One line to introduce the solution.** After the pain point lands, say what this version does in one sentence. 3. **Break down the supporting mechanisms.** Explain the layers / building blocks that make the solution work. Order them by the flow the user experiences, not by importance. 4. **Industry context as supporting evidence, not the opening.** If there are relevant industry trends (e.g., new tools from Anthropic, competitor features), reference them to validate the direction. But they go in the middle or late section, never the lead. 5. **Converge to a conclusion.** Tie the pieces back together. The punchline should echo the opening pain point: "this is why you can now do X." ### Tone and voice - **Don't speak for the reader.** Never write "you probably think X" or "you defin...