Human Interface Guidelines (update and hosting)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Human Interface Guidelines (update and hosting)

Eben Eliason
Hello everyone -

The Human Interface Guidelines [1] have been stagnant for some time,
and I'm starting an initiative to remedy the situation.  This effort,
as I see it, has two components: 1) update the contents of the HIG and
2) tease apart OLPC guidelines from Sugar guidelines, and adjust
hosting accordingly.

UPDATE: The content update is something I'll spearhead myself, as I
wrote most of the current guidelines.  Assistance is certainly
welcome, however, /especially/ in amassing lists of holes that need to
be plugged; I'm sure there are countless implicit guidelines we all
follow that should really be laid down clearly and explicitly.
Ideally, we should be able to answer any noob question about visual or
interaction design by pointing to a sentence in the HIG.  In that
regard, there is a component for the HIG in the OLPC trac system, so
tickets are welcome.  As I mentioned, a small bit of the HIG (mostly
the "input methods" section, but perhaps others) are XO specific.
I'll attempt to tease this apart as well.

HOSTING: The second aspect of this effort is transitioning the HIG to
the sugarlabs wiki, which seems a more appropriate place for the
(Sugar) Human Interface Guidelines.  I foresee this as a relatively
large task, given the size of the HIG and the set of templates, raw
HTML, and nested transclusion which makes a quite navigable but
relatively complex page structure.  I'm not a wiki pro, myself, and
I'd be quite grateful to any who have the know-how and are willing to
assist with, or even take on, this task.

PARALLELISM: Finally, there's a third implied complication, which is
how these two efforts can happen simultaneously (or not).  Should we
a) transition the HIG to sugarlabs, and then update/edit and move any
XO specific pieces back to the OLPC wiki or b) perform a complete
update in place, teasing XO specific parts into separate pages, and
then move it to sugarlabs when we're done or c) come up with a way to
work in parallel?

Thanks for your assistance!

[1] wiki.laptop.org/go/HIG
_______________________________________________
Sugar mailing list
[hidden email]
http://lists.laptop.org/listinfo/sugar
Reply | Threaded
Open this post in threaded view
|

Re: Human Interface Guidelines (update and hosting)

David Farning-5
On Wed, Dec 17, 2008 at 3:13 PM, Eben Eliason <[hidden email]> wrote:

> Hello everyone -
>
> The Human Interface Guidelines [1] have been stagnant for some time,
> and I'm starting an initiative to remedy the situation.  This effort,
> as I see it, has two components: 1) update the contents of the HIG and
> 2) tease apart OLPC guidelines from Sugar guidelines, and adjust
> hosting accordingly.
>
> UPDATE: The content update is something I'll spearhead myself, as I
> wrote most of the current guidelines.  Assistance is certainly
> welcome, however, /especially/ in amassing lists of holes that need to
> be plugged; I'm sure there are countless implicit guidelines we all
> follow that should really be laid down clearly and explicitly.
> Ideally, we should be able to answer any noob question about visual or
> interaction design by pointing to a sentence in the HIG.  In that
> regard, there is a component for the HIG in the OLPC trac system, so
> tickets are welcome.  As I mentioned, a small bit of the HIG (mostly
> the "input methods" section, but perhaps others) are XO specific.
> I'll attempt to tease this apart as well.
>
> HOSTING: The second aspect of this effort is transitioning the HIG to
> the sugarlabs wiki, which seems a more appropriate place for the
> (Sugar) Human Interface Guidelines.  I foresee this as a relatively
> large task, given the size of the HIG and the set of templates, raw
> HTML, and nested transclusion which makes a quite navigable but
> relatively complex page structure.  I'm not a wiki pro, myself, and
> I'd be quite grateful to any who have the know-how and are willing to
> assist with, or even take on, this task.

Please let me know if you need help on this.  I am just now posting my
notes on the pywikipedia bot at
http://sugarlabs.org/go/WikiTeam/Resources/Bots .  Hopefully, this
will reduce the learning curve a bit!

> PARALLELISM: Finally, there's a third implied complication, which is
> how these two efforts can happen simultaneously (or not).  Should we
> a) transition the HIG to sugarlabs, and then update/edit and move any
> XO specific pieces back to the OLPC wiki or b) perform a complete
> update in place, teasing XO specific parts into separate pages, and
> then move it to sugarlabs when we're done or c) come up with a way to
> work in parallel?
>
> Thanks for your assistance!
>
david
_______________________________________________
Sugar mailing list
[hidden email]
http://lists.laptop.org/listinfo/sugar
Reply | Threaded
Open this post in threaded view
|

Re: Human Interface Guidelines (update and hosting)

Edward Cherlin
In reply to this post by Eben Eliason
On Tue, Dec 16, 2008 at 1:13 PM, Eben Eliason <[hidden email]> wrote:
> Hello everyone -
>
> The Human Interface Guidelines [1] have been stagnant for some time,
> and I'm starting an initiative to remedy the situation.  This effort,
> as I see it, has two components: 1) update the contents of the HIG and
> 2) tease apart OLPC guidelines from Sugar guidelines, and adjust
> hosting accordingly.

Thanks. I have just been in a discussion of Help facilities (Yay!),
and of doubly-delayed popups (Boo!). The question is how to make as
much as possible easily discoverable, and what to do about anything
left over.

Earth Treasury is getting a textbook rethinking, redesign, and
implementation consortium together.

http://wiki.sugarlabs.org/go/User:Mokurai/Creating_textbooks

At some point we want to write a new XO+Sugar manual that encourages
as much discovery as possible, but covers every known non-discoverable
feature in some way. But we won't stop at features. We will move on to
the non-discoverable parts of teaching discovery, collaboration, and
other Really Big Ideas.

> UPDATE: The content update is something I'll spearhead myself, as I
> wrote most of the current guidelines.  Assistance is certainly
> welcome, however, /especially/ in amassing lists of holes that need to
> be plugged; I'm sure there are countless implicit guidelines we all
> follow that should really be laid down clearly and explicitly.
> Ideally, we should be able to answer any noob question about visual or
> interaction design by pointing to a sentence in the HIG.  In that
> regard, there is a component for the HIG in the OLPC trac system, so
> tickets are welcome.  As I mentioned, a small bit of the HIG (mostly
> the "input methods" section, but perhaps others) are XO specific.
> I'll attempt to tease this apart as well.

I'll invite in some other people who know something about the matter.
I assume that we need to comb through the Sugar framework and existing
Activities to find any exceptions to documented practices, and discuss
whether to document or change them.


> Thanks for your assistance!
>
> [1] wiki.laptop.org/go/HIG


--
Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name
And Children are my nation.
The Cosmos is my dwelling place, The Truth my destination.
http://wiki.sugarlabs.org/go/User:Mokurai
_______________________________________________
Sugar mailing list
[hidden email]
http://lists.laptop.org/listinfo/sugar