Shows the three live packages as cards with their price and what is included. Each card links to the contact section with ?pakket=<id>, so the contact form can preselect it. Invalid packages from the CMS are skipped and the pakket value is only accepted when it names a package. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Functional Design Plan — Unit 3: Prijzen
Scope: FR-HP-04 (cards, link with package), the package data that unit 5 reuses, and the pakket search parameter on /. Questions: prijzen-fd-questions.md.
- 1. Collect and analyze answers (follow-up questions if needed)
- 2.
domain-entities.md—PricingPackage, its invariants (unique id slug, positive whole-euro price, non-empty features) and its relation to the contact form's shoot options - 3.
business-rules.md— price formatting,pakketsearch parameter (accepted values, unknown/invalid values, multiple values, case), link targets, what happens on a second "Boek je shoot" click, VAT note, accessible link names; decision flowchart - 4.
business-logic-model.md— flow from "Boek je shoot" via the URL to the preselected form value (unit 5 consumes it), and the pure functionsformatPriceandpackageFromSearch - 5.
frontend-components.md—Pricing,PriceCard, decorations; props, states (hover, focus, reduced motion), responsive layout, accessibility - 6. PBT-01 property identification for
formatPriceandpackageFromSearch(invariants, oracle, idempotency where relevant) - 7. Validate against FR-HP-04, NFR-HP-01/02/03/06 and the Security/PBT extensions