Professional Documents
Culture Documents
Ingredients
Module Positions
Template module positions are identified in the templateDetails.xml file. The following template positions are fairly standard, and by using these, your content will have somewhere to go in one of the supplied templates. <positions> <position>left</position> <position>right</position> <position>top</position> <position>breadcrumb</position> <position>user1</position> <position>user2</position> <position>user3</position> <position>user4</position> <position>debug</position> <position>syndicate</position> </positions>
Joomla! 1.5
The template BEEZ has these files: The ones with * are required for even a basic template. *index.html (blank html so users wont see the contents of folder include one of these in every sub-folder as well!) *index.php (Start with your html and replace blocks with snippets from the Templates Cheat Sheet.) *css (folder) (A minimum of one template.css file, you can have others for ie or print.) *images (folder) (Include all images used in template or to decorate modules or components.) html (folder) (Borrow whole folder from Beez to use in your template - and make it better!) *templateDetails.xml (Start wth file from Beez and modify for your template.) *template_thumbnail.png (Take a screenshot of your html design, then reduce to 206px wide.) favicon.ico (Generate one of these at http:// tools.dynamicdrive.com/favicon. ) component.php (Used by Joomla! print button - to print component without other layout divs - overrides system/component.php.) images_general (folder) javascript (folder) params.ini (needed if you define parameters for your template.)
Template Overrides
Joomla! out of the box writes less than optimal html code, wrapping things in tables and using table data cells where wed rather have an h1 or h2 heading. Template overrides are files you include in the html folder of your template that will be used instead of the core Joomla! code when html is generated. The Beez template was created to improve the html for web standards and for accessiblity and the html folder from Beez is a common starting point for Joomla! template development. Side 2 of this card has tips on creating your own template overrides.
templateX/html/category/blog.php AND templateX/html/com_content/section/blog.php Move this line up to enclose the php that generates the h1: <div class=blog<?php echo $this->escape($this->params>get(pageclass_sfx)); ?>> and change the class from blog... to cat-blog... or sect-blog... These 5 changes give me styling handles that CAN be made more specific through the use of page class suffixes so that any article, blog or list page can be styled uniquely.
100%
What component is loading? Another variable that can be created within your template is one that identifies the component being called for any given page. Your non-sef urls show you this: index. php?option=com_content..... or index.php?option=com_virtuemart... or... Add this to opening php block: $pageoption = JRequest::getVar( option, ); and then append $pageoption to a containing div to give you handles for styling different kinds of pages with different css rules. (See Cory Webbs, howtoJoomla.net 4.17.2008 blog post for other ideas using this variable.)
Barb Ackemann Iris Lines Designs Brattleboro, Vermont , USA 802 257 7391 irislines.com