Allex
A Figma design from Panze Studio, rebuilt in Webflow as a template for the Webflow marketplace — a digital product designer’s portfolio with four home variants, CMS-driven case studies and an Insights blog.
- Webflow
- Webflow CMS
- CMS collections
- Digital product design portfolio
- Webflow developer, via Panze Studio
- Webflow Development
- allex-flowze.webflow.io
The ask
A Figma design from the agency, to be rebuilt in Webflow as a template for the Webflow marketplace.
The build
Rebuilt to the design with a class system meant to be extended, and everything that changes modelled as CMS collections.
The outcome
A template a buyer can run without touching code — four home variants, all of it CMS-driven.
THE PROBLEM
A template is judged by how it is built, not how it looks
A one-off Webflow site only has to work for its owner. A marketplace template has to work for strangers: someone buys it, opens the Designer, and starts changing things with no idea what any of it was called or why. Class names, structure and CMS design all become part of the product — and Webflow does not import a Figma file, so every one of those decisions gets made during the rebuild rather than inherited from the design.
THE SOLUTION
Rebuilt in Webflow, structured for a stranger
I rebuilt the Figma file in Webflow with a class system meant to be extended rather than one that merely satisfies the first page, and modelled everything that changes — case studies, journal posts — as CMS collections so a buyer fills the template rather than rebuilding it. The four home variants are the same content presented in different orders, which is the part a template buyer is actually shopping for.
- Four home page variants, so the same portfolio can be presented several ways
- Case studies and Insights posts as CMS collections, published without touching the Designer’s structure
- CV, bookmark and contact pages alongside the work itself
- A project inquiry flow in place of a plain contact form
THE STACK
Chosen for who picks it up next
Webflow and its CMS, with no third-party dependencies to explain — a marketplace buyer should be able to open the project and recognise everything in it:
- Webflow
- Webflow CMS
- CMS collections
THE RESULT
A portfolio that runs on its own CMS
The template does what a designer’s portfolio has to do without a developer involved: add a case study, publish a journal post, reorder the homepage. Built for the marketplace, it had to hold up for buyers nobody briefed and nobody supports directly.
THE SERVICE BEHIND IT
Want something built this way?
This project came out of my Webflow Development work. That page covers the process in full — what I deliver, how a project runs, and the questions people usually ask before starting one.
What that service covers
- Figma to Webflow builds matched to the design
- CMS architecture built around how your team publishes
- Reusable components and a documented class system
MORE WORK
Other case studies
Same write-up every time — the problem, the approach, the stack and what changed.
HTML template · Creative agency
Wesal
PSD to front end for Quomodosoft, approved on ThemeForest — work, skills, services, team and pricing in one long scroll, in four colour variants.
- HTML5
- CSS3
- Bootstrap
Product landing page · Consumer electronics template
MI Speaker
PSD to front end for Quomodosoft, approved on ThemeForest — features, specification table, video walkthrough and colour-variant checkout on one scroll.
- HTML5
- CSS3
- Bootstrap