Added FlyonUI Free Component Library

[saanvi-ts]

FlyonUI	https://flyonui.com
Resource name here	Resource link here

FlyonUI is a free, open-source Tailwind CSS component library designed to streamline web development with semantic classes and headless JavaScript plugins. It offers a robust set of customizable, responsive UI components for building modern, accessible interfaces across frameworks like React, Vue, and Svelte. With over 2k Github Stars, it is getting popular in the community for its ease of use and freshness.

Here is the GitHub Repo: https://github.com/themeselection/flyonui

Features:

• 80+ Responsive Components: Includes buttons, cards, forms, modals, navigation bars, and more, all built with Tailwind CSS utility classes.
• Semantic Classes: Simplifies styling with clean, readable class names for maintainable code.
• Headless JS Plugins: Adds interactivity (e.g., accordions, dropdowns, overlays) without dictating styles.
• Unlimited Themes: Supports light, dark, and custom themes with one-line dark mode toggle.
• Framework-Agnostic: Compatible with React, Vue, Svelte, Angular, and more.
• Accessibility-Focused: Components meet accessibility standards for inclusive design.
• RTL Support: Built-in support for right-to-left languages.
• Third-Party Integration: Supports libraries like ApexCharts, FullCalendar, and Flatpickr.
• MIT License: Free to use, modify, and distribute for any project.

---

• I have read and followed the contribution guidelines
• My item is in the right category
• My item is logically grouped below similar items
• My item's name and description respects the conventions of the list
• My item is awesome, and I really mean it
• My item is in line with the Tailwind brand usage guidelines

[joshmanders]

This resource was already on the list and we deemed it no longer worthy and was removed in #598.

[saanvi-ts]

This resource was already on the list and we deemed it no longer worthy and was removed in #598.

Hi @joshmanders , May I know what makes it "no longer worthy"?
I mean the library I submitted is regularly updated. It is open source and has 2k+ GitHub star and it is still growing.

Above all it supports latest Tailwind CSS 4 i.e. it is not out of date.
In fact there are many upcoming updates in the products.

New framework integrations was also included.
It would be really helpful for us to understand the reason so that we can improve it accordingly.

[innocenzi]

The reason I removed Flyon UI from the list is that I am not comfortable with the Flyon UI pro CTAs on the site. We avoid products with paid tiers on the list.

I also don't like that PRs from ThemeSelection on this repository don't respect the guidelines, despite checking the box.

[joshmanders]

@saanvi-ts besides what @innocenzi said, I looked at all the PR's by the people behind the ThemeSelection github org who keep submitting their stuff here don't follow the very simple guidelines and seem to be treating this repo like their personal marketing channel.

Being something that uses or is built for Tailwind doesn't immediately mean it's acceptable for this list. We had a massive list that just was full of meh and not Awesome. We want to make it truly awesome stuff.

Premium templates and UI libraries are not awesome. No disrespect to those who build them, but they're not truly awesome.

[saanvi-ts]

The reason I removed Flyon UI from the list is that I am not comfortable with the Flyon UI pro CTAs on the site. We avoid products with paid tiers on the list.

I also don't like that PRs from ThemeSelection on this repository don't respect the guidelines, despite checking the box.

@joshmanders @innocenzi

I appreciate your feedback and would like to address your concerns.

I understand the guidelines regarding the listing of resources, and I wanted to clarify that we offer both free and premium versions of our product.

The link I submitted pertains to the free version, and I noticed that another library with a similar model—offering both free and premium versions—also includes a "PRO CTA" in the heading section.

While I am happy to make any necessary adjustments, I feel that pointing out the "PRO CTA" in our case does not seem entirely justified, especially considering the inclusion of other similar resources.

If the issue lies with submitting GitHub links exclusively for free products, I am more than willing to provide the GitHub link to our free version for future submissions.

Regarding the guidelines, could you please specify which ones we may have overlooked? I’d like to ensure that we fully comply in the future and make the necessary adjustments if needed.

As for linking back to the Awesome TailwindCSS list, I wasn’t aware of that requirement to put the badge on the product page. We have no issue with linking back, and we would be happy to do so if that resolves the concern.

Aside from that and forgetting to use the term "Tailwind CSS" in the description, I believe I’ve followed all other guidelines.

• Product is Open source: https://github.com/themeselection/flyonui?tab=readme-ov-file#license-
• Our project is actively maintained: https://github.com/themeselection/flyonui/blob/main/CHANGELOG.md
• supports Tailwind CSS 4
• provided short description starting with the capital letter
• Every name and description are in English.
• Our project is not violating the Tailwind brand usage guidelines.
• Item follows the provided format: [Item name] (link) - Description.
• Descriptions must not start with "The", "A" or similar.
• Description starts with an uppercase character and ends with a period.
• Descriptions must describe the resource, not be a slogan.
• Listed the item in the right category
• Item is logically grouped below similar items - Is a library and has copy paste use case, for example you can check this: https://flyonui.com/docs/components/accordion/#always-open
• My item's name and description respects the conventions of the list as listed the points above
• My item is awesome, and I really mean it

[joshmanders]

Okay I really don't want to argue back and forth, the biggest stopper is the fact that we don't want to promote paid for products. This is not another marketing channel.

If you submit something that isn't trying to upsell to something else, we'll gladly add it. And regarding other things being pro in the list, we had previously allowed stuff and have cleaned a lot of it up, sometimes things get missed, if you see something that is doing what we just said here, point it out and we'll remove it.

The only premium upsells we're allowing is from Tailwind Labs themselves.

This is a hard rule by me. The team gives sooooo much away for free and allows so much, the least we can do is not promote their competitors with their material.

[saanvi-ts]

Okay I really don't want to argue back and forth, the biggest stopper is the fact that we don't want to promote paid for products. This is not another marketing channel.

If you submit something that isn't trying to upsell to something else, we'll gladly add it. And regarding other things being pro in the list, we had previously allowed stuff and have cleaned a lot of it up, sometimes things get missed, if you see something that is doing what we just said here, point it out and we'll remove it.

The only premium upsells we're allowing is from Tailwind Labs themselves.

This is a hard rule by me. The team gives sooooo much away for free and allows so much, the least we can do is not promote their competitors with their material.

I can certainly point out that one product which follows a freemium model and includes a CTA for the pro version in getting started page & in every page. However, I’d prefer not to mention it publicly, as I don’t wish to single out anyone. Since your team handles the review and filtering process, It's up to you.

Also, I’d like to clarify that I’m not using this repository as a marketing channel. As mentioned earlier, it’s already a well-known resource, so this submission won’t significantly impact its reach.

We’ve simply created an open-source Tailwind CSS component library, much like other useful resources shared in the community. That’s why I submitted it—as an open-source contribution.

Anyway, would it be alright if I submit the GitHub link instead of the homepage? This way, users can directly access and download the source code for free. So, it will be suitable here.

This is last try from my end.
Final call is yours and I will respect your decision without stretching it further.

Thanks for your time.