Magnus Opus/Resume & Cover Resources

  • Final Project HELP HERE

    See this page for how to complete the course; due dates and directions for turning in your last assignments.

  • FINAL PROJECT PROPOSAL: Magnus Opus and Exigence

    To be POSTED ON Friday,  April 20. no later than midnight, yet, I suggest you do this in class. Topic and Document Proposal  USE YOUR INITIALS.  You do not need to put your email here. I will reply as a comment to the post.


    Working Title (in the subject line of post).  




    DOCUMENT TYPE (please think about this carefully; not a term paper. In class we will keep talking about options.) 

  • FINAL PROJECT: Rev. Bib. and audience worksheet

    Part 1) Consider their ethos with the annotation process. To Be Discussed on Wednesday, April 25, this Annotated Bibliography (7-10 sources; due in hard copy on Friday or Monday (4/27 or 4/30)

    Part 2) Complete the audience analysis worksheet in this sheet in class, Friday, April 27,  hard copy to be provided by me/or you can use this MS Word document linked above)


  • FINAL PROJECT:Structures and Arguments

    Write a structure, shape, and content MAP for your document. Arrange information in terms of logos, pathos, and ethos categories. Be prepared to post by Wednesday, May 4. I suggest strongly that you finish and post this digital entry in class.).

    Elements for this assignment, first, the shape of the document:  Is this a lemon?  A pear? Is your document a divided document? Two parts?  Three parts?  Is your document a series of documents, like a packet ?(or Google Drive folder, with separate pages).


    • hook audience with one of the beginning strategies
    • what definitions or descriptions will your audience need BEFORE the main evidence and take-aways of your document?

    Middle: Divide the main part of our document into three or four points that either inform your audience of content they need or prepare them for advice or recomendation (adjust if your document is a packet, but the idea of three or four is still a useful strategy).

    • often, we provide the stases of elaborated definition/description or practical causality in this section

    End:  Is your document primarily 

    • information for the reader to help them more generally in work or tasks: WHAT TO KNOW
    • information for the reader to complete tasks:  HOW TO DO
    • information for the reader to decide, with you advising or recommending: WHAT TO DO

    Do you have overlap?  Think Venn Diagram.


    ADDITIONAL STRUCTURE (beyond begining, middle, end):  1) Tell a Story and 2) Illustrate a Concept 3) Support a User 4) Convince a Skeptic 5) Divide Complex Information into Reasonable Parts 5) Provide Joy

    GOAL:  Especially at the END, is your reader now clear about your goal? 
    • to inform?  
    • to persuade/advise?  
    • to support in tasks?
  • FINAL PROJECT: Abstract and Reader's Reponse

    By midnight, on Monday, May 7, post this  Abstract and Reader's Response (finish and post this digital entry by midnight).

    Write an abstract of your work, in 250 words or less.  Then write a Reader's Response paragraph from the point of view of a difficult-to-reach-reader.  This means you will address at least one argument against what you write about. Another way to think of this is to address the objection of a difficult or bored or hostile reader.

    For the abstract, consider these options for your voice:

    • write in first person, if you are writing for a lay audience
    • write in third person if you are writing for a technical audience. 

    For the Reader's Reponse, write in first person as if you were inside the head of the reader. 

    See my example on The Science of Happiness.