Switch sidebar menu logic to use layouts

[andrewtavis]

Terms

• I have searched open and closed feature requests
• I agree to follow activist's Code of Conduct

Description

In discussing some bugs for the platform, a decision was made that the current way that we're deriving the sidebar menus is brittle because it's being determined based on URL based checks. We should instead determine this based on the actual routes using layouts - i.e. all /organizations pages would have a layout with the given sidebar menu.

Contribution

Happy to look into this! 😊

[andrewtavis]

Note here that we need to further hoist other component logic into the layouts, not just the sidebar :)

[andrewtavis]

• For /organization/UUID routes we want to be making one call on the layout level that then instantiates all needed components for a given page based on the route and getting the id
• For /organizations/UUID/groups/UUID we would create a sub layout of the organizations layout to then bring in the organization through the parent layout
• For /events/UUID we would need to do two different calls via the event layout

[kirasvg]

Hi @andrewtavis ,I would like to work on this issue. Could you please assign it to me?

[andrewtavis]

Hi @kirasvg 👋 This is a pretty pressing issue and is likely something that I'll pick up in the coming days. If something changes or I'm able to break it down a bit better then I'll let you know! As it stands there are just so many changes that will need to happen.

Thanks for your interest, and please let us know if there's something else you'd have interest in working on in the meantime!