Why Layouts and content_for in Ruby on Rails? - Purpose & Use Cases

The Big Idea

Discover how to stop repeating yourself and make your website easier to build and update!

The Scenario

Imagine building a website where every page needs the same header, footer, and sidebar. You have to copy and paste the same HTML into every page file.

The Problem

Copying the same code everywhere is tiring and risky. If you want to change the header, you must update every page manually. This wastes time and can cause mistakes.

The Solution

Rails layouts let you define a common page structure once. The content_for method lets you insert unique content into specific parts of the layout easily.

Before vs After

✗ Before

<header>Site Header</header>
<p>Page content here</p>
<footer>Site Footer</footer>

✓ After

<!-- layout.html.erb -->
<header>Site Header</header>
<%= yield %>
<footer>Site Footer</footer>

<!-- page.html.erb -->
<p>Page content here</p>

What It Enables

You can build consistent pages quickly and update shared parts in one place, making your site easier to maintain and grow.

Real Life Example

Think of a blog where every post shares the same menu and footer. Using layouts and content_for, you only write the menu once, and each post adds its own title and content.

Key Takeaways

Layouts provide a shared page structure for all views.

content_for lets you add custom content to layout sections.

This approach saves time and reduces errors when updating your site.