Add dark mode support #110
Labels
No labels
bug
devops
duplicate
enhancement
good first issue
layout
next major release
next minor release
question
research
testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lvl0/fedi-feed-router#110
Loading…
Reference in a new issue
No description provided.
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?
Summary
The app is light-only. There are zero
dark:variants anywhere inresources/views/, anddarkModeis not configured intailwind.config.js.Users browsing with a dark OS/browser theme get a fully light UI — bright white cards and modals against their otherwise dark environment.
Current state
dark:variants in any viewdarkModestrategy configuredbg-white,text-gray-900,border-gray-300, etc.Why this surfaced
Discovered while fixing #108. The modal backdrop originally used
bg-gray-500/75— a mid-grey tuned for light UIs — which in dark mode read as a washed-out haze rather than a dim. Changing it tobg-gray-900/50 backdrop-blur-smimproved things in both themes, but the modal panel itself is stillbg-white, so it remains a bright card on a dark page.That fix treated the symptom. This ticket is the actual cause.
Scope
This is a broad visual change touching effectively every view:
darkModestrategy (classrecommended, so a toggle is possible;mediaif following the OS is sufficient)dark:variants across all surfaces, text, borders, and form controlsx-form-modalcomponent and the Breezex-modalAffected areas
layouts/app.blade.php,layouts/guest.blade.php,layouts/onboarding.blade.phpform-modal,modal,dropdown,page-header,text-input, buttons,notification-bellNotes
Tailwind v4 handles dark mode differently from v3 — the strategy is configured via CSS (
@variant dark) rather than thedarkModekey in the config file. Check the v4 dark mode docs before starting.Worth doing after #109 (renamed utility migration), so the utility scale is consistent first.