Another example of what I call “book companion websites” is about a site that creates book companion websites, in addition to the books themselves. The book Lean Publishing is about how to apply a work-style from Internet startups to the process of iterating and releasing a book.
This book explains [the philosophy behind Leanpub](https://leanpub.com/manifesto), from its origin in "[a book is a startup](http://www.newyorker.com/online/blogs/books/2013/03/leanpub-netminds-web-publishing.html)" to the present form. Lean Publishing is the act of publishing an in-progress book using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. This book explains what that all means, where it came from and why it's important...
I’m very interested in this idea, independently from the idea of book companion websites.
After switching to Markdown as my file format of choice for writing, I’ve found, as others have, that my writing has become faster and more frequent after switching to a simpler format. Could the process of creating books benefit similarly from an upgrade?
The “upgrade” goes by many names, such as SubCompact Publishing for example, and a lot of the “philosophy” on the subject is actually marketing copy promoting various web applications, but I do enjoy learning new ways to make things. There are a growing number of interesting parallels being drawn between software development methodologies such as rapid development and more traditional creative process. For an example that doesn’t involve as much focus on software, file formats and applications, the Book Sprint is interesting. It’s much more about how you make the book (quickly, in sprints) than about the tools of the trade.