...
Name | Institution | Expected contribution | ||||
---|---|---|---|---|---|---|
Mathieu Plourde | mathieu@udel.edu | University of Delaware | Ideas, workflows, leadership (Needs Assessment/Ideas, Standards, Editorial Board, Writing, Project Management) | |||
Alan Regan | alan dot regan at pepperdine dot edu | Pepperdine University | Ideas, workflows, content (Needs Assessment/Ideas, Standards, Editorial Board, Writing) | |||
Lorie Stolarchuk | lorie@uwindsor.ca | University of Windsor | Pain points of current situation, integration joys/woes of Brock's MediaWiki, ideas (time permitting ) | |||
Robin Hill | hill@uwyo.edu | University of Wyoming | Content, editing... whatever I checked on Alan Regan's form (Standards, Editorial Board, Writing) | |||
Sean Keesler | sean.keesler@threecanoes.com | Three Canoes | Project Management, Writing, Workflows, Editing | |||
Matt Clare | Matt.Clare@BrockU.ca | Brock University | We're more than happy to share our documentation at http://kumu.brocku.ca/sakai A lot of MediaWiki experience. Big advocate of ease-of-edit and radical trust. | |||
Greg Doyle |
| University of Cape Town | Writing | |||
Margaret Wagner | mwagner@umich.edu | University of Michigan | Ideas, Writing | |||
Trisha Gordon | psg3a@virginia.edu | University of Virginia | Content, editing, ideas | |||
Kara Stiles | kstiles@rsmart.com | rSmart | Content, Writing | |||
|
|
| Rafael Morales | rmorales@udgvirtual.udgd.mx | University of Guadalajara | Localization |
|
|
|
| |||
|
|
|
|
Some areas of contribution to consider: Project Management, Needs Assessment/Ideas, Accessibility, Standards, Editorial Board, Writing, Programming/Development, Workflows, Localization (Internationalization/Translation), Screenshots/Videos.
...
Before we start defining our process, please share your thoughts the following questions:
1. How do we define "end-user documentation" - purpose, audience, and content? And media?
- Purpose
- to document the OOTB experience
- to document configuration options that change the OOTB experience
- to demonstrate how to accomplish common tasks
- Audience
- Faculty should be a primary audience
- Instructional designers
- Could we consider faculty as end-users and students as end-end-users?
- Faculty design choices influence student user experience
- Content
- Beginner and Advanced levels would allow a faculty member to get a quick start with the basics and then later explore the more complex features
- Conceptual Introduction - brief description of the purpose of the tool
- Task oriented instructions
- Brief (3 min?) screencast
- Annotated screenshots
...
10. How should we address the branding and localization issues (different names, logos, style sheets, languages)?
- What is the difference between localization and branding?
11. "Wish list" thoughts?
...