From 53f259243e1bb3c054350127f19711bc566badd8 Mon Sep 17 00:00:00 2001 From: Marcel Date: Tue, 9 Jun 2026 16:31:34 +0200 Subject: [PATCH] docs(glossary): add Interlude/Zwischentext entry Interlude is a first-class editorial concept introduced by the JourneyEditor (#753): a note-only JourneyItem with no backing document, stored in the note column and distinguished visually by --color-interlude-* CSS tokens. Co-Authored-By: Claude Sonnet 4.6 --- docs/GLOSSARY.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/GLOSSARY.md b/docs/GLOSSARY.md index e38eb070..65e902b8 100644 --- a/docs/GLOSSARY.md +++ b/docs/GLOSSARY.md @@ -159,6 +159,9 @@ _See also [Chronik](#chronik-internal)._ **DocumentSummary** (`DocumentSummary`) `[internal]` — lean document read-model used inside `JourneyItemView`. Contains title, date, senderName, receiverName, receiverCount, datePrecision — no tags or file storage info. +**Interlude / Zwischentext** `[user-facing]` — an editorial paragraph inserted between document items in a *Lesereise*. An interlude is a `JourneyItem` with `document_id IS NULL` and a non-empty `note`; its content is a plain-text string stored in the `note` column (not `body` or `text`). Visually distinguished by `--color-interlude-bg/border/label` CSS tokens and a `ZWISCHENTEXT` label. Interludes cannot have their note removed (removing the interlude deletes the entire item). +_Not to be confused with a document item's optional note_ — a document item's note is curator commentary attached to a linked letter; an interlude is standalone editorial prose with no backing document. + **Lesereise** `[user-facing]` — a curated reading journey through a sequence of family documents, optionally annotated with editorial notes. Implemented as a `Geschichte` with `type=JOURNEY`. The reader UI (follow-on issue) renders items as a sequential reading experience. **Notification** (`Notification`) — an in-app message delivered to an `AppUser`. No email or SMS delivery exists today. Delivered via Server-Sent Events (`SseEmitterRegistry`) and persisted in the `notifications` table.