In cases such as this, we have a separate "webin" siteaccess. Then, we can create an editor-specific full view override template for the special container classes. The template lists the children, even with edit buttons next to them if necessary. To preserve the ability for editors to see what their content is going to look like, they can always use the preview functionality and select a different siteaccess.
I'll think about an adaptation of this solution because I'm working on a website factory and I wanted to avoid to duplicate the siteaccesses for each site if possible...
