Skip to content

Script of the Archives

“Clarity of script is clarity of memory.”

This guide shows the markdown you’ll actually use in the Grand Archives.
Anything more complex is optional flavour, not a requirement.


Every page in the Archives starts with frontmatter, a YAML block between --- lines:

---
title: "Session 03 — The Shattered Road"
description: "The party leaves Emberfall and realises the roads are no longer safe."
type: "session"
sessionNumber: 3
draft: true
---
  • title - what appears in the sidebar and at the top of the page.
  • description - short summary for search/preview.
  • draft: true - hide from the sidebar until it’s ready.

After the second ---, you write normal markdown.


Use # for headings. More # = smaller heading.

# Main Title (usually supplied by frontmatter)
## Section
### Subsection
#### Sub-subsection

Recommended pattern for sessions:

## Summary
## Cast
## Major Events
## Consequences
## Loot & Rewards

For lore/locations:

## Overview
## History
## Important Figures
## Hooks

_italic text_
**bold text**
**_bold and italic_**

Example:

The **Church of Sacro Elcarion** claims to serve the light, but its _methods_ suggest otherwise.

- First point
- Second point
- Indented sub-point
1. First step
2. Second step
3. Third step

Perfect for timelines and ordered events.


If you know the URL/slug:

See also: [Emberfall](/locations/cities-and-villages/emberfall/)
[Official D&D SRD](https://www.dndbeyond.com/)

Tables are great for NPCs, factions, loot, etc.

| Name | Role | Notes |
| ------------- | ------------------ | ----------------------------- |
| Elion | Archivist | Knows far too much. |
| Jora | Innkeeper | Owns the Ember Inn. |
| Father Malrec | Priest of Elcarion | Smiles too much at autopsies. |

Make sure the header row, separator row, and data rows all have the same number of | columns.


7. Code blocks (for mechanics, rolls, or technical notes)

Section titled “7. Code blocks (for mechanics, rolls, or technical notes)”

Use triple backticks ``` to create a fenced block:

```text
DC 15 Perception to notice the hidden sigil.
On a success: they sense they’re being watched.
On a failure: the sigil activates later, unnoticed.
```
(When writing this in a real file, remove the extra indentation/backticks around the example.)
You can also tag the block with a language like `bash`, `json`, etc. for technical notes.
---
## 8. Blockquotes (for in-world text or emphasis)
```md
> This is a blockquote.
> It can span multiple lines.

Example for lore:

> “The First Turning was not a blessing. It was a bargain.”
> — Fragment from the Ashen Tablets

Use three or more dashes:

---

Great for separating sections or scenes:

## Major Events
- The caravan is found destroyed.
- The only survivor speaks of pale lights in the fog.
---
## Consequences
- Trade prices in Emberfall spike.
- The Church quietly sends its own investigators.

If you later add maps or character art and store them under /public:

![Alt text for screen readers](/images/maps/emberfall-city-map.png)

Keep alt text short but descriptive.


---
title: "Session 05 — Into the Shattered Pass"
description: "The party braves the pass and discovers what stalks the old road."
type: "session"
sessionNumber: 5
---
## Summary
Brief recap of the session.
## Cast
- **Character** – role this session.
- **NPC** – how they were involved.
## Major Events
- Event 1
- Event 2
## Consequences
- Immediate fallout.
- Long-term repercussions.
## Loot & Rewards
- Gold, items, favours, information.
---
title: "Emberfall"
description: "Trade-city built around an ever-burning forge."
type: "location"
category: "city"
region: "Central Omain"
---
## Overview
High-level description and vibe.
## Districts
- **Forge Quarter** – industrial, noisy, hot.
- **Sky Market** – precarious walkways and rope bridges.
## Important Figures
- **Elra the Forgemaster** – controls most metalwork.
- **Jora** – innkeeper and information broker.
## Hooks
- Rumours, quests, reasons to come back.

If something looks strange in the rendered site:

  1. Check for missing closing " or --- in the frontmatter.
  2. Make sure headings start at ## (since the page title is already #).
  3. Ensure tables have the same number of columns per row.
  4. Avoid mixing tabs and spaces around list bullets.

If it still misbehaves, hand it to the Scribe (your dev friend) and blame the quills.

Your job is to remember the world. The markdown is just the script the Archives read.