Course Participation
Course participation will occur primarily through class discussions in Zoom and the course instance of Slack. “Participation” is a broad category of activities that include but are not limited to constructively speaking up or using chat in videoconferencing sessions; discussing readings and technical assignments in Slack; bringing outside readings and knowledge into Slack; and seeking technical support and working with classmates to problem-solve in the #tech-support Slack channel.
Weekly “How Are Things Going?” Assignments
Every Monday, students will create and post a meme (using a site like Imgflip) or post a gif with textual clarification (try searching Giphy) to the class Slack. The meme/gif should either speak to something they learned/did in the past week or to how they are currently feeling about the course. These memes and gifs should be G, PG, or PG-13 rated. If you have any question about the appropriateness of a meme/gif, please DM it to before posting.
Skill-Building Mini Assignments
When you are ready to submit a mini assignment, you should post to the #mini-assignments channel in Slack. Alternatively, you may connect your repository to the Slack channel directly (in which case Slack will post about all commits/issues activity) using the command “/github subscribe owner/repo”
The three required mini assignments (1, 2, and 8) have stars after their due dates. Remember that these are final due dates, with the expectation that each assignment may need to go through a round or two of revision first, and don’t wait until the last minute to submit!
Speaking of last minutes, the literal last minute to submit is 11:59pm on each due date, unless specifically noted otherwise.
- initialize a GitHub repository with the name “username.github.io” where “username” is your GitHub username; include a index.html file containing the text “hello world” – due October 11*
- create a text-only Twine story with at least 15 passages, export it as index.html, and commit the resulting file to your GitHub repository – due October 11*
- update your Twine story with multimedia (images, audio, and/or video) in at least 5 passages, export it as index.html, and commit the file changes to your GitHub repository – due November 7
- update your Twine story with conditionals in at least 5 passages, export it as index.html, and commit the file changes to your GitHub repository – due November 7
- update your Twine story with variables in at least 5 passages, export it as index.html, and commit the file changes to your GitHub repository – due November 14
- update your Twine story with input in at least 5 passages, export it as index.html, and commit the file changes to your GitHub repository – due November 14
- update your Twine story by changing colors and stylizing the text throughout, export it as index.html, and commit the file changes to your GitHub repository – due November 21, 2022
- create a readme.md file to explain the final contents of your GitHub repository – due November 21*
Final Project
Final projects will be done in small teams and have four components, with three interim deadlines before the final deadline. You will have access to the course Slack for coordination and can also use GitHub issues or projects. I can supply access to a Basecamp instance on request.
- Abstract (one paragraph on expected topic/narrative) – due October 3
- Annotated bibliography (you don’t need to have read everything yet!) – due October 17
- Storyboard (narrative outline and planned division of responsibilities) – due October 31
- Narrative (published Twine story)* – due Friday, December 2
*NOTE: to publish your final Twine story, one of your teammates will need to set it up as index.html in their username.github.io repository – please rename the index.html file from the mini-assignments to “mini-assignments.html” so that I can continue to easily have access to it
Performance Analysis
- Final performance analysis – due by the University-scheduled final exam slot, Monday, December 12, no later than 7:15pm
