Tagged with: rails

A couple of weeks ago I wrote about trying to build a universal ButtonComponent — one with no custom CSS classes. The result worked but was complicated. The night I wrote it up, a simpler approach just came to me.

A colleague asked recently whether we could push all of our button styles into a single component. Could we get rid of the CSS classes and have one place that knows what a button looks like — regardless of whether it’s a link, a form submit, a control, whatever?

Nearly every project I’ve worked on has, at some point, had to answer the question of inlining SVGs into HTML. I’ve been refining my approach to this from project to project and now have something stable and reusable I just drop into anything new.

Recently, I implemented a couple of ViewComponents to display links to our app in the app stores. These ViewComponents contained in a single place: the appropriate logo for app store, the link to the app in said app store, descriptions to make the links accessible and click tracking.

This post walks through the process of adding a rating system to a Turbo powered single page application. The application in question was built up in a previous post. If you want to follow along with the post, you can grab the repo at the starting point or just read the pull request.

Turbo (part of Hotwire) is a supercharged version of Turbolinks. If you’re used to immediately turning off Turbolinks in any new project, you might be surprised to learn that you don’t need React or Vue to build a rich and interactive web app.