semi-design VS flowbite-react

// Semi Github Repository Directory ├── semi-animation # js animation ├── semi-animation-react # react animation ├── semi-animation-styled # style animation ├── 👉🏻 semi-foundation # foundation │ ├── button │ ├── ... ├── semi-icons # icon ├── semi-illustrations # illustrations ├── semi-theme-default # theme ├── 👉🏻 semi-ui # react adapter │ ├── button │ ├── ... ├── ... # Packaging related // https://github.com/DouyinFE/semi-design/tree/main/packages

To get you started you can check out the full collection of React components from the Flowbite React repository and browse the documentation for the source code of each component.

Yeah, the Flowbite React library and community already has this in the works and will be updated accordingly.

The open-source Flowbite libraries such as Flowbite React, Flowbite Svelte, and Flowbite Vue have been nicely growing in terms of number of components, functionality, documentation, and also usage.

You can check out Flowbite React.

You can either use the core vanilla JS and static HTML components from the Flowbite Library or you can import dedicated React components such as the Alert, Modal, or Navbar from the Flowbite React library.

Flowbite React is a free and open-source library of UI components based on the Flowbite design system that allows you to plug-and-play interactive and responsive React components such as modals, navbars, dropdowns, and more directly inside your Remix and Tailwind CSS configured project.

Also not a lawyer, but I think it would technically count as personal information because it's a preference. Even if it's to provide functionality requested by the user, it would still be necessary to inform the user that this preference is being stored, etc.

However, I agree to your second point, that asking the user's browser to store the information, and then have the browser make decisions based on that without anything being shared back probably does not violate GDPR as it wouldn't count as 'processing'.

It would seem (although, without a deep dive into the codebase, I can't be 100% sure) that the tool just adds a class to the body: https://github.com/themesberg/flowbite-react/blob/765fedb3c9...

If this is the case, I think it unlikely that this would be found to be a GDPR violation as Flowbite (or the company which has deployed Flowbite) would not normally be able to detect this preference.

It would be different if for example the preference caused a different stylesheet to be downloaded, which could then be combined with server logs, but overall, it seems as though all of the processing of the data (whether you consider it personal or not) is done entirely on the user's computer, and there would be no processing of any data by the company which has deployed Flowbite, therefore it would not open up any GDPR liability.

Once again though, IANAL.

The package is handling state, styling and more https://github.com/themesberg/flowbite-react/blob/main/src/lib/components/Tab/Tabs.tsx

Flowbite React is an open-source set of interactive React components based on the Tailwind CSS utility-first framework featuring interactive elements such as modals, navbars, dropdowns, carousels, and more.

There is another newcomer called Flowbite React.