fix: render event occurrences as readable timestamp chips #6

Merged
exler merged 3 commits from feature/group-similar-events into main 2026-09-02 12:18:19 +02:00
Collaborator

Summary

  • render every occurrence as a separate, readable timestamp chip
  • use semantic <time> elements with ISO datetime values
  • distinguish the active occurrence and preserve links to older events

Root cause

The event detail template used low-contrast, bare inline timestamps, making adjacent occurrences visually run together.

Validation

  • DJANGO_SECRET_KEY=... ./.venv/bin/python manage.py test events.tests.OccurrenceNavigationTest.test_occurrences_render_as_semantic_timestamp_chips -v 1
  • DJANGO_SECRET_KEY=... ./.venv/bin/python manage.py test events -v 1 (35 tests)
  • git diff --check

Note

Tailwind compilation was not run locally because this checkout has no node_modules and no lockfile; the template uses the existing Tailwind build workflow.

## Summary - render every occurrence as a separate, readable timestamp chip - use semantic `<time>` elements with ISO `datetime` values - distinguish the active occurrence and preserve links to older events ## Root cause The event detail template used low-contrast, bare inline timestamps, making adjacent occurrences visually run together. ## Validation - `DJANGO_SECRET_KEY=... ./.venv/bin/python manage.py test events.tests.OccurrenceNavigationTest.test_occurrences_render_as_semantic_timestamp_chips -v 1` - `DJANGO_SECRET_KEY=... ./.venv/bin/python manage.py test events -v 1` (35 tests) - `git diff --check` ## Note Tailwind compilation was not run locally because this checkout has no `node_modules` and no lockfile; the template uses the existing Tailwind build workflow.
docs: add occurrence chip visual verification
All checks were successful
Push Docker Image / push (push) Successful in 4m6s
7432d1af78
exler merged commit 7432d1af78 into main 2026-09-02 12:18:19 +02:00
exler deleted branch feature/group-similar-events 2026-09-02 12:18:21 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
exler/mado!6
No description provided.