10,579
edits
Changes
Jump to navigation
Jump to search
Line 31:
Line 31: + + + + + + + + + + + + + + + +
Deployment Team/Small deployment guide (view source)
Revision as of 06:07, 27 September 2008
, 06:07, 27 September 2008→Why Sugar?
===Why Sugar?===
===Why Sugar?===
* Sugar comes with hundreds of tools for discovery through exploring, expressing, and sharing:
** web browsing; reading; chatting; playing movies and music; playing games; word processing; reflecting and assessment (Journal); creating graphics; creating rich media; and programming.
* Sugar comes with a built-in collaboration system:
** It features collaboration with or without Internet access.
** Benefits of Sugar include peer-to-peer learning; always-on support; and single-click sharing <nowiki>[Should we trademark these terms? :)]</nowiki>
* Sugar comes with built-in tools for reflection:
** Features include an auto-generated journal (all your work is auto-saved and can be annotated and tagged).
** Benefits of the Sugar Journal are that it serves as a portfolio assessment tool, a place of reflection, and a forum for discussion between children, their parents, and their teachers.
* The Sugar learning platform is discoverable:
** It features a scalable interaction model that is iconic and discoverable through hover menus:
** Benefits include that you don't need to learn everything at once—you can progress, using simple means to reach to complex ends: no upper bound on where you can reach.
* Sugar is designed for local appropriation:
** It features free and open-source software, a view-source mechanism, and built-in tools for making changes and improvements.
** Benefits include a growing global community of support;
* Sugar puts an emphasis on learning through doing and debugging.
** Benefits include a more engaged learner able to tackle authentic problems.
[[Category:Deployment]]
[[Category:Deployment]]