ahmedgagankodyt

<p><strong>Taxonomy Submenu Block</strong> allows you to create dynamic submenu structures inside the Gutenberg Navigation block by simply selecting a taxonomy. All terms inside the chosen taxonomy automatically appear as submenu items.</p>
<p>Unlike the default WordPress submenu block, this plugin gives you <strong>complete styling freedom</strong> — you can customize every part of the submenu, including submenu container, submenu items, text, backgrounds, hover effects, spacing, borders, typography, and more.</p>
<p>Perfect for blogs, LMS websites, ecommerce stores, real-estate portals, directories, or any site where taxonomy-based menus improve navigation.</p>
<h3><strong>Key Features</strong></h3>
<h4>🚀 Dynamic Taxonomy Menus</h4>
<ul>
<li>Select any taxonomy (categories, tags, custom taxonomies)</li>
<li>Submenu items are automatically generated from all terms</li>
<li>Updates instantly when new terms are added</li>
</ul>
<h4>🎨 Full Styling Control (More than WordPress Core)</h4>
<p>You can style every element without writing a single line of CSS:</p>
<ul>
<li>Submenu container:
<ul>
<li>Padding, margin, background, borders, radius, shadows</li>
</ul>
</li>
<li>Submenu item:
<ul>
<li>Typography, spacing, border, text color, background color</li>
</ul>
</li>
<li>Link styling:
<ul>
<li>Normal & hover colors  </li>
<li>Hover backgrounds  </li>
<li>Active state styling</li>
</ul>
</li>
</ul>
<h4>🧩 Editor-Friendly & Lightweight</h4>
<ul>
<li>Works inside the Navigation block like a native element  </li>
<li>Uses the same CSS variables as core Navigation for compatibility  </li>
<li>No front-end performance impact  </li>
<li>No admin pages or complex settings</li>
</ul>


Taxonomy Submenu

A Gutenberg block that creates dynamic submenu items from any taxonomy and offers complete styling control beyond the default WordPress submenu block.

Stephanie Leary

<p>Imports well-formed static HTML files into WordPress. Requires PHP 5.</p>
<p>This plugin will import a directory of files as either pages or posts. You may specify the HTML tag (e.g. <code><body></code>, <code><div id="content"></code>, or <code><td width="732"></code>) or Dreamweaver template region (e.g. ‘Main Content’) containing the content you want to import.</p>
<p>If importing pages, the directory hierarchy will be preserved. Directories containing the specified file types will be imported as empty parent pages (or, if an index file is present, its contents will be used for the parent page). Directories that do not contain the specified file types will be ignored.</p>
<p>As files are imported, the resulting IDs, permalinks, and titles will be displayed. On completion, the importer will provide a list of Apache redirects that can be used in your <code>.htaccess</code> file to seamlessly transfer visitors from the old file locations to the new WordPress permalinks. As of 2.0, if you change your permalink structure after you’ve imported your files, you can regenerate the redirects—the file’s old URL is stored as a custom field in the imported post.</p>
<p>Options:</p>
<ul>
<li>import files into any post type (posts, pages, or custom post types set to <code>public</code>)</li>
<li>import linked media files (images, documents, etc.) to the media library</li>
<li>select content, title, and custom fields by HTML tag or Dreamweaver template region</li>
<li>remove a common phrase (such as the site name) from imported titles</li>
<li>remove the imported title from within the content area</li>
<li>upload a single file or scan a directory for files to import</li>
<li>specify file extensions to import (e.g. html, htm, php)</li>
<li>specify directories to exclude (e.g. images, css)</li>
<li>if importing pages (or any hierarchical post type), specify whether your top-level files should become top-level pages or children of an existing page</li>
<li>specify index file names (e.g. index.html, default.htm) whose contents should be used for the directory parent pages </li>
<li>set tags, categories, and custom taxonomies</li>
<li>choose status, author, and timestamp</li>
<li>use meta descriptions as excerpts</li>
<li>clean up imported HTML and strip unwanted tags and attributes in content and custom fields</li>
<li>fix internal links in imported files to match new permalinks</li>
<li>import the entire file and generate the title from the filename </li>
<li>preserve the original filename as the imported page’s slug</li>
<li>choose the date from an HTML tag or Dreamweaver region (uses <a href="http://php.net/strtotime" rel="nofollow ugc">strtotime()</a>; results may vary)</li>
<li>import additional HTML tags or Dreamweaver regions as custom fields</li>
<li>option to remove imported title from within content area</li>
<li>fallbacks: if your chosen tag/area is empty or does not exist, the importer will select <code><body></code> for content and <code><title></code> for the title</li>
<li>use a custom field named ‘post_tag’ to import tags from a portion of the file</li>
</ul>
<p>See the <a href="http://stephanieleary.com/code/wordpress/html-import/html-import-2-user-guide/" rel="nofollow ugc">User Guide</a> for details on all the options.</p>
<h4>Thanks</h4>
<p>Thanks to…</p>
<ul>
<li>Tom Dyson’s <a href="http://wordoff.org/" rel="nofollow ugc">Wordoff.org</a> for inspiring the Word cleanup option in 1.1. </li>
<li>Dion Hulse’s <a href="https://wordpress.org/extend/plugins/add-from-server/" rel="ugc">Add from Server</a> plugin and bbqiguana’s <a href="https://wordpress.org/extend/plugins/add-linked-images-to-gallery-v01/" rel="ugc">Add Linked Images To Gallery</a> plugin, from which I borrowed a lot of the logic behind the image import feature in 2.0</li>
</ul>


HTML Import 2

Imports well-formed HTML files into WordPress pages.

Taxonomy Submenu vs HTML Import 2