sakai 3 r&d
DESCRIPTION
Sakai 3 R&DTRANSCRIPT
Sakai 3Sakai 3The Road To A Next Generation SakaiThe Road To A Next Generation Sakai
Introduction
Nicolaas Matthijs([email protected])CARET, University of CambridgeFront-end developer
You ?
The plan
MyCamTools
UX Improvement Project
Sakai 3 R&D
Demo
Questions
MyCamToolsMyCamToolsUniversity of Cambridge
December 2007 - July 2008University of Cambridge
December 2007 - July 2008
Goals
Make (local) Sakai more user friendly
Changing expectation (web 2.0)+ Make technologically more up-to-date
Lower development bar
Speed up development process
Separation between front and back-end=> Well-balanced team
Rise of Client Side
User Centered
Rapid cycles
More balanced team
Experimental Team
Architecture
EB + SDataStatic files
Sakai 2.5
http://camtools.cam.ac.uk
http://camtools-labs.caret.cam.ac.uk
http://camtools.cam.ac.uk
http://camtools-labs.caret.cam.ac.uk
http://camtools.cam.ac.uk
http://camtools-labs.caret.cam.ac.uk
Result
Production since July 2008
Very positive reactions
Stable
Ready for you to use
Ideas for Sakai 3
Sakai Everywhere
Documented datafeeds allow Sakai to
appear anywhere
UX Improvement InitiativeUX Improvement InitiativeSakai Community
August 2008 - January 2009Sakai Community
August 2008 - January 2009
UX Improvement
Screens designed by Nathan Pearson
Aimed at improving Sakai 2
Same development techniques
Not complete enough for 2.6/2.7 => playground forsome of Sakai 3 concepts
Made a lot work on 2.x
Ideas for Sakai 3
Content Authoring
Content basics
Simple page creation(wiki-like)WYSIWYG editingTemplate-based authoringVersioning
Interactive widgets
UX Improvement
Development has stopped now
Code is not production ready
People are free to take code and turn it into production ready code
Can be nice migration path to Sakai 3
Tools can be inserted in authored pages as widgets
Architecture
EB + SDataStatic files
Sakai 2.5
Sakai 3 R&DSakai 3 R&DSakai Community
January 2009 - September 2009Sakai Community
January 2009 - September 2009
Sakai 3 R&D
New set of wireframes from Nathan Pearson
Make conceptually more sense
Continue building on some of the Sakai 3 concepts
New back-end = K2
Wireframes
Ideas for Sakai 3
WireframesUser-Centered
WireframesContent Authoring
WireframesBasic Social Networking
Visual Design ProjectVisual Design ProjectSam Peck / Flow Interactive
June 2009Sam Peck / Flow Interactive
June 2009
Visual Design
Hired consultancy
Flow Interactive / Sam Peck
Visual design => wireframes
Out of the box experience
Easily institutionalized
Visual Design OutputVisual style applied to 4 key screens
Visual Design OutputExample of easy customization
Visual Design Output
Master Files
Components
Specifications + interactions
Tool when developing new screens
Basis for style guide
Master Files
Master Files
Progress
Fluid === a11y
FSS
Reorderer
Keyboard a11y plugin
Inline Edit
(Uploader)
K2
Functionality exposed is UI driven
Clean front and back end separation
Standards based / 3rd party code
Scalability
Developer productivity
Code quality and maintenance
Easier to install/build
Architecture
Static files
Kernel 2 (Sling+)
Kernel 2 (Sling+)
Timeline
Q3 2009: First hybrid production
Several projects (groups, assessment workflows, ...)
July 2010: Full stand-alone production
ParticipationK2 working group
http://groups.google.com/group/sakai-kernel
UX working group
UX Listhttp://confluence.sakaiproject.org/display/3AK/3akai
How would you like to be involved
Code (Java - Javascript)DesignDocumentationWrite style guide
?