Actions

Difference between revisions of "Developer Area/Specifications in Development/App style navigation"

From Mahara Wiki

< Developer Area‎ | Specifications in Development
Line 1: Line 1:
 
=Implementation notes for the app-style navigation for Mahara 17.04=
 
=Implementation notes for the app-style navigation for Mahara 17.04=
  
We have [[Media:Mahara_app-style_nav_20170118.pdf | wireframes]] for the implementation.
+
[[File:App_style_nav_20170120.jpg | overview wireframe]]
 +
 
 +
We are using the responsive navigation everywhere also on desktop but move the admin navigation out so it's more easily accessible for those that require it. The admin icon is still to be decided on as it a bit too close to the "Settings" one.
  
 
The navigation is context-sensitive. That means that when you are anywhere in the "Content" area and you click the "Menu" icon, you see the "Content" navigation items directly and don't have to click on "Content" first. And when you are in "Portfolio", you see all menu items in that section. When you are in "Configure site" in the admin area, you see all those navigation elements etc.
 
The navigation is context-sensitive. That means that when you are anywhere in the "Content" area and you click the "Menu" icon, you see the "Content" navigation items directly and don't have to click on "Content" first. And when you are in "Portfolio", you see all menu items in that section. When you are in "Configure site" in the admin area, you see all those navigation elements etc.
  
The navigation overlays the page and you need to click on a navigation element or close the menu in order to do something on the page again.
+
In the transition period to the new navigation, we will keep the "old-style" navigation available in Mahara:
 
+
* Hide the drop-down menu option in site and institution settings.
The navigation for mobile devices stays the same with the hamburger when the screen size gets too small to display the regular menu.
+
* Keep the value in the database though.
 
+
* Duplicate the current raw theme and call it "Raw old navigation" keeping all current templates in place so that a site could switch the base theme from "Raw" (the new nav) to "Raw old nav" in order to regain the old navigation. If they want to change the value for the drop-down navigation, it would need to be done in the database though.
We will use Font Awesome icons as in other parts of the site.
+
* Have all built-in themes in Mahara use the new navigation, i.e. stay on the new "Raw" that has been stripped off the old navigation styles.
 
 
The "Drop-down menu" option would need to be removed from the "Configure site" -> "Site options -> "Site settings" as we will not have an alternative navigation.
 
  
=Ideas for the future beyond the intial implementation for Mahara 17.04=
+
=Ideas for the future beyond the initial implementation for Mahara 17.04=
  
The idea of showing a "strip" on the left for the menu is so we can also pin other elements there. This could be a user-defined option so that people can pin portfolios, artefacts or other frequently used menu items there in order to access them easily.
+
Be able to pin items under the user menu for easy access.

Revision as of 08:17, 25 January 2017

Implementation notes for the app-style navigation for Mahara 17.04

overview wireframe

We are using the responsive navigation everywhere also on desktop but move the admin navigation out so it's more easily accessible for those that require it. The admin icon is still to be decided on as it a bit too close to the "Settings" one.

The navigation is context-sensitive. That means that when you are anywhere in the "Content" area and you click the "Menu" icon, you see the "Content" navigation items directly and don't have to click on "Content" first. And when you are in "Portfolio", you see all menu items in that section. When you are in "Configure site" in the admin area, you see all those navigation elements etc.

In the transition period to the new navigation, we will keep the "old-style" navigation available in Mahara:

  • Hide the drop-down menu option in site and institution settings.
  • Keep the value in the database though.
  • Duplicate the current raw theme and call it "Raw old navigation" keeping all current templates in place so that a site could switch the base theme from "Raw" (the new nav) to "Raw old nav" in order to regain the old navigation. If they want to change the value for the drop-down navigation, it would need to be done in the database though.
  • Have all built-in themes in Mahara use the new navigation, i.e. stay on the new "Raw" that has been stripped off the old navigation styles.

Ideas for the future beyond the initial implementation for Mahara 17.04

Be able to pin items under the user menu for easy access.