Skip to content

pitt-cdm/visual-rhetoric--jfrank1120

Repository files navigation

Project 2: Visual Rhetorical Collage

Your task in this unit is to make a rhetorical claim through the juxtaposition of images and text. It's kind of a collage, but a collage with an argument to make. In assigning this, I have two main goals for you: (1) to learn how to ethically obtain images and edit them using digital tools, and (2) to explore the affordances of still images as a medium, and especially their ability to direct attention and help make ideas memorable.

As with the sound project, the context for your argument is open: you could be making a social commentary, calling for action, constructing a parody, riffing on a pun, explaining a concept, inviting someone inside, and so on. Whatever you choose, you should consider your audience and what they would find persuasive or interesting, and how you therefore wish to attract and direct their attention.

As you start planning your composition, consider: What ideas do you want help remembering? Or what do you want to persuade others of? Is there something you've noticed that you want to bring to the attention of others? See if any terms or images come to mind when you think of your subject, then work back and forth from image to word and back.

Generative constraints

We can revisit these after we get into the midst of composing, but to get you started:

  • Include at least two images from separate sources.
  • Include at least one word, with a carefully chosen font.
  • Include at least one image or photograph produced (e.g. taken or drawn) by you.
  • Use arrangement, size, color, visual rhythm, and/or contrast to focus viewers' attention.
  • Aim for surprise or metaphorical leap in the elements you bring together.

Deadlines and products

At each stage, unless otherwise specified, upload (push) your materials to your own copy of this assignment repository. I recommend that you save often, using meaningful commit messages; for best results, please keep your filenames clear, lowercase, and space-free (use hyphens or underscores).

If you are using Box, please nevertheless share a link to your Box folder prominently in your GitHub repository.

date what's due expected files
Tues Feb 12 Visual Rhetoric Proposal Thinking in writing about what you'd like to do for this assignment.
  • Post to the appropriate Issue Queue with your proposal, suggesting in prose the idea or appeal you're hoping to make.
  • In the same post, or as a separate file called ASSETS.md, include a prospective assets chart (see Writer/Designer p. 149) naming what images you'll need to obtain.
  • Please also link to your repository in your post.
Thurs Feb 14 Visual Rhetoric Preview An early snapshot of your progress, to get the gears turning. Turn in:
  • A layered GIMP project file (.xcf), showing the arrangement of your images and text so far (need not be a complete argument or collage yet).
  • A static screenshot (.png or .jpg) of your GIMP file in progress (for comparison later to subsequent drafts).
  • A plain text (.txt) or markdown (.md) file, explaining in at least 300 words what you're showing us in this preview. Feel free also to ask questions or lay out next steps for yourself!
  • An updated ASSETS.md file, now with the files you actually recorded or otherwise obtained. As you go, add source documentation for any outside sources – and your permission to use them (e.g. licenses, fair use; see Writer/Designer p. 160-165).
Tues Feb 19 Visual Rhetoric Draft A solid attempt at a complete Visual Rhetorical Argument. Turn in:
  • A layered GIMP project file (.aup), showing the arrangement of your images and any layer effects so far
  • At least one more static screenshot (.png or .jpg) of your GIMP file in progress.
    • Think about what moments are worth remembering as you go: where did you level up, or realize something, or get stuck?
  • An updated README.md file, introducing the Visual Rhetorical Argument to a new audience.
  • An updated ASSETS.md file – or rename it CREDITS.md – including documentation of any outside sources, and your permission to use them (e.g. licenses, fair use); see Writer/Designer p. 160-165.
Sun Feb 24, at 11:59pm Visual Rhetoric Final Draft Include the same components as in the earlier draft, but updated.
Tues Feb 26 Visual Rhetoric Reflection Give a sense of the work you put into your Visual Rhetoric project and whether it accomplishes what you wanted it to. Turn in:
  • at least 500 words describing the work you did
  • at least two screenshots showing your work in progress
  • at least one photograph of a notecard with feedback that you responded to in revising (and please say how)
  • your own assessment of how you met the baseline criteria for the class, as well as aspirational criteria as appropriate
Post your reflections to the course site's Issue queue, to make it easier to embed images. (If you want to then copy the source code into a file in your repo called reflections.md, I won't stop you!)

Releases

No releases published

Packages

No packages published