user-interface

(Difference between revisions)

Jump to: navigation, search
m (Fixed link to John Hicks' image.)
(added netnewswire screenshot)
Line 72: Line 72:
* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock] <br /> [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ http://blog.wilsonet.com/mockups/Flock/Flock-PickContacts_thumbnail.png]
* [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ Microformats in Flock] <br /> [http://blog.wilsonet.com/archives/2006/04/30/microformats-in-flock/ http://blog.wilsonet.com/mockups/Flock/Flock-PickContacts_thumbnail.png]
* [http://glazkov.com/blog/margin-marks/ Margin Marks UI Concept], [http://flickr.com/photos/dglazkov/sets/72157601860335196/ Margin Marks Comps on Flickr]
* [http://glazkov.com/blog/margin-marks/ Margin Marks UI Concept], [http://flickr.com/photos/dglazkov/sets/72157601860335196/ Margin Marks Comps on Flickr]
-
 
+
* NetNewsWire [http://flickr.com/photos/factoryjoe/454706107/in/photostream/ detects] and then [http://flickr.com/photos/factoryjoe/454705203/ converts hcard and hcalendar data] in feed entries:<br />[http://flickr.com/photos/factoryjoe/454705203/ http://farm1.static.flickr.com/183/454705203_33f9b8d7c6_o.png]
== Implementations ==
== Implementations ==
See [[implementations]], and document examples of good UI from there, here.
See [[implementations]], and document examples of good UI from there, here.

Revision as of 04:19, 8 October 2007

User Interface

Recently there have been many really good user interface ideas and suggestions for working with microformats. This page serves to collect and document them so that we may be inspired by and iterate on each others' works.

Contents


Design Guidelines

These are some suggested design guidelines for Web designers and developers by Alex Faaborg, a user experience designer at Mozilla:

Challenges

Social Network Portability

See the separate social-network-portability page.

Browser Integration

From screenshot brainstorms to working plugins, there is a lot going on with browser integration of microformats support.

In General

Browser support for microformats consists of three things in general:

  1. Automatically detect the presence of microformats on a page
  2. Parse them into a set of microformats for that page (preferably maintaining their relative relationships perhaps within a tree structure).
  3. Do something useful with them

Do something useful

Do something useful could be any or all of:

Additional user interface

Some examples of additional user interface for common actions to take with microformats found in pages, grouped by specific microformat. Note that most of these actions should be applicable to all instances of the microformat on the page at once (e.g. export all contacts), of for a selection of instances (e.g. export selected contacts), or one just one specific instance (e.g. export contact XYZ).

Screen Shots

Implementations

See implementations, and document examples of good UI from there, here.

Plugins

Greasemonkey user scripts

Browser buttons

CSS user stylesheets

Planning and Discussion

Simpler Markup Languages

There are plenty of wiki-formats that attempt to make it easier for more people author semantic markup, often with textually decorative punctuation.

As these simpler markup languages are something that *users* are expected to type, they are user interface.

Markdown extension for hCalendar

See Markdown and the hCal microformat which proposes an extension to the Markdown text markup language to capture and represent hCalendar event semantics in a human editable form.

See Also

user-interface was last modified: Wednesday, December 31st, 1969

Views