Templates are a central feature of Bricks. There are different types of templates. A template can contain a single section (such as your website header, footer, hero section, etc.) or an entire page (single blog post layout, archive pages, search results page, error page, etc.).
You can create your own templates or browse dozens of pre-designed templates from the Template Library by clicking the Templates (folder) icon in the builder toolbar.
This ever-growing collection of pre-designed templates can be inserted with a single click right within the builder. All images are royalty-free and can be used in your own and your client projects.
When starting out with Bricks inspecting a template is a great way to learn how a certain layout is structured.
You can view, create, import, and export your own templates also from the WordPress dashboard:
This also provides a great overview of where on your site a template appears (Template Conditions), the Template Type, plus any template metadata you’ve added (Templates Bundle, Template Tags)
Let’s quickly go over those template-specific terms:
Template conditions determine where on your site a template appears.
For example, the Archive template in the screenshot above is used on all author and date archive pages. The Single Blog Post template is responsible for all your posts. Both were set using template conditions.
If no template condition is set Bricks will show templates of a certain Template Type by default on the frontend of your website, such as header and footer templates.
View the table below to see which template types are picked up by default.
To set template conditions when editing a template in the builder click the Settings (gear) icon in the builder toolbar, then go to Template Settings > Template Conditions:
TIP: To disable the use of default templates go to Bricks > Settings and select the Disable Default Templates option.
Setting a template type is required for any template.
Assigning the most suitable template type helps you easily filter large template libraries and it tells Bricks to determine if a certain template should be shown on the frontend of your website by default. This is if you haven’t disabled this option as described in the tip above.
|Template Type||Description||Used By Default|
|Header||Set for any template that contains your website header (logo, nav menu, etc.)||Yes|
|Footer||Set for any template that contains your website footer (copyright info, footer nav menu, etc.)||Yes|
|Content||Set for any template that contains the main content. Such as a single blog post template.||No (it’s unique)|
|Section||Set for any template that contains a single section. Such as a hero section, contact section, etc.||No (it’s unique)|
|Archive||Set for any template that contains your website archive. Can be broken down via Template Conditions into author, date, category/tags archive pages.||Yes|
|Search Results||Set for the template that you want to use to display your search results page.||Yes|
|Error Page||Set for the template that you want to use as your 404 error page.||Yes|
Template Bundles & Template Tags
Those two custom template taxonomies that can be used to group templates together. They are completely optional.
For example: Community Templates use Template Bundles to group individual templates of the same website design (Milo, Sizzle, etc.) together. Feel free to use template bundles in any other way.
Template Tags are simple tags. The “My Templates” screenshot above uses template tags such as “Dark” and “Light”. Again, completely optional, but often super useful. Especially as your template library grows.