Hover to scroll the page · click to open it full size
The outcome
A US government contracting audience expects specific things on a page — identifiers, NAICS codes, past performance — and reads their absence as disqualifying. Six capability pages carry the operational detail, the capabilities statement is gated behind a request form so every download is a lead, and the contract identifiers sit in view rather than buried in a PDF.
What was built
- Six capability detail pages served from DB with static fallback
- Enquiry form posting to a Resend-backed API with Zod validation
- Contact form prefills capability and inquiry type from the URL
- Admin editing for the six capabilities, full CRUD on operations
- Operations entries carry draft/published status and sort order
- Image upload to blob storage, gated on an admin session
- Keyboard-navigable photo lightbox for past-performance galleries
- Meta Pixel and GA4 injected only when their env IDs are set
- Generated OG image plus Organization and Service JSON-LD