Project document
App Flow
How a reader moves through ub3r, from first visit to finishing a series.
Primary flow
- Entry: a reader lands on the home page from a link or search.
- Home: they start the first chapter or open the featured series.
- Series: they read the chapter list and check prerequisites on the map.
- Chapter: they read, run playgrounds, toggle diffs and join the discussion.
- Celebration: at 80% scroll the chapter completes; the gold check plays and progress updates everywhere.
- Next: the next-chapter card continues the series; the last chapter points back to the library.
Returning reader
On return the home call to action reads "Continue learning" and the strip lists every partially completed series with its next unread chapter.
Routing map
/ Home
/library Library (filters + search)
/series/:slug Series overview + prerequisite map
/series/:slug/:chapter Chapter reader
/docs Project docs index
/docs/:doc prd | trd | app-flow | design-brief | background-schema | implementation-plan
* 404Edge cases
- Direct link to a chapter whose prerequisites are unread: allowed; the series page shows the requirement but never blocks.
- Completed chapters can be marked unread, which allows the celebration to replay.
- Playground errors and timeouts appear inline in the output panel and never break the page.