<div dir="ltr">Congratulations on getting a class up and running. It's been a long time since one could take that for granted.<div><br></div><div>Here are some <i>unofficial</i> reactions:<br><div><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-AU" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">1.<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'">
</span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Study Design (SD) defines by giving a list of what are websites for online communities. Wikis blogs etc. Do we have to author one of these?</span></p></div></div></blockquote><div><br></div><div>Yep. But obviously in the real world few sites offer only ONE of those tools. There is usually a combination of them for different purposes. The case study you give kids should guide them in their choices of what tools need to be added. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-AU" link="blue" vlink="purple">
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The SD also lists the web functions or HTML features eg CSS that we must use. If I go online and just find a site and use their tools to build a wiki is that
enough. Seems to me that you would not get to use a lot of HTML if you did that.</span></p></div></blockquote><div>The SD is looking a bit long in the tooth now, IMO, in its assumption that sites are created with individual HTML/CSS pages with an editor. But you should probably resist the temptation to use automated web creation sites, CMS etc for the time being and instil in kids knowledge of basic concepts indicated by VCAA's list of required functions. Including ALL of the features is a reach, however: none of my kids ever included EVERY listed function in their sites.</div><div><br></div><div>Remember that the 'prototype' rider means that you don't have to make wikis, blogs etc actually <i>functional</i>. </div><div>- I got kids to take a screen shot of (say) a wiki, edit it in Photoshop so its contents looked relevant to the case study, and stick the image of the wiki into a webpage.</div><div>- Web forms need not actually send data to a real destination site.</div><div>- Login screens can also be faked. A screenshot of a login box with an image map placed over the "login button" can be linked to the "You are logged in" page, so when the 'button' is clicked, it simulates a login.</div><div><br></div><div>The main thing of the outcome, I believe, is that kids demonstrate their knowledge of the <i>need</i> for certain features, such as a wiki, data entry facilities, security, and create a site that demonstrates that they know <i>how</i> these needs can be satisfied - even if they're faked.</div><div><br></div><div>So - no <b>real</b> wiki, blog, login box, search box etc are needed. Implementing most of them in a school environment would be damned near impossible anyway, and don't add to a kid's demonstration of their understanding of the key knowledge.</div><div><br></div><div>2.2c worth (with GST)<br>Do you have a Rewards Card?</div><div><br></div><div>Cheers</div><div>Mark</div></div>-- <br><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Mark Kelly</div><div>mark AT vceit DOT com</div><div><a href="http://vceit.com" target="_blank">http://vceit.com</a></div><div><br></div></div></div></div></div></div>
</div></div></div>