The OpenWALDO project website — https://openwaldo.org
Open Weights. Open Artifacts. Open Licenses. Open Data. Open Origins. OpenWALDO.
Plain static HTML/CSS, no build step, no external dependencies. Served by
GitHub Pages from the main branch root (CNAME sets the custom domain;
.nojekyll disables Jekyll processing).
index.html project thesis and live corpus record
corpus/ accountability, evidence, and the live corpus record
training/ model lifecycle and current implementation boundaries
contributing/ contribution paths for community, tooling, data, models, and compute
community/ community participation and project entry points
posts/ generated Markdown archive and individual posts
about/ project purpose and principles
assets/style.css primary visual system
assets/main.js corpus feed, explorer, and shared accessibility
The primary pages use one shared visual system in assets/style.css and one
shared behavior layer in assets/main.js. Detailed implementation guidance
lives with the WALDO code and index repositories so it can evolve with the
software.
The front page corpus record and the corpus explorer load live from the
canonical feed the index repo publishes:
https://openwaldo.github.io/waldo-index/status.json. The site accepts the
older stats.json name only as a compatibility fallback. Nothing in this repo
generates those numbers—they update whenever the index does. Until the live
feed loads, the pages show an explicit loading or unavailable state rather
than stale corpus totals.
Posts are markdown files in posts/content/ named YYYY-MM-DD-slug.md,
with flat frontmatter (title, type, author, description, optional
logo). Publishing is just adding the file and pushing: the deploy
workflow (.github/workflows/deploy.yml) runs
.scripts/build-posts-index.py to generate posts/index.json — the
listing and search index — and ships it in the Pages artifact. The file is
gitignored; to test locally, run the script yourself, then serve:
$ python3 .scripts/build-posts-index.py
wrote posts/index.json: 2 post(s)
$ python3 -m http.server -d . 8080Note: deploys go through GitHub Actions now — the repo's Pages source must be set to "GitHub Actions" (Settings → Pages → Source).
Edit the HTML, push to main, GitHub Pages redeploys. To preview locally:
$ python3 -m http.server -d . 8080
# → http://localhost:8080Preview through the server, not file://, so dynamic corpus and post behavior
matches production.
The www.openwaldo.org repo holds the redirect from www to the apex domain.
Related projects: the OpenWALDO GitHub organization
and openwaldo/waldo-index (the
public data tree).