Difference between revisions of "Design Team"

 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}</noinclude>{{TOCright}}
 
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}</noinclude>{{TOCright}}
 +
 +
== Outdated ==
 +
 +
When Sugar Labs was very large, we found it convenient and effective to divide into teams. This was one of the teams.
  
 
== Status ==
 
== 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.
+
Design includes user experience, appearance, graphic design, architecture, and code design.
 +
 
 +
These pages illustrated the design vision for Sugar. Many of the ideas had been incorporated into Sugar. Some were 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.
 
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 was the primary author of many of these pages, but is no longer involved.
+
Much of this content was developed during the collaboration between the One Laptop per Child Sugar Team, Pentagram, and Red Hat in 2006/2007. Eben Eliason was the primary author of many of these pages, but is no longer actively involved in the project.
  
 
== [[/Mission|Mission]] ==
 
== [[/Mission|Mission]] ==

Latest revision as of 19:15, 27 November 2019

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

Outdated

When Sugar Labs was very large, we found it convenient and effective to divide into teams. This was one of the teams.

Status

Design includes user experience, appearance, graphic design, architecture, and code design.

These pages illustrated the design vision for Sugar. Many of the ideas had been incorporated into Sugar. Some were 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 the One Laptop per Child Sugar Team, Pentagram, and Red Hat in 2006/2007. Eben Eliason was the primary author of many of these pages, but is no longer actively involved in the project.

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.

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