End-User Documentation Meetings

All agendas and minutes will be listed here as child pages in the future.

This effort was organized on the Help Files and Documentation Process Redesign page.

Tentative Agenda

1. Introductions/Expectations/Skills/Availability of participants

2. Define goals

• Scope (redistributable KB or wiki, prioritized list of docs needed)
• Exploration of different levels of documentation for different audiences

3. Timeframe

4. Success stories, other products available?

• Study of Samigo, at Stanford:  Current Status of Tests & Quizzes Documentation (R. Hill) 
• Why is it so hard to document the portfolio tools?  (R. Hill, relying on S. Keesler)

1. Because we're too lazy to learn the skills clearly designated as necessary; we're looking for the magical effort-free path.
2. Because the Help files are written to an audience (faculty at Indiana) that understands the entire context.
3. Because Sean's documents on Confluence are scattered across several branches of the hierarchy.
4. Because there is no visible intermediate result that affords the author a self-check of progress.
5. Because there are assumed procedures and scenarios that hide restrictions.
6. Because portfolios, insofar as they capture the essence of learning, are inherently complex objects.

5. Define structure of this group