Group items matching

in title, tags, annotations or url

Providing a rich and engaging environment for your children

Years later, I found out that they were visiting a questionable chat room where a stranger was vaguely threatening them.

seventeen-year-old son of a Pakistani immigrant had connected with a like-minded geek with whom he had begun sharing ideas for creating apps — and soon a business was launched.  His mystified father shook his head as he told this story. “I don’t know how he did that,” he said.

ProfHacker has written quite a bit about the app and their post “GoogleDocs and Collaboration in the Classroom” is chock-full of links to various tips and useful ideas. Getting Smart’s “6 Powerful Google Docs Features to Support the Collaborative Writing Process” provides an excellent step-by-step guide to using Google Docs especially for collaborative writing. And for a basic overview of Google Docs’ features and potential uses, you can browse through this slideshow:

I have asked my Basic English Skills students to keep a daily journal (which can be on anything they wish to write about and functions to help them build their writing muscles) in Google Docs, which they’ve only shared with me. Besides alleviating any anxiety students might have felt about making their journals public, Google Docs allows me to easily monitor new entries (whenever a Doc is edited, the title turns bold) and to verify when students are completing their entries (by using the revision history feature).

I decided to have the students write in teams of three, with one team member serving as lead editor each week. The lead editor is in charge of each week’s blog post, which includes coming up with a focus question and locating 2-3 sources to help them answer their question, which they share with their team before the week’s first class meeting (I have had the teams indicate each week’s lead editor in a spreadsheet in Google Docs so that I am aware of which students are in charge each week). But it gets really interesting when the teams come together in the week’s first class meeting. The lead editor creates a Google Doc, which they share with their team and me, and type in their focus question and a brief summary of how they plan to answer it. What follows is a 30-40 minute session in which the team discusses the question, the lead editor’s sources, and their plan for answering the question completely in writing in the Google Doc, observing a strict rule of silence (I adapted this activity from Lawrence Weinstein’s “Silent Dialogue” activity in Writing Doesn’t Have to Be Lonely).