This checklist defines the set of required global components used across Bricks templates. Required Global Components are reusable collections of elements that represent shared UI patterns and dynamic groupings that appear in multiple contexts.
These components are created once, saved to the Component Library, and reused without modification inside templates. They are not page‑specific and should not contain hard‑coded content.
Checklist Objective
Create and validate the required set of global components so templates remain clean, consistent, and easy to maintain.
Preconditions
- Bricks — Component Library Definition is completed and approved
- Bricks Builder parent theme is installed and licensed
- Bricks Child theme is active
- No required global components have been created yet
Checklist Steps — Required Global Components
- Identify required components.
- List components that are reused across templates and contexts
- Avoid creating components for single‑use scenarios
- Create component structures.
- Assemble elements into logical groupings
- Use dynamic data sources where appropriate
- Apply consistent styling behavior.
- Ensure components inherit Global Styles where applicable
- Avoid inline or page‑specific styling
- Configure responsive behavior.
- Validate component behavior across all defined breakpoints
- Confirm inheritance and overrides behave as expected
- Save components to the library.
- Use approved naming conventions
- Confirm components are reusable and discoverable
- Validate component reuse.
- Insert components into multiple templates
- Confirm changes propagate consistently
Required Output
- Required global components defined and created
- Components saved using approved naming conventions
- Components validated across templates and breakpoints
- Templates free of duplicated UI logic
Pause & Lock
Once approved, required global components become locked building blocks for all templates and layouts.
Outputs from this checklist are required context for Content Systems — Post/Page Structure .