github.com
I think calling these things "components" feels wrong. Components are far more elemental than what these are; these are pages, or maybe modules.
Nonetheless, some of these "components" are quite bad [1]; it smells like AI was used to generate these? They run the gamut between bad enough that I wouldn't use them, or simple enough [2] that I wouldn't use them, and I'm not seeing a ton occupy the middle.
[1] https://easyfrontend.com/component-details/error-404-buttons...
[2] https://easyfrontend.com/component-details/grid-style-number...
It also helps that the New York style is very nice as well.
There is proper way we follow > design components > make it HTML Tailwind > React Tailwind
And all are free to use.
As someone who is doing a lot of React/Tailwind development lately the more you can assemble larger pages from independently usable components the better. For example here: https://easyfrontend.com/components/ui/all/html?page=1
It would be useful sometimes to be able to search for a "card" component that I want to use rather than remember that I want to see cards I need to go to Blog #10. This seems to be my normal intent when I'm using a framework is that I'm trying to find a [card, dialog, select box, data table, etc].
Anyway though, don't let the feedback get you down, it's awesome and greatly appreciated that you're releasing nicely designed Tailwind UI components. Github repo starred and thread upvoted!
I tried not to buy flowbite but it just speeds things up so much, it's a no-brainer. This is in a similar vein and will be ok for some less discerning use cases.
Like, I don't mean to be, well, mean about this; but I'm struggling not to be so here it is: I find it difficult to believe that any human with an ounce of the craft in their bones could have created that. So my conclusion was AI, because that is the more kind of two conclusions I could draw. The authors responding to my original comment by stating that no AI was used in the production of these assets, unfortunately, leaves only the other conclusion.
our teams works several months for the components and you are here to say it using AI.Its easy to say that so it using AI. Please try to build 700+ components with HTML, REACT and framework of TailwindCSS and Bootstrap. With light and dark version.
let me know which AI do that and give me the link I will follow next time.
"Faq's" in the top menu does not need the apostrophe and "lets" on the frequently asked questions page needs an apostrophe. So all in all, you don't need to acquire any new apostrophes, you can just move the one you already have in "Faq's" to between the t and the s in the "lets". Result!
A great website to learn the basics of the English language
However, this feels a bit edgy or just unkind:
> Getting it wrong makes you look stupid. And ugly.
Oh well.
Their Twitter posts seem to have retweeted a post by "Dorik AI" which is a website which has exactly the same theme and mentions "Dorik AI Website Generator can generate a complete website for you in a matter of seconds".
I wonder if this is how these components* were initially built? They seem very mishmash and all over the place.
*: I mention "components" because these feel more like auto-generated pages rather than the granular things you'd expect a component to have.
Modern HTML and CSS are awesome tools on their own, and are able to do so much without needing to rely on massive JavaScript bundles, but you still end up with component libraries that are <div><div><div><div> all the way down.
For more complex projects you'd tweak the components of course but it helps a lot that you can see the whole blocks rendered in advance and can prototype way faster this way.
What these libraries don't do is confer any design sense. You still have to know how to put the components together well, which means you'll spend way more time than expected adjusting sizing, spacing, and thinking about responsive design.
You definitely need some copyediting on your home page.
It'd be nice if you abstracted fonts (and colors?!) across components, so that users could pick their main combo and have those applied throughout.
The editor sidebar should be wider, since that's the main place where somebody working on the frontend will be tweaking styles and editing text.
In the editor, you can choose theme colors and fonts, but the theme style is still in process. We will publish it soon.
1) Another section "Dashboard" including components for responsive tables, date pickers, lists, maybe charts 2) A really pure, semantic and therefore light HTML/CSS3 version; no bloated code; I do love the approach of PicoCSS 2
On the other end of that spectrum is Ant.Design. It feels like a constant fight against the framework, with a scattershot approach of poorly thought out and overly specific components that are hard to configure to your needs.
Are there more components in Easyfrontend? Better ones?
After checking again I see you can pay (1-time) to unlock site templates and more components: https://tailwindui.com/templates
Does Easyfrontend have site templates? That's what would compare it with Tailwind's paid product, which is a different product.
[0] https://github.com/easy-astro-blog-creator/easy-astro-blog-c...
Still haven't seen an open-source UI kit that would get even close of the original one: https://tailwindui.com/
Nice work!
So it's good to see new component libraries being released supporting vanilla Javascript with Tailwind and gives developers who do not like React a choice.
See: https://tailwindui.com/components/application-ui/data-displa...
Would have preferred to see more vanilla components as well. Looks like they are doing really well and hiring, so I'm hopeful.
Most "frameworks" seem to follow the same patterns: NPM, lots of JavaScript, "revolutionary new approach to how you specify your layouts", few components, styling suitable for landing pages and startup home pages, not for data-dense applications, and nobody cares about tables.
If you ask "so what's wrong with Semantic-UI?" — nothing, except it isn't really developed and maintained anymore. I wish it also relied less on JavaScript. But otherwise it's pretty good.