Lives in Transit: tutorial metagame / writers' docs
@martin.dusinberre and I have been hard at work on creating a LiT game that helps you learn to make LiT games.
It's hosted on GitHub, but you can submit pull requests (merge requests) just as you would on GitLab. You can also request maintainer status if you want to push to master.
The master is automatically published as the LiT Tutorial game at http://marugoto.s3it.uzh.ch/ . Feel free to have a look at this work in progress, it's supposed to be(come) a user friendly introduction to building games.
If for one of your assignments, you want to create a game, you can perhaps fork https://github.com/uzh/lit-tutorial, or https://github.com/uzh/lit-functional, which has more features and fewer explanations, and start developing your own game from there. Give me a link to it and I'll put it on the test system for you, and you can just push to GitHub to see your updates happen every 15 minutes. You could also, as part of your homework/project, contribute to a tutorial game, as this still demonstrates the key competencies we're looking for (git+key issues in digital history)
We'd also benefit from feedback on what needs to go into such our tutorial, as the tool is feature-rich and not fully documented. If you play the demo at livesintransit.org, there may be functionality there that you can't figure out how ti implement on your own. And please note, it's sometimes hard for those who have spent a lot of time around the project to know which bits are hard to understand, so feedback here, or on those repositories, would be just dandy.
Please let us know here if you do plan to produce a game, and we can help get you a spot on the test system, and make sure you have all you need to start writing game content! @daniel.mcdonald for deployment issues, @martin.dusinberre for JSON syntax questions, and @leyla.feiner for game theory is probably the best division of expertise!
If you do plan to develop a game on the platform, you'll have to speak up here, as if nobody is going to do it we'll not invest so much time in user documentation for the time being, and then nobody wins. So please do speak up@