Consider switching from templates to forks?

[lazerwalker]

#34 is easy to do if users clone this repo as a fork rather than a template. That complicates things: should we tell people to use forks instead?

Pros to forking:

• Individual devs can more easily update their projects to the latest Twine App Builder code
• Git history is a combination of both Twine App Builder's infra code and a dev's game history
• Easier for me to get metrics on usage

Pros to templates:

• Git history is your own
• Developers can't easily see every other public repo using the project

I'm going to sleep on this, but I suspect this means forks are the answer. The primary audience for this tool is people who don't use git; they won't care about commit history.