Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I look forward to Tailwind CSS v4, I’ve also started working on v2 of
tailwind_styled_content
.The plan for v2 is to fully support Tailwind CSS v4 and remove DaisyUI as a required dependency.
Previously, DaisyUI was used primarily for form styling. Moving forward, this will be handled by
@tailwindcss/typography
along with some custom CSS. I decided to move away from DaisyUI because, while it’s a great tool for quickly creating styled UIs, it falls short in terms of accessibility and has a somewhat recognizable, playful default style.I don’t want to impose that design choice on you. If you still wish to use DaisyUI, feel free to include it yourself. This shift allows us to adopt a more sensible default style.
TODOS: