Blogs, Wikis, Docs: Which is right for your lesson?
A Comparison Table
A blog is a web log, a frequently updated website. More - http://en.wikipedia.org/wiki/Blog
A wiki is a web page that visitors can quickly edit. More - http://en.wikipedia.org/wiki/Wiki
Google Docs provides an online office suite that allows you to access your documents from any computer via a web browser. It also facilitates collaboration and sharing. More - http://en.wikipedia.org/wiki/Google_Docs
Usually only one person or a small team can post. Each post is one author's voice. Others can only leave comments.
Many. Most wikis allow either anonymous editing or editing by a limited number of approved users.
Each document is created by an individual, who can then invite collaborators.
Usually visitors can comment. Sometimes a small team has the ability to post.
All visitors can be collaborators - or access to edit the wiki can be limited to approved users.
Docs can be shared with a small team of collaborators at one time (synchronously). A larger number of users can collaborate asynchronously.
Reverse chronological order. The newest post appears at the top of the page and older posts move down until archived (usually by month). Most blog systems also support creation of a few static pages, such as an about page or class expectations page.
A wiki site is a hyperlinked collection of individual pages.
Each document is separate. Users can view all docs that they create or collaborate on at their Google Docs home page, which allows organization in folders. A published document can be viewed as an individual website.
Frequency of updates varies, but blogs tend to be updated more often and more consistent than wikis and docs. Visitors return often to blogs that are updated frequently and consistently. RSS users can also subscribe to a feed so that new posts come to them automatically.
Wikis are updated as needed, usually when new information about the topic becomes available, information changes, or a mistake is found. RSS users can subscribe to a feed so that they are notified of changes automatically.
Docs are usually created and edited for a specific purpose, but they can be saved indefinitely for reuse at a later time.
Blogs are easily created and easily updated.
If you can email, you can blog! And adding images and files is as easy as adding attachments.
Some blog systems allow authors to embed media.
It's a Two-Way Technology - visitors can leave comments.
Most blogs allow teams of authors with various permissions.
Some blogging systems allow users to download a backup of their blog.
Wikis maintain a history of all revisions to each page, including who made what changes.
Most wikis also provide a discussion forum for each page, though this is not always a threaded discussion.
Most wikis allow different permissions for different users.
If you can word process, you use a wiki! And adding images and files is as easy as adding attachments to an email.
Most wikis allow users to download an html backup.
Google Docs are the best choice for synchronous collaboration on a single document - with some delay, users can see others changes as they occur! The system handles conflicting changes well.
A history of revisions is kept for all documents.
Each spreadsheet has a built in chat room for collaborators.
Each presentation has a built in chat room for viewers.
Upload and export most word processing and spreadsheet file types.
No multiple authors on a single post (usually).
No history of revisions on a single post (usually).
Though archives are searchable and can be organized by category, it can be difficult to find old content.
Some blogging systems do not allow users to download a backup of their blog.
Users can overwrite each others' changes if they are editing the same page at the same time. Wikis are best for asynchronous collaboration, not synchronous collaboration.
Though many wiki systems now have WYSIWYG (what you see is what you get) editors, some wikis require additional knowledge of wiki syntax that is different than HTML. This is helpful for troubleshooting problems with WYSIWYG editors, too. Wiki syntax can be different for different wiki systems.
Though a history of revisions is available, archives of old content are not easily accessible by category or searching.
The history of revisions can be difficult to navigate.
Old data may be difficult to find because it is not easily accessible by category or searching.
Only a small number of users can collaborate synchronously. (About 10 in docs and presentations, but Google says 50 can join a spreadsheet at one time.)
Docs only allow two levels of permissions: viewers & collaborators (plus owners).
Importing and exporting files is limited to only a few formats (but Microsoft Office formats are included: .doc, .xls, .ppt)
Spectrum of Uses:
Subject Specific Examples:
More On Educational Wikis: