Use Client-First for large marketing sites with many unique sections and sites that will pass between several developers, because its semantic class names are easy to read and widely known. Use Lumos for highly componentized design systems, where its utility classes and fluid sizing save build time. Pick one before the build and don’t mix them.
Client-First vs Lumos at a glance
| Client-First | Lumos | |
|---|---|---|
| Created by | Finsweet | Timothy Ricks |
| Approach | Semantic, BEM-inspired names | Utility-first, similar in spirit to Tailwind |
| Example classes | section_hero, heading-style-h2 |
Short utilities with a u- prefix |
| Responsive sizing | Breakpoint-based | Breakpointless, fluid |
| Best for | Large sites with many unique sections and several developers | Componentized, repetitive design systems |
Why do naming systems matter in Webflow?
Webflow doesn’t enforce any naming convention, so without one every project ends up inconsistent and hard to hand over. A naming system gives everyone who works on the site, now and later, the same language for classes. That makes edits faster and lowers the risk of breaking a layout when someone new takes over.
- Webflow has no enforced naming convention out of the box, so without a system, every project becomes inconsistent and hard to hand off
- A naming system is really a shared language between developers (and future developers) working on the same site
What is Client-First?
Client-First is a Webflow class naming system created by Finsweet. It uses semantic, BEM-inspired names such as section_hero and heading-style-h2, with reusable global classes and scoped combo classes for exceptions. It’s widely used by freelancers and agencies, so most Webflow developers already know it, which makes hiring and handover easier.
- Created by Finsweet, structured around semantic, BEM-inspired class names (e.g. section_hero, heading-style-h2)
- Strong emphasis on reusable global classes plus scoped combo classes for exceptions
- Widely adopted across the freelance and agency Webflow community, which makes hiring and handoff easier since more developers already know it
What is Lumos?
Lumos is a Webflow framework created by Timothy Ricks that takes a utility-first approach, similar in spirit to Tailwind. It relies on short, reusable utility classes with a u- prefix and on fluid sizing that scales between screen sizes without fixed breakpoints. For repetitive patterns like spacing and colour, it usually needs fewer classes overall.
- Created by Timothy Ricks, leans into utility-first thinking (similar in spirit to Tailwind) with short, reusable utility classes (u- prefix)
- Designed around breakpointless, fluid responsive sizing rather than fixed breakpoints
- Tends to produce fewer total classes for highly repetitive utility patterns like spacing and color
When should you use Client-First or Lumos?
Client-First fits larger marketing sites with lots of unique sections, teams that value readable class names, and projects likely to pass between several developers over time. Lumos fits highly componentized, repetitive design systems, where fluid scaling and fewer custom breakpoints save real build time. The site’s structure should decide, not personal habit.
- Client-First: larger marketing sites with lots of unique sections, teams that value semantic readability, projects likely to be handed off between multiple developers over time
- Lumos: highly componentized, repetitive design systems where fluid responsive scaling and fewer custom breakpoints save real build time
Can you mix Client-First and Lumos in one project?
You can, but you shouldn’t. Mixing two systems in a single project removes the consistency that makes either one worth using, and the next developer has to learn both. Choose one before development starts, write down how it’s used, and keep to it instead of letting the naming drift during the build.
- Technically yes, but it’s not recommended for a single project, since mixing systems undermines the consistency benefit either one provides
- Pick one before development starts and document it, rather than letting it evolve organically mid-build
Building a site that needs to scale across a team? I can set up a naming system from day one so future updates don’t turn into guesswork. Book a free call.



