My company just published our first programming book, jQuery Plugin Development In 30 Minutes. I worked with the author to establish a workflow that leveraged GitHub and markdown, but at the end of the day the material had to be brought into Scrivener for the final production steps.
FWIW, Scrivener has limited markdown support that let me bring in the code blocks and terms that are formatted in the Scrivener editing window. But getting text formatted as code to compile properly to various versions (PDF, epub, mobi, etc.) took some work -- specfically I had to freeze the formatting for every block and term. It was a pain, but the final product turned out well.
The only other thing I would like to add is I wish there were a way to get the Scrivener manuscript back into markdown and Git, for future revisions. Anyone have ideas on how to handle that?
Comments
My company just published our first programming book, jQuery Plugin Development In 30 Minutes. I worked with the author to establish a workflow that leveraged GitHub and markdown, but at the end of the day the material had to be brought into Scrivener for the final production steps.
FWIW, Scrivener has limited markdown support that let me bring in the code blocks and terms that are formatted in the Scrivener editing window. But getting text formatted as code to compile properly to various versions (PDF, epub, mobi, etc.) took some work -- specfically I had to freeze the formatting for every block and term. It was a pain, but the final product turned out well.
The only other thing I would like to add is I wish there were a way to get the Scrivener manuscript back into markdown and Git, for future revisions. Anyone have ideas on how to handle that?