Writing Technical Books with Pandoc and Markdown
$6.00
Affiliate Disclosure:
SpecMeOut may earn a commission from the links on this site, at no extra cost to you.
Thank you for supporting SpecMeOut.
Product Specs
| Deal Type | |
|---|---|
| Reviews Count | |
| Questions Count | |
| Availability | |
| Stacking Type | |
| License Type | |
| Stacking Maximum | |
| Date Days | |
| Date End | |
| Date Price Valid | |
| Date Published | |
| Date Start | |
| Marketplace | |
| Price Saved Dollar | |
| Price Saved Percent |
Product Description
A template to make it easier to write technical books (especially books with code) with Pandoc and Markdown.
In 2020 I decided to start a new project, a blog.
After a few months of writing about programming, I thought “hey, maybe I should write a book”.
The topic would be a simple and straight forward guide for beginners about the Python programming language.
The book was downloaded over 4,000 times and counting and I have received multiple messages on e-mail and social media of people thanking me for the book.
This is the nice part of the story, but when I started writing the book I had some problems.
I thought: “this is a programming book, it will have code, of course, but how do I format it as painlessly as possible?”.
Some tools were no longer supported by their creators, others had some limitations and then I finally found Pandoc.
It was everything I needed: a free, open-source, markdown compiler with many options, and it was easy to install.
But as with many tools, to make really good and productive use of it takes some time.
My intention with this book is to give you an advantage by learning and using the exact same structure I use to write and publish my books.
Any questions: renan@renanmf.com
