The ten live photos in a filterable masonry grid with an accessible lightbox, filters per shoot type kept in the URL (?shoot=), the shared Instagram block, and an indexed page with image gallery structured data and its own preview image. Soorten fotoshoots now only links to the portfolio for shoot types that have photos there. The filter bar stays on one row, so the web font loading no longer shifts the photos below it, and no photo loads before the page has: the grid fades in, so loading its photos early only delayed the fonts and the intro text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Functional Design Plan — Unit 3: Portfolio page
Depth: standard. Scope from the execution plan: the photo data (shoot type and alt text per photo, approved by the user — clarification 4), the preview image, the ?shoot= rules, the filter/caption mapping onto the unit 2 blocks, the ImageGallery structured data, the follow-up for the Soorten fotoshoots links, and the testable properties of the new helpers (PBT-01). Questions: portfolio-page-fd-questions.md.
- Collect and analyse the answers in
portfolio-page-fd-questions.md domain-entities.md—PortfolioPhoto,PortfolioContent, the 10 photos with shoot type, alt text, sizes; relation toShootType,GalleryItem,ImageObjectbusiness-rules.md— photo and image rules (sizes, order), filter rules (options,?shoot=parsing and fallback, canonical), caption, lightbox scope, SEO (indexed, title/description unchanged,ogImage,ImageGallery), Soorten links rule, LAYOUT.mdbusiness-logic-model.md— route → gallery → grid/lightbox flow; pure helpers and their properties (PBT-01)frontend-components.md—PortfolioGalleryand the route: hierarchy, props, state, accessibility, test ids- Validate against requirements.md, application-design.md, unit 2 design and the extension rules