Dapo Obembe

<p><strong>Swift FSE Blocks</strong> gives you the freedom to design your WordPress site visually — faster, smarter, and without code.</p>
<p>Built for the <strong>Full Site Editing (FSE)</strong> experience, Swift FSE Blocks offers a growing collection of beautifully designed, performance-optimized blocks that help you create stunning layouts in minutes.</p>
<p>Whether you’re building a landing page, portfolio, or blog, Swift FSE Blocks integrates seamlessly with the WordPress Site Editor to help you bring your creative vision to life.</p>
<h3>Why Choose Swift FSE Blocks?</h3>
<ul>
<li><strong>No code required:</strong> Create professional designs visually inside the editor.</li>
<li><strong>SCF/ACF-COmpatible:</strong> Get and use dynamic data from your SCF fields on any page or templates.  </li>
<li><strong>Blazing fast:</strong> Lightweight and built with performance in mind.  </li>
<li><strong>Modern design:</strong> Stylish, responsive, and mobile-ready out of the box.  </li>
<li><strong>FSE ready:</strong> Works flawlessly with WordPress block and full-site editing themes.  </li>
<li><strong>Seamless customization:</strong> Tweak spacing, colors, and typography with intuitive controls.  </li>
<li><strong>Developer friendly:</strong> Clean, extensible code following WordPress standards.</li>
</ul>
<p>Start designing your site the modern WordPress way — simple, fast, and flexible.</p>
<h3>Additional Information</h3>
<p>Swift FSE Blocks helps you <strong>design faster and smarter</strong> using the power of WordPress Full Site Editing.<br />
Perfect for freelancers, creators, and business owners who want to launch beautiful, high-performing websites — no coding required.</p>


Swift FSE Blocks

Build beautiful, fast WordPress sites with flexible Full Site Editing blocks — made for devs, freelancers, and DIY creators.

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.

Swift FSE Blocks vs Network Template Parts