On 03.01.2018 13:29, Peter Dimov via Boost wrote:
Stefan Seefeld wrote:
github already allows per-project pages, and some of the github projects use them (e.g. http://boostorg.github.io/python/). So let's assume for a moment that all Boost projects use github pages to publish their documentation.
Doesn't this ignore the current release procedure, which builds the html documentation from the qbk/rst/asciidoc sources in the repositories and includes the generated result into the release?
I don't see any conflict there. In case of Boost.Python, it's the exact same content / build process used for both, which is why I believe this would be an almost trivial change for other projects, too. Stefan -- ...ich hab' noch einen Koffer in Berlin...