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.

Weston Ruter

<p>This plugin extends the core Post Date block variation, specifically the “Post Date” variation of the Date block. It appends the modified date to the block whenever it differs from the published date (when rendered in the provided date format). You can configure prefixes and suffixes for both dates, and you can display the modified date on a separate line.</p>
<p>For a full writeup of this plugin, see my <a href="https://weston.ruter.net/2026/01/19/post-date-block-published-modified/" rel="nofollow ugc">blog post</a>.</p>
<p>This is a prototype or stopgap for <a href="https://github.com/WordPress/gutenberg/issues/53099" rel="nofollow ugc">gutenberg#53099</a> (Post date: It is not clear that “display modified date” replaces the publishing date). See also <a href="https://github.com/WordPress/gutenberg/pull/61920" rel="nofollow ugc">gutenberg#61920</a> (Add prefix / suffix to Post Date block). What eventually lands in core will hopefully leverage “<a href="https://github.com/WordPress/gutenberg/issues/73929" rel="nofollow ugc">shortblocks</a>” so that the conditional prefixes and suffixes needn’t be provided in a block settings panel.</p>
<h4>Usage</h4>
<ol>
<li>Open the Site Editor to edit a block template.</li>
<li>Insert a Date block.</li>
<li>In the block settings, click the “Transform to variation” button and select “Post Date”.</li>
<li>A new “With Modified Date” panel appears in the settings. Enable the “Show modified date when different from published date” toggle.</li>
<li>Configure the prefixes and suffixes for the published date and modified date when the two differ for the selected date format; optionally enable the toggle to show the modified date on a separate line.</li>
</ol>
<p><strong>Note:</strong> There is currently no preview in the editor. To see the changes, save the block template and navigate on the frontend to a post that has been modified at least a day after publishing.</p>


Post Date Block: Published & Modified

Appends the modified date to the Post Date block when different from the published date.

Network Template Parts vs Post Date Block: Published & Modified