Sakai 3 R&D
Upcoming SlideShare
Loading in...5
×
 

Sakai 3 R&D

on

  • 1,269 views

Sakai 3 R&D

Sakai 3 R&D

Statistics

Views

Total Views
1,269
Views on SlideShare
1,264
Embed Views
5

Actions

Likes
0
Downloads
17
Comments
0

1 Embed 5

http://www.slideshare.net 5

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Who is a manager ? Who is a developer ? Who is a designer (UX/UI) ? Who is support ? Who is faculty ?

Sakai 3 R&D Sakai 3 R&D Presentation Transcript

  • Sakai 3
    • The Road To A Next Generation Sakai
  • Introduction
    • Nicolaas Matthijs ( [email_address] ) CARET, University of Cambridge Front-end developer
    • You ?
  • The plan
    • MyCamTools
    • UX Improvement Project
    • Sakai 3 R&D
    • Demo
    • Questions
  • MyCamTools
    • University 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 + SData Static 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 data feeds allow Sakai to appear anywhere
  • UX Improvement Initiative
    • Sakai 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 for some 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 editing
      • Template-based authoring
      • Versioning
    • 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 + SData Static files Sakai 2.5
  • UX Improvement + http://131.111.21.17:9090/dev/
  • Sakai 3 R&D
    • Sakai 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
  • Wireframes User-Centered
  • Wireframes Content Authoring
  • Wireframes Basic Social Networking
  • Visual Design Project
    • Sam 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 Output
    • Visual style applied to 4 key screens
  • Visual Design Output
    • Example of easy customization
  • Visual Design Output
    • Master Files
    • Components
    • Specifications + interactions
    • Tool when developing new screens
    • Basis for style guide
  • Master Files
  • Master Files
  • Sakai 3 R&D Demo http://3akai.sakaiproject.org/dev
  • 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
  • Participation
    • K2 working group
      • http://groups.google.com/group/sakai-kernel
    • UX working group
      • UX List
      • http://confluence.sakaiproject.org/display/3AK/3akai
    • How would you like to be involved
      • Code (Java - Javascript)
      • Design
      • Documentation
      • Write style guide
  • ?