Ready for contributions: The Tectonic Book!

[efx]

Three cheers to your achieving autopublishing! I think it will help teach new users about the project.

@pkgw

Now the new irony is that our documentation is in Markdown, not TeX, but for the time being my dreams of beautiful HTML output from TeX are just dreams, so we’re being pragmatic.

Version 2 will be texbook.

@pkgw

Another question to consider is which content should go on the website, and which content should go in the book — it’s not obvious to me how to decide that, although a key distinction is that the book is in-repo with the main code, and the website repo is separate. Any thoughts on that?

Great question. Initially I think tutorials, and technical documentation seem best alongside the main source code. Putting the documentation next to the actual code makes it easier to synchronize changes whenever internal implementation details or the CLI interface change.