An equivalent to Rails’s `content_for`?

Let’s say I wish to display various resources with a common layout consisting of a toolbar and a list. In Rails, I might do something like the following:


<div class="toolbar">{{yield :toolbar}}</div>


<%= content_for :toolbar do %>
  <%= render partial: "toolbar" %>
<% end %>


<%= content_for :toolbar do %>
  <%= render partial: "toolbar" %>
<% end %>


<button>New User</button>


<button>New User</button>

In Ember:

router.js {


<div class="toolbar">{{outlet 'toolbar'}}</div>


App.ResourceRoute = Em.Route.extend({
  renderTemplate: function() {
  renderContent: function(name, options) {
    options = Em.$.extend(options, { outlet: name });
    try {
      this.render(this.get('routeName') + '/' + name, options);
    } catch (e) {}


App.UsersRoute = App.ResourceRoute.extend();


App.PostsRoute = App.ResourceRoute.extend();   


<button>New User</button>


<button>New Post</button>

Each resource route extends App.ResourceRoute which renders RESOURCE_NAME/toolbar into the toolbar outlet.


Is this a sensible approach? Could this pattern be improved?

The toolbar shouldn’t be an outlet helper. Use a Component instead. That’s why you have to make that extra resource route with the render content function, which essentially kind of duplicates what Ember would give you for free.

I’ve got some time right now, so if you still need help, I can extend that jsbin for you to implement the toolbar component.

Thanks. Are you suggesting that every template have a toolbar component?

Like this?

Yes, that’s how to do it. Notice how that simplified the logic and templates.It’s also reusable across this, and any other Ember App. Ember guides you toward a more composable, component architecture, but especially recently when Web Components got mainstream.

Yes, it appears more concise for that example for sure. The downside is that it requires the component to be included in each template, whereas in the previous version the markup only exists in the application template (or “layout”), and is filled in as required.

I guess what I’m trying achieve is templates that are free from as much required common “layout” markup as possible.

In this example the toolbar is present regardless of whether there are buttons or not, and can be filled in by creating a toolbar template. Consider this toolbar required layout markup.

With the components method, a developer would need to include an empty toolbar component to achieve the same effect.

It’s only a subtle difference, but there is something that feels incorrect about duplicating layout markup.

I hope that makes sense!?

I don’t know much about Rails anymore so I’m kinda lost right now. I think it’s a totally valid question, so I’ll defer to someone that knows more, but I’ll pop back in if I can think of something soon.


I’m not sure if I’ve articulated the problem particularly well. I’m currently working on the ember inspector (itself an ember app). application.hbs includes something like this:


and the desired layout is something like:




I could change the application template so that it just contains the main {{outlet}}, and include the header, custom view, and footer templates within each “leaf” template, but that seems to be rather a lot of repetition.

Thanks again

I’ve just extracted something from our (in progress) app which might help.

It lets you render to an outlet as normal but handles all the edge cases where you need to re-render etc…

Eg consider the layout:

{{outlet "header"}}
  • / has a default header
  • /foo has a custom header
  • /foo/bar/ doesn’t change the header
  • /foo/bar/baz sets a new header

When going from /foo/bar/baz/foo/bar we want to re-render the header from /foo but normally exiting /foo/bar/baz will just clear the outlet. This addon handles all that stuff.

If you’re using ember-cli it’s just a npm install --save-dev ember-render-stack away, it’s on Github here along with the usage instructions.

Hopefully it’s of some use.

That looks really great. We currently don’t have the need to re-render the header from a parent route, but it certainly looks useful.

Out of interest, how are you standardising outlet rendering across routes? Are you subclassing e.g.:

App.BaseRoute = Em.Route.extend(StackRouteMixin, {
  renderStack: function() {
    this.renderToStack(this.get('routeName') + '/nav, {
      outlet: 'navigation'

App.ResourceRoute = App.BaseRoute.extend();
App.AnotherResourceRoute = App.BaseRoute.extend();

We currently handle it on a route by route basis as there are many resources which don’t change the outlet and just use their parent’s ones. We have two or three different outlets which we update on a case by case basis - contextual navigation, header content etc…

If every resource has its own template for the outlet then something like your example would work well.

1 Like