The schoodl roadmap (School Documentation Architecture diagram) is a visual representation of the programs you install on your school’s main computer (not the District Server) (You should get approval about the programs you choose to install). Your main computer is usually located in the school office.

When you download a program, list them in your Administrative Wiki (for example, on a page you entitle: “Software”). Link programs together by hyperlinks. For example, on the “Teacher’s Websites” page in your wiki, list your teachers with links to their websites. If your District already has the capability for teachers to create websites, that’s OK. You can still list the links to their sites in your Administrative Wiki.

Other things to list in your wiki are your Staff Directory, school newsletters, announcements, etc. Soon. everyone will know how to find any document at your school. Starting with an Administrative Wiki is the number one item on your “To Do” list (which, by the way, you can store in the wiki!). This concept was derived many years of technical documentation experience and from best practices of Manual Writing, which I teach at Vancouver Island University.

Print, laminate, and post the roadmap around your school so that people can see the direction you’re headed.

Private Tools

The three tools should be made available to your administration and technology team (at first). Over time, you can grant others permission to contribute.

1. Administrative Wiki

To start: Get a free wiki at wikispaces!

  • Add some key pages, such as “Staff Directory,” “Back to School Newsletter,” and “Teachers’ Software.”
  • Add a page for each bubble. A “State Educator’s Network” page, would have a description and link to the state network; the “e-learning” page would describe how your school uses e-learning, including links to teachers’ websites, and the like.
  • Add a page that describes the administrative wiki, (“About this Wiki”) including how to structure information and copy and paste. For example, you may add this text:

“In our Administrative Wiki, we plan on managing all of our school’s important written content, keeping it up to date, and making it accessible to everyone. From now on, the Principal’s monthly newsletter will be located on the “Principal’s Newsletter” page. You may copy it, for example, on a back-to-school night flier, or teacher’s website.

If you have any information that you would like to add to our Administrative Wiki, please contact the technical team.”

Suggested Products:
2. District Programs
  • Add pages to your Administrative Wiki that explain how to use district programs, such as attendance and grading.
  • Add relevant links if stakeholders are meant to follow directions from another source. For example, the district should provide training on how to use attendance and grading programs. Announcements training on the front page of the wiki, if that is where you store announcements.
  • At first, information about the programs that teachers use on a daily basis can be copied and pasted to other locations, such as a newsletter or email blast. Eventually, these pages might be made accessible to all teachers.
3. Teachers’/Administrators’ Social Networking
  • For a school technology center to succeed, your stakeholders need to collaborate. To gradually change your school milieu, your teachers might vote to have a Facebook, google +, ning, or yahoo group. Remind everyone to remain professional when they communicate with others online – no bashing or bullying. As teachers share with one another, they can bring ideas to staff meetings; you will never again have trouble coming up with relevant agenda items for one again.
Suggested Products: facebook


Public Tools

4. Teacher’s Websites
  • Many schools want teachers to have websites, but do not recommend how they do so. Your technology team can provide good recommendations. Describe how your school expects teachers to build websites on your Administrative Wiki “Teacher’s Websites” page.
Suggested Products:


5. e-learning Platform
  • Classes are going hybrid! Your state or district may already have classes available to students on an e-learning platform – California does! If you want information on setting up a large series of classes on moodle or other emerging platforms, contact Elly.
Suggested Products:
6. State and Federal Links
  • Your state may provide high speed data networks, administrative groups, and other information to share on your technology center platform. Create wiki pages for them so people can readily find out the latest news about state and federal educational resources.
Suggested Products: California provides a free K12 High Speed Network for all schools in the state.


7. Content Management System
  • To enable information about your school in front of the cloud, how about using a WordPress website? This would replace Word, however, Word is still invaluable for formatting larger documents. Obviously, WordPress is my favorite cms, as you can see from this very blog you are reading! You may also sign up for a schoodl WordPress site and join our network for free.
8. School Marketing/Social Media
  • What attracts students, teachers, and staff to your school? Now that your content is being managed effectively, it’s time to advertise. Create a space in which people who want to know about your school can share information and ask questions. Facebook groups are great for this. Will you have to monitor it to make sure discussions remain positive and secure? Most likely. In social networking, entities need to make sure discussions remain positive. You may also find your school’s social media space to be a great place to answer students’ questions about your school.
  • Recent trends in social networking show that groups self-monitor in order to promote positive experiences. For your school technology center, these considerations may be a bit further down the line, but you will eventually get to the point where your tech-savvy school is the highlight of the neighborhood.

Comments are closed.