Resolve open questions; update all core specs

specification/00-overview.md

@@ -1,40 +1,55 @@
 # Diana Website — Specification Overview (v1)
 
+## Brand
+**Home Enhancement and Renovation — HER**
+- Short-form: **HER** (used in logo/header)
+- Full name: "Home Enhancement and Renovation" (footers, About, legal)
+
 ## Purpose
 Build a **mobile-first, SEO-friendly, static website** for Diana (handywoman) that primarily **converts visitors into qualified quote requests**.
 
-This document is the navigation map for the specification set.
-
 ## Goals
 1. **Generate qualified leads** via a lightweight quote/contact form.
-2. Communicate Diana’s differentiation: **trustworthy, easy to work with, female handyman/handywoman**, strong **project coordination/mediation** skills.
-3. **SEO-first information architecture**: separate service pages with clear local relevance (San Francisco + 50-mile radius).
+2. Communicate Diana's differentiation: **trustworthy, easy to work with, female handyman/handywoman**, strong **project coordination/mediation** skills.
+3. **SEO-first information architecture**: separate/grouped service pages with clear local relevance (San Francisco + 50-mile radius).
 4. **Fast, mobile-first UX** (Core Web Vitals friendly, readable, tap-target safe).
 
 ## Non-goals / Out of scope (v1)
 - Blog
 - Booking / calendar scheduling
 - Payments
-- Deployment/infrastructure work beyond “static site served behind Caddy reverse proxy”
+- Analytics / tracking (no cookie consent banner required)
+- Deployment/infrastructure work beyond "static site served behind Caddy reverse proxy"
 
 ## Key constraints
 - Language: **English**.
 - Site type: **static website**.
 - Content updates expected to be infrequent (maintained by owner/you).
 - Form should be **lightweight** (no file uploads in v1).
+- Form backend: **existing AWS service** (details TBD — see OQ-3 / ADR-002).
 
 ## Primary user flows
 1. Visitor lands on Home page → scans credibility/services → taps **Request a Quote** → submits form.
-2. Visitor lands on a Service page (SEO) → sees what’s included + service area + CTA → submits form.
+2. Visitor lands on a Service page (SEO) → sees what's included + service area + CTA → submits form.
 3. Visitor checks About / Testimonials for trust → CTA → submits form.
 
-## Intended information architecture (high level)
-- Home
-- Services (hub)
-- Service detail pages (one per service)
-- About Diana
-- Testimonials
-- Contact / Request a Quote
+## Intended information architecture
+| Page | URL slug | Notes |
+|------|----------|-------|
+| Home | `/` | Hero, positioning, services overview, CTA |
+| Services hub | `/services/` | Links to all service pages |
+| Painting | `/services/painting/` | |
+| Tile Setting | `/services/tile-setting/` | |
+| Drywall & Sheetrocking | `/services/drywall/` | |
+| Minor Plumbing | `/services/plumbing/` | |
+| Minor Electrical | `/services/electrical/` | |
+| Carpentry & Mounting | `/services/carpentry-and-mounting/` | |
+| Flooring & Wood Refinishing | `/services/flooring/` | |
+| Security & Safety Equipment | `/services/security-safety/` | |
+| Boat Work | `/services/boat-work/` | |
+| About Diana | `/about/` | Story, experience, credibility |
+| Testimonials | `/testimonials/` | Customer quotes |
+| Contact / Request a Quote | `/contact/` | Form + secondary contact (email, phone) |
 
 ## Specification documents
 ### Core specs (Phase 2)
@@ -47,5 +62,3 @@ This document is the navigation map for the specification set.
 - `33-frontend-spec.md` — pages, components, UX, mobile-first design, conversion flow
 - `37-seo-content-spec.md` — page structure, metadata, schema.org, sitemap/robots, content requirements per page
 - `38-lead-capture-spec.md` — form fields, validation, spam protection, delivery/routing, confirmation UX
-
-(If a themed spec requires an architectural decision, it will be captured in `02-architecture-decisions.md`. If uncertainty remains, it will be captured in `99-open-questions.md`.)