Files
AndreaSlopFotografie/aidlc-docs/features/soorten-fotoshoots-page/aidlc-state.md
T
SluijsensandClaude Opus 5.5 a4149e86af
Continuous Integration / check (pull_request) Successful in 10m46s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 12m15s
Continuous Integration / deploy-production (pull_request) Skipped
Records Build and Test of the Soorten fotoshoots page and completes the feature
Full pnpm check at d12665c passed (325 tests, Lighthouse within budget)
and 19 browser checks against the production build passed. Adds the
build and test instructions and summary, marks the feature complete
and logs the session in the audit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 16:30:33 +01:00

90 lines
7.3 KiB
Markdown

# AI-DLC State Tracking
## Project Information
- **Feature Name**: Soorten fotoshoots page (`/soorten-fotoshoots`)
- **Feature Slug**: soorten-fotoshoots-page
- **Project Type**: Brownfield
- **Start Date**: 2026-10-24T19:30:00Z
- **Current Stage**: Complete (PR #8 to master, auto-merge by the owner)
- **Branch**: feature/soorten-fotoshoots-page (fast-forwarded to master 11a5224 after over-mij-page merged, PR #7)
- **Worktree**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-soorten-fotoshoots
## Workspace State
- **Existing Code**: Yes
- **Programming Languages**: TypeScript (React/TSX)
- **Build System**: pnpm + Vite (`tsc && vite build`), Gitea Actions CI
- **Project Structure**: Single front-end SPA in `web/`; static HTML design reference in `design/andreaslop-static/`; `api/` folder present but empty (.NET back-end planned)
- **Reverse Engineering Needed**: No (artifacts in `_shared/` already include the over-mij shared blocks as of e152153; per team agreement only the lines about this feature's own route/components are updated, no full refresh)
- **Workspace Root**: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-soorten-fotoshoots
## Code Location Rules
- **Application Code**: Workspace root (NEVER in aidlc-docs/) — front-end lives in `web/`
- **Feature Documentation**: aidlc-docs/features/soorten-fotoshoots-page/ only
- **Shared Artifacts**: aidlc-docs/_shared/
- **Structure patterns**: See code-generation.md Critical Rules
## Language Configuration
- **Documentation Language**: English
- **Conversation Language**: User Language (Dutch)
- **Source**: inherited from aidlc-docs/language-preference.md (answer A); user may override
## Parallel Work Agreements
Agreed with the parallel sessions (contact-page, portfolio-page, over-mij-page) on 2026-10-24:
- One worktree per feature; nobody switches branches in a shared checkout
- No full RE refresh; each feature updates only its own lines in `_shared/reverse-engineering/`
- Hot files (`sitePages.ts`, `lighthouserc.cjs`, `active-features.md`): own entry/row only
- `seo.ts`: contact-page owns a generic `webPage(type: WebPageType, path, extra)` helper (separate commit, cherry-picked by the others); this feature builds its JSON-LD on it, no own `xxxPage()`
- `PageIntro` is used by everyone: message the others before changing it
- Claims of this feature: `content/shootTypes.ts`, shared `CallToAction` band, backwards-compatible `reverse` prop on `MediaText`
- contact-page does not touch `Pricing.tsx`; an `id="prijzen"` anchor there is fine with it. Until its `/contact?onderwerp=` format is final, shoot links use `/#contact` (with `?pakket=` where a package exists)
- Each entry in `shootTypes.ts` gets a `slug` plus an optional `packageId` (a `packages.ts` id), so the links work with either option contact-page is still deciding on: `/contact?pakket=<packageId>` (its recommendation) or `/contact?onderwerp=<slug>`
- Photos: this feature owns the shoot photos in `web/src/assets/shoots/`; portfolio-page uses none of them (no overlap) and processes its own 10 photos into `web/src/assets/portfolio/`
- `shootTypes.ts` is also used by portfolio-page (filters per shoot type, lightbox captions). Agreed shape `{ id: ShootTypeId; name; shootLabel; paragraphs; image; packageId? }`, ids `newborn | zwangerschap | gezin | loveshoot | portret` stay stable. Delivered as the **first commit of unit 1** (types + shootTypes.ts + assets/shoots/), hash goes to portfolio-page, which cherry-picks it
- Possible extra (pending both users): portfolio filter in the URL `/portfolio?shoot=<id>`, so shoot blocks could link to "Bekijk meer …foto's". New scope for this page, put it to the user once portfolio-page confirms
- contact-page's final preselect format: `/contact?pakket=<packageId>` (unknown values ignored; shoot types without `packageId` link to plain `/contact`)
- Shared service area (`areaServed`) in `siteContent` and its use in `professionalService`: owned by this feature, in a separate small commit (siteContent + seo.ts + tests). No waiting on each other: different functions in `seo.ts`, so whoever commits first sends the hash and the other rebases on top. contact-page follows the approved wording (send it once the user approves)
- If this feature reaches Code Generation before contact-page's `webPage()` commit exists: ask contact-page first whether this feature should add `webPage()` exactly to the agreed signature (then contact-page rebases on it), rather than writing a page-specific function
- contact-page also changes `content/types.ts` and `siteContent.ts` (its unit 2): `SocialLink.label?`, `SiteContent.contactForm = { enabled, replyTime }`. Different fields from `serviceArea`; whoever commits second resolves the small textual conflict
- Lighthouse (`pnpm check`, preview on port 4173 `--strictPort`): send "claim 4173" to the other sessions before starting and "4173 free" when done; no heavy runs (full vitest with coverage, build) while someone else's Lighthouse runs
- Test environment (one, last deploy wins): "claim test" with the reason before a `deploy_test` dispatch, "test free" after the review; a merge to master also deploys to test, so check for an open test claim before merging and announce the merge
- Claims of others: contact-page — ContactForm generalisation, contact-details block, `/contact?onderwerp=` (pending its user's decision); portfolio-page — PortfolioGrid, Lightbox, InstagramGrid move to shared
- over-mij-page sends the merge commit once merged; all stacked features then rebase onto master
## Extension Configuration
| Extension | Enabled | Decided At |
|---|---|---|
| Security Baseline | Yes | Requirements Analysis |
| Property-Based Testing | Yes (full enforcement) | Requirements Analysis |
## Operations Configuration
- **Include Operations Phase**: No
- **Decided At**: Requirements Analysis
## Stage Progress
### 🔵 INCEPTION PHASE
- [x] Workspace Detection
- [x] Reverse Engineering - SKIP (shared artifacts current; delta lines only)
- [x] Requirements Analysis (approved)
- [x] User Stories - SKIP
- [x] Workflow Planning (approved)
- [x] Application Design - EXECUTE (minimal) — approved
- [x] Units Generation - SKIP
### 🟢 CONSTRUCTION PHASE
- [x] Functional Design - EXECUTE (unit 2 ✅) / SKIP (unit 1)
- [x] NFR Requirements - SKIP
- [x] NFR Design - SKIP
- [x] Infrastructure Design - SKIP
- [x] Code Generation - EXECUTE (per unit): 1 Shared blocks and content ✅ (eb23536 / befe97a / 6cf9095) → 2 Soorten fotoshoots page ✅ (4521539, d2c1d2c)
- [x] Build and Test - EXECUTE (approved)
### 🟡 OPERATIONS PHASE
- [x] Deployment Setup, Monitoring Setup, Production Readiness Validation - SKIP (Operations = No)
## Execution Plan Summary
- **Stages to Execute**: Application Design (minimal), Functional Design (unit 2 only), Code Generation (2 units), Build and Test
- **Stages to Skip**: Reverse Engineering (shared artifacts current), User Stories (single persona, concrete FRs), Units Generation (split fixed in the plan), Functional Design for unit 1, NFR Requirements and NFR Design (set at requirements level), Infrastructure Design (static assets only), Operations (decided No)
- **Units**: 1 Shared blocks and content → 2 Soorten fotoshoots page
- **Delivery**: branch feature/soorten-fotoshoots-page, separate commits for portfolio-page (assets/content) and contact-page (service area), full `pnpm check` per unit, one PR at the end