As I’ve mentioned in my previous posts, I’m working on a project that illustrates and advocates for non-linear, queer composing as a death-defying act of world-making. To do this in a digital project, I’ve been making my project using Twine, self-described as “an open-source tool for telling interactive, nonlinear stories.” I think most people tend to use Twine to create a kind of “choose your own adventure” story-game. In this way, the platform works perfectly for my project. I want users to click through it and feel like their experience is completely random and different every time they come to the site.
The weird thing about Twine is that it has its own coding language, plus it uses html, css, and javascript. It won’t let me just code using html, but rather I’ve been doing a combination of both html and Twine’s style of coding. So, to get a bunch of overlapping pictures like this:
I have to code it like this:
Plus some css on another page.
I’m not great at coding in the first place– I knew nothing about it until starting this fellowship, so having to both continue to learn the basics of html, css, and javascript, as well as Twine’s formatting is a bit of a chore. To be frank, it took me six hours to get those pictures randomly on the screen and turn them into clickable buttons. Still, I love working with Twine because it offers up a cool way to think about creating a website/story that is random and non-linear in the way that I need it to be. This is what my collection of pages look like right now: 
I’m so excited to keep working and build an even bigger web of pages. Wish me luck!
Leave a Reply