Also want to mention the fact the new zones are not added to any of the automatically generated menu's, which means anyone who uses zones will have to switch to manually managing their menu's.

Hi,

As this is 'private' I'm going to respond directly rather than keeping it open.

I'm setting as won't fix, but I'll try and cover each point.

1) I think you're saying a zone xxx should create a page xxx in it by default. I don't see it like that actually. I have no idea what someone might put in a zone, it could just be transparent redirects to modules in other zones for example, I would not want to assume.

2) The sitemap menus use the 'page groupings' system, and a new zone doesn't fit cleanly into that. There is a config option to change the string defining how the default menus are constructed, I believe you could change that to not use page groupings then each drop-down would be a zone instead of a page grouping. However, one of the strongest reasons for these autogenerated menus is to help people build simple sites - having Composr be simple by default. If people are making zones, they're not making a simple site anymore, they are deep within authoring a site with a deep structure - so expecting them to learn a menu editor isn't a big ask. It's kind of having a cake and eating it situation - we can't make Composr incredibly flexible and powerful for advanced sites, while also being able to make every decision on behalf of people so they can avoid learning the technologies - simple by default, but customisable for those who learn the tech.

3) Yes, we don't create panels by default for new zones now. It's easy to add a new menu block in though using the zone editor. Wherever possible I'd rather we not bake in unnecessary assumptions and code overhead.

Understood and agreed with.