Portfolio Project 1

Graph replication + redesign

Overview

In your first portfolio project, you’ll apply what you’ve learned about ggplot2 and design principles to replicate and redesign a published graph. This part of your portfolio consists of three parts:

  1. Replicating an existing graph using ggplot2. Depending on the graph you choose, this may require some creativity in recreating data.
  2. Using design principles from class, re-design the original graph to be better. This should include, at minimum, a change to the geometry or aesthetic layer.
  3. A written summary (no more than 1 printed page) including (1) an evaluation of the original graph and (2) reasoning for your design choices in improving the graph. This should include references to readings and discussions from class.

Options and Examples

The list below includes some good places to get started finding a graph. You do not have to choose a graph from one of these sources. It can be hard to find associated data with some published graphs, so don’t spend too much time trying to find data for a specific graph before moving on.

Submission

Your submission should include two visualizations (replication and improvement), a written overview of your work, and all associated code. You should work in a rmarkdown or quarto file. Your knitted/rendered file can be either pdf or html. I will distribute GitHub skeleton repos that you should fill in as you work. You should commit your final code and output file to your repo and link your repo to gradescope to submit.

Rubric

A successful project will:

    • Aesthetics should faithfully represent the representation of the underlying data
    • Very few grammatical mistakes, spelling mistakes, or typos
    • Appropriate labels and font sizes
    • A readable theme
    • The rendered document does not contain any unnecessary content (package loading messages, warnings, etc.)

An excellent project will meet all of the requirements for a successful project, plus

    • All changes to aesthetics, geometries, etc. should be faithful representations of the underlying data (e.g. changes for the sake of making a change don’t count!)

For this portfolio project, you may work individually or in pairs. If you choose to work in a pair, let me know by Friday of Week 3. Both partners should have a record of committing and pushing to the repo.

FAQ

If you have any questions, please post them to the #portfolio-projects channel on slack.