Cheap and Dirty Websites · Google Docs · GitHub Pages · itch.io · QR Codes

Cheap and Dirty Websites (v2)

The simplest route from a document to a shareable website: start with a Google Doc, publish it to the web or export HTML, then host it on GitHub Pages or itch.io

Why This Workshop Exists

This workshop is about getting something online quickly, cheaply, and in a way students can understand. We treat a website as two problems:

Cheap and dirty websites use tools you already have — Google Docs and a free GitHub account — to solve both problems with as little friction as possible.

Route 1 — Publish a Google Doc to the Web

Fastest route, minimal control. Good for class notes, instructions, and zine-like documents that don’t need custom layout.

Pros: extremely easy, hosting is handled by Google, good for quick workshop outputs.
Cons: limited format control, Google headers/footers, hard to customize the look.

Route 2 — Export HTML and Host with GitHub Pages

Simple but more control. Good when you want a small “real website” that behaves like a static page and can be edited later.

Step 2.1 — Export HTML from Google Docs

The exported HTML is messy under the hood, but it works and can be tweaked later.

Step 2.2 — Create a GitHub Pages Site

GitHub will give you a URL of the form username.github.io. Your page will be visible at:
username.github.io/your-repository-name/index.html (or whatever file name you used).

Example: jonathaniscarroll.github.io/test-website/01-main.html

Shortcut for classes. Prepare a simple HTML file in advance, upload it to a GitHub repo, and let students replace the text and images inside that file rather than dealing with export or hosting themselves.

Route 3 — Docs + Apps Script as a Web App (Optional)

For interactive content (chatroom, archives, spreadsheet-driven sites), you can turn a Google Doc or Sheet into a web app using Apps Script. This is more technical, but powerful.

Pros: interactive content, hosting covered by Google.
Cons: more technical, single-page feel, URLs are cumbersome.

Hosting the Twine Game You Made

A finished Twine story is just one HTML file plus the image files it points to, so it is already a cheap and dirty website. The easiest route is Route 2 above, with a Twine story in place of the Google Doc export. A second route, itch.io, is described further down.

Easiest: GitHub Pages

1. Publish from Twine. In Twine, open your story and choose Build → Publish to File. You get one playable .html file.

2. Name it. Rename the file to index.html so the site address does not need a file name on the end.

3. Gather the images. Keep your character frames and backgrounds in an images folder beside index.html. The paths in your story (for example images/char-idle-1.png) must match the folder exactly, including capital letters.

4. Upload both. In your GitHub repository choose Code → Upload files, drag in index.html and the whole images folder, and click Commit changes.

5. Switch on Pages. Go to Settings → Pages, choose main under Branch, and save.

6. Test and share. After a minute or two the game is at username.github.io/your-repository-name/. Open it on a phone, then turn the address into a QR code and put it on the page or print it.

If images are missing online but fine on your computer, check three things: the folder was uploaded, the file names match exactly (Char-Idle-1.png is not char-idle-1.png), and the story uses relative paths such as images/... rather than a path on your own computer.

Can I use Google Drive instead?

Not as a straightforward host. Google Drive does not serve a folder of files as a website, so a Drive link to your Twine file will show code or offer a download rather than run the game. There are two partial options:

For the workshop, teach GitHub Pages as the main route and treat Apps Script as the optional “stay inside Google” route.

Route 4 — Upload a Twine or HTML Project to itch.io

itch.io is a free home for games and interactive art. It runs HTML projects directly in the browser on a project page of their own, with a cover image, description and screenshots, and it recognises Twine stories automatically. Use it when you want a Twine game to look like a published work, and to be found by people who play interactive fiction. The same steps work for any small HTML, CSS and JavaScript project, such as a page you made in Route 2.

GitHub Pages or itch.io? GitHub Pages gives you a plain web address you fully control, which is good for a site that will keep changing. itch.io gives you a game page with a play button, a cover and an audience, which is good for a finished piece. You can use both: the same files work on either.

What you need first

Step 1: Decide: one file or a ZIP

Your projectWhat to upload
One .html file with no separate pictures (text-only Twine, or pictures embedded in the file)The .html file itself, unzipped. It cannot refer to any other file you upload.
An index.html plus an images folder, sound or other filesA ZIP file. A ZIP is the only archive type itch.io accepts; .rar, .7z and .tar.gz do not work, and uploading files one at a time does not work either.

Step 2: Prepare the files

1. Name the entry file. The ZIP must contain a file called index.html. That is what players see first.

2. Use relative paths. Write images/nora-happy.png, never /images/nora-happy.png or a path on your own computer. A path starting with a slash points outside your project on itch.io and fails.

3. Match capitals exactly. itch.io’s server is case-sensitive, so a file called Hello.png will not load as hello.png. A project that works on your Mac or Windows computer can fail after upload for this reason alone.

4. Load other things over HTTPS. If the project fetches anything from another website, that address must start with https://.

Step 3: Make the ZIP

  1. Open your project folder so you can see index.html and the images folder.
  2. Select both items inside the folder, not the folder that holds them. This puts index.html at the top level of the ZIP, where itch.io looks for it.
  3. Mac: right-click the selection and choose Compress. Windows: right-click and choose Send to → Compressed (zipped) folder.
  4. Rename the result to something like my-twine-game.zip.
  5. Check it: open the ZIP and look for index.html straight away, without opening another folder first.

Step 4: Create the project page

1. Start a new project. Log in, open your dashboard from the menu in the top right, and choose Create new project.

2. Fill in the basics. Enter a title, check the project URL (it becomes yourname.itch.io/your-title), and write a short description that appears when the game is shared.

3. Set the kind. Under Kind of project, choose HTML.

4. Upload the file. Under Uploads, choose Upload files and select your ZIP (or your single .html). When it has finished, tick This file will be played in the browser.

Step 5: Set the embed options

After you upload a playable file, an Embed options section appears. These settings decide how the game sits on the page.

OptionWhat to choose for a Twine game
Launch modeClick to launch in fullscreen is the easiest choice, since the game then fits any screen and you do not have to give sizes. Or choose Embed in page and enter a viewport size, for example 960 × 640 pixels.
Click to PlayLeave it on. The game starts when the player clicks, which keeps the page quick to open.
Fullscreen buttonTick it if you used Embed in page.
ScrollbarsTick it if a passage can run longer than the viewport. They are hidden by default, so a long passage could otherwise be cut off.
Mobile FriendlyTick it once you have checked the game in a phone browser. On phones itch.io then always uses fullscreen launch.

A Twine story with a background picture and a character picture, like the class story, adapts to any size, so fullscreen launch is the safest option.

Step 6: Dress the page and publish

Step 7: Test it like a player

  1. Open the page, click the play button, and click through every path of the story.
  2. Check that every background and character picture shows, and that animated frames still play.
  3. Open the page on a phone and try the fullscreen launch.
  4. If pictures are missing, open the browser console (usually F12, then Console). A line such as ERR_ABORTED 403 means a file name, capital letter or folder path does not match.

Updating the game later

Make the fixes, build a new ZIP, open the project’s Edit project page, and upload it. Delete the old file once the new one is in place, and tick the browser-play box on the new file. The page address stays the same.

Limits to know about

Common itch.io problems

ProblemLikely cause and fix
Nothing to play, or only a download linkThe kind is not HTML, or the box This file will be played in the browser is not ticked.
Blank page or “index.html not found”index.html is not at the top level of the ZIP. Zip the contents of the folder, not the folder.
Works on your computer, pictures missing on itch.ioCapital letters differ from the file names, or the path starts with /. Use exact names and paths such as images/nora-happy.png.
Console shows 403The request points to a folder, or to a file that is not in the ZIP. Check each path.
Text is cut offTurn on Scrollbars in the embed options, or use fullscreen launch.
Wrong or old version showsThe old ZIP is still attached. Delete it, upload the new one, and reload the page.
Upload refusedThe file is not a ZIP (for example .rar), or it breaks the limits above.

itch.io’s own guide is at itch.io/docs/creators/html5. Menu names may change over time, so look for the same word if one has moved.

QR Codes for Sharing

Whether you use a published Google Doc, a GitHub Pages URL or an itch.io page, QR codes make sharing easier in the room:

Templates and Examples

The original Cheap and Dirty Websites workbook lives here:

Position in the Handmade Techniques Day

In the full session, Cheap and Dirty Websites comes second: