On 2018-12-17 4:17 p.m., Mateusz Loskot via Boost wrote:
If the old notion of Wiki is not required, I'd stick to git repo with collection of Markdown files and set up a CI build that runs MkDocs and publishes stuff at `boostorg.github.io/wiki`. Then new content could be submitted via PR. I see advantage of having mechanism to review content. - a classic wiki feels like it's too easy to drop any new page with any garbage, scratch notes, etc. A PR-based maintenance would help to avoid that.
I think there is room (and raison d'etre) for both. A wiki is a convenient playground for new content to be "prototyped". Once stable, it can be migrated to a more curated model. But shutting down a wiki is certainly no way to grow a community (if growing a community is what Boost wants - sometimes I'm in serious doubt about that). Stefan -- ...ich hab' noch einen Koffer in Berlin...