This checklist applies the required core Bricks Builder settings that define how Bricks behaves at a system level before any breakpoints, styles, templates, or components are created.
These settings are applied once, verified, and then locked so all downstream Bricks configuration occurs against a known, predictable baseline.
Checklist Objective
Configure and validate Bricks core settings so markup output, editor behavior, and system defaults align with the documented build system.
Scope Boundary
This checklist covers:
- Bricks Builder global/core settings
- Markup and output behavior
- Editor and UX defaults
- Verification of a clean Bricks baseline
This checklist does not cover:
- Breakpoints or responsive behavior
- Global styles or CSS systems
- Templates, components, or layout work
- Performance or caching configuration
Checklist Steps — Bricks Core Settings
1. Verify prerequisites
- Confirm completion of: Bricks Builder — Base Hooks & Config
- Confirm no Bricks settings have been modified yet
- Confirm no templates, styles, or components exist
2. Open Bricks core settings
- Navigate to Bricks → Settings
- Confirm you are viewing the default settings state
3. Review and apply General settings
- Review General settings intentionally
- Confirm no experimental features are enabled
- Do not enable features not explicitly required by the system
4. Review HTML & markup output settings
- Confirm HTML output options match documented standards
- Avoid enabling markup features that introduce unnecessary complexity
- Ensure accessibility‑related defaults remain intact
5. Review editor behavior settings
- Confirm editor UX defaults are acceptable
- Do not customize editor shortcuts or behaviors yet
- Leave advanced editor options at defaults unless documented
6. Save and validate settings
- Tap Save Settings
- Reload WP‑Admin
- Return to Bricks → Settings
- Confirm settings persist correctly
7. Confirm clean baseline state
- Confirm no breakpoints are defined
- Confirm no global styles exist
- Confirm no templates or components have been created
- Confirm no warnings or notices appear
Required Output
- Bricks core settings reviewed and saved
- Settings documented and auditable
- No default or accidental configurations remain
- Stable Bricks baseline established
Pause & Lock
Bricks core settings are now locked. Deviations require documented justification before proceeding.
Proceed to: Bricks — Breakpoints Definition Checklist