Docs/Bricks Builder

Bricks Builder

Bricks-specific sync coverage for templates, components, settings, styles, and builder metadata.
Updated June 2026·WPChangeSync 2.0

Bricks remains first-class

WPChangeSync grew out of BricksSync, and Bricks still has deep coverage. WPChangeSync includes handlers for Bricks templates, components, settings, global classes, global elements, global queries, theme styles, colors, typography, breakpoints, variables, custom code, custom CSS, custom fonts, custom icons, icon fonts, sidebars, element defaults, element manager, style manager, pseudo classes, and Adobe fonts.

Optional dependency

Bricks is no longer required for the plugin to run. Bricks integrations become available when the relevant Bricks data exists, while WordPress and third-party integrations remain usable in builder-agnostic installs.

Template and component moves

Use the Library to export selected templates/components, push them to remotes, or include them in workflows. Use versioning/rollback where available before replacing production builder data.

Bricks CLI examples
wp wpchangesync templates listnwp wpchangesync templates export --id=123nwp wpchangesync components listnwp wpchangesync components show hero-card

Reference checklist

Bricks-oriented automation can use template and component CLI commands for listing, exporting, importing, versioning, and restore flows.