Could setup a webhook kinda like we do on github, so one of the “moderators” could do !publish and a script would create and publish the post or something. That way blog posts could also still be written as code directly.
I have trouble writing markdown at the best of times, let alone asciidoc. So I almost never contribute to anything on jenkins.io
I’m not sold discourse is the right way to handle this, but I do agree that the github flow sucks.
There’s also https://www.netlifycms.org/ which would allow the exact flow to keep, but gives you a web ui tied to github
Or completely redo it, so site is backed by a full CMS. Gatsby has a wordpress, or contentful (bleh) or any other CMS plugin, then outputs a static site. Keeps runtime nice and fast, and the backend less accessible.
I don’t have any real opinions on how, but as a non writer I don’t like contributing content at all to jenkins.io right now.