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

As a user I want to see a summary header above the conversation so I know the scope before reading #31

New Issue
Closed
opened 2026-03-20 12:30:16 +01:00 by marcel · 0 comments
marcel commented 2026-03-20 12:30:16 +01:00
Owner
Copy Link

Background

Once both persons are selected the conversation loads immediately, but there is no at-a-glance summary. The user has to scroll to the bottom to count documents or find the date range.

Desired behaviour

A compact info bar between the filter panel and the conversation list showing:

  • Document count (e.g. 14 Dokumente)
  • Date range (e.g. 1921 – 1947), omitted if no documents have dates

Implementation notes

Frontend only. Both values are fully computable from data.documents using $derived. Reuse the existing formatDate-adjacent patterns — extract year with doc.documentDate?.substring(0, 4).

Style: same visual weight as section subheadings elsewhere — text-xs font-sans uppercase tracking-widest text-gray-400, inline with a · separator.

## Background Once both persons are selected the conversation loads immediately, but there is no at-a-glance summary. The user has to scroll to the bottom to count documents or find the date range. ## Desired behaviour A compact info bar between the filter panel and the conversation list showing: - Document count (e.g. `14 Dokumente`) - Date range (e.g. `1921 – 1947`), omitted if no documents have dates ## Implementation notes **Frontend only.** Both values are fully computable from `data.documents` using `$derived`. Reuse the existing `formatDate`-adjacent patterns — extract year with `doc.documentDate?.substring(0, 4)`. Style: same visual weight as section subheadings elsewhere — `text-xs font-sans uppercase tracking-widest text-gray-400`, inline with a `·` separator.
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
 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
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#31
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?