Darminsky Website — Hybrid Foundry-Sync Content Model
The public Darminsky website built with Next.js 14 and a hybrid content model: static JSON for app data, Foundry-backed venture data synced at build time with a public curation overlay.
Challenge
A studio-and-ventures website needs to stay current without becoming a content management burden. Ventures and projects evolve fast; managing them manually across two systems is error-prone and slow. At the same time, not every internal project or planning item belongs in public view.
Approach
Built on Next.js 14 App Router and TypeScript with Tailwind CSS. The venture/project content layer uses a hybrid model: a build-time sync script pulls project data from Project Foundry into a generated JSON cache, while a checked-in overlay file controls what is shown publicly (with options to hide, reorder, or override fields). App content (Dossier, etc.) stays as direct JSON files. This keeps the public site in sync with planning without exposing internal details.
Outcome
The website is live at darminsky.ca and deployed to Azure Container Apps. The content model handles Foundry-backed data, checked-in overrides, and static app files consistently. Adding or updating a public venture requires only a rebuild — no manual site edits needed.