Jeremy Felt

Happy Prime

slocker

philcable

<p>When managing a brand across many sites, it is often necessary to ship changes to the look and feel with the certainty that they will be applied immediately.</p>
<p>In its current iteration, the WordPress site editor allows individual site administrators to make changes to a theme’s templates and template parts. Once a template or a template part has been edited on an individual site, it no longer receives updates from the theme automatically, which may in turn cause unintended consequences.</p>
<p>This plugin provides a way for site administrators to edit parts of the site without accidentally overwriting pieces that should remain consistent.</p>
<p>Network Template Parts works in tandem with <a href="https://github.com/happyprime/restrict-network-templates" rel="nofollow ugc">Restrict Network Templates</a>, which restricts the editing of templates on individual sites.</p>
<h3>Assumptions</h3>
<h3>Templates provided by the theme should not be edited.</h3>
<p>A theme’s core structure is defined by templates. (e.g. <code>templates/home.html</code>)</p>
<p>It should be possible to set a structure in these templates and assume that they will not be overridden on individual sites.</p>
<h3>Network-level template parts are managed by network administrators.</h3>
<p>Parts of a theme’s structure rely on data from the main site on a network. (e.g. global navigation)</p>
<p>It should be possible for a template to specify that a section of a page is rendered in the context of the main site.</p>
<h3>Site-level template parts are managed by site administrators.</h3>
<p>Parts of a theme’s structure rely on data from individual sites on a network. (e.g. site navigation, content)</p>
<p>It should be possible to override site-level template parts from an individual site.</p>
<h3>Block</h3>
<p>The Network Template Part block renders a selected template part in either a “site” or “network” context.</p>
<p>Attributes:</p>
<ul>
<li><code>slug</code> determines which template part to load. Template parts are located in a theme’s <code>parts/</code> directory.</li>
<li><code>context</code> determines the context in which the part should render.</li>
</ul>
<h3>Examples</h3>
<p>Often, a network will provide common header and footer areas while leaving the site content between to site administrators. With Network Template Parts, this can be accomplished as so:</p>
<p>A <code>templates/index.html</code> file may contain:</p>
<pre><code>


</code></pre>
<p>></p>
<p>This loads <code>parts/header.html</code> from the main site on the network, <code>parts/main-index.html</code> from the current site, and <code>parts/footer.html</code> from the main site on the network.</p>
<p>The <code>parts/header.html</code> file main contain:</p>
<pre><code>

</code></pre>
<p>></p>
<p>This defines two areas in the header to be managed at the network level. The <code>parts/header-main.html</code> may contain something like:</p>
<pre><code>
<div class="wp-block-group">
    
    <header class="wp-block-group">
        
        
    </header>
    
</div>

</code></pre>
<p>></p>
<p>This provides some common HTML structure, loads a network-level logo, and also provides a site-level navigation in <code>parts/header-main-site-navigation.html</code>.</p>
<p>Now, an individual site administrator can make changes to a navigation menu while also receiving updates from the theme and the network if the look and feel of the broader network changes.</p>

Network Template Parts

Render template parts in a site or network context.

Troy Chaplin

<p><strong>Ever needed to track down where a specific block is being used?</strong> Block Finder adds a dashboard widget that searches your entire site for any core or custom block. Pick a block, click Search, and instantly see every place it appears — along with a count of how many times it’s used, whether it’s nested inside another block, and a direct link to edit that content.</p>
<p>No more manually opening posts one by one hoping to find the right block. Block Finder does the searching so you don’t have to.</p>
<h4>Who is this for?</h4>
<p><strong>Content editors and site managers</strong> — need to update every post that uses a specific call-to-action block? Wondering which pages are still using a block you’re about to change? Block Finder gives you the answer in seconds, with one-click access to edit each result.</p>
<p><strong>Developers and theme builders</strong> — auditing block usage across templates and template parts in the Site Editor, checking registered patterns, or running automated checks from the command line. Block Finder has you covered.</p>
<h4>Features</h4>
<p><strong>Search your way:</strong></p>
<ul>
<li>Type-ahead block picker powered by WordPress’s native Combobox — no hunting through a long list</li>
<li>Search Posts, Patterns, Templates, and Template parts all from one form</li>
<li>Filter by post type to narrow results, or search across everything at once</li>
<li>Filter by post status — include drafts, pending, scheduled, and private content alongside published</li>
</ul>
<p><strong>Understand what you find:</strong></p>
<ul>
<li>See the total number of times a block appears in each piece of content</li>
<li>InnerBlock detection shows how many of those instances are nested inside another block</li>
<li>Source badges make it clear at a glance whether a result came from a post, a pattern, a template, or a template part</li>
<li>Status badges surface non-published content so nothing gets missed</li>
</ul>
<p><strong>Act on results quickly:</strong></p>
<ul>
<li>Direct edit links open any result straight in the block editor or Site Editor</li>
<li>Paginated results keep large result sets easy to browse</li>
<li>Filter between all instances and nested-only with a single click</li>
</ul>
<h4>For Developers and Theme Builders</h4>
<p><strong>WP-CLI</strong> — run <code>wp block-finder search <block></code> from the command line. Supports <code>--post-type</code>, <code>--post-status</code>, <code>--sources</code>, and <code>--format=table|json|csv|count|ids</code>. Use <code>--format=count</code> in CI pipelines or <code>--format=csv</code> for export and audit reports.</p>
<p><strong>Template and template part search</strong> — find blocks inside Site Editor templates on any block theme. Both file-based and database-stored templates are included.</p>
<p><strong>Pattern search</strong> — covers user-saved synced patterns and every pattern registered by your theme or plugins via <code>WP_Block_Patterns_Registry</code>, not just the ones saved to the database.</p>
<p><strong>Developer hooks</strong> — extend or modify search behaviour without touching plugin code:</p>
<ul>
<li><code>block_finder_sources</code> — add or remove sources before the search runs</li>
<li><code>block_finder_results</code> — modify the assembled result set before it is returned</li>
</ul>
<p><strong>REST API</strong> — <code>GET /wp-json/block-finder/v1/search</code> is available for custom integrations. Requires <code>edit_posts</code> capability.</p>


Block Finder

Find any block, anywhere on your site — posts, patterns, templates, and template parts.

Network Template Parts vs Block Finder