Compose and submit a project proposal for a five-week project addressing some aspect of blogging, wikis, or, more generally, social media. Post your proposal on your wiki name page. Go to your WikiName page, create a new page titled ProjectProposal- followed by YourWikiName.
Think of writing the project proposal as practice for a writing a grant. You'll need to be specific, semi-formal, and ringingly clear. Don't try to impress with language or be too clever. Grants try not to call attention to their language or the author; they focus on the project. Don't BS or strain for hype. Impress by designing an interesting and creative project that you and others will learn from.
- Draft proposals due Mon Feb 27, midnight. Post them on a wiki page, not your blog, so we both can review and revise them. I'll review them and get back to you in class, Feb 28. Expect an approval or a request for revision.
- If your proposal isn't approved on the first round, re-submit by midnight Fr1 3 March. You'll have a response from me on Sat, 4 March.
- For full credit, your project must start Mon 6 Mar, 2017. Projects officialy end on Mon 24 April.
- Post weekly reports to your blog by midnight, Monday, each week. No report = no points for the week.
- Monday 27 Mar. About three weeks into the project. Point of Abandonment. If the project isn't going well, this is the last point to re-think it.
- During the week of April 3 - 9, you'll be taking studio tours of the projects of others. The assignment will be posted.
- Last class meeting: Apr 18. We will meet face to face to compare notes and talk about preparing final presentations.
- April 24: End of project.
- TBA: Finals Final. Face to face students present their work.
- 4 May 2017 Online student reports due.
here, for instance.
For ideas for blogs and micro-blogging, look around WordPress. Review what students have done. Try the PastParticipants pages, and the PageIndex > P.
For the project, you may use your current weblog or start a new one.
If you're going to use a wiki, you'll need to find a platform. WikMatrix has a list and some advice on choosing a platform. PBWorks is good but it seems to have gone corporate, and I've heard good reports about WikiSpaces. Dig around for offers for student wikis. Dig around on our course wiki, as well.
If you take an experiment or project angle on the project, phrase your executive description as a hypothesis (Project: To discover if twittering class notes will help me master material. I hypothesize that it will lead to ...).
But your project will include a weekly reflection 500 or so words, linked to appropriate materials. The report is a consideration of what happened that week and what that might mean: what you did, what went well, what went poorly, how you dealt with things. Post this to your blog by midnight, Monday, each week. I generally check on progress on Tuesdays.
Start with an overview of your intent. In a paragraph, explain what do you hope to do, or achieve, or find out.
Then, walk through your project in more detail: What are you going to do first, second, third ... why specifically are you going to do that rather than something else, and what specifically you hope to learn about what from doing that. You want to link what you're doing with what you expect of that doing. In this section, address
What ideas or theory or other examples of blogs or wikis are you grounding your project in? For instance, if you're looking at setting up a community wiki, what other wikis have you looked at and what are you drawing on from them? What other blogs have you looked at? What are you borrowing, what will you be doing differently?
Describe how will the blog or wiki be designed. What will be in the blogroll, if you use one? What else on the side bar? If a wiki, how do you expect to organize things?
What will you write about, what will the space contain? How will you use images if you use them?
In the last paragraph of this section, mention how you envision your project report: Will it be a wiki essay or something on your blog? What will you deal with in this report - as specifically as you can imagine it now. You can change your mind on this one, but start thinking about it now. You'll be making a brief in-class presentation along with your report.
Grad Students: Readings Your project report (at the end of the project) should include background reading or theory based on readings for the course and your own reading. So, include a section on outside reading you'll be doing for your project. The reading can be web-based or print; and can be in great part looking at other blogs and / or wikis. A preliminary bibliography is best, but you can also list or talk about the kinds of readings / sites you're thinking of looking at and how you see them tying in with what you're doing in the project. You might start with readings and sites on the BlogReadingsForCourse, WikiReadingsForCourse, or HypertextReadingsForCourse, as appropriate.
For instance, if you plan on keeping a blog, how often will you post? How long do you expect those posts to be? If you're working with others on a collective blog, how will you distribute the tasks? What will each person contribute? Who will be responsible for what?
Or if you're building a wiki, about how many nodes do you expect it to grow to? How often will you add material?
Set your contract. Here are some guidelines.
- 100 pts (about a C) for keeping a general, non-topic specific blog three or four times a week, with entires of about 200 - 500 words/day. For a wiki, sort of a freeform, general notebook or collaboration of the same frequency and length.
- 150 pts (B) for a focused blog, including searching for subjects to blog on (online or off), with links to online material when appropriate, 3 - 4 times a week, about 500 words or so a day. For a wiki, focused, well-linked.
- 250 pts (A) for a focused, extensive blog. Not just blogging 3 - 4 times a week, but some entries becoming 500 - 750 - 1000 word essays... For a wiki, focused, well-linked, but more developed, more richly linked, more organized than the 150 points.
Contracts are set for the number of points: 100 / 150 / 250.
You can earn more points than you contract for if you end up going beyond what you originally planned on. On the other hand, if you fall short on the contract, you may receive fewer points. (I'm hoping for the former.)
The points accumulate by week. A late or missing means no points for that week. Your final write-up adds up to 50 points to the mix.
There are other projects to look at in the archives at PastParticipants.
See also BlogSites for examples | ExampleWikis and WikiAsCulture for examples | CourseSyllabus
==== Title of project ==== ==== Your email address and URL for the project ==== ==== Executive description ==== ==== Narrative ==== The narrative is detailed description of the project. ==== Weekly Reports ==== ==== Contract for Grade ====