Core Framework necessary?

Hi everyone,

with Bricks adding more native features over time — especially things like the new Color Manager, CSS variables, utility classes, theme styles, typography/spacing scales, etc. — I’m wondering how the community currently sees tools like Core Framework and Advanced Themer.

I own both and have used them because they added a lot of structure and workflow improvements that Bricks didn’t have natively before.

But now I’m asking myself:

  • Do Core Framework and Advanced Themer still provide enough real value today?

  • Or is Bricks native now good enough for most projects?

  • Where do you still see a clear benefit in using them?

  • And where do you think they have become redundant because Bricks now covers those areas itself?

My current impression is:

  • Core Framework seems to overlap more and more with what Bricks now does natively, especially around colors, variables, utilities, and design system structure.

  • Advanced Themer feels like it may still have more value because it improves workflow, builder UX, and day-to-day productivity rather than only managing design tokens.

So I’d be really interested in hearing how others handle this in 2026:

  • Are you still using Core Framework?

  • Are you still using Advanced Themer?

  • If yes: for which specific reasons/features?

  • If no: what made you drop them?

I’m mainly trying to avoid unnecessary overlap, double maintenance, and too many layers in my Bricks stack.

Curious to hear how others approach this.

2 Likes

Still using CF, mainly because I want all classes available in the Gutenberg editor as well. Bricks doesn’t do this (yet). And the interface is somewhat easier, but yeah, that’s more because I’ve used it longer I think…

I asked similar question on the FB group, search for: Bricks Native Framework vs CSS Framework?

Might be useful, cheers!