Extend Aurelia safely with a child theme

A child theme can change presentation while the parent theme remains a versioned runtime unit. The parent loader uses get_parent_theme_file_path and generated assets are protected; do not shadow inc/, assets/manifest.json, generated assets or languages/. Child code is not a security boundary, so keep it reviewed and narrowly scoped.

Supported extension lanes

1. Prefer documented Hotel Booking hooks, component renderers, public CSS roots and theme filters.
2. Use WordPress template hierarchy and child-first template parts for theme content.
3. Add a child stylesheet after the parent aurelia-style handle and keep its version tied to the active child header.
4. For a Hotel Booking template, use the closed catalog under hotel-booking/, include Hotel Booking Template, Template Package, Template Version and Theme Contract headers, and match the exact current template version. An invalid or outdated candidate falls through to the parent or plugin default. Keep the literal Template Version header intact when updating an override.

Never instantiate plugin services, query tables, calculate totals, inspect Pro licenses or call WPML/Polylang directly. Test a poisoned child fixture, catalogued override, parent fallback and a parent reactivation while checking customizer values, menus and translations remain intact.

Next: update and roll back Aurelia.