Glaucus

'''This document is a work in progress. Comments are appreciated but this is not a final draft.'''


 * In Greek and Roman mythology, Glaucus (Glaukos, "glaring (eyes)"; compare Greek glaux, owl, of the same origin) is the symbolic owl of Athena or Minerva, respectively.

This document describes the design of a mobile-focused skin and interaction system intended to be deployed to the Wikipedia mobile gateway. It is intended to serve as the first step towards a greater rethinking of the interface, codenamed Athena.

Glaucus is not intended to solve several major interaction problems that exist within Wikipedia itself. Instead, it is intended provide a framework for further addition of features and links in a sane manner.

This document is a work in progress. Screen mockups are approximate at this time. Feedback is appreciated on the talk page.

Rationale
Currently, Wikipedia's mobile gateway is not designed to handle additional features well. New features are being developed all the time, and there is no obvious way to include them into the interface.

Goals

 * To organize various features of the mobile site in such a manner as to:
 * Be intuitively navigable
 * Allow for growth
 * Provide a modern visual refresh
 * Serve as an intermediate step within the greater vision for the mobile and desktop platform

Feature Categorization
Broadly, features for mobile have been categorized into the following areas:


 * Site Specific - functionality and navigation that is relative to Wikipedia as a whole
 * Article Specific - functionality relative to the article being viewed
 * User Account Related - functionality specific to the user in question
 * Contributary - functionality related to contributing to the project (such as image uploads or curation tools)
 * Search - functionality related to searching the encyclopedia

A special case is made for inter-wiki language links. This feature is of extreme importance to readers (70%+ of whom are multi-lingual). While these links are article-related, hiding them behind a menu is not desirable, as there is no easy way to explain to a reader that they can change their language if they do not understand the language the site is currently being presented in.

Top Bar
A primary component to the Glaucus interface is the "top bar". This area is designed to be an obvious series of menus that the user may interact with.

The buttons on the top bar align closely with the previous described feature categories, though their labels may not.

During early iterations of development, not all buttons will be included. For example, contributions are unlikely to appear with the first launch.

With one exception, tapping on any of the buttons will activate a category-specific menu that will overlay the screen ("Search" is the exception; see below for its behavior).

The five designed menu buttons are:


 * Wikipedia
 * Article
 * You / Log In
 * Contribute
 * Search

In the case of the "You/Log In" button, the button will be "Log In" if the user has not logged in and will change to the user menu if they have.

Behavior
Upon first load of the site, the top bar (and inter-wiki links) will be visible and remain visible, always. The top bar should be fixed positioned.

An alternative behavior is to have the top bar scroll off the screen as the user scrolls, but then appear immediately if the user taps the screen.

This interaction behavior should be tested.

Button Layout
The two primary buttons, Wikipedia and Search, are to be set flush left and right, respectively. Additional buttons are to be evenly spaced within the top bar.

Wikipedia

 * Main Page - links to the main page.
 * Featured Content - links to the featured content portal.
 * Recent Changes - links to the recent changes feed (disable?)
 * Random Article - links to Special:Random

Article

 * History - links to the article's history page.
 * Discussion - links to the article's discussion page.
 * What Links Here - links to "what links here" for the article.

NOTE: This menu perpetuates a poor interaction within Wikipedia, which is the conflation that there are not also histories to discussions and so forth. Solving the greater Wikipedia "tab/sub-tab" interaction is currently outside of the scope of this feature.

Personal

 * User Page Link - links to the user's user page.
 * Your Notifications - This feature is dependant upon the development of an notification system.
 * Your Talk Page - links to the user's talk page.
 * Your Watchlist - links to the user's watchlist.
 * Your Contributions - links to the user's contributions list.
 * Your Preferences - links to the user's preferences setting form.
 * Log Out - This option is given extra vertical spacing.

Contribute
The contents of this menu are currently to be determined.

Inter-wiki Language Links
The inter-wiki language links bar is docked to the top bar. It will have a different background color designed to better connect it to the article content.

If the top bar is fixed, then the inter-wiki links should undock from the top bar as the user scrolls (thus scrolling off the screen). If the top bar is not fixed, then the inter-wiki links should appear along with the top bar.

The entire link bar is "hot". Clicking anywhere on it will bring up the simple language picker.

The choice of which languages to show in the language bar is up for discussion. Regardless of the order, at least one language should utilize non-Roman glyphs.

Search Button Behavior
Clicking on the "Search" button will replace the entire screen with the new "full screen" search results functionality. The top bar will disappear as the search system overlays the entire screen.

Minimal Mobile Interface

 * This is a gallery of a minimal version of the mobile interface. Imagining a step between the existing UI and Glaucus.

Minimal header revisions

 * Indicating the search field and imagining an expanding menu.

Minimal contact/feedback page
This gallery includes yet another version of the simplified header.
 * 1) Any other buttons and boxes used in this interaction should match the header.
 * 2) The user device information should be automatically included with comments that are forwarded.
 * 3) Search box remains at the top but email and comment fields should not clear by clicking away.
 * 4) Oops, they need a clear button!
 * 5) Should the user be sent a copy of their own comment?