These are two completely separate topics. 1. Remove the unified documentation build. In a boost archive there is a /doc/ folder at the root. This doesn't follow the standard in-libs doc builds format, and so it's not modular, or consistent. It will require many PRs, editing Jamfiles, to move those into each respective libs/. This ought to be done. (But requires effort by each maintainer). PRs are welcome. 2. Split the Boost release into two archives The contents of those two would be... "source only" (for faster downloads) and "full" (including docs. and, keeping backwards compatibility). If there is any question, it is "which of those takes the place of the current download archives". If "full" remains in-place, as the main URL, it will be fully backwards compatible, and not break anything, while offering an alternative "source-only" to speed up downloads. How high priority is that (for end-users, or for boost). Yes, it's on the radar (as a project), but there are always many other tasks at any moment. Or use https://github.com/boostorg/boost/releases