Theme Framework Integration

A site-specific child theme inherits shared structure from Theme Framework and owns only the presentation decisions its website genuinely needs.

The Relationship at a Glance

A Practical File Structure

A child theme adds files only for responsibilities it owns. It does not need a local copy of every parent template or function. A consistent project structure keeps setup, assets, and focused overrides easy to locate.

client-site-theme/
├── style.css
├── style.min.css
├── functions.php
├── assets/
│   └── css/
│       └── editor-style.css
├── lib/
│   ├── init.php
│   ├── setup.php
│   └── functions-assets.php
└── theme.json          # only when the site has real overrides

Declare the Parent Theme

The WordPress Template header connects the child to Theme Framework. WordPress then applies its normal parent-child loading, template resolution, asset, and configuration rules.

/*
Theme Name: Client Site Theme
Template: theme-framework
Text Domain: client-site-theme
*/

Prefer a Focused Hook to a Copied Template

When the framework exposes the right action or filter, a child theme can change one decision while continuing to inherit the shared renderer and later framework improvements.

namespace ClientSite\Theme;

function modify_entry_meta_items( $items, $post_id ) {
    unset( $items['author'] );

    return $items;
}

add_filter(
    'theme_framework_entry_meta_items',
    __NAMESPACE__ . '\\modify_entry_meta_items',
    10,
    2
);

How WordPress Resolves the Final Site

1. Theme Framework supplies parent templates and shared presentation contracts.
2. The child theme registers its own setup, assets, actions, and filters.
3. A matching child template takes precedence only where the site needs different markup.
4. Supported parent and child theme configuration is merged by WordPress.
5. The editor and frontend receive coordinated framework and site-specific styles.

When should a parent template be copied?

Only when the site must change the template's markup or rendering sequence. Smaller changes should use actions, filters, configuration, or focused child-theme functions.

What does not belong in the child theme?

Business workflows, data processing, and project application logic remain plugin responsibilities. The child theme owns presentation and theme-side integration.