TransHover

THE TASK

A new product that needs explaining requires a presence that does three things at once: show the brand, make the product understandable and sell it directly. And all of that for exactly one product. Off-the-shelf shop systems are a poor fit here: too much platform overhead, running costs and template constraints for a single-product sale that must be legally sound (German button rule, GDPR).

APPROACH

A fully custom-built shop, tailored precisely to this one product: a static Astro site with targeted server endpoints. Fast, SEO-clean product pages, configuration and checkout without detours, and server-side price calculation where the amount shown is guaranteed to be the amount charged. Payments via Mollie, transactional order e-mails, content editing without a developer through a Git-based CMS.

CHALLENGES

• → Displayed === charged: every price component from one shared source for client and server (§ 312j BGB)
• → Bot defence without friction for real customers: honeypot plus rate limiting, IP addresses only as hashes
• → Content Security Policy with script hashes instead of blanket allowances
• → GDPR without a consent banner: no trackers, personal data only where needed and documented

RESULT

Live at transhover.com: a purchasable shop in German and English, without a cookie banner, with hardened security headers and a documented data flow, from first sketch to go-live from a single source.

TECHNICAL EXECUTION

• → Astro + TypeScript, statically generated with API endpoints on Netlify
• → Mollie payment integration: webhook with API re-fetch and idempotency claim
• → One Zod schema for client AND server validation, locale-aware error messages
• → Rate limiting and order store via Netlify Blobs, IPs only as SHA-256 hashes
• → CSP with script hashes, self-hosted fonts, transactional e-mails via Resend

SKILLS IN THIS PROJECT