Hi Guillaume, Thanks for starting this thread. ---------------------------------------------------------- Current Drawer analysis: Languages ( L / G ) --- Home ( G ) [N] --- Administer wiki ( L ) [A] [W] --- Wiki Index ( G ) [I] [W] Page Index ( L ) [I] User Index ( L / G ) [I] Applications Index ( L) [I] --- Create wiki ( G ) [A] [W] --- Delete wiki ( L ) [A] [W] L = Local/Wiki setting/action/effect G = Global/Farm setting/action/effect N = Navigation A = Action W = Wiki entity ---------------------------------------------------------- Some examples of grouping: 1. Local / Global effect grouping (ex. Main/Subwiki actions should be grouped) 2. Entities grouping (Wiki related actions should be grouped: create, administer, delete, etc.) 3. Index grouping (group all index applications together) 4. Navigation grouping (to Main wiki or other wikis) 5. Actions grouping 6. other? So the main question is what grouping would we want to prioritize first: 1-5? ---------------------------------------------------------- Some things to consider: A. Naming consistency: A1. Across wiki: we need to consider the terms usage. For example Home vs. Homepage; Wiki vs. Subwiki; Settings vs. Administration; Wiki Index vs. Browse all wikis vs. Show all wikis -- We need to align these usages and pick the one most relevant for the end user and correct as terminology A2. Across the menu: this implies having all entries plural/singular or having the same additional text (ex. do we mark Indexes the same way? Administer wiki / Delete this wiki / Create a new wiki, etc.) B. Explicit (vs. Cryptic) -- how explicit should we make the labels vs. icons usage C. Quick access to local actions -- in subwikis we should optimize for local actions and try to display them first, since some teams might have dedicated wikis and the main wiki could be used just as a portal or as a farm D. Order most used actions first -- for example 'Delete wiki' is not a very used action E. Navigation vs. Actions grouping E1. Actions removal -- for example we could even remove 'Delete wiki' action and consider that the wiki management actions can be accessed just from Wiki Index -- this would mean that 'Administrate wiki' would be removed too, and we use that action a lot in the initial configuration phases, so that would increase the time to reach Administration E2. Adding more wiki navigation -- For example http://jira.xwiki.org/browse/XWIKI-12538 talks about having a way to add quick access to other subwikis (ideally as favorites, since listing all wikis does not scale) ---------------------------------------------------------- Proposals grouping feedback: Current. -1 (Local/Global), -2 (Wiki grouping), +3 (Indexes), partial 4 (Navigation), -5 (Actions) || +A2 (Naming consistency), -C (Quick access) P1. -1 (Local/Global), partial 2 (Wiki grouping), +3 (indexes), partial 4 (Navigation), partial 5 (Actions) || +A2 (Naming consistency), -C (Quick access) P2. partial 1 (Local/Global), -2 (Wiki grouping), partial 3 (Indexes), -4 (Navigation), -5 (Actions) || +A2 (Naming consistency), +C (Quick access) P3. partial 1 (Local/Global), -2 (Wiki grouping), +3 (Indexes), -4 (Navigation), -5 (Actions) || +A2 (Naming consistency), +C (Quick access) P4. -1 (Local/Global), partial 2 (Wiki grouping), +3 (Indexes), -4 (Navigation), +5 (Actions) || +A2 (Naming consistency), partial C (Quick access) ---------------------------------------------------------- The problem is that when you approach an usability problem using these kind of grouping / grading it's very easy to fall in the 'technicalities' trap and not think about the user perspective. So although I understand why I proposed P1-4, for users it will not make sense. That's why I like P5, because the grouping comes natural and is more explicit, although is not using the consistent terminology. P5: +1 (Local/Global), -2 (Wiki grouping), -3 (Indexes), partial 4 (Navigation), -5 (Actions) || -A2 (Naming consistency), -A1 (Across wiki), +B (Explicit), +C (Quick access to local), ? D (Most used actions) Things to fix for P5: - Think where to fit the "Languages" - A1 + A2: we need to think about the naming of Indexes (especially Wiki Index in this case) and fix them in drawer and across; replace Settings with Administration; fix the "Go to ..."; consistent actions naming. Additionally we should fix A1 (see http://jira.xwiki.org/browse/X WIKI-9363) ---------------------------------------------------------- Before starting this thread I tried to rethink about a new solution and I came up with P6: -1 (Local/Global), +2 (Wiki grouping), +3 (Indexes), +4 (Navigation), +5 (Actions) || +A2 (Naming consistency), -A1 (Across wiki), -B (Cryptic/Iconography), -C (Quick access), ? D (Most used actions), +E2 (More navigation) i) Having Indexes listed before local actions (will give a -C for quick access), but the advantage is that the menu composition will change less if we visit main wiki vs. subwikis. P5 also have this propety. ii) I've grouped and added more navigation by providing the list of wikis. There are several problems with this approach: ii.1 - not scalable for large number of wikis (even though I've put an accordion there) ii.2 - cryptic actions (icon usage for Create, Administration, Delete wiki) ii.3 - mobile issues (because the icons are very small and we will need a different layout for mobiles or we might have problems with large wiki names) ---------------------------------------------------------- Thanks, Caty On Wed, Oct 26, 2016 at 11:42 AM, Miroslav Galajda < miroslav.galajda(a)gmail.com&gt; wrote:

Hi Guillaume, Thanks for starting this thread. ---------------------------------------------------------- Current Drawer analysis: Languages ( L / G ) --- Home ( G ) [N] --- Administer wiki ( L ) [A] [W] --- Wiki Index ( G ) [I] [W] Page Index ( L ) [I] User Index ( L / G ) [I] Applications Index ( L) [I] --- Create wiki ( G ) [A] [W] --- Delete wiki ( L ) [A] [W] L = Local/Wiki setting/action/effect G = Global/Farm setting/action/effect N = Navigation A = Action W = Wiki entity ---------------------------------------------------------- Some examples of grouping: 1. Local / Global effect grouping (ex. Main/Subwiki actions should be grouped) 2. Entities grouping (Wiki related actions should be grouped: create, administer, delete, etc.) 3. Index grouping (group all index applications together) 4. Navigation grouping (to Main wiki or other wikis) 5. Actions grouping 6. other? So the main question is what grouping would we want to prioritize first: 1-5? ---------------------------------------------------------- Some things to consider: A. Naming consistency:

A1. Across wiki: we need to consider the terms usage. For example Home

Homepage; Wiki vs. Subwiki; Settings vs. Administration; Wiki Index vs. Browse all wikis vs. Show all wikis -- We need to align these usages and pick the one most relevant for the

user and correct as terminology

A2. Across the menu: this implies having all entries plural/singular or having the same additional text (ex. do we mark Indexes the same way? Administer wiki / Delete this wiki / Create a new wiki, etc.) B. Explicit (vs. Cryptic) -- how explicit should we make the labels vs. icons usage C. Quick access to local actions -- in subwikis we should optimize for local actions and try to display

first, since some teams might have dedicated wikis and the main wiki

be used just as a portal or as a farm D. Order most used actions first -- for example 'Delete wiki' is not a very used action E. Navigation vs. Actions grouping E1. Actions removal

-- for example we could even remove 'Delete wiki' action and consider

the wiki management actions can be accessed just from Wiki Index

-- this would mean that 'Administrate wiki' would be removed too, and we use that action a lot in the initial configuration phases, so that would increase the time to reach Administration

E2. Adding more wiki navigation -- For example http://jira.xwiki.org/browse/XWIKI-12538 talks about

a way to add quick access to other subwikis (ideally as favorites, since listing all wikis does not scale) ---------------------------------------------------------- Proposals grouping feedback: Current. -1 (Local/Global), -2 (Wiki grouping), +3 (Indexes), partial 4 (Navigation), -5 (Actions) || +A2 (Naming consistency), -C (Quick access) P1. -1 (Local/Global), partial 2 (Wiki grouping), +3 (indexes), partial 4 (Navigation), partial 5 (Actions) || +A2 (Naming consistency), -C (Quick access) P2. partial 1 (Local/Global), -2 (Wiki grouping), partial 3 (Indexes), -4 (Navigation), -5 (Actions) || +A2 (Naming consistency), +C (Quick access) P3. partial 1 (Local/Global), -2 (Wiki grouping), +3 (Indexes), -4 (Navigation), -5 (Actions) || +A2 (Naming consistency), +C (Quick access) P4. -1 (Local/Global), partial 2 (Wiki grouping), +3 (Indexes), -4 (Navigation), +5 (Actions) || +A2 (Naming consistency), partial C (Quick access) ---------------------------------------------------------- The problem is that when you approach an usability problem using these

of grouping / grading it's very easy to fall in the 'technicalities' trap and not think about the user perspective. So although I understand why I proposed P1-4, for users it will not make sense. That's why I like P5, because the grouping comes natural and is

explicit, although is not using the consistent terminology. P5: +1 (Local/Global), -2 (Wiki grouping), -3 (Indexes), partial 4 (Navigation), -5 (Actions) || -A2 (Naming consistency), -A1 (Across

+B (Explicit), +C (Quick access to local), ? D (Most used actions) Things to fix for P5: - Think where to fit the "Languages" - A1 + A2: we need to think about the naming of Indexes (especially Wiki Index in this case) and fix them in drawer and across; replace Settings with Administration; fix the "Go to ..."; consistent actions naming. Additionally we should fix A1 (see http://jira.xwiki.org/browse/

) ---------------------------------------------------------- Before starting this thread I tried to rethink about a new solution and I came up with P6: -1 (Local/Global), +2 (Wiki grouping), +3 (Indexes), +4 (Navigation), +5 (Actions) || +A2 (Naming consistency), -A1 (Across wiki), -B (Cryptic/Iconography), -C (Quick access), ? D (Most used actions), +E2 (More navigation) i) Having Indexes listed before local actions (will give a -C for quick access), but the advantage is that the menu composition will change less

we visit main wiki vs. subwikis. P5 also have this propety. ii) I've grouped and added more navigation by providing the list of

There are several problems with this approach: ii.1 - not scalable for large number of wikis (even though I've put an accordion there) ii.2 - cryptic actions (icon usage for Create, Administration, Delete

ii.3 - mobile issues (because the icons are very small and we will need a different layout for mobiles or we might have problems with large wiki names) ---------------------------------------------------------- Thanks, Caty On Wed, Oct 26, 2016 at 11:42 AM, Miroslav Galajda < miroslav.galajda(a)gmail.com&gt; wrote: http://jira.xwiki.org/browse/ > > > XWIKI-13070. > > > > > > The problem is that the current order (that I have implemented

on that based > on > > > a consensus. > > > > > > Here are mine: > > > > > > P1: There is a logical order and separation between item. However,

> > > seems the more used actions (Wiki Index, Page Index) are less

> > than > > > some other (Delete Wiki, Create Wiki...) > > > > > > P2: The order and the separation are logic. The "delete wiki"

is > > > still very visible but all other items are good. > > > > > > P3: Same than P2. Except that having "Wiki Index" along with "User, > Page > > > and Application Index" mixes up local and global items. > > > > > > P4: Why not, but maybe the 3 first actions should be placed after

mixing items because I _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs