wescleveland

Add unique classes to the body tag for easy styling based on post attributes (post type, slug, and ID) and various WordPress “is” functions:
<ul>
<li>wp_is_mobile()</li>
<li>is_home()</li>
<li>is_front_page()</li>
<li>is_blog()</li>
<li>is_admin()</li>
<li>is_admin_bar_showing()</li>
<li>is_404()</li>
<li>is_super_admin()</li>
<li>is_user_logged_in()</li>
<li>is_search()</li>
<li>is_archive()</li>
<li>is_author()</li>
<li>is_category()</li>
<li>is_tag()</li>
<li>is_tax()</li>
<li>is_date()</li>
<li>is_year()</li>
<li>is_month()</li>
<li>is_day()</li>
<li>is_time()</li>
<li>is_single()</li>
<li>is_sticky()</li>
<li>$post->post_type</li>
<li>$post->name</li>
<li>$post->ID</li>
<li>wp_get_post_categories() (Page/Post Categories)</li>
<li>wp_get_post_tags() (Page/Post Tags)</li>
<li>$user->nicename</li>
<li>$user->id</li>
<li>$user->roles</li>
<li>$user->allcaps</li>
<li>$archive->slug (e.g. Category slug, Tag slug, etc.)</li>
<li>$archive->id (e.g. Category id, Tag id, etc.)</li>
</ul>
Add post specific classes to the body tag in the post editor. Use any class name you want to uniquely style an individual post or a set of posts.
Add classes based on user scrolling through the page. You can check things like:
<ul>
<li>is-scroll-top (at the top of the page – synonym for is-not-scroll)</li>
<li>is-not-scroll-top (not at the top of the page – synonym for is-scroll)</li>
<li>is-scroll (not at the top of the page – synonym for is-not-scroll-top)</li>
<li>is-not-scroll (at the top of the page – synonym for is-scroll-top)</li>
<li>is-scroll-top-px (has not reached the scroll start value for scroll measurement by pixels)</li>
<li>is-scroll-top-vh (has not reached the scroll start value for scroll measurement by viewport height)</li>
<li>is-scroll-top-dh (has not reached the scroll start value for scroll measurement by document height)</li>
<li>is-scroll-10-px (scrolled down 10 pixels)</li>
<li>is-scroll-8-vh (scrolled down 8% of the viewport height)</li>
<li>is-scroll-5-dh (scrolled down 5% of the document height)</li>
<li>is-scroll-mid-px (has reached the scroll start value but not the scroll limit for scroll measurement by pixels)</li>
<li>is-scroll-mid-vh (has reached the scroll start value but not the scroll limit for scroll measurement by viewport height)</li>
<li>is-scroll-mid-vh (has reached the scroll start value but not the scroll limit for scroll measurement by document height)</li>
<li>is-scroll-max-px (has reached the scroll limit for scroll measurement by pixels)</li>
<li>is-scroll-max-vh (has reached the scroll limit for scroll measurement by percent of viewport height)</li>
<li>is-scroll-max-dh (has reached the scroll limit for scroll measurement by percent of document height)</li>
</ul>
Add classes based on the results from mobiledetect.net’s Mobile_Detect script. This script parses the value passed by the browser in the HTTP_USER_AGENT string. Consequently, mobile detection is more of an art than a science and, unfortunately, is not perfect. You can check things like:
<ul>
<li>is-mobile</li>
<li>is-tablet</li>
<li>is-phone</li>
<li>Mobile Operating System</li>
<li>Mobile Browser</li>
<li>Type of tablet</li>
<li>Type of phone</li>
</ul>
This plugin adds classes to the html body tag indicating:
<ul>
<li>
whether or not the requesting device is a mobile device (.is-mobile or .is-not-mobile)
</li>
<li>
the type of post being viewed (.is-? where ? is the post type (page, post, whetever special post types are defined) ). 
 E.g. .is-page or .is-post
</li>
<li>
the slug of the post being viewed (.is-?-! where ? is the post type and ! is the post slug). 
 E.g. a post with slug “hello-world’ would have class .is-post-hello-world
</li>
<li>
the ID of the post being viewed (.is-?-# where ? is the post type and # is the post ID). 
 E.g. a post with ID “1” would have class .is-page-1
</li>
<li>
whether or not the requested page shows archived results (.is-archive or .is-not-archive)
If the page being displayed is an archive
<ul>
<li>
the type of archive being viewed (.is-? where ? represents the type of archive (author, category, date, tag) ) 
E.g. .is-author
</li>
<li>
the slug of the archive being viewed (.is-?-! where ? is the archive type and ! is the archive slug) 
E.g. a category with slug “uncategorized’ would have class .is-category-uncategorized
</li>
<li>
the ID of the archive being viewed (.is-?-# where ? is the archive type and # is the archive ID) 
E.g. a category with ID “1” would have class .is-category-1
</li>
</ul>
</li>
<li>
How far down the page the viewer has scrolled in pixels or as a percentage of viewport height or as a percentage of document height
</li>
<li>
Post specific class(es) that are set in the post editor
</li>
</ul>
Use these classes in your styling to provide a better browsing experience for your viewers.
<h4>Custom Body Classes</h4>
Create your own Custom Body Classes by adding your PHP code in the “Custom Body Classes” section.
Here’s an example. Not sure why we would want to do it, but suppose we want to do some custom styling when the page is being displayed to someone that can manage WordPress options. We might enter something like:
<pre><code>if (current_user_can('manage_options')) $classes[] = 'user-can-manage-options';
</code></pre>
Then we can use the body.user-can-manage-options qualifier in our CSS styling.
<h4>Example</h4>
Suppose you have a large h1 top margin that you want to eliminate on mobile devices to avoid a lot of white space. After activating the wp247-body-classes plugin and indicating that the .is-mobile class is desired, all you need to do is add this line to your CSS:
body.is-mobile h1 { 
 margin-top: 0; 
}
Suppose you have a sticky header but want to shrink it by dynamically reducing the top and bottom padding from 25px to 5px as the viewer scrolls down the page based on 20 pixel scroll increments up to 80 pixels of scrolling:
Set WP247 Body Classes Scroll setting to “Scroll by Pixel” with a 10 pixel increment and an 80 pixel limit and then add the following to your CSS:
body.is-scroll-20-px header { 
 padding-top: 20px; 
 padding-bottom: 20px; 
} 
body.is-scroll-40-px header { 
 padding-top: 15px; 
 padding-bottom: 15px; 
} 
body.is-scroll-60-px header { 
 padding-top: 10px; 
 padding-bottom: 10px; 
} 
body.is-scroll-max-px header { 
 padding-top: 5px; 
 padding-bottom: 5px; 
}

WP247 Body Classes

Activating this plugin takes up about 300mb of memory, even on admin pages. Other than that it is great and simple to use.. 5 stars easily once this is fixed.



Currently unusable due to high memory footprint

Add unique classes to the body tag for easy styling based on various attributes (archive, user, post, mobile, scrolling) and WordPress "is"  …

Taylor Lovett

A simple plugin to let you control who has access to what posts. By default in WordPress, we can create users 
and assign them to roles. Roles are automatically assigned certain capabilities. See the codex article for a list of 
<a href="https://codex.wordpress.org/Roles_and_Capabilities" rel="nofollow ugc">Roles and Capabilities</a>. Sometimes default roles are not enough, 
and we have one-off situations. Editorial Access Manager lets you set which users or roles have access to specific 
posts. Perhaps you have a user who is a Contributor, but you want them to have access to edit one specific page? This 
plugin can help you.
<h4>Configuration Overview</h4>
There are no overarching settings for this plugin. Simply go to the edit post screen in the WordPress admin and 
configure access settings in the “Editorial Access Manager” meta box in the sidebar.
<h4>Managing Access by Roles</h4>
In the “Editorial Access Manager” meta box, enable custom access management by “Roles”. Once enabled, the post can only be 
edited by users that fall into those roles. However, no matter what, the Administrator role can always edit any post. 
This if for safety reasons. You can also only use roles that have the “edit_posts” capability; therefore “Subscriber” by 
default cannot be used.
<h4>Managing Access by Users</h4>
In the “Editorial Access Manager” meta box, enable custom access management by “Users”. Once enabled, the post can only be 
edited by designated users. However, no matter what, any administrator can edit any post. This if for safety reasons. 
You can also only use users that have the “edit_others_posts” capability; therefore “Subscriber” users by default 
cannot be used.
Fork the plugin on <a href="http://github.com/tlovett1/editorial-access-manager" rel="nofollow ugc">Github</a>

Editorial Access Manager

Allow for granular editorial access control for all post types in WordPress

WP247 Body Classes vs Editorial Access Manager