[jpmckinney]

Moves two Make targets into docs/conf.py, for phase 2 of open-contracting/deploy#266 (comment): the build becomes plain sphinx-build, runnable on any CI or host.

This is now blocking. standard_profile_template@latest has already dropped both targets from include/common.mk, so the next script/update here would pull a common.mk with no current_lang target while conf.py has no replacement — and 23 files refer to build/current_lang, so the build would fail.

• current_lang. A symlink so that build/current_lang paths in directives resolve to the language being built. setup() already writes into build/<language>/, so it creates the symlink beside it and removes it on build-finished.
• compile. config.mk ran pybabel compile for every language up front. conf.py compiles only the language being built, and only the domains translate reads. That empties the hook, so common.mk drops it and config.mk drops the target — one mechanism instead of two.

English is the source language and has no catalogs, so the call is guarded with if language != "en", matching the default on the line that sets language. The guard is deliberately at the call site rather than inside the helper: a translated language missing a catalog is an error, and now fails loudly. Verified by deleting docs/locale/es — the Spanish build stops with FileNotFoundError: .../es/LC_MESSAGES/schema.po, where a path.is_file() guard inside the helper would have silently shipped untranslated pages.

include/common.mk is synced from standard_profile_template and is byte-identical to it and to the six other documentation repositories.

Verified

make source, es and fr all pass under -nW, producing 56 pages per language, with no build/current_lang left behind.

compile_catalogs was checked differentially, not by deleting .mo files — that proves nothing, because Sphinx's gettext_auto_build recompiles them. With it, the Spanish schema reference renders 4 translated strings; without it, 0.

🤖 Generated with Claude Code