Skip to content

Give stadion documentation - #5

Merged
DenisDrobyshev merged 1 commit into
mainfrom
docs-site
Aug 23, 2026
Merged

Give stadion documentation#5
DenisDrobyshev merged 1 commit into
mainfrom
docs-site

Conversation

@DenisDrobyshev

Copy link
Copy Markdown
Member

Every other library in the organisation publishes a documentation site. stadion did not — its homepage pointed at PyPI and the README carried everything.

Five pages, built from the README rather than newly invented:

Page What it holds
index.md What the project is, why the optimum matters, what a run looks like
tasks.md The six tasks, the classical method and optimum for each, the headroom table
agents.md The act(view) contract, both surfaces, reading the score
protocol.md Generated instances, the tuning budget, pairing, degenerate scales
verify.md stadion verify and why it is the check that matters

Two things stated plainly that the README left implicit

A score slightly above 1 is sampling noise. The optimum is optimal in expectation, and a finite run scatters around its mean. Only a score clearly above 1, with an interval that does not reach back down to it, is a bug report. Left unqualified, the first reader to see 1.02 files the wrong issue.

report.degenerate is worth handling rather than ignoring. The agent page says so and links the protocol section explaining why the scale sometimes has no denominator.

Corrected

The Status section said "Not yet on PyPI" — four lines under an install command that reads pip install stadion-rl, and after the 0.1.0 release went out. It now links PyPI and the documentation.

Verified

mkdocs build --strict passes: six pages, no broken internal link, nothing outside the navigation.

The theme is configured font: false and the built HTML makes no third-party request — checked against the output rather than assumed. The only external href in a built page is the canonical link. No Google Fonts.

site/ added to .gitignore, since the site is published from CI rather than committed.

After merging

Pages has to be pointed at Actions, and the repository homepage moved off PyPI:

gh api -X POST /repos/DrobyshevDev/stadion/pages -f build_type=workflow
gh api -X PATCH /repos/DrobyshevDev/stadion -f homepage=https://drobyshevdev.github.io/stadion/

Once that is live, the organisation site can link it — the front page deliberately does not yet, because https://drobyshevdev.github.io/stadion/ is currently a 404.

Every other library in the organisation publishes a documentation site.
stadion did not, so its homepage pointed at PyPI and the README carried
everything.

Five pages, all built from the README rather than newly invented: what the
project is and what a run looks like, the six tasks with their headroom table,
writing an agent, the protocol, and the self-check.

Two things the README did not say plainly enough to leave implicit:

A score slightly above 1 is sampling noise - the optimum is optimal in
expectation, and a finite run scatters around its mean. Only a score clearly
above 1, with an interval that does not reach back down, is a bug report. Left
unqualified, the first reader to see 1.02 would file the wrong issue.

`report.degenerate` is worth handling rather than ignoring, so the agent page
says so and links the protocol section that explains why the scale sometimes
has no denominator.

Also corrected: the Status section said "Not yet on PyPI" four lines under an
install command that reads `pip install stadion-rl`. It has been on PyPI since
the 0.1.0 release.

Built with `--strict`, which fails on a broken internal link or a page outside
the navigation. The theme is configured `font: false` and the built HTML makes
no third-party request - verified against the output, not assumed.
@DenisDrobyshev
DenisDrobyshev merged commit 743169e into main Aug 23, 2026
12 checks passed
@DenisDrobyshev
DenisDrobyshev deleted the docs-site branch August 23, 2026 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant