You-Dont-Know-JS Making *You Don't Know JS* easier to read

@getify, I love your work on this amazing book! I know the topic of making You Don't Know JS has been brought up in the past, but I was hoping to open up some more discussion on it.

https://github.com/getify/You-Dont-Know-JS/issues/635
https://github.com/getify/You-Dont-Know-JS/issues/831
https://github.com/getify/You-Dont-Know-JS/issues/869
https://github.com/getify/You-Dont-Know-JS/issues/537
https://github.com/getify/You-Dont-Know-JS/issues/524
https://github.com/getify/You-Dont-Know-JS/issues/725
https://github.com/getify/You-Dont-Know-JS/issues/630

From https://github.com/getify/You-Dont-Know-JS/issues/635, it appears the main issue with using gitbooks is that it allows PDF exports, which O'Reilly does not permit.I was wondering if there's a way to leverage gitbooks or a similar technology, in a way that does not violate agreements with publishers.

Here are a few thoughts -

Gitbook CLI lets you easily package and serve books written in Markdown. It requires a SUMMARY.md file to be supplied, listing chapters and paths to corresponding files. The tool does not automatically publish to gitbook.com, nor does it automatically export to pdf (although the option to export to pdf does exist).

Running gitbook build creates a directory containing the book packaged as html files. Users can read the book by opening index.html. This directory can be included in this repository, or served elsewhere (Github Pages could be a neat solution). Including only the output of the command (html files) in the repo ensures end users do not have the ability to easily export to pdf.
Another option to make this more accessible could be to include the SUMMARY.md file and a docker setup that runs gitbook serve in a docker container. An end user can simply run docker-compose up to serve the book locally and be able to read the book inside a browser.

What do you and the wider community think about this? I'm happy to provide more information or examples if required. I know the contribution guide mentions that this repo is not primarily intended to optimize reading experience. Given that, what are your thoughts on forks?