Ship Bricks sites clients can’t break.
Tick one box in Bricks and that element becomes a field in the block editor. Your client edits it there. Structure, classes and styling never enter the room.
Built for the block editor and WordPress 7 · Bricks Builder 1.9 and newer
This is your client’s entire job
A native block, native panels, nothing else. Change a field on the right and the section updates — the demo behaves exactly like the plugin does in WordPress.
Play your first round in five days
From your first swing to the licence test, coached by our PGA pros.
- Small groups, fixed times
- Clubs included
Client control takes one click per element
No shortcodes, no field mapping, no second admin screen to keep in sync. Open the template you already built and release what the client is allowed to touch.
Select an element in Bricks
Heading, text, rich text, image, gallery, button, counter — or any section, container, block or div.
Tick “Editable in Gutenberg”
Optionally name the field and pick which formatting the client gets. That is the entire configuration.
Save. That’s it.
The template appears as a block, the field appears in the sidebar, and one template still drives every page that uses it.
What changes on handover day
This is not a feature comparison. It is a question of who can break what, and who gets the call when they do.
| On a client site | With ClientWP |
|---|---|
| Who can change the layout | Only you. Structure and classes are never exposed |
| What the client sees | The fields you released, in the editor they already know |
| Training required | None. It is the standard WordPress editor |
| Layout alternatives | Variants in one template. The client switches, the copy survives |
| Repeating content | Rows per block instance, so two lists on one page stay separate |
| Adding new sections | You allow, restrict or block each one, site-wide |
| Editing rich text | A real editor with lists, bold, italic and links |
| Changing the design later | Edit the template once. Every page follows |
Control that goes further than locking the builder
Every feature answers the same question: how much freedom does this client need, and where exactly does it stop?
What clients may edit
Headings, text and buttons one click
Click into the block and type. You choose the allowed formatting per element, and which heading levels are on the table.
Rich text in a real editor our advantage
Bulleted and numbered lists, bold, italic, links — in a proper WYSIWYG, not a textarea full of tags. It saves clean HTML that Bricks renders untouched.
Image or colour backgrounds our advantage
Per container you release the background image, the colour, both, or neither. Sizes, positions and overlays stay in your template.
Links on containers a-tag
When a card is wrapped in a link, the client picks the destination by searching posts. No typed URLs, correct across languages.
Where control gets serious
Variants at every level our advantage
Not only alternative sections: variants inside containers, inside blocks, nested as deep as your template goes. One template covers image-left, image-right, stacked and more — and the copy carries over when the client switches.
Visibility that really removes no markup
Off means the element never renders. No hidden divs, no empty wrappers, nothing a stray CSS rule can bring back.
Block rules for the whole site our advantage
Allow, restrict to content areas, or forbid every core block — one by one or by category, from a single screen.
Parts that only live inside parent
A card template belongs in the card grid. Mark it “content areas only” and it disappears from the main inserter for good.
Content areas with a guest list grid / flex
Drop a content area into the template, style it with the Bricks layout controls you already use, then name exactly which blocks may go inside and how many.
Usage you can see count
Before you change a template, check how often it is used and on which pages.
Structured content
ACF repeaters per block our advantage
Two team lists on one page hold two separate sets of rows, because the values belong to the block instead of the page. You keep the ACF query loop and tags you already use.
The field types you actually use ACF
Text, WYSIWYG, image, gallery, file, select, checkbox, date, colour, range, and relationships to posts, terms and users with live search.
Brand colours in the editor variables
When your Bricks colour variables come from an options page, they resolve inside the editor too. Clients preview real colours instead of grey boxes.
Open in Bricks, for you only capability
Anyone holding builder rights gets a button straight to the template. Everyone else never learns it exists.
Already using Gutenbricks?
Migration reads the markings you set there, translates them into ClientWP, and rewrites the content on every page that uses the block. One click per template.
Both plugins keep running while you move, so you can go template by template on a live site. Everything is backed up first, and restore mode puts it all back.
- 1
Scan
Every template carrying data from the other plugin is listed, with a preview of what will be translated and what needs your hand.
- 2
Migrate
Editable markings, variants, visibility switches and the template type all come across.
- 3
Content follows
Text, images, buttons, background images and field values are carried over on every affected page.
- 4
Review or roll back
A report per page, and a restore mode that returns templates and content to their previous state.
Let clients build pages without handing them building blocks
A content area is a slot in your template with a guest list. The client fills it with the parts you approved, as many as the page needs, and the grid keeps behaving.
Combine it with block rules and “content areas only”, and the inserter shows a client exactly the pieces that belong to their site.
Card grid — what may go inside
- Card template
--Cardallowed - Paragraphhere only
- Imagehere only
- Columns, Cover, Groupblocked
- Maximum entries6
The client adds cards. Nested layouts are fully supported since the new version — here the guest list simply says which may follow.
One licence, full client control
No feature tiers. The only difference is how many sites you run it on.
Single
For the individual creator shipping one site at a time.
- Every feature
- 12 months of updates and support
- Migration included
Agency
For agencies running a portfolio. Recommended.
- Every feature
- 12 months of updates and support
- Move licences between projects
Unlimited
For enterprises and large agencies that do not count sites.
- Every feature
- 12 months of updates and support
- Priority on support requests
Prices exclude VAT. When a licence lapses the plugin keeps working; updates and support stop. 14-day no-questions refund.
Questions people ask first
Does my client need access to Bricks?+
No. They work entirely in the block editor. Anyone who does hold Bricks permissions gets an extra button in the sidebar that opens the template in the builder.
Is this built for the block editor, or bolted onto it?+
Built for it. Templates register as real blocks with real attributes, the fields use native editor components, and the plugin is developed against WordPress 7 while staying compatible back to 6.3.
What happens when I change a template later?+
Changes apply everywhere immediately, because the block renders the template rather than copying it. Values your client set stay put as long as the field key stays the same, and fields they never touched pick up your new defaults.
Does it work on multilingual sites?+
Yes. Values live on the block and are maintained per translation. Internal link targets are stored as post IDs, so the right language version is resolved on output.
What about performance?+
On the front end Bricks renders the template as usual and ClientWP passes the field values through. No extra markup, no front-end scripts of its own.
Can I try it first?+
Yes. Within 14 days of purchase we refund without asking questions if it does not fit the way you build.
Hand over the site. Keep the build.
Clients who keep their own content current, without a single support call about a broken grid.