Bundled documentation for Nuitka derived from Nuitka-Website #109
Description
I started having a "bundle" folder with symlinks and even a target bundle for invoke.
I forgot about how good this actually is. But what I want out of it, is a subset of the Nuitka documentation to be distributed as part of the Nuitka itself. Right now in Nuitka many things are not maintained for this documentation, but removing it, means later it will be unknowable what worked.
The bundle is an attempt at a sub-site to produce HTML. I need to be able to get this HTML somehow when build release tar balls, and obviously dynamic.inc maybe shouldn't be a symlink but produced instead by that build process. Please help me design an approach that is sustainable.
Some things that are currently symlinks probably shouldn't be (e.g. doc/commercial) and bundle.conf may seek to share more with another common file that both site and bundle use, blog config there is of course wrong. The pages should work locally in a browser and cannot use outside JS of course, so e.g. search bar should not be there, that kind of thing. Maybe no right hand side bar, or a different one.