A shared WordPress foundation for content and tools.

The problem: one site, different page experiences

The project combines a marketing homepage, a blog, ordinary pages, and a custom post type for frontend utilities. Its child theme sits on a block-theme parent. In this setup, ordinary content could be rendered through a different template path from the custom homepage. The resulting experience made a shared header and consistent navigation harder to maintain.

The editorial expansion introduced a second concern: readers needed more than a long list of articles. Guides, downloadable resources, working utilities, and supporting images needed clear destinations and links. The task was to give those content types a coherent presentation while keeping them editable through WordPress.

The implementation

The child theme uses WordPress’s template_include filter to select its PHP templates. Explicitly assigned custom page templates remain supported. Standard posts use the article template; other singular content uses a shared page template unless a dedicated template is assigned.

This matters because a visual header fix alone would not address a different template being selected underneath it. The routing rule makes the page shell explicit, and the header remains a single place to change navigation. The tradeoff is that the PHP child theme owns this presentation layer; future changes to parent block templates do not automatically redesign these pages.

Editorial controls and resource architecture

The shared article layout provides readable line length, responsive images, and clear separation between prose and code. The blog index uses cards with featured images and pagination. These are presentation decisions intended to improve comprehension; their effect on engagement still needs production analytics and user observation.

What the evidence establishes

Inspect the local response-time record or explore the resource collection. These artifacts make the scope concrete without turning local measurements into unsupported business outcomes.

What another team can take from this

Start with template ownership before changing individual pages. When a CMS mixes custom templates, parent-theme behavior, and different content types, inconsistent rendering can be a structural issue. Trace the route, identify the responsible template, and establish a common shell before adding more one-off CSS.

Next, keep content relationships explicit. A guide should link to the tool or resource it explains, and that destination should give the reader enough context to use it. Finally, separate editorial checks from performance claims. A word-count gate is useful for an agreed publishing requirement, but it does not establish authority, accuracy, accessibility, or commercial impact.

For a project with similar constraints, our design systems and frontend engineering service starts with a representative journey and a clear list of acceptance criteria.