NO NEED FOR A MENU

[tavershimafx]

While I was working on modifying this project for a better, I discovered that there is actually no need for a menu.

1. The menu has actually been used for some set of fixed design (UI) cases, which the user may want to implement this same menu we are talking about several places. But in practice, these designs are fixed and some have been hardcoded into the source code with Ids which are fixed and cannot be deleted like we see in the footer. Footers change as we have seen how Microsoft's website footer has dynamically changed over the years. With our current design this can be achieved only be revisiting the source code then uploading a new push to our server which is an extreme case. It actually defiles our CMS principle of allowing the user edit dynamic content which is intended to change over time while the website is still running. Sometimes the user might want to create a new menu and let it show somewhere else. In the case of our menu, it has sub-menus which have been implemented as sub list items. Even the footer which we have currently on the platform is not supposed to have a sub menu as we have seen how good design practices does not allow us do that in the footer but a menu somewhere else might seriously be in need of that sub-menu.

someone might say lets then just create another menu to fix the situation. But how many menus will we keep on creating just to meet our theme UI requirements? the answer to this is simply to abondon the menu and go for a widget. Widgets have saved me alot in creating some nasty engineering, especially that property of a widget called AdditionalData. I add many properties to a widget without having to tamper with my database model.

In my recent project I have turned my category menu into a widget. this will be in the push I'm trying to send shortly. You can now hide almost anything on your webpage and make it look empty except for the main header as this does not change because its part of your theme design.