Page model glossary

This article describes the various elements that are used on the pages of a Microsoft Dynamics 365 Commerce site.

Page element definitions

The following table provides a summary of terms that you should be familiar with when you change the look, feel, and content of your site. For more thorough explanations and procedures, follow the links.

Term Description and notes

Definition: Modules are building block that can be authored and make up the skeleton of a webpage. Examples include header, hero, and carousel modules.

Where it's selected: Deployed modules can be selected and configured in various stages of the site authoring workflow, such as the template, layout, page, and fragment authoring stages.

Where it's edited: Custom modules are created in code by using the software development kit (SDK). They are then uploaded to your site, where they become available for selection.

Module property

Definition: Module properties are specific settings that are defined by the module. They can be edited in the e-Commerce authoring tools. For example, module properties are used to set the heading and background image of a banner module.

Where it's configured: Module properties are selected and configured in the property pane that appears in the authoring environments (editors) for templates, layouts, pages, fragments, and app settings.


Definition: Templates define the module combinations and options that should be used for a category of pages (for example, marketing pages, category pages, and product pages).

Where it's selected: Templates can be selected during page or layout creation workflows.

Where it's edited: Templates are authored in the template editor. No code is required to create or modify them.


Definition: Layouts define the final selection and arrangement of modules from the parent template's set of options. A layout can be configured for a single page (custom layout), or it can be shared by multiple pages (preset layout).

Where it's selected: Layouts can be selected during new page creation or when a different layout is required for an existing page.

Where it's edited: Layouts are authored in the layout editor. No code is required to create or modify them.

Page instance

Definition: Page instances define the final, page-specific localized content for a single page. This content is derived from the values of module properties.

Where it's selected: Pages are selected when URLs are assigned.

Where it's edited: Pages are edited in the page editor. No code is required to create or modify them.


Definition: Themes define the Cascading Style Sheet (CSS), and determine the look and feel of the modules that are rendered on a page.

Where it's selected: After a theme is uploaded to your site by using Microsoft Dynamics Lifecycle Services (LCS), it can be selected as a property of the page container module.

Where it's edited: Themes are currently created and edited by using the SDK. They are then uploaded to your site by using LCS.


Definition: Fragments are fully configured modules that have localized content that can be reused and centrally updated across multiple pages. For example, a fragment that is created from a header module can be used in all templates and on all pages across your site, and centrally updated in one place.

Where it's selected: Fragments can be selected wherever modules can be selected. They can be substituted for a module to help increase efficiency through reusable and centralized authoring.

Where it's edited: Fragments are edited in the fragment editor. No code is required to create or modify them.


Definition: Uniform resource locators (URLs) are addresses that point to webpages or other URLs.

Where it's selected: URLs are selected if links between pages are required.

Where it's edited: URLs are edited in the URL editor. No code is required to create or modify them.


Definition: Assets are file binaries that have an extension such as .jpg, .docx, .pdf, or .mpg.

Where it's selected: Assets are selected as module properties for modules that require them.

Where it's edited: Assets are uploaded, and associated metadata is edited in the asset manager.

Additional resources

Ways to add content

Document states and lifecycle

Work with publish groups

Enable and use cross-channel sharing

Work with modules

Work with fragments

Templates and layouts overview

Customize site navigation