Glossary

jdoc statements are included in every Joomla template and indicate where the output from other parts of Joomla or its extensions should be positioned in the overall web page. A typical jdoc statement looks like this:

<jdoc:include type="component" />

See the jdoc statements article for more information.

The official directory for all components, plugins and modules available for use with the Joomla platform. This database is maintained by the Joomla developers.

A Joomla extension that displays the results of a survey conducted on your site.

A user level on a Joomla site that is the same a Public except for the Allow permission for the Site Login action. This means members of this group have access only to the front-end access to the site. Should you wish it, a registered user is able to see additional content to that seen by casual visitors to your site.

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.

Reference: http://docs.joomla.org/Glossary

A user level on a Joomla site with access only to the front end. Publishers have permission to write, edit, and publish site content.

In Joomla, a program that associates a path (URL) with internal Joomla queries. Normally a router contains two methods, build() and parse(). The build() method takes an array of commands and returns a JURI object. The parse() method reverses this and turns a JURI object into an array of commands.