This repository publishes the organization GitHub Pages site. The public front
door presents CI-gated emulebb-rust nightly builds as the active beta testing
channel. eMuleBB MFC 0.7.x remains the stable long-term maintenance line.
Rust development is best-effort, and contributors are welcome.
The public site is expected to publish at:
Generated HTML remains committed as a drift check and branch-publishing
fallback, but source edits go through the Jinja2 renderer and the shared
emulebb-tooling\manifests\public-presence.v1.json contract:
python -m pip install -r requirements.txt
python ..\emulebb-tooling\helpers\public-presence.py validate
$lastmod = Get-Date -Format yyyy-MM-dd
python tools\render_pages.py --lastmod $lastmod
python tools\render_pages.py --lastmod $lastmod --check
python tools\render_pages.py --lastmod $lastmod --output-root .local\siteRun the validation helper before publishing:
python ..\emulebb-tooling\helpers\pages-site-tools.py --pages-root .local\site validate
python ..\emulebb-tooling\helpers\check-tooling-doclinks.py --docs-root ..\emulebb-tooling\docs .local\site.github/workflows/pages.yml repeats these checks, verifies
install.ps1.sha256, uploads only .local/site, and deploys through GitHub
Pages Actions on main. Scheduled runs validate contract drift without
publishing.
Long-form product docs are maintained as Markdown in emulebb-tooling and
published as rendered HTML at:
https://emulebb.github.io/emulebb-tooling/
Before changing homepage claims, update and validate the source docs. Lifecycle
and roadmap facts come from PRODUCT-PORTFOLIO.md and ROADMAP-SUMMARY.md;
release facts remain owned by the corresponding product repository:
cd ..\emulebb-tooling
python scripts\docs-publish-check.pyThen return here, update the structured homepage source, regenerate the static HTML, and run the Pages validation commands above.