manage_docs

Automate Sphinx documentation builds by running make or sphinx-build to render HTML from docs/web/en and docs/web/ja directories. This ensures consistent bilingual output and reduces manual effort.

Cross-link verification checks bilingual Sphinx documentation builds for broken or inconsistent links between English and Japanese outputs. This validation runs automatically as part of the build workflow to ensure quality.

Yes, you need Sphinx and common build tooling like make or sphinx-build installed locally. These tools render the HTML output from your source files and enable incremental builds and verification checks.

Yes, you can integrate documentation verification into CI/CD pipelines to automatically build and validate English and Japanese Sphinx docs. This ensures output quality and consistency before publishing.

Keep English and Japanese documentation synchronized by automating the build and validation process for both language directories together. This enforces consistency and catches discrepancies during the build.

Sphinx incremental builds may fail to reflect updates if source files are not properly saved or if build caching issues occur. Running a clean build with sphinx-build ensures the latest HTML output is generated correctly.