Pixflow Docs
Pixflow Design documentation for Bricks Builder, with a separate legacy track for the manual web-based workflow.
Welcome to Pixflow.
Pixflow is designed for use with Bricks Builder. It helps designers and developers build faster by providing reusable, production-ready layouts and components that can be customized and scaled across projects.
You can use Pixflow in two ways, with two clearly separated documentation tracks:
- Choose Pixflow Design for the recommended WordPress-first workflow.
- Choose the Web-Based Workflow only if you intentionally want the manual browser-based workflow and do not want the extra features that come with the plugin.
Choose your workflow first
Section titled “Choose your workflow first”If you are not sure which route you should follow, read Plugin vs web-based workflow before going into either section.
That page gives you a quick side-by-side explanation of when the plugin is the right choice and when the legacy web-based workflow still makes sense.
The plugin is now the recommended workflow
Section titled “The plugin is now the recommended workflow”If you are deciding from scratch, start with Pixflow Design.
Pixflow Design is the recommended route because it removes the manual setup the older web-based workflow used to require, while giving each site its own working Pixflow setup.
- resource packs, templates, projects, and workspace state now live in WordPress
- custom mapping for native Bricks is configured per site, so each website can keep its own setup
- new features will be added to Pixflow Design going forward, while the legacy browser-based workflow remains available as-is for users who still need it
Use the web-based workflow only if you do not want to use a plugin
Section titled “Use the web-based workflow only if you do not want to use a plugin”The web-based workflow will remain active, but it is now the legacy workflow.
- framework choice is still available in the web-based workflow and will continue to work
- custom mapping will still be available in the web-based workflow, but it does not affect the plugin
- using the Pixflow Framework through this legacy route still requires full manual setup inside your builder
Start here
Section titled “Start here”- Pixflow Design docs if you want the recommended path
- Plugin vs web-based workflow if you need to compare both routes first
- Web-based manual workflow if you are intentionally staying on the browser-based path