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>
This commit is contained in:
@@ -35,7 +35,7 @@ The system SHALL expose the public routes of SPEC §5.1: `home` (`/`), `services
|
||||
|
||||
### Requirement: Home renders the editorial structure from CMS content
|
||||
|
||||
The home page SHALL render, in the order defined by SPEC §6.2, header/navigation, hero, featured visual proof, services summary, working method, selected cases, testimonials, final briefing CTA, and footer with contact, social links and legal links (WEB-01). Hero copy, brand name and contact data MUST come from `site_settings`; services, cases and testimonials MUST come from published records.
|
||||
The home page SHALL render, in order: header/navigation, hero, manifesto, featured services summary, featured portfolio selection, working method (four steps), testimonials, Amare positioning/profile, final contact CTA, and footer with contact, social links and legal links (WEB-01). Hero copy, brand name, manifesto, method and principles MUST come from `site_settings` (with editorial defaults when optional fields are empty); services, cases and testimonials MUST come from published records. The home MUST follow the Heritage Editorial composition (asymmetric spreads on desktop, linear sequence on mobile) rather than rounded card grids.
|
||||
|
||||
#### Scenario: Published content is displayed in configured order
|
||||
|
||||
@@ -43,18 +43,21 @@ The home page SHALL render, in the order defined by SPEC §6.2, header/navigatio
|
||||
- **WHEN** a visitor loads the home
|
||||
- **THEN** the published content MUST be displayed following the `sort_order` and featured flags
|
||||
- **AND** the hero MUST show the values stored in `site_settings`
|
||||
- **AND** the manifesto, method and positioning sections MUST be present
|
||||
|
||||
#### Scenario: CTA leads to the briefing page
|
||||
#### Scenario: CTA leads to the contact placeholder page
|
||||
|
||||
- **WHEN** a visitor activates the primary or final CTA on the home
|
||||
- **THEN** the visitor MUST be taken to the `contact` route
|
||||
- **AND** no lead record MUST be created
|
||||
|
||||
#### Scenario: Empty content does not break the home
|
||||
#### Scenario: Empty catalog sections are omitted
|
||||
|
||||
- **GIVEN** no published services, cases or testimonials
|
||||
- **WHEN** a visitor loads the home
|
||||
- **THEN** the response MUST be 200
|
||||
- **AND** the affected sections MUST be omitted instead of rendering empty containers
|
||||
- **AND** the services, portfolio and testimonials sections MUST be omitted instead of rendering empty containers
|
||||
- **AND** hero, manifesto, method, positioning and final CTA MUST still render
|
||||
|
||||
#### Scenario: Home has no console errors
|
||||
|
||||
@@ -63,12 +66,13 @@ The home page SHALL render, in the order defined by SPEC §6.2, header/navigatio
|
||||
|
||||
### Requirement: Listing and detail pages exist for catalog content
|
||||
|
||||
The system SHALL render a services listing (WEB-02) and a portfolio listing plus case detail (WEB-03). The case detail MUST present summary, event type, optional city/venue/date, challenge, solution, optional result, cover image and the ordered gallery.
|
||||
The system SHALL render a services listing (WEB-02) and a portfolio listing plus case detail (WEB-03) using the Heritage Editorial visual language. The case detail MUST present summary, event type, optional city/venue/date, challenge, solution, optional result, cover image and the ordered gallery.
|
||||
|
||||
#### Scenario: Services listing shows published services
|
||||
|
||||
- **WHEN** a visitor loads `/servicos`
|
||||
- **THEN** every published service MUST be listed with title and summary in `sort_order`
|
||||
- **AND** the listing MUST use the public editorial layout (not an unrelated visual system)
|
||||
|
||||
#### Scenario: Gallery respects stored order
|
||||
|
||||
@@ -83,7 +87,7 @@ The system SHALL render a services listing (WEB-02) and a portfolio listing plus
|
||||
|
||||
### Requirement: Institutional and error pages have brand identity
|
||||
|
||||
The system SHALL provide the Sobre and Política de privacidade pages and branded error pages (WEB-07). The 404 page MUST use the public layout, and the 500 page MUST NOT expose stack traces or internal details when `APP_DEBUG` is false.
|
||||
The system SHALL provide the Sobre and Política de privacidade pages and branded error pages (WEB-07) using the Heritage Editorial public layout, including the brand mark when available. The 404 page MUST use the public layout, and the 500 page MUST NOT expose stack traces or internal details when `APP_DEBUG` is false.
|
||||
|
||||
#### Scenario: Unknown URL renders branded 404
|
||||
|
||||
@@ -100,7 +104,7 @@ The system SHALL provide the Sobre and Política de privacidade pages and brande
|
||||
|
||||
### Requirement: Contact page presents contact data as briefing placeholder
|
||||
|
||||
The `contact` route SHALL render the contact page using `site_settings` (e-mail, phone, city, social links) so the home CTA has a valid destination before the briefing form exists. The page MUST NOT create leads in this change.
|
||||
The `contact` route SHALL render the contact page using `site_settings` (e-mail, phone, city, social links) so the home CTA has a valid destination before the briefing form exists. The page MUST NOT create leads and MUST NOT submit a functional briefing form in this change.
|
||||
|
||||
#### Scenario: Contact page shows configured contact data
|
||||
|
||||
@@ -117,3 +121,28 @@ Public pages SHALL load related content with explicit eager loading through dedi
|
||||
- **WHEN** a case detail page with many gallery images is rendered
|
||||
- **THEN** the gallery MUST be loaded with eager loading
|
||||
- **AND** the query count MUST NOT grow with the number of images
|
||||
|
||||
### Requirement: Public header exposes brand mark and responsive navigation
|
||||
|
||||
The public layout SHALL render the Amare brand mark (faceted-heart logo lockup or configured logo), primary route navigation, and a contact CTA. On narrow viewports the navigation MUST be operable via a disclosure control with accessible name and `aria-expanded` state.
|
||||
|
||||
#### Scenario: Desktop header shows navigation and CTA
|
||||
|
||||
- **WHEN** a visitor loads any public page at a desktop viewport
|
||||
- **THEN** the header MUST include brand mark, links to home/services/portfolio/about/contact, and a contact CTA
|
||||
|
||||
#### Scenario: Mobile menu toggles accessibly
|
||||
|
||||
- **WHEN** a visitor activates the menu button on a narrow viewport
|
||||
- **THEN** the primary navigation MUST become available
|
||||
- **AND** the control MUST expose an updated `aria-expanded` value
|
||||
- **AND** activating a navigation link MUST close the menu
|
||||
|
||||
### Requirement: Demonstrative photography is labeled until authorized assets exist
|
||||
|
||||
When public pages render illustrative/demo photography that is not an authorized Amare asset, the system SHALL mark that imagery as demonstrative in visible copy or accessible labeling so visitors are not misled.
|
||||
|
||||
#### Scenario: Portfolio demo imagery is disclosed
|
||||
|
||||
- **WHEN** the home or portfolio renders placeholder photography
|
||||
- **THEN** a visible note or equivalent disclosure MUST indicate the imagery is illustrative pending authorized assets
|
||||
|
||||
Reference in New Issue
Block a user