Problem
The existing sourcing website needs to become a focused digital-services platform without an unsafe one-time rewrite.
Requirements
- Keep the existing sourcing pages available during the digital-services rebuild.
- Separate reusable templates from project work and case studies.
- Carry the chosen template or project into a structured quote request.
Solution
A phased Next.js rebuild with shared design foundations, reusable service content, a scalable template catalog and structured quote intake.
Architecture
Pages
Next.js App Router pages render the service, template and work content through the project's Vinext runtime.
Project content
Typed project records are read through a repository interface and passed to shared cards and case study pages.
Quote intake
The quote page resolves the selected project by slug. The quote form uses shared Zod validation. When configured, a protected server endpoint validates the request again and saves a private lead in Supabase; otherwise the form remains a local preview.
Main Features
- Reusable page sections
- Dynamic template catalog
- Validated quote form
- SEO and metadata foundations
Technology Stack
- Next.js
- TypeScript
- Tailwind CSS
- Supabase-ready
Challenges
- Keeping templates and actual project work distinct while sharing the site's visual foundation.
- Describing the state of internal and concept projects without presenting plans as delivered client work.
Testing
Not documented
- A dated project testing report has not been published. This case study does not claim completed user acceptance, accessibility or production integration testing.
Screenshots
Demo
Result
The current implementation includes separate template and work catalogs, reusable project cards and project-aware quote intake. No measured commercial outcomes have been published.
What I Learned
The project author's retrospective has not been published yet.
Build Something Similar
Tell us what you need. We’ll use this project as a starting point for discussing your scope.
Build Something Similar