Uploaded on

Sakai 3 R&D

Sakai 3 R&D

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
637
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
18
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Who is a manager ? Who is a developer ? Who is a designer (UX/UI) ? Who is support ? Who is faculty ?

Transcript

  • 1. Sakai 3
    • The Road To A Next Generation Sakai
  • 2. Introduction
    • Nicolaas Matthijs ( [email_address] ) CARET, University of Cambridge Front-end developer
    • You ?
  • 3. The plan
    • MyCamTools
    • UX Improvement Project
    • Sakai 3 R&D
    • Demo
    • Questions
  • 4. MyCamTools
    • University of Cambridge
    • December 2007 - July 2008
  • 5. 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
  • 6. Rise of Client Side
    • User Centered
    • Rapid cycles
  • 7. More balanced team
  • 8. Experimental Team
  • 9. Architecture EB + SData Static files Sakai 2.5
  • 10. http://camtools.cam.ac.uk http://camtools-labs.caret.cam.ac.uk
  • 11. http://camtools.cam.ac.uk http://camtools-labs.caret.cam.ac.uk
  • 12. http://camtools.cam.ac.uk http://camtools-labs.caret.cam.ac.uk
  • 13. Result
    • Production since July 2008
    • Very positive reactions
    • Stable
    • Ready for you to use
  • 14. Ideas for Sakai 3
  • 15. Sakai Everywhere Documented data feeds allow Sakai to appear anywhere
  • 16. UX Improvement Initiative
    • Sakai Community
    • August 2008 - January 2009
  • 17. 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
  • 18. Ideas for Sakai 3
  • 19. Content Authoring
    • Content basics
      • Simple page creation (wiki-like)
      • WYSIWYG editing
      • Template-based authoring
      • Versioning
    • Interactive widgets
  • 20. 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
  • 21. Architecture EB + SData Static files Sakai 2.5
  • 22. UX Improvement + http://131.111.21.17:9090/dev/
  • 23. Sakai 3 R&D
    • Sakai Community
    • January 2009 - September 2009
  • 24. 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
  • 25. Wireframes
  • 26. Ideas for Sakai 3
  • 27. Wireframes User-Centered
  • 28. Wireframes Content Authoring
  • 29. Wireframes Basic Social Networking
  • 30. Visual Design Project
    • Sam Peck / Flow Interactive
    • June 2009
  • 31. Visual Design
    • Hired consultancy
    • Flow Interactive / Sam Peck
    • Visual design => wireframes
    • Out of the box experience
    • Easily institutionalized
  • 32. Visual Design Output
    • Visual style applied to 4 key screens
  • 33. Visual Design Output
    • Example of easy customization
  • 34. Visual Design Output
    • Master Files
    • Components
    • Specifications + interactions
    • Tool when developing new screens
    • Basis for style guide
  • 35. Master Files
  • 36. Master Files
  • 37. Sakai 3 R&D Demo http://3akai.sakaiproject.org/dev
  • 38. Progress
  • 39. Fluid === a11y
    • FSS
    • Reorderer
    • Keyboard a11y plugin
    • Inline Edit
    • (Uploader)
  • 40. 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
  • 41. Architecture Static files Kernel 2 (Sling+) Kernel 2 (Sling+)
  • 42. Timeline
      • Q3 2009: First hybrid production
      • Several projects (groups, assessment workflows, ...)
      • July 2010: Full stand-alone production
  • 43. 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
  • 44. ?