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

Geschichten overview is narrower than the other directory pages — page looks inconsistent next to Dokumente/Personen #799

New Issue
Open
opened 2026-06-10 22:34:47 +02:00 by marcel · 1 comment
marcel commented 2026-06-10 22:34:47 +02:00
Owner
Copy Link

Problem

/geschichten uses max-w-4xl (896px) while the Dokumente search (/) and Personen overview (/persons) both use max-w-7xl (1280px). Switching between directory pages makes the Geschichten list feel cramped and inconsistent.

Fix

frontend/src/routes/geschichten/+page.svelte: container max-w-4xl → max-w-7xl.

The detail page (/geschichten/[id]) intentionally stays at max-w-3xl — it is a prose reading column (spec R-2 pins it); widening it would push the serif body past the 45–75ch readability range.

Acceptance criteria

  • /geschichten container matches / and /persons (max-w-7xl)
  • /geschichten/[id] unchanged (max-w-3xl)
## Problem `/geschichten` uses `max-w-4xl` (896px) while the Dokumente search (`/`) and Personen overview (`/persons`) both use `max-w-7xl` (1280px). Switching between directory pages makes the Geschichten list feel cramped and inconsistent. ## Fix `frontend/src/routes/geschichten/+page.svelte`: container `max-w-4xl` → `max-w-7xl`. The **detail** page (`/geschichten/[id]`) intentionally stays at `max-w-3xl` — it is a prose reading column (spec R-2 pins it); widening it would push the serif body past the 45–75ch readability range. ## Acceptance criteria - [ ] `/geschichten` container matches `/` and `/persons` (`max-w-7xl`) - [ ] `/geschichten/[id]` unchanged (`max-w-3xl`)
marcel added the P2-mediumui labels 2026-06-10 22:35:01 +02:00
marcel commented 2026-06-10 22:50:26 +02:00
Author
Owner
Copy Link

Amendment after user review: the detail page does not stay at max-w-3xl as originally specified here. Decision: outer container goes to max-w-7xl (sheet spans the page like the other directory pages), with an inner max-w-3xl mx-auto reading column inside the sheet preserving the prose line length. Implemented in 264d7268; both spec impl-ref tables updated.

Amendment after user review: the detail page does **not** stay at `max-w-3xl` as originally specified here. Decision: outer container goes to `max-w-7xl` (sheet spans the page like the other directory pages), with an inner `max-w-3xl mx-auto` reading column inside the sheet preserving the prose line length. Implemented in 264d7268; both spec impl-ref tables updated.
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 P2-medium ui
Milestone
No items
No Milestone
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#799
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?