Twine Project Instructions


A best practice for this project is to clearly outline roles for each group members. Your group has the final say on how to organize the project, but here are some suggested roles. More than one person can serve in a role:

  • Writers: Two or three people responsible for ensuring the story is being written, with extensive input from the rest of the group. Every group member is involved in crafting the story. The writers just are responsible for making sure it’s all written down.
  • Copy Editor: One person who edits the story as written by the writers, and imports the story into the Twine program. If more than one person is doing this job, only one should be in charge of porting the story to Twine.
  • Playtesters: One or two people who will play through the story to ensure it works, bring up any story issues with the group, and debug/fix any technical issues that appear.
  • Coder (OPTIONAL): If the group wants to use HTML, CSS, and JavaScript to add functions such as inventory systems, using sound, and integrating media, one person can be assigned to learn or use skills they already have to add code into the Twine story.


Every group for this assignment has been added to a shared google drive folder (you can find a link to it here on moodle). Navigate to find the folder with your group number.  

  • Create a Google Doc in this folder, and make sure it is shared with your group. This is the document where you will be collaboratively drafting your Twine story.
  • Create two sections of the Google Doc. The first section will be used to brainstorm your project’s story with your group. The second section is where the text of the story will be written.
  • While writing, use [[brackets]] to designate new story choices (links). These will carry over into Twine.
  • Do not use Google Docs to format your text. Use HTML, which will carry over into Twine. Here are some basic examples:
    • <b> – Bold text : <b>example</b> ⇢ example
    • <i> – Italic text : <I>example</I> ⇢ example
  • Below are some resources to add more complexity to your story, using HTML and CSS:


If you need help getting started, don’t forget review the Twine tutorial on the course website and the Twine Guide. Use TA office hours if you still are having trouble.


When ready, your group’s Copy Editor will review the text of the story and import it into Twine.

  • Optional: If applicable, the Coder will integrate HTML, CSS, and/or JavaScript code to add inventory systems, use sound, or integrate media here, if they haven’t been integrated earlier in the project


Once the story is imported, have the Playtesters go through the story a final time, and ensure everything works, and debug/fix any issues that come up (unintentional endless loops). If story issues come up, go back to the larger group to discuss how to resolve them.


Upload the final html draft of your story to google drive, and we will put it on the internets!