Manoel Freitas
cf1589c916
* feat: recreate public frontend with Heritage Editorial identity Replace placeholder visual system with EB Garamond/olive tokens, brand assets, editorial home narrative, São Paulo settings, real testimonials, and regenerated visual baselines. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: archive recreate-public-frontend and sync Heritage Editorial specs Merge delta requirements into main OpenSpec capabilities and move the completed change into the dated archive. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
1.9 KiB
1.9 KiB
ADDED Requirements
Requirement: Brand logo assets are available to the public layout
The system SHALL provide optimized Amare brand logo assets derived from the official faceted-heart lockup for use in the public header, footer and institutional pages. Assets MUST preserve the original geometry, include an accessible text alternative, and provide variants suitable for light and dark tonal fields. When site_settings.logo_path is present, the uploaded logo MUST be used; otherwise the versioned static brand asset MUST be used.
Scenario: Header renders brand mark with alt text
- WHEN any public page is rendered
- THEN the brand mark image or equivalent MUST expose accessible alternative text identifying Amare Assessoria
Scenario: Dark portfolio field uses a legible logo variant
- WHEN the brand mark is rendered on an olive-deep or otherwise dark public surface
- THEN the chosen logo variant MUST remain legible against that background
Scenario: Uploaded logo overrides static fallback
- GIVEN an admin has saved
logo_pathandlogo_altin site settings - WHEN the public layout renders the brand mark
- THEN the uploaded logo MUST be used instead of the static fallback
Requirement: Editorial image treatment remains self-hosted and deterministic
Public photography SHALL continue to use validated self-hosted uploads and responsive variants. Decorative saturation/contrast treatment for editorial mood MUST be applied via CSS on self-hosted images and MUST NOT introduce external image CDN dependencies that break deterministic visual tests.
Scenario: Public pages do not depend on external stock hosts
- WHEN the visual or browser suite loads covered public routes
- THEN content images MUST resolve from the application media disk or static fixtures
- AND MUST NOT require network access to third-party stock hosts