Our great sponsors
-
view_component
A framework for building reusable, testable & encapsulated view components in Ruby on Rails.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
twin.macro
🦹♂️ Twin blends the magic of Tailwind with the flexibility of css-in-js (emotion, styled-components, solid-styled-components, stitches and goober) at build time.
-
headlessui
Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Rails has view components. GitHub started the pattern years ago in their Rails app.
If you are not into making your own component library, you can use DaisyUI instead.
I still think that Bootstrap and Tailwind are a bit backward. May as well go all in and use CS-what. I'd personally never sign on to a project that forced me to use them but I'm spoiled. My job is to teach how to write great HTML and CSS. But that doesn't mean that utility/class frameworks don't have value to other organizations. Their goal is to make it easier and more maintainable, so - if you learn CSS well, then you should we able to be productive in a framework right away. Any CSS lover has at some time created their own little framework (or many) along these lines. And there's no silver bullet. But the problem with that is - then the other team members will have to learn your unique angle on CSS.
Headless UI and Tailwind UI (paid but worth the time saved).