feat(site): phase 17 - per-game module pages, /runicnpc/, and checkTerms over the built site
All checks were successful
PR checks / checks (pull_request) Successful in 2m37s
All checks were successful
PR checks / checks (pull_request) Successful in 2m37s
PLAN.md §16 phase 17, built on the org lead's answers of 2026-10-22, recorded as D75-D79 (count of record 79). - D75: core marketing pages describe what a game module adds in core's words. "Game intelligence" became "What a game module adds"; each game's own list moved to src/data/games/ and renders only on the new /modules/uo/ and /modules/rust/. /modules/ is a card per game. - The page-side capability check is per game (assertGameCoverage), the item phase 13 moved here. - D76: the homepage keeps its game screenshot, labelled. screens.mjs entries may carry `game` (D67); Screenshot.astro and the app grid print the game's name and mark the figure data-game. - D77: /app/ describes the Rust screens (released the same day). - D78: /runicnpc/, the standalone page, is in the header and footer; the narrow header was re-measured so five links keep two rows. - D79: checkTerms.mjs --built reads every built page's visible text after the build; game routes and data-game elements allow their game's words. Proven against ten plants. Still the twelfth check. - Re-read fixes: /architecture/'s "two machines is also the maximum", Discord "guild" on /integrations/, and collection.mjs against what Steam sign-in and the Rust module keep (PLAY_DATA_SAFETY.md regenerated; the Play answers are unchanged). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
107
src/components/GameFeatures.astro
Normal file
107
src/components/GameFeatures.astro
Normal file
@@ -0,0 +1,107 @@
|
||||
---
|
||||
import type { Capability } from '../data/capabilities.mjs';
|
||||
|
||||
/**
|
||||
* A game's own feature list, with the argument for each — PLAN.md §16, phase 17.
|
||||
*
|
||||
* Rendered only by a game's page under `/modules/` (`GAME_ROUTES` in `checkTerms.mjs`),
|
||||
* which is what lets the items be written in the game's own words. It is `/features/`'s
|
||||
* card treatment (D20: the label and the detail, never the label alone), so a reader who has
|
||||
* seen that page reads this one the same way.
|
||||
*
|
||||
* A feature with a `demoPath` gets the per-capability demo link of D25. The markup is the
|
||||
* exact contract `scripts/checkBrand.mjs` enforces and `applyBrand.mjs` rewrites at boot —
|
||||
* see the note in `/features/` before touching it. A stock build hides every one.
|
||||
*/
|
||||
interface Props {
|
||||
title: string;
|
||||
lede?: string;
|
||||
items: Capability[];
|
||||
}
|
||||
|
||||
const { title, lede, items } = Astro.props;
|
||||
---
|
||||
|
||||
<section class="page section feats">
|
||||
<h2>{title}</h2>
|
||||
{lede && <p class="prose feats__lede">{lede}</p>}
|
||||
|
||||
<ul class="feats__items">
|
||||
{
|
||||
items.map((item) => (
|
||||
<li class="panel feats__item">
|
||||
<h3>{item.label}</h3>
|
||||
<p class="feats__detail">{item.detail}</p>
|
||||
{item.demoPath && (
|
||||
<a
|
||||
class="demo-link"
|
||||
href="" data-demo-url="" data-demo-path={item.demoPath}
|
||||
rel="noopener noreferrer"
|
||||
>
|
||||
See it running
|
||||
</a>
|
||||
)}
|
||||
</li>
|
||||
))
|
||||
}
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<style>
|
||||
.feats h2 {
|
||||
margin: 0;
|
||||
font-size: clamp(1.5rem, 3vw, 1.95rem);
|
||||
}
|
||||
|
||||
.feats__lede {
|
||||
margin: 0.85rem 0 0;
|
||||
color: var(--muted);
|
||||
}
|
||||
|
||||
.feats__items {
|
||||
display: grid;
|
||||
gap: 1rem;
|
||||
margin: 1.75rem 0 0;
|
||||
padding: 0;
|
||||
list-style: none;
|
||||
grid-template-columns: repeat(auto-fit, minmax(min(100%, 21rem), 1fr));
|
||||
}
|
||||
|
||||
.feats__item {
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
}
|
||||
|
||||
.feats__item h3 {
|
||||
margin: 0 0 0.6rem;
|
||||
color: var(--gold);
|
||||
font-size: 1.04rem;
|
||||
}
|
||||
|
||||
.feats__detail {
|
||||
flex: 1;
|
||||
margin: 0;
|
||||
color: var(--muted);
|
||||
font-size: 0.94rem;
|
||||
}
|
||||
|
||||
/* As on /features/: a link rather than a button, and the flex item itself, so the
|
||||
global rule that hides an empty demo link takes its margin with it. */
|
||||
.demo-link {
|
||||
display: inline-flex;
|
||||
align-items: center;
|
||||
gap: 0.35rem;
|
||||
margin-top: 1rem;
|
||||
color: var(--portal);
|
||||
font-size: 0.88rem;
|
||||
text-decoration-color: color-mix(in srgb, var(--portal) 40%, transparent);
|
||||
}
|
||||
|
||||
.demo-link:hover {
|
||||
color: var(--portal-bright);
|
||||
}
|
||||
|
||||
.demo-link::after {
|
||||
content: '\2197';
|
||||
}
|
||||
</style>
|
||||
@@ -28,6 +28,8 @@ const brand = renderBrand(Astro);
|
||||
const links = [
|
||||
{ href: '/features/', label: 'Features' },
|
||||
{ href: '/docs/', label: 'Docs' },
|
||||
// D78 (phase 17): the standalone RunicNPC page, for a Rust server owner who runs no site.
|
||||
{ href: '/runicnpc/', label: 'RunicNPC' },
|
||||
{ href: '/app/', label: 'App' },
|
||||
{ href: '/community/', label: 'Community' },
|
||||
];
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
import { screenById, WEB, PHONE } from '../data/screens.mjs';
|
||||
import platform from '../data/platform.json';
|
||||
|
||||
/**
|
||||
* One screenshot, as a figure with its caption. PLAN.md §13 phase 9, D4 / D44.
|
||||
@@ -44,9 +45,16 @@ const src = `/screens/${shot.id}.webp`;
|
||||
// taken at one geometry (see screens.mjs), and `checkScreens.mjs` asserts the files really
|
||||
// are that size, so these attributes cannot drift from the pixels.
|
||||
const { width, height } = shot.family === 'web' ? WEB : PHONE;
|
||||
|
||||
// D67: a game's screen says whose it is. The name comes from `platform.json`, as
|
||||
// GameExample's does, so the label cannot disagree with the tag the check reads.
|
||||
const game = shot.game ? platform.games[shot.game] : null;
|
||||
if (shot.game && !game) {
|
||||
throw new Error(`Screenshot "${id}" is tagged game "${shot.game}", which platform.json does not have`);
|
||||
}
|
||||
---
|
||||
|
||||
<figure class="shot">
|
||||
<figure class="shot" data-game={shot.game}>
|
||||
<img
|
||||
src={src}
|
||||
alt={shot.alt}
|
||||
@@ -55,7 +63,14 @@ const { width, height } = shot.family === 'web' ? WEB : PHONE;
|
||||
loading="lazy"
|
||||
decoding="async"
|
||||
/>
|
||||
{!bare && <figcaption>{shot.caption}</figcaption>}
|
||||
{
|
||||
(game || !bare) && (
|
||||
<figcaption>
|
||||
{game && <span class="shot__game">{game.name}</span>}
|
||||
{!bare && shot.caption}
|
||||
</figcaption>
|
||||
)
|
||||
}
|
||||
</figure>
|
||||
|
||||
<style>
|
||||
@@ -78,4 +93,18 @@ const { width, height } = shot.family === 'web' ? WEB : PHONE;
|
||||
font-size: 0.9rem;
|
||||
line-height: 1.5;
|
||||
}
|
||||
|
||||
/* The game's name, ahead of the caption (D67). Styled here rather than with the global
|
||||
chip, because the docs pages render this component without the marketing stylesheet. */
|
||||
.shot__game {
|
||||
display: inline-block;
|
||||
margin-right: 0.5rem;
|
||||
padding: 0.05rem 0.55rem;
|
||||
border: 1px solid var(--line);
|
||||
border-radius: var(--radius-pill);
|
||||
color: var(--muted);
|
||||
font-size: 0.76rem;
|
||||
letter-spacing: 0.04em;
|
||||
white-space: nowrap;
|
||||
}
|
||||
</style>
|
||||
|
||||
63
src/components/SupportedGames.astro
Normal file
63
src/components/SupportedGames.astro
Normal file
@@ -0,0 +1,63 @@
|
||||
---
|
||||
import { games } from '../data/games/index.mjs';
|
||||
|
||||
/**
|
||||
* "Supported games: Ultima Online · Rust" — PLAN.md §16, D63.
|
||||
*
|
||||
* The one place a core page names the games, and the way it hands a reader on to them. Core
|
||||
* pages describe what a game module adds in core's words (D75); this strip is the link to
|
||||
* the page where each game says it in its own. The names come from `platform.json` through
|
||||
* `games/index.mjs`, so a third game appears here the day it is added there.
|
||||
*/
|
||||
interface Props {
|
||||
/** Extra class for the caller's spacing. */
|
||||
class?: string;
|
||||
}
|
||||
|
||||
const { class: className } = Astro.props;
|
||||
---
|
||||
|
||||
<p class:list={['games', className]}>
|
||||
<span class="games__label">Supported games</span>
|
||||
{
|
||||
games.map((game, index) => (
|
||||
<>
|
||||
{index > 0 && <span class="games__sep" aria-hidden="true">·</span>}
|
||||
<a class="games__link" href={game.href}>
|
||||
{game.name}
|
||||
</a>
|
||||
</>
|
||||
))
|
||||
}
|
||||
</p>
|
||||
|
||||
<style>
|
||||
.games {
|
||||
display: flex;
|
||||
flex-wrap: wrap;
|
||||
align-items: baseline;
|
||||
gap: 0.35rem 0.65rem;
|
||||
margin: 0;
|
||||
font-size: 0.95rem;
|
||||
}
|
||||
|
||||
.games__label {
|
||||
color: var(--dim);
|
||||
font-size: 0.78rem;
|
||||
letter-spacing: 0.08em;
|
||||
text-transform: uppercase;
|
||||
}
|
||||
|
||||
.games__label::after {
|
||||
content: ':';
|
||||
}
|
||||
|
||||
.games__sep {
|
||||
color: var(--dim);
|
||||
}
|
||||
|
||||
.games__link {
|
||||
color: var(--gold);
|
||||
font-weight: 600;
|
||||
}
|
||||
</style>
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
import { screensOf, PHONE } from '../../data/screens.mjs';
|
||||
import platform from '../../data/platform.json';
|
||||
|
||||
/**
|
||||
* The app's screenshot strip. Reserved in phase 5 (D26), filled in phase 9.
|
||||
@@ -45,7 +46,7 @@ const shots = screensOf('phone');
|
||||
|
||||
<ul class="shots__grid">
|
||||
{shots.map((shot) => (
|
||||
<li class="shots__item">
|
||||
<li class="shots__item" data-game={shot.game}>
|
||||
<img
|
||||
src={`/screens/${shot.id}.webp`}
|
||||
alt={shot.alt}
|
||||
@@ -54,7 +55,10 @@ const shots = screensOf('phone');
|
||||
loading="lazy"
|
||||
decoding="async"
|
||||
/>
|
||||
<p class="shots__caption">{shot.caption}</p>
|
||||
<p class="shots__caption">
|
||||
{shot.game && <span class="shots__game">{platform.games[shot.game].name}</span>}
|
||||
{shot.caption}
|
||||
</p>
|
||||
</li>
|
||||
))}
|
||||
</ul>
|
||||
@@ -91,6 +95,19 @@ const shots = screensOf('phone');
|
||||
box-shadow: var(--shadow-card);
|
||||
}
|
||||
|
||||
/* The game's name on a game's screen (D67), as Screenshot.astro prints it. */
|
||||
.shots__game {
|
||||
display: inline-block;
|
||||
margin-right: 0.5rem;
|
||||
padding: 0.05rem 0.55rem;
|
||||
border: 1px solid var(--line);
|
||||
border-radius: var(--radius-pill);
|
||||
color: var(--muted);
|
||||
font-size: 0.74rem;
|
||||
letter-spacing: 0.04em;
|
||||
white-space: nowrap;
|
||||
}
|
||||
|
||||
.shots__caption {
|
||||
margin: 0.85rem 0 0;
|
||||
color: var(--dim);
|
||||
|
||||
@@ -26,8 +26,8 @@ import platform from '../../data/platform.json';
|
||||
<p class="eyebrow">Where the game stops</p>
|
||||
<h2>A seam, with a version on it</h2>
|
||||
<p class="prose">
|
||||
The core site does not know what a shard is, what a guild is, or that Ultima Online
|
||||
exists. Everything that does lives in an installable module on the other side of a
|
||||
The core site does not know what game it serves, what that game calls a group of
|
||||
players, or that Ultima Online and Rust exist. Everything that does lives in an installable module on the other side of a
|
||||
declared interface — which is what makes "put your game on it" a shape rather than a
|
||||
slogan.
|
||||
</p>
|
||||
@@ -123,8 +123,8 @@ import platform from '../../data/platform.json';
|
||||
<p>
|
||||
Core owns the Teams primitive — the roster, the forum, the notifications, the voice
|
||||
channel — and does not own the <em>word</em>. A Team cannot be created in core at
|
||||
all; it arrives from the module, which is why the UO module calls them guilds and
|
||||
builds those pages itself. That is the pattern the whole interface is built on: core
|
||||
all; it arrives from the module, which is why each module calls them by its own
|
||||
game’s word and builds those pages itself. That is the pattern the whole interface is built on: core
|
||||
supplies the machinery, the module supplies the meaning.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
@@ -9,7 +9,10 @@
|
||||
* doing capacity planning, and "how many machines is this" is the first question they have.
|
||||
*
|
||||
* Drawn generically for the same reason the homepage's diagram is (D17) — "your game host",
|
||||
* not "your ServUO box" — with the prose beside it naming the real components. The boundary
|
||||
* not a particular game's server — with the prose beside it linking to each game's page,
|
||||
* which names its real components (D75). Until phase 17 the caption named one game's and
|
||||
* said two machines was also the maximum, which stopped being true when Rust shipped: one
|
||||
* sidecar serves one server, so six servers means six sidecars. The boundary
|
||||
* is the one drawn argument: everything above it is reachable because you published it, and
|
||||
* everything below it is not reachable at all.
|
||||
*
|
||||
@@ -73,8 +76,10 @@
|
||||
</svg>
|
||||
|
||||
<p class="diagram__caption">
|
||||
Today the game server is a ServUO shard and the sidecar is uo-link. Two machines is
|
||||
the minimum and also the maximum — nothing here scales by adding a third.
|
||||
The sidecar and the bridge plugin are each game’s own — see
|
||||
<a href="/modules/uo/">Ultima Online</a> and <a href="/modules/rust/">Rust</a>. Two
|
||||
machines is the minimum. A community running several game servers runs a sidecar
|
||||
beside each one, on whichever host that server already lives on.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
@@ -92,10 +97,10 @@
|
||||
<section>
|
||||
<h3>The game host</h3>
|
||||
<p>
|
||||
The machine your game server is already on. One installer binary puts the plugin
|
||||
into the server's tree, installs the sidecar beside it and registers the service —
|
||||
then prints four values. It never contacts your website; you paste those four
|
||||
values into the admin panel yourself, and that is the moment the two halves meet.
|
||||
The machine your game server is already on. One installer binary puts the bridge
|
||||
plugin into the server's tree, installs the sidecar beside it and registers the
|
||||
service — then prints what the site needs. It never contacts your website; you enter
|
||||
those values in the admin panel yourself, and that is the moment the two halves meet.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
import platform from '../../data/platform.json';
|
||||
import { capabilityGroups, assertCapabilityCoverage } from '../../data/capabilities.mjs';
|
||||
import { capabilityGroups } from '../../data/capabilities.mjs';
|
||||
import { games, assertGameCoverage } from '../../data/games/index.mjs';
|
||||
import SupportedGames from '../SupportedGames.astro';
|
||||
|
||||
/**
|
||||
* The grouped capabilities (PLAN.md §10). All five groups, named only — the argument for
|
||||
@@ -8,8 +9,10 @@ import { capabilityGroups, assertCapabilityCoverage } from '../../data/capabilit
|
||||
* copy to keep true.
|
||||
*
|
||||
* The call below is the point of the exercise: it throws, and therefore fails the build, if
|
||||
* the "Game intelligence" list and the module's own declared capabilities have drifted
|
||||
* apart. `checkFacts.mjs` already keeps `platform.json` honest against the module manifest;
|
||||
* either game's own feature list (`src/data/games/`) and its module's declared capabilities
|
||||
* have drifted apart. The homepage names neither list — its module-supplied group is the
|
||||
* neutral one, in core's words (D75) — but it is the page a reader meets first, so it is
|
||||
* the page that should refuse to build when a game page is out of date. `checkFacts.mjs` already keeps `platform.json` honest against the module manifest;
|
||||
* this makes the page honest against `platform.json`, which is the half that was missing.
|
||||
*
|
||||
* The "not built" line at the bottom is not a disclaimer bolted on — §2's absent-features
|
||||
@@ -17,17 +20,18 @@ import { capabilityGroups, assertCapabilityCoverage } from '../../data/capabilit
|
||||
* what exists while quietly omitting the well-known things that do not is the exact failure
|
||||
* §1 is written to prevent.
|
||||
*/
|
||||
assertCapabilityCoverage(platform.games.uo.module.capabilities);
|
||||
for (const game of games) assertGameCoverage(game.key);
|
||||
---
|
||||
|
||||
<section class="page section caps">
|
||||
<p class="eyebrow">What it does</p>
|
||||
<h2>A community site, and a window into the game</h2>
|
||||
<p class="prose caps__lede">
|
||||
The core is game-agnostic: it does not know what a shard is. Everything that does arrives
|
||||
as an installable <a href="/modules/">module</a>, which is why the same platform can carry
|
||||
a different game without a fork.
|
||||
The core is game-agnostic: it does not know what game you run. Everything that does
|
||||
arrives as an installable <a href="/modules/">module</a>, which is why the same platform
|
||||
carries two games without a fork.
|
||||
</p>
|
||||
<SupportedGames class="caps__games" />
|
||||
|
||||
<div class="caps__grid">
|
||||
{
|
||||
@@ -69,6 +73,10 @@ assertCapabilityCoverage(platform.games.uo.module.capabilities);
|
||||
color: var(--muted);
|
||||
}
|
||||
|
||||
.caps__games {
|
||||
margin-top: 1.25rem;
|
||||
}
|
||||
|
||||
.caps__grid {
|
||||
display: grid;
|
||||
gap: 1rem;
|
||||
|
||||
@@ -4,7 +4,7 @@ import { brand } from '../../lib/brand.mjs';
|
||||
/**
|
||||
* The get-started CTA (PLAN.md §10, the `/` row), built around the trap in §10's
|
||||
* "installation path": a "Runic Gateway install" is two independent installs. The installer
|
||||
* binary sets up the shard side only and never contacts the website; the website is a
|
||||
* binary sets up the game side only and never contacts the website; the website is a
|
||||
* separate Docker deployment.
|
||||
*
|
||||
* That belongs on the homepage rather than being saved for the docs. It is the single
|
||||
@@ -13,7 +13,9 @@ import { brand } from '../../lib/brand.mjs';
|
||||
* project. Saying it here is what makes the docs a confirmation rather than a surprise.
|
||||
*
|
||||
* The two halves are ordered site-first because that is the order they must be done in: the
|
||||
* shard side ends by pasting four values into the site's admin panel, which has to exist.
|
||||
* game side ends by entering what the installer printed into the site's admin panel, which
|
||||
* has to exist. Which screen that is belongs to the game module, so this says "the game
|
||||
* module's screen" rather than naming one game's menu (D63).
|
||||
*
|
||||
* Both "read the docs" links point at `/docs/` rather than at a page inside the journey.
|
||||
* Phases 7 and 8 write those pages and own their slugs; guessing one now would put a URL in
|
||||
@@ -44,9 +46,10 @@ import { brand } from '../../lib/brand.mjs';
|
||||
<div class="start__half">
|
||||
<h3><span class="start__num">2</span> The game side</h3>
|
||||
<p>
|
||||
One binary, run on the machine the game server already lives on. It syncs the plugin,
|
||||
installs the sidecar as a service, and prints four values. You paste those into
|
||||
Admin → Shard, and the two halves find each other.
|
||||
One binary, run on the machine the game server already lives on — or, for Rust, a
|
||||
Pterodactyl egg. It puts the bridge plugin in place, installs the sidecar, and prints
|
||||
what the site needs. You enter that on the game module’s screen in the admin panel,
|
||||
and the two halves find each other.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -9,12 +9,18 @@ import Screenshot from '../Screenshot.astro';
|
||||
* -----------------------------------------------------------------------------------------
|
||||
* `DataPath` above it draws the claim — a private game server, a sidecar, a public site —
|
||||
* and a diagram of a data path is a promise that the data arrives. This is the page where
|
||||
* it arrives, captured from a deployment wired to a running shard, so the section directly
|
||||
* under the diagram is the diagram's evidence.
|
||||
* it arrives, captured from a deployment wired to a running game server, so the section
|
||||
* directly under the diagram is the diagram's evidence.
|
||||
*
|
||||
* It is one game's screen, and says so (D76, taken in phase 17 under D67): the screenshot is
|
||||
* tagged `uo` in `screens.mjs`, so it prints "Ultima Online" beside it and may keep that
|
||||
* game's words in its alt and caption. A core screen was the alternative and was declined:
|
||||
* the claim here is live game state on a public page, which no core screen shows. Phase 18
|
||||
* adds a Rust capture beside it, labelled the same way.
|
||||
*
|
||||
* A gallery here would compete with `Capabilities` further down, which is the part of the
|
||||
* homepage that enumerates. So: one figure, the signature screen, and the rest of the set
|
||||
* on `/features/` where each one sits beside the claim it supports.
|
||||
* on each game's page under `/modules/`, where each one sits beside the claim it supports.
|
||||
*/
|
||||
---
|
||||
|
||||
@@ -22,9 +28,9 @@ import Screenshot from '../Screenshot.astro';
|
||||
<p class="eyebrow">What it looks like</p>
|
||||
<h2>The other end of that diagram</h2>
|
||||
<p class="prose looks__lede">
|
||||
A demo deployment with a real shard behind it. The gold supply, the state of the link and
|
||||
the player online in Britain are all read from the game server over the bridge. None of it
|
||||
is typed in, and none of it is a mock-up.
|
||||
A demo deployment with a real Ultima Online server behind it. The gold supply, the state
|
||||
of the link and the player online in Britain are all read from the game server over the
|
||||
bridge. None of it is typed in, and none of it is a mock-up.
|
||||
</p>
|
||||
|
||||
<Screenshot id="shard-status" />
|
||||
|
||||
Reference in New Issue
Block a user