I started up a document on Confluence with the aim of gathering a Sakai
3 UX related guidelines, best practices and development information. The
aim of this document is to be a quick reference for anybody doing UX
development, provide a entry points for more in depth information if
needed, and serve as a reference for evaluating UX patches.
As you can see it is not complete, a lot of areas needs discussion, so
feel free to let me know what do you think:
Sakai 3 UX Development Guidelines and Information:
http://confluence.sakaiproject.org/display/3AK/Sakai+3+UX+Development+Guidelines+and+InformationMy personal opinion is:
1. Long text heavy guidelines never reach their aim as guidelines, so
I think in the future we should look at other media as well (5 min
screen casts?, well coded interactive examples in the upcoming pattern
library?).
2. This particular document should always contain the absolute minimum
set of guidelines and the most important best practices, with links to
more detailed things when needed. The more detailed pages should be live
and updated with things as we pick them up during the development process.
3. This document should be even shorter and more to the point
4. Rather than concentrating meticulously on particular technical
guidelines, the important thing should be a well-defined common
understanding and vision for the UX community around Sakai 3 which
automatically carry best practices and guidelines with themselves.
As the document has relevance to K2 developers as well, I am
cross-posting this to the Kernel list, welcoming
comments/recommendations from the back-end guys as well.
Oszkar
_______________________________________________
sakai-ux mailing list
sakai-ux@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-uxTO UNSUBSCRIBE: send email to
sakai-ux-unsubscribe@... with a subject of "unsubscribe"
