A Webflow design system now has three layers that Webflow itself supports: variables for values, classes for the styles that are left over, and components for structure. Webflow added variable modes on 14 January 2025, function variables with clamp(), calc(), min(), max() and color-mix() on 3 June 2025, and slot restrictions on 28 August 2026, so most of what used to need a framework convention or custom code is now a product feature.
This guide is the build discipline we would apply to a marketing site that a marketing team will extend for two years: which values become variables, how few classes you need, when a section becomes a component, and what to write down. Product facts come from Webflow's update log, pricing page and its own design system guidance; framework rules come from the Client-First documentation.
What breaks in year two, and which layer prevents it
A design system is judged in month fourteen, not at launch, when the original designer has moved on and a marketer has built thirty landing pages. The table lists the failures we would expect on an audit and the layer that prevents each.
| Symptom in year two | Usual cause at build time | Layer that prevents it |
|---|---|---|
| Five slightly different greys in the style panel | Hex values typed into classes | Primitive and semantic variables |
| A rebrand means editing hundreds of classes | Colours and sizes not connected to variables | Semantic variables, with modes for themes |
| Classes such as heading-2-copy-copy | New classes made to change one property | Utility classes plus a naming rule |
| Elements with six stacked classes nobody dares edit | Deep stacking to reuse styles | Custom classes per component |
| Marketing duplicates a page to get a section | Sections built as loose elements | Components with properties |
| A section breaks when a marketer drops in the wrong card | Open slots | Slot restrictions and defaults |
| The microsite drifts from the main site | Styles copied by hand between sites | A Shared Library |
Layer 1: variables, primitives first and semantics on top
Webflow's own guidance calls variables the most atomic unit of a design system and splits them into two kinds. Primitives are raw values named for how they look, such as Blue 400 or Gray 100. Semantic variables are named for what they do, such as Primary Text or Card Border, and reference a primitive when several share a value.
The reason for two tiers is shown in Webflow's own example. If 3rem is used as a margin, a padding and a font size, create one primitive for the raw value and two semantic variables, one for spacing and one for font size. A later change to the type scale then leaves spacing alone.
Naming. Webflow recommends title case with spaces, a 100 to 900 scale for colour shades so a new shade can be inserted later, and one consistent ramp for sizes, either numbered steps or t-shirt sizes. Its guidance notes that applied variable names add to the size of the rendered CSS, so keep them short but readable.
Collections and modes. Since January 2025 variables can sit in custom collections such as Colour Palettes or Typography, and each variable can hold several values called modes. Automatic modes follow the Tablet, Mobile Landscape and Mobile Portrait breakpoints; manual modes are applied to a page, section or element, for a dark band or a campaign theme. Webflow's test for a mode is whether you would ever relink the same property to a different value. If a value never changes with context, it does not need a mode.
Function variables. Since June 2025 a variable can hold clamp(), calc(), min(), max() or color-mix(), so one fluid heading size can replace per-breakpoint overrides.
| Collection | Primitives | Semantic variables that reference them | Modes |
|---|---|---|---|
| Colour | Brand 100 to 900, Neutral 100 to 900, White | Text Primary, Text Muted, Background, Surface, Border, Accent | Light, Dark, one campaign theme if needed |
| Typography | Font families, Size 1 to 9, line heights | Heading 1 to 6 size, Body, Small, Eyebrow | Automatic per breakpoint |
| Spacing | Space 1 to 9 | Section Padding, Gap Cards, Gutter | Automatic per breakpoint |
| Layout | Max widths | Container Large, Medium, Small | None |
| Decoration | Radii, border widths, shadows | Card Radius, Button Radius | None |
Source: structure follows The Webflow Way variable use cases (colour, typography, spacing, components, decoration, sizes); values are the reader's own
Layer 2: classes, fewer than you think
With variables holding the values, a class system needs only a naming rule, a small set of global utilities and one custom class per part of each component.
Client-First. Finsweet's convention is the most widely documented. Utility classes are global and never contain an underscore. Custom classes contain one, reading from general to specific, as in team-list_headshot-wrapper. Combo classes take an is- prefix and only work on top of their base class. The documentation advises against deep stacking because many classes on one element are hard to read, reorder and edit in the Designer; when stacking gets complicated, it says to create a custom class.
Core utilities worth keeping. Client-First's utility systems give a useful minimum: padding-global for side gutters, container-large, container-medium and container-small for widths, padding-section-small to padding-section-large for vertical rhythm, heading-style-h1 to heading-style-h6 so the look of a heading is separate from its tag, and a spacing scale from 0 up to 12rem. Its documentation shows these values living in variable collections, which keeps the two layers connected.
Lumos. Timothy Ricks's framework leans harder on variables and variable modes, and its utilities cover grid and flexbox layout, so fewer custom classes are needed. A 2026 comparison by the Webflow agency Digidop judged it less accessible to clients than Client-First.
| Approach | Strength | Risk in year two | Fits |
|---|---|---|---|
| Client-First | Names any editor can read; documented widely | Utility sprawl if every one-off gets a class | Teams with mixed skills and agency handovers |
| Lumos | Variable-led; theming through modes | Steeper for non-developers | Teams with a developer on hand |
| Component-led, few utilities | Styles live inside components and variants | Needs discipline when building new sections | Sites where marketing builds from components only |
Source: Finsweet Client-First documentation; Digidop, Client-First vs Lumos, updated 2026-01-25; The Webflow Way, Components
Webflow's own guidance pushes toward the third row. It describes developer components, layout patterns built as components, as often a better alternative to utility classes when combined with style variants, because they cut class bloat. We would still keep a small Client-First style utility set for gutters, containers and heading styles, and put everything else inside components.
Layer 3: components with properties, variants and slots
Webflow's guidance is direct: build a component for any UI that appears more than once, including headers, footers, buttons, cards, sections and Collection Lists, and treat a page section as the largest sensible scope. Page structures belong in page templates, which are built from components.
The harder decision is how each component varies. Webflow has three tools, and using the wrong one is the most common reason a component library ends up duplicated.
| What varies between instances | Use | Example |
|---|---|---|
| Text, image, link, an optional element | Properties | Section headline, body, image and an optional button |
| Appearance with the same structure | Style variants | Button Primary and Secondary; Card Horizontal and Vertical |
| How many child items, or which ones | Slots | A testimonial section that takes three or six testimonials |
| Nothing, by design | Static content inside the component | Footer navigation links |
| Structure and props differ substantially | A separate component | Pricing Card versus a generic Card |
Source: The Webflow Way, Components; Webflow University design system checklist
Variants. Style variants arrived on 19 November 2024. Every variant inherits changes to the base, and variants can be combined on nested components, so one Card with layout variants can hold a Button with colour variants. Webflow suggests renaming the Base variant to something meaningful, such as Primary, and ordering variants by how often they are used.
Slots and their guardrails. Slots arrived on 10 July 2024 and let an instance take any components. Webflow's own tip is that many visibility properties on one component usually mean it should have a slot instead. On 28 August 2026 Webflow added slot restrictions, which let anyone with the Designer or Site manager role limit a slot to named components; a marketer who drops in anything else sees a message listing what is allowed. On 23 October 2026 slot defaults followed, so a card can arrive with its button already in place. Slots still accept everything by default, so restrictions have to be set on purpose.
Test like the editor. Webflow's checklist asks for components to be tested with long content and on small screens.
Our earlier post, A Marketing Website the Marketing Team Can Actually Edit, covers page templates, roles and what to lock; this guide is the layer underneath.
When one site becomes several: Shared Libraries
A design system that lives on one site is copied by hand the first time the company launches a microsite or a product subdomain. Shared Libraries remove the copying. Built first for components and variables, they gained assets and variable modes on 11 March 2025, and tag styles such as body and headings on 7 October 2026.
Plan limits. On Webflow's pricing page, read in November 2026, the Starter Workspace has no Shared Libraries, Core, Growth and Freelancer have one, and Agency has unlimited.
How updates move. Library resources are edited only on the source site; each consuming site reviews and accepts an update, then republishes. With tag styles, the consuming site's own tag styles win over the Library's, and classes win over both. Uninstalling a Library merges the tag styles into the site, so its appearance does not change.
In our white-label work for Web Tonic, 20 or more Webflow sites in twelve months at two to three weeks each, a repeatable starting point is what makes that pace possible; a Library is where we would keep it.
The style guide page and the change log
The last layer is documentation, and Webflow's design system checklist treats it as part of the build, not an extra. It asks for a style guide page showing colours, type, spacing and common components with usage notes, one current guide covering limits and examples, and a change log.
What the style guide page holds. Every semantic variable, every utility class in use, every component with each variant, and which slots accept what. Kept on the site, it stays in sync with the system.
How things are retired. The checklist suggests labelling phased-out resources Legacy before removing them, and testing changes on a few pages first. That one habit stops most year-two breakage, because nobody deletes a class that forty CMS pages still use.
Who owns it. Name one person who approves new variables, classes and components. In our four-week marketing site process, we would hand this over in the last week with the CMS guide.
What this means for your next Webflow build
Budget the design system as build work, not as polish. In practice that means four decisions before anyone styles a page: the primitive and semantic variable set, the class convention and its utility list, the component list with the variation method for each, and who owns changes after launch. If the site will have siblings, decide on a Library source site in the same meeting.
When you brief an agency, ask to see a past project's style guide page and component list, not only its homepage. Our marketing websites page explains how we scope a Webflow build with this structure.


