But I also like that they have an online editor, a platform for publishing, and have done some good work to make the toolset accessible to a wide audience, not just those of us who choose to write articles in Vim. As someone who wrote a small book in Markdown, using a Git repository, of course, I'm likely to feel positive toward GitBook. Since I am going to be a little negative in parts, let me start by saying I love the concept of GitBook. I strongly considered not writing about my experience, or writing about it in a generic way that didn't explicitly reference the tool, but I concluded that there are enough positives from my experience that I can write something balanced, and the negative parts of my opinions might have broader applicability. Unfortunately, after exploring it, it ended up not being usable for my particular case. The latter item I think is very important for documents that are built iteratively, over time, as otherwise it gets difficult to see and review changes.įor this reason, I was really excited when I saw that GitBook has an editor that is cross-platform and provides both the items I mentioned above. Second, a "project" organization concept (to gently ease people who are used to editing a document into editing multiple individual files that are assembled). I have been looking for two main features: first, word-processor-like behavior with Markdown (to simplify adoption for new users).
In my effort to convert all of my documents to Markdown, I have been looking for a tool that would allow the use of Markdown for larger technical documents (the kind of thing traditionally done in Microsoft Word).
0 kommentar(er)
