Playbook: setting up Bricks global classes the right way from day one

Playbook: setting up Bricks global classes the right way from day one

Global classes are Bricks' superpower — and its biggest footgun if rushed.
— Define a naming convention before building (BEM-lite: btn, btn--ghost).
— Build spacing/typography utility classes first, apply them everywhere instead of per-element styling.
— Turn ON "class management" cleanup to prune unused classes monthly.
— Avoid styling on the element ID — push everything to classes so changes cascade.

Pros:
— One edit updates the whole site; tiny CSS output.
— Behaves like a real design system.

Cons:
— Steep for designers used to clicking each element.
— Messy early naming is painful to refactor later.

Best for: developers who want a Tailwind-style workflow inside a visual builder.