- A Webflow design system has four layers: variables, classes, components and, if you run several sites, a shared library.
- Build them in that order. Each layer stands on the one before it.
- Put a value in a variable, a look in a class, a repeated section in a component.
- Shared libraries help when more than one site in a Workspace needs the same parts. One site does not need one.
- Test the system with a real job: can someone build a new page without creating a new class?
The short answer
A design system in Webflow is four layers: variables hold your values, classes hold your styles, components hold your repeated sections, and a shared library carries all of it to other sites. Build in that order. Most single sites need the first three and can skip the fourth.
The test of a good system is simple. A teammate can build a new page from what is already there, without making a new class or typing a new colour.
Layer 1: variables hold the values
Webflow has five variable types: colour, size, percentage, number and font. Size covers spacing and type sizes. Number covers unitless values such as font weight.
A variable can also point to another variable of the same type. This is called an alias, and it gives you a clean two-step setup:
- Base values. The raw palette and scale, such as
purple-500orspace-4. Nobody styles with these directly. - Roles. Names that say what a value is for, such as
text-accentorsection-gap. Each one is an alias of a base value.
Now a rebrand means changing a few base values, and a change of role means relinking one alias. Modes let one variable hold different values, such as a dark theme or a tablet size. One thing to plan around: an alias across collections takes the base mode value of the target collection, so keep values that change by mode in the same collection where you can.
Layer 2: classes hold the looks
Classes should read their values from variables, so the class says what a thing looks like and the variable says how much. Pick one naming system and stay with it. We used Client-First on Petavue, so the team can add pages and sections that stay consistent with the rest of the site, and on TripleDart.
Use a global class for anything shared and a combo class for a true variation, such as a dark version of a card. If you keep making combo classes to undo the base class, the base class is doing too much. Split it.
Layer 3: components hold the sections
Turn a section into a component once it appears on a second page. Then decide what editors may change, and expose only that through component properties: heading, text, image, link, and a show or hide switch for optional parts.
Two real examples of how far this goes:
- TripleDart. Every section is a Webflow component on a Client-First class system, and the team now adds pages from those components.
- Bailey Creative Studio. A reusable outreach page built from components. Bailey duplicates it, fills in the client name, video and links through component properties, and sends it.
Few properties beat many. A component with twenty switches is a form nobody wants to fill in. If a section needs that many, it is probably two components.
Keep the structure inside a component locked, and let the properties carry the content. That is what stops a busy editor from breaking the layout the week before a launch.
Layer 4: shared libraries carry it across sites
A shared library lets you reuse components, variables, fonts, tag styles and assets across sites in one Workspace. Webflow suggests a separate design system site to hold them. The rules that shape your workflow:
- The main component can only be edited on the source site. Other sites change instances through properties.
- Variable values and modes can only be edited on the source site.
- Changes are pushed from the source, then reviewed and accepted on the sites that use them.
You want this if you run a main site plus a docs site, or a group of regional or product sites. You do not want it for one site, because it adds a review step and gives you nothing back. Plan limits and feature status change, so check the current Webflow docs before you commit.
What goes where: a decision table
| You have | Put it in | Why |
|---|---|---|
| A colour, a space, a type size | Variable | One change updates every use |
| A look used in many places, such as a card | Global class | Keeps the styles in one spot |
| A small variation of that look | Combo class | Inherits the base and changes little |
| A section repeated across pages | Component with properties | Edit once, and editors cannot break it |
| A list of similar items, such as case studies | CMS collection | Content grows without layout work |
| Parts needed on a second site | Shared library | One source for several sites |
Building on a style guide you already have
You often will not start clean. On CUBE, the team sends HTML prototypes of new pages, and those prototypes bring their own fonts and colours. We rebuild each page natively in Webflow and link every colour, heading and space to CUBE's existing variables, so new pages match the rest of the site and the team can edit them in the Designer.
The lesson works for any site with a style guide: never copy values across from a design or a prototype. Map each one to a variable that exists. If nothing fits, decide on purpose whether the system needs a new value or the design needs to change.
A checklist before you call it done
- No element uses a typed colour where a variable exists.
- Every role variable is an alias of a base value.
- Heading styles are set once, not per section.
- Class names follow one written convention.
- Every repeated section is a component.
- Component properties cover what editors change, and nothing else.
- A style guide page shows each type style, button and colour.
- Modes, if you use them, have been checked on every key page.
- Someone new builds a test page without a new class.
- Unused classes are cleaned up before handover.
What to do next
Start with an audit of one page: count the typed colours, one-off classes and copied sections. That tells you which layer to fix first. If your design is still in Figma, plan the variables there, then follow our Figma to Webflow checklist.
If you want this built or cleaned up, see Webflow development or send us your site.
Terms used: Webflow, Webflow components



