Templates, how are they made... Boy I could have fun with this... LOL
We have inside of templates the following:
Please note, the base has the following:
Please note the tmpl_uni has the following:
Now, keep this in mind:
Your colors, widths, image calls (most, not all) are all done in the css files and there is an order of hierarchy to them.
Lowest to Highest:
templates/base/css/general.css
templates/tmpl_uni/css/general.css
templates/base/css/index.css
templates/tmpl_uni/css/index.css
What this means is both base/css/general.css & ..._uni/css/general.css will load for every page, but if an item is called from .../base/css/index.css then it will over rule the general.css files and if it's called from ..._uni/css/index.css then that is trump. Go ahead and take a look at the files.
Now, for columns on most pages (those that don't utilize page builders) please take a moment and look at:
base/scripts/BxBaseIndex.php & ..._uni/scripts/BxTemplIndex.php files. note that tmpl_uni/ is always the trump and gets the final say. Where as inc/classes/BxDolIndex.php is the primary (lowest hierarchy) in the run. Obviously that puts base/scripts/BxBaseIndex.php in the middle of it all.
I hope I've thoroughly confused everyone with this, but it's really not. At least not until you start to notice that anchor.css likes to throw it's weight around once in a while, it tends to make development drag until you remember to raise your anchor.css. LOL... Of course, you also need to look sometimes at the index.php page to see if it's calling a custom /css/file.css or not. Also, you might have some extra Java or SWF thrown in that you need to take into consideration.