39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
---
|
|
# nuzlocke-tracker-mz16
|
|
title: Session Journal / Blog Posts
|
|
status: completed
|
|
type: epic
|
|
priority: normal
|
|
created_at: 2026-02-19T07:43:05Z
|
|
updated_at: 2026-03-20T15:37:21Z
|
|
---
|
|
|
|
Let users tell the story of their nuzlocke run through session journal entries (blog posts).
|
|
|
|
Nuzlockes are inherently story-driven — encounters you first think are weak become the star of the show, a needed sacrifice lets the run survive, one crit in a boss battle means defeat. Users should be able to capture those moments.
|
|
|
|
## Concept
|
|
|
|
For each play session, users can write a short post to document what happened. Posts can:
|
|
|
|
- Include rich text / markdown content
|
|
- Embed screenshots and images
|
|
- Automatically link to their current team (or a subset of it)
|
|
- Reference deaths, new encounters, and other run events
|
|
- Be tied to a specific run
|
|
|
|
The journal becomes a chronological narrative of the nuzlocke run, with game data woven in automatically.
|
|
|
|
## Decisions
|
|
|
|
- **Editor:** Plain markdown textarea with preview
|
|
- **Images:** Via markdown URL syntax (no uploads)
|
|
- **Run linkage:** Entries belong to a run, optionally linked to a boss battle
|
|
- **Visibility:** Private only (no sharing — deferred until user accounts exist)
|
|
- **Templates:** Blank slate — no templates
|
|
|
|
## Success Criteria
|
|
|
|
- [x] Backend: journal entries CRUD API is complete (`nuzlocke-tracker-vmto`)
|
|
- [x] Frontend: journal list, editor, and view are functional (`nuzlocke-tracker-d68l`)
|