I'm having trouble with this because my main application is an intranet. There sitemap is complex, yet some modules by themselves would warrant a nested menu.
Currently I'm getting by using buttons, tabs, and dropdowns, but a nested menu would be the fastest way to navigate the site. The mobile access is very useful, though, so I'm not going to break it by hacking the nested menu back. Since I have lots to learn about design, I just wanted to see how others were coping with this change. On Monday, April 4, 2016 at 12:03:02 PM UTC-5, Leonel Câmara wrote: > > The good alternative to 3rd level menus is to actually rethink your > website and how you present the information. 3rd levels menus happen mostly > due to laziness, not wanting to make choices and having everything in the > menu. The menu is NOT a sitemap and not everything needs to be accessed via > the menu. The menu should only have the links to the absolutely most > commonly visited areas. Other stuff can go to the footer or appear > contextually where it makes sense. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
