thingsym

<p>Nav Menu Trim plugin trim html id/class attributes of Nav Menu.</p>
<h4>Support</h4>
<p>If you have any trouble, you can use the forums or report bugs.</p>
<ul>
<li>Forum: <a href="https://wordpress.org/support/plugin/nav-menu-trim/" rel="ugc">https://wordpress.org/support/plugin/nav-menu-trim/</a></li>
<li>Issues: <a href="https://github.com/thingsym/nav-menu-trim/issues" rel="nofollow ugc">https://github.com/thingsym/nav-menu-trim/issues</a></li>
</ul>
<h4>Contribution</h4>
<p>Small patches and bug reports can be submitted a issue tracker in Github. Forking on Github is another good way. You can send a pull request.</p>
<p>Translating a plugin takes a lot of time, effort, and patience. I really appreciate the hard work from these contributors.</p>
<p>If you have created or updated your own language pack, you can send gettext PO and MO files to author. I can bundle it into plugin.</p>
<ul>
<li><a href="https://github.com/thingsym/nav-menu-trim" rel="nofollow ugc">VCS – GitHub</a></li>
<li><a href="https://wordpress.org/plugins/nav-menu-trim/" rel="ugc">Homepage – WordPress Plugin</a></li>
<li><a href="https://translate.wordpress.org/projects/wp-plugins/nav-menu-trim" rel="nofollow ugc">Translate Nav Menu Trim into your language.</a></li>
</ul>
<p>You can also contribute by answering issues on the forums.</p>
<ul>
<li>Forum: <a href="https://wordpress.org/support/plugin/nav-menu-trim/" rel="ugc">https://wordpress.org/support/plugin/nav-menu-trim/</a></li>
<li>Issues: <a href="https://github.com/thingsym/nav-menu-trim/issues" rel="nofollow ugc">https://github.com/thingsym/nav-menu-trim/issues</a></li>
</ul>
<h4>Patches and Bug Fixes</h4>
<p>Forking on Github is another good way. You can send a pull request.</p>
<ol>
<li>Fork <a href="https://github.com/thingsym/nav-menu-trim" rel="nofollow ugc">Nav Menu Trim</a> from GitHub repository</li>
<li>Create a feature branch: git checkout -b my-new-feature</li>
<li>Commit your changes: git commit -am ‘Add some feature’</li>
<li>Push to the branch: git push origin my-new-feature</li>
<li>Create new Pull Request</li>
</ol>
<h4>Contribute guidlines</h4>
<p>If you would like to contribute, here are some notes and guidlines.</p>
<ul>
<li>All development happens on the <strong>develop</strong> branch, so it is always the most up-to-date</li>
<li>The <strong>master</strong> branch only contains tagged releases</li>
<li>If you are going to be submitting a pull request, please submit your pull request to the <strong>develop</strong> branch</li>
<li>See about <a href="https://help.github.com/articles/fork-a-repo/" rel="nofollow ugc">forking</a> and <a href="https://help.github.com/articles/using-pull-requests/" rel="nofollow ugc">pull requests</a></li>
</ul>
<h4>Test Matrix</h4>
<p>For operation compatibility between PHP version and WordPress version, see below <a href="https://github.com/thingsym/nav-menu-trim/actions" rel="nofollow ugc">Github Actions</a>.</p>


Nav Menu Trim

Nav Menu Trim plugin trim html id/class attributes of Nav Menu.

Jenst

<p>Settings:</p>
<ul>
<li>Mobile location</li>
<li>Mobile breakpoint</li>
<li>Background color</li>
<li>Text brightness</li>
<li>Logo as text or image</li>
<li>Logo and menu font family</li>
<li>Disable navigation, menu location, CSS, javascript</li>
<li>Hide on scroll, on or off</li>
<li>Custom CSS</li>
</ul>
<p>If you don’t want the HTML to go through the action wp_footer, place this somewhere after the beginning of your body-tag: <code><?php do_action('mn_nav'); ?></code>. It might be better for readability and perhaps SEO.</p>


Mobile Navigation

This broke my whole site on mobile mode.



Don't use if you are on hueman theme

A responsive fullscreen mobile menu navigation. Activate it for your custom made theme to save some time.

Nav Menu Trim vs Mobile Navigation