Skip navigation
All People > Laura Gibbs > Laura Gibbs' Blog > 2018 > February

This is a post not so much about Canvas (although I could deploy this same web content in a Canvas page if I wanted to); instead, it is meant more as an example of very specific solution for my classes to a very GENERAL problem that I think we all face: how do we surface student content in a class so that students can see their own work as being of real value?


As someone who really believes both in constructivism and in connected learning, it is absolutely essential for me that the students be able to share their content with one another. I could go on and on about the pedagogical reasons for that (just Google non-disposable assignments for lots of thoughts and leads to follow), but what I want to focus on here is the practical problem that we face: when there are a lot of students (I have 90 students total every semester) who are producing a lot of content (my students write one or two stories every week that I want to share), then what can I do to make sure that this valuable content finds an audience of other students...?


Last semester, I tried a "live stream" experiment where I used Diigo to bookmark new story additions to the students' projects, and then with Diigo RSS I displayed that live stream in Canvas and also on the project directory page at my class website. The Diigo RSS worked great, but I wasn't getting the complete surfacing that I really wanted: there were too many new stories coming in, especially at certain times of the week, so they were not all getting equal display time, while other stories were getting more display time, etc. And using Diigo as an image management tool was hard because it doesn't work well with screenshots; Diigo really only works for image files that are part of the bookmarked page, and even then it created some weirdly truncated thumbnails.


My new approach this semester: an image randomizer. Randomness is a superpower for displaying content when you have a large body of content that you want to surface, especially the randomizer is used on a page that students visit frequently, which is definitely the case for the class project directory pages: Myth-Folklore and Indian Epics.


There's an alphabetical list of links in the left-hand column, and the right-hand column contains multiple iterations of the image randomizer (there's also a text-only randomizer at the top of the right-hand column):


screenshot of myth-folklore project directory


Indian Epics project page screenshot


So, I won't go into the nitty-gritty since this is something really only relevant to my classes, but suffice to say that I have a spreadsheet (I have a spreadsheet for basically everything that goes on in my classes), and it lists the address for each student project. When a new story comes up, I snag a picture (either an illustration from the page, or a screenshot if they have used the illustration as a banner image), I put the name of the image file in the spreadsheet, and upload to my webspace. Then, once or twice a week, I update the randomizer (a simple copy-and-paste from the spreadsheet), and presto: ALL the stories appear at random, linked to the project they come from. Probably about an hour of work each week total, but it is well worth it. And it's fun to snag the images!


Now, one drawback is that, at the moment, the same image will occasionally show up more than once; it's the same randomizer repeated on the same page, which means the same image might come up at random more than once. But the odds of that happening will grow smaller over time as there are more and more images from the stories accumulating. More images to randomize!


And really, that is the only drawback... which means I am very happy with this system, much more than the Diigo stream from last semester.


One of my biggest complaints about LMSes in general, and that includes Canvas in particular, is that content is generally viewed as top-down content created by the instructor which is usually in a one-size-fits-all, this-first-then-that sequenced approach that is the same for all students. That doesn't work for me: I want to students to be able to choose what content they are working on, and I want student-created content to be at the heart of my classes.


Randomizers are a big way that becomes possible for me, and here's a more general observation about the power of random: I hope that when Canvas redoes the Discussion Boards (as surely they will some day?), they will think about the power of random for surfacing content in those discussion boards and connecting students one to another. :-)

I haven't posted here in a while; my life has been really chaotic, but I discovered a strangely FREE bit of time this evening, and I wanted to write up something about Twitter Moments which I just started using this week. I've written a lot of posts here about how much I like using Twitter as a content source for my classes. I have a dedicated class Twitter stream, OnlineMythindia, which covers the topics of both my classes (Myth-Folklore and India), plus other items related to creativity, writing, and also campus events, etc. etc., and I consider this Twitter stream a really important part of my classes.


So, that all-purpose stream is great for including in my class announcements blog (which is also my Canvas Homepage: and, but for some of my other class-specific blogs, I want to filter out just the relevant tweets for those blogs (like the MythFolklore UnTextbook). The way I used to do that was by adding class-specific hashtags to the items I retweeted (like #OU4993 for India), but the wonderful ClassicRetweet extension stopped working a while ago, and it's been a lot of trouble to add those hashtags manually.


I was honestly getting kind of frustrating and not sure what to do when I read Alan Levine's post about Twitter Moments and realized I should give them a try.
Archiving Tweets: Are You Missing the Moment?


MOMENTS SOLVED MY PROBLEM (ALMOST) PERFECTLY. So, the way it now works is that I retweet everything/anything I want in my class account, and then I "save to moments" the items that ALSO go in one of these content-specific streams: Myth-Folklore, Indian Epics, and Growth-HEART-Writing), and I embed those moments in the relevant blog sidebars (they replace my old hashtag widgets).


Because......... YES, you can embed Twitter Moments! It's like any other kind of Twitter embedding: you go to Twitter, get the embed code, copy-and-paste that code into a vanilla HTML file, upload that to Canvas Files, and then iframe that Canvas File into a Canvas Page.


So, for example, here is my Growth-Heart-Writing Moment at Twitter.


screenshot of Twitter moment with embed code


Here is the embed code:

<a class="twitter-moment" href="">Growth-HEART-Writing</a> <script async src="" charset="utf-8"></script>


I put that into a vanilla HTML file called GrowthMoment.html, and uploaded that as a Canvas File here ( is a great way to create those little HTML files). I honestly never figured out after the javascript security discussion if this will, or will not, continue to work in the future; if javascript security shortcircuits this step, you can just publish the HTML file in your own webspace (or, heck, let me know and I will publish it in my space for you if Instructure leaves you out in the cold with no home for your nice javscript):
Exploring Growth Mindset 


Then I iframed that File into a Canvas Page:

Twitter Moment: Exploring Growth Mindset 


It works!


screenshot of Twitter moment in Canvas


Some things I have learned about Twitter Moments from playing around with them so far:


-- The hashtag stream was always live, with newest to oldest. With Twitter Moments, editing is required; when you edit, you can select "newest to oldest" OR "oldest to newest" based on what suits your needs (for me, it is all about newest to oldest)


-- A Moment has cover art up at the top, so my new routine is to update each Moment once a day, changing the cover art; that's an extra step I did not have to do before, but it's actually good for my curation awareness, so I don't mind


-- Moments are LONG and the embed code doesn't let you customize the height like you can do with (some) other Twitter widgets, like the hashtag widgets I used to use


-- Embedded media do not seem to play (???) in the Moment stream like they do in the regular Twitter stream, so it is not good for displaying YouTube videos (just a link to them), WordPress blog previews (again, just a link), etc.


That last item is a real drag for me, but so far, that is the only true problem (for my purposes) that I have run into. And since I am just using these Moments in my ancillary blog, not my main course announcements blog, that's okay.


Is anybody else using Moments? What tips can you share based on your experience...?


Jonathan Yoder of course I thought of you when I was writing this post as promised. :-)