Files
AndreaSlopFotografie/aidlc-docs/features/portfolio-page/aidlc-state.md
T
SluijsensandClaude Opus 5.5 e013f1436b Shares the Instagram block between pages
Moves InstagramGrid out of the homepage sections and gives it its own
content module, so the portfolio can show the same block. The homepage
renders exactly as before; the tiles keep reusing the intro and review
photos, so each photo keeps one description.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 21:32:48 +01:00

7.4 KiB
Raw Blame History

AI-DLC State Tracking

Project Information

  • Feature Name: Portfolio page (/portfolio)
  • Feature Slug: portfolio-page
  • Project Type: Brownfield
  • Start Date: 2026-10-24T19:30:00Z
  • Current Stage: CONSTRUCTION - Code Generation (Unit 1 Shared Instagram block, generated, awaiting approval)
  • Branch: feature/portfolio-page (fast-forwarded onto master 11a5224 after the over-mij-page merge, PR #7)
  • Worktree: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie-portfolio

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 current with the over-mij blocks; team agreement: no full refresh, each feature updates only its own lines)
  • Workspace Root: K:\Development\SlpSoftware\Projects\AndreaSlopFotografie

Code Location Rules

  • Application Code: Workspace root (NEVER in aidlc-docs/) — front-end lives in web/
  • Feature Documentation: aidlc-docs/features/portfolio-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

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

Execution Plan Summary

  • Stages to Execute: Application Design (standard), Functional Design (units 2 and 3), Code Generation (3 units), Build and Test
  • Stages to Skip: Reverse Engineering (team agreement), User Stories (single persona, concrete FRs), Units Generation (split fixed in the execution plan), Functional Design for unit 1 (behaviour-preserving move), NFR Requirements and NFR Design (NFRs set at requirements level), Infrastructure Design (static assets only), Operations (decided No)
  • Units: 1 Shared Instagram block → 2 Gallery building blocks → 3 Portfolio page (needs the webPage() and shootTypes.ts peer commits)
  • Delivery: branch feature/portfolio-page, commits per unit, full pnpm check (incl. Lighthouse) per unit, one PR at the end

Parallel Work Agreements

Parallel features, each in its own worktree (originally stacked on feature/over-mij-page, merged to master as 11a5224): contact-page (session andreaslopfotografie-91), soorten-fotoshoots-page (session andreaslopfotografie-3f). Over-mij session ("Over mij pagina") notifies when merged.

  • No full RE refresh; each feature only updates the RE lines about its own route/components
  • Hot files: own entry only in sitePages.ts, lighthouserc.cjs, active-features.md
  • Lighthouse / pnpm check (port 4173): send "claim 4173" to the other two sessions before a run and "4173 free" after; avoid CPU-heavy work (full vitest with coverage, build) while another session runs Lighthouse
  • Peer commits to cherry-pick at the start of unit 3:
    • soorten-fotoshoots: eb23536 "Adds the shoot types and their photos" (content/types.ts ShootTypeId/FrameColor/ShootType, content/shootTypes.ts + test, assets/shoots/.jpg 960×1200, theme.ts frame. tokens, test/arbitraries.ts shootTypeId/shootType/uniqueShootTypes). Run pnpm typegen afterwards (theme change). Their Gezin photo is F41A7138 (also portfolio photo 9; overlap accepted by their user; different derivatives)
    • contact-page: webPage() — hash pending
  • seo.ts: contact-page builds generic webPage(type, path, extra) (aboutPage refactored onto it) in a separate commit; portfolio cherry-picks it and uses it for ImageGallery/CollectionPage JSON-LD. No own xxxPage() helper. Proposed signature: webPage(type: WebPageType, path: RoutePath, extra: Record<string, unknown> = {}) with WebPageType = 'WebPage' | 'AboutPage' | 'ContactPage' | 'ImageGallery' | 'CollectionPage' (add a type to the union in an own one-line commit if needed) → { @context, @type: type, @id + url: canonicalUrl(path), name/description from sitePages[path], inLanguage: 'nl-NL', ...extra } (extra last). Commit hash follows once contact's user approves; design against this signature until then
  • Claims: portfolio — PortfolioGrid, Lightbox, InstagramGrid moved from components/home/ to shared; contact — ContactForm generalisation, contact-details block; soorten-fotoshoots — content/shootTypes.ts, CallToAction band, optional MediaText reverse prop
  • PageIntro is used by all; announce before changing it
  • Photos: soorten-fotoshoots owns the shoot photos (newborn, zwangerschap, loveshoot, portret, gezin) in web/src/assets/shoots/, delivered as an assets-only commit; portfolio cherry-picks it if the user picks any of them. Portfolio-only photos go in web/src/assets/portfolio/. Photos already in web/src/assets/home/ (intro-2, intro-4) are imported from there. Send the final photo list to soorten-fotoshoots after Requirements Analysis. Update: user chose the 10 live photos (Q1 A), no overlap with the shoot photos; list sent
  • Shoot types: portfolio reuses soorten-fotoshoots' list for filters and captions. Proposed shape in content/types.ts: ShootTypeId = 'newborn' | 'zwangerschap' | 'gezin' | 'loveshoot' | 'portret'; ShootType { id; name ('Newborn', …, 'Portretten'); shootLabel ('Newbornshoot', …, 'Portretshoot'); paragraphs; image; packageId? }; order newborn, zwangerschap, gezin, loveshoot, portret. Delivered as a separate commit (types + shootTypes.ts + assets/shoots/) at the start of their unit 1; hash follows. Portfolio photo data references ShootTypeId only. ?shoot=<id> link from their page: confirmed by their user; shown only once /portfolio is indexed: true (no message needed at merge). Portfolio route: validateSearch returns typed { shoot?: ShootTypeId } so their search: { shoot } type-checks. Types without portfolio photos fall back to "Alles"; portfolio exports a pure helper (working name shootTypesWithPhotos) in unit 3 and sends its name. ShootType gains photosLabel and frameColor (theirs, additive). RichParagraph moves to components/ (theirs)

Stage Progress

🔵 INCEPTION PHASE

  • Workspace Detection
  • Reverse Engineering - SKIP (artifacts current; team agreement)
  • Requirements Analysis (approved)
  • User Stories - SKIP
  • Workflow Planning (approved)
  • Application Design - EXECUTE (approved)
  • Units Generation - SKIP

🟢 CONSTRUCTION PHASE

  • Functional Design - EXECUTE (units 2 and 3) / SKIP (unit 1)
  • NFR Requirements - SKIP
  • NFR Design - SKIP
  • Infrastructure Design - SKIP
  • [~] Code Generation - EXECUTE (per unit) — Unit 1 Shared Instagram block: generated, awaiting approval
  • Build and Test - EXECUTE

🟡 OPERATIONS PHASE

  • Deployment Setup, Monitoring Setup, Production Readiness Validation - SKIP (Operations = No)

Current Status

  • Lifecycle Phase: CONSTRUCTION
  • Current Stage: Code Generation — Unit 1 Shared Instagram block (awaiting approval)
  • Next Stage: Functional Design — Unit 2 Gallery building blocks