David Smith

<p>This Plugin allows you to display and apply alternative styling to different navigation menus based on the screen size using the WordPress Navigation block.</p>
<p><a href="https://wordpress.org/plugins/getdave-responsive-navigation-block/" rel="ugc"></a> <a href="https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/getdave/responsive-navigation-block/refs/heads/trunk/.wordpress-org/blueprints/blueprint.json" rel="nofollow ugc"></a></p>
<h3> Video Walkthrough</h3>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/R5kzAaEsDMg?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h3>Features</h3>
<ul>
<li>Two new Navigation Block (variations) for:
<ul>
<li>Mobile</li>
<li>Desktop</li>
</ul>
</li>
<li>Style your menu differently depending on screen size.</li>
<li>Use a different menu for each screen size.</li>
<li>Customize the “breakpoint” (where you switch between mobile and desktop).</li>
<li>Automatically switch editor to “mobile” preview when editing the mobile navigation.</li>
</ul>
<h3>Usage</h3>
<p>This Plugin creates two block variations from the Navigation block which will be <strong>automatically hidden/shown at the configured screensize</strong> (breakpoint):</p>
<ul>
<li>Navigation (Mobile) – will be displayed only on smaller screen sizes.</li>
<li>Navigation (Desktop) – will be displayed only on larger screen sizes.</li>
</ul>
<p>This affords the ability to <strong>independently style mobile vs desktop navigation</strong> and even allows for <strong>completely different menus</strong> to be used.</p>
<p>The Plugin should be used as follows:</p>
<ul>
<li>Install and Activate the plugin – two new block variations will be automatically registered for “Mobile” and “Desktop”.</li>
<li>Go to the Editor and remove any existing Navigation block.</li>
<li>Add the “Desktop Navigation” block – style and configure the menu for “desktop” as required.</li>
<li>Add the “Mobile Navigation” block – style and configure the menu for “mobile” as required.</li>
<li>View the front of your website and resize your browser to see the navigations swap out at the appropriate breakpoint/screensize.</li>
</ul>
<p>Alternatively you can transform the default Navigation block to either <code>Mobile</code> or <code>Desktop</code> variations via the block’s interface.</p>
<h3>Support</h3>
<p>Please see FAQs. If you still have an issue please:</p>
<ul>
<li>check <a href="https://github.com/getdave/responsive-navigation-block/issues" rel="nofollow ugc">Github for existing Issue reports</a>.</li>
<li>(if none) then file a new Issue on Github</li>
</ul>
<h3>Privacy Statement</h3>
<p>Responsive Navigation does <em>not</em>:</p>
<ul>
<li>use cookies.</li>
<li>send data to any third party.</li>
<li>include any third party resources.</li>
</ul>
<h3>Contributing</h3>
<p>Contributions to this Plugin are welcome. Please fork the Github repository and submit a PR for review.</p>
<h3>Development Setup</h3>
<p>This Plugin uses the <a href="https://developer.wordpress.org/block-editor/reference-guides/packages/packages-scripts/" rel="nofollow ugc">@wordpress/scripts package</a>.</p>
<ul>
<li>Check out the Github repo into the <code>wp-content/plugins</code> directory of a WordPress installation.</li>
<li><code>cd</code> into the Plugin’s directory install the dependencies with <code>npm i</code>.</li>
<li>Running <code>npm start</code> will start the <code>@wordpress/scripts</code> package in watch mode ready to compile the JavaScript on modification.</li>
<li>PHP files can be edited in the usual manner.</li>
</ul>
<h3>Testing</h3>
<p>The Plugin has e2e test coverage for the key features courtesey of @wordpress/scripts and Playwright.</p>
<p>To run the tests – in your terminal of choice:</p>
<ul>
<li><code>npm run build</code>.</li>
<li><code>npm run wp-env start</code>.</li>
<li>Run the tests: <code>npm run test:e2e</code></li>
</ul>
<h3>Releasing</h3>
<p>Releasing the Plugin to the WordPress.org Plugin repo is the prerogative of the Plugin owner (@get_dave). The process is as follows:</p>
<h4>Test the Plugin</h4>
<ul>
<li>Commit all changes to <code>trunk</code> branch.</li>
<li>Push changes to <code>trunk</code> (only) – <code>git push origin trunk</code>.</li>
<li>In Github:
<ul>
<li>Actions</li>
<li>Select the <a href="https://github.com/getdave/responsive-navigation-block/actions/workflows/build-release-zip.yml" rel="nofollow ugc"><code>Build Release Zip</code> action</a>.</li>
<li>Select the <code>Run workflow</code> dropdown and run the workflow to generate a zip file.</li>
<li>When action completes download the generated Plugin zip artifact.</li>
<li>Manually install and test the .zip.</li>
</ul>
</li>
</ul>
<h4>Deploy to WP.org</h4>
<ul>
<li>When ready to deploy.</li>
<li>Bump Plugin version and tag release – <code>npm run bump-version</code>.</li>
<li>Push trunk and tags – <code>git push origin trunk --tags</code></li>
<li>Deployment to WP.org will be handled automatically.</li>
</ul>


Responsive Navigation Block


Thanks for providing a solution to this common problem, it is very helpful


Such a needed feature, thank you!

Complete control over your navigation menus based on screen size including styles and menu items.

GuyPrimavera

<p>This open source and lightweight plugin allows users with the role <strong>Editor</strong> or <strong>Shop Manager</strong> to access the <strong>Menus</strong> and <strong>Widgets</strong> areas of the Appearance menu in WordPress’ admin area.</p>
<p>This is a common task that would be useful for clients to manage themselves to give them more control over their website’s content.</p>
<p>This plugin also gives access to the <strong>Customize</strong> submenu and other theme options, but these can be hidden through the options page at <strong>Appearance > Editor Access</strong> if you wish.</p>
<p>You can also select other menus to hide from Editors and Shop Managers (e.g. custom theme or plugin options pages), as well as hiding <strong>any elements on the Admin Bar</strong>.</p>
<p><strong>Features</strong></p>
<ul>
<li><strong>Allow access</strong> to Customize, Menus and Widgets for Editors and Shop Managers.</li>
<li><strong>Theme Options</strong> remain hidden from these user roles.</li>
<li><strong>Hide custom options pages</strong> from these users (if your theme/plugin has a custom settings page you wish to hide).</li>
<li><strong>Hide any other menus</strong> or submenus. Simply select which menus you wish to hide.</li>
<li><strong>Hide admin bar menus and elements</strong>. Choose which elements you wish to hide.</li>
</ul>


Editor Menu and Widget Access

Ideal

Allow and control Editor and Shop Manager access to the menus, widgets and appearance menu, plus other menus and adminbar items.

Responsive Navigation Block vs Editor Menu and Widget Access