32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
|
---
|
||
|
|
# nuzlocke-tracker-mz16
|
||
|
|
title: Session Journal / Blog Posts
|
||
|
|
status: draft
|
||
|
|
type: epic
|
||
|
|
created_at: 2026-02-19T07:43:05Z
|
||
|
|
updated_at: 2026-02-19T07:43:05Z
|
||
|
|
---
|
||
|
|
|
||
|
|
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.
|
||
|
|
|
||
|
|
## Open Questions
|
||
|
|
|
||
|
|
- [ ] What editor experience? (Markdown, rich text, block editor?)
|
||
|
|
- [ ] How are images stored? (Local uploads, external links, cloud storage?)
|
||
|
|
- [ ] What run events can be linked/embedded? (Team snapshots, deaths, catches, badge progress?)
|
||
|
|
- [ ] Should posts be publishable/shareable, or private by default?
|
||
|
|
- [ ] How does the journal UI look? Timeline view? Blog-style list?
|