Last updated: January 1, 2021

PageMaps define the contents, themes, and layouts of the action pages associated with a PageType. Settings are in the pageMaps.xml file, located within the PageType configs folder; e.g., /DB/pageTypes/[pageType]/configs (Themes and layouts are available in /libraries/layouts and /libraries/themes.)

The separation of content, themes (styles), and layouts always for various configurations of the user experience. For example, a PageMap associated with Layout A may render the content in the order of A, B, C. However, a PageMap associated with Layout B may render the content in the order of B, A, C. Using a similar example, Theme A may color the page red and Theme B may color the page blue.

Layouts and themes have assigned defaults for all PageType pages, but can be overridden within the scope of a page. For example, if a PageType has three action pages (display, manage, edit), they can all share the same themes and layouts by default. This eases the overhead with manual management since each action type does not need to be defined.

However, there are cases in which actions types may need to deviate from the default. For example, since manage and edit have very specific administrative functions, they can share the same page design; i.e., these are admin pages requiring the same UX. However, display may be used to show content to the general site user, and so, this may require its own layout and theme.

The actual areas are located within /DB/shared/areas, rather than a subfolder of the PageType’s data folder because content may be shared across PageTypes. For example, the admin header, nav, and footer may used across various PageTypes. The same is also true for user-facing PageTypes such as blogs and pages.