![gitbook editor ofline gitbook editor ofline](https://i0.wp.com/codeless.co/wp-content/uploads/2020/10/Gatsby-Gitbook-Starter.png)
I think I just need to find a good set of vim settings for markdown, or give Atom another try.Īre you familiar with Ghost, the open-source Markdown-based blogging platform? It might suit what you're looking for.Īlso, I haven't written any books, but I wonder if Markdown is the best choice for a canonical format. And, the idea of paying for a text editor, especially one as limited as this one seems to be (though it has some neat tricks), when there are such good/flexible/powerful/free/open editors, seems bizarre. I don't really want anyone else in the workflow until I send it off to an editor or for print publication. A subscription service for a text editor just feels wonky. But, this doesn't look like the right tool for me, at all. In short, I think I need to be working in Markdown. pandoc changes the rules entirely, and markdown seems the most "native" format for pandoc. Final format for publication was a Word doc with extensive templates provided by the publisher.Īll of that was a long time ago, though, and there's a lot more flexibility in where a document can start and end up in various other formats. I wrote my first book, and a lot of old documentation in SGML DocBook, and then later converted it to XML had many benefits, and with a decent vim setup wasn't too hard to work with, and the output options were super flexible. I've been posting the chapters as blog entries, as I complete them, but editing in WordPress leaves a lot to be desired, and I don't really think HTML is the right authoritative source for a book. I'm working on a new book lately, and I've been trying to settle on the right workflow.