Design Team

From Sugar Labs
Revision as of 16:44, 14 May 2016 by Walter (talk | contribs)
Jump to navigation Jump to search

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Vision   ·   To Do   ·   Meetings

Status

These pages illustrate the design vision for Sugar. Many of the ideas have been incorporated into Sugar. Some are deprecated and some have yet to be realized. Browse these pages to get a general understanding of the rational behind the Sugar user experience, but be aware that there is not necessarily a direct correspondence to the current implementation.

The Features section of the wiki contains specific requests to incorporate new design features into Sugar releases.

Much of this content was developed during the collaboration between One Laptop per Child, Pentagram, and Red Hat in 2006/2007. Eben Eliason is responsible for many of these pages.

Mission

The mission of the Design Team was to make Sugar beautiful, elegant, and highly functional for our target users.


Human Interface Guidelines

The Sugar Human Interface Guidelines provide insight into the design of the Sugar experience, as well as guidelines for designing custom icons, controls, and activity interfaces.

Table of Contents
Introduction
Core Ideas
Design Fundamentals Know Your Audience Key Design Principles
The Laptop Experience Introduction Zoom Metaphor The Frame Bulletin Boards The Journal View Source Global Search
Activities Introduction Activity Basics Activity Bundles
Security
The Sugar Interface Input Systems Layout Guidelines Icons Colors Text and Fonts Toolbars Rollovers Controls Cursor

Specifications

The Design Team also maintains a list of specifications which provide additional details regarding the appearance and behavior of various software features. The specifications page is empty at present, but will be populated soon with preliminary specs for a number of features either currently implemented or planned for upcoming releases.

Designs

The Design Team manages a series of Design "slideshows" which illustrate various parts of the interface and how they function in a typical workflow.

Proposals

Subpages