...
Collaborative review and verification-- inconveniently tedious and time-consuming, and dependent on careful coordination-- with the same level of respect and attention accorded to QA of code.
10. How should we address the branding, customization, and localization issues (different names, logos, style sheets, languages, policies)?
- 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.
- Customization: Each institution goes into the help files and purges tools that are not used, or takes out references to a certain role, etc. It would be nice if those customizations could be easily visible to all, so that they could be integrated in your local help files.
11. "Wish list" thoughts?
...