S2 Framework
Clone S2 in Webflow
English
English
  • Welcome
    • S2 is flow simple!
    • Getting Started
  • How to use the Cloneable?
  • Guide & Documentation
    • Basic Concepts
      • Styling in Webflow
      • Utility Classes
      • Units
      • Fluid Typography
    • Variables
      • Colors vs Palettes
      • Colors in S2
      • Text
      • Variable Groups
    • Naming Strategies
      • Class Naming
      • Other Naming Strategies
      • Naming Custom Attributes
    • Structure
      • HTML Structure
      • Global Code
    • S2 Attributes
    • S2 Components
  • Editions
    • Build your own S2
      • One-page Style Guide
      • Lite Edition
  • More
    • FAQs
    • Ready to switch to S2?
      • Frameworks Comparison Overview
      • From Client-First
      • From MAST or The Saddle
      • From Lumos
    • Tools and Resources
    • Read More
      • Foundations of S2
      • Our Approaches
  • Links
    • 🤘Clone in Webflow
    • 🪵Changelog & Roadmap
  • Copyright & Terms
Powered by GitBook
On this page
  • Naming Variables
  • Naming Components
  • Naming Webflow Interactions
  1. Guide & Documentation
  2. Naming Strategies

Other Naming Strategies

PreviousClass NamingNextNaming Custom Attributes

Last updated 3 months ago

Naming Variables

Use full words and standard English for variable names.

Avoid lengthy names. Other than normal hyphens and spaces, avoid using underscores and other unnecessary punctuations in variable names.

Compare:

Variable name on the panel
Actual code generated

Good ✅

Padding/Tablet Small

var(--padding--tablet-small)

Bad ❌

Component - Card/Card Body Padding [LG]

var(--component-card--card-body-padding-lg)

We aim for clear and simple names that are easy to search for in the Webflow panel. They should also be easy to type when coding.

Naming Components

While it is flexible, we recommend naming Webflow components using natural and concise English titles with title capitalization; keep names short and make your components easily searchable and identifiable. Organize your components into folders. Examples:

Blog Card

Latest Status Block

CTA: Subscribe

CTA: Enquiry

Some components are meant to be nested within another component. In that case, you can add a "- " before the name to make them easily identifiable and prevent them from appearing at the top when using . Examples:

Subscription Section

- Simple Subscription Form

Naming Webflow Interactions

Suggested format: Name of element + [State: Optional description of action]

Section Image [Fade in]

Box Icon [Open]

Box Icon [Close]

Box Icon [Open: Rotate]

Box Icon [Close: Back to 0]

"While scrolling" and "Mouse move" animations don't typically change to a specific state, so you can get more descriptive with them, e.g. Profile Cards [Floating effect].

About title capitalization:

The naming convention for Webflow Interactions is the same as that suggested by . You should also keep the names short and descriptive, for example:

Quick Find
Capitalization in Titles: Rules and Examples
Client-First