3 ms·
Have you consider making the "handbook" available as a single file, i.e. a PDF containing the site contents? Some folk find it easier to scroll through that wa
by 0ct4via 3y ago
Have you consider making the "handbook" available as a single file, i.e. a PDF containing the site contents?
Some folk find it easier to scroll through that way (it can still support header links, etc.), rather than having to click through sections of the site as required :)
- swampthing 3y agoThat is on our list of TODO items! We were thinking more along the lines of ebook formats though, like Kindle and ePub. Would you prefer a PDF instead?
- nazzacodes 3y agoyeah I think pdf should be the priority given the audience.
- swampthing 3y agoNoted!
- 0ct4via 3y agoBit weird for you to answer a question that wasn't aimed at you... could've easily replied to my comment, or given me time to answer the question that was directed at me... ¯\_(ツ)_/¯
- 0ct4via 3y agoAs the parent you were asking, yes, I'd prefer a PDF - it's accessible, easy to generate and distribute, and ebook readers can handle them fine without you having to deal with typesetting for multiple formats.
- swampthing 3y agoThanks, makes complete sense :) We'll work on that!
- CalChris 3y agoePub. Definitely ePub (but really, why not both?). I have a million PDFs but for reading a book, ePub on either a Kindle or iPad is much more pleasant. I can read a PDF on the iPad or Kindle. But nothing beats reading something properly rendered for ePub: read, read, read, swipe left. That said, for long ass manuals (the 5,062 page Intel® 64 and IA-32 Architectures Software Developer’s Manual comes to mind) then PDF. Also for published papers. But for books, ePub. For example, the Pro Git book is available in ePub, PDF and mobi. It is regularly updated. https://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2
- swampthing 3y agoYea, I have the same preferences as you :) We’ll try and do both!