mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-15 21:59:40 +02:00
b857063120
eventstream was confusingly branded "Events" in the app registry, colliding with the real events calendar module. Renamed to activity (DE: Aktivität) since it's a live activity feed across all modules. cycles -> period (DE: Periode) makes the menstrual-tracking module self-describing. Tables cycles/cycleDayLogs/cycleSymptoms renamed to periods/periodDayLogs/periodSymptoms; field cycleId -> periodId; TimeBlockType 'cycle' -> 'period'; domain event CycleDayLogged -> PeriodDayLogged. Generic "cycle" usages (billing, lifecycle, breath, bicycle, import cycles) left untouched. Constant disambiguation: prior DEFAULT_PERIOD_LENGTH (bleeding days) renamed to DEFAULT_BLEEDING_DAYS; prior DEFAULT_CYCLE_LENGTH (28d full cycle) is now DEFAULT_PERIOD_LENGTH. Pre-launch, no data migration needed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
51 lines
1.9 KiB
Markdown
51 lines
1.9 KiB
Markdown
# Frontend Consistency Improvements
|
|
|
|
Tracked improvements for UI/styling consistency across the Mana unified app.
|
|
|
|
## 1. Standardize ListView Styling Approach
|
|
|
|
**Status:** Open
|
|
**Priority:** Low (no functional impact, maintenance concern)
|
|
**Effort:** Medium (13 modules to migrate)
|
|
|
|
### Problem
|
|
|
|
Module ListViews use two different styling approaches:
|
|
|
|
- **Scoped CSS + `hsl(var(--color-*))` theme tokens** — 27 modules (65%)
|
|
- todo, notes, drink, contacts, journal, dreams, habits, firsts, calendar, chat, places, inventory, finance, news, body, calc, events, photos, automations, period, uload, picture, recipes
|
|
- **Tailwind utility classes** — 13 modules (35%)
|
|
- food, plants, moodlit, cards, presi, storage, skilltree, context, guides, memoro, who, music, playground, citycorners, questions, times
|
|
|
|
### Why it matters
|
|
|
|
- Tailwind modules sometimes hardcode colors (`bg-white/5`, `text-white/80`) instead of using theme tokens, breaking theme consistency.
|
|
- `transition-all` in Tailwind classes can cause rendering bugs with CSS custom properties (recipe module had invisible text until hover — fixed by switching to specific transition properties).
|
|
- Mixed approaches make it harder to audit theme compliance and onboard new contributors.
|
|
|
|
### Recommendation
|
|
|
|
Migrate the 13 Tailwind-based ListViews to scoped CSS with `hsl(var(--color-*))` tokens, matching the majority pattern. Key rules:
|
|
|
|
1. Use `hsl(var(--color-foreground))`, `hsl(var(--color-muted))`, etc. — not hardcoded colors.
|
|
2. Use specific `transition: transform 0.15s, box-shadow 0.15s` — never `transition-all` (causes CSS variable animation bugs).
|
|
3. Keep scoped `<style>` blocks — no Tailwind utility classes in ListView templates.
|
|
|
|
### Modules to migrate
|
|
|
|
- [ ] food
|
|
- [ ] plants
|
|
- [ ] moodlit
|
|
- [ ] cards
|
|
- [ ] presi
|
|
- [ ] storage
|
|
- [ ] skilltree
|
|
- [ ] context
|
|
- [ ] guides
|
|
- [ ] memoro
|
|
- [ ] who
|
|
- [ ] music
|
|
- [ ] playground
|
|
- [ ] citycorners
|
|
- [ ] questions
|
|
- [ ] times
|