Blocking out some major segments of user experience. 

Add a Page (unknown dev work ... options will need to be explored)

• Name the page
  
• Display the URL for the page being created (this will allow us to explain what happens to the URL if the page is renamed)
  
• Choose a Template
  
• Edit this new page now (opens a new tab in the browser thus not destroying the work they are in the middle of)
  
• If user choose to create a page and go back to what they were in the process of editing you have not put information into the new page there is a visual indicator like red with a + (our current experience)

• The page is also displayed in the sidebar as a new page added
  

• Thoughts on page hierarchy (seems to be a common user request.)
• Confluence has a children of pages relationship
• Wordpress has a subcategories and parent pages relationship
• PB wiki has a folder system
• View all pages (manage tool where the user can rename, delete, change security etc.)
• This will be determined by the permission the user has.
  

View a Page (for a single wiki page)

• Who's working on the page (easy)
  
• last 5 people who have been active on the page
  
• Display meta data like time, date contributions were made
  
• History (easy)
  
• View changes compare with an older version?
• Subscribe to notifications via the RSS of the history feed.
  

• Meta Data about the page (easy)
  
• Last updated (when and who)
• tags (do we want to tag other things? integrate with wordpress?)
  
• # of comments (currently comments are per revision, not per page
  
• Security (setting permissions on the page/set of pages) (depends on how we want to do this)
  
• Group level settings vs page level settings
  
• Page level settings (a la google pages)
  

Editing a Page (all these will require some exploration to determine how feasible they are)

• Formatting text and the Xinah experience
• Simplifying some of the Xinah tools
  
• Consolidating formatting tools vs. action items like linking and adding pages, images etc.
  
• Increasing the capacity for formatting with color, rules, drop letter columns etc.
  

• Inserting a Page
• User highlights a word and decides to make it a page
  
• User places cursor and hits "Creates a New Page" on entering information the new page link is placed in the edit window.
• User selects a word to link to an existing page
  
• Adding Images
• Redefining the Image upload workflow
• Linking (URL, email, Page or Image)
• Single space that allows the user to create a link to a page, to a URL, to an Image and to an Email
  
• Adding Media (files - pdf, doc; then others -- videos, music, etc)
• Do these sit in the same repository as the Project Files?
  
• Do we display only page specific or wiki-wide images, files and pages?
  

• Save
• Javascript notification when user navigates back, closes browser or quits browser.
  
• Save and continue
• Auto Save
  
• Broadcast notifications on save
• Email
  
• RSS
  
• Automatic?
  
• Choice in settings (a la google)
  
• Tagging - assigning and managing
• Categories
• Folders
  
• Page Hierarchy (a la Confluence)
  
• Lock Page when in Edit mode