Layouts and content_for in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a layout in Rails?

A layout in Rails is a common template that wraps around views to provide a consistent look and feel, like a frame around pictures. It usually contains shared elements like headers, footers, and navigation.

beginner

What does the content_for helper do in Rails layouts?

content_for lets you define a named block of content in a view that can be inserted into a layout at a specific place. It's like saving a note in one place to read it somewhere else.

intermediate

How do you yield a named content block in a Rails layout?

Use <code><%= yield :block_name %></code> in the layout to insert the content defined by <code>content_for :block_name</code> in the view.

intermediate

Why use content_for instead of just putting everything in the layout?

Because content_for lets views add specific content to parts of the layout without changing the layout file itself. This keeps layouts clean and flexible, like slots where views can put their own content.

beginner

What happens if you call yield without a name in a Rails layout?

It inserts the main view content. This is the default place where the view template's content appears inside the layout.

In Rails, where do you define a layout for your views?

A In the controller using <code>layout</code> method

B Inside the <code>config/routes.rb</code> file

C In the <code>Gemfile</code>

D In the database schema

You specify which layout to use in the controller with the layout method.

What does content_for :sidebar do ... end do in a Rails view?

A Defines content for a named block called :sidebar

B Immediately renders the sidebar content

C Creates a new layout file named sidebar

D Deletes the sidebar content

content_for defines content for a named block that can be used in the layout.

How do you display the content saved with content_for :footer in a layout?

A <code><%= render :footer %></code>

B <code><%= content_for :footer %></code>

C <code><%= footer %></code>

D <code><%= yield :footer %></code>

Use yield :footer to insert the named content block into the layout.

What is the default content inserted by yield without arguments in a Rails layout?

A The layout header

B The content from <code>content_for</code>

C The main view template content

D Nothing, it causes an error

The default yield inserts the main view content inside the layout.

Which of these is a benefit of using layouts in Rails?

A Writing database queries faster

B Reusing common page structure like headers and footers

C Improving server response time automatically

D Replacing CSS stylesheets

Layouts help reuse common page parts like headers and footers for consistent design.

Explain how content_for and yield work together in Rails layouts.

Think of content_for as saving content and yield as showing it.

Describe why using layouts improves your Rails app's structure and maintenance.

Imagine changing a header in one place instead of many.

Practice

1. What is the main purpose of using content_for in Rails layouts?

easy

A. To define the main layout file for the application

B. To insert specific content into named sections of a layout

C. To create a new controller action

D. To style the page with CSS

Solution

1. Step 1: Understand the role of layouts

   Layouts provide a shared structure like headers and footers for pages.

2. Step 2: Understand content_for usage

   content_for allows views to add content to specific named areas in the layout.

3. Final Answer:

   To insert specific content into named sections of a layout -> Option B

4. Quick Check:

   content_for inserts content into layout spots [OK]

Hint: Remember: content_for fills layout placeholders [OK]

Common Mistakes:

• Confusing content_for with layout definition
• Thinking it styles pages directly
• Mixing it up with controller actions

2. Which of the following is the correct syntax to define a content block named :sidebar in a Rails view?

easy

A. <%= yield :sidebar %>

B. <% content_for :sidebar = 'Sidebar content' %>

C. <% sidebar_content 'Sidebar content' %>

D. <%= content_for :sidebar do %>Sidebar content<% end %>

Solution

1. Step 1: Recall content_for block syntax

   The correct way is to use content_for :name do ... end with ERB tags.

2. Step 2: Check each option

   <%= content_for :sidebar do %>Sidebar content<% end %> uses <%= content_for :sidebar do %> ... <% end %> which is correct syntax. <% content_for :sidebar = 'Sidebar content' %> tries assignment incorrectly. <%= yield :sidebar %> is for yielding, not defining. <% sidebar_content 'Sidebar content' %> is invalid.

3. Final Answer:

   <%= content_for :sidebar do %>Sidebar content<% end %> -> Option D

4. Quick Check:

   Use content_for :name do ... end to define content [OK]

Hint: Use content_for :name do ... end to define blocks [OK]

Common Mistakes:

• Using assignment instead of block for content_for
• Confusing yield with content_for
• Missing ERB tags or using wrong ones

3. Given the layout code:

<html>
<body>
  <header><%= yield :header %></header>
  <main><%= yield %></main>
  <footer><%= yield :footer %></footer>
</body>
</html>

And the view code:

<%= content_for :header do %>Welcome Header<% end %>
Main content here
<%= content_for :footer do %>Footer Info<% end %>

What will be rendered inside the <main> tag?

medium

A. Footer Info

B. Welcome Header

C. Main content here

D. Nothing

Solution

1. Step 1: Understand yield usage in layout

   yield without arguments renders the main view content. yield :header and yield :footer render named content blocks.

2. Step 2: Identify main content in view

   The main content is the part outside content_for blocks: <p>Main content here</p>.

3. Final Answer:

   <p>Main content here</p> -> Option C

4. Quick Check:

   Main content = yield without args = <p>Main content here</p> [OK]

Hint: Main content is outside content_for, shown by plain yield [OK]

Common Mistakes:

• Thinking content_for blocks appear in main yield
• Confusing named yields with main yield
• Ignoring content outside content_for

4. You have this layout snippet:

<header><%= yield :title %></header>

And this view code:

<% content_for :title = 'Page Title' %>

Why does the title not appear in the header when rendering?

medium

A. Because content_for must use a block, not assignment

B. Because yield is missing in the layout

C. Because the layout file is not linked properly

D. Because content_for only works in controllers

Solution

1. Step 1: Check content_for syntax in view

   The code uses assignment content_for :title = 'Page Title', which is invalid syntax.

2. Step 2: Correct usage of content_for

   content_for requires a block: content_for :title do 'Page Title' end or content_for(:title) { 'Page Title' }.

3. Final Answer:

   Because content_for must use a block, not assignment -> Option A

4. Quick Check:

   content_for needs blocks, not assignment [OK]

Hint: Always use blocks with content_for, not assignment [OK]

Common Mistakes:

• Using assignment instead of block for content_for
• Forgetting to yield named content in layout
• Assuming content_for works in controllers

5. You want to create a layout that shows a custom page title if provided, or a default title otherwise. Which layout code correctly uses content_for and yield to achieve this?

hard

A. <title><%= content_for?(:title) ? yield(:title) : 'Default Title' %></title>

B. <title><%= yield(:title) || 'Default Title' %></title>

C. <title><%= content_for(:title) || 'Default Title' %></title>

D. <title><%= yield :title if content_for?(:title) %></title>

Solution

1. Step 1: Understand content_for? and yield

   content_for?(:title) checks if content was provided. yield(:title) outputs it.

2. Step 2: Check each option for fallback logic

   <title><%= content_for?(:title) ? yield(:title) : 'Default Title' %></title> uses a ternary to show yield(:title) if present, else 'Default Title'. <title><%= yield(:title) || 'Default Title' %></title> uses yield(:title) || 'Default Title' but yield(:title) returns nil if no content, so fallback works but less explicit. <title><%= content_for(:title) || 'Default Title' %></title> uses content_for(:title) which returns nil and does not output content. <title><%= yield :title if content_for?(:title) %></title> only yields if content exists but shows nothing otherwise.

3. Final Answer:

   <title><%= content_for?(:title) ? yield(:title) : 'Default Title' %></title> -> Option A

4. Quick Check:

   Use content_for? to check, then yield or fallback [OK]

Hint: Use content_for?(:name) to check before yielding [OK]

Common Mistakes:

• Using content_for instead of content_for? for checking
• Assuming yield(:name) returns empty string instead of nil
• Not providing fallback content