Notifications/User Experience

Key Components of the Notifications Experience are: Notifications Growler & Notifications Flyout Notifications Archive Notification Settings Email Experience Real time Confirmations/ Notifications [edit]Notifications Growler and Flyout A new user interface link, "Notifications," will appear in the user's chrome. If the user has "unread" notifications, the number of unread notifications will appear next to the link as a badge upon a red background. This badge will auto-update (see below). Clicking on the "Notifications" link or the badge will display the Notifications Bar (clicking on it again, or anywhere outside of the Notifications Bar, will close the bar, possibly marking all Notifications as read). The Flyout will carry groups of Notifications. Groups are categories of notifications arranged in a specific priority based on a users mental model. The content within each group will be ordered in reverse chronology. A group at the top may contain Notifications that are older than those contained in groups beneath it. [edit]Archive An Archive of notifications where a user might be able to go to a dedicated page and see a history of notifications will be available. The feed/ groups here will be time capped with the ability to see previous notifications. Buckets are sorted in reverse chronological order with the most recent timestamp held within the bucket. [edit]Notification Settings Settings around Notifications can be customised to a large extent. Although Echo attempts to carry smart defaults, an editor may decide what type of notifications they want to switch off. [edit]Email Experience [edit]Real Time Notifications This is a list of real time Notifications Real Time System Messages Edit Notices Error Messages Descriptor Messages Protection Notices Talk Page Edit Notices Site Notices Central Notices [edit]Read vs Unread Note: It is important to note that all notifications exist in a state of "read" or "not read". The process by which a notification is marked as "read" is something that we will want to experiment with. There are several ways of handling Notifications as Read": They have been "seen" (e.g., when the user views their notifications) They have been "acted upon" (e.g., the user visits their talk page after being notified it was edited) They are manually marked read The mockup provided assumes that notifications are marked read upon being seen. [edit]Elements and Process A new user interface link, "Notifications," will appear in the user's chrome. If the user has "unread" notifications, the number of unread notifications will appear next to the link as a badge upon a red background. This badge will auto-update (see below). Clicking on the "Notifications" link or the badge will display the Notifications Bar (clicking on it again, or anywhere outside of the Notifications Bar, will close the bar, possibly marking all Notifications as read). Notifications are "bucketed" by the wiki they have come from. Individual wiki buckets will contain all unread notifications from that wiki, regardless of timestamp. Buckets are sorted top-to-bottom based on the most recent timestamp held within the bucket. Thus, it is possible for a bucket at the top of the bar to contain Notifications that are older than those contained in buckets beneath it provided that there are Notifications that are newer than the most recent Notification in lower buckets. Buckets will have a header that indicates which wiki they are coming from (both its "official" name and the "URL"). Headers are not hot. Inside each bucket, Events are displayed. Events may be atomic or bundled, depending on the preference of the Publisher. Events contain timestamps printed in context-relative format (e.g., "10 minutes ago, "3 hours ago"), with the most recent listed first. Event text should really be capped at 250 characters. Events should have distinguishable icons. (Should the process of Event-to-Icon association should happen at the Central Service layer or at the Publisher layer? Or skin?) Clicking on any one Event's entry will cause that Event to be "actioned" - usually going to view the item in question. The entire section of the Event is "hot". While some things (such as user names) may appear to be hot links, they are not - the entire element is and is focused on a single URL. At the bottom of the Notifications Bar will be an additional link, "View all notifications". Clicking this will bring the user to a Special page which lists all notifications, read and unread. [edit]Echo Replaces The "yellow bar" notifications about talk page edits, LiquidThreads "New Messages" link and special page, others as determined.