...
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 |
Some areas of contribution to consider: Project Management, Needs Assessment/Ideas, Accessibility, Standards, Editorial Board, Writing, Programming/Development, Workflows, Localization (Internationalization/Translation), Screenshots/Videos.
...
1. How do we define "end-user documentation" - purpose, audience, and content?
- 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
- 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
2. What do users need to accomplish their tasks in Sakai?
...