Localization CI and CD

Desired checks

• locale inventory consistency
• fresh site generation before parity review
• link validation
• article and page generation
• spellcheck where available
• placeholder parity
• accessibility smoke tests
• screenshot and diagram coverage checks

Fresh generation rule

Localization CI and review workflows must not base parity findings on stale generated artifacts.

Required sequence:

1. generate the site from the current repository state
2. run validators against the freshly generated output
3. inspect generated HTML where needed
4. inspect rendered output where needed

This matters because source Markdown, generated HTML, deployed output, and browser-rendered behavior can temporarily diverge during development.

Review priority

Apply the strongest native-language and parity review first to:

• newly created content
• recently expanded content
• content currently being edited

Then extend the same review standards progressively to older localized content.

Defect-class progression

Localization CI should track both:

• Localization Debt
• Open Defect Classes

Debt measures remaining source-content work.

Open defect classes measure whether the system can still permit a category of problem to reappear.

As soon as a defect class reaches zero occurrences, its validator should move from advisory to blocking where practical.

Examples:

• placeholder draft publishing
• untranslated summaries
• untranslated metadata
• untranslated bodies
• mixed-language publishing

CI is not only a gatekeeper. It is the mechanism that keeps closed defect classes from reopening silently.

Generation order for article navigation

The current public article navigation contract is:

• post-article-nav
• related-content
• related-topic-nav

Generation and validation should happen in this order:

1. generate article HTML
2. generate index pages
3. run any remaining navigation post-processing only if still required
4. validate freshly generated output
5. review generated HTML or rendered output if the workflow calls for human parity assessment

If a validator still expects the legacy topic-nav block, update the validator to the current contract instead of patching generated HTML.