What problem does it solve?
Keeping a multilingual Docusaurus product manual aligned with a changing application is error-prone: translated pages drift out of sync, screenshots go stale, navigation misses new pages, and a passing build does not prove the prose is accurate. This Skill provides a disciplined workflow for updating, translating, auditing, and validating a Docusaurus manual so documentation stays consistent with the actual product.
Core Features & Use Cases
- Locale Parity Auditing: A bundled Python script compares canonical docs trees against i18n locale trees, reporting missing, extra, and identical-body pages per locale.
- Structured Update Workflow: Step-by-step guidance for verifying product behavior from source code, updating canonical pages, preserving frontmatter and MDX components, and propagating changes to every published locale.
- Screenshot and Validation Discipline: Rules for using deterministic screenshot registries, plus a staged validation ladder from parity audits through production builds and rendered-page review.
- Use Case: After shipping a new feature, use this Skill to document it in the canonical locale, update all translated MDX trees, register new screenshots, run the parity audit, and validate the production build before publishing.
Quick Start
Use the maintain-docusaurus-manual skill to document the latest feature change, update all locales, and validate the Docusaurus site before release.