4 ms·

I'm gonna be rough here. I think calling these things "components" feels wrong. Components are far more elemental than what these are; these are pages, or mayb

by 015a 2y ago

I'm gonna be rough here. 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-left-aligned-image?lang=html&frame=bootstrap&mode=sources&colorScheme=light https://easyfrontend.com/component-details/error-404-buttons... [2] https://easyfrontend.com/component-details/grid-style-number-cards?lang=html&frame=bootstrap&mode=sources&colorScheme=light https://easyfrontend.com/component-details/grid-style-number...

adif_sgaid 2y ago
I totally agree...
FireInsight 2y ago
If you want some "copy-paste tailwind components" you're really best of using shadcn/ui or whatever port exists for your favorite UI libraty. I've been using shadcn-svelte in a recent project and it's the best decisions I made. Having the source code there and modifying it to suit my needs really has helped me learn a lot of good practices.
- mattgreenrocks 2y ago
  shadcn is fantastic. Bit of a learning curve vs component libraries (like Flowbite), but you can just go in and make the changes you need as necessary. It also helps that the New York style is very nice as well.
deleted 2y ago
[deleted]
santush 2y ago
hi, thank you for the comment. We didnot build any components using AI. The link you provided if you choose the language and framework you will see the actual code of the component. There is proper way we follow > design components > make it HTML Tailwind > React Tailwind And all are free to use.
- bytearray 2y ago
  First off, thanks for doing something cool and releasing it as open source! Second, think the person 2 messages up has a valid point and I would like to offer the same constructive feedback. 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 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!
  - nprateem 2y ago
    There are loads of those already. For chucking together something decent quickly we need more 'block' level components than elements. 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.
  - santush 2y ago
    thank you for the comment. We will improve it based on your feedback.
KMnO4 2y ago
Yikes, that’s some bad code. What’s the point of using tailwind if half the elements have their own custom CSS classes attached?
- that_guy_iain 2y ago
  Are you looking at the tailwind code or bootstrap? I can’t see custom classes in the tailwind version just the bootstrap version
- 015a 2y ago
  Oh I didn't necessarily mean the code, at least in the first example; you have to click the "Preview" button to see what the code results in, but its a rather bad 404 page, using broken english, phrases that generally wouldn't/shouldn't appear on a 404 page ("this page is broken"), a button that fully disappears rather than correctly entering a hover state, and a button that generally would never appear on a 404 page ("Try Again"). 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.
  - santush 2y ago
    hi 015a, thank you for the comments. I admit that there are some improvment must need and we will continue improve it. 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.
- santush 2y ago
  I don't know where you found custom CSS. Maybe you checked the main site and didn't follow which language and framework are selected. Also, please select the Tailwind CSS framework to see the Tailwind codes.
qingcharles 2y ago
They're not awful, they're just very average, IMO.

by 015a 2y ago

adif_sgaid 2y ago

I totally agree...

FireInsight 2y ago

If you want some "copy-paste tailwind components" you're really best of using shadcn/ui or whatever port exists for your favorite UI libraty. I've been using shadcn-svelte in a recent project and it's the best decisions I made. Having the source code there and modifying it to suit my needs really has helped me learn a lot of good practices.

mattgreenrocks 2y ago
shadcn is fantastic. Bit of a learning curve vs component libraries (like Flowbite), but you can just go in and make the changes you need as necessary. It also helps that the New York style is very nice as well.

deleted 2y ago

[deleted]

santush 2y ago

hi, thank you for the comment. We didnot build any components using AI. The link you provided if you choose the language and framework you will see the actual code of the component. There is proper way we follow > design components > make it HTML Tailwind > React Tailwind And all are free to use.

bytearray 2y ago
First off, thanks for doing something cool and releasing it as open source! Second, think the person 2 messages up has a valid point and I would like to offer the same constructive feedback. 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 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!
- nprateem 2y ago
  There are loads of those already. For chucking together something decent quickly we need more 'block' level components than elements. 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.
- santush 2y ago
  thank you for the comment. We will improve it based on your feedback.

KMnO4 2y ago

Yikes, that’s some bad code. What’s the point of using tailwind if half the elements have their own custom CSS classes attached?

that_guy_iain 2y ago
Are you looking at the tailwind code or bootstrap? I can’t see custom classes in the tailwind version just the bootstrap version
015a 2y ago
Oh I didn't necessarily mean the code, at least in the first example; you have to click the "Preview" button to see what the code results in, but its a rather bad 404 page, using broken english, phrases that generally wouldn't/shouldn't appear on a 404 page ("this page is broken"), a button that fully disappears rather than correctly entering a hover state, and a button that generally would never appear on a 404 page ("Try Again"). 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.
- santush 2y ago
  hi 015a, thank you for the comments. I admit that there are some improvment must need and we will continue improve it. 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.
santush 2y ago
I don't know where you found custom CSS. Maybe you checked the main site and didn't follow which language and framework are selected. Also, please select the Tailwind CSS framework to see the Tailwind codes.

qingcharles 2y ago

They're not awful, they're just very average, IMO.