Centralizing CC and DC Gnav Large Menu Authoring

[jmatadobe]

Gnav Large Menu (Section Menu / AEM Mega Menu) is authored in multiple projects today in Feds on Milo because of the decentralized authoring approach.

This will allow individual teams to potentially change the Large Menu, resulting in inconsistent experiences and unwanted experiences being pushed out to different sites. It will also require any new updates to the Large Menu section to be made at multiple locations.

CC and DC GWP Teams are requesting to centralize the Gnav Large Menu authoring for their teams so that it is easy for them to manage the Feds Milo Gnav.

[auniverseaway]

You can already centralize the authoring of gnav. You can either do this through libs or you can self-host in CC.

I think long term, /libs/feds is the place, but @narcis-radu would have the most up to date info.

I'm still not personally convinced of this need, but we do support it.

[overmyheadandbody]

Yes, that's the direction we're looking into - centralise section menus in the /libs/feds folder. So for example, on a Photoshop page, the gnav.docx file would still live in the CC Sharepoint. Just the Creativity & Design section/cloud menu would live under /libs/feds to make sure cloud menus stay consistent across properties. Same might be done for the footer eventually.

[gabr1ela]

I agree with @overmyheadandbody centralising is the way to go with current requirements and avoid inconsistencies.