Re: Proposal: Abandoning monolithic Boost documentation.

From: Alexander Grund (alexander.grund_at_[hidden])
Date: 2025-04-22 08:50:10

Am 18.04.25 um 19:45 schrieb Andrey Semashev via Boost:
> Perhaps, the answer to that is setting up a per-library CI that builds
> the library docs. Though if the library is unmaintained, it wouldn't
> have much of an effect.
>
I fully agree with that. The documentation build should be functional at 
each point in time and hence that should be tested in the same way as 
the rest of the code.

I actually have that as part of CI for my libraries.
E.g. 
https://github.com/boostorg/nowide/blob/f3566858722e0bb9fea057ea06078f112543e2a3/.github/workflows/ci_tests.yml#L131-L138 


I guess for other libraries a similar job is easy enough to include.
But then again: Who receives the notifications and can that person act 
on it to get it fixed?