I think the biggest problem is without some sort of standardization there is a breakdown in continuity.  While we want teachers to explore and be creative, there is a break in continuity if a teacher leaves and the next teacher is not given or does not have access to an existing classroom website.  There are also issues with intellectual property and who ultimately owns the website, the teacher or the school. In general anything created while under contract for employment for the benefit of your employment the employer owns it.    And finally there are the tech support issues; how much technology support is going to be expected from the tech department for a website they know nothing about.  In practice “if you create it you are responsible for it” but in reality more often than not, if a teacher gets stuck they blind side the tech department for assistance.

John Peters
Director of Technology
North Country Supervisory Union
121 Duchess Ave Suite A
Newport, VT 05855
[log in to unmask]<mailto:[log in to unmask]>


From: School Information Technology Discussion [mailto:[log in to unmask]] On Behalf Of Raymond Ballou
Sent: Friday, August 08, 2014 7:29 AM
To: [log in to unmask]
Subject: Re: School sanctioned teacher websites

This raises some of the BYOT (as opposed to BYOD) discussion from the past.

Are you better off having your teacher, use the tool they are most comfortable and familiar with, or the tool the school is providing?

All sorts of reasons why one might win out over the other.

That said, my hope is the Google Classroom will eventually allow for website/blog features, so that the teacher can do all that from one screen.

We have one teacher who has had a current and updated webpage for at least the past decade, going from Standards Into Action, to Teacher's Workplace (?) to two different iterations (soon to be the third) of a page on our school website (Site@School, Joomla, Wordpress)

The only thing that stays the same ...



Search <> the SCHOOL-IT Archive

Manage<> your Subscription to SCHOOL-IT