3 ms·

As a 20+ years Pascal/Delphi lover, this read is too much for beginners. I had no problem going through it in one go, but it did felt a lot of energy was spent

As a 20+ years Pascal/Delphi lover, this read is too much for beginners. I had no problem going through it in one go, but it did felt a lot of energy was spent even by me. Maybe it's better to be split in chapters, giving a potential inquiry mind time to breath. And yes, I do realize it has a left ToC. So maybe instead of one big document with a lot of inline anchors, should be made separate files. Or perhaps both, giving readers the opportunity to choose whichever they like.

oefrha 6y ago
> Or perhaps both, giving readers the opportunity to choose whichever they like. Yeah, good old texinfo-style entirely-on-one-page and one-page-per-node model (as seen on the documentation page of any GNU project, e.g. https://www.gnu.org/software/texinfo/manual/texinfo/ https://www.gnu.org/software/texinfo/manual/texinfo/) is heavily underrated and underutilized in “modern” documentation systems. Want to quickly search for something in the entire manual? Use the one page version. Want to read cover to cover or link to a specific topic? Use the split up version. Btw, this book is apparently written in AsciiDoc and generated by Asciidoctor. There seems to be a multi-page plugin available, although I haven’t tried it myself. https://github.com/owenh000/asciidoctor-multipage https://github.com/owenh000/asciidoctor-multipage https://github.com/asciidoctor/asciidoctor/issues/626 https://github.com/asciidoctor/asciidoctor/issues/626