Marketpath Site Standards 1 (hereafter referred to as MPSS1) is a set of standards and requirements that allow the greatest interoperability between site themes, page templates, and components.
All packages that conform to the MPSS1 standard should also attempt to conform to the standards defined in the Marketpath CMS Package Development Guidelines. This is where many of the development and usability best practices are defined.
The standard used by each package should be noted by a label with the key of "standard" and a either a value of "mpss1" (eg: "standard=mpss1") or a framework-specific code if the package only applies to a specific framework for which an additional framework-specific standard has been created (eg: "standard=mpss1-bootstrap5").
Each full site package should have a single standard, which will be used by sites created from that package when locating new page packages to install (ie: do not have both standard=mpss1 and standard=mpss1-bootstrap5 on the same full site package).
An MPSS1 package may depend on other packages that are NOT MPSS1 packages (eg: data, component, widget, etc… packages) so long as they are also consistent with the interoperability guidelines defined in this document.
Content that is not essential to the functionality of the package should be included in the package as “Install Only” to make it as easy as possible for content editors to make changes without fearing that their changes will be overwritten or make package updates more complicated than necessary.
All MPSS1 full site packages should include the following assets:
Browser Title Guideline: When building full site MPSS1 packages, you should NOT modify the title or browser in the /_header.liquid template. Doing so would make it difficult for content editors - or other components for that matter - to customize those values and also makes the SEO preview in the page edit interface inaccurate.
The Browser Title Guideline only applies when creating full site (theme) packages - when implementing a custom MPSS1 website you may do as you wish, although there may still be issues when modifying the title and/or browser title globally across the site. The preferred way to customize the browser title is by setting the Default Browser Title Prefix and Suffix options in the Site Settings (which will apply to new pages) and editing the SEO properties of existing pages.
If an asset needs to be updated with a breaking change that is no longer compatible with the original asset:
You must include any license files and/or other assets required according to the original source inside your package. Place the assets as a template inside your root package path. If the asset does not have a name or extension, use a descriptive name and the .txt extension. Example: /marketpath/foundation6/LICENSE.txt
Note: There is no requirement that the license and/or other ancillary assets must be published unless they must also be consumable by end users.
If the terms of an agreement must be explicitly agreed to prior to installing the package on a site, include those terms in the package agreement. You should not have to include more than one agreement per package - if your package requires agreement to multiple terms and conditions then it should be separated into multiple packages with their own agreements.
Double-check that you have permission to distribute all images, documents, and other copyrighted content in each package before activating it.
The following changes have been made to the Package Development Guidelines: