docs(readme): the module system shipped #3

Merged
whitlocktech merged 1 commits from docs/module-system-shipped into main 2026-08-12 23:05:26 +00:00
Member

The org landing page's half of the module-system cutover (website#150). Merges after it.

One paragraph, retired

The quick start's "install a module" section carried a caveat telling a visitor that the Modules screen it had just finished describing wasn't on main yet, and that a checkout served the Ultima Online features from core directly. Both halves became false at the cutover, and the note now contradicts the page around it — on the repo's front door, which is the worst place to be wrong.

Replaced rather than deleted: a reader who saw the old note deserves to know it resolved, and the replacement carries the one fact this page owes about the change — a main checkout is a game-agnostic core, and Ultima Online arrives as the module the section above tells you to install.

Nothing else needed touching

Worth saying, since the landing page goes stale silently and is usually the last thing anyone checks. It was written describing the module system as the shape of the project rather than as work in progress — the repo table, the data-path diagram, the three-things quick start and the Integration-kit row are all still accurate — which is exactly what left one paragraph to retire instead of a rewrite.

Risk

None. Single-paragraph edit to a README that nothing builds or imports.


🤖 AI-assisted: written with Claude Code (Claude Opus 5).

The org landing page's half of the module-system cutover ([website#150](https://gitea.whitlocktech.com/RunicGateway/website/pulls/150)). Merges after it. ## One paragraph, retired The quick start's "install a module" section carried a caveat telling a visitor that the Modules screen it had *just finished describing* wasn't on `main` yet, and that a checkout served the Ultima Online features from core directly. Both halves became false at the cutover, and the note now contradicts the page around it — on the repo's front door, which is the worst place to be wrong. Replaced rather than deleted: a reader who saw the old note deserves to know it resolved, and the replacement carries the one fact this page owes about the change — a `main` checkout is a game-agnostic core, and Ultima Online arrives as the module the section above tells you to install. ## Nothing else needed touching Worth saying, since the landing page goes stale silently and is usually the last thing anyone checks. It was written describing the module system as **the shape of the project** rather than as work in progress — the repo table, the data-path diagram, the three-things quick start and the Integration-kit row are all still accurate — which is exactly what left one paragraph to retire instead of a rewrite. ## Risk None. Single-paragraph edit to a README that nothing builds or imports. --- 🤖 AI-assisted: written with Claude Code (Claude Opus 5).
wtclaude added 1 commit 2026-08-12 23:04:33 +00:00
The quick start carried a caveat telling a visitor that the Modules screen it
had just described was not on `main` yet, and that a checkout served the Ultima
Online features from core directly. The cutover merged on 2026-08-12
(website#150), so both halves of that are now false and the caveat contradicts
the page around it.

Replaced rather than deleted: a reader who saw the old note deserves to know it
resolved, and the sentence that replaces it is the one fact the front page owes
about the change - a `main` checkout is a game-agnostic core, and Ultima Online
arrives as the module the section above tells you to install.

Nothing else on the page needed touching. It was written describing the module
system as the shape of the project rather than as work in progress, which is
what left exactly one paragraph to retire.

Co-Authored-By: Claude <noreply@anthropic.com>
whitlocktech merged commit 545590e7ff into main 2026-08-12 23:05:26 +00:00
whitlocktech deleted branch docs/module-system-shipped 2026-08-12 23:05:27 +00:00
Sign in to join this conversation.
No description provided.