I'm working on a new book lately, and I've been trying to settle on the right workflow. 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 wrote my first book, and a lot of old documentation in SGML DocBook, and then later converted it to XML DocBook...it had many benefit…
Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
11–20 of 39 posts
Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#12This is perhaps a general question about 3rd-party auth, but how am I supposed to trust an app like this when I click "log in with google/github/etc"? I'm simply shown a new pane within the same application that could easily be a phishing attack. There's no way to verify who the hell I'm sending my user/pass to. Is there some way for native apps to launch my preferred default browser to do this task? (Note: this is b…
I see this happening over and over again on my phone. Especially with Facebook logins.
Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#13Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#14Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#15Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#16I'm working on a new book lately, and I've been trying to settle on the right workflow. 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 wrote my first book, and a lot of old documentation in SGML DocBook, and then later converted it to XML DocBook...it had many benefit…
Also, I haven't written any books, but I wonder if Markdown is the best choice for a canonical format. The syntax is lightweight but also limited. For example, it doesn't support tables, and doesn't differentiate between source code (which should be syntax highlighted) and literal text (which shouldn't). You could define your own extensions, of course, but that breaks the compatibility feature. I think reStructuredText (for example) might be a better choice, although Emacs' Org-mode is my personal favorite document format. I suppose that in the end, whichever's most comfortable for the author to write in is the best.
edit: I should mention that this is in reference to a technical book because I've been thinking about technical writing lately. It just occurred to me that you could be writing the type of book that doesn't need tables or source code, in which case Markdown is probably perfect.
Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#17Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#18Neat editor, I've long felt there's room for a markdown editor geared to writing 'real' documents - been working with Atom which covers a lot of ground with the right plugin - I even wrote a plugin that does something similar to their inline math rendering: https://atom.io/packages/preview-inline
If you're on mac, I'd give ulysses a try – it's pay to play — but well executed.
Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#19Earlier quoted context omitted.
If you're on mac, I'd give ulysses a try – it's pay to play — but well executed.
Agreed! I just wish tables were supported. I actually have to export it to a .docx and then add the tables :/. I asked them a while back and they said they weren't planning on supporting tables any time soon.
Re: Show HN: GitBook Editor Beta – Markdown WYSIWYG, TeX
#20Rust by Example[0] (and possibly the Rust Book[1]) uses gitbook, for those curious as to how a language reference may look like with GitBook. [0]: http://rustbyexample.com [1]: https://doc.rust-lang.org/book/