Difference between revisions of "Vision for OneVille documentation"

(Created page with 'Vision for the wiki documentation: documentation should be coherent -- glued to our core research questions, throughout. documentation should be visually inviting. Think of en…')
 
Line 1: Line 1:
 
Vision for the wiki documentation:
 
Vision for the wiki documentation:
  
documentation should be coherent -- glued to our core research questions, throughout.
+
Documentation should be coherent -- glued to our core research questions, throughout.
  
  
documentation should be visually inviting. Think of enticing a teacher or young person or parent to tackle (or document!) similar issues where they live.
+
Documentation should be visually inviting. Think of enticing a teacher or young person or parent to tackle (or document!) similar issues where they live.
  
 
 
documentation should in the end be downloadable, and distributable by people; something they can email around their school.
 
  
 +
Documentation should in the end be downloadable, and distributable by people; something they can email around their school.
 
   
 
   
  
the documentation should include the voices of our participants.
+
The documentation should include the voices of our participants.
  
 
            
 
            
 +
I think the more direct quotes and videos we have from youth, parents, and kids, the better we will do! I am curious about including short video interviews that enrich the content but aren’t required by site visitors if they want to understand what we've been doing.
  
            **I think the more direct quotes and videos we have from youth, parents, and kids, the better we will do! I am curious about including short video interviews that enrich the content but aren’t required by site visitors if they want to understand what we've been doing.
 
 
 
We might have prompts on the wiki that ask our participants to create testimonials: to report out specific examples of what they have done and learned. (in video, or in text.) Testimonials might include:
 
 
 
  
-what interested you in doing this in the first place? What did you think might be gained?
+
We might have prompts on the wiki that ask our participants to create testimonials: to report out specific examples of what they have done and learned. (in video, or in text.)
  
-what are particularly thought-provoking stories from your project, that say something about improving communication in public education?
+
Testimonials might include:
  
-What are continuing barriers to needed communications?
+
What interested you in doing this in the first place? What did you think might be gained?
  
-What's your current take on how youth, parents, and teachers can participate in improving communications in public education, and creating new uses for basic technologies? Should others do what you have been doing?  
+
What are particularly thought-provoking stories from your project, that say something about improving communication in public education?
  
+
What are continuing barriers to needed communications?
  
              the documentation should also include our contact info, so that people can ask questions of us and our participants. Maybe we and our participants can offer our contact emails and urge people to “please contact us!”
+
What's your current take on how youth, parents, and teachers can participate in improving communications in public education, and creating new uses for basic technologies? Should others do what you have been doing?
  
+
The documentation should also include our contact info, so that people can ask questions of us and our participants. Maybe we and our participants can offer our contact emails and urge people to “please contact us!”
  
            The site should be hypertextual: in sentences, we put in links to relevant/research/prior information.
+
The site should be hypertextual: in sentences, we put in links to relevant/research/prior information.
  
            We should offer an index that also talks about other things to read.
+
We should offer an index that also talks about other things to read.

Revision as of 10:01, 25 May 2011

Vision for the wiki documentation:

Documentation should be coherent -- glued to our core research questions, throughout.


Documentation should be visually inviting. Think of enticing a teacher or young person or parent to tackle (or document!) similar issues where they live.


Documentation should in the end be downloadable, and distributable by people; something they can email around their school.


The documentation should include the voices of our participants.


I think the more direct quotes and videos we have from youth, parents, and kids, the better we will do! I am curious about including short video interviews that enrich the content but aren’t required by site visitors if they want to understand what we've been doing.


We might have prompts on the wiki that ask our participants to create testimonials: to report out specific examples of what they have done and learned. (in video, or in text.)

Testimonials might include:

What interested you in doing this in the first place? What did you think might be gained?

What are particularly thought-provoking stories from your project, that say something about improving communication in public education?

What are continuing barriers to needed communications?

What's your current take on how youth, parents, and teachers can participate in improving communications in public education, and creating new uses for basic technologies? Should others do what you have been doing?

The documentation should also include our contact info, so that people can ask questions of us and our participants. Maybe we and our participants can offer our contact emails and urge people to “please contact us!”

The site should be hypertextual: in sentences, we put in links to relevant/research/prior information.

We should offer an index that also talks about other things to read.