Packaging German Translation Add-on for WordPress

This chapter describes creation of an APS package containing a German translation for Wordpress. Here we will refer to a translation as an add-on – an APS package adding extra functionality to another (master) APS package. You may also use this brief guide to create add-ons for any other applications. Before you create your first APS package, you are recommended to familiarize with the packaging procedure for a master package (see Packaging WordPress Application):

Listed below are the sections of APP-META.xml file supplied with the add-on package:

Type of Environment. A translation is attached to all instances of Wordpress, therefore it belongs to shared type.
Model of Service Provisioning. A translation should be provisioned as a single-tenant application, because Wordpress add-ons are configured for each Customer according to his specific demands.
Services hierarchy. A translation is represented as a single service and appears in the following way:
```
<service id="de-lang">
```
Used technologies. The add-on does not impose any requirements for any specific technologies, rather relying on the master application (Wordpress).

Presentation details and settings. The representation details include the supported add-on version, changelog, application category and the language.

<presentation>

	<summary>German translation for WordPress</summary>

	<changelog>

		<version version="2.9.1" release="1">

			<entry>German translation for WordPress is packaged.</entry>

		</version>

	</changelog>

	<categories>

		<category>Theme</category>

	</categories>

	<languages>

		<language>de</language>

	</languages>

</presentation>

To switch Wordpress to German, add the following setting:

<setting id="replace_current_lang" type="boolean" default-value="true">

	<name>Activate language</name>

</setting>

Content delivery. German translation comprises a number of files which are placed to the same path where WordPress resides. This means that the WordPress add-on belongs to the Inside Package content delivery type.
```
<provision>
```
```
	<url-mapping>
```
```
		<installed-size>1794048</installed-size>
```
```
		<mapping url="/" path="htdocs"></mapping>
```
```
	</mapping>
```
```
	</url-mapping>
```
```
</provision>
```

Metadata file. Now it is time to make a draft of the add-on application metadata file. Describe application general information in the Specification terms, and also the id of the master package ("") to which this translation should be applied.

Create an APP-META.xml file and begin with adding general details as follows:

<id>http://de.wordpress.org/</id>

	<name>German Translation</name>

	<version>3.0.5</version>

	<release>1</release>

	<homepage>http://de.wordpress.org/</homepage>

	<master-package>

		<package id="http://wordpress.org/">

	</master-package>

	<vendor>

		<name>wordpress</name>

		<homepage>http://de.wordpress.org/</homepage>

	</vendor>

	<packager>

		<name>Parallels</name>

		<homepage>http://parallels.com/</homepage>

		<icon path="images/icon.png" />

		<uri>uuid:714f0a7b-85d6-4eb8-b68e-40f9acbb3103</uri>

	</packager>

Editing configuration script. Create a configuration script that performs configuration and removal of the add-on. Configuration script should perform registration of the translation file in Wordpress. For list of environment variables, refer to the Sample Environment Variables section further in this guide.
Archiving application. Form application package pursuant to the requirements stated in the 4. Basic Package Format section of the Specification and archive it.

`APP-META.xml`	# Metadata container. XML file.
`scripts/`
`configure`	# This script will be invoked when the add-on is instantiated.
`images/`
`icon.png`	# Add-on Icon
`htdocs/`	# Translation files