component naming

[raycohen]

-content and -for don't immediately resonate with which side of the wormhole is represented.
how about something like portal-input and portal-output ?

[raycohen]

I think it's particularly confusing to me because of the similarity to rails's content_for method.

If you wanted to get fancy you might be able to use ember's new hasBlock property, such that you only expose one component, when used in block form it is treated as input, and when used without a block it is output

[rlivsey]

Definitely open for some bikeshedding on the naming, I also want to use the new positional parameters stuff in Canary soon so you don't need the name= part and could just do {{portal-for "footer"}}.

I'm 👎 on using the same component name for both the input and output because that would make the component itself pretty messy (having all code mixed up in the same component).

{{portal-outlet}} could be a better name because of the parallels with the normal {{outlet}}.

[raycohen]

My imagination for how the "one-component" version would work is to delegate to two different (internal) components in the if/else with hasBlock. Not sure how implementing it would actually play out though.

[knownasilya]

I think having a block format for the portal-for would be nice for default content if the portal-content hasn't been used for that portal.