Barrett Golding

<p>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.</p>
<p>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).</p>
<h4>Enqueue Registered Styles and Scripts (by Handle)</h4>
<p>Use the Postscript meta box (Edit Post screen) to enqueue registered styles and scripts (listed by handle in checkboxes).</p>
<h4>Enqueue Unregistered Styles, Scripts, and Data Files (by URL)</h4>
<p>For each post, you can also enqueue unregistered files, by entering URLs in the meta box text fields for:<br />
* 1 CSS stylesheet.<br />
* 2 JavaScript URLs, e.g, one JSON data file and one script file.</p>
<h4>Add Post and Body Classes</h4>
<p>And for each post, you can add:<br />
* A classname, to the HTML body tag (requires <code>body_class()</code> in theme).<br />
* A classname, to <code>class="post"</code> list (inserted by WordPress, requires <code>post_class()</code> in theme).</p>
<h4>Settings and Security</h4>
<p>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.</p>


Postscript

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

ryanjbonnell

<p>This plugin transforms any registered, enqueued CSS or JavaScript URLs into their “protocol-relative” equivalent.</p>
<p>Consider the following examples:</p>
<p><strong>Protocol Relative CSS URL</strong></p>
<pre><code><link href="//example.com/wp-content/themes/twentytwelve/style.css" />
</code></pre>
<p><strong>Protocol Relative Javascript URL</strong></p>
<pre><code><script src="//example.com/wp-includes/js/jquery/jquery.js"></script>
</code></pre>
<p>More appropriately called a “network-path reference” or “scheme-relative path”, a protocol-relative URL helps to avoid common scenarios such as:</p>
<ul>
<li>Broken SSL padlock icon in browser’s address bar when showing mixed HTTP/HTTPS content</li>
<li>Error message in Internet Explorer saying, “This Page Contains Both Secure and Non-Secure Items”</li>
<li>Serving HTTP assets when viewing HTTPS pages</li>
</ul>
<p>The idea of using protocol-relative URLs was popularized by <a href="http://paulirish.com/2010/the-protocol-relative-url/" rel="nofollow ugc">Paul Irish</a> and has become common as sites switch between serving HTTP and HTTPS assets.</p>
<p>This plugin will standardize all properly enqueued theme files to use protocol-relative paths, even those added from third-party plugins.</p>
<p><em>Note: This plugin does not transform any image paths that may be embedded in the WordPress editor or output as featured images or elsewhere in the theme — it presently only works on enqueued CSS/JavaScript files.</em></p>


Protocol Relative Theme Assets

Transforms enqueued CSS and JavaScript theme URLs to use protocol-relative paths.

Postscript vs Protocol Relative Theme Assets