Documentation

Theme CSS

HoverCraft keeps its CSS modular and easy to audit instead of building a large framework or design-token layer inside the theme.

• CSS is grouped by real theme areas such as layout, forms, footer, navigation, and WooCommerce when separate files improve maintainability.
• Shared rules stay shared when WordPress, WooCommerce, bbPress, or multiple theme components should use the same visual baseline.
• Customizer settings are compiled into direct theme CSS rather than routed through a broad :root token system.
• Responsive rules generally use the theme's 1200px desktop breakpoint, with shared declarations kept outside media queries when possible.
• Plugin-specific CSS adapts plugin markup to HoverCraft rather than creating a separate design system for each plugin.
• Generated CSS should remain deterministic, with module paths and generator includes kept in sync whenever CSS files are reorganized.

Site-specific overrides should not be added by editing HoverCraft's parent-theme CSS. See CSS Customization for Additional CSS and child-theme guidance.