Design
 Dropped
 
 

Description

Macaw Skin's purpose is to showcase ideas about our menus/actions organisation, integrated inside a mobile-oriented skin.

Proposal

ContextThere are users that complain that XWiki's menus are hard to use, being very complex and displaying a lot of options. 
Proposal ConclusionsPros Reduced clutter, focusing on most used actionsCons  In order to achieve a certain action the user might require 2+ clicks
Pros Optimised for mobile devicesCons 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
overviewDesktop.png

Tablet View
overviewTablet.png

Mobile View
overviewMobile.png

Global Menu

PurposeSimplify the available actions in the global menu
Place the main global actions in a drawer navigation

Drawer Activator
global1.png
global4.png

Search Activator
global2.png
global3.png

Drawer - Tablet View
drawerTablet.png

drawer.png

Primary Action

PurposeEasily identify the primary-action
Adjust the primary-action depending on the context
NotesBy default, the primary-action could be 'Edit'

An additional rule could be: 

  • all children-pages have 'Edit' as primary-action, 
  • while parents-pages have 'Add' as primary-action
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).
Alternative option: don't have a primary-action

Edit Page
primary-EditPage.png

Add User
primary-AddUser.png

Install Extension
primary-InstallExtension.png

Join Wiki
primary-JoinWiki.png

Content Menu

PurposeProvide page related actions
Depending on the context, adjust the menu content

Desktop View
contentDesktop.png

View Mode
contentView.png

Edit Mode
contentEdit.png


 

Tags:
Created by Ecaterina Moraru (Valica) on 2015/05/15 16:28
    

Get Connected