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.

iansvo

<p>This block allows you to add an additional block content area to a site-editor template and store the block output inside a meta field. By default, WordPress posts or pages may only store blocks in one place: post_content. These blocks are output on the page using the core/post-content block. This block allows you to have multiple “outlets” where you can add blocks so you can have post-specific blocks appear in more than one location in the template.</p>
<p>The block is a fork of the core/post-content block that uses a customized version of the useEntityBlockEditor hook which supports meta keys. The blocks for your content area are then stored inside that meta key (instead of post_content). This allows you to keep the blocks separate and you can use as many of these on a single template as you want (but in most cases 2 is probably enough). It’s all up to you!</p>
<h3>Requirements</h3>
<ol>
<li>Using this plugin requires you to enable template previews (which will let you visually see the new content area you’re adding). This can be enabled on any given post or page, but you can optionally set it on by default using a filter.</li>
<li>Your theme must be a block theme (i.e. it uses the site editor). This won’t work for a hybrid or classic theme (which has no concept of live template preview in the block editor).</li>
</ol>
<h3>Hooks</h3>
<p>If you want to disable this meta key’s registration, add the following to your theme or plugin:</p>
<pre><code><?php
add_filter( 'content_area_block_register_default_meta', '__return_false' );
</code></pre>
<p>For advanced users, there is also a filter for the entire block’s output. See the below snippet from render.php:</p>
<pre><code><?php
/**
 * Filter the block's frontend output.
 *
 * @param string $parsed_content The parsed block content for output.
 * @param int    $block_post_id  The current post ID the block is displaying in.
 * @param array  $attributes     The block attributes.
 * @param string $content        The original unparsed block content.
 * @param object $block          The current parsed block object.
 *
 * @return The block content for output on the frontend.
 */
$output = apply_filters( 
    'content_area_block_content', 
    do_blocks( str_replace( ']]>', ']]&gt;', $content ) ), 
    $block_post_id, 
    $attributes, 
    $content, 
    $block 
);
</code></pre>
<h3>Contributing</h3>
<p>The plugin source code may be found here: https://github.com/iansvo/content-area-block.</p>
<p>To build the plugin from source, you must have NodeJS (v24+) installed.</p>
<p>Setup Steps:</p>
<ol>
<li>Navigate to the project folder in your terminal.</li>
<li>Run <code>npm i</code> to install dependencies.</li>
<li>Run <code>npm run build</code> to performn the initial build.</li>
</ol>
<p>If you’re using wp-env to run the plugin…<br />
1. Run <code>npm run wp-env start</code> to start the docker container.<br />
2. Run <code>npm run start</code> to watch for file changes.</p>


Content Area Block

Adds a block content area to a site editor template and stores the blocks in a specified meta field. By default, the plugin will add a new meta field  …

Network Template Parts vs Content Area Block