1. 29
  1. 8

    hi there, i’m one of the authors of this book

    the book was originally set to be published by a big tech publisher, but they backed out so we are releasing the book for free on the web and we are going to try to self-publish it

    we are in the process of re-writing the book with a bit more of a conceptual bend than what the publisher wanted, and we are happy with how it is turning out. It is a work in progress, and there are incomplete sections and some repetitive areas, but the structure is about where we want it and much of the content is finished

    the book covers hypermedia in general, then htmx for hypermedia-driven web applications, then Hyperview for hypermedia-driven mobile applications

    hope people find it useful and interesting

    1. 3

      This explanation of the usefulness of hx-boost is something that had never occurred to me, and I’ve been thinking about (in addition to actually incrementally using it in new things) how HTMX improves my apps’ experience off and on for a few months now:

      You might reasonably ask: what’s the advantage here? We are issuing an AJAX request and simply replacing the entire body.

      Is that significantly different from just issuing a normal link request?

      Yes, it is in fact different: with a boosted link, the browser is able to avoid any processing associated with the head tag. The head tag often contains many scripts and CSS file references. In the boosted scenario, it is not necessary to re-process those resources: the scripts and styles have already been processed and will continue to apply to the new content. This can often be a very easy way to speed up your hypermedia application.

      That’s a good point, and might merit mention in the official documentation, because my initial reaction to hx-boost was to ignore it because there didn’t seem to be much joy in using AJAX just to transfer the full page anyway. I was mostly thinking in terms of network transfer. I don’t think I’m alone.

      1. 2

        The head tag often contains many scripts and CSS file references.

        Does the browser re-process them if those resources are cached and not expired? I don’t think it is any different in that case…

        1. 1

          Good question. I haven’t dug into that. Maybe @1cg has?

    2. 6

      Hello, I’m the least Anglophone-friendly name on the cover. I mostly worked on chapters 03 and 10. I also designed the website — please yell at me if it’s broken!

      We lost our editors as a result of being dropped, so for now, we’re relying on the wisdom of crowds to help us pull this book closer to something worth printing.

      Note – chapter 03 is literally half empty and completely unedited. It was kind of a last-minute addition.

      1. 1

        While not a replacement for proper editors, online systems such as ProWritingAid can help you folks a lot. You can tell it that you’re writing a technical book in English and tweak a ton of editing parameters. The end result will be better than not having an editor and even if you decide to hire a proper editor later down the road, passing the book through ProWritingAid before sending it to a professional will make the work easier for that editor (unless we’re talking about developmental editing which happens before that).

        I’m not affiliated with them, I just enjoy the product and used it for some of my own technical writing.

      2. 5

        Off-topic question for the authors out of curiosity: Why do you use asciidoc? Was it your choice or did your publish require this? Are there any other formats your publisher would have allowed?

        1. 4

          in case anyone wants to contribute, the hypermedia systems repo is now public:


          the content of the book is licensed under Creative Commons BY-NC-SA 4.0


          all other content is licensed under 0-Clause BSD: