Records unit 1 of the Soorten fotoshoots page as generated
Adds the feature's inception documents (requirements, execution plan, application design), the code generation plan and summary of unit 1, its state and audit log, and its row in the active features list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,17 @@
|
||||
# Services — Soorten fotoshoots Page
|
||||
|
||||
The SPA has no service layer. Orchestration happens in the route, the same pattern as the homepage and Over mij.
|
||||
|
||||
## Route `routes/soorten-fotoshoots.tsx`
|
||||
|
||||
- **`head()`**: `pageHead('/soorten-fotoshoots')` (title, description, canonical, `og:image`, no `noindex` once indexed) plus one `application/ld+json` script: `structuredDataScript(webPage('WebPage', '/soorten-fotoshoots', { mainEntity: shootServices(shootTypes, siteContent) }))`.
|
||||
- **`component`**: composes, in page order:
|
||||
1. `PageIntro` with the page head texts (eyebrow, h1, intro).
|
||||
2. `ShootList` with `shootTypes` and `portfolioLive = isPortfolioLive(sitePages)`.
|
||||
3. `CallToAction` with the closing title, the lead as `RichParagraph` (link "de pakketten" → `/#prijzen`) and a `LinkButton variant="accent"` "Boek je shoot" → `/#contact`.
|
||||
|
||||
## Data flow
|
||||
Static content modules (later the CMS API) → route → components via props. Components never import content directly, so tests can pass any content and the API can replace the modules 1-to-1.
|
||||
|
||||
## External dependency
|
||||
`webPage()` comes from contact-page (separate commit). If unit 2 starts before that commit exists, this feature asks contact-page whether to add it to the agreed signature itself (see aidlc-state.md § Parallel Work Agreements).
|
||||
Reference in New Issue
Block a user