Fork from Flowbite. Shouldn't it be mentioned?
See original GitHub issueHey everyone,
First of all Iām happy to see more open-source projects being built on top of the Tailwind CSS ecosystem. This is important for the overall industry and for the community to benefit from more content.
Iāve taken a good look at Preline and I must say that as one of the founders of Flowbite I have found a whole lot of similarities starting from the way to the documentation looks and feels and up to the components themselves.
Of course the code is not exactly the same, but the whole concept of Preline seems VERY similar to Flowbite.
As a contributor it would be nice to at least mention it if youāve taken it as an inspiration.
Otherwise, I wish you good luck with the development of this library.
Thanks!
Edit: after taking a better look Iāve found that youāve actually forked the Flowbite repository. You can see this if you take a look at the commit history on Preline and check out the authors from the package.json
file:

I donāt think there is anything else to comment on here until a response from the authors of Preline.
Edit: @green-cats I saw that you have just removed the evidence under the disguise of a commit message.
Commit removing the evidence: https://github.com/htmlstreamofficial/preline/commit/8896fdf488979be67e0d87003cfae936958eec2e
Issue Analytics
- State:
- Created a year ago
- Reactions:24
- Comments:5 (3 by maintainers)
Hello @jahaganiev,
Thanks for getting back to me.
I still canāt wrap my head around why would the contributors from Flowbite appear on the
package.json
file from Preline while you also claim that not one single code has been copied from other projects.Other than that, if you compare the two pages it is obvious that Preline was built to replicate Flowbite:
Preline buttons: https://preline.co/docs/buttons.html Flowbite buttons: https://flowbite.com/docs/components/buttons/
Preline navbars: https://preline.co/docs/navbar.html Flowbite navbars: https://flowbite.com/docs/components/navbar/
Weāve had these published since September 2021.
And so many other documentation related features that were available only for Flowbite, such as:
preline/plugin
, couldnāt have been something else but itās clear that you took this from FlowbiteOf course, the code is not exactly the same, and the design is not exactly the same, but in concept, it is a replica and a copycat.
And if I take a look at your roadmap, you will also replicate the fact that we have a Figma design system and probably copy everything else that we will launch from now on.
Based on that we wonāt be able to view it as a unique and standalone library, but I wish you all the luck in the world!
Regards, Zoltan
Hi @zoltanszogyenyi š
Thank you for your feedback and wishes. I truly appreciate it!
First of all, I totally agree with you on the importance of diversifying Tailwind CSS resources and also hope this community grows further.
Please note that Preline UI is NOT a fork of any other project and was created entirely from scratch. Regrettably, your public statements about Preline being a replica are deceptive at its core.
Anyone can examine the code and design in depth and ensure that itās nowhere close to other Tailwind based products. Over the last 10 years, weāve been creating UIs for front-end developers with a lot of concepts, and if you look closely at our products, youāll notice a lot of similarities to our own existing premium Bootstrap Themes.
Besides our own products, the Docs layout in Preline is inspired by the original Tailwind CSS documentation. Simple example links to compare:
Preline UI: https://preline.co/docs/index.html
Tailwind CSS: https://tailwindcss.com/docs/installation
We respect all the hard work of the teams behind other products in the market and for that reason we never copied a single line of code during the last 10 years of creating UIās in the market.
Also, Iāve just dropped a reply on the Product Hunt for your message regarding the above statement here https://www.producthunt.com/posts/preline-ui
Wrapping up, Iād like to wish all the best for your projects and team!
Cheers! š»