bilingual

To auto-create missing bilingual posts for Hugo blog content parity, the Skill detects single-language files in content/posts/, notes/, or raw/ and generates the missing zh-cn or en counterpart automatically.

Yes, the Hugo markdown translation process preserves frontmatter fields like date and tags, keeps code blocks, URLs, and technical terms intact, and translates titles, descriptions, and body content naturally.

The best way to generate missing zh-cn and en versions is triggering translation on creation, edits, publication, or explicit requests across content/posts/, content/notes/, and content/raw/ directories.

Yes, you can translate Hugo blog tags for different language versions, as the Skill supports language-specific tag translations while maintaining the rest of the frontmatter and body content structure.

To trigger an explicit translation request for a single Hugo blog post, provide the source post path and request translation to the missing language to generate the missing counterpart file directly.