...
12. What is the current status of Sakai documentation?
- For Study of Samigo, at Stanford:-- Current Status of Tests & Quizzes
- For developers and deployers:
- Many of the current resources labeled "Documentation":
sakaiproject.org/documentation
Confluence "Project: Documentation"
- Many of the current resources labeled "Documentation":
- For the Portfolio tools, a case study: Why is it so hard to document the portfolio tools? (R. Hill, relying on S. Keesler)
- Because we're too lazy to learn the skills clearly designated as necessary; we want documentation to reveal the effort-free path.
- Because the Help files are written to an audience, trained faculty, that enjoys an environment of expert support.
- Because Sean's comprehensive documents on Confluence are found in different branches of the hierarchy.
- Because some Confluence pages have lost their context and suffer from neglect, e.g., http://confluence.sakaiproject.org/display/OSPDOC/Data+warehouse
- Because there is no visible intermediate result that affords the author a self-check of progress.
- Because there are assumed procedures and scenarios that hide restrictions.
- Because portfolios, insofar as they capture the essence of learning, are inherently complex objects.