Files
amare/openspec/changes/remodel-about-page/specs/public-site-pages/spec.md
manoel freitas fc1c6177d6
All checks were successful
CI / static (push) Successful in 2m21s
CI / unit (push) Successful in 3m17s
CI / feature (push) Successful in 2m29s
CI / container (push) Successful in 18s
CI / browser (push) Successful in 3m8s
feat: remodelar /sobre conforme mock editorial
Co-authored-by: manoel freitas <manoel.josefneto@gmail.com>
Co-committed-by: manoel freitas <manoel.josefneto@gmail.com>
2026-08-12 20:34:13 +00:00

2.1 KiB

ADDED Requirements

Requirement: About page follows approved editorial composition

The /sobre route SHALL render the Heritage Editorial public layout with this section order: split hero (eyebrow “Sobre nós”, title “Sobre a Amare”, lead from about_summary or editorial default, CTA to #michele), three pillars, founder block #michele (Michele), process (“Como trabalhamos”), featured portfolio masonry (up to six published featured cases), and a final proposal CTA. The page MUST use shared motion markers (data-motion="page-open", data-reveal*) without route transitions. Principles list MUST NOT appear on /sobre (home may still show them). Contact, privacy and error surfaces remain unchanged by this requirement.

Scenario: Visitor sees the mock section order

  • WHEN a visitor loads /sobre
  • THEN the response MUST include the headings for Sobre a Amare, the three pillars, Conheça Michele, Como trabalhamos, Portfólio em destaque, and the proposal CTA copy
  • AND MUST NOT render the numbered principles list formerly used on About

Scenario: Founder photo comes from CMS when configured

  • GIVEN site_settings.founder_image_path is set with alt text
  • WHEN a visitor loads /sobre
  • THEN the Michele section MUST render that image with the configured alt
  • AND MUST use eager loading only for the about hero image, not invent a founder asset path when unset

Scenario: About hero uses about_image with tonal fallback

  • WHEN about_image_path is configured
  • THEN /sobre MUST render a split editorial hero with that media (loading="eager" and fetchpriority="high")
  • WHEN about_image_path is empty
  • THEN /sobre MUST render a tonal hero fallback without an empty image request
  • GIVEN published featured portfolio cases exist
  • WHEN a visitor loads /sobre
  • THEN the masonry MUST link to those cases (or the portfolio index)
  • AND MUST NOT invent decorative photography when no cases exist (tonal slots allowed)