Share Your Twine Story on Google Sites

on

 Sometimes, when I find things difficult to find online, I make a post so that they're easier to find. 

And one question that my students have over and over again is how to share their Twine stories. I've found the availability of good tutorials or Q&As on this subject to be rather difficult to locate. 

There are many ways to share your Twine html file, including in an online cloud that allows for sharing like OneDrive or Google Drive, etc. Of course, that means people would still need to download the file and sometimes sites like OneDrive expire the link for various reasons. 

The easiest thing to do is to embed the code into a webpage. Google Sites is one of the easiest sites for beginners to use, and if your main goal is to just get your story on a link, then here you are:

  1. Create a new Google Site. Choose a blank template.
  2. Once in your editor, go to Pages. Click the Big Plus Sign at the bottom of the column, and this will ask what kind of new page you want to create. Choose "Full Page Embed."
  3. This will create a new page and ask you to either put a link to get code from or to copy and paste the code yourself. There are two ways to get the code from your game/story easily. The first is to open the HTML file in a browser, then right click the webpage. Choose "view source code." Then select all and copy, then paste into the Google Sites page. The second option, is to open your html file in a Text Editor instead of a browser, and copy from there. 
  4. From there, just design the top navigation or other Google Site pages as you want to.

You can also of course embed the HTML code into one block on a page and design other stuff around the story if you want to also. 

You can also put the html file into Drive and select to import from the file directly. This of course requires the extra step of uploading the file to Drive, but that isn't  a big deal. 

You can then publish your Google Site and share its link. You can also put other stories on other pages and add a navigation bar at the top between them. Just make sure your design is clear enough that readers don't mistake the top bar as part of the story itself. 

 I haven't seen any issues doing it this way. It's fast and easy. There may be issues with stories with additional stored assets. But if I'm overlooking something, let me know in the comments. 

 

Comments

Post a Comment