In a feature discussion titled “link each config option (and theme component, etc) automatically to a Staff topic,” mattdm proposes that each admin setting should have a dedicated, automatically created Staff topic to document the “why” behind changes — complementing the existing change history. This would allow admins to record rationale (e.g., “max username length set to match SSO”) or initiate discussions like “should we change this?” — keeping documentation centralized and connected. Moin references a prior suggestion for annotating admin settings. mattdm argues for leveraging Discourse’s existing topic-based discussion tools rather than building a limited annotation system. TheBestPessimist offers an alternative: logging all admin changes in a single Staff topic, with one post per change. This allows flexibility — admins can edit the system-generated post to explain their action, reply before or after changes, or summarize groups of changes — while keeping staff informed and maintaining a searchable, threaded record of decisions.
Many community sites have a somewhat-disconnected and possibly informal group of site admins. The change history is a cool feature, so one can see who did what, and when. But there’s not a place for why, and sometimes I would like to note “max username length set his way to match the SSO”, or ask “hey, should we change this?” and have a record of the discussion. Of course, we can put that elsewhere, but that documentation gets disconnected.
It’d be awesome if each setting had a button like the little history icon which would create a linked topic in the Staff category, or of course go to an existing one if there is one.
My thought is… the software already has great tools for recording discussion on a topic, so might as well use those rather than make a new less-capable annotation feature.
An alternative take on this feature request:
All admin changes should be logged in one topic. It could even be a staff topic, so that staff is informed as well.
One post per change.
This way, there are multiple ways to summarize changes:
after the admin changes something, he can just go and edit each system-created post explaining why he did it
he can post a reply before doing any of the changes, explaining what is he doing and why
he can post a reply after doing all the changes (or a group of changes) explaining what he did and why