# BlueBoxed 1.4.0 Source Audit

Date: 2026-10-16

## Architecture

BlueBoxed is a classic PHP theme with hybrid block-editor support. The PHP template hierarchy renders the frontend; `theme.json`, editor styles, block styles, and patterns provide block-editor integration. Bootstrap 4-style assets, jQuery, Popper, and theme CSS/JS provide interaction and presentation.

## Existing Surface

- Menu locations: `primary`, `footer`.
- Widget IDs: `sidebar-1`, `footer-1`, `footer-2`, `footer-3`.
- Existing Customizer transport: site title, tagline, and header text color.
- Existing theme supports: custom logo/header/background, thumbnails, HTML5, wide blocks, responsive embeds, editor styles, starter content, WooCommerce galleries, and selective widget refresh.
- Existing public template functions and block style/pattern identifiers were retained.

## Verified Defects

- The Customizer module was not required by `functions.php`.
- The Customizer preview script was referenced but absent.
- Bootstrap was enqueued without its Popper dependency.
- The sidebar was registered but not rendered by templates.
- The dark-mode CSS had no complete user-facing control or Customizer wiring.
- The existing release metadata was inconsistent across runtime, RTL CSS, and readme files.
- The duplicate accessibility skip-link hook was removed; the canonical header link targets `#primary`.

## Compatibility-Sensitive Areas

Existing templates, menu locations, widget IDs, theme modification keys, public functions, hooks, CSS classes, and child-theme template overrides must remain available. New settings therefore default to the previous appearance and new layouts are opt-in.

## Missing or Limited Capabilities

Homepage/layout selection, card style selection, sidebar rendering, reading enhancements, richer 404/search UX, WooCommerce coverage, and release verification were limited or absent. No theme-local automated test, lint, browser, or build harness is configured.

## Implementation Approach

Use additive Customizer settings with safe defaults, existing template parts, native WordPress queries, conditional WooCommerce hooks, namespaced CSS variables, and small progressive-enhancement scripts. Do not import demo content or replace the classic architecture.

## Change Classification

- Safe additive: Customizer controls, optional layouts, dark appearance, card classes, sidebar presentation, 404/search enhancements, documentation.
- Existing behavior modification: only bug fixes for disconnected Customizer loading, script dependency ordering, and duplicate skip-link output.
- Compatibility-sensitive: any default layout, menu markup, widget registration, or stored setting change. These remain opt-in.
- Potential breaking: none intentionally introduced.

## Regression Strategy

Validate PHP syntax and editor diagnostics, inspect all public identifiers, verify asset paths and dependency order, test no-content and no-image states, exercise Customizer defaults, check RTL metadata, and perform browser/mobile/keyboard/WooCommerce checks when a runtime harness is available. Unavailable checks remain explicitly reported rather than marked passed.
