Replies: 1 comment
-
Same thing is happening to me. Since I'm new to Django (the framework used in my project) I was wondering if this was something specific from the Python ecosystem so I opened a thread in the Django forum a few days ago. It may be a lot of effort for the project to maintain framework specific implementations of the components but it would be great to ease devs task as suggested and then I guess the community could contribute repos of frameworks examples or go-to starting points. I'm currently going to implement it with django-cotton. So let us know if the team has some advice on this matter. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Current Situation
I've been exploring Flowbite for a Flask project and find it to be an excellent component library. However, I've encountered a limitation in how the component HTML templates are distributed.
Currently—please correct me if I'm wrong—the only comprehensive source for component HTML markup appears to be embedded within Markdown documentation files in the
flowbite-docs
repository.The Challenge
This creates several inefficiencies for developers:
Feature Request
Could Flowbite provide a dedicated repository or section within the existing repository that contains standalone HTML template files for all components? Ideally, this would be:
Benefits
This approach would:
Again, sorry if this information is somewhere already, but I can't seem to find it.
If not, is this something on the roadmap?
It would significantly enhance the developer experience for those of us building with Flowbite, especially in Flask and other server-rendered frameworks.
Beta Was this translation helpful? Give feedback.
All reactions