Menu Navigation Structure Logic
Hello ok, need some help in terms of logic structuring a menu system whereupon my client can create their own header menu items, these will then display sidebar sub menus which will be individual to the page that the header menu is linked to. furthermore there maybe a sidebar submenu that maybe shared with 2 or more header menu items.
im thinking this would require 3 tables
and linking menu
the header menu will also contain its own small icon image.
also the way i want to display the URL links is using the MenuName (rather then an ID value)
Plus I want the client to be able to control which menu items from the database will be displayed on the header menu (for example 6 months down the line they may want to make one of the sidemenus to be the header menu item)
And this will also involve them create new header menu items and even deleting menu items at will.
the menu name will also be stored in a "content" table in the database so that when the menu item is clicked then the relating content from the content table is dynamacially displayed.
Im just wondering if I am overcomplicating my logic with the 3 tables? Can it be done with less tables or does it require more tables?
I want to sort out my logic before coding.
currently my tables are as follows:
#TopNavName (this is the actual displayed name of the link + will shows in the URL)
#TopNavIcon (this stored a graphic image)
#TopNavState (this allows for the top menu items to be displayed or temporary disabled)
#SubNavName (this is the actual displayed name of the link + will shows in the URL)
#SubNavState (this allows for the sub menu items to be displayed or temporary disabled)
If this is the correct approach then how can I join these tables together in the correct way to correctly display from my description?