Download as KEY, PPTX
Uploaded byLawrence Bruce
Making Wikis Work
The document discusses how teachers can increase the workload of wikis in their classrooms to take them to the next level and help both teachers and students achieve more. It provides examples of how wikis can be used for publishing student projects, facilitating student projects with templates, maintaining a class calendar, guiding the curriculum, and creating student portfolios. The document emphasizes that wikis demand participation and work best when created for a specific function that will be used.
More Related Content
![Making Heads Or Tails Of Web 2 0[1]](https://cdn.slidesharecdn.com/ss_thumbnails/makingheadsortailsofweb201-1231978427303410-2-thumbnail.jpg?width=640&height=640&fit=bounds)
Making Wikis Work
- 1. Making Wikis WORKFor Your Classroom Take your wiki to the next level by increasing the wiki workload, helping both you and your students to achieve more than ever before. Lawrence Bruce @bruce1lj Union City Community Schools bruce1lj@gmail.com High School U.S. History, World Studies mrbruceshistory.wikispaces.com
- 2. Making Wikis WORKFor Your Classroom Take your wiki to the next level by increasing the wiki workload, helping both you and your students to achieve more than ever before. Lawrence Bruce Union City Community Schools @bruce1lj bruce1lj@gmail.com High School U.S. History, World Studies mrbruceshistory.wikispaces.com
- 3. Making Wikis WORKFor Your Classroom Take your wiki to the next level by increasing the wiki workload, helping both you and your students to achieve more than ever before. Lawrence Bruce @bruce1lj Union City Community Schools bruce1lj@gmail.com High School U.S. History, World Studies mrbruceshistory.wikispaces.com
- 4. Making Wikis WORKFor Your Classroom Take your wiki to the next level by increasing the wiki workload, helping both you and your students to achieve more than ever before. @bruce1lj Lawrence Bruce bruce1lj@gmail.com Union City Community Schools High School U.S. History, World Studies mrbruceshistory.wikispaces.com
- 5. Making Wikis WORKFor Your Classroom Take your wiki to the next level by increasing the wiki workload, helping both you and your students to achieve more than ever before. Lawrence Bruce @bruce1lj Union City Community Schools bruce1lj@gmail.com High School U.S. History, World Studies mrbruceshistory.wikispaces.com
- 6. No Feverish Writing! MACUL Space: maculspace.ning.com My Profile: Members>Search:Lawrence Bruce Multiple File Types (Slideshare, Google Doc, PPT, Keynote, etc) While there, join the conversations by becoming a member! Class Wiki: mrbruceshistory.wikispaces.com “MACUL Visitors” Same options as above
- 7. Introductory Resources WikiWalk-Through: http://www.teachersfirst.com/content/wiki/ EduWikis: http://educationalwikis.wikispaces.com/ Wikispaces for Educators: http://www.wikispaces.com/site/for/ teachers Wikispaces Features: http://www.wikispaces.com/site/features Notice a trend? Wikispaces is worth promoting!
- 8. What Are Wikis? Session for all levels, but perhaps not everyone Necessary thoughts on design, important for beginners on up
- 9. The Field... Many Collaborators Static Dynamic One Author
- 10. The Field... Many Collaborators Static Dynamic Developed by “experts” using Dreamweaver, NVU, Traditional iWeb, FrontPage - web files hosted on purchased Website server space (GoDaddy, MobileMe, et al) or on school web space. One Author
- 11. The Field... Many Collaborators Static Dynamic Weebly, Squarespace, Google Sites, Webs Traditional Web-Based Website Publishing One Author
- 12. The Field... Many Collaborators Static Dynamic Blogs Traditional Web-Based Website Blogs are blogs... Publishing One Author
- 13. The Field... Many Collaborators Social Networking Facebook, Ning Static Dynamic Blogs Traditional Web-Based Website Publishing One Author
- 14. The Field... Many Collaborators Social Networking Course Management Static Moodle, Blackboard, Dynamic Edmodo Blogs Traditional Web-Based Website Publishing One Author
- 15. The Field... Many Collaborators Social Networking Course They continue to Management span the Static spectrum, they Wikis Dynamic do it all! Blogs Traditional Web-Based Website Publishing One Author
- 16. The Field... Many Collaborators Social Networking Course Management Static Wikis Dynamic Blogs Traditional Web-Based Website Publishing One Author
- 17. Wikis Do itAll The possibilities with wikis are endless What do you want your wiki to DO? Determine function, then plan for design
- 18. Function Variables impactingfunction Audience: students, parents, both, neither Accessibility: computer lab, single workstation in classroom, 1:1
- 19. Examples Publishing Student Projects FacilitatingStudent Projects Use a Template Class Calendar Curriculum Guide Portfolio
- 20. Publishing Student Projects Students create all sorts of projects through the year Work deserves to be displayed Publish student work along with assignment description Allow for feedback and reflection New Deal Presentations http://mrbruceshistory.wikispaces.com/7.1.3+Presentations+10
- 21. Facilitating Student Projects Student-created web pages as an assessment of learning Students can embed media, hyperlink to outside sources Discussions can be held on page content Use rubrics for evaluation The Big Kahuna http://mrbruceshistory.wikispaces.com/Big+Kahuna+2013
- 22. Use a Template A blank slate can be intimidating for many students Create a template that is more directive and includes the objective Inaugural Addresses http://mrbruceshistory.wikispaces.com/08-09+Inaugural+Address+6th
- 23. Class Calendar Everhave a student absent? Issue instructional materials, directions, media, links, resources, etc. Use a “calendar template” to make this task simple This Day in History http://mrbruceshistory.wikispaces.com/Class+Homework+Calendar
- 24. Curriculum Guide Instructionalplatform based on content expectations Place instructional content on expectation pages Involve students Include elements of both instruction and assessment Curriculum Page http://mrbruceshistory.wikispaces.com/Curriculum
- 25. Portfolio - StudentPages Curriculum = Template for student page Students link demonstration of understanding to expectation to have been learned Discussion and reflection on their work Demonstrate and evaluate growth and learning Student Pages http://mrbruceshistory.wikispaces.com/Class+of+2013
- 26. Lasting Value Wikis Demand Participation Create Somthing to be USED Open structure + Open Mind = Function
Editor's Notes
- #2 Opener:
- #3 Opener:
- #4 Opener:
- #5 Opener:
- #6 Opener:
- #7 Opener:
- #8 Opener:
- #9 Opener:
- #12 If you’re wondering what a wiki is, this may not be the session for you. I hope to provide those that have already created a wiki site or those that are considering creating one with a picture of the potential of such a tool as Wikispaces (or other). If you’re new to wikis, I hope to direct your thinking toward an open horizon. Wikis are much more than a fluffy buzzword expected to die off.
- #13 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #14 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #15 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #16 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #17 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #18 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #19 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #20 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #21 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #22 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #23 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #24 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #25 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #26 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #27 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #28 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #29 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #30 Traditional Website: Developed by “experts” using Dreamweaver, NVU, iWeb, FrontPage - web files hosted on purchased server space (GoDaddy, MobileMe, et al) or on school web space. Web-Based Publishing: Weebly, Webs, Google Sites, Blogs: No examples necessary Course Management: Moodle, Blackboard, Edmodo Social Networking: Facebook, Ning Disclaimer: There is an opportunity cost. What is gained in collaborative functionality, you lose in complete control over aesthetic flexibility.
- #31 Wikis can do it all. They can be the static teacher home page that exists to welcome students and parents and to perhaps disseminate digital content, or they can be the dynamic, multi-collaborator site where students all contribute and change content daily. If this is the case, that means your purpose falls somewhere in the middle. The question becomes, what is your purpose. What do you want your wiki/web presence to do? What will be its function? Variables exist: Audience Accessibility Once the function has been determined - and understand that function can change over time - then planning can begin. Designing your wiki is more important than many organizers realize, especially if you seek to have others collaborate with you.
- #33 List increases in intensity and involvement.
- #36 Templates are an easy way for students to make a wiki project a reality without stepping on students’ toes. Consider it an interactive worksheet/handout/assignment sheet. Viewing the 6th hour page show: the blank template Chris and Susan Jasmine and Marissa
- #37 Identify that this satisfies a much-needed gap in every classroom. When asked about the events from the preceding day, it is exhilarating to respond, “Check the calendar”; partly because you have no idea what you did yesterday. The creation of this calendar required a significant amount of time. Setting up the month tables with my numerical images that linked to non-existent pages was cumbersome at first, but now requires no maintenance. The trick is in unique names so that next year’s March 11 does not show content for today. Updating in-between school years takes a bit - but not nearly the intensity of the first.
- #38 Create an instructional platform that is directly linked to content expectations Place instructional content on expectation pages Have students create expectation pages Instruction and assessment on the same page Copy and paste the GLCEs or HSCEs into a the wiki page and make the numerical annotation a link to its own page. Then be creative about what to do with that page.
- #39 Student portfolios are Make a template that starts from the Curriculum Page. Make every expectation a new row.
- #40 Wikis are websites that demand participation. Compare to a teacher creating a website - employing time, effort, and resources (sometimes monetary) - that is never visited. Blogs have a similar goal/function/value. However, wiki involvement is so much more advanced.