Before we dive into the new workflow, here are a few notes on everyone’s recap styles. These should help us work more smoothly in Chapter 3—and ideally keep things updated daily and on time:

• If an event is covered in multiple POVs (like dungeons or parties) and it's not central to your POV, keep it brief. A short mention or general summary is enough.
• Focus on what’s essential or genuinely funny.
• Don’t include every single interaction with other POVs—just the ones that actually matter.
• Avoid making your recaps too "listy." A well-paced recap with fewer but meaningful moments is better than a bullet list of events with minimal context.
• Remember: this is a recap, not a transcript. You don’t need to cover absolutely everything.

• Don’t write your recap first and add timestamps later. Drop in your timestamps as you write—otherwise it’s easy to forget and annoying to backtrack.
• Keep a bullet-point list of timestamps on the side as you go. You should already have a mental map of your timeline when drafting your recap.

---

We’ve moved from HackMD to GitHub for better version tracking and syncing. The structure here is more formal, so please follow these guidelines when submitting recaps.

If you're already comfortable with Git—cloning a repo and working locally—this will be straightforward, but you should still read through everything.

All recap work should be done on the recap branch. Walt and I will handle merging into the live site.

Recaps live in /recap-data, sorted by chapter and day folders:

To create a new recap, make a .md file in the correct folder.

Naming format:

• Node recaps: liz-c2d5, nerissa-c2d8, gigi-c2d4
• Edge recaps: liz-nerissa-c2d5, gigi-cecilia-c2d7

⚠️ Names (liz, nerissa, etc.) must come from the official list in Notes. No made-up names.

Node recaps go in the nodes folder. Edge recaps go in the edges folder.

---

• Write your recap in Markdown. Use the Preview tab to check formatting.

  • You can draft it in a preferred editor (or HackMD) and paste it in when ready.

• When done, click “Commit changes.” Add a short, clear commit message—think of it like a title or changelog:

  • Examples: added liz-c2d8, updated title for liz-nerissa-c2d3

To update a recap:

---

Some tag formats have changed (Chapter 2 has already been updated—you don’t need to revise old entries).

• [Title](#node:name) Example: [Elizabeth](#node:liz)

• [Title](#edge:name1-name2) Example: [Elizabeth-Nerissa](#edge:liz-nerissa) Just write the title as [Elizabeth-Nerissa]; no need to include the relationship name—it will autofill on the site.

⚠️ Always use the official names from the provided list.

---

• Big Timestamp → [Title](#embed:timestamp url)
• Small Timestamp → [Title](timestamp url)
• External Links → [Title](link)

---

For relationship cards, always include the title as a comment at the top of the file (keyboard shortcut: Ctrl + /) , with the "title:" part as well:

---

That’s it! Have fun archiving!