Vision for OneVille documentation

Overall hopes for our documentation:

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

Most of all, we need analytic "buckets" coherent across the project. Otherwise the project will not make a clear contribution to thinking or work.

The project needs to be analytically coherent to make a difference. That work --naming categories for data and ideas -- is what usually takes the longest and is the hardest. Doing it now is hard. But we need some incredibly basic "buckets" that hold constant across the documentation even as each working group then goes forth.

===Who is this for===: we want to create one form of online documentation (not multiple) that:

a) helps teachers, families, and kids tackle similar issues and efforts where they live, and, b) helps researchers or public to think differently about communications in public education.

We write for a) and also to include b). So, our focus is on supporting practice, but letting researchers and others learn from that.

-cites to any research or other projects go in footnotes. -simple language. -examples of “how to” take precedence.

  • TBD: should we keep one consistent structure on each project's main page, or not? See parent connector network as one draft structure.

Documentation should be visually inviting. Think of enticing a teacher or young person or parent to tackle similar efforts where they live.

The site should be hypertextual and particularly, should link to other projects within the OneVille Project. Also put in links to relevant research, prior information.

The documentation should include the voices of our participants. (see below)

(More details:)

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

The documentation should perhaps also include our contact info, so that people can ask questions of us and our participants. Should we urge people to “please contact us"?

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


Of particular concern: including participant voices

Some of us will literally construct the documentation with our participants but we should start w/ a template each time. That could include:

a. texting: a subset of kids and teachers helping us look over an initial layout, and update it.

b. eportfolio: Susan and teachers and kids and EliJAH will design their documentation together, based on the initial "buckets."

buckets for the stuff that should be documented in each project:


ADD BUCKETS HERE.

    • HOW TO set up the technology of it.



We hope that the more direct quotes and videos we have from youth, parents, and youth, the better we will convey what we've been doing.

We might get quotes from participants through targeted interviews now, or, take them from data collected throughout the project.

We might include short video interviews that enrich the content but aren’t required by site visitors to watch if they want to understand what we've been doing.

Some prompts for getting those voices:

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?

Technical instructions aiding OneVille colleagues in the documentation

How to upload an image to the wiki:

http://www.mediawiki.org/wiki/Help:Managing_files

from ^ but modified for our theme slightly:

Upload a file

  1. Prepare the file for upload. Make sure the file is exactly as you want it.
  2. In the sidebar, under “toolbox”, click “Special Pages.”
  3. On the Special Pages page, click "Upload File"
  4. Click “Browse” next to the “Source filename:” to locate the file on your computer (the name of the “browse” button depends on your web browser).
  5. Change the “Destination filename:” to something descriptive, if necessary.
  6. Fill in the “Summary,” if necessary.
  7. Click the “Upload file” button.


To use an image in another page, you treat it much the same as a wiki link:

^ File name |size to display | caption ]]