feat: reestruturar jornada pública de casamentos

This commit is contained in:
2026-08-11 15:42:43 -03:00
parent 70cc65227a
commit 68632c32df
61 changed files with 1006 additions and 78 deletions

View File

@@ -0,0 +1,38 @@
## ADDED Requirements
### Requirement: Home presents the weddings and corporate editorial journey
The home SHALL expose anchored chapters for presentation, Amare, service directions, weddings, Corporate, portfolio/acervo, testimonials and final contact paths. It MUST retain the photographic hero, tonal fields, fine rules, EB Garamond and progressive/reduced-motion behavior. Corporate SHALL present only institutional copy and a briefing CTA until authorized copy and proof exist.
#### Scenario: Canonical anchor journey is reachable
- **WHEN** a visitor loads the home or follows a `/#chapter` link from another public page
- **THEN** the relevant chapter exists with a stable id and is reachable without JavaScript
#### Scenario: Corporate does not imply unauthorized proof
- **WHEN** a visitor loads the Corporate chapter before client proof is published
- **THEN** no Corporate service list, image, metric or case is rendered
### Requirement: Production portfolio remains truthful when no cases are published
The public portfolio chapter SHALL render a visible acervo-em-preparação note when no real published cases are available. Production seeders MUST NOT publish development fixture cases.
#### Scenario: Empty production acervo is explicit
- **GIVEN** production has no published portfolio cases
- **WHEN** a visitor loads the home
- **THEN** the portfolio chapter displays the acervo preparation note and no case card
## MODIFIED Requirements
### Requirement: Contact page presents contact data as briefing placeholder
The `contact` route SHALL render the partner and supplier inquiry page using `site_settings` contact data. The detailed event proposal form SHALL be served by the `briefing` route at `/briefing`; public proposal CTAs MUST target that route. Neither public form MUST create a Lead in the launch scope.
#### Scenario: Contact page shows partner journey
- **WHEN** a visitor loads `/contato`
- **THEN** partner-specific copy, fields and privacy notice MUST be displayed
- **AND** the detailed event briefing MUST NOT be rendered
#### Scenario: Briefing route remains reachable for prospects
- **WHEN** a visitor loads `/briefing`
- **THEN** the detailed event proposal form MUST be displayed
- **AND** no Lead record MUST be created