Feature Requests

With the addition of ACF flexible content fields, it would be helpful to be able to export global blocks and templates in bulk without copy pasting everything individually.

Dear Breakdance Team, I'd like to submit a feature request regarding a much-needed enhancement to the Loop Builder: the ability to assign native facets directly within Breakdance – without relying on third-party solutions like GridBuilder or FacetWP. Why This Matters Breakdance already has an excellent Query Builder and includes a basic Filter Bar. However, the Filter Bar feels more like a nice bonus than a fully realized feature. It works smoothly and includes pleasant animations, but its functionality is extremely limited – almost as if it was added and then never touched again. And that’s a shame, because the foundation is already there. The Problem with Third-Party Plugins Styling limitations: Tools like FacetWP or GridBuilder often don't integrate seamlessly with Breakdance’s styling system. Matching their UI to a Breakdance site requires extra work and often still feels "off." Functional conflicts: Particularly with GridBuilder, we've noticed incompatibilities when working with Breakdance's advanced query and dynamic content tools. Loss of native experience: The smooth animations and intuitive UX of Breakdance’s built-in filter system are missing in these third-party tools – unless we start writing custom scripts, which defeats the purpose of using a visual builder. What We Need We’d love to see first-class native facets support within Breakdance, tightly integrated with the existing Query Builder and Loop Builder. Ideally, this would include: Support for filtering by taxonomy, custom fields, post types, etc. Multiple filter types: dropdowns, checkboxes, sliders, search fields, etc. Ajax-based filtering with no reloads. Full visual styling control within Breakdance. Conditional logic and dynamic filtering combinations. The Result A native facets system would elevate Breakdance's Loop Builder to a new level, enabling complex, dynamic content filtering without compromising on design, compatibility, or user experience. It would also reduce reliance on third-party plugins, making Breakdance a more complete, reliable solution out of the box.

Allow to customize the Woo notification emails for new orders, failed orders, etc. Please add the tracking number widget as well.

Consider Relume AI sitemap/wireframe type functionality or integration allowing for rapid prototyping.

translatepress is faster page loading, more powerful, and less expensive than wegolt

Please allow the ability for me to create and rename each of them - colours, buttons and different button states. One might be a contact button and I'd need to be able to have open a modal so in some cases I'll want to have pre filled links and hashes Not every website needs only two buttons - I have a very strong visual hierarchy and it'd be great if I can allow them to change button types easily. Please also please allow us to use the 'fullwidth on X breakpoint setting'

I would like to rename my style sheets so that in a view I can understand what is written there

A limitation of Breakdance in the UX department is being unable to rename CSS classes to fix things like typos or just to repurpose or otherwise clarify their function in the CSS class name to follow BEM standards for example. Oxygen also has this limitation and it’s one of the most requested features there. Bricks Builder allows renaming CSS classes and it’s super helpful. Hopefully we see this in Breakdance someday soon too.

Being able to apply modified parameters to a class without make it first a class. Workflow: Modify single item Click on modified at the bottom Apply to new class