Hey everyone! In working with other CBIs as well as developing my own, there are certainly things that need to be considered so that this resource may reach its fullest potential. When first thinking about what would make a good CBI resource, I simply figured that the content needed to be adequate/correct and that the site/links should be completely functional. In retrospect, there are many more things to consider, many of which are taken for granted but important none-the-less. First it is important that the audience is identified and kept in mind when designing the resource. Also, there should be a clear purpose and the resource should meet all of these objectives. The general look of a CBI is also important, including the clarity of text, the layout of pages, and the spacing of text and links. It is important that a student not be discouraged by what the information that they are being presented with looks like before they have a chance to learn anything. Finally, the lessons, whether it be in a StAIR project or a WebQuest, need to be clear and interesting. There are some pitfalls that should be avoided, but by keeping these things in mind in creating CBI opportunities, students should be successful.
The following link http://www.catawba.k12.nc.us/techtrac/plus/mcintosh/ is a good example of a WebQuest for a newspaper project for the novel To Kill a Mockingbird. The site is very clear, accessible, aesthetically pleasing, and fully functional. Through this teaching tool students will better understand the novel, but also be able to connect their lives to the literature which is the ultimate goal.
Check out this WebQuest and let me know what you think!
Your point about identifying the audience in key. If a webquest is chosen poorly students won't be properly prepared for it.
ReplyDeleteThe webquest you chose sounds interesting and a neat way to engage the students in a literature, although I'm not sure I fully understand what is being shown/explained in the processes tab.
Justin,
ReplyDeleteI felt the same way about the big key of a webquest was that it was simply functional. I think your point about the actual appearance of the webquest is one that many people overlook. If the webquest itself is not presentable, that could ultimately outweigh the depth of the information since people will never look past the opening page.