Skip to content →

WRIT 3152 | Week Two

Readings and activities for the week; this link posted to Discord in #announcements.

In class . . .

We’ll be building some practical definitions of the following terms for use in this week’s activity.

Community

Social media

Platform specific

Stakeholders

Sources

Public good

Digital community

Our work this semester will interact with communities that all into the following categories: non-profit organizations, academic projects, and fan/fandom communities. We will work towards common definitions/understandings of the above terms so that we can study these communities with shared language and priorities.

Our reading for this week:

Read the “Introduction” to Digital Community Engagement by Wingo, Heppler, and Schadewald

Activity for this week:

Sign up for one of the 7 prompts in the #activities channel for this week. Each student chooses a platform specific digital community (as defined in class) that fits the category defined in their thread. Create a shared document (One Drive, Google Doc, or PDF) that includes:

(The phrase “with annotations” below means that for each artifact or source, you should include 1-3 sentence annotation that summarizes the source and explains its importance, relevance, or reason for inclusion.)

  • a description of the community (3 sentences)
  • a list of five artifacts (social media posts from community members), with annotations
  • a list of three sources important to the community (academic, journalistic, “other”), with annotations
  • an analysis of the ways in which people communicate within that community (3 sentences)
  • connection to the Rhetoric UnTextbook reading from week one (3 sentences)
  • connection to the Digital Community Engagement, “Introduction” reading above (3 sentences)

Updated: Post that to the channel by Sunday, 8/25.

Be on the lookout for the Weeks Three and Four posts that will be published by Friday, 8/23, as they will describe work that begins from Friday.

Published in writ3152

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php