Discussion on "Why Ruby on Rails Needs Components"

Avi Flombaum · 2023-08-01T12:37:49.229Z

I previously wrote a bit about What Rails Components and why don't we have them are at a very high level. Rails Components are shareable, encapsulated, and interoperable pieces of functionality that can be dropped into your Rails application. They ar...

You are right Avi. Rails is missing this magic dust 🪄🎨 that empowers developers and add beauty to any Rails app. I've used yours and it is wonderful well written. As a developer with front-end and design experience, I started mine UI components to save myself time and work. And after a few weeks I launched Rapidrails UI as a product built on top on ViewComponent and TailwindCSS. While it is not an open source, I'm working on an free one, as a part of Rails Rails agency public kit.

I echo your voice, we need more Rails UI components.

Have you seen a Phlex though?

I totally have and love it. What this is about is a pattern for how we would share components, Phlex, ViewComponent, between applications and how we should create more component libraries that do that, regardless of the underlying implementation.

In Rails, a few gems add component functionality (like mountain_view). Unfortunately, the side effect of using components after some time is adding more specific logic in generic components.

I think you're right that it would be helpful to have a drop-in gem to provide some nice looking components. CSS frameworks like Bootstrap have helped with that in the past. I've been meaning to write a blog post about this, but the magic combination that has been working well for us has been Hotwire, Tailwind, and the ViewComponent gem. We've built our own components pretty easily and I'd recommend that stack for anyone who feels like components are lacking in Rails.

Avi Flombaum The library is live at shadcn.rails-components.com you can install the gem in an app and generate components into it.

Andrew Havens When I started RapidRails library I had no plan to make is a gem, I want developers to copy and past files and folder. But, as the library grow and my goal is to make it unique I have several folders and files needs moving around. Maybe having a generator is an option. Still looking for a good solution.

For my custom clients work (deign to code) I create a few folders and developers copy/past, because it is unique for every project. How do you structure your library?

Discussion

Why Ruby on Rails Needs Components

Responses(3)

Recent in Forum

Search Hashnode

Why Ruby on Rails Needs Components

Responses(3)

Recent in Forum