Previously, moving things like theme styles, classes, variables, templates, breakpoints and other configuration between sites could involve a collection of separate files.
Now, Bricks can bundle everything into a single ZIP file and, more importantly, lets you decide exactly what you do and do not want to move between projects.
A Better Way to Reuse Your Bricks Setup
This is particularly useful if you tend to start new projects from a familiar design system.
You may already have:
- Theme styles
- Global classes
- Colour palettes
- Typography
- Spacing scales
- Variables
- Templates
- Custom breakpoints
- Bricks settings
With the new import/export tools, those can all be packaged together and reused on another site.
The big advantage is that you are not forced to import everything.
You might want your spacing, typography and variables but not the colours. Or perhaps you want the design system without any existing templates.
Bricks now gives you that level of control.
One Export File Instead of Several
The export interface gives you a clear overview of what is available and how many items exist in each area.
You can enable or disable entire sections, then go deeper and choose specific settings within them.
For example, you may decide not to export things like:
- API keys
- WooCommerce settings
- Maintenance settings
- Performance options
- Particular templates or variables
Once you are happy with the selection, everything is packaged into one ZIP file.
That is a much cleaner workflow than managing multiple export files for different parts of Bricks.
Better Control When Importing
The same flexibility carries over to the import side.
When you load an export bundle into another Bricks site, you can see everything inside it and choose which parts you actually want to bring across.
Bricks also checks for conflicts.
If the destination site already has something with the same name or setting, you can choose whether to:
- Keep the existing version
- Replace it
- Exclude that item entirely
This is useful when you are working with an established project rather than a completely blank site.
For example, you may already have a custom colour palette or local fonts that you do not want overwritten, while still wanting to import your spacing system, variables and classes.
A Practical Starting Point for New Projects
For me, this is where the feature becomes most useful.
You could create a master Bricks setup containing the parts of your normal workflow that you use on most projects.
That might include your preferred:
- Typography system
- Spacing variables
- Border radius scales
- Layout variables
- Global classes
- Theme styles
- Common templates
When you start a new site, you import that bundle, remove anything you do not need, and you have a consistent starting point almost immediately.
That is much faster than rebuilding the same setup every time or maintaining a folder full of individual export files.
My Thoughts on the New Import/Export System
This is one of those features that may not look particularly exciting on the surface, but it can make a big difference to day-to-day workflow.
If you only build the occasional Bricks site, it is a nice convenience.
If you build Bricks sites regularly and use your own design system, framework or starter setup, it could save a considerable amount of repetitive work.
The ability to bundle everything into one file is useful, but the real strength is the control over what gets imported and how conflicts are handled.
It means you can create a reusable Bricks starter system without forcing every project to inherit exactly the same settings.
Simple idea, but a very useful one.
