

Overview
UX investigation
- The search is local and specific. Nobody searches "renovation". They search for a product and a place — screens, roller shutters, a veranda, fly screens — which means one page per service, each able to rank on its own, beats a single services page with anchors.
- Trust is visual and immediate. A homeowner comparing installers is looking for evidence of finish quality. Photographs of completed work do more than any amount of copy, so the portfolio is a primary page rather than a footnote.
- The phone number is the conversion. Many customers will not fill in a form at all; they will call. So the number sits in the header on every page, permanently, tappable.
- The two requests are different. "I have a question" and "I want a price for this specific job" need different fields. Forcing both through one form loses the second, which is the valuable one.
UI direction
- Photography carries the page. A full-bleed hero of real installed work, shot on site, with the copy laid over it. The product is the craftsmanship, so the imagery is the argument.
- A warm, industrial palette: charcoal and a single construction orange for action. Restrained enough to read as professional, warm enough not to feel corporate.
- Plain, confident Dutch. Ramen & deuren op maat. No slogans, no filler. A trade customer wants to know what you do and where you do it, in the first sentence.
- Mobile-first, because the traffic is. Large tap targets, a header that keeps the phone number reachable, and forms that are short enough to finish standing up.
Key features
- Nine service pages — windows, doors, curtain walls, verandas, screens, roller shutters, sealant work and fly screens — each a real page with its own metadata and structured data, not a tab.
- Filterable portfolio: completed projects filtered by category, each with a photograph and a short description of the work.
- A two-mode contact page: a general enquiry tab and a full quote-request tab that captures the service, the location and the details an installer needs to price a job without a second phone call.
- Contact details as content: address, phone, email and opening hours laid out where a customer looks for them, not hidden behind a form.
- A self-service backend: submissions land in a database the client can read, alongside the portfolio projects and testimonials, so the site's content is theirs to change.
Architecture
Technologies used
- Frontend: React with Vite, React Router, Tailwind CSS, Radix UI primitives with class-variance-authority, Framer Motion for restrained transitions, Lucide icons.
- SEO: react-helmet for per-route metadata, a custom server-render and prerender pipeline, JSON-LD structured data, and a generated machine-readable site summary.
- Backend: PocketBase, self-hosted, with versioned collection migrations and rate limits configured.
- Images: Sharp for build-time image processing.
- Hosting: Netlify, with explicit cache headers and redirect rules.
