Webflow
Build Webflow sites your team can keep running.
Six chapters of standards for a Webflow build, from the Figma handover to launch sign-off. With naming rules, decision tables and checklists you can copy.
A good Webflow build starts from a brief with named owners and a design that passes a readiness check. It uses one written class system, variables, components and a planned CMS model. Motion stays light and respects reduced motion, the team can publish without help, and each launch check has proof. This guide sets out those standards, chapter by chapter.
Chapters
Read it in order,
or jump in.
- 01
Brief and Figma handover
A build should start from decisions, not guesses. A one-page brief, a pass or fail gate for the Figma file, and what to do when the design arrives in another form.
6 min - 02
Client-First, classes and variables
Anyone should be able to open the project and know what a class does before they click it. The structure, the naming rules, the stacking limits and how variables fit in.
6 min - 03
Components and CMS model
The biggest structure choice in a build: should this be a component, a CMS collection or a one-off section? Decision rules, field standards, and real project examples.
7 min - 04
Interactions that stay fast
Every animation should earn its place. A ladder for choosing the lightest tool, a one-line spec for each interaction, reduced motion rules, and the numbers to test against.
6 min - 05
Editor handover
A handover is finished when your team has published something without help. Choosing roles, building for editors, a safe and ask-first table, and the handover pack.
6 min - 06
Pre-launch checks
The last gate. A table of checks, each with its proof, owner and severity, plus the Webflow traps worth testing by hand and a clear rule for when a problem blocks launch.
7 min
What you get
6 chapters that each end with a clear next move.
- One page of answers comes before the first class: owners, scope, editors, forms and tracking.
- Pick one written class system from the first section. Client-First is our default for new builds.
- CMS for items with their own URL, filters or data sources. Components for one design with different content. Plain sections for true one-offs.
- Each animation needs a job. Write down its trigger, phone behaviour and reduced motion behaviour.
- Handover is designed during the build. Props and fields decide what editing feels like.
- Each check needs proof someone can look at. "Looks fine" is not a result.
Who it is for
Marketing leads, designers and Webflow developers who are planning a build, handing a design over, or inheriting a project and want a standard to hold it to.
Planning a Webflow build? Book a free 20 minute callKeep a copy
Take the whole guide
as a PDF.
It all stays free to read here. If you want a copy for your team, leave your email and the download link shows up right away.
Thanks. Use it, share it, and tell us what is missing.
Download the PDFDownload the PDFFAQs
Questions
people ask.

No. What matters is one written system that the whole project follows. Client-First is our default for new builds because it is free, well documented and readable. If your site already has a working style guide, build on that, as we do for CUBE.
A one-page brief with named owners, final pages marked in the design, phone layouts or stacking rules, named text and colour styles, licensed fonts, and real content for key pages. Chapter 1 has the full gate.
Yes. CUBE sends HTML prototypes, and Baraka Impact had content and no design. The source changes, but the need for clear decisions and one class system does not.
Use the CMS when items need their own URL, need filters, or are created from data. Use a component when one design takes different content and the items are added by hand. Ask who adds the next one, and how often.
It can, depending on how it is built. Keep the hero visible at load, prefer transform and opacity, load heavy scripts only where they are used, and test on a real phone. Our post on interactions and performance goes deeper.
Give each person the lowest role that fits, put what changes into props and CMS fields, write down what needs asking first, and run a live publish test. Chapter 5 has a table you can copy.
Yes. It is written so that any team can use it. If you want us to do the build or review one, see Webflow development.


