Tran Ngoc Tuan Anh

7 Listings

7 Post Classes removes post classes in post archives or widgets. We love semantic markup, but we also like clean code.
Some users like to add a lot of categories and tags to their posts, products or custom post types. These taxonomies are added as post classes in your post archives or widgets. This can result in poor code to text ratio for SEO.
Major features include:
<ul>
<li>simple</li>
<li>light weight</li>
<li>does not affect single post body classes</li>
</ul>
Upcoming features:
<ul>
<li>settings</li>
<li>ability to remove more classes (category, post)</li>
<li>regular updates to unsure best practices and functionality</li>
</ul>

7 Post Classes

Remove taxonomy post classes from posts in archives or widgets for better SEO.

Aaron T. Grogg

This plug-in limits the classes WordPress added to navigation menus to only those desired by the Theme owner, 
adds a unique ID to each <code>li</code> and removes any empty <code>class</code> attributes.
More about this plug-in can be found at: 
http://aarontgrogg.com/2011/09/28/wordpress-plug-in-navigation-menu-ids-classes/
Please let me know if you have any questions/suggestions/thoughts,
Atg

Navigation Menu IDs & Classes

At least some aspect of this plugin seems like it should be available in WordPress core. 
I understand the rationale for menu items having menu-item-ID, but it's pretty practical for them to have the slug in there, as this plugin provides.
Suggestion for plugin feature - offer option for slug prefix.
Like if I have a menu item "updates" I may use the class "updates" elsewhere, but class "menu-item-updates" would target the menu-item for sure. Of course I can currently use double selectors.



1 for inclusion in core

To reduce the extraneous WordPress classes and add unique IDs to navigation menus.

7 Post Classes vs Navigation Menu IDs & Classes