+ Page "Why not markdown?"

[sethwoodworth]

Make a page describing why we're not using markdown.

[samwilson]

Also, "why not ReST"?

[eshellman]

More precisely, we're not focusing our development on a markdown-based toolchain. (or LaTeX, or TEI). I hope we don't do anything that would prevent addition of these in the future. For example, Gitbook has done some nice work on Markdown- we're borrowing ideas and I hope it goes in both directions.

[samwilson]

Ah right. Yes, that sounds sensible.

By the way, is this documentation repo going to be included in the main gitenberg.org site somehow? I'm never very sure how relative links are meant to work within Github.

[sethwoodworth]

Agreed. There are too many high quality books from Distributed Proofreaders in LaTeX, TEI and even ReST to refuse to use them.

One of the benefits of the current travis-ci build system is that we can configure how to create an epub file on a repo-by-repo basis.

[sethwoodworth]

Yes @samwilson This repo is intended to be used on the website. But it hasn't happened yet and I haven't decided how I'm going to implement it.

We could also include everything into a single file and turn it into an ebook!

[samwilson]

Cool! Yeah, I've been wondering if there would be a central build system, or if individual repos could specify their own. If it's Travis, then it's easy to build whatever custom bits need it; that's great!

I'm going to try adding a Travis config to one of the books I'm working on. (Or, maybe the documentation repo itself?)

:-)

[sethwoodworth]

Take a look at Huck Finn's travis file

[samwilson]

Just for interest: Pandoc now supports TEI output. https://github.com/jgm/pandoc/releases/tag/1.17