Joomla! Documentation - User contributions [en]

Build Test Packages From A Release Branch/de

2019-10-19T14:17:53Z

Oliverhh: Created page with "Solange du keine PHP-Syntaxfehler hast und jedes der Release-Tags in deinem lokalen Checkout verfügbar ist, solltest du in der Lage sein, das Build-Skript auszuführen und vo..."

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

===Bearbeiten des build Skripts===
Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Starten des Skripts===
Solange du keine PHP-Syntaxfehler hast und jedes der Release-Tags in deinem lokalen Checkout verfügbar ist, solltest du in der Lage sein, das Build-Skript auszuführen und vollständige Pakete zum Testen bereitzustellen.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/11/de

2019-10-19T14:17:53Z

Solange du keine PHP-Syntaxfehler hast und jedes der Release-Tags in deinem lokalen Checkout verfügbar ist, solltest du in der Lage sein, das Build-Skript auszuführen und vollständige Pakete zum Testen bereitzustellen.

Build Test Packages From A Release Branch/de

2019-10-19T14:17:16Z

Oliverhh:

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

===Bearbeiten des build Skripts===
Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Starten des Skripts===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/4/de

2019-10-19T14:17:16Z

Oliverhh:

===Bearbeiten des build Skripts===

Build Test Packages From A Release Branch/de

2019-10-19T14:15:18Z

Oliverhh: Created page with "===Starten des Skripts==="

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

===Bearbeiten des build scripts===
Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Starten des Skripts===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/10/de

2019-10-19T14:15:18Z

Oliverhh: Created page with "===Starten des Skripts==="

===Starten des Skripts===

Build Test Packages From A Release Branch/de

2019-10-19T14:14:24Z

Oliverhh: Created page with "Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen."

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

===Bearbeiten des build scripts===
Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Run the Script===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/5/de

2019-10-19T14:14:24Z

Oliverhh: Created page with "Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen."

Um Pakete aus deinem Feature-Zweig zu erstellen, musst du nur zwei Änderungen am Build-Skript vornehmen.

Build Test Packages From A Release Branch/de

2019-10-19T14:13:35Z

Oliverhh: Created page with "===Bearbeiten des build scripts==="

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

===Bearbeiten des build scripts===
To build packages from your feature branch, all you need to do is make two changes to the build script.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Run the Script===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/4/de

2019-10-19T14:13:34Z

Oliverhh: Created page with "===Bearbeiten des build scripts==="

===Bearbeiten des build scripts===

Build Test Packages From A Release Branch/de

2019-10-19T14:13:05Z

Oliverhh: Created page with "Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Sk..."

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

===Editing the Build Script===
To build packages from your feature branch, all you need to do is make two changes to the build script.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Run the Script===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/3/de

2019-10-19T14:13:05Z

Um die Pakete zu erstellen, muss dein lokaler Checkout mit der Basis Joomla! CMS Repo synchronisiert sein, um alle Release-Tags zu enthalten. Das ist wichtig, da das Build-Skript die bei jedem Release erstellten Git-Tags verwendet, um die Update-Pakete zu erstellen. Als nächstes sollte dein Feature-Zweig mit dem Staging-Zweig aus dem Joomla! CMS Repo synchronisiert werden, um sicherzustellen, dass der aktuelle Code zusätzlich zu deinen vorgeschlagenen Änderungen getestet wird.

Build Test Packages From A Release Branch/de

2019-10-19T14:10:45Z

Oliverhh: Created page with "== Voraussetzungen =="

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

== Voraussetzungen ==
In order to build the packages, your local checkout must be in sync with the base Joomla! CMS repo, to include all release tags. This is important because the build script uses the git tags created at each release to build the update packages. Next, your feature branch should be in sync with the staging branch from the Joomla! CMS repo to ensure that the current code is being tested in addition to your proposed changes.

===Editing the Build Script===
To build packages from your feature branch, all you need to do is make two changes to the build script.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Run the Script===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

Translations:Build Test Packages From A Release Branch/2/de

2019-10-19T14:10:45Z

Oliverhh: Created page with "== Voraussetzungen =="

== Voraussetzungen ==

Build Test Packages From A Release Branch/de

2019-10-19T14:10:25Z

Oliverhh: Created page with "Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joom..."

<noinclude><languages /></noinclude>
Gelegentlich müssen neue Funktionen und vorhandene Fehler während der Installation oder des Updates zwischen Joomla! Versionen getestet werden. Das [https://github.com/joomla/joomla-cms/blob/staging/build/build.php Build-Skript], das sich im CMS Repo auf GitHub befindet, kann einfach verändert werden, um Pakete aus einem feature branch zu erstellen, und führt zu einer vollständigen Palette von Paketen (Vollinstallation und Update) zur Verwendung.

===Requirements===
In order to build the packages, your local checkout must be in sync with the base Joomla! CMS repo, to include all release tags. This is important because the build script uses the git tags created at each release to build the update packages. Next, your feature branch should be in sync with the staging branch from the Joomla! CMS repo to ensure that the current code is being tested in addition to your proposed changes.

===Editing the Build Script===
To build packages from your feature branch, all you need to do is make two changes to the build script.

* '''Line 66''':
** Change this line to read <tt>"system($gitPath . ' archive BRANCH-NAME | tar -x -C ' . $fullpath);"</tt> and replace your branch name as appropriate
* '''Line 144''':
** Change this line to read <tt>"$command = $gitPath . ' diff tags/' . $previousTag . ' BRANCH-NAME --name-status > diffdocs/' . $version . '.' . $num;"</tt> and replace your branch name as appropriate

===Run the Script===
So long as you don't have any PHP syntax errors and each of the release tags are available in your local checkout, you should be able to run the build script and have full packages ready for testing.

<noinclude>
[[Category:Bug Squad]]
[[Category:Tutorials]]
</noinclude>

2018-09-08T12:45:35Z

Oliverhh: Created page with "de"

<noinclude><languages /></noinclude>

{{RightTOC}}Joomla! ist schon nach der Standard Installation ein Content Management System (CMS) mit vielen Funktionen. Beim Entwickeln einer eigenen Website kann es vorkommen, dass benötigte Funktionen nicht mit der grundlegenden Installation zur Verfügung stehen. Für diesen Fall kann Joomla! sehr einfach um weitere Funktionen erweitert werden.
Grundsätzlich sind fünf Typen von Erweiterungen möglich: Komponenten, Module, Plugins, Templates und Sprachen. Jeder dieser Erweiterungstypen ist für die bestimmte Funktionen zuständig (einige der Standard Funktionen von Joomla! sind ebenfalls über Erweiterungen umgesetzt).

[[Image:Extensions-de.jpg]]

== [[S:MyLanguage/Component|Components]] ==

Components are the largest and most complex extensions of them all; they can be seen as mini-applications. Most components have two parts: a site part and an administrator part. Every time a Joomla! page is requested, ''one'' component is called to render the body of the page. For example, Content (com_content) is the component which handles the display of content; users can view at the frontend of your site and, as an administrator, you can edit the content. Components are the major portion of your page because a component is driven by a menu item and every menu item runs a component.

'''Examples:''' Content (com_content), Banners (com_banners), Contacts (com_contact), News Feeds (com_newsfeeds) and Web Links (com_weblinks)

'''Management feature:''' ''Admin head menu'' > “Components” > (“Contacts” for com_contact)

== [[S:MyLanguage/Module|Modules]] ==

Modules are more lightweight and flexible extensions used for page rendering. These modules are mostly known as the “boxes” that are arranged around a component, for example: the login module. The Footer is a module. Modules are assigned per menu item. So, you can decide to show or hide the login module depending on which menu item the user is viewing. Sometimes modules are linked to components such as the “Latest News” module which links to the com_content and displays links to the newest content items. However, modules do not need to be linked to components, as a matter of fact they don't even need to be linked to anything and can be just static HTML or text.

'''Examples:''' Banners (mod_banners), Menus (mod_menu), Who's Online (mod_whosonline)

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Module Manager”

== [[S:MyLanguage/Plugin|Plugins]] ==

Plugins are more advanced extensions and are in essence event handlers. In the execution of any part of Joomla, be it the core, a module or a component, an event can be triggered. When an event is triggered, plugins that are registered with the application to handle that event execute. For example, a plugin could be used to intercept user-submitted articles and filter out bad words.

'''Examples:''' Content - Load Modules, Editor - TinyMCE

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Plugin Manager”

== [[S:MyLanguage/Template|Templates]] ==

A template is basically the design of your Joomla! powered website. With a template you can change the look and feel of your website. Templates have certain fields in which the component (just one) and modules (as many as you like) will be shown. Templates are easy to build or customize and they provide maximum flexibility in how you style your site.

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Template Manager”

== [[S:MyLanguage/Language|Languages]] ==

Probably the most basic extensions are languages. Languages can be packaged in two ways: either as a core package or as an extension package. In essence, both the core and the extension language package files consist of key/value pairs, which provide the translation of static text strings, assigned within the Joomla! source code. These language packs will affect both the front and administrator side of your Joomla site. Note: these language packs also include an XML meta file which describes the language.

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Language Manager”

== Extension Installation ==

There are 4 methods of installing an extension. You can upload an extension, install from a directory, install from a URL or install from web.
:[[File:30-Installing-template-upload-package-file-en.png|Administrator Installation]]

<noinclude>
[[Category:Extensions]]
[[Category:Definition lists]]
</noinclude>

Translations:Extension types (general definitions)/2/de

2018-09-08T12:45:34Z

Oliverhh: Created page with "de"

Extension types (general definitions)/de

2018-09-08T12:45:19Z

Oliverhh: Created page with "Joomla! ist schon nach der Standard Installation ein Content Management System (CMS) mit vielen Funktionen. Beim Entwickeln einer eigenen Website kann es vorkommen, dass benö..."

<noinclude><languages /></noinclude>

{{RightTOC}}Joomla! ist schon nach der Standard Installation ein Content Management System (CMS) mit vielen Funktionen. Beim Entwickeln einer eigenen Website kann es vorkommen, dass benötigte Funktionen nicht mit der grundlegenden Installation zur Verfügung stehen. Für diesen Fall kann Joomla! sehr einfach um weitere Funktionen erweitert werden.
Grundsätzlich sind fünf Typen von Erweiterungen möglich: Komponenten, Module, Plugins, Templates und Sprachen. Jeder dieser Erweiterungstypen ist für die bestimmte Funktionen zuständig (einige der Standard Funktionen von Joomla! sind ebenfalls über Erweiterungen umgesetzt).

[[Image:Extensions-en.jpg]]

== [[S:MyLanguage/Component|Components]] ==

Components are the largest and most complex extensions of them all; they can be seen as mini-applications. Most components have two parts: a site part and an administrator part. Every time a Joomla! page is requested, ''one'' component is called to render the body of the page. For example, Content (com_content) is the component which handles the display of content; users can view at the frontend of your site and, as an administrator, you can edit the content. Components are the major portion of your page because a component is driven by a menu item and every menu item runs a component.

'''Examples:''' Content (com_content), Banners (com_banners), Contacts (com_contact), News Feeds (com_newsfeeds) and Web Links (com_weblinks)

'''Management feature:''' ''Admin head menu'' > “Components” > (“Contacts” for com_contact)

== [[S:MyLanguage/Module|Modules]] ==

Modules are more lightweight and flexible extensions used for page rendering. These modules are mostly known as the “boxes” that are arranged around a component, for example: the login module. The Footer is a module. Modules are assigned per menu item. So, you can decide to show or hide the login module depending on which menu item the user is viewing. Sometimes modules are linked to components such as the “Latest News” module which links to the com_content and displays links to the newest content items. However, modules do not need to be linked to components, as a matter of fact they don't even need to be linked to anything and can be just static HTML or text.

'''Examples:''' Banners (mod_banners), Menus (mod_menu), Who's Online (mod_whosonline)

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Module Manager”

== [[S:MyLanguage/Plugin|Plugins]] ==

Plugins are more advanced extensions and are in essence event handlers. In the execution of any part of Joomla, be it the core, a module or a component, an event can be triggered. When an event is triggered, plugins that are registered with the application to handle that event execute. For example, a plugin could be used to intercept user-submitted articles and filter out bad words.

'''Examples:''' Content - Load Modules, Editor - TinyMCE

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Plugin Manager”

== [[S:MyLanguage/Template|Templates]] ==

A template is basically the design of your Joomla! powered website. With a template you can change the look and feel of your website. Templates have certain fields in which the component (just one) and modules (as many as you like) will be shown. Templates are easy to build or customize and they provide maximum flexibility in how you style your site.

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Template Manager”

== [[S:MyLanguage/Language|Languages]] ==

Probably the most basic extensions are languages. Languages can be packaged in two ways: either as a core package or as an extension package. In essence, both the core and the extension language package files consist of key/value pairs, which provide the translation of static text strings, assigned within the Joomla! source code. These language packs will affect both the front and administrator side of your Joomla site. Note: these language packs also include an XML meta file which describes the language.

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Language Manager”

== Extension Installation ==

There are 4 methods of installing an extension. You can upload an extension, install from a directory, install from a URL or install from web.
:[[File:30-Installing-template-upload-package-file-en.png|Administrator Installation]]

<noinclude>
[[Category:Extensions]]
[[Category:Definition lists]]
</noinclude>

Translations:Extension types (general definitions)/1/de

2018-09-08T12:45:19Z

Joomla! ist schon nach der Standard Installation ein Content Management System (CMS) mit vielen Funktionen. Beim Entwickeln einer eigenen Website kann es vorkommen, dass benötigte Funktionen nicht mit der grundlegenden Installation zur Verfügung stehen. Für diesen Fall kann Joomla! sehr einfach um weitere Funktionen erweitert werden.
Grundsätzlich sind fünf Typen von Erweiterungen möglich: Komponenten, Module, Plugins, Templates und Sprachen. Jeder dieser Erweiterungstypen ist für die bestimmte Funktionen zuständig (einige der Standard Funktionen von Joomla! sind ebenfalls über Erweiterungen umgesetzt).

Extension types (general definitions)/de

2018-09-08T12:35:10Z

Oliverhh: Created page with "Erweiterungstypen (allgemeine Definition)"

<noinclude><languages /></noinclude>

{{RightTOC}}Joomla! already is a rich featured content management system, but if you're building a website with Joomla! and you need extra features which aren't available in Joomla! by default, you can easily extend it with extensions. There are five types of extensions for Joomla!: Components, Modules, Plugins, Templates, and Languages. Each of these extensions handle specific functionality (some built-in features of Joomla! are implemented using extensions).

[[Image:Extensions-en.jpg]]

== [[S:MyLanguage/Component|Components]] ==

Components are the largest and most complex extensions of them all; they can be seen as mini-applications. Most components have two parts: a site part and an administrator part. Every time a Joomla! page is requested, ''one'' component is called to render the body of the page. For example, Content (com_content) is the component which handles the display of content; users can view at the frontend of your site and, as an administrator, you can edit the content. Components are the major portion of your page because a component is driven by a menu item and every menu item runs a component.

'''Examples:''' Content (com_content), Banners (com_banners), Contacts (com_contact), News Feeds (com_newsfeeds) and Web Links (com_weblinks)

'''Management feature:''' ''Admin head menu'' > “Components” > (“Contacts” for com_contact)

== [[S:MyLanguage/Module|Modules]] ==

Modules are more lightweight and flexible extensions used for page rendering. These modules are mostly known as the “boxes” that are arranged around a component, for example: the login module. The Footer is a module. Modules are assigned per menu item. So, you can decide to show or hide the login module depending on which menu item the user is viewing. Sometimes modules are linked to components such as the “Latest News” module which links to the com_content and displays links to the newest content items. However, modules do not need to be linked to components, as a matter of fact they don't even need to be linked to anything and can be just static HTML or text.

'''Examples:''' Banners (mod_banners), Menus (mod_menu), Who's Online (mod_whosonline)

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Module Manager”

== [[S:MyLanguage/Plugin|Plugins]] ==

Plugins are more advanced extensions and are in essence event handlers. In the execution of any part of Joomla, be it the core, a module or a component, an event can be triggered. When an event is triggered, plugins that are registered with the application to handle that event execute. For example, a plugin could be used to intercept user-submitted articles and filter out bad words.

'''Examples:''' Content - Load Modules, Editor - TinyMCE

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Plugin Manager”

== [[S:MyLanguage/Template|Templates]] ==

A template is basically the design of your Joomla! powered website. With a template you can change the look and feel of your website. Templates have certain fields in which the component (just one) and modules (as many as you like) will be shown. Templates are easy to build or customize and they provide maximum flexibility in how you style your site.

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Template Manager”

== [[S:MyLanguage/Language|Languages]] ==

Probably the most basic extensions are languages. Languages can be packaged in two ways: either as a core package or as an extension package. In essence, both the core and the extension language package files consist of key/value pairs, which provide the translation of static text strings, assigned within the Joomla! source code. These language packs will affect both the front and administrator side of your Joomla site. Note: these language packs also include an XML meta file which describes the language.

'''Management feature:''' ''Admin head menu'' > “Extensions” > “Language Manager”

== Extension Installation ==

There are 4 methods of installing an extension. You can upload an extension, install from a directory, install from a URL or install from web.
:[[File:30-Installing-template-upload-package-file-en.png|Administrator Installation]]

<noinclude>
[[Category:Extensions]]
[[Category:Definition lists]]
</noinclude>

Translations:Extension types (general definitions)/Page display title/de

2018-09-08T12:35:10Z

2018-09-08T11:17:30Z

Oliverhh: /* Current Translations Teams */

[[File:JDOC translation icon.png|right]]
Here, people '''translating''' {{SITENAME}} can sign up as a translator. Please be sure to read the required reading list below.

After you add your username to the list below under the appropriate language heading, a [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator you can start translating! Please be on the look out for a [[Template:Translator welcome|welcome message]] with more information posted to your user talk page.{{-}}

==Required Reading==
* Getting started, read [[JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]
* Detailed explanation of translating, [[JDOC:Page Translation Explained|Page Translation Explained]].
* Our [[JDOC:Language policy|Language policy]]
* [[JDOC:Translator Tips|Translator Tips]]
* [[Joomla:JDOC%27s_Translation_Guidelines|Translation Guidelines]]
* Having an [[JDOC:Translation Questions|issue or need help]]?

{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}

===Add Your Language===
If your language isn't listed below, please add it using the format:

<code><lang code> - Localised language name - English language name </code>

Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code>

When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.

==Current Translations Teams==

Documentation language codes are different from Joomla! language codes, they are ISO 639-1 2 letter code. A small quantity of 4 letter language codes are used as an exception, but these language codes are all lowercase.

=== ar - عربي - arabe ===
* {{User|ghilo}}
* {{User|HawraMilani}}
* {{User|hossen}}
* {{User|ahmadm42}}

=== af - Afrikaans ===
*{{User|JoeSA}}

=== be - Беларуская - Belarusian ===
* {{User|Nikolice}}

=== bg - Български - Bulgarian ===
* {{User|bdimov}}
* {{User|Mastwd}}

=== bn - বাংলা - Bengali ===
* {{User|ashiks}}
* {{User|smsnobin77}}

=== ca - Català - Catalan ===
* {{User|el_libre}}

=== cs - Čeština - Czech ===
* {{User|fredericco-cz}}
* {{User|Bart}}
* {{User|n3tcz}}
* {{User|svatas}}

=== da - Dansk - Danish ===
* {{User|ot2sen}}
* {{User|rbuelund}}

=== de - Deutsch - German ===
* {{User|Astridx}}
* {{User|Assmann}}
* {{User|Balzercomp}}
* {{User|Batmin}}
* {{User|ceus1984}}
* {{User|Chmst}}
* {{User|chrishoefliger}}
* {{User|FancyFranci}}
* {{User|Farrell}}
* {{User|FLin1}}
* {{User|FrankyD}}
* {{User|Franz.wohlkoenig}}
* {{User|fruppel}}
* {{User|gorgonz}}
* {{User|jehacgn}}
* {{User|joomla-agency}}
* {{User|Joomti}}
* {{User|Ka3media}}
* {{User|King_Louis_1}}
* {{User|Knig.Markus}}
* {{User|Kolvar}}
* {{User|Kurztipp}}
* {{User|m-b-o}}
* {{User|Maggus}}
* {{User|Max123kl}}
* {{User|michaelmyk}}
* {{User|oliverhh}}
* {{User|Paterna}}
* {{User|Pc-doppler}}
* {{User|Pete71}}
* {{User|phillopp}}
* {{User|plocher}}
* {{User|Prof.Logout}}
* {{User|RMajewski}}
* {{User|Schmidie64}}
* {{User|SeigetsuShoen}}
* {{User|Sisko1990}}
* {{User|Stefanie}}
* {{User|tfecha}}
* {{User|Tkahl}}
* {{User|UCFnet002}}
* {{User|Usimon}}
* {{User|Webberry}}
* {{User|Yvesh}}
* {{User|zero24}}
* {{User|Xadomir}}
* {{User|Widmann}}

=== el - Ελληνικά - Greek ===
* {{User|pnkr}}
* {{User|SiteworksGr}}

=== es - Español - Spanish ===
* {{User|Abulafia}}
* {{User|Andrea Gentil}}
* {{User|BNovoa.S}}
* {{User|brucevalle}}
* {{User|carcam}}
* {{User|cristobal.vio}}
* {{User|Crsanchez}}
* {{User|danielperaza}}
* {{User|filisfutsarov}}
* {{User|framon}}
* {{User|Irene.lopez}}
* {{User|isidrobaq}}
* {{User|ivanramosnet}}
* {{User|Javiparati}}
* {{User|Jcollver}}
* {{User|Koa}}
* {{User|Leo_Soto}}
* {{User|netandsoftware}}
* {{User|NunoLopes}}
* {{User|pfvidal}}
* {{User|shaz}}
* {{User|Urielmx}}
* {{User|VictorYork87}}
* {{User|viena}}
* {{User|Willin}}

=== et - Eesti - Estonian ===
* {{User|Eraser}}

=== fa - فارسی - Persian ===
* {{User|azolfagharj}}
* {{User|Grand}}
* {{User|Heydari}}
* {{User|Joomlafarsi}}
* {{User|Levelup}}
* {{User|mhehm}}

=== fr - Français - French ===
* {{User|david613}}
* {{User|edelouche}}
* {{User|Erix}}
* {{User|Garstud}}
* {{User|MATsxm}}
* {{User|Opware2000}}
* {{User|Perete}}
* {{User|Sandra97}}
* {{User|MaximeK7}}
* {{User|Shim-sao}}

=== ga - Gaeilge - Irish ===
* {{User|rvbgnu}}

=== he - עברית - Hebrew ===
* {{User|ydl}}
* {{User|shirdesign}}

=== hi - हिंदी - Hindi ===
* {{User|AlamM}}
* {{User|Rana}}
* {{User|Syhussaini}}
* {{User|Shivamrajput}}
* {{User|ankitify}}

=== hr - Hrvatski - Croatian ===
* {{User|limoo}}

=== hu - Magyar - Hungarian ===
* {{User|Balazs}}
* {{User|webgobe}}

=== hy - Հայերեն - Armenian ===
* {{User|Aaleksanyants}}

=== id - Bahasa Indonesia - Indonesian ===
* {{User|dw1Rianto}}
* {{User|Micokelana}}
* {{User|sikumbang}}

=== it - Italiano - Italian ===
* {{User|alexred}}
* {{User|aleorco}}
* {{User|alikon}}
* {{User|Andreacarriero}}
* {{User|CinziaDesign}}
* {{User|donato}}
* {{User|Ladyj}}
* {{User|Luca.marzo}}
* {{User|marioluciani}}
* {{User|moqui}}
* {{User|nemo_bis}} (occasionally)
* {{User|Paolo Alberti}}
* {{User|Fabio Caracciolo}}
* {{User|robertolongo}}
* {{User|ste}}

=== ja - 日本語 - Japanese ===
* {{User|Koji Hijikuro}}
* {{User|Nori}}
* {{User|Richell}}
* {{User|Yama}}

=== nl - Nederlands - Dutch ===
* {{User|AboutTime}}
* {{User|Alex0703}}
* {{User|Annemiek}}
* {{User|Arkomat}}
* {{User|bcdesign}}
* {{User|crommie}}
* {{User|Grubosoft}}
* {{User|fcschippers}}
* {{User|HermanPeeren}}
* {{User|Hvdmeer}}
* {{User|janvankuijk}}
* {{User|John Flour}}
* {{User|JorSanders}}
* {{User|Josien}}
* {{User|Lara}}
* {{User|Lianne}}
* {{User|klatte88}}
* {{User|ManuAmpe}}
* {{User|Marcelk}}
* {{User|marionnijhuis}}
* {{User|Marnix}}
* {{User|MartijnM}}
* {{User|Meta}}
* {{User|metdick}}
* {{User|Mtb}}
* {{User|n9iels}}
* {{User|Nemphias}}
* {{User|Nico-van-Leeuwen}}
* {{User|Onderzoekspraktijk}}
* {{User|rachel73}}
* {{User|Renem}}
* {{User|Ries}}
* {{User|Rineke}}
* {{User|Schrijvers123}}
* {{User|slibbe}}
* {{User|Stitch123}}
* {{User|Vertaalbirdy}}
* {{User|webmiep}}
* {{User|webcatsolutions}}
* {{User|willoweb}}
* {{User|wimstrik}}

=== pl - Polski - Polish ===
* {{User|Derek}}
* {{User|justyna}}
* {{User|MiloW}}
* {{User|Zwiastun}}

=== pt - Português - Portuguese ===
* {{User|Djesus}}
* {{User|Horus_68}}
* {{User|Lampreia Lopes}}
* {{User|Mansil}}
* {{User|Nunof}}
* {{User|NunoLopes}}
* {{User|Ricardo.fusco}}

=== pt-br - Português Brasil - Brazilian Portuguese ===
* {{User|Airton}}
* {{User|alangustavo}}
* {{User|AleMorettiSan}}
* {{User|Anabarcellos}}
* {{User|Ariadnepinheiro}}
* {{User|Belisards}}
* {{User|Dagoberto}}
* {{User|DiLeu}}
* {{User|Filipetorres}}
* {{User|Gleisonsoares}}
* {{User|Helvecio}}
* {{User|Henrydouglas}}
* {{User|Jeann Wilson}}
* {{User|Juliano.freitas}}
* {{User|Murilotimo}}
* {{User|VitorAdonai}}
* {{User|Vizetti}}
* {{User|Welkson Ramos}}

=== ro - Română - Romanian ===
* {{User|andreeastefan}}
* {{User|isac}}
* {{User|Dudi161}}

=== ru - Русский - Russian ===
* {{User|AlexSmirnov}}
* {{User|Antonio3}}
* {{User|b2z}}
* {{User|cadko}}
* {{User|Cronolio}}
* {{User|Dosfanat}}
* {{User|Dzandut}}
* {{User|Igor}}
* {{User|Kanta}}
* {{User|Leo240}}
* {{User|Nikitm}}
* {{User|Nikolice}}
* {{User|Serg SSN}}
* {{User|Vyatka}}
* {{User|Yambergaa}}

=== si - සිංහල - Sinhala ===
* {{User|Yasirunilan}}
* {{User|Supun}}

=== sk - Slovenčina - Slovak ===
* {{User|adambako}}

=== yu - Srpski (Latin) - Serbian (Latin) ===
* {{User|novii}}

=== sr - Српски (Ћирилица) - Serbian (Cyrillic) ===
* {{User|novii}}

=== sv - Svenska - Swedish ===
* {{User|Propellerhuvud}}
* {{User|Sgagner}}

=== sw - Kiswahili - Swahili ===
* {{User|Ayeko}}

=== th - ไทย - Thai ===
* {{User|Supachai_chai}}
* {{User|Mrs.siam}}
* {{User|Ariesanywhere}}

=== tr - Türkçe - Turkish ===
* {{User|Ugur}}
* {{User|Umitkenan}}

=== ukr - Українська - Ukrainian ===
* {{User|Olesya6968ak}}
* {{User|sera527}}
* {{User|trv}}

=== ur - ur-PK - اردو - Urdu Pakistan ===
* {{User|hoornayyer}}

=== vi - Tiếng Việt - Vietnamese ===
* {{User|huyhoa}}

=== zh - 中文 - Chinese ===
* {{User|asika32764}}
* {{User|eyesofkids}}
* {{User|Guozhanfeng}}
* {{User|KellyXYM}}
* {{User|lai32290}}
* {{User|Mori0725ken}}
* {{User|myskies}}
* {{User|Wulijun01234}}
* {{User|Zace}}
* {{User|Zhang19min88}}
* {{User|Zhous98}}

=== zh-tw - 繁體中文 - Traditional Chinese ===
* {{User|Yuhoward}}

==Translation Administrators==

The responsibilities of a Translation Administrator will require slightly more attention to the documents for translation. Translation Administrators should feel comfortable with using wiki markup, made hundreds of contributions to their specific language and assisted others in translation of docs. Administrators will need to check the documentation every few days and perform any required tasks. These tasks include re-marking pages in en-GB with edit changes, tracking language units which need translation and welcoming new translators. Ideally, we should have at least one Translation Administrator who will not be tied to any specific language and when the time comes, one Translation Administrator for active language teams.

===Current Volunteer Translation Administrators===
{{:Special:ListUsers/translationadmins}}

==Common Language Codes==
<div class="small-4 columns"> afr - Afrikaans - Afrikaans
</div><div class="small-4 columns"> ar - عربي - Arabic
</div><div class="small-4 columns"> be - Беларуская - Belarusian
</div><div class="small-4 columns"> bg - Български - Bulgarian
</div><div class="small-4 columns"> bn - বাংলা - Bengali
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan
</div><div class="small-4 columns"> ca - Català - Catalan
</div><div class="small-4 columns"> ce - Nohçi - Chechen
</div><div class="small-4 columns"> da - Dansk - Danish
</div><div class="small-4 columns"> de - Deutsch - German
</div><div class="small-4 columns"> es - Español - Spanish
</div><div class="small-4 columns"> fa - فارسی - Persian
</div><div class="small-4 columns"> fi - Suomi - Finnish
</div><div class="small-4 columns"> fr - Français - French
</div><div class="small-4 columns"> hu - Magyar - Hungarian
</div><div class="small-4 columns"> hy - Հայերեն - Armenian
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian
</div><div class="small-4 columns"> is - Íslenska - Icelandic
</div><div class="small-4 columns"> it - Italiano - Italian
</div><div class="small-4 columns"> ja - 日本語 - Japanese
</div><div class="small-4 columns"> ko - 한국어 - Korean
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam
</div><div class="small-4 columns"> mr - मराठी - Marathi
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay
</div><div class="small-4 columns"> nl - Nederlands - Dutch
</div><div class="small-4 columns"> pl - Polski - Polish
</div><div class="small-4 columns"> pt - Português - Portuguese
</div><div class="small-4 columns"> pt-br - Português do Brasil - Brazilian Portuguese
</div><div class="small-4 columns"> ro - Română - Romanian
</div><div class="small-4 columns"> ru - Русский - Russian
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók
</div><div class="small-4 columns"> sq - Shqip - Albanian
</div><div class="small-4 columns"> sv - Svenska - Swedish
</div><div class="small-4 columns"> sw - Kiswahili - Swahili
</div><div class="small-4 columns"> ta - தமிழ் - Tamil
</div><div class="small-4 columns"> th - ไทย - Thai
</div><div class="small-4 columns"> tr - Türkçe - Turkish
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese
</div><div class="small-4 columns"> zh - 中文 - Chinese
</div><div class="small-4 columns"> zh-tw - 繁體中文 - Traditional Chinese
</div>

<noinclude>
[[Category:Documentation Wiki Policies and Guidelines]]
[[Category:Documentation Translation]]
</noinclude>