marcel/familienarchiv
1
0
Fork 0
Code Issues 119 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

feat(lesereisen): Lesereise reader UI — curated document journey viewer #786

New Issue
Closed
opened 2026-06-08 12:47:03 +02:00 by marcel · 0 comments
marcel commented 2026-06-08 12:47:03 +02:00
Owner
Copy Link

Context

Issue #750 introduced the data model: GeschichteType.JOURNEY, JourneyItem entity, and V72 migration that replaces the old geschichten_documents junction table.

This issue implements the reader-facing UI for a Lesereise — a curated, ordered sequence of documents with editorial notes.

Goal

When a Geschichte has type: JOURNEY, the reader sees a step-by-step journey through documents rather than a prose story. Each stop (JourneyItem) shows the document thumbnail, title/date metadata, and an optional editor note. Clicking a stop opens the full document.

Acceptance Criteria

Reader view (/geschichten/[id])

  • If g.type === 'JOURNEY', render a journey layout instead of the prose layout
  • Each JourneyItem that has a documentId shows:
    • Document thumbnail (if available)
    • Document title (fetched from the document record — not "Open document" placeholder) and date
    • item.note as editorial caption (if present)
    • Link to /documents/[documentId]
  • Items without a documentId (note-only stops) show the note as a standalone editorial paragraph
  • Items are displayed in position order (backend already returns them ordered)
  • Empty journey (no items) shows a placeholder message

Note: The current placeholder text "Dokument öffnen" / "Open document" shipped in #750 as a known stopgap. This issue must replace it with the actual document title before the reader experience can be considered complete.

Editor view (/geschichten/[id]/edit)

  • If g.type === 'JOURNEY', show the JourneyItem editor panel alongside the prose editor (prose body becomes optional/hidden for JOURNEY type)
  • Add item: pick a document from DocumentMultiSelect or write a note-only item
  • Reorder items: drag-and-drop or up/down arrow buttons
  • Remove item: trash icon with confirmation
  • Save persists items via the backend API (new endpoint needed — see below)

Backend (new endpoint)

  • PUT /api/geschichten/{id}/items — accepts List<JourneyItemDTO> with {position, documentId?, note?}, replaces the item list atomically
  • Validates CHECK constraint (documentId or note must be present)
  • Returns updated Geschichte (with items initialized)
  • Requires WRITE_ALL permission

Type toggle (create/edit)

  • GeschichteEditor gains a type selector: STORY (default) / JOURNEY (Lesereise)
  • Switching to JOURNEY shows the items panel; switching back to STORY hides it (items preserved server-side)

Out of scope

  • Mobile-optimised journey layout (tracked separately)
  • Journey analytics / reading progress
  • Public/shareable journey links

Depends on

Closes / follows on from #750

## Context Issue #750 introduced the data model: `GeschichteType.JOURNEY`, `JourneyItem` entity, and V72 migration that replaces the old `geschichten_documents` junction table. This issue implements the reader-facing UI for a Lesereise — a curated, ordered sequence of documents with editorial notes. --- ## Goal When a `Geschichte` has `type: JOURNEY`, the reader sees a step-by-step journey through documents rather than a prose story. Each stop (JourneyItem) shows the document thumbnail, title/date metadata, and an optional editor note. Clicking a stop opens the full document. --- ## Acceptance Criteria ### Reader view (`/geschichten/[id]`) - [ ] If `g.type === 'JOURNEY'`, render a journey layout instead of the prose layout - [ ] Each `JourneyItem` that has a `documentId` shows: - Document thumbnail (if available) - **Document title** (fetched from the document record — not "Open document" placeholder) and date - `item.note` as editorial caption (if present) - Link to `/documents/[documentId]` - [ ] Items without a `documentId` (note-only stops) show the note as a standalone editorial paragraph - [ ] Items are displayed in `position` order (backend already returns them ordered) - [ ] Empty journey (no items) shows a placeholder message > **Note:** The current placeholder text "Dokument öffnen" / "Open document" shipped in #750 as a known stopgap. This issue **must** replace it with the actual document title before the reader experience can be considered complete. ### Editor view (`/geschichten/[id]/edit`) - [ ] If `g.type === 'JOURNEY'`, show the JourneyItem editor panel alongside the prose editor (prose body becomes optional/hidden for JOURNEY type) - [ ] Add item: pick a document from `DocumentMultiSelect` or write a note-only item - [ ] Reorder items: drag-and-drop or up/down arrow buttons - [ ] Remove item: trash icon with confirmation - [ ] Save persists `items` via the backend API (new endpoint needed — see below) ### Backend (new endpoint) - [ ] `PUT /api/geschichten/{id}/items` — accepts `List<JourneyItemDTO>` with `{position, documentId?, note?}`, replaces the item list atomically - [ ] Validates CHECK constraint (documentId or note must be present) - [ ] Returns updated `Geschichte` (with items initialized) - [ ] Requires `WRITE_ALL` permission ### Type toggle (create/edit) - [ ] `GeschichteEditor` gains a `type` selector: STORY (default) / JOURNEY (Lesereise) - [ ] Switching to JOURNEY shows the items panel; switching back to STORY hides it (items preserved server-side) --- ## Out of scope - Mobile-optimised journey layout (tracked separately) - Journey analytics / reading progress - Public/shareable journey links --- ## Depends on Closes / follows on from #750
marcel added this to the Lesereisen (Reading Journeys) milestone 2026-06-08 12:47:03 +02:00
marcel added the P1-highfeature labels 2026-06-08 12:47:44 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-critical
Blocks a core user journey, causes data loss, or is a security/accessibility barrier. Work on this before P1+.
 P1-high
Significant friction on a main user journey; workaround exists but is non-obvious. Next up after P0.
 P2-medium
Noticeable improvement; doesn't block anything; schedule opportunistically.
 P3-later
Cosmetic or parking-lot work; fine to stay open indefinitely.
 audit
Read-only audit / assessment work; produces a report rather than changing code
 bug
Something isn't working
 cleanup
Removal of dead code, vague comments, naming violations, and scratch artifacts
 collaboration
We want to extend the family archive to have more collaboration tools
 conversation
descoped
We will do that later
 devops
documentation
README, ARCHITECTURE, GLOSSARY, CONTRIBUTING, per-domain docs
 epic
Marker for epic-level issues that group multiple child issues
 feature
file-upload
legibility
Codebase Legibility Refactor — preparing the codebase for human evaluation and bus-factor reduction
 needs-discussion
Has an open decision or design question that must be resolved before implementation can start.
 notification
person
phase-1: security
Security hygiene — must be done first
 phase-2: container-images
Production-ready multi-stage Docker images
 phase-3: prod-compose
Production compose overlay + Caddy reverse proxy
 phase-4: spring-prod-profile
Spring Boot production configuration profile
 phase-5: backups
Database and object storage backup strategy
 phase-6: deployment-docs
.env.example, DEPLOYMENT.md, runbook
 phase-7: monitoring
Prometheus, Loki, Grafana, Alertmanager
 refactor
Code restructuring without behaviour change
 security
test
ui
UI/UX and accessibility issues
 user
No Label P1-high feature
Milestone
No items
No Milestone Lesereisen (Reading Journeys)
Projects
Clear projects
No project
Assignees
Clear assignees
Jens marcel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#786
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?