On 8/10/24 2:11 PM, Andrey Semashev via Boost wrote: Good points.
You do have the documentation with the library - in its source form (i.e. QuickBook/Markdown/AsciiDoc/etc.). Committing the generated html in git is similar to committing compiled binaries of your library in git.
BUT how is a potential or current user to access the latest html version of the documentation? Is he expected to generate it himself. Then there's the question of what if the documentation the user is meant to see is located on different branches? In general, who is expected to generate the documentation and when is he expected to do it? And what about the readable documentation out of sync with the code? Robert Ramey
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost