The WordPress builder ecosystem has shifted a lot over the past few years. As more developers move away from Oxygen Builder and toward Bricks Builder, one thing has become very clear: speed and structure matter more than ever. Design systems aren’t a “nice to have” anymore — they’re the backbone of scalable, repeatable client work.
If you built sites with Oxygen, chances are you relied heavily on OxyMade. And if you’re now building with Bricks, you’ve probably been searching for that same level of structure. That’s where BricksMade enters the picture.
OxyMade became popular for one main reason: it made Oxygen Builder practical at scale. Instead of rebuilding spacing systems, button styles, typography rules, and layouts on every project, OxyMade introduced a predictable, utility-driven design system that actually stuck.
Built specifically for Oxygen Builder, OxyMade combined three important ideas:
The result was faster builds, less second-guessing, and way fewer “why does this section feel off?” moments. You could move quickly without your designs drifting over time. Honestly, once you used it, going back felt rough.
While Oxygen slowed down development-wise, Bricks Builder continued to evolve. Bricks introduced a faster editor, cleaner architecture, native components, better conditional logic, and a workflow that feels closer to modern frontend development.
But early on, one thing was missing: a true OxyMade-style design system that felt native to Bricks.
Yes, you could wire together your own setup with utility frameworks, global classes, and templates — but that takes time. And time is the thing agencies and freelancers have the least of.
BricksMade is essentially the answer many former Oxygen users were waiting for. It brings the same philosophy that made OxyMade successful — structured layouts, reusable blocks, and consistent styling — but rebuilds it specifically for Bricks Builder.
Instead of forcing Bricks into an Oxygen-shaped workflow, BricksMade leans into how Bricks actually works.
This matters more than it sounds. Because Bricks already has a powerful components system, BricksMade blocks can be converted into reusable components, edited once, and updated everywhere. That’s huge for long-term maintenance.
At a high level, here’s how the two systems line up:
The goal is the same in both cases: build faster, stay consistent, and stop reinventing the wheel on every project. The execution is just tailored to the builder.
Design systems aren’t just about speed — they’re about mental load. When spacing, typography, and layout decisions are already solved, you can focus on content, UX, and conversion instead of fiddling with pixels.
For client work especially, this is where profit is won or lost. Faster builds mean better margins. Consistency means fewer revisions. And reusable systems mean future changes don’t turn into disasters.
This is exactly why tools like OxyMade thrived — and why BricksMade is gaining attention now.
From my perspective at MKS Web Design, BricksMade feels like the natural continuation of what OxyMade started. It doesn’t try to overcomplicate things. It respects how Bricks works, and it gives you a strong starting point without locking you into a single opinionated system.
If you’re coming from Oxygen, BricksMade will feel familiar — but cleaner. If you’re already deep into Bricks, it’s a solid way to standardize builds without slowing yourself down.
No system is magic, but having one is almost always better than pretending you don’t need it.
OxyMade proved that structured design systems could dramatically improve WordPress workflows. BricksMade takes that same idea and applies it to a builder that’s actively evolving and pushing forward. If you care about speed, consistency, and scalability — especially for client sites — this is a space worth paying attention to!
