Custom sidenav in Gnav menu on mobile

[yesil]

In order to provide a smooth navigation experience on mobile for SPA applications like Plans, Business Plans, Catalog etc, can we imagine rendering the navbar(Categories) on the sections 1 or 2 as in the below screenshot?
Currently, the sidenav becomes a dropdown inside a sticky menu and gnav's menu icon is disabled in order to avoid overlaps on mobile.

I'm not sure what Consonant recommends on this, would like to hear their feedback.

https://www.adobe.com/creativecloud/plans.html
https://www.adobe.com/creativecloud/business-plans.html
https://www.adobe.com/products/catalog.html

[overmyheadandbody]

Usually there is no nav content on these pages, just brand and profile. In this scenario, we don't load a hamburger menu at all. This was requested explicitly and committed as part of #860. So I'm not sure if your request matches our requirements.

Moreover, I'm not sure we'd want to combine the main navigation with the aside one. From a UX perspective it might be odd to get two different types of content mixed - one is page-specific, one is site/consumer-specific. Also, the categories are always visible right now, moving them to the hamburger menu would require users to perform additional actions to see page-relevant content. We also need to think about the keyboard navigation/accessibility requirements that need to follow a particular pattern; adding mixed content in the nav has potential of great overhead for our logic. Lastly, the categories would need to be moved in the DOM based on device type, which might not be an efficient approach.

[yesil]

The hamburger menu provides a convenient and standardised method for discovering contextual actions on mobile devices. In my opinion, clicking on a dropdown on mobile is not preferable to clicking on the hamburger menu and then selecting a specific action from the side navigation.

adding mixed content in the nav has potential of great overhead for our logic

For visitors, there may be no noticeable difference between mixed content items. They simply represent a set of actions that lead to different pages or in-page actions.

Considering accessibility, most websites hide actions within the hamburger menu.
If this approach posed any accessibility issues, it is unlikely that it would have been widely adopted.

I'm not a UX expert, but I think it's important for us to discuss this matter before migrating those applications to Milo.

[honstar]

Is this a business-driven use-case @yesil ? If so, it definitely needs to be routed via the Consonant team.

[yesil]

@honstar it is part of my due diligence for the migration of Plans.
I'm exploring the pros and cons.
After initial discussion, I'll consider reaching out to Consonant team or abandoning the idea.