4 ms·
We did the same for our book about Groovy language. Our Jenkins-based build was: - checking markdown for grammar errors - transforming the markdown into doc f
by koevet 12y ago
We did the same for our book about Groovy language. Our Jenkins-based build was:
- checking markdown for grammar errors
- transforming the markdown into doc files, required by the publisher (Packt), with all the Word formatting applied
- compile the Groovy code in the examples and verify the code with a Linter
- stunthamsterio 12y agoI've written a book for Packt, and I'm in the middle of another - I'd kill for a Markdown converter for their Word format. Any chance you've open sourced it?
- koevet 12y agodrop me an email - contact details in my profile