This page defines the terminology and conventions used throughout WordPressBricks.com. Its purpose is to remove ambiguity, prevent terminology drift, and ensure that all system documentation remains precise, repeatable, and authoritative.
Each term includes a short definition, an expanded definition, usage guidance, and notes on where the term originates or is enforced within the system.
Hub Page
Short definition: A global router that presents the full, ordered execution path across all site phases.
Expanded definition: A Hub Page is a high‑level orchestration page that links to major phases or systems in the exact order they are intended to be executed. It does not contain configuration steps or authority. It exists solely to guide navigation and sequence.
Examples:
- Start Here
Correct usage:
- Global execution index
- Ordered, living router
Incorrect usage:
- Landing page
- Tutorial
- Guide
Usage sourcing: Internal documentation model, influenced by long‑form infrastructure runbooks (e.g., DirectAdminVPS.com).
Landing Page
Short definition: Entry point for a single system or phase.
Expanded definition: A Landing Page introduces one bounded system (Planning, WordPress Setup, Bricks Builder, etc.), defines its scope, and routes the reader to its runbooks or atomic checklists. It is authoritative for scope, not execution detail.
Examples:
- Planning
- WordPress Setup
- Bricks Builder
- Content Systems
- Operations
Incorrect usage:
- Hub (global only)
- Category page
- Pillar page (marketing term)
Usage sourcing: Information architecture best practices; adapted for system documentation (not SEO marketing).
Atomic Checklist Page
Short definition: The single source of truth for executing or configuring one specific thing.
Expanded definition: An Atomic Checklist Page defines a complete, authoritative checklist for a narrowly scoped task (e.g., wp‑config constants, Bricks breakpoints, WPvivid backups). These pages are long‑lived, reusable, and referenced by multiple runbooks.
Examples:
- WordPress — Performance & Compatibility wp‑config.php Constants
- Bricks — Breakpoints Definition Checklist
- Softaculous — WP Manager Security Baseline Checks
Incorrect usage:
- Post
- Article
- Guide
Usage sourcing: Internal execution checklists; reinforced by Squirrly SEO governance (authoritative, non‑duplicated sources).
Runbook
Short definition: A controller that defines when and in what order atomic pages are used.
Expanded definition: A Runbook enforces sequencing, prerequisites, and lock points. It references atomic checklist pages but does not redefine their contents. Runbooks ensure execution happens in the correct order.
Examples:
- WordPress Setup 01 — Baseline Installation & Core Settings
- Operations 02 — Backups & Recovery
Incorrect usage:
- Tutorial
- How‑to article
Usage sourcing: Operations and infrastructure disciplines; adapted for WordPress application workflows.
Template (Bricks)
Short definition: A layout controller for a content type.
Expanded definition: In Bricks, a Template defines structure for a content type (Page, Post, Archive, Search). Templates control layout and hierarchy, not reusable UI fragments.
Correct types:
- Page Template
- Post Template
- Archive Template
- Search Template
Incorrect usage:
- Header template
- Footer template
Usage sourcing: Bricks Builder terminology and internal component/template separation.
Component (Bricks)
Short definition: A reusable group of elements.
Expanded definition: A Component is a saved, reusable set of Bricks elements (e.g., Post Meta block) that can be inserted into templates. Components reduce duplication and enforce consistency.
Examples:
- Post Meta
- Footer content block
Incorrect usage:
- Template
- Widget
Usage sourcing: Bricks Builder component model.
Global Styles
Short definition: System‑wide styling rules.
Expanded definition: Global Styles define typography, color variables, spacing, and container behavior that apply site‑wide. They are system configuration, not design experimentation.
Incorrect usage:
- Theme styles
- Page‑level styles
Usage sourcing: Bricks Builder global styling system.
Execution‑Time Activity
Short definition: A real‑world action performed using the documentation.
Expanded definition: Execution‑time activities include installing plugins, running updates, creating content, or performing backups. These actions are guided by the site but are not part of the documentation itself.
Usage sourcing: Internal separation between documentation and operations.
Governance
Terminology changes are rare and deliberate. When a term is updated, all related documentation is aligned to match. This page is the authoritative reference for resolving terminology questions.
Pause & Lock
Once approved, these terminology and convention definitions become locked inputs for all future documentation and updates on WordPressBricks.com.