WebMan Design | Oliver Juhas

<p>Extending WordPress Navigation block with functionality to display classic menus.</p>
<h4>What problem does it solve?</h4>
<p>❓ <em>Do you experience problems making your website navigation multilingual when using block theme (FSE – full site editing)?</em><br />
❓ <em>Are you using a plugin that modifies classic menu but not Navigation block and you are using block theme?</em></p>
<p><strong>Classic Menu in Navigation Block</strong> plugin lets you display classic menus in Navigation block so you can gain from using classic menu modification plugins and yet display the menu with accessibility, customization and responsive features of Navigation block.</p>
<p>This method is particularly useful when building a multilingual website and your multilingual plugin does not handle Navigation block very well. You can simply “revert” back to using classic menu, which multilingual plugins supports out of the box.</p>
<p>You can do changes to your classic menus and Navigation block will always display up to date version of the menu.</p>
<p>To speed things up the plugin also applies caching for your classic menus converted to blocks. This cache is updated every time you update your classic menu. If you are using a very dynamic classic menu modification plugin, you can even disable the cache.</p>
<h4>Got a question or suggestion?</h4>
<p>In case of any question or suggestion regarding this plugin, feel free to ask at <a href="https://wordpress.org/support/plugin/classic-menu-in-navigation-block/" rel="ugc">support section</a>, or at <a href="https://github.com/webmandesign/classic-menu-in-navigation-block/issues" rel="nofollow ugc">GitHub repository issues</a>.</p>


Classic Menu in Navigation Block


Great job, maybe needed some polishing, but it provides exactly that is needed. Gives the Classic Menu Admin and ability to style.



It would be great to see the classic menu working on the edit mode when the menu is selected, otherwise it is a little confusing, is it selected or not.


Exactly what needed


Great to add that classic control when using an FSE theme.


Worked like a dream

Extending WordPress Navigation block with functionality to display classic menus.

Jeremy Felt

Happy Prime

philcable

slocker

<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.

Classic Menu in Navigation Block vs Network Template Parts