Upgrading Rails applications to Tailwind 4 - With the TailwindCSS 4 beta out, I decided to upgrade my Rails applications. Here are the steps I took to do the upgrade^*:

Beware Tailwind Color Changes - Let’s talk about the humble HTML button. Let’s imagine you have a beautiful button that you styled in the classic green style made famous by all the scientific research that showed that a green button converts better.

Intro to Raycast For Developers - Quick demo of setting up Raycast to search the Tailwind and Devdocs documentation.

• Raycast - https://www.raycast.com
• Raycast Tailwind Extension - https://www.raycast.com/vimtor/tailwindcss
• Raycast Devdocs Extension - https://www.raycast.com/pomdtr/devdocs
• TailwindCSS - https://tailwindcss.com
• DevDocs - https://devdocs.io
• Matt Swanson Twitter - https://twitter.com/_swanson
• BoringRails - https://boringrails.com

Rails 'new' customizations for Rails 7 - With Rails 7 and its plethora of new javascript and css configuration options and flags, it can be quite challenging to remember just what these options are when creating a new app.

For quite some time Rails has had the ability to read in a config file you have in your home folder named .railsrc This file contains the various flags you would otherwise pass into ‘rails new’ manually. By putting your preferred options/flags into this file, every Rails app you create will be created consistently and just the way you like it.

I prefer postgres as my database and esbuild for my javascript processing and tailwind as my css framework. So my .railsrc file looks like this

--database=postgresql
--javascript esbuild
--css tailwind

Now I just start a new Rails app with

rails new brilliant_app_idea

And my new app is ready to rock configured just the way I prefer.