Skip to content

Components

Components let you create reusable elements. Each instance can be customized through properties.

While templates serve as blueprints for pages, components serve as blueprints for a specific element or group of elements, such as a button, card, navigation, or hero section. You can reuse a component throughout your site and customize each instance only where needed.

Any change to the main component automatically applies to every instance of that component. This keeps repeated structures and styles consistent across your website while still letting each instance use its own content, query, variant, or slot content.

A component is a saved element tree with one root element. Bricks stores the component definition separately from the page content. Each instance on a page points to that definition through its component ID and stores only its own instance-specific values, such as property overrides, a selected variant, and slot children.

When Bricks renders the page, it expands the referenced component definition into the page and applies the instance values. If an instance points to a component that no longer exists, that instance is skipped on the frontend.

Create a component from most elements, except Template and Query Filter elements, by right-clicking the element and selecting the Save as component action. You need the Create components builder permission to create new components.

In the popup, enter a name (required), category (optional), and description (optional) for your new component. Click Create to finish creating the component.

Once created, the selected element becomes a component instance. Bricks moves the original element tree into the component definition, replaces the page element with an instance that points to that component, and adds the component to the Components library.

You can access your components from the Components tab, located next to the Elements panel tab.

From here you can add a component to the canvas or structure panel via drag and drop or click, the same as any other element.

In Bricks 2.4, you can also manage components from the Builder Browser. Open the Browser from the folder icon in the builder toolbar, then select Components.

You can perform the following actions from the Components tab:

  • Import: Import component JSON or ZIP files from another installation.
  • Export: Export all components of your site as a JSON file. To export a specific component, hover over it and click the export action icon.
  • Delete: Click the delete icon to enter delete mode. Once activated, hover over the component you want to delete and click the delete icon.
  • Edit: Open the component properties panel from the component action icons.
  • Duplicate: Create a copy of an existing component.
  • Use in block editor: Toggle whether a component can be used as a block in the WordPress block editor, when the block editor integration is enabled.

Component actions are permission-gated. Inserting components, creating components, deleting components, editing component definitions, setting instance property values, and importing/exporting components are separate builder permissions.

Imported components with duplicate IDs are skipped. Exported component JSON also includes global classes used by the component’s element settings and class properties.

The Browser’s Components view gives you a wider management screen for existing components.

From there you can:

  • Search components.
  • Filter by category.
  • Show and filter components by element type (Bricks 2.5).
  • Filter by usage: all usage, used on current page, used elsewhere, or unused.
  • Switch between grid and list view.
  • Import component JSON or ZIP files.
  • Edit, duplicate, export, delete, or generate a screenshot for a component.
  • Generate screenshots for the currently filtered component list.

Generating component screenshots requires the Edit components builder permission. Component import and export require the Import/export components builder permission. The Used elsewhere filter only shows components that are not used on the current page but are used on another page or template.

Component screenshots are enabled by default on new installations under Bricks > Settings > Templates & components. Disable the setting to stop automatic and manual generation and hide stored local thumbnails. Disabling it does not delete existing screenshot files. Use Delete screenshots in the same settings section to remove all generated component screenshots.

Since Bricks 2.5, the Components browser can show each component’s element type and filter the library by it. The element type is the component’s root, its outermost element, such as a Section, Container, Block, Div, or Heading. Check it before inserting a component to see what kind of element you are adding.

Element types are hidden by default. To show them, click More (the three-dot icon) in the toolbar and enable Show element type. Bricks remembers this choice in your current browser.

More menu in the Components browser with Show element type enabled. Element type labels appear on the component cards and the Element type filter shows All (25).

With the setting enabled:

  • Each component shows its element type as a label in the top-left corner of the card in grid and masonry views, or at the end of the row in list view.
  • An Element type dropdown appears in the toolbar. Select a type, or choose All to remove the type filter.

Components browser in list view with the Element type menu open, listing each type with its component count, and element type labels at the end of each row.

The menu lists the types available in the current results, with a component count for each. Search, category, and local usage filters narrow these options and counts. For example, select your page-section category, then choose Section to find components whose outermost element is a Section.

Changing the type returns to the first page of results. If another filter removes every component of the selected type, the type filter returns to All. Disabling Show element type also resets the filter to All, so a hidden filter never narrows your results.

Remote components use the element type supplied by their source site. If that information is unavailable, the component has no type label and appears under All, but not under a specific type.

Since Bricks 2.5, use Sort by in the Components browser toolbar to choose Newest, Oldest, Title A–Z, or Title Z–A. Newest is the default. Date sorting uses creation dates, including for remote components.

Click Import in the toolbar to import component JSON or ZIP files into the local library. This action requires the Import/export components builder permission. When an import switches you from a remote source to the local library, the usage filter is cleared so it does not hide the imported components.

Components browser with the sort menu open and arrows pointing to the sorting control and Import button.

Since Bricks 2.5, the Components browser has a Categories sidebar. It lists All components, Uncategorized, and each category with its component count. Click a row to filter the library. Drag the sidebar edge to resize it, or use the arrow button to collapse it.

Each component belongs to one category at a time. You can assign categories in three ways from My components:

  • Drag and drop: Drag a component card onto a category in the sidebar. If the card is selected, Bricks moves every selected component, including selections on other pages. An unselected card moves on its own. Drop onto Uncategorized to remove the category. If the sidebar is collapsed, hold the dragged card over the expand button to open it.
  • Assign category: Select components with their checkboxes. In the selection toolbar, click Assign category, choose a category, and click Apply. To create a category, type a new name in the picker and choose the Create "name" option before you apply it.
  • Create category: With components selected, enter a name in the New category name field below the category list and click Create category. Bricks assigns the selected components to it. If a category with the same name already exists, ignoring letter case, Bricks uses that category instead of adding a duplicate.

Each assignment is a single undo step. Click the info icon in the sidebar header to show a short version of these instructions.

Categories exist only while at least one component uses them. If you move the last component out of a category, the category disappears from the sidebar.

Category labels are hidden on component cards by default. To show them, open the More (three dots) menu in the toolbar and enable Show category. Bricks stores this choice in your browser. Click a category label on a card to filter the library to that category.

Assigning categories requires the Edit components permission. Remote libraries and users without that permission can browse categories, but cannot change them. Save in the Builder to keep the changes.

Components browser with two selected components. The Categories sidebar shows counts, the help text, and a New category name field filled with Hero sections above the Create category button.

Assign category picker with Uncategorized, Atelier North, and Studio essentials options, plus Cancel and Apply buttons.

Below the name of the component is the instance count. For example, Instances: 3/6 means the component is used three times on the page you are currently editing and six times across the site.

In the Components panel, hover over the component and click the globe icon to see all instances of this component on the current page, plus a list of other pages where the component is used.

In the Builder Browser’s Components view, click the instance badge to open the usage popover. The popover separates Current page instances from Other pages. Current-page items take you to the matching instance in the builder. Other-page items open the matching page or template in Bricks in a new browser tab.

Every time you add a component to a page, Bricks creates an instance of that component.

Changes to the main component automatically reflect in all instances of this component throughout your site. Instance-specific property values, variants, and slot content affect only the selected instance.

The following screenshot shows three instances of the same Card component:

To view and edit the elements of the main component, which is the source of truth for all its instances, right-click any instance and select Edit component.

Alternatively, click the gear icon in the control panel header of the instance to enter component editing mode:

You are now editing the main component, indicated by the purple color in the control panel header.

As mentioned before, any change you perform on the main component applies to all instances of this component on your site.

The main component header contains the following actions:

  • Description (info icon): Show or hide the component description.
  • Category (folder icon): Show or hide the component category.
  • Block editor (WordPress icon): Show or hide block editor settings when the component is enabled as a block.
  • Variants (drop icon): Open the Variants panel.
  • Properties (box icon): Open the component properties panel.
  • Instance (arrow icon): Exit component edit mode and return to the instance you were editing before, or to the Components library. Pressing the Escape key also exits the main component.

When editing the main component, you can see and edit all elements of this component in the structure panel:

To edit the title of a Card component, select the Heading element inside the component and change its text to Just a card.

All instances of the Card component automatically reflect this change:

This is useful for shared structure and design. The real power of components comes from combining shared structure with properties that can be customized per instance.

Since Bricks 2.5, use Revisions on a component row in the Components panel, or on a component in the Browser, to open that component’s earlier versions. Component revisions include a rendered preview and changed values named by element label. Restoring one component keeps unrelated components at their current versions. See Global data revisions for permissions, deleted-item recovery, and the behavior inside drafts.

Properties let you expose controls for customization on each instance.

For example, a Card component can expose a card title property and a card image property. Each Card instance can then use different content while still sharing the same component structure and styling.

To connect a property directly to a control, follow these two steps:

  1. Create a property.
  2. Connect that property to one or more compatible controls inside the component.

Creating and editing property definitions requires the Edit components builder permission. Setting property values on an instance requires the Edit properties (Instance) permission.

To access the properties panel, select any instance of the component you want to edit. Then click the edit icon in the properties control panel on the left-hand side:

If there are no instances of the component on the current page, go to the Components library, hover over the component, and click the edit icon.

If you are already editing the main component, you can access the Properties panel by clicking the box icon in the panel header.

You can choose from these property types and connect them to compatible controls inside your component:

Property typeConnectable toExample
TextText and textarea controlsHeading or Basic text
Rich textRich text controlsRich text or Accordion content
IconIcon controlsIcon or Icon Box element
ImageImage controlsImage or Logo element
Image galleryImage gallery controlsImage gallery or Carousel element
LinkLink controlsButton or Heading link
Select (@since 2.0)Select, text, textarea, and rich text controlsHTML tag, Button style
Toggle (@since 2.0)Checkbox and toggle controlsHide element toggle
Query loopQuery controlsLayout elements
Repeater (@since 2.5)Native repeater controls and Array queriesTestimonials, FAQ or card lists
Global classes (@since 2.0)Global classes controlsElement global classes

The property name is mandatory. Choose a descriptive name, especially for complex components with many properties.

The property description is optional, but it helps other builders understand how the property should be used.

The property group is optional and helps organize properties inside the instance panel.

The default property value is optional. It is used when an instance has not set its own value. If an instance value is cleared or reset, Bricks removes the override so the default value can apply again. Repeater properties distinguish an intentionally empty row list from a reset; see instance rows and defaults.

Since Bricks 2.5, Create properties from content creates and connects several properties in one step. Use it after building a component’s content, such as a card with a heading, image, and button.

Open the component’s Properties panel and click Create properties from content. Bricks detects these controls in the main component:

ElementDetected content
Heading, Basic TextText
Rich TextRich text
ImageImage and alternative text
ButtonText and link
IconIcon

The scan stops at nested component instances. Edit a nested component’s own properties separately.

  1. Review the detected rows and deselect content that should stay fixed. Hover a row to locate its element on the canvas and in the Structure panel.
  2. Give each property a clear name. Open its More menu to edit its description, default value, and group. The element’s existing content supplies the initial default.
  3. Drag rows to change their order. Use Groups to create or edit groups, then assign rows with the group selector or drag them into a group.
  4. Click Create and connect to apply the selected properties and their connections. If you are only editing existing properties, the button reads Save.
  5. Save in the Builder, then select an instance to customize the new properties.

Search and group filters help narrow the list. Select all applies to the unconnected rows in the current search and group. Existing connected properties retain their connections while you edit their names, defaults, descriptions, groups, or order.

Closing and reopening Groups keeps your pending changes while you remain in the creation panel. Cancel or the back arrow leaves the creation panel without applying the pending changes.

Create properties panel with six selected properties, condition icons, and the Create and connect button.

For newly selected content, enable Hide if empty from the row’s condition icon or More menu. This requires access to element conditions. Bricks adds a connected Dynamic data → is not empty condition to the element. You can inspect or edit it in the element’s Conditions panel afterward.

For a Button, both its text and link must resolve to non-empty values. Image alternative text is not used to decide whether an Image should render. If the element already has multiple condition groups, the presence check is added to each group so the existing OR logic is retained.

The check uses the resolved property value, including its default. Clearing an instance’s text or rich-text value restores the default. If that default contains content, the element stays visible. For an optional text field, clear its property default too, then enter text only on the instances that need it.

Rich-text markup such as <p><br></p> still counts as content for this comparison. Remove the markup as well if the field should be empty. Check the frontend result: element conditions keep elements available for editing in the Builder.

After creating a property, connect it to the control that should be editable on the instance.

Unconnected properties show a broken-link icon next to their name:

To connect a text property to a Heading element:

  1. Edit the main component.
  2. Select the Heading element inside the component.
  3. Find the text control.
  4. Click the purple + property icon.
  5. Select the property you want to connect.

Clicking the + icon reveals a list of properties that can connect to this control:

Once selected, the control shows the name of the property that is connected:

When an instance changes that property, Bricks applies the instance value to every connected control. For nested components, Bricks can also connect a child component property to a property from the parent component.

Most connected controls can use one non-class property. Global class properties are the exception and can be combined with other class property connections.

To disconnect a property from a setting, click the connected property setting, hover over the connected property name, and click the unlink icon.

Since Bricks 2.5, you can disconnect a property everywhere it is used inside the main component:

  1. Open the component’s Properties panel.
  2. Find the connected property and click Disconnect all on its row.
  3. Confirm the dialog, then save in the Builder.

The property, its default value, and its group remain available, so you can connect it again later. The action removes that property’s control connections and connections forwarded to nested component instances inside the main component. Other properties keep their connections.

Disconnected controls return to their own saved settings. Inline references such as {prop.title} are replaced with the property’s default value, rather than the value of the instance you happen to be editing. Review the affected content and conditions before saving, especially if the component’s instances had different values.

If Bricks cannot safely replace a reference, it leaves the component unchanged and identifies the reference to resolve first. Fix or remove that reference, then try Disconnect all again. Choosing Cancel in the confirmation dialog also leaves the connections intact.

The FAQ items property row with the Disconnect all button highlighted and its tooltip visible.

Since Bricks 2.5, a Repeater property lets each component instance manage a list of structured items. Use it for FAQs, testimonials, pricing features, or cards whose layout stays the same while their content and number of items change.

A repeater property can supply an element’s native repeater control or an Array query loop inside the component.

  1. Edit the main component and open Properties.
  2. Create a property with Type set to Repeater and name it Cards.
  3. Under Fields, add Title (Text), Image (Image), and Link (Link).
  4. Use Add item in the default-value editor to enter the initial rows.
  5. Save the property, then connect it to the content it should control.

Supported field types are Text, Rich text, Image, Link, Select, Toggle, and Repeater. For Select fields, enter one option per line. A nested Repeater contains another set of fields; Bricks supports two repeater levels in total.

Cards has Title, Image, and Link fields and two default items, Lake Bohinj and Soča Valley.

Use a query loop to design each item with ordinary Bricks elements.

  1. Inside the main component, create a Block containing a Heading, Image, and Button. This Block is the layout for one card.

  2. Enable Query loop on the Block.

  3. Open the property connection control for its Query and select Cards. Bricks supplies an Array query from the repeater rows.

    The Card Block’s Query is connected to Cards, and two destination cards appear on the canvas.

  4. Select each child element and use its property connection control to connect the Heading text to the Title field, the Image to the Image field, and the Button link to the Link field of Cards.

    The selected destination Heading is connected to Cards.Title and displays Lake Bohinj in the first card.

  5. Exit component editing and edit the Cards rows on the instance.

The loop repeats the Block for each row. Compatible Array-query options, including offset, results conditions, and pagination, remain available. A repeater property can supply multiple queries, but each query takes its rows from one source property.

Each field exposes a copyable Field tag. For a field whose key is title, the tag is:

{query_array @key:'title'}

Use the copied tag inside the matching repeater query loop. It also works in mixed text, such as Read more about {query_array @key:'title'}. Copy the actual tag from the field editor: changing a field’s display name does not change its saved key.

Image and Link field tags include the field type so Bricks can resolve their structured values in compatible image and link controls:

{query_array @key:'image' @field-type:'image'}
{query_array @key:'link' @field-type:'link'}

For general Array-query syntax and nested loops, see Query Type: Array.

For elements that already have an item list, such as Testimonials, connect the property directly to that repeater control.

To start from existing content, open the repeater’s property connection menu and create a new property there. Bricks creates supported fields, default rows, and mappings from the native items.

To use an existing Repeater property, connect it to the item list, then open the visible template item and connect its compatible controls to the repeater fields. Field names do not need to match the element’s control names. For example, a field named Quote can supply the testimonial content control.

Unconnected controls keep the fixed values from the first native item. Unsupported field types, such as Number and Icon, can remain fixed this way. Auto create and populate properties adds missing supported fields and connections without replacing existing mappings or row values.

Select an instance to add, edit, duplicate, remove, or drag rows into a different order. These changes affect that instance only.

An instance without its own rows uses the property’s default rows. Deleting every row creates an intentionally empty list; it does not restore the defaults. Reset the property to inherit its defaults again. Repeater properties also support row editing in Components as Blocks.

Change fields and forward nested properties

Section titled “Change fields and forward nested properties”

Renaming a field keeps its key and existing values. Deleting a field removes it from the editable schema, so update copied tags and nested connections that reference it.

Changing a saved field to an incompatible type creates a new key and clears its default. Existing instance values are not converted. Changes between Text, Rich text, and Select preserve the field key.

When forwarding a Repeater property through a nested component, the parent and child definitions must have matching field keys and types, including nested fields. Creating the parent property from the child’s connection control copies its field definitions. Disconnect the forwarding before making incompatible changes to either definition.

Since Bricks 2.5, insert a component property into dynamic-data-enabled content with {prop.key}. Combine a property with surrounding text, use it in a condition, or reuse it in a supported field without connecting the entire control to that property.

Open the main component’s Properties panel and edit a property. Its Reference key identifies it within that component. Use the copy button to copy its tag, such as {prop.title}.

Choose the key when creating the property. It must be unique within the component and contain lowercase letters, numbers, and underscores, starting with a letter or underscore. Once created, the key is read-only. Renaming the property label does not break its references.

The Title property has the reference key title and a button to copy its tag.

For a promotion component with Text properties using the keys title and price, enter this in a Basic Text element inside the main component:

Book {prop.title} for {prop.price}.

Each instance supplies its own title and price. An instance without an override uses the property default. Clearing a text override restores the default; 0 and Toggle false remain explicit values.

In supported text controls, type {prop. to see property suggestions, or select a property from the dynamic data picker. Bricks also flags incomplete, missing, or unsupported references in the Builder.

Use a full Image or Link property in a compatible image or link control. To use a single value in text, select a supported field:

PropertyExampleValue
Image{prop.photo.url}Image URL
Image{prop.photo.id}Attachment ID, when available
Image{prop.photo.alt}Image alternative text
Link{prop.cta.url}Resolved link URL

Replace photo and cta with your actual reference keys. A whole structured Image or Link value cannot be printed as ordinary text.

For a conditional offer label, add a Dynamic data element condition, enter {prop.offer}, and compare it with the value you want to match. The condition uses the current instance’s resolved value, including its default when no override is present.

Property keys belong to their component. The same key can exist in different components without sharing values. A reference outside a component instance cannot read a property from an unrelated component on the page. To pass values into a nested component, connect its properties to the parent properties.

Property references are intended for content and supported settings. They do not substitute editable values into CSS, JavaScript, executable PHP source, or executable HTML attributes such as onclick and style.

A Code element inside a component can render property tags in its HTML output when Execute code and Parse dynamic data are enabled. PHP code can read typed values with bricks_get_component_property().

Deleting a property can leave unresolved references. Review the locations shown in the deletion warning and replace or remove those references before saving. Unlinking a component replaces supported references with resolved instance values; Bricks stops the unlink operation when a reference cannot be replaced safely.

Select a component instance to customize the properties exposed by the main component. Properties used through control connections or dynamic data references appear in the instance controls.

For example:

  • One Card instance can use a custom heading.
  • Another Card instance can use a different image.
  • Another Card instance can keep the default property values.

Instance changes do not affect the main component or other instances. They only affect the selected instance.

Components are compatible with query loops. You can enable a loop on the component root or place a query loop inside the component.

In the following screenshot, the Card component is used inside a loop. The Card title uses the post_title dynamic data tag and the Card image uses the featured_image tag to render the post title and featured image of the loop results.

There is also a Query loop property type, which allows each component instance to customize an in-component query loop.

Variants give one component more than one look. All variants share the same content, structure, and properties. Only the styles differ. Each instance then picks the variant it uses, so a page that needs a different look does not need a second component.

Examples:

  • Primary and secondary button styles.
  • Card layouts with different spacing.
  • Light and dark versions of the same component.
  • A standard and a more prominent page hero.

Variant styles are saved on the component definition. The selected variant is saved on the instance.

  1. Edit the main component.
  2. In the control panel header, click Variants (drop icon). The tooltip shows how many variants the component has.
  3. The first row is the base look. Naming it is optional. Without a name, it shows as Base.
  4. Click Add Variant. Bricks adds a variant named Variant 1 (the next one is Variant 2, and so on) and makes it the active variant. Rename it in place, for example to Prominent.
  5. Close the Variants panel.

Variants panel of the Page hero component in edit mode, with the Base row, a variant named Prominent, and the Add Variant button.

With more than one variant, drag a variant by its handle to change the order.

When you close the Variants panel, a Variant select appears at the top of the control panel. It shows which variant you are styling. It is hidden while the Variants panel is open.

With a variant selected, select any element of the component and change its style settings, such as background, spacing, or typography. Bricks saves these settings for the selected variant only, including settings on other breakpoints.

Content, structure, and properties stay shared. If you edit a text or add an element while a variant is selected, the change applies to every variant.

To edit the base look again, set the Variant select back to Base.

A variant stores only the settings you change while it is selected. Everything else comes from the base.

When you later change the base, the change reaches every variant that does not set the same setting itself. For example, if you center the content in the base, both looks are centered, because the variant does not set the alignment. If you change the title color in the base, a variant that sets its own title color keeps it.

Select an instance on a page. If its component has variants, a Variant select appears above the properties. Leave it on Base or pick a variant. The choice applies to this instance only. Other instances of the same component keep their own variant.

When a component is enabled as a block, the component block in the block editor has the same Variant select.

Page hero instance selected in the Builder, with the Variant select above Properties set to Prominent and the dark Prominent look on the canvas.

Open the Variants panel and click the trash icon next to the variant. After you confirm, Bricks removes all styles of that variant, and instances that used it switch back to the base.

  • Use a variant when instances need a different look of the whole component, with several style changes that belong together.
  • Use a property when each instance needs its own value, such as a text, an image, a link, a query, or a toggle. See Properties.
  • Use a global class when the same style should apply to elements in different components and pages. To let each instance choose classes, use the Global classes property.

The following patterns use component properties to customize each instance. They are useful when you want instance-level choices without creating formal component variants.

Bricks 2.0 introduces a Hide element feature, available by clicking the eye icon in the element panel header or from the context menu.

You can create a Toggle property and connect it to the Builder: Hide element and/or Frontend: Hide element controls to show or hide elements inside your component on an instance basis.

The frontend hide control is not just a visual CSS helper. Hidden frontend component elements are excluded from the frontend render/settings output.

The Global classes property type, available since Bricks 2.0, lets you create styling variations through global classes. Assign a collection of default and/or custom classes on the instance for any element of your component.

In the following example, we create a global classes property with the custom options Small, Medium, and Large. Each option has a different global class assigned to it. You can also assign multiple classes.

Once you have created the new Heading size property, connect it to the global classes control of the element of your choice. In this example, it is connected to the Heading:

Once connected, the property becomes available on every instance. In the following screenshot, the Large option adds the global class prop-text-lg to the Heading element of the instance.

You can connect as many global class properties to an element as needed.

When defining custom options, you can leave the label empty to show the selected global class names instead. User-friendly labels are usually the preferred option.

You can change the global class selection of an option any time. The newly selected global classes are added to the instance if the corresponding option is selected.

If you are not working with global classes, you can use the Select property type to define custom options that users can choose from, then apply those class names through an attributes control inside the component.

Next, create a Select property with class name options:

Once you create and connect this select property to the attributes value, it becomes available on the instance. You can then apply the local class with one click, which adds the color-red class to the Heading element inside the component.

You can also connect a Text control to the attributes value if you want users to enter plain class names directly instead of choosing from predefined options.

The Slot element lets a component define a placeholder for instance-specific children. Add a Slot inside the main component where instance content should appear, then add elements to that slot from a component instance.

A Slot element in the main component is a placeholder. When you select an instance, Bricks exposes virtual slot areas where you can add instance-specific children. Those children are saved on the instance and rendered inside that slot for that instance only.

To add a slot, edit the main component and select the element that should hold the instance content. While you edit a component, the Elements panel shows the Slot element in the Component group. Click it to add the slot. To name the slot, double-click it in the Structure panel, for example Actions. Every instance shows this name for its slot.

Elements panel in component edit mode with the Slot element in the Component group.

To fill a slot, select the instance. In the Structure panel, select its slot row and click an element in the Elements panel, drag an existing element onto the slot row, or right-click the slot row and select Paste. Elements in a slot are regular elements of the page, so you can edit and style them like any other element.

Structure panel with a component instance, its Actions slot and two elements inside the slot.

  • A slot adds no wrapper element. Bricks renders only the instance’s elements in its place.
  • An empty slot outputs nothing. A slot has no default content.
  • If you delete a slot from the main component, the elements that instances added to it are no longer rendered.
  • Component blocks in the block editor do not support slots. See Components as Blocks.

Components can be used as blocks in the WordPress block editor if the Gutenberg integration is enabled.

To use a component as a block:

  1. Enable the Gutenberg integration in Bricks settings.
  2. Enable the component for the block editor.
  3. Configure the component block title, category, icon, and preview image.
  4. Insert the component from the WordPress block editor.

Block editor controls are generated from component properties that are connected to controls inside the component, including direct and nested property connections.

For the full setup, see Components as Blocks.

To unlink an instance from a component, right-click the instance and select the Unlink component icon under the Edit component menu item.

Once unlinked, the instance is no longer tied to the main component and can be edited independently, like any other element.

Global elements are deprecated since Bricks 2.0. You cannot create new global elements, but you can convert existing global elements to components from Bricks > Settings > General > Global elements.

These details explain how Bricks stores and renders component instances:

  • Component definitions live in Bricks component data, not as ordinary copied children on every page instance.
  • A component must have one root element. The root element ID is the component ID.
  • A page instance references its component through the component ID.
  • Instance-specific property values are stored on the instance by property ID.
  • Component properties are definitions. A property exposes an instance value when it is connected to compatible controls or used through a supported dynamic data reference inside the component.
  • Variant selections live on the instance. Variant-specific settings live on the component definition.
  • Slot children live on the instance, not in the main component definition.
  • A missing component reference should be treated as invalid. Bricks skips instances whose component definition no longer exists.
  • Components are best for repeated design patterns.
  • Properties are best for values that change per instance.
  • Use categories to keep the component library organized.
  • Use descriptions to make components easier to understand for teams and future maintenance.
  • Use variants for design presets.
  • Use slots for flexible inner content.
  • Use component properties instead of duplicating components for small content differences.
  • Export important components before deleting or heavily changing them.
  • Keep components simple and focused. Very large components can become harder to maintain.