Creating Module Content Pages
A page is a Markdown file — this is where most of a module's actual text lives: chapters, encounters descriptions, GM notes, whatever your module needs.
In the Module section's title bar, click the Create Page icon. Unlike the original Module Packer, this doesn't create a page immediately — a prompt appears asking for a name first (pre-filled with "New page", which you can keep or replace). Confirm it, and MPX creates pages/<slug>.md and opens it.
Every page starts with a block of metadata, before the content:
---
name: "Chapter 1: The Approach"
slug: chapter-1-the-approach
rank: 0
parent:
---
| Field | Required | Format | Purpose |
|---|---|---|---|
name |
Yes | Text | The page's display name. |
slug |
Yes | lowercase, digits, hyphens only | Generated from name at creation. Used to link to this page and to set it as another item's parent. |
rank |
Yes | Number | Order among its siblings (other items sharing the same parent). Lower comes first. |
parent |
No | A page's or group's slug, or empty |
Leave empty for a top-level page, or set it to nest under that page or group. A map or encounter can't be a parent. |
There's no in-editor autocomplete for these four fields — set them by hand.
Everything after the closing --- is plain Markdown: headings, lists, tables, images, links to other pages. A few things worth knowing early:
- Snippets insert common formatting fast — colored blockquotes, tables, images with captions — instead of typing the syntax from memory.
- Linking to another page uses its slug:
[Chapter 2](chapter-2-the-lighthouse). - An image goes in
images/at the project root and is referenced as. - Compendium content — an item, spell, monster, or roll table — can be written directly inside a page. See Managing the Compendium.
Open the built-in Markdown preview (the icon at the top right of the editor) to see roughly how the page will actually look in EncounterPlus, using your project's theme. See Building and Importing for more on the preview and what changes once you actually build.
Groups — organize pages (and maps, and encounters) into a hierarchy.