Files
Calendar_Frontend/docs/features.md
T
PaddyandClaude Opus 5.5 61e0393f01
Test and deploy / test (pull_request) Successful in 2m18s
Test and deploy / deploy (pull_request) Skipped
Support the read-only calendar role, show "Vorstand", fix link buttons
- Read-only role: /admin/me's permissions decide via canEditCalendar
  (lib/permissions.ts, mirrors the API's canWrite: only `access` writes).
  Read-only accounts see everything but get no "Neuer Termin", no "+", no
  "Veröffentlichen"; an event opens as "Termin ansehen" with locked fields.
  A "Nur lesen" badge in the header explains why. The API refuses their
  writes regardless.
- The management calendar is labelled "Vorstand"; the slug stays
  `management` for the API, URLs and iCal links.
- The subscription dialog's Apple/Google links are plain anchors styled with
  buttonVariants instead of Base UI Buttons rendering an <a>, which warned in
  dev and would have given them role="button".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 22:15:31 +01:00

3.0 KiB

Features

What the calendar app does, as of the Next.js rewrite (September 2026).

Public page (/)

  • Subscribe to the public calendar: Apple Kalender (webcal://), Google Kalender (deep link), or copy the iCal URL (shows the URL if the clipboard isn't available).
  • "Nächste Termine": the next four public events with date, time and place; an event with a web link opens it. Refreshed every five minutes; hidden if the API can't be reached.
  • Link to the Verwaltung (/admin).

Verwaltung (/admin)

Sign-in happens in the admin app (one account for all Nachklang apps). Accounts need the calendar permission; without it the page says so instead of redirecting.

Two levels (granted in the admin app): Vollzugriff (access) can do everything below; Nur lesen (read, since 2026-11-08 in this app) sees every calendar, draft and subscription link but changes nothing - no "Neuer Termin", no "+", no "Veröffentlichen", and opening an event shows "Termin ansehen" with locked fields and only "Schließen". A "Nur lesen" badge in the header says why. The API refuses read-only writes anyway (403); the UI just doesn't offer them.

List

  • All calendars in one list, grouped by month, colour-coded per calendar.
  • Calendar chips toggle calendars on and off, with a count each; Geburtstage is off by default.
  • Kommend / Vergangen / Alle. "Vergangen" shows the newest first; "Alle" scrolls to a "Heute" marker.
  • Search over title and location.
  • Sort by start or by creation date (the latter as a flat list).
  • The view is in the URL, so a link reproduces it.
  • Drafts show an "Entwurf" badge and a "Veröffentlichen" button, which asks for confirmation and says who will see the event.
  • Repeating events (birthdays) show a "jährlich" badge and appear at their next occurrence.
  • Failed calendars are marked on their chip with a retry banner; the rest of the list stays usable.

Edit sheet (bottom sheet on phones, side panel on larger screens)

  • Create ("Neuer Termin" in the header, "+" button on phones), edit, duplicate, delete.
  • Fields: Kalender, Titel, Ganztägig, Beginn, Ende, Ort, Link, Beschreibung (multi-line), Status (Entwurf / Veröffentlicht; "Privat" is kept but not selectable).
  • Moving the start moves the end with it. Whole-day events take dates only.
  • A link without https:// is completed; anything that isn't a web address is flagged.
  • Moving an event into Geburtstage makes it yearly; moving it out removes that again.
  • Errors appear next to their field; a failed save keeps the edits and says why.
  • Closing with unsaved changes asks first; so does leaving the page.
  • Shows who created and last changed the event.

Abonnieren (header)

  • Subscription links for every calendar, including the internal ones with their password: Apple, Google, or copy. Chor and Geburtstage share a password.

Not (yet) possible

  • Restoring deleted events and editing recurrence need API work first - see api-wishlist.md.
  • A month-grid view was deferred (decision Q6); the agenda list came first.