Sunday, July 31, 2016

Week 6 Explanation

This week’s blog topic asks you to discuss and explain archetypes and classical allusions found in your summer reading books. Look up these terms to get a better idea of what they mean. Check out my example to see a possible way to address this topic. You can talk about several archetypes or allusions, or just focus on one and explain your take on its use in one or more summer reading books. The books can be ones you’ve read already or a new one you haven’t written about yet. Answer questions like: What do these archetypes and allusions add to the story? Why are they used? Does it make sense? Why is the archetype or allusion important? How does the author address the archetype or allusion?


You CAN use first-person POV if you’d like.

When you write for this assignment (and most of the others) keep the following general guidelines and possibilities in mind: 1). DO NOT SUMMARIZE. I don’t care if I haven’t read your book; I’m not asking for the plot. 2). Pay attention to your content, ideas, organization, using quotes, and citation as you structure your post. 3). Certainly mention the book title (use italics to set it off) and author. The title of the post should contain the title of the book and your last name, like in the example that follows these directions 4). Deal with other issues that are interesting, novel, and intellectual yet still relate to the general topic of the post.

Try to have a good time. Remember internet safety protocols: don’t use your entire name or give away identifying information. You should probably change your display name if you’re using your real name. Be tactful and don’t disparage anyone. You are graded on the quality of thought and expression in your post, its length (between 700 - 1000 words), and on using quoted material properly (if you use any). I suggest writing the post in a word processing program and then pasting it into the post window. Contact me if you have any questions and I’ll answer ASAP. The following example is not a strict template of what you should do but only a possibility, and a poor one at that. Off we go then…

No comments: