Description

Exploring the wiki from the WYSIWYG editor

• Exploring the wiki from the WYSIWYG editor

1) Wizard

Mockup

Pros / Cons

Pros

• Scalable : we can have multiple wikis + spaces (even a space hierarchy)
• Easy to use: users are guided throughout the process of selecting an item
• The dialog size is fixed, action buttons are always at the same position on screen
• The dialog doesn't looked oversized compared to the WYSIWYG
• Small footprint: can be used even on low resolution displays
• Since it's a wizard it's highly extensible
  Cons

• 3 or 4 steps are necessary to reach the current document
• Does not provide a global overview of where the user is located in the wiki's hierarchy

2) Finder

Mockup

Pros / Cons

Pros

• Allows the user to see where he is currently located in the wiki
  Cons

• Not scalable : displaying 4 columns is already a lot (screen width), displaying a space hierarchy would require an horizontal scrollbar.
• 3 or 4 steps are necessary to reach the current document.
• Only mac users are familiar with this kind of UI (finder).
• Doesn't allow to display parent/child relationships between pages.

3) Tree

Displaying the wiki as a tree, like the filesystem in windows explorer or like we (and confluence) already do to display a wiki hierarchy.

Mockup

Pros / Cons

Pros

• Scalable : we can have multiple wikis + spaces (even a space hierarchy)
• Allow to display parent/child relationships between pages (thus allowing to handle a lot of pages in a space)
• Allows the user to see where he is currently located in the wiki (default selection)
  Cons

• A lot of info displayed in the same dialog
• Adding a page + Uploading a file = 3 dialogs of very different sizes

4) Tree + Wizard (WINNER)

Mockup

Pros / Cons

Pros

• Easy to use: users are guided throughout the process, one action at a time.
• The dialog size is fixed, action buttons are always at the same position on screen
• The dialog doesn't looked oversized compared to the WYSIWYG
• Small footprint: can be used even on low resolution displays
• Since it's a wizard it's highly extensible
• Scalable : we can have multiple wikis + spaces (even a space hierarchy)
• Allow to display parent/child relationships between pages (thus allowing to handle a lot of pages in a space)
• Allows the user to see where he is currently located in the wiki (default selection)
  Cons

• 1 additional click compared to 3)

5) Tree + Wizard variant

Mockup

Pros / Cons

Pros

• Easy to use: users are guided throughout the process, one action at a time.
• The dialog size is fixed, action buttons are always at the same position on screen
• The dialog doesn't looked oversized compared to the WYSIWYG
• Small footprint: can be used even on low resolution displays
• Since it's a wizard it's highly extensible
• Scalable : we can have multiple wikis + spaces (even a space hierarchy)
• Allow to display parent/child relationships between pages (thus allowing to handle a lot of pages in a space)
• Allows the user to see where he is currently located in the wiki (default selection)

6) Tree options