How should we format the game text?

@haileycoop has proposed using gitbook to be able to render the game text into a book. I agree this would be a nice feature to have.

@kas proposed that we could collaborate and host content on git-ssb, then use gitbook later to do the conversion process for us.

I'm not familiar with the format they expect, but if we can find a process which is comfortable outside their platform while still being compatible, I think that would be ideal.

Otherwise, we've discussed using markdown headers for Periods, and other markup for Events and Scenes. My initial thought was to use nested lists, but headers are probably a more attractive and readable format.

I agree with using markdown headers or lists. I guess I'm leaning towards headers so that we can include descriptions of each card (the part that would normally be vocalised in-person) and still have good visual organisation. We can always revert to lists

GitBook has an editor. I haven't installed that one yet (and I'm not sure I will), but installing it and make a few faux chapters, sections, etc. should make it possible to reverse engineer their document structure.

It seems that you cannot clone a GitBook book directly from GitBook, but if we can find a book that has been imported from Github, we may be able to take a look at the format that way.

In my opinion, each game should have its own git repo that holds all the files relevant to that particular game.

Maybe we can create a reference file for a style guide, and link to it from the readme?

I'm ok to use this repo, since we only have the one game so far, but if you create another repo I'll use that one. If you do, please ping me about it so I don't miss it!

I've used gitbook quite a bit - it's really just markdown files which the cli client understands with gitbook serve - checkout https://github.com/enspiral/handbook for an example

Hey team, now that we have some content, it seems like we need to make a choice on how we store content.

I feel less qualified to make this call but my thoughts are:

• go with @kas's basic template as a starting point
• start a fresh repo for each game (I'm less sure about this, but it would be nice to have the issues clearly separated between rules/workflow and between a particular game)

But I'll ultimately roll with any choice

I vote for a fresh repo for each game, keeping the microscope-ssb repo for our meta discussions and ammendments to the rulebook.

We could have each game as a separate branch in a common repo that holds all games, but eventually we will eff it up and commit stuff to other branches than we intended to.

I just gathered our title and bookend history into a file based off of the template @kas suggested.

:+1: to move the content into a new repo once it's ready.