When we first set out to build the Commons, it was with the inspiration of other projects like the CUNY Academic Commons, and the Domain of One’s Own project headed up by Jim Groom among others, which at the time was a small project happening at Mary Washington University. The ideals behind that project has emerged across a number of different institutions, and can now boast their own conference. You can see some of the tweets below, to get a flavour for the event:
Standing on the shoulders of those giants, we initially adopted a policy in which all students would be provisioned only one blog. That site would play host to their academic output across multiple grades, and act as a digital portfolio of their time at HWDSB. Because WordPress, the idea was that students could also export that content upon graduating, and host it elsewhere. Part of the plan — that due to funding constraints never came to light — was the idea that each student, once in Secondary school, would be provisioned their own domain, which we could then use to embark on conversations about ownership, authorship, internet freedoms, and democratized publishing.
As an elementary teacher, having only one blog worked in my classroom, and in the classrooms of many of my colleagues. Many of our subjects are taught in interdisciplinary ways, and so the idea of having a separate Math blog, and English blog, and Social Studies blog, was an acceptable limitation. It may also have been that those looking to use blogs in the classroom were rare, and students weren’t being asked by too many others to spin up a separate site. What we are finding now is that this idea doesn’t scale well, perhaps particularly in Secondary, where students are being tasked with creating a blog for French, then another site for Media Studies, and another site for Business Studies.
One would think that seeing this explosion of additional blog requests would be a source of joy, and yet instead I’m plagued with the anxiety that the vision of one student:one blog is now crumbling.
The sites these students are creating for these classes are brilliant. The French blogs are fully translated, immersing the reader in another language. Those looking to complete the transformation can even switch the language on their site to French, to translate the blog dashboard as well as the front end.
There are Business blogs that provide opportunities for students to Explore WordPress as a site builder for fictitious companies, and Media Arts sites where students are creating digital photography portfolios.
We can’t stifle that. We need to get out of the way and allow the Commons to support that work; but building a website is a different idea than owning a small corner of the internet (one that we will fund for you while you are a student at HWDSB, without fear of advertising, or data mining, or changing terms of service). Is there still room for the initial vision? If we open up the floodgates to allow students to request multiple blogs, how do we eliminate having thousands of sites with only one or two posts, when categories in a menu could have been a strategy to centralize those posts in one diverse portfolio? How do we differentiate between website creation and the larger ideals of the #DoOO project? How do we preserve the dream, while continuing to be relevant to emerging needs?
Over the past few weeks, Andrew Kelly and I have been working together on Version 2.0 3.0 of a new Open Educational Resources Repository on the Commons. This continuing work dates back to 2015, when the 21CL team here @HWDSB began planning the Professional Development sessions for a roll-out of iPad kits for Grade 4 and 5 classrooms.
Up until that point, our Professional Development around the Explain Everything app was based around screencasting. As Doug Peterson rightly points out in a post he wrote this week, that functionality isn’t new. For this roll out, Tim Kivell ran a breakout session on “Templates in Explain Everything“. At the time we geared this session towards the more advanced user (now we introduce the functionality right away, as a great entry-point for the effective use of this app).
In order to share examples, we began hosting a few of the templates we had made on the blog we were using to help organize the day. After the PD sessions were over, we left the site up and continued to promote the space as a repository for teachers to find and submit templates for use in the classroom. That site, located at tle.commons.hwdsb.on.ca, was used for subsequent PD sessions, and still stands as an archive of the work; but as the template repository grew, we realized it should really be housed under its own URL: Enter explain.commons.hwdsb.on.ca.
We can consider this Version 2.0 of the repository. We decided to redirect users from the old TLE site to this new repo. Around the same time, Andrew Kelly and Theresa Price were hired on to help support the effective integration of technology in our self-contained Special Education classrooms. Templates in Explain Everything revealed themselves to be a fantastic means of differentiating both the task and the modality students might use to respond and share their learning. This focus on some of our most at risk learners, revealed the Universal Design for Learning opportunity these templates provided. We need to use these with everyone.
This became the message all of 21CL began to share out in classrooms, and in within the broader Edtech community. Karen Wilson, Jeff Allison, Sonya Clarke, and the rest of the previously mentioned team have delivered breakout sessions, both in schools and at larger regional conferences, on the power of these templates to disrupt traditional learning structures. The amplificaton of that message is definitely working: these templates permeated a number of different math sessions during this year’s Grade 6 TLE PD sessions led by the Instructional Coach team.
Although there were a number of different sites around the web that hosted templates like this (One of the earliest examples being Explaining Understanding), none of them made locating the templates very simple. Theresa and Andrew started reaching out to the authors of these sites, asking if we could host their templates on our new repository. Many were happy to oblige: we provide “props” to those creators within the repository metadata. The collection quickly grew to over 100 different templates, all sorted by subject area.
When Theresa went back to the classroom (😢), Andy Boldt picked up where she had left off, continuing the work in our Special Classes, and has created a number of amazing templates. We found that we could create a similar experience using the Book Creator app: when books are saved in the ePub format, they can be pulled back into Book Creator and students can continue working on them. This resulted in a brief secondary repository and submission system, but also triggered a “why are we focusing on the tool” conversation. At the rate we were going, we would soon have multiple different repositories for whichever new app came along offering similar promise. For example: I’ve been trying to find an entry-point to launch H5P as a tool for use in our school board (Aside: HWDSB Commons users can find the plugin and activate it on their site if that link looks intriguing), and those .h5p files are going to need a home once teachers start to build them.
A popular discussion topic within the team is: VLE or Commons? VLE stand for Virtual Learning Environment — in HWDSB we call it the HUB (you might know it as D2L, or Brightspace , but let’s not complicate things any further than we have to). The VLE already has a Curriculum repository, wouldn’t that make for a more appropriate venue to house this work? Invariably when we opt for the Commons, it’s because we want to share our work more broadly with our community, and with other colleagues around the province (and the world). The VLE certainly has the functionality to house resources, but the repository is private, and the permissions are traditionally hierarchical: only teachers can contribute to the resource share in the VLE.
That last point is incredibly important, and it came to fruition last week with our first student submission to the OER repository. That simple act of approving a student submission to our OER repository revealed the promise a space like this presents. When we say we want students to lead their own learning, and we honour “Curiosity, Creativity, and Possibility“, we need to ensure that our digital tools allow for that mandate to flourish. I’ve blogged in the past about the rich set of tools we offer here at HWDSB,
It connects all our other tools together via Single Sign On
It provisions access to a variety of powerful resources built by HWDSB teachers, and at the Provincial level by curriculum writing teams
Resources like those hosted on our OER site, can be easily shared within a course in the VLE
but in this case, the Commons was the right choice to host this content. As a Publicly funded institution, we need to ensure that our innovations can be shared and replicated — not only for students in Hamilton — but for students across Ontario and beyond. Sharing our work openly achieves that, whether through blogging, through Twitter, or through openly accessible resources like our new OER site. We still have a lot of work to do: we’ve added a space for tags, and the ability to categorize by Grade, so we need to swing back and add those additional search elements to the existing artifacts.
A big thank you to the teachers (and now students) who have embraced this site not just as a resource repository, but as a space where they are sharing and publishing their content for others. We are just scratching the surface of what’s possible with this space.
I’ve noticed the topic of WordPress in Education recently in my Twitter feed. @Jeffr0 over on WP Tavern was recently polling his followers for info on the type of CMS (Content Management Systems) used by schools, along with the cost to run such platforms. Here at Hamilton Wentworth District School Board, we are big WordPress users. Our main website is a WordPress site (http://www.hwdsb.on.ca). We run over 100 individual school websites on a WordPress Multisite Network, and back in May of 2011, we launched the HWDSB Commons: a second Multisite Network which now hosts over 8000 blogs for over 30 000 users.
There is a saying in the WordPress community, that WordPress is Free as in Freedom, not Free as in Beer. Beer may not the best example given the audience that may stumble upon this post in the feed (oh Puritan Canadian, you worry too much); free as is Costco samples would work as well, although it won’t look as good on a T Shirt). I don’t think I understood that concept when we first began this journey, because when you are first starting out, beyond the hosting fee, we found everything we needed in the free Plugin Repository hosted on WordPress.org. (In this instance I suppose I saw my own time dedicated to the project as a free resource.)
Think of plugins like “Apps for your Blog”. Plugins add additional functionality to your site. We use a number of different plugins to bend the Commons to meet our needs (more on that later, or by exploring the “plugins” tag on this site. Everything from BuddyPress to connect all our sites together in a Social Learning Network, to plugins that connect to our SAML infrastructure to enable Single Sign on between the Commons, our Brightspace LMS, and our Google Apps for Education instance. When you are first starting out, those free plugins are probably all you need.
I don’t want to paint a rose-coloured picture that WordPress is free though (in the beer/Costco-sample sense). I actually get quite perturbed when someone refuses to pay for a $25 dollar solution to a problem they are having with their blog, to a small web dev agency spending their time creating thoughtful solutions. We pay for premium plugins. We pay for premium themes. We pay a developer who helps us to build new functionality. The biggest difference that the WordPress in Education community provides, is that others are also paying developers to build out functionality, and the vast majority of those institutions share the things they build for free.
Think about the private CMS companies working in Education today. Most of them will have a catalogue of premium enhancements you can purchase. Sometimes, when they don’t have what you need, they will develop something for you (at an cost, and then an additional maintenance cost). Once that enhancement has been built for you, it gets added to their catalogue, and each additional client pays (again) for that same, previously developed functionality to be turned on. This incremental payment system leads to all of the school boards overpaying for functionality that already exists.
In the WordPress ecosystem we operate in, I pay for functionality to be developed, and I share it openly on platforms like the WordPress plugin repository, or on sites like Github. The money you would have spent to enable the previously developed functionality, you can now spend on something else, something that I might benefit from. Think about how much more responsible this model is, particularly when we are talking about spending public money.
We are all contributing; and the community benefits from those contributions; and our money — and the functionality of our platforms — improves exponentially faster than if we were all spending our money paying the private company over and over again for code that has already been paid for by previous customers.
This is the true benefit. As an example: we built an integration between Google Apps and WordPress, and everyone else can use it for free. The money you save by not having to pay for the same add on, can be used to build something new; something that I might need too.
Currently that community is comprised of mostly post-secondary institutions, but a couple of my K12 colleagues have started asking questions about how they might replicate what we have built at HWDSB.
This (long winded) post is an attempt to help them stand on our shoulders.
What do you need to get started?
If your school board doesn’t have staff who understand Linux, or look at you sideways when you say NGINX or Apache, I would strongly suggest paying a hosting company to host your site for you. We started out hosting internally, but as we grew, we realized that there were hosting companies out there who have a dedicated team working to ensure that the server is optimized for the kind of traffic you are going to experience. We struggled for the first few years with the site going down. It always happened on the weekend. @avivaloca would DM me, and I would sheepishly hope that the technician (who wasn’t paid to work weekends) would respond to my panicked text messages, and restart the server. Save yourself that heartache and host with a professional hosting company. Not everyone in the organization will think that your site being down is as much of an emergency as you do. I nodded my head in agreement when the Mark Zuckerberg character in the movie The Social Network stated that Facebook could never go down. That’s the kind of passion I felt about the Commons, and we are now in a place were a 500 error is very rare occurrence.
You want control of the plugin infrastructure. Although tools like CampusPress offer a limited number of plugins to enhance your experience, the collaboration I am hoping we can build towards requires you to have full control of the plugin and theme directories on your site. Otherwise you’ll still be looking on with jealous stares at what we can accomplish with our independently managed WordPress install.
Storage is going to be your biggest headache. We built that Google Apps integration to allows users to host their content on Google, and embed it on their blog. We also built an integration with Vimeo Pro that let’s us host video on their servers for cheap, without our videos ever appearing within the vimeo.com directory. That helps, but the local media library is hard to beat when creating photo galleries. You can limit the size of each site on a multisite instance so users need to manage their content. We host our content on the Amazon S3 cloud, which is the cheapest way we have found to allow users to archive work from past years without having to worry too much about space. You won’t need this right away, but eventually your users will start asking for more room. We use Tarsnap to back all that up. We haven’t had an incident yet, but you should have a contingency plan if your site gets hacked.
We use Let’s Encrypt to secure all our sites with SSL certificates. It’s free, but you need to find a host who supports provisioning the certificates. This isn’t essential, but in some of our more creative uses of the site, we have embedded a blog within a course in Brightspace, and for that, you need https.
We use a Moderation plugin to help moderate inappropriate content on the site. Part of the mandate is to create a gradual on-ramp for young users to experience social networking, in a space we have full control over. When a post or comment is flagged, the 21CL team is notified, along with the owner of the blog, and the author of the post. These are key teachable moments, and are much easier to deal with than if the same issue cropped up on a platform we have less admin control over (like FB or Instagram).
We moderate the creation of blogs too. Teachers can create multiple sites, but with students we try to limit them to one site. This helps keep the blogging directory free from sites with only one or two posts, with the eventual hope that we will be able to help students procure their own domain in high school, and understand the value of owning their digital footprint.
For sites where we want to foster collaboration across the school board, we have created a plugin that allows students to request membership to a site. This is one of the key differences between how we use our LMS, and how we use the Commons. The LMS tends to be linked to a specific class/course. The Commons opens up the opportunity to collaborate across the hall with other classrooms, between schools within the school board, or around the world with external community partners, or other international contacts.
We have an integration with Brightspace that syncs the membership of a course to a role on a blog. This is great if a class wants to create a group blog to collaborate with their classmates. Think of it like the discussion forum is the rehearsal space, and the blog is the public performance space.
We have set up a site for all of our secondary schools, and a number of our elementary schools, to create an announcements slide show functionality, that is embedded in school websites, and displayed in the hallways of schools, and within classrooms. That Brightspace sync makes sure teachers all have the correct permissions to be able to add announcements from anywhere.
We host LOTS of classroom blogs. These sites create a window into the learning happening in the classroom, and I’m sure contribute to richer “what did you do at school today” conversations around the dinner table.
Some things we don’t do too much of yet: @therealmrkelly and I have been talking about podcasting lately. I noticed local Journalist Joey Coleman tweeting recently about the Podlove plugin that powers his podcast and need to explore that further.
On the topic of journalism, every school should have a student newspaper, and the Editflow plugin is installed and ready to be activated on any school site looking to explore this medium.
We solve a lot of problems with WordPress. We share all our solutions with the broader WordPress community. Maybe you should consider joining us.
I’ve been working on and off for a little while in the off hours on re-configuring how announcements are delivered at schools. We currently have an incredibly convoluted process that Paul Hatala and I conjured up when we were building the secondary school landing pages in the HUB (our LMS). Looking at it now, it seems like perhaps we were trying to see how many different pipes we could connect together before reaching our destination.
Teachers submit an announcement through a Google Form
That Google Form feeds a Spreadsheet
The Spreadsheet is running a Google Script add-on called FormEmailer
FormEmailer sends an email to a secret email address set up on a WordPress blog running Jetpack
Jetpack has Post By Email enabled, and takes the #tokens# from FormEmailer, and converts them to a blog post
The RSS feed from those blog posts feed widgets in the HUB created on http://feed.mikle.com/
All steps from Version one except the widgets from step six
While that is happening, back on the Google Form, it was determined that pulling announcements from the spreadsheet was difficult, so another Google Addon, DocAppender, came to the rescue, to make announcements more legible for reading off the PA
An IFTTT.com recipe is sending each Slide as a Tweet in a few instances
Someone needs to be deleting the slides once the announcement is no longer applicable
And then sometimes it breaks. We never know which cog in the gears is the offender, so fixing it is always an adventure.
Enter Version Three
It’s a blog on the Commons.
That’s it. One piece of software (with multiple custom bits built into the theme). So when it breaks, it’s easy to fix, and when a school wants to start digitizing their announcements, we don’t have to pull out the two pages of documentation created to build version one and two.
It still uses those beautiful reveal.js slides from version two, which can be embedded in different places (like the HUB, and school homepages, or on websites like this). It looks great on monitors hanging in hallways, and is responsive, so it looks nice on your phone too.
Panic Inc. has created an app called Statusboard, that provides a widgetized interface for creating displays. This one includes a feed from an Outlook calendar with the rotary days on it, a feed of Tweets from a Twitter Account, a Countdown widget, the Announcements Slideshow, the Weather, and the Time. You can develop your own widgets for the board, so students could expand on the functionality I’m just scratching the surface on here:
I’ve created an instruction manual that lives on the site, along with a couple of videos to explain how it all works. Schools interested in adopting this new system can reach out to the 21CL team for assistance:
Why Go To All That Trouble?
One of the new strategic directions at the school board this year is about communication. This method of announcement delivery takes what was once private on the PA system in the school and presents it to the parent community. It also makes it available to students who couldn’t-hear/weren’t-listening/missed-something/were-absent while the announcements were being presented. It gives caregivers an opportunity to help get students involved in their school (Hey, you should go out for that play/team/club/thing).
Many of our schools can now boast having a digital projector in every room. Phase two of the master plan is to eliminate the PA system announcements all together. Why not display and read the announcements in your classroom at a time when students are ready to consume them, rather than when they are still struggling in the hall with snowpants or locker combos. What could an English class do with the concept of being communication managers for their school? What makes a good slide? A good Tweet? What other multi-media could we use to disrupt announcements (Props to SJAM-TV on forging a path here). There are companies who pay for social media managers to help support their digital footprint. What role could our students play in this at a school level?
We want students to do real things, and real things are necessary to help a school run. This is a small example with what I believe has a lot of potential. I look forward to seeing where people can take it.
Warning; technical details ahead: Over the weekend, the entirety of the Commons was switched over to the HTTPS protocol. This has been in the works for a few months now, and took a few key steps.
We first needed to secure all of the content that you share on your site. We accomplished this by shifting all our media content to be served up using an S3 Offloads plugin developed by a company from Nova Scotia named Delicious Brains. For the most part all 200 000+ media items made the shift over to their new home. You might find you need to add your header back to the top of you blog, or if you manually referenced an image or file in a widget on your sidebar, you may need to grab the URL again now that it’s being served from a different server.
The next step was to procure certificates for all our our custom domains. Most of the sites on the site are covered under a wildcard certificate: *.commons.hwdsb.on.ca, but users who have opted for a custom URL aren’t covered by this certificate. We leveraged an exciting new initiative called Let’s Encrypt to secure sites like mrpuley.ca, suedunlop.ca, adunsiger.com, and mrjarbenne.ca. Although these sites comprise a small subsection of the 7097 sites hosted on the Commons, I’m inspired by the work of the Domain of One’s Own project, and would love to eventually see our work extend out to allow students to being building out their own digital cloud, as referenced in that linked article from Wired Magazine:
“Writing for EDUCAUSE Review in 2009, Gardner Campbell took the argument a step further. In A Personal Cyberinfrastructure he argued that learning to build and operate a personal cloud was a life skill students would need and should be taught”
If you don’t see the green lock at the top of the browser bar, you might have “mixed content”. This is caused by elements on the page that aren’t secured, and are still being delivered via http, and not https. In many cases, you can navigate to the post in question, and just add an “s” to the end of the “http” portion of the URL in the embed code (most sites that offer embedded content are secured by SSL. If you use a service that isn’t secure, reach out to them on Twitter and ask them to secure their embeddable content). Mixed content has been an “issue” within the HUB (Desire2Learn/Brightspace) for a few years now, so users who navigate that space will be aware of the issue. There is a movement to secure the web that we heartily support.
We couldn’t have done this without the help of our web-host and WordPress security specialist @boreal321.
As always, if you run into issues, don’t hesitate to comment below, or reach out to your 21CL Consultant via email.
5 years ago, around this time of the year, we sat in the Memorial Building in Ancaster, feeling like perhaps it was too late, and that maybe we should wait to launch until Semester Two. What would become the Commons had just been brought to life on a small server. Most of the summer was spent to ensure we would be ready for September, knowing that if we lost a Semester, we would loose the year.
Today, we accepted our 30 000 user into that “little” blogging community, where we provide a stage for students to publish their work; a window into the classroom so that parents can peer inside; a space for professional dialogue. We provide a means of connecting learners across the board with other learners, with colleagues and parents, and with expertise out in our community.
And somehow through all of that, my avatar looks younger ;).