viniciusbo

Allow pages/categories to have different styles by adding a CSS Class (the Page Name or Category/Tag Slug) to the BODY.
The CSS class can be the following:
<ul>
<li>Home Page: “home”</li>
<li>Search Page: “search”</li>
<li>Category Page: category slug</li>
<li>Single Post/Page: page/post slug</li>
<li>Posts listed by any date: “archive”
<ul>
<li>If posts are listed by year: “archive year”</li>
<li>If posts are listed by month: “archive month”</li>
<li>If posts are listed by day: “archive day”</li>
</ul>
</li>
<li>Posts listed by author: “author”</li>
<li>404 Error: “404”</li>
</ul>
Please, feel free to contribute or give me any feedback!

Page Style

Allow pages/categories to have different styles by adding a CSS Class (the Page Name or Category/Tag Slug) to the BODY

mneil

Finds all possible .js and .css files from a WP install available and allows you to combine and/or compress the files to reduce 
load time. The plugin can monitor file changes in “development” mode (by hashing file mtime) which allows the plugin to 
recompile the files when a file changes. Or, it can cache the files in “production” mode so that files are only recompiled 
if they are not found or are deleted manually from the cache folder. Additionally, this plugin will allow you to force the 
inclusion of javascript files into either the head or the foot of the page.
There are two modes, development and production, the ability to force the files to print in the header or footer*, the use of 
Google Closure as a JS compiler, and finally the ability to pick and choose which files, including dependencies, should be combined.
*forcing head compiles can fail on JS files queued after the call to wp_head(). The plugin will, in this case, render the late 
queued files in the footer as originally intended.

MnCombine

Easily manage the merging and compression of js and css files from plugins and themes

Page Style vs MnCombine