![Introduction Nicolaas Matthijs ( [email_address] ) CARET, University of Cambridge Front-end developer You ?](https://image.slidesharecdn.com/sakaiboston-090722090541-phpapp01/85/Sakai-3-R-D-2-320.jpg)
Sakai 3 R&D
- 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
- 9. Architecture EB + SData Static files Sakai 2.5
- 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
- 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. ?
Editor's Notes
- #3: Who is a manager ? Who is a developer ? Who is a designer (UX/UI) ? Who is support ? Who is faculty ?