Add Tailwind CSS, migrate most of the styles #27
No reviewers
Labels
No Label
integration
discourse
integration
ejabberd
integration
ldap
integration
lndhub
integration
nostr
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/akkounts#27
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/tailwind-css"
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?
This change adds the Tailwind CSS framework to the app, with new styles being defined in
app/javascripts/stylesheets
.I have already migrated a lot of existing styles to the new concept of using Tailwind classnames, as well as custom components made up of classes, too. I already added the forms plugin, and in addition to custom-styling our buttons, the (still barebones) forms look a bit nicer on average now.
I also removed our own resets in favor of the rather complete Tailwind base resets.
The rest still mostly looks the same as before. This PR is only intended to introduce Tailwind in the first place, and demonstrate how it can be used. And it took a couple of days to get this far already. So I think this should be merged now, and the rest of the styles migrated in separate PRs, where we can then also improve the overall layout at the same time.
👍