Feature Wiki
Tabs
Introduce a Hamburger Menu for Narrow Screens
Page Overview
[Hide]- 1 Summary
- 2 Problem Statement
- 3 Concept
- 4 User Interface Modifications
- 5 Non-Functional Implications
- 5.1 Security
- 5.2 Privacy
- 5.3 Accessibility Implications
- 6 Process Information
- 6.1 Involved Authorities
- 6.2 Contact
- 6.3 Funding
- 7 Discussion
- 8 Implementation
- 8.1 Description and Screenshots
- 8.2 Test Cases
- 8.3 Privacy
- 8.4 Approval
1 Summary
Replace the current bottom tab-style main menu on narrow screens with a hamburger control in the header. The control opens the Slate containing all available main-menu entries, with clear closing and back-navigation controls. Preserve existing menu configuration, permissions and entry functionality.
2 Problem Statement
On narrow screens, the main menu often displays only a subset of entries and places additional entries behind a “more”-entry. There is a spatial disconnect between the bottom trigger and the additional entries displayed at the top, together with insufficient closing controls and unclear orientation within opened menu sections. (see analysis)
A recent large-scale needs assessment identifies navigation and content discovery as major usability issues in ILIAS. Better and more intuitive navigation was the most frequently requested improvement. The open-ended feedback confirms a need for clearer overviews. These issues are especially relevant for mobile use, as smartphones and tablets are widely used and navigation is rated less favourably on smartphones.
3 Concept
Place a hamburger control on the left side of the header below a responsive breakpoint. Activating it opens a vertically scrollable Slate directly below or adjacent to the header, maintaining a clear spatial relationship with the trigger.
Show all main-menu entries available to the current user in their configured order. Remove the bottom tab strip in this layout.
Reuse the existing Main Bar and Slate mechanisms. Preserve contributed entries and their existing actions rather than requiring their migration to a new navigation model. When an entry opens another menu view, display its title and provide an explicit return to the main-menu overview. Existing inline accordion sections retain their interaction.
Keep closing available at every menu level. When open, the hamburger icon changes to an (X)-Icon. Opening a destination closes the mobile menu; navigating within the menu keeps it open.
The wide-screen Main Bar remains unchanged.
Note: The mockup uses a different design from the classic Slate entries. The styling changes are not part of this feature request. The mockup is only intended to illustrate the functionality and how it could be implemented.
I simply used an existing ILIAS hamburger menu solution from a platform and applied styling in the style of the ILIAS Drilldown to see how it would look. I really like the implementation in this style, and it is also a goal to make future changes to ILIAS styling. However, those changes are not part of this feature request.
As mentioned, this request is solely about implementing the main menu as a hamburger menu.

4 User Interface Modifications
4.1 List of Affected Views
- Global header and Main Bar - all views displaying the Main Bar below the responsive breakpoint; no dedicated breadcrumb
- Main-menu Slate - opened from the hamburger control; no dedicated breadcrumb
- Existing Main Bar tab strip - removed below the responsive breakpoint
4.2 User Interface Details
- Add a hamburger button with the aria-label “Open main menu”
- When the menu is open, replace the hamburger icon with an X and change its aria-label to “Close main menu”
- Display all available main-menu entries with readable labels and sufficiently large interaction areas
- Preserve existing entry actions, nested content and active-state indicators
- Support closing through the close control and Escape
- Move focus into the Slate when opened and return it to the trigger when closed
4.3 New User Interface Concepts
Introduce a responsive hamburger entry point for the existing main menu.
4.4 Technical Aspects
Adapt the responsive presentation and opening behaviour of the existing Main Bar and Slate. Preserve existing GlobalScreen contributions, permissions and menu configuration.
5 Non-Functional Implications
5.1 Security
No new endpoints, permissions or authentication mechanisms are proposed.
5.2 Privacy
No additional personal data or persistent user preferences are required.
5.3 Accessibility Implications
The trigger must expose its expanded state and identify the controlled Slate. Ensure keyboard operation, visible focus, accessible names and predictable focus management.
If the Slate is implemented as a modal overlay, prevent interaction with background content and contain focus while it is open.
6 Process Information
6.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Fuhrer, Thibeau [tfuhrer]
- Authority to Sign off Code Changes: Fuhrer, Thibeau [tfuhrer]
If this request is related to multiple components, please list both authorities for all related components.
6.2 Contact
Person to be contacted in case of questions about the feature or for funding offers: Becker, Matthias [matthias.becker]
6.3 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
7 Discussion
8 Implementation
Feature has been implemented by {Please add related profile link of this person}
8.1 Description and Screenshots
{ Description of the final implementation and the changed behaviour in the related components. Please add screenshots to visualise the changes if possible. }
8.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
8.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
8.4 Approval
Approved at {date} by {user}.
Last edited: Yesterday, 12:21, Becker, Matthias [matthias.becker]