←
All Posts
8 min read
Client-First vs Lumos: Which Webflow Naming System Should You Use?
Client-First and Lumos solve the same problem with different philosophies. Here's how they actually compare for real Webflow projects.
Why Naming Systems Matter in Webflow at All
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 Client-First Is
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 Lumos Is
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
Where Each One Actually Shines
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 Them?
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.
FAQs
Which naming system is better for SEO?
Neither has a direct SEO impact, since class names aren't a ranking factor. The indirect benefit is maintainability: a well-organized system makes it faster to update content and fix technical SEO issues later without breaking the layout.
Do I need to know Client-First or Lumos if I'm not a developer?
No. These are internal organizational systems for whoever builds and maintains your site. As a business owner, what matters is that whoever builds your site uses some consistent system, not which one specifically.
Is one of these systems Webflow's official standard?
No, Webflow itself doesn't enforce or officially endorse either system. Both were created by individual experts in the Webflow community and have become de facto standards through widespread adoption.
Can I switch a site from one system to the other later?
Yes, but it requires going through and renaming classes throughout the project, which takes real time on anything beyond a small site. It's much more efficient to choose a system before the build starts.
Curious which approach fits your specific project? Send me your Figma file and I'll recommend a structure before any building starts.
Why Naming Systems Matter in Webflow at All
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 Client-First Is
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 Lumos Is
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
Where Each One Actually Shines
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 Them?
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.
FAQs
Which naming system is better for SEO?
Neither has a direct SEO impact, since class names aren't a ranking factor. The indirect benefit is maintainability: a well-organized system makes it faster to update content and fix technical SEO issues later without breaking the layout.
Do I need to know Client-First or Lumos if I'm not a developer?
No. These are internal organizational systems for whoever builds and maintains your site. As a business owner, what matters is that whoever builds your site uses some consistent system, not which one specifically.
Is one of these systems Webflow's official standard?
No, Webflow itself doesn't enforce or officially endorse either system. Both were created by individual experts in the Webflow community and have become de facto standards through widespread adoption.
Can I switch a site from one system to the other later?
Yes, but it requires going through and renaming classes throughout the project, which takes real time on anything beyond a small site. It's much more efficient to choose a system before the build starts.
Curious which approach fits your specific project? Send me your Figma file and I'll recommend a structure before any building starts.
Work with me
Have a design that needs a clean build?
Have a design that needs a clean build?
Have a design that needs a clean build?
I help designers, studios, and founders turn Figma files into fast, responsive Webflow and Framer sites that are easy to manage after launch.
I help designers, studios, and founders turn Figma files into fast, responsive Webflow and Framer sites that are easy to manage after launch.
I help designers, studios, and founders turn Figma files into fast, responsive Webflow and Framer sites that are easy to manage after launch.