Building¶
All builds are driven through the Makefile. Run targets from the sphinx-docs/ directory.
Build commands¶
Command |
Description |
|---|---|
|
Install Python dependencies via |
|
Build the English site → |
|
Build the Japanese site (uses |
|
Build EN + JA, assemble into |
|
Extract translatable strings into |
|
Run |
|
Build EN + JA + assemble + Pagefind, then serve |
|
Run |
|
Validate all links → |
|
Build the Pagefind search index for an existing |
|
Run |
|
Run |
|
|
|
Remove |
Output¶
Path |
Contents |
|---|---|
|
English HTML (the default |
|
Japanese HTML. |
|
Assembled bilingual site with |
|
|
|
|
i18n round-trip¶
Whenever an English .md source changes, the round-trip is:
make update-po # rebuilds .po files from current sources
# Edit msgstr in locale/ja/LC_MESSAGES/<file>.po
make build-ja # verify Japanese build
make build-all # final bilingual assembly
Empty msgstr entries in .po cause Sphinx to fall back to the English source string for that paragraph in the Japanese build, which is acceptable as a temporary state but should be filled in before release.
CI Pipeline¶
The active workflow is .github/workflows/docs.yml. It triggers on push and PR for changes under sphinx-docs/** and on manual dispatch.
Stage |
Tool |
Purpose |
|---|---|---|
Install |
|
Install Python deps |
Lint |
|
Style |
Test |
|
Test suite under |
Build |
|
EN + JA + Pagefind |
Deploy |
GitHub Pages |
Only on |
The status of every workflow file (active / opt-in template / planned for the initial release) is documented in .github/workflows/README.md.
Note
GitHub Pages deployment is currently inactive because the repository is private (see the README “Visibility” block). Pages will be enabled at the initial release together with the visibility switch.