Actions

J2.5

Difference between revisions of "Getting Started with Templates"

From Joomla! Documentation

m (add version/tutor template, will have to rewrite some dpl calls to grab Namespace for JVer icon automatically)
(Purpose of templates: Remove 2.5 namespace)
Line 5: Line 5:
 
This introductory tutorial will give you an insight into the Joomla! templating system and what you can do with it.
 
This introductory tutorial will give you an insight into the Joomla! templating system and what you can do with it.
 
==Purpose of templates==
 
==Purpose of templates==
{{:J2.5:What is the purpose of a template?}}
+
{{:What is the purpose of a template?}}
  
 
= What can you do =
 
= What can you do =

Revision as of 05:21, 6 June 2013


Contents

Intro

This introductory tutorial will give you an insight into the Joomla! templating system and what you can do with it.

Purpose of templates

<translate>

J3x-template-example-screenshot.png

</translate>

<translate> A template controls the overall look and layout of a site. It provides the framework that brings together common elements, modules and components as well as providing the cascading style sheet for the site. Both the front-end and the back-end of the site have templates.</translate>

<translate> When Joomla! is first installed several templates are automatically included. You can find many more templates at other websites. Some are available without charge under various licenses, and some are for sale. In addition, there are many developers available who can make custom templates. You can also make your own template.</translate>

<translate> Templates are managed with the Template Manager, which is located on the Extensions menu in the back-end (administrator) area of your site.</translate>

<translate>=== Why does Joomla! use templates? [A real beginners guide!] === </translate>

<translate> The way Joomla! is designed separates out the key tasks involved in producing a website for efficient maintenance of the software. One of these tasks is to create the aesthetic (the look, feel and layout) of the site. This includes making decisions such as which content elements (components, modules and plugins) you may want to place in any given page.</translate>

<translate> When producing a web page, the location of most elements will stay the same (menus, banner locations, sidebars etc.). Additionally, you will want to create the same look (fonts, header styles, colour scheme etc.) for every page. For some parts of the site you may want to alter the general feel to indicate a different purpose for those pages (such as a blog section). A little planning is required for this, but once you have settled on the overall layout for your site, you then have the task of producing each page of content.</translate>

<translate> And that’s where the template comes in. You can either write all the code for each page separately, or use a template for each major section of your site so that when you want to create a new page you simply “fill in the blanks”. Okay, perhaps it's not that simple, but this tutorial is designed to give you a step by step guide for effective template use, starting with how to use one and ending with how to create one for yourself.</translate>

<translate>

  1. Use one of the templates supplied with Joomla!
  2. Download one of the many free offerings from the Internet.
  3. Pay for one to be modified or produced from scratch if your needs cannot be met any other way.</translate>

<translate> Summary – a template controls the look of your site and at the same time allows the website administrator focus more on the actual content.</translate>


What can you do

J2.5:What can you do with a template?

Templates Supplied

The following templates are supplied with a default installation of Joomla! 2.5

Site Templates

  • Beez 20 (Default template)
  • Beez 5
  • Atomic

Administrator Templates

  • Bluestork (Default template)
  • Hathor


Switching Templates

To change the default Template for the Site (Front-end) or Administrator (Back-end), follow these steps:

  • Click on: Extensions -> Template Manager

Extension-manager-template-manager.png

You will now see the Template Manager screen.

Note: If you do not see Template Manager listed as an option on the Extensions menu, then it is most likely because you are not logged in as a Super Administrator. Only Super Administrators will see this menu item.


From here you manage your templates for Front-end and Back-end. The default view shows your installed Front-end templates. The default template for the Front-end is marked with a star; in the image below it is rhuk_milkyway.

To change the default template to beez:

  • click the checkbox left from the template name to select it;
  • click "Default" on the toolbar;

the star changes from rhuk_milkyway to beez and you are done.

25-Switching-templates-1.png

Assigning more than one template for the Front-end

Using Template Manager

  • Go to Extensions > Template Manager, choose a template style by checking the box to the left of its name and then click on the Edit button. Alternatively, simply click the name of the template style to edit it.
  • On the Edit Style screen, check the menu items that should display the chosen template style and click on the Save button.

The image on the left shows the Getting Started page displaying the Beez2 template style. The image on the center shows the Atomic template style being assigned to the Getting Started menu item. The image on the right shows the Getting Started page now with Atomic template style.

25-Switching-templates-assign-menus.png

  • Go to the fronted of your website and refresh the page to view the modifications.

Using menu items under Menus

  • Go to Menus > Menu Name, choose a menu item by checking the box to the left of its name and then click on the Edit button. Alternatively, simply click the name of the menu item to edit it.
  • On the Edit Menu Item screen, in Template Style, choose the desired template style and click on the Save button.

Atomic template style being applied to the Getting Started Menu item.

  • Go to the fronted of your website and refresh the page to view the modifications.

Installing Templates

Install via Admin Panel (packed template file)

Log into the back-end of your site (www.your-site.com/administrator/)

Click on: Extensions -> Extension Manager

25-Installing-template-navigate.png

You see the page "Extension Manager"

From here you can install your Templates, Plugins, Modules, Components and Languages. You have three options:

  • Upload Package File - (select a package from your PC, upload and install it)
  • Install from Directory - (enter the path where the package is located on your server)
  • Install from URL - (enter the URL to the package)

Here, we choose the first method: Upload Package File

Select the package from your PC and click the button "Upload File & Install"

25-Installing-template-upload-package-file.png


If the package contains no errors you are done and get a success message like the one below.

25-Installing-template-install-success.png

Install via FTP (unpacked template file)

Templates can also be installed via FTP without packaging them. Simply select the template folder on your PC and upload it to your server, using your favorite FTP software. Be sure you upload the template folder to the directory: /path_to_joomla/templates/ - where /path_to_joomla/ is the location of your Joomla! installation on the server. This method is mostly used when you have created a template yourself, and do not want to have to package it to install the template, or if you want to upload more than one template at once. You must then go into extension manager and click on Discover in the sub menu. Click on "Discover" in the toolbar if your template doesn't immediately appear. A list of uninstalled items in the FTP should then appear. Click the checkbox to the left of your template and click install.

Note: Do not try to use FTP to install Components, Modules and Plugins if you are a beginner/novice. These items need database entries which have to be inserted manually if you bypass the package installer.


<headertabs/>