fec-doc-sync

To keep frontend documentation in sync with code, you can automatically gather facts from package.json, lockfiles, routes, and framework configs, then diff them against existing README, ADR, and changelog files to update only stable, public-facing content.

Documentation drifts from actual project configuration when facts are updated manually. Synchronizing documentation directly from source code, .env.example, and framework configs ensures the README, ADRs, and changelogs accurately reflect the current state.

Yes, you can sync documentation across multiple languages for the same frontend project. The synchronization process ensures the main language documentation and other language versions remain consistent after gathering deterministic facts from the codebase.

The best way to automatically update a changelog from lockfiles and routes is to perform deterministic fact gathering from these source files, carefully diff the findings against existing documents, and update only the stable, public-facing entries.

To sync frontend docs from code, the required documentation sources include package.json, lockfiles, framework configs, .env.example, routes, API clients, architecture docs, and existing entry points like README, docs, ADRs, and changelogs.

Frontend documentation sync is specifically designed for projects with multiple documentation entry points such as README, docs, and ADRs. It gathers facts from code and configuration to carefully diff and update stable, public-facing documents.