While areas seem to be named quite well, many components still feature too technical sounding names. Please revisit all components and try to use declarative, non-technical terms to what a component contains or points to. It might be a good idea to ask Antti (or any other technical writer) for assistance.

During the user tests, this has caused several frowns. Having better names would have improved orientation significantly during some user tests, especially in complex scenarios involving nested components. Since the editor might not perform well in such cases, having better component names would have helped somewhat.

Names could be chosen to match expectations, e.g. if I've just added a Carousel, I'd like to see that name appear on the bars. So, in the example I've attached, instead of using "Stage"/"Teaser Group - Stage Paging"/"Teaser items"/"Teaser Group - Carousel item" we could e.g. use "Stage"/"Carousel"/"Carousel items"/"Single item", or if this has to remain somewhat more generic "Stage"/"Stage item"/"Carousel"/"Carousel item".