The first time you call it, it works great. The second time you call it, it prints out the data from the first block AND the second block. The third time it renders the block information from the first call AND the second call AND the third; and so on and so on.

def with_partial(name, options = nil, &block)
  content_for(name.to_sym, &block)
  concat(render(:partial => name.to_s, :locals => options), block.binding)
end

Then your partial could be:

  < % with_partial :sidebar, :title => 'Hello word' do %>

And now back to the way I was doing things before

Item
Item
Item


  < % end %>

And the partial _sidebar.rhtml could be:

< %= title %>

        < %= yield :sidebar %>
      

*Logan*: You’re right. I had my terms mixed up. Thanks for the heads up.

*Jules*: there is that, but it’s not something that can be cached as a fragment.

*John*: Look at the “@concat@ method”:http://api.rubyonrails.org/classes/ActionView/Helpers/TextHelper.html#M000611. It’s more of a function of Binding than it is a String’s concat. I got this syntax from rails’ “@form_for@ method”:http://api.rubyonrails.com/classes/ActionView/Helpers/FormHelper.html#M000491 and I’m not 100% sure how Bindings work as of yet.

Wouldn’t this append start after the block’s text? If it doesn’t, then how is it possible that this works?
concat(end, block.binding)

wouldn’t the end go at the front of it all? sorry, somewhat confused by concat’s and bindings.

def create_sidebar(html, &block)
  raise ArgumentError, “Missing block” unless block_given?
  case html.length
  when 1
    concat(html[0], block.binding)
    block.call
    concat(‘</div>’, block.binding)
  else
    concat(html[0], block.binding)
    create_sidebar(html[1..html.length], block)
    concat(‘</div>’, block.binding)
  end
end

My ruby is a little rusty so this isnt the most elegant implementation im sure…but the point remains that it feels natural to write nested div elements using a recursive algorithm.