Improve the Template API

[shazahm1]

The firth gen API is great for me, however, it makes it far more difficult for users who just want to tweak their templates a little. So let improve that a little by:

• Add an option to disable the enqueueing of the skeleton CSS file. Ref Add option to disable styles. #216.
• Develop method to disable the enqueuing of template specific CSS files.
• Create process to easily allow user to override a template's CSS file with their own tweaked version.
• Create a method that allow a user to easily override a template file.
• Create a template loading hierarchy.

[shazahm1]

Disabling CSS Detail

• Add a new settings section under the Advanced tab for CSS.
• Include a directions header.
• Add option to disable core CSS.
• Add option to disable Chosen CSS.

NOTES:

The Chosen and qTip styles should not be enqueued by default. The template's should enqueue them as needed. I'm stuck with loading the Chosen CSS for now, but I should update all templates that use it to enqueue the CSS. As for the CSS for qTip, leave it registered, but their is no reason to enqueue it.

• Do no enqueue the CSS for qTip

[shazahm1]

Overriding Template CSS Detail

User would create a folder named connections_templates in their parent or child theme; within that folder they would create a folder named with the template's slug. They could then copy the the template's CSS file into this folder which will override the template core CSS file. This should make it upgrade safe when upgrading both the templates and core.

• This should be hierarchal. First look in the child theme, then parent theme, next the connections_templates folder and lastly in the template's folder.
• When in each folder, first check for a minified version if WP_DEBUG is enabled and then check for the un-minified version. If WP_DEBUG is not enabled an no minified version is available, load the un-minified version.

[shazahm1]

Overriding Template Layout Files

User would create a folder named connections_templates in their parent or child theme; within that folder they would create a folder named with the template's slug. They could then copy the the template's files into this folder which will override the template core files. This should make it upgrade safe when upgrading both the templates and core.

• This should be hierarchal. First look in the child theme, then parent theme, next the connections_templates folder and lastly in the template's folder.

[shazahm1]

Loading template files based on context.

Currently using the template API a list result card and a single entry card can be registered for use. Using this method required that the user know just a little more than just basic PHP. This should be changed to load based on if the file exists or not. This will allow for the user to easily override a template file in an upgrade safe manner and add support for other views if the template does not come with one.

• Create template loading based on context.
• If file exists, it should override the template parts registered via the API. This will provide backward compatibility for all the templates out there.

Template should load in the following order:

• card-category-category_slug.php
• card-category.php
• card-country-country_slug.php
• card-country.php
• card-region-region_slug.php
• card-region.php
• card-postal-postal_slug.php
• card-postal.php
• card-locality-locality_slug.php
• card-locality.php
• card-locality-locality_slug.php
• card-organization-organization_slug.php
• card-organization.php
• card-deparment-deparment_slug.php
• card-deparment.php
• card-single-name_slug.php
• card-single.php
• card.php

NOTE: This really isn't a true hierarchy, the template that will be loaded will be based on context of what the requested results are. Only if the template file for that context is not available will it fall back to the card.php template file.

[shazahm1]

Important

Note to self: Keep qT in mind when making these changes because templates created with qT will not have actual files, but if the files exist, they should override what was added when making the qT.

[shazahm1]

Ref:
http://connections-pro.com/support/topic/can-use-basic-design-for-pro-templates/

[shazahm1]

This class can very likely be modded for my use.

ref:
http://pippinsplugins.com/template-file-loaders-plugins/