[Question] Why not use a UI component library?

[malparty]

Issue

The UI has a lot of inconsistency or minor issues (see below).

Could you share more about the decision to only use Tailwind (without a UI component library like DaisyUI or similar)? If you would have to redo this project, what would you change regarding the UI implementation?

Here is a pick of some UI issues:

• Buttons miss the pointer cursor
• The file input has a different active style than the search input
• The authentication form has a totally different UI (buttons, inputs, ...)
• The responsiveness of the keyword list and the application menu does not work for mobile devices
• The success/alert messages have no style

[macropusgiganteus]

Thank you for your question.

I'm aware that the UI has a lot of inconsistency and willing to improve it.

Q: Why not use a UI component library A: At the beginning of the project, I thought it would be faster to use plain tailwinds. So, didn't think of the UI library. I tried grouping the button style in app/assets/stylesheets/application.tailwind.css but it clearly wasn't enough to make the code consistent.

Q: If you would have to redo this project, what would you change regarding the UI implementation? A: I would use the UI library for faster development and code consistency and also group repeated styles into shared classes.