Page-template catalogue

Designers and agents compare reader jobs, public contracts and implemented page patterns before choosing a composition. This extends the existing design-system catalogue; it introduces no component library or product claims.

Composition​

Read mode. The overview is a chooser, not the whole artifact. It leads to one specific template page per exact registry pattern ID, for example subject-index-template.tsx for the subject-index page pattern. The overview keeps the Storybook-inspired filter and cards so a designer can find the page type quickly; each template page then explains where the pattern is used, why it fits those routes, which components assemble it, what presentation risks matter, and what alternative template choices would change the page shape.

One overview article per exact registry pattern ID still groups live examples because the shared ID describes a contract shape, not identical implementation. Registry order and supplied reader jobs remain intact. Each article links to the specific explainer page, the public page-contract registry, live examples, and sources.

The Storybook showcase informs the name filter and compact two-column cards, not a new dependency. Cards show specimen and live-example counts beside implementation status. Name filtering matches displayed names and raw pattern IDs case-insensitively, preserves the typed value and registry order, and accepts any text. Empty results have a clear-filter recovery. Supporting specimens remain visible and are explicitly outside this filter. No owner identities, logos or outcome metadata are invented.

Named iframe specimens use this same route's specimen query. Each has its own document, headings and keyboard scope, with a full-page link for inspection. Unknown keys render the ordinary catalogue. Native disclosures toggle open and closed. Prompt movement stays within first/final boundaries; marketplace filtering can return to all choices. No extra error protocol is introduced.

Specimens and boundaries​

Fixtures supply fictional copy and no outcome claims. AgencyHome and the finder’s featured jobs own fixed public text, identified as such rather than rewritten. All eight page-pattern directories have a rendered representative. Supporting story and venture components have smaller fixtures; composed parts render through their owners. Capability results and shape controls depend on finder state. Context-bound HomeDreamSeed, RelatedVentureApps and SouthernhagenReport have explicit exceptions with public source/live-context links rather than fictional persisted intent, app destinations or report metadata.

VentureHero is only the reusable opening of a page-private venture story. Other page-private pattern IDs get contract cards, not invented components. Navigation, copying and visible sample scores prove no beneficiary outcome. Humans retain consent, judgment and stop authority. Frames isolate URL changes from the catalogue, not storage or analytics permissions; existing copy actions remain real and labelled.

Verification​

test/components/PageTemplates.contract.test.tsx binds registry coverage and live routes. test/e2e/page-templates.spec.ts exercises the parent entry, frames, reversible disclosures, deck boundaries, empty marketplace recovery, unknown specimen fallback and page reflow across the repository's browser projects. Projection, publication, links and TypeScript checks remain authoritative. Specimen overflow is contained by the preview well rather than changing the underlying pattern.