Case study · Website
A website that
keeps up with
a growing brand
I designed the Mynzo website end to end. When Figma Sites stopped keeping pace with how the brand worked, I rebuilt it in code with Claude, so the site now moves as fast as the brand grows.
- My role
- Designer and site ownerDesign, visuals, build direction and hosting
- Platform
- WebsiteDesktop, tablet and mobile
- Built with
- Code, GitHub and VercelMedia on AWS
- Focus
- Easy to keep currentFor a growing brand
Designer and site owner
I designed and produced the entire website: layout, visuals, motion and content structure. Claude wrote the code from my instructions. I also ran the site day to day, and I decided when to migrate it.
What I owned
- The design of every page, across desktop, tablet and mobile
- The visuals and motion, including the AI-generated hero video and visuals
- Day-to-day content updates
- The decision to migrate
- The specification and review of the new build, admin panel and form
- Hosting, code storage and media storage
How the new site was built
- I wrote the specification
- Claude generated the code
- I reviewed each result and requested revisions
Five parts, each with one job
The new site is code rather than a design file. Each part lives in its own place.
A growing brand changes its site every day
Mynzo is a growing brand, so parts of the website needed editing daily. The site was built in Figma Sites, with its CMS holding the blog. After a third-party marketing team joined, the site also had to support their work.
Problem statement
Figma Sites could not keep up with the pace of change, or support the marketing team's need for access.
Goal. Keep the site current with minimal effort per update, and give the marketing team direct access to work on it.
Four limits, from running the site
- Blog ordering
The newest post did not appear first
The CMS always showed the first uploaded post at the top.
- Maintenance
Every change was repeated across views
An edit made in the desktop view had to be redone for tablet and mobile. The views adapt automatically, but image placement and text size still needed manual adjustment.
- Access
No route for the marketing team
The third-party marketing team needed the site's code to customise it and run ads. The Figma file is a design tool they do not work in, so every change depended on me.
- Search visibility · Risk
No sitemap
As far as I know, Figma Sites did not provide a sitemap, which helps search engines index every page. No customer or teammate reported difficulty finding the site, so the impact is unconfirmed.
Continue on Figma Sites, or rebuild in code
Blog ordering, repeated edits and the marketing team's access all pointed to the same limit: the tool no longer fit how the site was run. The options were to continue on Figma Sites or to rebuild the site in code.
Continue on Figma Sites
- Site already designed and live
- Blog order unchanged
- Edits repeated across desktop, tablet and mobile
- No code access for the marketing team
- No sitemap
Rebuild in code
- Full control of blog order
- Updates made in a custom admin panel
- Code on GitHub, open to the marketing team
- Search setup, including a sitemap, under my control
- Hosting, code and media become my responsibility
- Code written with Claude and reviewed by me
Decision
Rebuild the website in code with Claude, hosted on Vercel, with the code on GitHub, images and videos on AWS, and a custom admin panel.
Five requirements, drawn from the problems
| The site had to | Because |
|---|---|
| Show the newest blog post first | Figma Sites placed the first uploaded post at the top. |
| Allow quick updates | Content changes daily. |
| Adapt across screens with minimal rework | Each desktop change needed tablet and mobile adjustments. |
| Be open to the marketing team | They needed code access to customise the site and run ads. |
| Be discoverable in search | Figma Sites had no sitemap, as far as I know. |
I wrote the specification, Claude generated the code
I rebuilt the whole site this way. My role was to define what the site should do and to verify that it did.
- Step 1
Brief
I specified each page, section and behaviour.
- Step 2
Build
Claude generated the code from the specification.
- Step 3
Review
I checked each result and requested revisions.
- Step 4
Publish
Hosted on Vercel, with code on GitHub and media on AWS.
Four parts worth a closer look
The whole website is my design. The hero video, the card visuals and the process video were generated in OpenArt: images first, with several models, then videos from them. Reni is my concept.
The opening of the site
A 30-second loop that opens the home page. It sets up the idea behind the heading, Precision Forest Monitoring: carbon and biodiversity, measured from space and on the ground.
Five cards, one per topic
Each card explains one part of how forests are monitored.





A video that follows the four steps
- Satellite-based forest mapping and land cover analysis
- Ground-truth ecological and biodiversity sampling
- AI-driven monitoring and recalibration
- Evidence for independent review
A 13-second video runs beside the steps, and each step is highlighted as the video reaches it.
An interactive demo of a custom AI assistant
Reni is my idea: a nature asset analyst that shows visitors how a custom AI works on a client's own data, so they can ask for more detail about it. Pick a question below to try it.
A working copy of the demo, with the questions and answers from the live site. Responses and portfolio figures are illustrative.
Interactive demo. Responses and portfolio figures are illustrative.
Reni v2.4 online — nature asset intelligence active.
What is survivability across my sites?
Scanning 3 active sites… Avg survivability: 87.4%. ⚠ Site B (mangroves) at 74% — recommend ground validation sweep in Q2.
The website, as it runs today
This is the live site, embedded at desktop width. Scroll inside the frame to move through it.
Is the site easier to keep current?
The goal is a site that is quick to update and always correct. These are the measures I would track against how the Figma Sites version behaved.
| Measure | What it tells us |
|---|---|
| Time to publish an update | Minutes from making a change to seeing it live, against editing three sections by hand. |
| Blog order | Whether the newest post appears first after every publish. |
| Layout on phones, tablets and desktops | How many tweaks each change needs, against the tweaks Figma Sites needed. |
| Marketing team requests | Changes still routed through me, against changes the team can now make directly. |
| Page speed | Load time on phone and desktop, since the site carries images and videos. |
| Search visibility | Which pages Google finds, and how many visits come from search. Google Analytics shows this. |
What I would carry into the next project
No significant issues
The admin panel, CMS and form work as intended. Form entries reach the company email, and no specific changes have been needed.
Migrated when the tool stopped fitting
I kept the site live while rebuilding it, and migrated once blog ordering, repeated edits and access constraints made the old setup too costly to maintain.
Document the update process
I would write down how to publish a change, so anyone on the team can update the site, not only me.