Macaw Skin
Last modified by Vincent Massol on 2024/02/26 17:57
- [Iteration][UX] Macaw Skin - simplifying global and content menus http://markmail.org/thread/py42qcwl7c5pkebr (May 15, 2015)
- Totem Application (May 2015)
- Extended Breadcrumb (May 2015)
- Nested: Drawer (Jun 2015)
Description
Macaw Skin's purpose is to showcase ideas about our menus/actions organisation, integrated inside a mobile-oriented skin.
Proposal
Context | There are users that complain that XWiki's menus are hard to use, being very complex and displaying a lot of options. | |
Proposal Conclusions | Reduced clutter, focusing on most used actions | In order to achieve a certain action the user might require 2+ clicks |
Optimised for mobile devices | Since not all actions are displayed at a certain moment, the user needs to change the context in order to launch a certain action |
Disclaimer:
- This is not a skin for developer usage. It's purpose is to be as simple as possible to be used, focusing on the main action that can be done on a particular page.
- Development should be done on Flamingo skin or another skin that is not hiding complex actions under multiple user clicks. Another solution would be to activate a development custom menu that contains actions like: edit rights, edit class, edit objects, etc.
Navigation:
- Actions for a certain type of entity will be done on the entity page. example: if you want to delete a space, the action will not be displayed in the actionmenu, but it will available in the Spaces Index menus.
- The rationale behind is that: we put emphasis on often user actions, hiding the seldom actions.
Overview
Desktop View
Tablet View
Mobile View
Global Menu
Purpose | Simplify the available actions in the global menu |
Place the main global actions in a drawer navigation |
Drawer Activator
Search Activator
Drawer - Tablet View
Primary Action
Purpose | Easily identify the primary-action |
Adjust the primary-action depending on the context | |
Notes | By default, the primary-action could be 'Edit' |
An additional rule could be:
| |
Application developers would overwrite the default primary-actions using an extension point | |
Allow shifting primary-action's type depending on user's status (registered, hasRight). |
Edit Page
Add User
Install Extension
Join Wiki
Content Menu
Purpose | Provide page related actions |
Depending on the context, adjust the menu content |
Desktop View
View Mode
Edit Mode