Built for modern Webflow creators

Client-First Class Naming: The Rules I Follow in Every Webflow Template

How I name classes in every Webflow template with Client-First: sections, components, wrappers, combo classes, CMS lists and common mistakes.
2026-11-04
5
min read
Client-First Class Naming: The Rules I Follow in Every Webflow Template

Key Takeaways

  • I work only with Client-First, and I have done so since I started with Webflow.
  • A good class name tells you what the class controls before you open the Style panel.
  • Custom classes use group_element. Utility classes use hyphens only. Combo classes start with is-.
  • Repeated elements reuse the same class names, so you never create duplicate styles.
  • Most template problems I fix for clients come from bad class names: empty, random or unclear.

Why I Use Client-First for Every Project

I started with Client-First right away, because it is the best fit for building websites in Webflow. I did not need to switch from another system.

This case is for anyone who works with Webflow: people who are learning, people who want to build sites the right way, and people who want to scale a site that already exists.

Clear naming solves one simple problem. You can see which class is responsible for what, and which styles it controls. You do not get lost in class names. You can extend classes, add new ones, and keep the same styles on many pages. This works for spacing and sizes, and also for text and headings.

Webflow Navigator showing Client-First class structure of the hero section.
A clean class structure in the Navigator: every element has a clear name.

The Naming Pattern in One Table

The main rule of Client-First is simple: first the main name, then the subclass. The underscore separates the group from the element. Hyphens separate words inside a name.

Client-First class naming patterns I use in every Webflow template.
Class type Pattern Examples
Section section_name section_hero section_about section_services
Component name_component navbar_component header_component footer_component
Wrapper group_element-wrapper hero_image-wrapper heading_wrapper stats_icon-wrapper
Utility class Words joined with hyphens only padding-global container-large text-size-medium
Combo class is- + name is-white is-center is-tag

After you learn this table, you can read almost any Client-First project.

How I Name Sections, Components and Wrappers

Sections get the section_ prefix and a name that describes the content: section_hero, section_about, section_services.

Components end with _component: navbar_component, header_component, footer_component.

Wrappers describe what they hold: hero_image-wrapper, heading_wrapper, stats_icon-wrapper.

Utility Classes I Use in Every Template

These classes control the same things on every page:

  • Layout: padding-global, container-large, padding-section-large
  • Text size: text-size-small, text-size-medium, text-size-large
  • Headings: heading-style-h1, heading-style-h2, heading-style-h3
  • Buttons: button

Because these classes are shared, one change updates every place where the class is used. The same idea is behind the Style Guide page I build in every template.

Prepare the base before you build: see how I plan a complex Webflow project.

Webflow class list with Client-First utility classes padding-global, container-large and text-size-medium.
Utility classes control layout, text and headings across all pages.

Combo Classes with the is- Prefix

A combo class changes one thing on top of a base class. I use names like is-white, is-black, is-center, is-left, is-bold, is-small and is-tag.

The is- prefix makes it clear that this class is a modifier, not a separate element. When the base style is the same and only a small detail changes, I use a combo class.

When the element is different, I create a new class.
Webflow Style panel with a base class and an is-center combo class.
A combo class changes one detail without creating a duplicate style.

A Typical Section Structure in the Navigator

Every class has its own clear name, from the section to the smallest element. Here is how a hero section starts:

  1. section_hero
  2. padding-global
  3. container-large
  4. padding-section-large
  5. hero_component
  6. hero_content next to hero_image-wrapper
For repeated elements, the class names repeat too. This way I do not create new classes that duplicate the same styles, and I can change them quickly when needed.

Naming Classes in CMS Collections

Every collection has its own class names. By the name, you can see what the collection controls and which content belongs to it.

For example, a blog list looks like this: blog_list-wrapper, then blog_list, then blog_item. Inside the item is the repeated content, connected to the fields of the CMS collection.

Webflow Navigator with blog_list-wrapper, blog_list and blog_item classes in a CMS collection list
One naming pattern for every collection list.

Naming and Animations

This is general guidance, not a strict rule: keep your HTML tags correct, and use classes to connect animations. Do not add extra headings or extra wrapper elements only to make an animation work. Extra headings can confuse the page structure and get in the way of SEO.

How I Name Components in the Designer

I give components simple names that a person understands at once: Button, CTA, Footer, Faq Accordion, Header. Anyone who opens the Components panel sees what each component does.

Webflow Components panel with Button, CTA, Footer, Faq Accordion and Header components.
Components with clear names are easy to find and reuse.

Mistakes I See in Templates That Clients Buy

I work with templates that clients buy on the Webflow Marketplace, and I have seen many different mistakes:

  • empty classes without names
  • many unclear names with numbers
  • very short names that you cannot understand
  • names with two or three spaces
  • symbols from other languages, which are not recommended
  • one letter created in an H1, which is needed for SEO
  • many random names without a pattern
The number of classes depends on the size of the template: how many pages, how many sections and how complex they are. There is no exact number that is "normal".

The Mistake I Made When I Started

When I was learning, my biggest mistake was class nesting: I did not know which hierarchy a section needs. Some of my classes were unclear. Later I started to work with templates from other developers, and I saw how inconvenient it is. That experience taught me to build a clear structure from the beginning.

Why Clear Names Matter for Customization

Out of 15 clients who contacted me about a template they bought, 9 asked for customization and 6 asked to scale collections.

Customization means setting up the template and adding the client's own content. Sometimes clients ask me to set up separate animations, work with CMS content, or extend a collection so that all the needed content can be added. With clear names, I know where to change the style and where to add a field.

Webflow Marketplace Review

Before you submit a template, Webflow has a page with all the criteria you must meet. The review is very demanding and detailed. So if you see a published template on the Marketplace, you can be sure it passed all the checks.

My Advice for Beginners

Read the Client-First documentation. Then create a new site for yourself or for your portfolio. Create a new collection, fill it, and try to extend it with the data you need. This is the fastest way to understand the system.

About the Author:
I design and build Webflow templates for the Webflow Marketplace and work with the Client-First system, CMS structure and Variables. I write these guides from the templates and client projects I work on.
Last Updated:
2026-11-18
Best For:
SEO Specialists, CMS Editors, No-Code Developers, Website Owners, Marketing Teams

Webflow Class Naming FAQ: Client-First, CMS and Template Customization

These are the questions I hear most often about class names in Webflow. The answers come from my work with templates and with clients who customize them.

What is the difference between an underscore and a hyphen in Webflow class names?

In Client-First, an underscore splits a custom class into a group and an element, like blog_item. Hyphens join words inside a name, like blog_list-wrapper. Utility classes, such as padding-global, use hyphens only. So when you see an underscore, you know the class belongs to one group, and when you don’t, it is shared across the site.

What is a combo class in Webflow, and when should I use it?

A combo class is added on top of a base class to change one detail, for example is-center or is-white. My rule is simple: same element with one small change means a combo class, a different element means a new class. The is- prefix helps you spot modifiers in the class list at once.

Why does my Webflow template have empty or unnamed classes?

Usually the template was built in a hurry or imported from Figma with a plugin, without a naming system. I often see classes without names, names with numbers and names with extra spaces in templates that clients buy. You can rename them to the Client-First pattern, or remove unused ones in the Style Manager.

Can I rename classes in a Webflow template I bought?

Yes. A class is one shared style, so when you rename it, Webflow updates it everywhere it is used. Keep the same pattern as the rest of the template. Before you rename, check custom code: scripts and embeds that select a class by name, like .share-link, will stop working if the name changes.

How should I name classes for a CMS collection list in Webflow?

Use the same structure for every collection: blog_list-wrapper, then blog_list, then blog_item. For a new collection, copy this structure and change only the first word. The name then tells you which collection the class controls.

Do class names affect SEO in Webflow?

Class names are not a ranking factor, so renaming will not move your page up. What affects SEO is the structure behind them: one clear H1, a logical heading order, and no extra headings added only for animation. Clean names make it easier to find and fix such problems.

How many classes should a Webflow template have?

There is no right number. It depends on how many pages and sections the template has, and how complex they are. A better check is reuse: repeated elements should share the same class names, not new classes with the same styles.

What should I check in a Webflow template before buying it?

Open the template in the Designer and look at the Navigator and the class list. Good signs are clear names like section_hero, a repeating structure (padding-global, container-large, padding-section-large) and a Style Guide page. Bad signs are names like div-block-12, empty classes and random names.

How do I add a new section to a Client-First template without breaking it?

Copy a section that is already similar, then rename the section class, for example to section_pricing. Keep the wrapper chain the same: padding-global, container-large, padding-section-large. Reuse the existing utility classes for text and headings instead of creating new ones.

Does Webflow check templates before they go on the Marketplace?

Yes. Webflow has a page with the criteria a template must meet before you submit it, and the review is detailed. So a published template has passed those checks. Check the current requirements on that page, because they can change.

About Kedd Design
I design and build Webflow templates and websites with a clear structure.
I focus on clean structure and functional design.
100%
Built on Client-First methodology
Need a Webflow template or a custom website?
I build clean, well-structured Webflow websites. Tell me about your project, and I'll suggest the best next step.
tehnosupp@gmail.com
Prefer a quick chat? Reach me on:
Yevhen - Founder of Kedd Design
Yevhen - Founder of Kedd Design
Webflow Designer & Developer
Let's build something clear and well-structured together.