start: http://twinery.org/2
- create new story, name it
- add a sentence or two to first box, try dragging around
- click test button at bottom right, should have sentence
- create a new room by typing the name of the room like this:
[[Name of room]] - notice new room appeared with arrow once editor has been exited, double click it, add new content
- add link to old room, by typing in title of old room with double square brackets, will autocomplete
- press test again to try clicking the links to go between rooms
- maybe we don't want the name of room to be what shows up, so we can change the link to look like so
[[Turn on light->Name of room]] - format is
Text to display on link->Name of room. note no spaces in between the text to display and name of room, just the arrow-> - add some formatted text, like bold or italics (same as markdown,
*italics*, **bold**). full documentation: http://twine2.neocities.org/ (kinda split up between formatting and vars and macros... we should add a quick reference) - add a macro. explain what a macro is, and how it's a comp sci concept (nearly equivalent to a function) and all that. use a simple one like
The time is (current-time:).full documentation: http://twine2.neocities.org/ - press test again, and turn on the debug view. will show where the macro is in the story, and also how the links are a macro. we just used a shorthand for the link macro. explain all that
- click on the home button in the bottom left to go back to the dashboard. notice how it's auto-saved and stuff. mention it might not save when you log out of your computer, and that when they're gonna log out, they should save it somewhere safe.
- click on the gear icon on the story, and choose publish to file. tell student to move the downloaded file somewhere where it'll be safe, for later use. student can also open the file by double clicking to see their story.
- click on import from file to import the file they downloaded it if they want to edit their story on a later date.
- tell student to keep adding to their story, and create something fun. experiment with different macros and formatting. recommend to work in groups. emphasize that nothing can permanently break, and that if something does break, they can just delete the line of code they added that made it break.