Understanding how Sections behave
All styles are pre-defined and self-contained
Typography, spacing, colors, headings, buttons, animations – everything is already written into the classes of the Section. There is no dependency on Webflow Variables, and no reliance on a global style guide.
Collections have different naming conventions
Evermind uses a certain naming style.
Hollow uses another.
Forerunner has its own logic.
If you mix sections from multiple collections, Webflow will naturally generate class variations (like [class]section-2[/class], [class]heading-3[/class], etc.). This is expected and nothing is “broken”.
Sections prioritize visuals over systemization
They are intentionally simple: copy, paste, adjust.
No architecture, no tokens, no variables.
If you need scalability and a unified class system, Skeletons are the better choice.
Structural classes are unique and intentional
Grids, wrappers, inner containers, decorative elements – these classes define the layout and should usually remain unchanged. They belong to that Section specifically and don’t interfere with other components.
