Next Bricks

Next Bricks is an add-on for Bricks Builder that gathers extra design elements and visual features in one plugin. Its stated focus is practical rather than administrative: sliders, menus, buttons and background effects, with each component configured through the controls Bricks users already work with. That makes it relevant to site builders who want more building blocks without leaving the Bricks editing model.

A focused element library

The useful proposition is the range of components rather than a single headline feature. A project that needs a rotating content area can draw on the slider element; a navigation-heavy layout can use an additional menu component; and calls to action can be assembled with the button element. Background effects round out the visual side of the library, giving designers another way to shape sections and page surfaces.

These are familiar interface requirements, but keeping them together has a practical benefit. Instead of sourcing one extension for sliders, another for menus and a third for visual backgrounds, a Bricks site can look to one element collection first. The supplied description also calls the components customisable, so the appeal is not limited to inserting fixed patterns. The exact depth of that customisation is not specified, however, and the examples should be treated as the confirmed scope rather than a complete catalogue.

Built around Bricks controls

Next Bricks uses native Bricks controls for its elements. That matters because the plugin is presented as an extension of the builder rather than a separate design system with an unrelated interface. A designer already comfortable with Bricks can approach sliders, menus, buttons and background effects through a familiar control structure, which keeps the add-on conceptually close to the rest of the page-building workflow.

The same approach also suits teams that want their extra components to sit alongside existing Bricks content. There is no claim here of a separate dashboard, analytics layer or standalone editor; the product is specifically about adding elements and features to the Bricks experience. The vendor also positions its native-control approach as supporting integration and performance, though the supplied information does not provide technical details or measurements behind that claim.

What to weigh

The first trade-off is platform dependence. Next Bricks is useful only within a Bricks Builder workflow, so it is not a general-purpose element library for sites built with another editor. A team standardising on a different builder would gain little from its component set.

The second trade-off is uncertainty around the library’s boundaries. Sliders, menus, buttons and background effects are named, but the description does not list the number of elements, explain their individual controls or identify which background effects are included. That makes it harder to plan a project around a precise feature checklist before working with the plugin. A broad collection can also introduce more design choices to maintain and standardise across a site, particularly when several components address similar layout needs.

Who it suits

Next Bricks fits Bricks users who regularly build custom page sections and want a wider selection of ready-made components inside the builder. It is especially relevant to a designer looking for dedicated pieces for sliders, navigation, calls to action and section backgrounds, rather than a plugin focused on one narrow function.

It is less compelling for a site that already has the required elements, for a team seeking a builder-independent toolkit, or for anyone who needs a documented inventory of every component before choosing an extension. On the information available, the sensible expectation is a Bricks-specific collection of customisable elements, with its value tied to how often those four named areas appear in the site’s layouts.