Build your own

The branching scenario and theclue web are both generated from the same collection of scene files — nothing about either page names Blackwater Cove specifically. Swap in your own scenes and both views follow, which makes this a working preview of yourFinal Scenario submission, not just a demo to read past.

One file per scene

Each scene is a Markdown file under src/content/play/scenario/, frontmatter plus prose ending in a choice list. This is the whole schema:

title: string, required
start: true on exactly one scene — where scenario/index.astro sends readers
ending: "success" | "failure" | "ambiguous" — set only on a terminal scene
clues: a list of { id, name, redundancy, delivery }
  redundancy: "core" | "supporting" | "advantage"
  delivery:   "literature" | "social" | "trace"

redundancy and delivery are the same two taxonomies from Studio 6. A clue id that recurs across two scenes is exactly the redundant path the Investigation Architecture brief asks for — the clue web groups by that same id, so a redundant clue shows up once with both scenes linked underneath it.

A scene, stripped down

---
title: The Locked Cellar
clues:
  - id: workshop-key
    name: "The spare workshop key"
    redundancy: core
    delivery: trace
---

Two or three paragraphs of scene prose, ending on a choice.

**What do you do?**

- [Force the cellar door](/play/scenario/force-the-door/)
- [Go back upstairs instead](/play/scenario/upstairs/)

A terminal scene drops the choice list and clues, and addsending: success (or failure /ambiguous) instead.

Trying it yourself

1. Clone this repository and run pnpm dev.
2. Read a couple of the existing files undersrc/content/play/scenario/ as worked examples, then start replacing them with your own scenes — same folder, same schema.
3. Mark exactly one scene start: true.
4. Every choice link is an ordinary Markdown link to another scene's slug — the build's broken-link checker will flag a typo before it ships.
5. Run pnpm check. It typechecks the frontmatter against this schema, rebuilds both pages from your scenes, and re-checks links and accessibility.

None of this touches the graded assessment collections or the fixed course spec — playScenes is its own collection, kept out of both, so experimenting here can't put a real submission at risk.