04 · Work — 03
A distributor's site, maintained in-house
A corporate site for the distributor of an international simulator brand. It carries four kinds of content — the brand, client stories, news and dealer locations — and the last two keep moving.
- Deploys needed for a content change
- 0
- Kinds of content with their own admin
- 4
Next.js · React · Tailwind CSS · Prisma · Neon · NextAuth · Cloudflare R2 · ISR
What the site has to carry
A corporate site for the distributor of an international simulator brand, in four parts: the brand, client stories, news, and dealer locations. News and dealers keep changing — they are not content that is finished once.
What we did
The public site renders through ISR. Pages are generated ahead of time and read at close to static speed; when one piece of content changes, only that page regenerates, so nothing has to be redeployed.
The admin is a full content system. Brand pages, client stories, news and dealers each have their own create, edit and delete screens, body copy is written in a rich text editor, and images upload straight to Cloudflare R2 rather than onto the web host.
The data layer is Prisma on Neon. The admin is protected by NextAuth, and every API route that writes verifies a JWT.
What it does now
All four kinds of content are maintained in the admin, and an update reaches the public site without a redeploy.