MMehak Maini Mynzo Website

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.

mynzocarbon.comOpen the live site
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
My role

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
How it is set up

Five parts, each with one job

The new site is code rather than a design file. Each part lives in its own place.

CodeGitHubHolds the code, and the history of every change
HostingVercelHosts the live website
MediaAWSStores the images and videos
ContentAdmin panelA custom CMS, built with Claude, for the blog and site content
EnquiriesFormEntries are delivered to a company email, set up by a colleague
01Understand the problem
The problem

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.

Where it fell short

Four limits, from running the site

02Make the decision
The choice

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.

Stay

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
Move

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.

What the new site had to do

Five requirements, drawn from the problems

The site had toBecause
Show the newest blog post firstFigma Sites placed the first uploaded post at the top.
Allow quick updatesContent changes daily.
Adapt across screens with minimal reworkEach desktop change needed tablet and mobile adjustments.
Be open to the marketing teamThey needed code access to customise the site and run ads.
Be discoverable in searchFigma Sites had no sitemap, as far as I know.
03Build the site
How it was built

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.

Highlights from the site

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.

01 · Hero video

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.

02 · Why it matters

Five cards, one per topic

Each card explains one part of how forests are monitored.

Satellite Remote Sensing
Satellite Remote SensingMulti-spectral imagery aids forest health assessment.
Machine Learning Models
Machine Learning ModelsMachine learning helps identify changes in forest cover.
Carbon Sequestration Analysis
Carbon Sequestration AnalysisAlgorithms convert forest data into carbon metrics.
Biodiversity Assessment
Biodiversity AssessmentSatellite imagery and field sampling track habitat, species, soil and water health.
Temporal Insights
Temporal InsightsAnalyse ecosystem shifts, disturbances and long-term change across time.
03 · From forest data to reporting

A video that follows the four steps

  1. Satellite-based forest mapping and land cover analysis
  2. Ground-truth ecological and biodiversity sampling
  3. AI-driven monitoring and recalibration
  4. Evidence for independent review

A 13-second video runs beside the steps, and each step is highlighted as the video reaches it.

04 · Reni

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.

reni · nature asset analystReni

Interactive demo. Responses and portfolio figures are illustrative.

RENI · AI ANALYST

Reni v2.4 online — nature asset intelligence active.

What is survivability across my sites?

RENI · AI ANALYST

Scanning 3 active sites… Avg survivability: 87.4%. ⚠ Site B (mangroves) at 74% — recommend ground validation sweep in Q2.

Try the live site

The website, as it runs today

This is the live site, embedded at desktop width. Scroll inside the frame to move through it.

mynzocarbon.comOpen in a new tab
04Reflect
How I would measure 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.

MeasureWhat it tells us
Time to publish an updateMinutes from making a change to seeing it live, against editing three sections by hand.
Blog orderWhether the newest post appears first after every publish.
Layout on phones, tablets and desktopsHow many tweaks each change needs, against the tweaks Figma Sites needed.
Marketing team requestsChanges still routed through me, against changes the team can now make directly.
Page speedLoad time on phone and desktop, since the site carries images and videos.
Search visibilityWhich pages Google finds, and how many visits come from search. Google Analytics shows this.
Reflection

What I would carry into the next project

Since the move

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.

What I did

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.

What I would do now

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.