Content
View differences
Updated by Wieland Lindenthal about 8 years ago
- \[x\] Replaces the project menu.
- \[x\] An arrow left leads back to the project’s menu
- \[x\] All pages of the wiki are shown in a tree structure
- \[x\] The tree branches are collapsible
- \[x\] Custom menu items are deactivated (but the code and data is not yet removed)
- \[ \] We need to agree where the (now) static wiki link links to (currently `/<project-identifier>/wiki/wiki`
- \[ \] Discussion: Why should we have the menu item “Start page” if that page is part of the page hierarchy anyways?
- \[ \] Show current page as selected.
- \[ \] Fix breadcumbs on wiki pages (“Wiki” is missing)
- \[ \] Fully I18n
- \[ \] Ensure accessability
- \[x\] \[ \] Try menu on mobile
- \[ \] Cleanup `_main_menu.css`
- \[ \] Convert main-menu-controller.js to angular
Out of scope:
- The current menu Item logic that adds items to the project menu stays untouched. \[UPDATE: it got deactivated for Wikis\]
- Order within siblings.
- \[x\] An arrow left leads back to the project’s menu
- \[x\] All pages of the wiki are shown in a tree structure
- \[x\] The tree branches are collapsible
- \[x\] Custom menu items are deactivated (but the code and data is not yet removed)
- \[ \] We need to agree where the (now) static wiki link links to (currently `/<project-identifier>/wiki/wiki`
- \[ \] Discussion: Why should we have the menu item “Start page” if that page is part of the page hierarchy anyways?
- \[ \] Show current page as selected.
- \[ \] Fix breadcumbs on wiki pages (“Wiki” is missing)
- \[ \] Fully I18n
- \[ \] Ensure accessability
- \[x\]
- \[ \] Cleanup `_main_menu.css`
- \[ \] Convert main-menu-controller.js to angular
Out of scope:
- The current menu Item logic that adds items to the project menu stays untouched. \[UPDATE: it got deactivated for Wikis\]
- Order within siblings.