--- title: "Presentation" slug: "concepts-presentation" updated: 2026-05-11T14:37:47Z published: 2026-05-11T14:37:47Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.deltatre.com/llms.txt > Use this file to discover all available pages before exploring further. # Presentation This article introduces the presentation side of FORGE. --- ## FORGE Presentation FORGE Presentation covers organizing content inside digital channels (browser, app, etc.). Producers are responsible for FORGE Presentation, with *pages* as the key concept. ## Pages: Organization and structure ![PageBuilder-Page.jpg](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/13877881492508.jpg) ### Assets Assets are the page's building blocks; there are three available asset types: 1. Template: Templates structure pages by *slots*, including header, footer, and body: ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/10497788369436.png) Templates contain *slots* that contain layouts and modules: ![PageBuilder-Page2.jpg](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/13877881502108.jpg) 2. Layout: Layouts structure pages by splitting them out into a series of columns. Grid layouts make sure that added modules align with the design of the digital product: ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/10497795346844.png) Layouts contain *slots* that contain layouts and modules: ![PageBuilder-Layout.jpg](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/13877890246812.jpg) 3. Modules: Connects the page with content. Each module is specialized per content type (e.g., stories or photo albums) and describes the content and how it should be displayed in the front-end. For example, the *Story* module shows a story with a specific slug and describes how it displays in the front-end: ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/10188170876060.png) The module's position within a template and layout determines where the story displays on the page. ### Microcopy The FORGE Vocabulary Tool app helps producers manage *terms* (user interface copy). The phrase *terms* refer to the app's [microcopy](https://xd.adobe.com/ideas/process/information-architecture/four-cornerstones-writing-ux-microcopy/), rather than the editorial content. For example, '*Follow us on social media'* or short headers like '*Latest News**', or 'Top Stories'*: ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/10188239027356.png) Producers can use the FORGE Vocabulary Tool to do the following: 1. Manage, edit, and update terms. 2. Translate terms into multiple languages. 3. Use a Comma-Separated Values (CSV) file to upload a list of terms in one go (this saves considerable time). ### Folders Producers can group pages in folders to improve navigation and help with maintenance and project evolution. Find more information in [Folders and pages](/v1/docs/folders-and-pages). ## Pages: URL parameters The page name can contain parameters, which curl brackets enclose. E.g., parameter *{slug}* within ~/_a_big_fan_of_alpha/website/archive/*{slug}* Parameters within the page name can be used to value parameters of modules within the same page. In the example below, the *{slug}* parameter in ~/_a_big_fan_of_alpha/website/archive/*{slug}*, dynamically values the *Article slug* parameter of the *Common-Article* module. On the front-end, the result is that page ~/_a_big_fan_of_alpha/website/archive/*{slug}*with *slug = intro-to-alpha* - Has the URL ~/_a_big_fan_of_alpha/website/archive/*intro-to-alpha* - Renders the story with the slug=*intro-to-alpha* ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/13173466869532.png) ## Pages: Variables and permissions ![PageBuilder-Page3.jpg](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/13877881523100.jpg) ### Variables Variables change what a page displays on the front-end. Pages can inherit variables from parent folders: by default, variables' value is also inherited, but editors can override it. An example is allowing the producer to set the *header/footer* variable, which displays on the desired pages. Three types of variables include: 1. **Key value**: The most used editable variables, including *header* and *footer*. A *Key value* item is a couple key/value. 2. **Data item**: Allows web producers to reuse FORGE entities, for example, a news story to display on a selection of web pages. 3. **List item**: Allows web producers to display a list of entities on a selection of web pages. Each variable has a scope, which controls the pages the variable displays on: - **Inherited**: An inherited variable is applied to every page inside a specified folder. - **Local**: A local variable only usable on the current page and does not display across multiple pages. - **Overwritten**: An overwritten variable allows web producers to change the value of an inherited variable only for the current page. Overwritten variables can be restored to return to an inherited value. ### Permissions Administrators define permissions and assign them to producers, making visible only what's required. ## Editorial workflow Producers manage pages through a set of statuses that describe their availability to be delivered to the front end: - **Published**: The page is in a published state and is visible on the front-end. - **Not published**: The page is in a draft state and is not visible on the front-end.