Translia

Insights Authoring

Goal

Keep multilingual Insights easy to manage as more languages are added.

File Naming

Use one shared topic stem across languages.

• English: _insights_en/<topic-stem>.md
• Chinese: _insights_cn/<topic-stem>.md
• Future Korean: _insights_ko/<topic-stem>.md

Recommended language codes:

• en
• zh-cn
• ko
• ja
• fr

Do not use mixed patterns like some files ending in -cn, others ending in -zh, and others with translated file names. Keep the file stem stable and use the collection folder plus front matter to identify language.

Required Front Matter

Every article should include:

translation_key: workflow-before-quality-loss
lang: en

Or:

translation_key: workflow-before-quality-loss
lang: zh-cn

URL Rule

File naming is for internal management.

Public URLs should stay readable and local-market friendly through permalink.

That means:

• file names stay aligned across languages
• public slugs can still differ

Example

Internal files:

• _insights_en/workflow-before-quality-loss.md
• _insights_cn/workflow-before-quality-loss.md

Public URLs:

• /en/insights/why-content-workflows-break-before-translation-does/
• /cn/insights/workflow-before-quality-loss/