The user creates a new package node just like he is used to when creating a new content page using “right click” -> New.

After opening the node (“right click” -> Open) he sees a summary of the package's definition.

As this is a new package the page will be almost empty. So click "Edit definition" and you can change the package definition.

You can give additional information on the package. This is important if you want to pass the package to someone else for deployment:

• Title: a descriptive title
• Description: should reflect the package's content
• Restart is necessary: If checked the user will be informed after installing the package
• Release note: give additional information (like dependencies, ...)

To define the package's  content switch to the "Rules" section where you can define rules to include and exclude parts of repositories or the web application.

Let's create a package which stores everything you need for the preinstalled "features" web pages of Magnolia:

• website: Include (this and sub nodes) /features
• config: Include (this and sub nodes) /modules/templating/templates/samples
• config: Include (this and sub nodes) /modules/templating/dialogs/samples
• config: Include (this and sub nodes) /modules/templating/paragraphs/samples
• files: Include (this and sub nodes) /templates/samples

When defining the paths you can use the tree browser of the repositories which are available for important repositories. If for a certain repository there is no tree browser you will see an exception. You can enter the path directly in that case.

Click "Save" and the package definition will be updated to reflect the changes.

You see the rules created to specify the package's content. Switch to "Statistics" and you will see the nodes / files to be included if you download the package using the "Backup" feature in AdminCentral.