This checklist validates Bricks Builder readiness and applies the required child theme hooks that must exist before any Bricks settings, breakpoints, styles, templates, or components are configured.
All performance and compatibility constants are handled separately as a reusable atomic checklist. This page focuses only on prerequisites that ensure Bricks starts from a clean, known‑good state.
Checklist Objective
Confirm that the Bricks Builder environment is present, active, and clean so Bricks system configuration can begin without rework.
Scope Boundary
This checklist covers:
- Verification of Bricks Builder and child theme readiness
- Application of required child theme hooks
- Validation of a clean Bricks starting state
This checklist does not cover:
- wp‑config.php performance or compatibility constants
- Bricks Builder core settings
- Breakpoints, global styles, templates, or components
- Visual layout or design work
Checklist Steps — Base Hooks & Config
1. Verify prerequisites
- Confirm completion of: WordPress Setup 04 — Theme & Builder Installation
- Confirm the Bricks child theme is active
- Confirm no Bricks settings or templates exist yet
2. Verify wp‑config.php constants readiness
- If performance and compatibility constants have not been applied, pause here and complete: WordPress — Performance & Compatibility wp‑config.php Constants
- Return to this checklist only after that page is completed and locked
3. Prepare Bricks child theme for hooks
- Open: wp‑content/themes/<bricks‑child‑theme>/functions.php
- Confirm the file exists and is writable
4. Apply required child theme hooks
- Apply only the hooks defined in: Bricks — Required Child Theme functions.php Hooks
- Do not add experimental, optional, or undocumented code
- Save functions.php
5. Validate hook execution
- Reload the site frontend
- Reload WP‑Admin
- Confirm no PHP warnings or fatal errors occur
6. Confirm clean Bricks starting state
- Open Bricks → Settings
- Confirm Bricks system checks reflect a compatible environment
- Confirm no settings have been imported or modified
- Confirm no breakpoints, styles, templates, or components exist
Required Output
- Bricks Builder and child theme verified as active
- Required child theme hooks applied intentionally
- No PHP or runtime errors present
- Clean, unconfigured Bricks environment confirmed
Pause & Lock
Base hooks and prerequisite validation are now locked. Do not modify child theme hooks during subsequent Bricks configuration unless explicitly required and documented.
Proceed to: Bricks Builder — Core Settings