Difference between revisions of "Design Team"

From Sugar Labs
Jump to navigation Jump to search
 
(36 intermediate revisions by 11 users not shown)
Line 1: Line 1:
−
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}
+
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}</noinclude>{{TOCright}}
−
{{TeamHeader|DesignTeam}}</noinclude>
 
  
−
== Meetings ==
+
== Outdated ==
−
The design team holds a regular biweekly IRC meeting. Find out more about the meeting time, as well as upcoming and prior meetings [[DesignTeam/Meetings|here]].
 
  
−
[[Category:DesignTeam]]
+
When Sugar Labs was very large, we found it convenient and effective to divide into teams. This was one of the teams.
  
−
== Designs ==
+
== Status ==
−
At present, the latest designs for upcoming revisions of Sugar can be found [http://wiki.laptop.org/go/Designs here].
+
 
 +
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|Mission]] ==
 +
{{:Design Team/Mission}}
 +
 
 +
==[[Human Interface Guidelines]]==
 +
The [[Human_Interface_Guidelines | 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.
 +
{{Template:Hig-header}}
 +
== [[/Specifications|Specifications]] ==
 +
The Design Team also maintains a list of [[Design Team/Specifications | 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.
 +
{{Special:PrefixIndex/Design Team/Specifications}}
 +
== [[/Designs | Designs]] ==
 +
The Design Team manages a series of [[Design Team/Designs | Design "slideshows"]] which illustrate various parts of the interface and how they function in a typical workflow.
 +
{{Special:PrefixIndex/Design Team/Designs}}
 +
==[[/Proposals | Proposals]]==
 +
{{Special:PrefixIndex/Design Team/Proposals}}
 +
 
 +
==Subpages==
 +
 
 +
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 +
 
 +
[[Category:Design Team]]
 +
[[Category:Design]]
 +
[[Category:Team]]

Latest revision as of 18: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.

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

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Design_Team&oldid=103442"