Frameworks
Choose a CSS framework for your Bricks Builder templates
Fancy Bricks templates carry no colors or sizes of their own; they read your framework's variables, so what you paste matches your site.
- One templateWritten once, in Fancy Framework.
- Converted when publishedNames swapped per framework.
- Your variablesCopy yours: Fancy Framework, Automatic.css 4 or Core Framework.
Same template, your framework
Pick a framework. The card stays the same; only the variable names change.
Same name in all three:
--primary--space-s … --space-xl--text-s … --text-xl
.fbk-card {
padding: var(--card-padding);
border-radius: var(--radius);
background: var(--base-ultra-light);
color: var(--text-color);
}
.fbk-card__title {
font-size: var(--h3);
}.fbk-card {
padding: var(--space-s);
border-radius: var(--radius);
background: var(--bg-ultra-light);
color: var(--text-color);
}
.fbk-card__title {
font-size: var(--h3);
}.fbk-card {
padding: var(--space-s);
border-radius: var(--radius-m);
background: var(--bg-body);
color: var(--text-body);
}
.fbk-card__title {
font-size: var(--text-2xl);
}Name converted for this framework
Side by side
Fresh installs: Fancy Framework, Automatic.css 4.0.1, Core Framework 2.0.2.
| What | Fancy Framework | Automatic.css 4 | Core Framework |
|---|---|---|---|
| License | Free | Paid license | Free, open source |
| Variables live in | Bricks' global variables | Its own stylesheet | Its own stylesheet |
| Stylesheet added | None | 65 KB, 10 KB gzipped | 50 KB, 8 KB gzipped |
| Utility classes | No | Fewer in 4 | Yes, generated |
| Color shades | Shades and transparencies | Shades | Shades and transparencies |
| Dark mode | Yes, from 1.1 | Yes | Yes |
| Your AI through MCP | Yes, four abilities | Not in its docs | Not in its docs |
| Section padding by default | Yes | Yes | No; the template adds it |
| Root font size | Configurable | Configurable | Configurable |
| Also works in | Etch | Etch, Gutenberg | Gutenberg, Oxygen, Figma |
| Renamed in our conversion | None, the source | A few names | More names |
Coming from Fancy Bricks 1.0 or 2.0
Those templates set every value by hand; 3.0 reads your variables. What you already pasted keeps working.
Questions, answered
The long comparison is in Automatic.css vs Core Framework in Bricks.
Do I need a CSS framework to use Fancy Bricks templates?
Yes, every 3.0 template requires one. Fancy Framework is free, so you can start without any extra cost.
What’s the difference between Automatic.css, Core and Fancy Framework?
All three give the template its variables: colors, spacing and typography. Automatic.css and Core are separate frameworks you install on your own, while Fancy Framework is free and built for this library.
Do the templates follow the framework’s dark mode?
With Fancy Framework, yes: the templates marked “Dark mode ready” switch with the site when it goes dark. Dark mode is a framework setting for the whole site, not the same as a dark background on one section.
Can I switch frameworks later without losing the design?
Yes. The same template is available in all three frameworks, so switching doesn’t mean redoing the design.
I used Fancy Bricks 1.0 or 2.0 without a framework. What changes now?
Fancy Bricks 1.0 and 2.0 didn’t require one; the 3.0 library does. Fancy Framework is free, so you can move to 3.0 without buying anything extra, and the templates you already pasted keep working.
Start with the free Fancy Framework
Pick a template and copy the version for your framework.
