TenantAtlas/specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md
ahmido 71f94c3afa
Some checks failed
Main Confidence / confidence (push) Failing after 44s
spec: finalize 223 AstroDeck rebuild planning consistency (#262)
## Summary
- finalize Spec 223 planning artifact set for AstroDeck website rebuild
- align `spec.md`, `plan.md`, `tasks.md`, `research.md`, `data-model.md`, `quickstart.md`, and contract schema
- add/complete inventory, mapping, exception, drift-follow-up, and supersession artifacts
- mark legacy website-spec task references as superseded and wire follow-up ownership

## Key Outcomes
- no remaining cross-artifact consistency findings in the Spec 223 bundle
- explicit Spec 213 handling path added
- material-drift follow-up rules normalized
- exception register and documented exception model made explicit and schema-backed

## Validation
- Integrated browser smoke check passed for main website routes (`/`, `/product`, `/trust`, `/changelog`, `/contact`, `/privacy`, `/imprint`, `/legal`, `/security-trust`)
- no console errors/warnings observed during route smoke navigation
- YAML contract parses successfully

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #262
2026-04-22 07:52:32 +00:00

3.7 KiB

Mapping: Spec 215 - Website Information Architecture / Core Pages

Status

Field Value
classification continuing
follow-up owner specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md
legacy task file specs/215-website-core-pages/tasks.md
exception outcome no exception required
material drift references none

Spec 215 is the canonical IA source of truth. AstroDeck may only be adopted in ways that preserve this route model, page priority, and navigation discipline.

Mapping Records

Requirement reference Candidate primitive(s) Disposition Adaptation summary Acceptance mapping materialDriftReferences exceptionReference
Required core routes: /, /product, /trust, /changelog, /contact, /privacy, /imprint adk-page-home-marketing, adk-page-product-overview, adk-page-trust-proof, adk-page-content-index, adk-page-contact-conversion, adk-page-legal-utility adapt Bind each canonical route to an AstroDeck page family without inheriting template route names or page priorities. 215 FR-002, FR-003, FR-006, FR-008, FR-010, FR-012, FR-013 none none
Small primary navigation plus trust/legal footer discoverability adk-component-header-nav, adk-component-footer-nav, adk-section-footer-utility adapt Keep top-level navigation intentionally small and group footer trust/legal/contact links according to Spec 215. 215 FR-014, FR-015, FR-017, FR-018, FR-019, FR-025 none none
Optional and deferred surfaces adk-page-content-index, adk-page-supporting-showcase, adk-section-logo-strip, adk-section-testimonial-stack remove Suppress template pricing, docs, case-study, resource-hub, logo-cloud, and testimonial promotion until an active spec turns them on. 215 FR-004, FR-005, FR-016, FR-021, FR-022, FR-024 none none
Retained secondary routes and compatibility behavior adk-page-supporting-showcase, adk-page-legal-utility, adk-page-trust-proof adapt Keep /legal, /terms, /solutions, and /integrations published as secondary surfaces; preserve /security-trust as a redirect to /trust. 215 FR-011, FR-020, FR-023, FR-027 none none

Replacement Tasks

  1. Bind AstroDeck page aliases for home, product, trust/proof, content index, contact, and legal utility before route-level implementation starts.
  2. Adapt adk-component-header-nav so primary discoverability remains Product, Trust, Changelog, and Contact with one CTA only.
  3. Repurpose adk-page-content-index into /changelog and keep optional Resources or editorial surfaces unpublished unless substantive content exists.
  4. Adapt adk-page-legal-utility for /privacy, /imprint, /terms, and the retained /legal hub without shipping template legal copy.
  5. Keep adk-page-supporting-showcase available only for /solutions and /integrations, and do not let those routes displace the required core IA.
  6. Add an AstroDeck route-suppression pass for pricing, docs, case-study, resource, team, and newsletter surfaces that are not yet active.
  7. Preserve /security-trust as redirect-only behavior once /trust is mapped to the canonical proof page.

Spread Control and Acceptance Trace

  • Spread control: no AstroDeck route becomes publicly discoverable unless Spec 215 already classifies it as required, retained secondary, or approved optional.
  • Acceptance trace: the mapping above preserves the required core routes, the small top-level navigation, trust visibility, changelog visibility, and contact primacy.
  • Exception note: no exception is approved. A future exception would need to show that the mounted snapshot lacks a usable content-index or legal-utility family entirely.