We are trying to solve a seemingly related problem, and I am wondering if this is going the same direction.
I've not tried the module, but would be happy to, if this module aims to solve a similar scenario.
On our intranet we have "information-portals" based on organic-groups in D7 with this structure:
Portal (a custom node type "information portal")
-- Portalpage 1
-- Portalpage 2
-- -- Portalpage 2a
-- -- Portalpage 2b
-- -- Portalpage 2c
-- -- Portalpage 2d
-- Portalpage 3
-- -- Portalpage 3a
-- -- Portalpage 3b
-- -- Portalpage 3c
-- -- Portalpage 3d
At the moment the intranet has many (thousands) information-portals. Each portal has its own editorial team. In D7 editorial access is managed by organic-groups, as every portal is also a group with a group menu.
In D10 we would like to use the group module so that one group could manage many portals with its sub content (pages, events, news, ...)
The challenge is to have an editor friendly, intuitive way to manage thousands of portals, portal-menus and the related portal content, since editors can not be expected to manually arrange group content and group menus into individual information-portals.
It becomes even more important if information-portals are private, where read access is based on group membership. For private groups with many (hundreds) members it is essential to manage the members once for multiple related portals and portal content.
I agree with mmenavas #20
It's hard to test and provide feedback without this being merged