Barrett Golding

No more shoehorning stylesheets and JavaScripts into the post content box. No more loading scripts on every post that only a few use. Postscript lets you easily add libraries or single-post script and style files post-by-post.
The plugin uses the WordPress “enqueue” methods, which means you can control dependencies (when registering scripts), improve site performance by putting styles in the head and scripts in the footer, and eliminate loading multiple copies of the same library (jQuery, I’m looking at you).
<h4>Enqueue Registered Styles and Scripts (by Handle)</h4>
Use the Postscript meta box (Edit Post screen) to enqueue registered styles and scripts (listed by handle in checkboxes).
<h4>Enqueue Unregistered Styles, Scripts, and Data Files (by URL)</h4>
For each post, you can also enqueue unregistered files, by entering URLs in the meta box text fields for: 
* 1 CSS stylesheet. 
* 2 JavaScript URLs, e.g, one JSON data file and one script file.
<h4>Add Post and Body Classes</h4>
And for each post, you can add: 
* A classname, to the HTML body tag (requires <code>body_class()</code> in theme). 
* A classname, to <code>class="post"</code> list (inserted by WordPress, requires <code>post_class()</code> in theme).
<h4>Settings and Security</h4>
The Settings screen lets you control which user-roles and post-types display the Postscript meta box and which script/style handles users are allowed to enqueue.

Postscript

Data visionaries and multi-mediators, make any post sing with scripts and splendid with styles, all from within WordPress.

TylerShaw

What’s It Do?
This plugin adds a box to your pages and posts allowing for page-specific or post-specific CSS stylesheets.
Why Use It?
After developing quite a few WordPress websites, it seems to me that the style.css file gets bloated. If you add a style used on only one page, and then later that page is deleted, you’re visitors now have to download those styles that aren’t even used. It’s wasteful, but maintaining a clean style.css file requires an active effort. This plugin solves that by attaching the these styles to the page or post, allowing them to be updated just like the content is and deleted with the page.
It keeps your style.css file clean and reduces unused style clutter.
What About Efficiency?
There shouldn’t be an issue with overhead from the plugin. Admin code is only executed in the admin panel and front end code is executed on the front end. If you’re website has a large amount of page-specific styles within it that can be migrated into the plugin, it can boost performance by reducing the download size of your style.css file.
Roadmap
This plugin will receive ongoing maintenance as WordPress evolves. No major features are planned, but I am entirely open to feature requests!
Feel free to suggest any feature you desire, or check out the code or contribute on <a href="https://github.com/tyler-shaw/page-specific-stylesheets" rel="nofollow ugc">GitHub</a>, where the project is hosted.
<ul>
<li>Additional plugin options.</li>
</ul>
If you have a feature idea, suggest it.
Notes
<ul>
<li>Style data and options are not deleted by default on uninstall. You must check the options on the plugin settings page to enable the deletion of this data.</li>
</ul>

Page Specific Stylesheets

Adds a box allowing for the addition of page-specifc and post-specific CSS stylesheets. Reduces the need to edit and clutter up the style.css file.

Postscript vs Page Specific Stylesheets