An example of how to create advanced component APIs by combining ember-portal and contextual components.

{{#test-yields as |portals|}}
  {{#portals.header}}
    Header
  {{/portals.header}}

  Body

  {{#portals.footer}}
    Footer
  {{/portals.footer}}
{{/test-yields}}

Run this app for the working version. Note that you can use the component multiple times and the portals will "wormhole" into the correct instance of the component.

You can also nest components with portals.

See the component definition here.

1. Currently the portal components that the user uses, leave remnant DOM nodes, which you might have to account for in your CSS. They will be wherever the user placed them in the component's block. Using tagName="" prevents nested divs, but still renders a div where the portal was used in the block.

2. Using the same portal multiple times in the same block will only render the last portal of that type in the block. Workaround: Add showingPortalItem=true to the portal-content to append instead of replace.

• slots rfc

See the ember-cli 1.13 readme template for basic instructions.