themesberg / themesberg/flowbite
Suggest: Use the standalone-cli in installation docs for ease
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 862
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
There is no real problem, but I consider that installation steps could be easier to understand and adopt using the standalone cli.
Describe the solution you'd like
For example, with Django, we can ignore all the compressor stuff and only define 3 steps.
- Install standalone tailwindcss
- Add the js to base.html
- Call in a terminal tailwindcss -i ... -o ...
Additional context
Tailwindcss standalone cli is an official way to use tailwindcss https://tailwindcss.com/blog/standalone-cli
This feature has some time but it still present nowadays.
https://github.com/tailwindlabs/tailwindcss/releases/latest
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the installation documentation for using Flowbite with Django and review how the current compressor setup is described. Update the relevant guidance to cover the standalone Tailwind CSS CLI and its three installation, template, and terminal steps; done when the simpler official workflow is documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, tailwindcss
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100