...
- FAQ: What users are asking after having used the system
- Tasks: Based on workflows, not on tools (Setting up a course site vs. using Site Info, for instance)
- Help files tend to be in text, other documentation might be in document, audio, video, picture format.
8. How can we encourage the Sakai community to contribute their improvement back to the OOTB help files?
- Provide an easily editable platform for central documentation
- Provide guidance on what should be contributed back, and how
- Provide ways to point to localized documentation to supplement the core help files
- Have a vetting process in place to accept/reject contributed changes
- Make the help files easily "subscribable", customizable, exportable in multiple formats for quick local updates
...
- What is the difference between localization and branding?
- Good question
- I offer the suggestion that "branding" refers to the name and/or logo that an institution may give their instance of Sakai. Michigan calls their instance "CTOOLS," Indiana "Oncourse," VirginiaTech "Scholar," etc.
- Localization would refer to providing the same helpful information in multiple languages or regions, e.g. Spanish, English (UK), English (US), French, German, Chinese, Japanese, etc.
- Good question
- For "branding," can we provide definable fields. One definable field might be "brand name" that would default to "Sakai" out of the box (OOTB) but allow an institution to replace with their local instance's name. The text of the help files would either dynamically (or periodically) lookup and insert the local brand name into the help files. Similarly, a definable image source could be provided for a brand logo and placed into the help files. And definable formatting colors could also be available, which would insert the colors into the appropriate CSS and/or HTML source.
11. "Wish list" thoughts?
...