template

Landing-page implementation plan

Map approved landing-page inputs to routes, components, files, milestones, acceptance checks, and non-goals before code.

Inputs read

project-brief.md
knowledge-base.md
design.md
Approved public assets:

Proposed structure

Route	Purpose	Source content	Components	Acceptance check
`/`

File plan

File or folder	Create/change	Why

Milestones

Each milestone must run locally and end with a reviewable diff or commit.

Foundation: Astro shell, tokens, metadata baseline.
Content: approved sections and real assets.
Responsive pass: narrow and wide layouts.
Interaction: navigation, forms, or links required by the brief.
Quality: accessibility, link, content, and production-build checks.

Integrations

For each integration, state the need, data sent, credentials required, cost surface, and fallback. Write None when the brief requires none.

Checks

Development server:
Production build:
Narrow viewport:
Wide viewport:
Keyboard route:
Link check:
Content/claim review:

Non-goals

-

Approval

☐ Every route and integration traces to the brief.
☐ No missing content has been replaced with invented copy.
☐ The milestones are small enough to review and recover.
☐ The owner approves code generation.