El glosari de Joomla! és útil per a l'aprenentatge de les paraules més comuns usades als tutorials, a l'ajuda i a la documentació més avançada.
Els Àlies són peces breus de text que representen el títol de certs elements (elements de Menú, Articles i Categories) en una màquina-format amable. Aquest format només permet lletres minúscules i guions (-).
Els Àlies s'utilitzen a Joomla per fer Cercador amigable amb les URLs (Search Engine Friendly URLs). Hi ha limitacions tècniques per els tipus de personatges que es poden incloure a les adreces URL, així Joomla evita problemes amb caràcters que no són vàlids, ja que et permet especificar un àlies.
Pots omplir un àlies tu mateix. "'Si deixes el camp àlies buit"', Joomla crearà automàticament un àlies basat en el camp títol d'un article quan es desa. ""Això significa que si es modifica el títol d'un article, però deixes l'antic àlies al camp, l'àlies (i la URL que s'ha creat a partir d'ella) no canviarà."' Deixa buit el camp àlies si vols generar un nou àlies.
The word "core" in Joomla! pertains to the distributed files which are needed to create and administrate a Joomla CMS powered web site. These files can be downloaded from the Joomla website at http://www.joomla.org/download.html. The Joomla "core" also contains some basic functionality to get new Joomla installations working quickly and easily. Included are the user manager, article manager, weblink manager, category manager, contact manager, and menu manager. There is also a template manager with a few basic templates to power the front-end (website/user) view, a module manager with basic modules, plugin manager with basic plugins, and a few other "out of the box" extensions to extend the functionality of a basic Joomla installation. These core's extensions should not be confused with extensions which are available for downloading from the JED (Joomla! Extension Directory).
Mira també: Directori d'extensions Joomla.
Joomla fa un ús extensiu del patró de disseny Model-Vista-Controlador .
When Joomla is started to process a request from a user, such as a GET for a particular page, or a POST containing form data, one of the first things that Joomla does is to analyse the URL to determine which component will be responsible for processing the request, and hand control over to that component.
If the component has been designed according to the MVC pattern, it will pass control to the controller. The controller is responsible for analysing the request and determining which model(s) will be needed to satisfy the request, and which view should be used to return the results back to the user.
The model encapsulates the data used by the component. In most cases this data will come from a database, either the Joomla database, or some external database, but it is also possible for the model to obtain data from other sources, such as via a web services API running on another server. The model is also responsible for updating the database where appropriate. The purpose of the model is to isolate the controller and view from the details of how data is obtained or amended.
The view is responsible for generating the output that gets sent to the browser by the component. It calls on the model for any information it needs and formats it appropriately. For example, a list of data items pulled from the model could be wrapped into an HTML table by the view.
Since Joomla is designed to be highly modular, the output from the component is generally only part of the complete web page that the user will ultimately see. Once the view has generated the output the component hands control back to the Joomla framework which then loads and executes the template. The template combines the output from the component, and any modules that are active on the current page, so that it can be delivered to the browser as a single page.
To provide additional power and flexibility to web designers, who may only be concerned with creating new designs rather than manipulating the underlying code, Joomla splits the traditional view into a separate view and layout. The view pulls data from the model, as in a traditional MVC pattern, but then simply makes that data available to the layout, which is responsible for formatting the data for presentation to the user. The advantage of having this split is that the Joomla template system provides a simple mechanism for layouts to be overridden in the template. These layout overrides (often called "template overrides" because they form part of the template, although actually it is the layout that is being overridden) are bundled with the template and give the template designer complete control over all the output from the Joomla core and any installed third-party extensions that comply with the MVC design pattern.
The term patch file is used for two different file types. The term patch file is sometimes used to refer to archive files that allow you to upgrade from one Joomla! version to another (for example, from version 1.0.0 to version 1.0.7). These upgrade files are also referred to as upgrade packages.
L'altre utililitat per a un arxiu de pegats és un fitxer creat per codi font software de control de versió, per exemple, " Subversion " o SVN, que s'utilitza per al codi font de Joomla! Aquest tipus de pegat conté instruccions per canviar el contingut d'un o més fitxers de codi font. A l'SVN,el programari llegeix la revisió de fitxer i, a continuació, canvia automàticament el codi font dels fitxers que són modificats.
Patch files are used by the Bug Squad to test proposed bug fixes. They can also be used to contribute proposed new features to the version under development. For more information about the structure of SVN patch files, read Learn more about patch files.
A plugin is a kind of Joomla! extension. Plugins provide functions which are associated with trigger events. Joomla provides a set of core plugin events, but any extension can fire (custom) events. When a particular event occurs, all plugin functions of the type associated with the event are executed in sequence. This is a powerful way of extending the functionality of the Joomla! Platform. It also offers extension developers a way to allow other extensions to respond to their actions, making extensions extensible.
The Joomla! plugin architecture follows the Observer design pattern. The JPlugin class provides the means to register custom plugin code with core or custom events. The JDispatcher class (JEventDispatcher in Joomla 3.x) is an event handler which calls all plugins registered for a particular event, when that event is triggered.
A split menu is where different levels of a single menu are displayed in two or more locations on a single web page.
For example, a common requirement is for a menu of top-level items to appear at the top of the page. When one of the items is clicked the user is taken to a page where a secondary menu, say on the left of the page, shows second-level items within the scope of the top-level item.
The menus appear in separate locations on the page, but are related because one shows only top-level items while the other shows second-level items. This idea can be extended to include menus for third-level items and beyond.
This can be implemented in Joomla using a single multi-level menu then creating more than one menu module each referring to a different level.
Mira també: Menu/ca
A template is a type of Joomla! extension that changes the way your site looks. There are two types of templates used by the Joomla! CMS: Front-end Templates and Back-end Templates. The Front-end Template controls the way your website is presented to the user viewing the website's content. The Back-end Template controls the way your website's administrative tasks are presented for controlling management functions by a Joomla! Administrator. These would include common tasks such as: user, menu, article, category, module, component, plugin and template management.