My handwriting is poor. For years I have joked that I can get away with this because I’m a doctor.  And I have absolutely no trouble reading my own brand of shorthand. What’s the problem? As a writing teacher, I am always commenting on my students’ texts, mostly in marginal notes on papers and in an end comment letter. I work very hard to write legibly on my students’ texts. But the fact remains that my poor handwriting always makes its way into those comments. I offer a translation “service” to my students when I hand back papers and dedicate class time to a reading of my comments before we work to put common writing challenges on the board. And over the term my students do become better interpreters of my shorthand.

Commenting on student texts has always seemed more personalized when I’m hunched over a desk with a pencil in hand, making decisions about where and when to mark the text. And space limitations of the margins help reduce the likelihood that I’ll overwhelm the student with feedback, though that’s always a real possibility.

Back around 2001, when I taught freshman writing as an asynchronous online course, I experimented with digital markup using Acrobat. I found it time consuming and clunky, and while I could write more text quite quickly – and legibly – I disliked the distance the process put between the printed page and myself.

MS Word’s comment tools and track changes have always bugged me for some reason. Perhaps it’s the ease with which one can simply “accept all changes,” effectively allowing a student to let me revise the paper. (I feel this way even though I almost never actually rephrase or rewrite a student’s sentence.) This is already a challenge in teaching revision: students often revise only those moments we mark in a text, thinking that will “fix” the paper.

Strange. For all I’ve done to embrace emergent digital writing technologies over the last dozen years, I have resisted what is perhaps the most basic tool the writing teacher might adopt in working with student texts. Until now.

Enter Google Docs

I feel like a luddite for not getting serious with Google Docs. My institution uses Google Apps for Education, effectively putting all of my students on the Google network. This is quite exciting for a number of reasons that go way beyond Docs. But that’s another story.

Students write their papers directly into a Doc they create on their account, copy-paste a text document from their computer into a Doc, or upload a text doc to Docs. Once they have the paper appropriately formatted (double-spaced, block quotes, page numbers, etc.), they “share” the document with me. I comment on the document and they get immediate feedback.

It’s a bit like MS Office, making it less than beautiful, only I don’t need to have the files on my machine or worry about file compatibility. (Until this term, I regularly received attachments in .pages, .doc, .docx, .txt, .odt, and even – yes – .wpd formats.) I have four different word processing programs on my computer so that I can handle this variety!

I do have an issue with “shared” documents and marking texts. The real-time nature of Docs means that my comments show up immediately. I prefer to distribute final, marked papers at the same time, particularly since it can take several days to work through a (virtual) stack of papers. The workaround I’m using involves copying the shared document, pasting it into a new document I own, and making my comments. I can then share the comments to each student at roughly the same time.

Peer Review

More important than the way this tool enables me to comment on texts is its potential in the peer review process.  My approach to peer review has always involved in-class reading and discussion of student texts. Everyone brings multiple copies, small groups do read-arounds and discuss each text in the group, and I sit in on groups to offer guidance and encouragement.

New this term, I’m putting the reading of drafts onto homework, with the class period reserved for discussion of the ideas and suggestions for revision. Students share their draft Doc with designated peers; commenting happens on the Doc.

I can quickly and easily see the character of the students’ comments, flag and echo some of the best comments by peers, and add my own to the mix. Gone are the days when I would have to collect 3 copies of a draft to see the “layers” of peer feedback on a student’s text, or rely on some other elaborate, paper-heavy mechanism to evaluate the peer review in my classes.

I do worry that the marked document may overwhelm novice writers who can easily become overwhelmed by the quantity of feedback on a single document. (It would be very, very cool if the author could choose to view one set of comments or another.)

Problem – MS Office is Inescapable

In terms of workflow, I have found that the current version of Docs is very limiting when one wants to print comments. Print your Doc and the comments get stripped out before printing. Docs has a full portfolio of export/download options (.doc, .pdf, .html, and more). But only .doc preserves the comments though the export. Frankly, this stinks to high heaven!

Here’s the workflow:

1. Open Doc with comments that you want to print to bring to class, perhaps to reduce laptop multi-tasking during peer review.
2. Download .doc file to computer. Open in Word, Pages, Open Office, or another editor. Print.
3. Bring to class.

This approach isn’t too cumbersome if you’re only printing one Doc. Now multiply the process by 20, 40, 60 to hand back papers with comments.

The writing teacher has already spent 15-30 minutes marking each text. Putting two steps between “desire to print” and “actual print” seems ridiculous. And I’m not sure what technical hurdle would prevent comments from printing. I’m sure Google will address this in some upcoming update.

In an online or hybrid/blended writing course, I can see Docs as a wonderful tool. Printed text becomes irrelevant in an online environment.

It’s taken a little while for me to take it up, but I finally broke down and upgraded my WordPress install to the latest version. I’m only just starting to get to know this version. Still, it’s pretty clear that the WP team has made some good additions.

Drag and Drop Media Upload

Right away, I noticed a simplified media upload mechanism. WP is getting smarter. It can now detect the media type you want to upload and sort it appropriately. Even more interesting is the drag-and-drop functionality for media uploads. I gave the tool a quick test drive by uploading a header image, a shot of my backyard pond, below.

Backyard Pond.

Flyout Menus

Anyone who spends time with WP knows that the dashboard sidebar menu structure is a bit long.  On a laptop, it’s not uncommon to see the menu run below the fold, forcing a scroll just to locate the settings options.

Flyout menus changes all that.  It’s easy to see your menu options on hover, saving the extra click and streamlining the look of the text in the dashboard sidebar.

Why Update?

Good question. When is something good enough?  I can’t really answer that question.  There are security issues to consider, of course, and the newest version closes some vulnerabilities. In all honesty, the security concerns weren’t enough to move me to the upgrade.

I needed a little down time on my running sites to feel comfortable with an update.  The semester break created that down time for me.  (I didn’t want to break course websites midstream.) But that wasn’t even enough, really.

In the end, my desire to create an option for users to subscribe to Page updates through RSS led me down a path that required the update. RSS Pages for WordPress 3+ required an update to my WP 3.  That update went well, although the plugin page indicates that it had not yet been tested with 3.3.1.  Consider this a leapfrog moment.  I installed the plugin and it seems to be working just fine.

It’s official. Xtranormal is a great little online tool for composition courses, particularly if your course emphasizes the conversational nature of academic writing.

After contemplating the use of Xtranormal in my composition course for about a year, I offered students the option of creating an Xtranormal script and video in lieu of two low stakes assignments. Working in groups, students who opted for the video project produced two-minute videos that put Malcolm Gladwell, Sherry Turkle, and Nathan Rott into conversation on the issue of social media and social action.

Writing effective source-based papers with a strong dose of argument is a tough task for college freshmen. Producing animated videos that put texts into conversation can actually reduce the level of complexity involved in getting the argument rolling. On top of figuring out the texts, locating moments of connection, and putting the texts together in the service of a position or view, students need to wrestle with effective integration of texts, a balance of quotation, paraphrase, and summary, documentation style, organization, and sentence construction. It takes a full term (or two) for students to become even somewhat proficient at juggling all these elements, and it can be frustrating for them. Their ideas and readings can quickly outpace their ability to represent their views in the structure of the academic paper. Here’s where Xtranormal is a great tool.

Xtranormal uses Flash and text-to-speech technology to enable novice movie makers to produce animated videos online.

Students prepare a script that puts a couple characters in a scene and sets them in a conversation. When students have to use some of the language of the texts they’re reading as they develop the script, they really begin to do some of the hard work of academic thinking. Xtranormal is fun because the author chooses characters, a voice, a background, camera angles, sound effects, and more.

The major drawback, really, is Xtranormal’s revenue model. Rather than offer a free, ad-supported version for those unwilling to purchase the characters and sets, Xtranormal teases creators by providing seed money to make the first video. There is an education discount that puts the tool within some teachers’ budgets, but it’s likely that most students would have to work with a limited set and character selection to work in the budget of the teaser film. (Home economics for digital production?)

Xtranormal was optional this term. I think I’ll require a project of this sort next term.

I just completed the “rough” migration of my website into WordPress 3.0. I’m wrapping the weblog and the pages all in one blog. I’ll post the procedures once I finish tying up all the (very) loose ends on the project. For example, I just realized that I deleted the files that were controlling my CSS-switching experiment, a 4-5 year effort that I’d hate to lose just because I’m moving to WordPress for the site. Repairing the damage will take a little time. (Major ouch!)

What’s good about this move?

• I get Web 2.0 functionality and the database web moving forward.
• My weblog is integrated with the rest of my site.
• With WordPress 3.0 I can roll multiple sites/blogs into a single install, and manage them from one admin panel.
• This enables me to move all my course sites into WordPress (going forward). I experimented with WP-driven course sites in Spring 2010 and I mostly liked it.

What’s not good?

• My focus on content migration took my eye off design. I have a “designed” site, to be sure. But it has a very bloggy (or blocky?) look/feel to it.  In time I’ll push this issue, starting with experiments in course website.
• Lots of up front work to move things.
• Errors will be huge. (Let’s hope I don’t err.)

Last week my wife and I made the move from Palm to Android. It was sad to see my venerable Treo go, but it really wasn’t cutting it any longer. No wi-fi or GPS (in 2010!). And while it had good bluetooth functionality, the IR port on it just screamed retro. (People in IT literally laughed when I pulled it out of my pocket to schedule a meeting or check an email.) While I have yet to box it up and sell it back to Sprint (for $10 – ouch!), it’s done.

The new hotness (for me) is the HTC Evo, a candy bar of a phone with a 1 ghz processor and a 4.3″ display. It would seem huge to just about anyone in the market these days.  But it’s actually about 2/3 as thick as my Treo and not all that much larger. HD video, 8 megapixel camera,  GPS, wi-fi, and so, so much more. I’m still working my way around this beast, but it is so nice and super responsive.  I used the GPS (my first GPS experience, really) on a Maine trip and I might as well have a Garmin since the screen is about the same size.  Spoken turn-by-turn directions courtesy of Google.

And today, after discovering that my wi-fi will be a bit spotty in my Maine residence, I decided to try to use the phone to establish a wi-fi connection via USB tether. June Fabrics’ PDAnet on the Mac and on the Android. 5 minutes of installation and setup. Voila! (The image in this post comes from the June Fabrics site.)

You’re reading a blog post made from the Mac via USB tether. How’s that for cool? (Yes, I have the WordPress app for my phone and  I can post that way. But the point here is to test my ability to conduct “real” work from a 15″ screen  via my phone’s data connection. Done.)

Looks like it won’t last through the next OS update. I’ll have to think about that data plan add on, or find a reliable hotspot.

I took a test drive with WordPress 3.0 today. I installed it on my server, set up the Network capability, and took a shot at creating a couple test blog sites with the install. So far, so good. I also tried out the child theme feature recommended for theme customizations. That element also seems to be working fairly well.

After tweaking the CSS for the test “child” theme by mocking up a recreation of my main website, I’m now contemplating a wholesale adoption of WordPress for my entire website. I’m a little nervous about such a move, though I can easily see how it makes sense.

I have yet to push enough 3.0 buttons to decide if I really want to go “all in” on WordPress as a CMS for my site.  My current design is pretty tired, having been written back in 2007 and 2008.  If I’m actually going to write a new CSS for my site, I might as well consider doing it in WordPress. Hmm.

WordPress v.3 has now been released and I’m intrigued. This spring I ran two course websites in WordPress.  Previously, I had always built sites in Dreamweaver. The WP approach makes it much easier to build in RSS, and to add Web 2.0 functionality right in my single course site.  I no longer had to build the course site, and the blog as a separate site.

My success this past term got me thinking to the next 5 years, and to installing WordPress Multi-user (WPMU) on my server space.  This would enable me to build multiple course sites in a single WP installation.

With WordPress 3, it seems, I can simply upgrade to 3.0 and get multi-site functionality. The WPMU community that has grown up over the years may not be so happy about WP pulling multi-user functionality right into the core, and I can understand the sentiment given all the work in WPMU Dev, and elsewhere.

For me, this might be just the ticket. I wasn’t looking forward to getting WPMU running on my server, though I don’t expect it can be that difficult. WordPress’s “5-minute installation” just reduces all that worry – or so that’s the hope.

I was blown away at our last department meeting when it concluded with a farewell cake and much well-wishing as I prepare to leave York College for a new position at the University of New England in the fall. The cake was beautiful and delicious, and the card everyone signed left me sad to leave my colleagues. They’re just wonderful.

Deep took some pictures and sent them to me, and I’m posting them here so I’m reminded of my soon-to-be-former colleagues with each posting.

On March 3, I presented an assessment-based picture of writing at York College/CUNY. This talk was something I had been looking forward to for more than four months, and is a much more elaborated version of a talk I gave at the Provost’s 2010 Academic Leadership Retreat in late January. Following the talk, it was suggested that I make the talk available. So here it is.

I just learned that The Jump (Journal of Undergraduate Multimedia Projects out of UT-Austin) has accepted one of Anna Charles’ projects for publication in its upcoming issue.  Anna is one of the Communications Technology majors at York College, and I couldn’t be more excited for her.  I’m also excited for the CT program, and for Daniel Phelps, the Television Studio Director at York and Anna’s teacher for the project that will be published.

Her project is a great, short public service announcement-type film. I blogged about it a couple months back, as soon as I saw the film.Anna works as a studio consultant in the E-Writing Studio on campus, and assists students with their ePortfolio projects.

The work Anna has done in this film is actually work that is well within the range of our CT majors. I see this acceptance as a good sign that more CT majors can find publication venues for their work, perhaps even in The Jump.