If you want to quickly assess the quality of component libraries like these, especially in terms of accessibility, just take a quick look at their Select/Dropdown implementation.
Their variant breaks all keyboard navigation features and doesn't respond as expected to keyboard only input. If they want to up their game, they should address this before moving out of beta.
First of all, there are at least three comments in this thread that dont really make sense / have strange grammer, are from accounts that have never participated before, and all of the comments seem to share a similar positive sentiment towards the post. I find this very odd.
Moving on:
I'm super, super confused with the structure of the project. It uses tailwind, but with a custom prefix for some reason?
And then we have `colorVariantMapping.ts` which is over 3000 LOC. I just don't get it? Are they reimplementing parts of tailwind specifically for this project? I had a look at the tailwind github repo but I'm not familiar enough with it to be able to appropriately discern what is going on here.
I might be missing something, but I'd love to get a breakdown of the project structure, and information on how it all interconnects.
The components and site are all quite visually appealing, that's definitely a strong point. Unfortunately, the absence of any effort to make the components accessibly is very off-putting. Even a lot of non-accessibility UX standards are ignored (like ESC to close an open dropdown). The project might just be in beta, but accessibility should be part of the development process from the start, and not just an after thought, especially since there are so many great libraries that offer accessible, compliant ui primitives for react that you can then style / customize yourself.
All of the examples would be just as easy to build with a regular UI library combined with charts from some charting library of which there are just as many out there as well.
The components look really good but I don't quite get why the instructions make you create a new Next.js app? I understood this would work in any React app/framework and doesn't have any opinions on server-side rendering etc.
Why you think they have greek roots? GitHub organization's location is set to Switzerland, and linked Twitter users are based in Switzerland, Austria and England. Of course, that doesn't say if there is greek roots or not, just wondering how you arrived at the conclusion.
This looks really good! I'm definitely going to use it. I'm curious what the purpose of it is though.
It doesn't seem to be made purely out of the goodness of the creator's hearts, but it's not monetized in any way and I'm struggling to think about how it could be monetized.
At first I thought of the Tailwind model, but there are already ready-made blocks and components on their website for free.
Readit News
Their variant breaks all keyboard navigation features and doesn't respond as expected to keyboard only input. If they want to up their game, they should address this before moving out of beta.
Moving on:
I'm super, super confused with the structure of the project. It uses tailwind, but with a custom prefix for some reason?
And then there are all these files in `src/lib` like this [one](https://github.com/tremorlabs/tremor/blob/a5c979959bedf558b7...) which contains 500 LOC of just... adding their prefix to existing tailwind classes.
And then we have `colorVariantMapping.ts` which is over 3000 LOC. I just don't get it? Are they reimplementing parts of tailwind specifically for this project? I had a look at the tailwind github repo but I'm not familiar enough with it to be able to appropriately discern what is going on here.
I might be missing something, but I'd love to get a breakdown of the project structure, and information on how it all interconnects.
The components and site are all quite visually appealing, that's definitely a strong point. Unfortunately, the absence of any effort to make the components accessibly is very off-putting. Even a lot of non-accessibility UX standards are ignored (like ESC to close an open dropdown). The project might just be in beta, but accessibility should be part of the development process from the start, and not just an after thought, especially since there are so many great libraries that offer accessible, compliant ui primitives for react that you can then style / customize yourself.
All of the examples would be just as easy to build with a regular UI library combined with charts from some charting library of which there are just as many out there as well.
It doesn't seem to be made purely out of the goodness of the creator's hearts, but it's not monetized in any way and I'm struggling to think about how it could be monetized.
At first I thought of the Tailwind model, but there are already ready-made blocks and components on their website for free.
Are there some unpaid libs like this for tailwind? All I've found is tailwindui, but I find the price far too high for a side-project.
What I’m confused about is the change of the api from tailwind, the whole `maxWidth=“max-w-sm”` seems repetitive and a worse abstraction.
https://www.tremor.so/docs/getting-started/installation