TenantAtlas/specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.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.6 KiB

Mapping: Spec 218 - Website Homepage Hero

Status

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

Spec 218 keeps the hero contract narrow and semantic. AstroDeck may only be used as a hero substrate when it preserves one clear anchor, one CTA pair, product-near truth, and bounded trust cues.

Mapping Records

Requirement reference Candidate primitive(s) Disposition Adaptation summary Acceptance mapping materialDriftReferences exceptionReference
Hero text core: category context, headline, supporting copy adk-section-hero-split-media adapt Keep one clear product category cue, one headline, and one supporting-copy block; remove stacked marketing slogans and filler text. 218 FR-001, FR-002, FR-005, FR-006, FR-007, FR-013, FR-014 none none
One dominant primary CTA plus one lower-emphasis secondary CTA adk-component-primary-button, adk-component-secondary-button adapt Preserve the Contact-first action with one deepening CTA and remove any additional equal-weight buttons. 218 FR-008, FR-009, FR-016 none none
Product-near visual truth adk-section-hero-split-media, adk-component-card-surface adapt Replace generic analytics wallpaper with a governance-specific product visual or truthful placeholder tied to change history, review, restore, or drift. 218 FR-010, FR-011, FR-015, FR-020 none none
Optional bounded trust chips adk-component-badge-chip adapt Reduce AstroDeck hero chips to a small set of factual, supportable trust cues. 218 FR-012, FR-013 none none
Anti-pattern removal and mobile meaning order adk-section-proof-stats, adk-section-logo-strip, adk-section-testimonial-stack, adk-section-hero-split-media remove Remove badge walls, fake proof, and extra CTA pressure; preserve headline, copy, CTA, visual, and optional trust chips on mobile. 218 FR-017, FR-018, FR-019, FR-022 none none

Replacement Tasks

  1. Bind adk-section-hero-split-media to the homepage hero and reduce it to the allowed semantic structure before any art-direction pass starts.
  2. Adapt adk-component-primary-button and adk-component-secondary-button into the Contact-first CTA pair with no competing primary actions.
  3. Replace AstroDeck demo hero imagery with a governance-specific product visual or a truthful approximation derived from real product structure.
  4. Reduce adk-component-badge-chip usage to a small bounded trust-subclaim set that routes deeper context to /trust.
  5. Remove hero-adjacent proof stats, logo strips, testimonials, and extra CTA blocks that dilute the primary anchor.
  6. Verify the mapped hero preserves headline-first reading order, CTA visibility, and product-near proof on narrow screens before the homepage section pass is considered complete.

Spread Control and Acceptance Trace

  • Spread control: this sheet does not authorize a bespoke hero framework or a custom visual language separate from the Spec 214 foundation.
  • Acceptance trace: the mapping covers the required hero text core, CTA pair, product-near visual, bounded trust cues, mobile meaning order, and anti-pattern rejection from Spec 218.
  • Exception note: no exception is approved. A future exception would need to prove that the mounted AstroDeck hero family cannot preserve the current hero contract even after bounded adaptation.