Your client asks: "Can all the buttons be a bit rounder?" But you styled each button on its own.
That's twelve buttons across five pages, twelve edits, and you'll probably miss one.
The fix isn't working faster. It's knowing where your styles live.
Three places a style can live
Theme Styles set the defaults for every element of one type. We used them for section padding in Episode 2.
A global class is a named set of styles you can add to as many elements as you like.
Element styles belong to that one element only.
This episode compares the last two.
Element styles: one element only
When you select an element and style it, Bricks saves the style to that element's ID by default. The ID (like #brxe-a1b2c3) is the element's own unique name, so the style only affects that one element.
That's perfect for a true one-off, like a hero heading that only appears once.
The catch: duplicate that button, and you duplicate its styles too.
Now you have two separate sets of styles to keep in sync.
A global class works like a label
In the Bricks builder:
Select the element.
Click the ID field at the top of the panel.
Type a name, like
btn-primary, and press Enter.
From now on, every style you set goes to the class instead of the element.
Add the same class to every main button, and the styles live in one place.
When your client wants rounder buttons, you change the class once, and every button with that class updates on every page.