Overview ID: PM-CP-O

Packages are created using the same interfaces and dialogs that the rest of the Marketpath CMS UI uses. But there are a number of additional considerations and improvements to be aware of where packages are concerned. Armed with a little information, you can begin creating packages in no time. This and all following modules are only recommended for developers, who are recommended to complete the Developer Basic Training Course first in order to have a thorough understanding of Marketpath CMS from a developer’s point of view.

In the following lessons in this module we will cover topics related to creating and managing packages:

1. Tasks and decisions to complete before creating the package
   1. Package composition - assets and dependencies
   2. Demo and documentation pages
   3. Access control - public vs private packages - and how to share packages
2. Creating a package
   1. How to begin package creation
   2. Pointers on what makes for a good package
   3. Naming, descriptions, labels, and more
   4. Caveat for full site packages
3. Assets and dependencies
   1. Interface overview
   2. Options for managing assets and dependencies
   3. Shortcuts for adding assets
   4. How to get back to the assets and dependencies interface
4. Pre-activation and activation
   1. Setting the version and changelog
   2. What happens during pre-activation and why it is important
   3. Final actions before activating your new version
   4. Activating your new package
5. After activation
   1. What to expect after activating your package
   2. Creating a new version
   3. Removing old versions
   4. Managing changelogs and more

---

---