Usage instructions in the README file.
Follow the README to produce the documentation pages.
Point your browser to docfx/_site/index.html to see the results.
Use source files instead of dll (so the name does not change between meson and autotools) and scan all folders from the root down (so will work for any meson builddir which is a subfolder of root)
I am not too sure if we want to really download here without telling that to the user...
The normal way is installation via package manager, i could understand that a few users would be concerned that we *under the hood* download precompiled codes from somewhere, and execute it...
The alternative that i can think of is a seperated *install* script and a option to pass the docfx directory to the install script, or the generation script.
OK, thanks @zmike, I'll try to find more "volunteers" for testing.
Will a "Do you want to proceed with download?" message be enough?