Moving along with the steps I follow to create a new Rails application, I want to get into a little detail on some of the specific steps I outlined previously. These are the first steps in taking a Rails app beyond the default shell and making it do what you need to get done. While most of the steps I went through last week are familiar to anyone who’s set up a Rails application before, in the next few posts I want to talk about Nifty Generators, a set of useful generator methods to simplify customization of your application. You may be familiar with Nifty Generators and not realize it–if you’ve ever watched an episode of Railscasts, Ryan Bates’ popular screencast series about Ruby on Rails, you’ve probably seen Nifty Generators in action. Ryan created Nifty Generators and uses them in almost every example he provides in the series.
In my previous posts about bootstrapping a Rails app by hand and bootstrapping using an app template I showed how to use Nifty Generators’
nifty_config methods to create a nice layout file for your views and a global configuration file for your Rails environments, respectively:
So what do these two generators actually do? In this post I’ll talk about
nifty_layout, which essentially does three things. First, it generates a layout template for your application at
app/views/layouts/application.html.haml. In my case, this is a Haml-formatted file since I passed the
--haml flag; leaving it off would generate
/app/views/layouts/application.html.erb if that’s your markup preference.
Second, the generator adds a stylesheet for my app at
/public/stylesheets/sass/application.sass (foregoing the
--haml flag would generate a standard CSS file at
/public/stylesheets/application.css). By default, this gives your Rails app the look and feel of a Railscasts tutorial, which I find to be a nice, clean interface for getting started with my apps.
nifty_layout creates the file
app/helpers/layout_helper.rb. This file adds one particularly useful feature to help you DRY up your view templates. Essentially, within a given view template, the Haml-formatted line
renders my view’s title in two places: Inside an
<h1> element, and in the
If for some reason I only want the title to show within
<title>, I can use
If you take a look at the code in
app/views/layouts/application.html.erb) you can see what’s going on here–when the optional
show_title value is passed to the
title helper method, it helps the layout determine whether or not to render an
<h1> element for the page. In the case above, I passed
false for this value, so the
<h1> is not rendered.
Note also that the
title helper method doesn’t actually handle printing the title; it just prepares it for the layout to print to the screen. This is subtle, but important. It means I don’t use
= title 'my title' in Haml or
<%= title 'my title' %> in Erb; I just use
- title 'my title' or
<% title 'my title' %>, respectively.
That makes up pretty much all of my use of
nifty_layout, but there’s more to this generator. Take a look at its help file by typing
That’s it for
nifty_layout–next time I’ll talk about how I use its parter,
nifty_config, to simplify my apps’ global settings.
When using generated code like that from
nifty_layout, take time to look over the code to familiarize yourself with what it does and how it works. Not only will this practice help make sure you use the generated code as intended, it also gives you the chance to see how a seasoned developer like Ryan Bates writes code. In this case, you can pick up some tips on refactoring your view code into helpers and layouts.
I stand with the Black community against systemic racism, police violence and brutality, intolerance, and hate in the United States and worldwide. We must all demand better from our leaders, and ourselves. Stop tolerating intolerance.
While you're here, please consider making a donation to Black Girls CODE, who do great, important work to provide opportunity to underprivileged girls interested in tech, or any organization working toward equity and safety for all, not just the privileged. Thank you.
If you liked my series on practical advice for adding reliable tests to your Rails apps, check out the expanded ebook version. Lots of additional, exclusive content and a complete sample Rails application.
Ruby on Rails news and tips, and other ideas and surprises from Aaron at Everyday Rails. Delivered to your inbox on no particular set schedule.