The Template Provisioning plugin automatically links to stylesheet and javascript files in your theme directories based on the template file that renders a page. It searches in several pre-defined locations for files, and includes whichever files are found.<\/p>\n\n
I wrote this plugin because I prefer this method to using Wordpress's conditional tags in my header. Keeping resources for different templates separate helps me keep my custom theme directories clean and organized.<\/p>\n\n
For example, if I have a custom template \"map.php\" that is being used by a static page, I can create \"css\/map.css\" and \"js\/map.js\" files and they'll be automatically linked-up by this plugin.<\/p>\n\n
Will this plugin work with your theme? Probably. It's completely additive, and doesn't change anything that would affect other plugins. I have been using most of this code since Wordpress 2.5 or so. But be warned... I haven't thoroughly tested it across versions of Wordpress. I'll try to do that soon and post the results.<\/p>\n\n\n
Using the plugin is easy. Just create some .css, .less and .js files where the plugin expects them... in the same directory as your template files. There are a series of files that it looks for when rendering a page using any given template file:<\/p>\n\n
Stylesheets for \"<template_name>.php\":\nincluded in page <head> by wp_head() function<\/p>\n\n
Javascript files for \"<template_name>.php\":\nincluded in page <head> by wp_head() function<\/p>\n\n
End-of-page Javascript files for \"<template_name>.php\" footer:\nincluded near the <\/body> tag by wp_footer() function<\/p>\n\n
If your script or stylesheet depends on others (i.e. jQuery) being loaded first, simply enqueue them in your template header before the call to wp_head().<\/p>\n\n
You can also specify dependencies in comments in included scripts and stylesheets using the following syntax (dependencies should be comma-separated):\n* \/\/ NEEDS: jquery, jquery-cycle<\/p>\n\n
NOTE: the above syntax will not actually enqueue the dependencies... it will only require them for our included scripts.<\/p>\n\n
As of version 0.2.4, the plugin will also look for .less files<\/p>\n\n
If you have the \"less.js\" javascript file in the expected location, it will also be enqueued:<\/p>\n\n
As of version 0.2.5, the plugin can be configured to output CSS and JS urls with a base URL from your blog URL. For example, if have an amazon S3 bucket publicly accessible at http:\/\/assets.yourdomain.com, and it contains \/css and \/js subdirectories, the plugin can link to those instead of to your theme directory.<\/p>\n\n
To configure an asset host URL, add the following to your theme's functions.php file:<\/p>\n\n
if (class_exists('Template_Provisioning')) {\n Template_Provisioning::set_asset_host('http:\/\/assets.yourdomain.com');\n}<\/p>\n\n
(Note: you probably don't want a trailing slash on that URL)<\/p>\n\n\n