mrn-base-stack Child Theme

Production scaffold for site-specific front-end work on mrn-base-stack. It keeps the parent upgradeable and inherits parent layout, spacing, accessibility, motion, and rendering behavior.

Site rollout

1. Rename the directory to the site child slug, such as acme-site-child.
2. Change the theme name, text domain, PHP function prefix, and version constant.
3. Keep Template: mrn-base-stack unless the deployed parent directory was deliberately renamed.
4. Add only site-owned styles, assets, and intentional template overrides.

Override surface

• Put CSS overrides in style.css, preferring documented parent variables and stable classes.
• Mirror parent paths for intentional template overrides, such as template-parts/content.php.
• Keep shared content models, fields, API handlers, save behavior, and rendering helpers in the parent stack or shared plugins.
• For custom ACF flexible-content wrappers, retain mrn-content-builder__row and call mrn_base_stack_get_row_spacing_attr_html_for_current_row() when the row array may omit spacing selectors.
• Use mrn_base_stack_get_row_spacing_contract( $row ) only when the complete row data is already available.

See CONTRACTS.md for the required production invariants and release checklist.