https://github.com/foca/sinatra-content-for
Sinatra extension to use a `content_for` helper similar to Rails' – Don't use it, use Sinatra::Contrib instead.
https://github.com/foca/sinatra-content-for
Last synced: 11 months ago
JSON representation
Sinatra extension to use a `content_for` helper similar to Rails' – Don't use it, use Sinatra::Contrib instead.
- Host: GitHub
- URL: https://github.com/foca/sinatra-content-for
- Owner: foca
- License: mit
- Created: 2009-05-07T05:59:28.000Z (about 17 years ago)
- Default Branch: master
- Last Pushed: 2014-03-20T05:39:28.000Z (over 12 years ago)
- Last Synced: 2023-04-10T10:20:05.568Z (about 3 years ago)
- Language: Ruby
- Homepage: http://github.com/sinatra/sinatra-contrib
- Size: 134 KB
- Stars: 66
- Watchers: 2
- Forks: 13
- Open Issues: 0
-
Metadata Files:
- Readme: README.rdoc
- License: LICENSE
Awesome Lists containing this project
README
= This project is no longer maintained. See http://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[http://sinatrarb.com] web framework
that allows you to use the following helpers in your views:
<% content_for :some_key do %>
...
<% 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 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[http://github.com/foca], inspired on the Ruby on Rails
helpers with the same name. Haml support by mattly[http://github.com/mattly].