All checks were successful
PR checks / checks (pull_request) Successful in 9m9s
PLAN.md §13 phase 4: /features/, /architecture/, /modules/, /integrations/, and /community/ — plus the two scope items the phase table never assigned to anyone. Six decisions taken by the org lead before coding, recorded in PLAN.md §10 as D20-D25: - D20 /features/ is the homepage's list with a `detail` line, not a second list. One data file, two renderings, so they cannot disagree about what exists. - D21 /architecture/ draws reasons, not reference: three new inline SVGs, one per boundary. No endpoint tables, no config keys — those are phase 8's and stay canonical in docs/. - D22 The deliberate absences of §2 become one tagged data file, rendered on the three pages that promise them. - D23 Phase 4 absorbs /community/ (specified in §10 and §14 N3, linked from the header since phase 1, built by no phase) and checkLinks.mjs. - D24 `needsModule`: writing the Teams detail exposed a false claim phase 3 shipped. Teams are module-sourced only — teams.module_id is NOT NULL, there is no create route, sync is gated on providerModuleId() — so the Community group no longer says a bare core does all of it. - D25 The per-capability demo affordance brand.json had promised since phase 2 is a deep link, filled at boot from data-demo-path. checkLinks.mjs reads the built HTML rather than src/, because half these links are assembled from data files and template literals. Its PLANNED_ROUTES list is checked in both directions, so it cannot rot into a permanent exemption. applyBrand.mjs gained a pass that recomputes deep links from their immutable path, making it idempotent and reversible; checkBrand.mjs lifts that pattern out and runs it against the stock markup so the two cannot drift. Both proved against a real mount, in both directions. Fixes a cascade bug the checks could not see: [data-demo-url=''] and a scoped component class are both specificity 0,1,0, so .demo-link's `display` beat the hide rule and twelve links to a nonexistent demo rendered, each resolving to the current page. The rule is now !important. The four diagrams' shared SVG vocabulary moved to src/styles/diagram.css. Verified from a clean checkout: npm ci, all five checks, astro check (0 errors), production build, and a live browser pass at desktop and 390px. Co-Authored-By: Claude <noreply@anthropic.com>
56 lines
1.5 KiB
Plaintext
56 lines
1.5 KiB
Plaintext
---
|
|
/**
|
|
* The opening of every marketing page except the homepage — eyebrow, `<h1>`, lede.
|
|
*
|
|
* A component rather than four copies of the same three elements, because phase 4 writes
|
|
* five pages and phases 5 and 6 write four more. The homepage is deliberately not one of
|
|
* them: its `<h1>` is the tagline inside the hero, set against the emblem, and pulling that
|
|
* into a shared header would either flatten the hero or push its layout in here (D19).
|
|
*
|
|
* The `<h1>` is the page's own name, not the product's, and `Base` appends the site name to
|
|
* the document title — so a page sets a short `title` and gets "Features — Runic Gateway"
|
|
* in the tab and "Features" on the page.
|
|
*/
|
|
interface Props {
|
|
/** Small uppercase line above the title. What kind of page this is. */
|
|
eyebrow: string;
|
|
title: string;
|
|
}
|
|
|
|
const { eyebrow, title } = Astro.props;
|
|
---
|
|
|
|
<header class="page section pagehead">
|
|
<p class="eyebrow">{eyebrow}</p>
|
|
<h1>{title}</h1>
|
|
<div class="prose pagehead__lede">
|
|
<slot />
|
|
</div>
|
|
</header>
|
|
|
|
<style>
|
|
/* The section rhythm gives generous space below; the header wants less, because the
|
|
first section under it is part of the same thought. */
|
|
.pagehead {
|
|
padding-bottom: clamp(1rem, 2.5vw, 1.75rem);
|
|
}
|
|
|
|
.pagehead h1 {
|
|
margin: 0 0 1rem;
|
|
font-size: clamp(2rem, 5vw, 2.9rem);
|
|
}
|
|
|
|
.pagehead__lede {
|
|
color: var(--muted);
|
|
font-size: 1.06rem;
|
|
}
|
|
|
|
.pagehead__lede :global(p) {
|
|
margin: 0 0 0.85rem;
|
|
}
|
|
|
|
.pagehead__lede :global(p:last-child) {
|
|
margin-bottom: 0;
|
|
}
|
|
</style>
|