Geschichten/Lesereise detail page renders flat on the canvas — article has no reading-sheet surface, page looks empty #797
Reference in New Issue
Block a user
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?
Problem
On
/geschichten/[id](both STORY and JOURNEY type), the article content sits directly on the sand canvas (--c-canvas#f0efe9) with no visual container. The page reads as flat and empty — especially for short stories where most of the viewport is bare canvas.The spec mockups show the article on a distinct light "reading sheet" panel:
docs/specs/geschichten-reader-journey-spec.html— R-2 mockup:.g-article=background:#FAFAF7; border-radius:6px; padding:16px 20px; max-width:640px; margin:0 autoon a darker#E8E7E2backdropdocs/specs/lesereisen-reader-spec.html— LR-2 inherits the same article container ("gleich wie StoryReader")Root cause of the deviation: the spec is internally inconsistent. The R-2 mockup shows the sheet panel, but the R-2 impl-ref table only specifies
max-w-3xl mx-auto px-4 py-10— no surface, border, or shadow. The implementation followed the impl-ref, so the sheet was never built.Fix
In
frontend/src/routes/geschichten/[id]/+page.svelte(single change covers both Story and Journey readers, including delete-error banner inside the sheet):BackButtonoutside the sheet (consistent with the rest of the app — back nav lives on the canvas).<article>in the standard card pattern from CLAUDE.md, translated to brand tokens:rounded-sm border border-line bg-surface shadow-smpx-5 py-6 sm:px-10 sm:py-10max-w-3xl mx-auto px-4 py-8.Dark mode needs no extra work —
bg-surface/border-lineare mode-aware tokens inlayout.css.Also
/geschichten/[id]/editand/geschichten/newvisually after the change — they should keep their current layout; this issue only targets the reader view.Acceptance criteria