Page · stable · v1.0.0 · owner: Site system lead · contract 19 of 20 points (open: figma)
Do and don't
Do: /
Declared by landing.tsA page declaration: hero → problem-section → lead-section → flow-section → job-section → proof-section → roles-section → founder-section → roadmap-strip → cta-section. Open associated page (declared association; rendered-page verification is separate).
Do: /ja/
Declared by landing.tsA page declaration: hero → problem-section → lead-section → flow-section → job-section → proof-section → roles-section → founder-section → roadmap-strip → cta-section. Open associated page (declared association; rendered-page verification is separate).
Don't: An unregistered block
Declared by landing.tsA page declaration: hero → problem-section → lead-section → flow-section → job-section → proof-section → roles-section → founder-section → roadmap-strip → cta-section. No captured page instance is attached.
Don't: Two fields touching
Declared by landing.tsA page declaration: hero → problem-section → lead-section → flow-section → job-section → proof-section → roles-section → founder-section → roadmap-strip → cta-section. No captured page instance is attached.
Rules
| Rule | Why | Check |
|---|---|---|
| Built pages follow: header, hero, problem-section?, lead-section?, flow-section?, job-section?, proof-section?, roles-section?, founder-section?, roadmap-strip?, cta-section, footer. | A declared composition is what makes the page checkable and the site consistent. | Automated: scripts/site/system/check-pages.ts (check_composition per page) |
| The existing page-landing shell opts its top-level non-hero sections into Layout’s progressive rendering policy; Hero remains eager and all content/section order stays in the DOM. | The initial promise must paint without eagerly laying out every lower-page illustration. | Automated: tests/site/progressive-rendering.spec.ts |
API
No props.
Contract details
The full contract: identity, anatomy, variants, states, tokens, layout, motion, accessibility, content, tests
Identity
| Aspect | Value |
|---|---|
| Id | page-landing |
| Layer | Pages |
| Category | page |
| Owner | Site system lead |
| Status | stable |
| Version | 1.0.0 |
| Source | apps/showcase/site/system/pages/landing.ts (private repository; the contract and the render function are this one module) |
| Version | Date | Change |
|---|---|---|
| 1.0.0 | 2026-10-26 | Landing as one module: its markup moved out of the page builder (scripts/site) into the system. |
Use when
- Paths matching /^\/(ja\/)?$/. Why: Every page of this kind is composed the same way, so readers learn it once.
Do not use when
- For a page with a different job. Why: A new kind of page gets its own declaration and review.
Anatomy
| Part | What it is |
|---|---|
| 1 | hero |
| 2 | problem-section (optional) |
| 3 | lead-section (optional) |
| 4 | flow-section (optional) |
| 5 | job-section (optional) (repeats) |
| 6 | proof-section (optional) (repeats) |
| 7 | roles-section (optional) |
| 8 | founder-section (optional) |
| 9 | roadmap-strip (optional) |
| 10 | cta-section |
Made of: header, hero, problem-section, lead-section, flow-section, job-section, proof-section, roles-section, founder-section, roadmap-strip, cta-section, footer.
Used in: pages directly.
Variants
| Variant | When | Why |
|---|---|---|
| default | Wherever the page declaration places it. | One shape per job keeps pages predictable. |
States
| State | Rendered or not applicable |
|---|---|
| default | default |
| hover | Not applicable: The landing is not interactive, so it has no hover state. |
| focus-visible | Not applicable: The landing does not take focus; links and buttons inside it carry their own focus ring. |
| active | Not applicable: The landing cannot be pressed. |
| disabled | Not applicable: The landing has nothing to disable. |
| loading | Not applicable: The landing is rendered at build time and is complete when the page loads. |
| empty | Not applicable: The landing is not rendered without content; the builder skips it. |
| error | Not applicable: The landing shows no data that can fail. |
| current | Not applicable: The landing has no current item. |
| visited | Not applicable: The landing is not a link. |
| expanded | Not applicable: The landing does not open or close. |
Tokens
| Part | Token |
|---|---|
| page.ground | --cotton |
Layout
| Aspect | Value |
|---|---|
| breakpoints | Required review at 390, 768, 1024 and 1440 px; execution is not implied by this declaration; columns stack under 768 px; the wrap keeps a 16 px gutter on phones. |
| wrapping | Text wraps; nothing scrolls sideways. |
| textExpansion | Japanese runs 20 to 40% longer; headings break between phrases (jaBreaks) and blocks grow downwards. |
Spacing and rhythm
| Aspect | Value |
|---|---|
| internal | Each template's own padding. |
| external | None. |
| rhythm | Field, cotton, field: never two fields touching; the woven edge at each join (D-SITE-002, D-SITE-003). |
Motion
| Aspect | Value |
|---|---|
| None | No intrinsic element animation. The optional claude-entrance consumer profile may translate below-fold structure once (20px, --dur-weave, --ease-enter, --stagger); reduced motion disables it. This preserved baseline entrance is separate from element playback. |
Runtime and reuse
Render-only element; mount any registered child enhancements separately. Preserve required Site CSS, fonts, responsive and locale rules from nativeElement.
Accessibility passport
| Aspect | Value |
|---|---|
| role | a landmark or list, as stated in its parts |
| name | Its visible text |
| keyboard | Links and buttons inside, in reading order. |
| focus | The --focus ring on every link and button inside. |
| screenReader | Read in source order; decorative weaving is aria-hidden. |
| contrast | Ink on cotton 14:1; text on every dye field 4.5:1 or better (checked by check-brand). |
| target | Links and buttons are 44 px tall. |
Content
| Slot | Length | Voice |
|---|---|---|
| hero: promise and actions | One opening promise using the Hero template's existing content limits. | Explain what Loom does and the reader's first step. |
| declared sections: argument and proof | Keep the declared section order; repeated jobs and proofs each make a distinct point before the closing action. | Support claims with attributable demonstrations; label coming work and sample results. |
Good: “The four jobs lead to named examples and a clear conversation or health-check action.”
Bad: “A sequence of unsupported slogans or a future feature shown as working proof.”
Japanese: Use the existing Japanese landing copy and section content, preserving the same argument and declared sequence. Translation presence is separate from native-language review; long headings remain subject to their owning template rules.
Icons and illustrations
None: this element uses no icon or illustration of its own.
Decisions and exceptions
- D-SITE-002: A field is always followed by cotton; two fields never touch
- D-SITE-003: The woven edge sits at every field/cotton join, and nowhere else
Usage
2 uses across the built pages (measured by npm run site:system).
Tests
| Aspect | Value |
|---|---|
| unit | tests/unit/site-system.test.ts: renders every do and don't example through the registry and checks the classes it owns |
| visual | Not yet: there are no screenshot baselines; the Library page is checked for sideways scroll at 1440 px by tests/site/system.spec.ts |
| a11y | tests/site/system.spec.ts: axe (0 serious or critical) on the element's Library page in light and dark |
| parity | scripts/site/system/check.ts: Library examples are rendered by the same render function the site imports |
Figma
not-yet: The Loom Site Figma library is the last stage of the plan; this element is not mapped yet.