Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Sinatra extension to use a `content_for` helper similar to Rails' – Don't use it, use Sinatra::Contrib instead.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 test
Octocat-spinner-32 .gitignore
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README.rdoc Mark that the gem is obsolete
Octocat-spinner-32 Rakefile
Octocat-spinner-32 sinatra-content-for.gemspec renamed "sr-mg" to "mg" ?
README.rdoc

This project is no longer maintained. See github.com/sinatra/sinatra-contrib

Sinatra::Contrib is a project maintained by the sinatra core team that packages several small widely used extensions, such as content_for. Please install that as that is actively maintained and compatibility is ensured with all future versions of sinatra.

ContentFor

Small extension for the Sinatra web framework that allows you to use the following helpers in your views:

<% content_for :some_key do %>
  <chunk of="html">...</chunk>
<% end %>

<% yield_content :some_key %>

This allows you to capture blocks inside views to be rendered later in this request. For example, to populate different parts of your layout from your view.

When using this with the Haml rendering engine, you should do the following:

- content_for :some_key do
  %chunk{ :of => "html" } ...

= yield_content :some_key

Note that with ERB yield_content is called without an '=' block (<%= %>), but with Haml it uses = yield_content.

Using an '=' block in ERB will output the content twice for each block, so if you have problems with that, make sure to check for this.

Usage

If you're writing “classic” style apps, then requring sinatra/content_for should be enough. If you're writing “classy” apps, then you also need to call helpers Sinatra::ContentFor in your app definition.

And how is this useful?

For example, some of your views might need a few javascript tags and stylesheets, but you don't want to force this files in all your pages. Then you can put <% yield_content :scripts_and_styles %> on your layout, inside the <head> tag, and each view can call content_for setting the appropriate set of tags that should be added to the layout.

Credits

Code by foca, inspired on the Ruby on Rails helpers with the same name. Haml support by mattly.

Something went wrong with that request. Please try again.