Page archetypes
One canonical composition for each genuinely different page type. Archetypes combine approved foundations, components, and sections without duplicating every production route.
The ownership boundary
The Design System owns reusable visual decisions and representative compositions. The Pierce website owns real routes, content, data, integrations, and conversion behavior.
Canonical page types
Each blueprint defines section order, hierarchy, responsibilities, and responsive composition while remaining free of production data and integrations.
Homepage
Orient, establish trust, route visitors, and create one clear consultation path.
Open blueprint → 02 /estate-planning · /probate · /elder-lawPractice area
Turn a legal concern into an understandable service, outcome, and next step.
Open blueprint → 03 /locations/raleigh-nc · /locations/durham-ncLocation
Establish local relevance without duplicating the entire website for each city.
Open blueprint → 04 /attorneys/jared-pierce · /about/our-teamAttorney profile
Turn credentials into a credible, human reason to begin a conversation.
Open blueprint → 05 /news/estate-planning/example · /authority/exampleArticle
Make complex legal information readable, trustworthy, and connected to help.
Open blueprint → 06 /estate-planning-landing · /how-much-does-an-estate-plan-costCampaign landing
Convert one audience around one offer with minimal competing navigation.
Open blueprint → 07 /contactContact and intake
Collect enough context to route a prospective client without making the first step feel burdensome.
Open blueprint →When a design reaches the website
- 1Prove the reusable decision here.
Update foundations, components, patterns, and the applicable archetype.
- 2Apply it to the real route.
Use the Pierce monorepo workspace to combine the reviewed system with real content and behavior.
- 3Review two explicit changes.
The Design System PR owns the reusable contract. The site PR owns implementation and the pinned submodule commit.