Group & Sub Group Features?

Group is a monster of a module!

*chuckles* I'm in danger

So it has about 3 content entities, which are straight fwd enough. Its when we get into the roles, permissions and config entities that it'll possibly get weird.

Really depends on what you think you'll need to fetch and what you'll need to do with that fetched data. Possibly to recreate Groups "out of the box", thats more of a JSON:API thing. It's very Drupally.

Alternatively, can you build views to get the data you need for groups?

If I was going to roadmap it, I'd say... I have a client that uses Group, so I could possibly find some integrated development there - But I don't understand enough about subgroup's structure yet. So it's possible to look at soon™.

Do you have any ideas on what data you would require, at a minimum?

Thanks for the update. I am migrating from the GraphQl V3 module which I am using in a readonly mode at present.

With the group module I provide an organisation (group) to have multiple venues (subgroup) which link to a variety of nodes to build a digital guide (Museum's Art Galleries etc). Example https://wam.experienceplus.digital

I think views would be a good approach because the org/venue views are pretty straightforward lists with a few entity references on them.

Thank you,
Danny

Yeah nice,
I'll change this status to Postponed. Let me know back if you have any major hurdles I can help with.