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 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.