We have moved!

You are currently looking at documentation for Umbraco 8 and older versions.
Go to docs.umbraco.com for documentation for Umbraco 9 and newer versions.

    Creating a Package

    This tutorial is for Umbraco 8 - however a lot of the things covered here will be the same or similar in Umbraco 7.

    The goal of this tutorial will be to take something that extends Umbraco and create it as a package. The tutorials starting point will be creating a package out of the dashboard from the Creating a Custom Dashboard tutorial. The process will be the same for most packages so feel free to follow along with something else.

    Creating a package in the backoffice

    If you have something you want to make into a package, you can do so through the Umbraco backoffice.

    First go to the Packages section and select Created in the top right corner. Next, choose the Create package button.

    Buttons to select for creating a package in the backoffice

    On the Create package page there are 4 sections with different info to fill out. Some of the info is mandatory, most of it is not. First of all you should give the package a name at the top - we will call our dashboard the same as in the tutorial: Custom Welcome Dashboard.

    The Package Properties section

    This section contains mostly meta data about the package and the creator. We will fill in the following things:

    Property Value Note
    Url https://umbraco.com This url will be shown as the "packages url" when others install it. Will mostly be a Github repo or similar
    Version 1.0.0 This is automatically set to 1.0.0 but can be changed or increased manually if needed
    Icon Url Blank Not a mandatory value, but will appear as the package icon different places in the backoffice if set
    Umbraco version 8.2.0 It will automatically select the Umbraco version you are currently using. This is then set as the compatible version for the package
    Author Your name Here you get to take credit for your awesome work!
    Author URL Your website or maybe Twitter tag Will link to this from the author name certain places in the backoffice
    Contributors Blank Here you can add the names of other contributors if you have any
    License MIT License Will be set to MIT by default. Please consider how you want your package licensed. If in doubt when deciding an open-source license there are good resources available.
    License URL http://opensource.org/licenses/MIT Will be set to the URL for the MIT license, can be changed as needed
    Package readme This will add a dashboard to your content section.

    The dashboard will show each user the most recent nodes they have saved.
    This will be shown when someone looks at the package in the package dashboard

    The Package Content section

    This section is used to determine which things the package should contain. We will fill in the following things:

    Property Value Note
    Content Empty Here you can include content - fx if you want to create a starter kit. Not relevant for this package though
    Document Types Empty Similar to the Content picker above. Important to note that if you include content you will need to also pick all its dependencies in this and the next steps for it to be packaged together!
    Templates Empty See Document Types above
    Stylesheets Empty This will come from the ~/css folder. If you have stylesheets you want to include from other locations you can do so at a later step
    Macros Empty See Document Types above
    Languages Empty See Document Types above - all text is hardcoded or within our own lang folder in this package, so this is not needed
    Dictionary Empty See Document Types above
    Data Types Empty See Document Types above

    The Package Files section

    In this section you will be able to select all of your own custom files. We will start with the Path to file option.

    Since everything in our Dashboard is from the same folder in App_Plugins, we can select the folder and it will include all items inside that folder:

    Selecting the files you want in your package

    We will leave the Package options view selector empty, but in case you were wondering you can select an HTML file here that will show up as package options. Here is an example from the package Articulate:

    Gif of Articulates use of Package options

    The Package Actions section

    Here you can add package actions. There are a number of default package actions and you can also create your own custom package actions

    Finally after filling out all the info we can select Create to create the package. We will download it, in order to take a closer look at what it contains in the generated zip file.

    Inspecting a package zip

    When you download and then open the zip package you will find that it looks like this:

    Content of a zip package

    The 5 highlighted files were the ones the package contained that we created in the Creating a Custom Dashboard tutorial, however there is another file here called package.xml - so let's take a look at that - it looks like this:

    <?xml version="1.0" encoding="utf-8"?>
          <name>Custom Welcome Dashboard</name>
          <license url="http://opensource.org/licenses/MIT">MIT License</license>
          <requirements type="Strict">
          <name>Jesper Mayntzhusen</name>
        <readme><![CDATA[This will add a dashboard to your content section. 
    The dashboard will show each user the most recent nodes they have saved.]]></readme>
      <DocumentTypes />
      <Templates />
      <Stylesheets />
      <Macros />
      <DictionaryItems />
      <Languages />
      <DataTypes />
      <Actions />

    You will notice that each of the fields we created is inside this XML file. All files have an orgPath attached to it - this is where it will try to move the file to when installing it. So, don't worry if you organized your package in folders and they are not so in the zip.

    It is very important to get the included files right, as all dependencies will be needed for something to work in your package. On the other hand everything included here will be deleted on uninstall, so you also have to make sure not to include unnecessary things!