Subject: [Boost-docs] interface between library documentation and Boost website
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2015-07-15 15:05:19
I'm reviewing the Boost.Python documentation, which right now consist
almost entirely of raw html.
These html files aren't fully functional as they contain relative URLs
that only work once the docs have been pulled into the main Boost website.
Is this process documented anywhere ? In particular, what are the
requirements that library-specific docs have to meet for this
integration to work ?
(I'm considering replacing the raw html by something else (e.g. ReST or
markdown) so I can generate multiple formats, but for that obviously
need to know how to validate that the generated html will meet the
requirements of the merging process.)
-- ...ich hab' noch einen Koffer in Berlin...
This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:41 UTC