Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A free and open-source starter project to help you get started with the core Flowbite Library components and Ruby on Rails.

A full-stack Next.js TypeScript template focused on functionality over UI, featuring Zustand, TanStack Query, and ESLint 9 support.
The Flowbite Ruby on Rails starter, also known as tailwind-rails-starter, is a free, open-source boilerplate that scaffolds a Rails application with Tailwind CSS v4 and the Flowbite UI component library, giving you prebuilt interactive components without writing custom JavaScript.
This starter project combines Ruby on Rails, Tailwind CSS, and Flowbite. It is distributed through a GitHub repository (13 stars) and documents a step-by-step setup: create a new Rails app, install Tailwind via the official tailwindcss-rails gem, then install Flowbite with npm and import its theme and plugin. The output is a Rails application where Tailwind utility classes and Flowbite interactive components work together out of the box.
The setup is a four-step process: (1) install the rails gem and create an app with rails new flowbite-app; (2) add tailwindcss-ruby and tailwindcss-rails gems and run rails tailwindcss:install; (3) install Flowbite with npm and import its theme, plugin, and source paths into your CSS; (4) import the Flowbite JavaScript either through importmap, ESBuild, or CDN. For Turbo apps, you must use the flowbite.turbo.js variant.
Yes. The repository metadata describes it as "free and open-source." There are no paid tiers or licensing fees mentioned, and it is hosted as a public GitHub project.
You need to install the tailwindcss-rails gem, run the Rails Tailwind installer, then add Flowbite via npm. In your application.css, import the Flowbite theme, plugin, and source files, and in your application.js import the Flowbite JavaScript. The page details commands for each step.
Yes. Flowbite ships a flowbite.turbo.js file with custom event listeners for the turbo:load event. You can pin it via importmap, import it through ESBuild, or load it from a CDN. This ensures components initialize correctly when Turbo navigates between pages.
