Content Architecture
We use a hybrid approach that balances developer control with editor flexibility.
Overview
| Content Type | Built With | Edited By |
|---|---|---|
| Standard pages (services, blog, etc.) | Bricks templates + components + Gutenberg blocks | Gutenberg |
| Complex/unique pages | Full Bricks builds + components | Bricks |
Bricks Templates
When to use: Blog posts, service pages, team members, case studies—any content that follows a consistent layout.
Setup
- Create a template in Bricks → Templates
- Set conditions (e.g., all posts of type "Service")
- Use dynamic data to pull in content
- Add component zones where editors can insert blocks
Bricks Components
Components are reusable content blocks that editors can add in Bricks or Gutenberg.
Creating a Component
- Build the block layout in Bricks
- Save it as a component
- Create properties for fields like text input
The Editor Experience
Once components are registered as Gutenberg blocks:
- Editors open the page in the standard WordPress editor
- They add blocks from the Bricks Components section
- The component renders with consistent styling—no layout decisions required
This keeps content teams in a familiar interface while enforcing design standards.
Quick Reference
| Task | Where |
|---|---|
| Create page structure | Bricks Templates |
| Build reusable blocks | Bricks Components |
| Edit standard content | Gutenberg |
| Build complex pages | Bricks Builder |