· 09 min read
Immersive Website Witha CMS Your Team CanEditWant an immersive, interactive 3D website AND a CMS your team runs on Monday? It's one build, not two. How an award-winning developer ships the wow without the black box.
You want an immersive website — the kind that makes a visitor feel your product before they read a word — but you have one fear that keeps the project stuck: what happens after launch? If the site is a sealed box only the agency can open, every price change, new menu, or seasonal campaign becomes a support ticket and an invoice. The good news is that the trade-off you're bracing for isn't real. An immersive website with a CMS your team can edit is one build, not two competing briefs. This is how I architect the wow and the backend together — so the experience ships, and your team runs it on Monday.
Who's writing — and why I can say this
I'm Hon Tran, a creative developer with 11+ years building award-winning, performance-first web experiences for founders, studios and agencies across Norway, Denmark, Sweden, Malta and Vietnam. I've been twice nominated for Awwwards "Independent of the Year" and I sit on the Awwwards jury (2026) — 19 international awards across Awwwards Site of the Day, The FWA, and CSS Design Awards.
That matters here for one reason: I don't just build the front-end spectacle and disappear. I own the backend too. Every award-level site I ship runs on a content system a non-technical team can operate without me — because a site nobody can update is a liability, not an asset.
The fear has a name: the black box
Founders commissioning their first immersive site almost always describe the same worry in different words:
- "It'll look incredible, but will I be able to change the hero copy myself?"
- "If I want to swap a product, add a dish, or run a sale — do I have to pay the agency every time?"
- "My marketing lead needs to own this. Will they be locked out?"
This is a legitimate fear, and it comes from real experience. A lot of "immersive" work is a black box: the animation, the 3D, and the copy are all baked into code, so the only way to change a price is to redeploy the site. The studio quoted the experience and treated the backend as an afterthought — or skipped it entirely.
The mistake is thinking you must choose: either a jaw-dropping custom experience or a site your team can actually run. You don't. Those live in two different layers of the same build.
Why it's one architecture, not two briefs
An immersive site has two layers, and keeping them separate is the whole trick:
- Content — the words, prices, images, menu items, case studies, SEO fields. This belongs in a CMS. It changes often, it's owned by your team, and it should never require a developer.
- Motion — the WebGL scenes, GSAP timelines, scroll choreography, shaders. This is code. It changes rarely, it's owned by me, and it should never require your team to touch it.
The motion layer reads from the content layer. Your hero animation doesn't hard-code the headline — it renders whatever headline the CMS currently holds. Your 3D product reveal doesn't bake in "$48" — it displays the price field your team edits. Change the content; the experience re-renders around it. Nothing breaks, because the animation was built to consume content, not to contain it.
That's the resolution to the fear: the spectacle and the editable backend aren't a trade-off because they aren't the same thing. One is code I write once; the other is data your team owns forever. Decoupling them is a day-one architecture decision — so I make it on day one, every time. I go deeper on this split in my guide to fullstack creative development.
ts
const hero = {
headline: { type: 'text' },
subhead: { type: 'richtext' },
backgroundScene: { type: 'select', options: ['jungle', 'ocean', 'studio'] },
menu: {
type: 'array',
of: { name: 'text', price: 'text', image: 'image' },
},
};
That's a simplified CMS field schema. Your team edits those values in a form. The WebGL hero and the
GSAP reveal are separate code that reads them at render time — so marketing can change the headline,
swap the jungle scene for ocean, or add a menu item with a new price, and the immersive front-end
simply reflects it. No deploy, no developer, no ticket.
Thinking about an immersive build but worried about the handoff? Tell me about your project — I'll show you exactly which parts your team will own.
What your team edits on Monday vs. what stays code
Here's the honest division of labour on a build I ship. This is the table I walk every founder through before we start, so expectations are set:
| Your team edits (in the CMS) | Stays in code (I own / maintain) |
|---|---|
| Headlines, body copy, CTAs | GSAP scroll timelines & choreography |
| Prices, menu items, product details | WebGL / Three.js scenes & shaders |
| Images, videos, galleries | Page transitions & smooth-scroll engine |
| Case studies, blog posts, team bios | Performance budget & mobile fallbacks |
| SEO titles & meta descriptions | The design system & component library |
| Which background scene a section uses | How that scene renders and animates |
The left column is 95% of what you'll actually want to change after launch — and it's all yours, self-serve. The right column is the craft you hired me for, and it almost never needs touching once it's tuned. If a campaign does need new motion, that's a scoped piece of work, not a permanent dependency.
Which CMS? That depends on what your team already knows. If your marketing lead lives in WordPress, I build the immersive front-end on headless WordPress so they keep the editor they're comfortable with. If you want a cleaner, developer-friendly backend, Sanity or Strapi. I break down the trade-offs in my headless CMS comparison — but the point is you don't adapt your team to the tech; the tech adapts to your team.
Proof: award-winning immersive sites that run on a CMS a team knows
This isn't theory. My recent flagship work is exactly this pattern — the "wow" and the editable backend, shipped together:
- Iventions — an immersive events site I built with SERIOUS.BUSINESS (designer Huy Phan). Stack: Next.js + headless WordPress + Three.js + GSAP. It won Awwwards Site of the Day & Developer award and CSS Design Awards Website of the Month (Oct 2025), and was a finalist for Website of the Year. The Three.js and GSAP carry the experience; WordPress means a non-technical team edits the content in an editor they already understand. Award-level motion, ordinary editing — same build.
- Mat Voyce (
matvoyce.tv) — a flagship motion portfolio, nominated for GSAP Site of the Year. Stack: Next.js + Strapi + GSAP. The heavy creative motion lives in code; the content lives in Strapi, a self-hosted CMS the owner controls.
In both cases the immersive layer and the content layer are decoupled. The award didn't come at the cost of a maintainable backend — it came with one.
What a clean handoff actually includes
"My team can run it" is only true if the handoff is real. When I ship an immersive site, the backend handoff includes:
- A CMS with your real content already in it — not an empty shell, but your live copy, prices and media, structured into clear fields.
- Named roles — your marketing lead, your editor, your founder each get access scoped to what they need.
- A short walkthrough — a recorded session plus a one-page guide showing how to change the things you'll actually change (hero, menu, images, SEO). No dev vocabulary.
- Guardrails — fields are typed and constrained, so an edit can't accidentally break the layout or the animation. Your team changes content inside safe boundaries; the experience holds.
That's the difference between "here are the keys" and "here's a locked building." You're searching for a developer who collaborates with your internal team, not one who hands you a black box and an invoice for every change.
FAQ
Can my team edit a 3D or immersive website without a developer?
Yes — the content on it, which is what you'll actually want to change. In a properly architected build, every word, price, image and menu item lives in a CMS your team edits through a form. The 3D scenes and animations are code that reads that content, so updating a headline or swapping a product never requires touching the WebGL. The only thing that needs a developer is genuinely new motion or a new section type.
Will the animations break when we change the content?
No, if it's built correctly. The animations are written to consume content, not to contain it — and the CMS fields are typed and constrained so an edit stays within safe limits. You can change the hero headline from three words to eight, swap an image, or add a menu item, and the motion re-renders around the new content. (A site where changing a price breaks the layout wasn't decoupled properly — that's the black box you're right to avoid.)
Isn't a custom immersive site harder to maintain than a template?
The motion is custom; the maintenance doesn't have to be. Day-to-day content updates on a well-built immersive site are exactly as easy as on a template — same CMS forms, same self-serve editing — because the content layer is standard. What's different is the front-end, which is code I maintain, not something your team babysits. You get template-easy editing with award-level design.
Can you build on the CMS my team already uses?
Usually, yes. If your team already runs WordPress, I build a headless WordPress backend so they keep their editor. If you're starting fresh, I'll recommend Sanity or Strapi based on your team's comfort and your content structure. The immersive front-end is CMS-agnostic — I pick the backend that fits your people, not the other way around.
Do I have to choose between "immersive" and "my team can run it"?
No. That's the entire point: they're two layers of one build, not two competing options. Every immersive site I ship is architected so the experience and the editable backend arrive together. See how I approach immersive website development end to end, or a real example in my immersive restaurant & hospitality build.
Let's build the wow — and the backend
You don't have to trade the experience for control, or control for the experience. An immersive, interactive site and a CMS your team runs on Monday are the same project, built by someone who owns both layers. Browse the live work in my projects archive, then tell me about your immersive project — I'll map out exactly which parts your team will own before we write a line of code.
External references: the Next.js App Router data-fetching docs and the Sanity content modelling guide describe the same content/code separation this approach relies on.
04 — Engineering note
For agencies, studios and brands
Need this levelof execution?
05 — Related notes
Same tags · same craft
Continue the thread.
- 01Deep-Tech Website Design for a Funded StartupStudio note / 085 · 22 Jul 26Deep-tech website design for a funded startup — one creative developer to take a robotics or AI rebuild from design through code, and hand you full ownership of the codebase.9 min
- 02Why Your WebGL Hero Disappears on Browser BackEngineering note / 068 · 11 Jul 26Your Next.js WebGL background is fine on first load and Link nav, then blank after the browser Back button? Here's the popstate root cause and the R3F rebuild fix.10 min
- 03Product Launch Microsite: Budget & Timeline (2026)Studio note / 080 · 10 Jul 26What a WebGL product launch microsite costs and how long it takes — real 2026 budget ranges, a week-by-week timeline, and a build that survives launch day.14 min