Post History

We need to create some better "new community" documentation, but moderators will be able to do most of what you need, so first we have to identify the initial moderators.  (Eventually each community will choose its own, but to get started we'll need to appoint two or three pro-tem moderators.)  The dev team doesn't want to be a blocker on site progress; that doesn't scale.

The following tools and customizations are available now:

- Creating help topics.  A starter set of help topics for all sites (for the stuff that's common or commonly-needed) is on the development to-do list but isn't there yet.  Y'all should definitely create a help topic about scope; if there are any points you haven't worked out yet, you can use your meta to reach consensus.

- Close reasons: there's a default set of reasons for closing questions.  If there are site-specific considerations you can add to or edit these reasons.

- Flags: moderators are notified of flags globally and also in-situ if they happen to visit a page with pending flags.  Mods can mark flags as helpful or decline them.  (You can't reply with custom text yet.)  And, of course, mods can delete posts and comments, with or without them having been flagged.

- Category definitions: you can add categories, change the text descriptions of them (markdown is permitted), change the default license, and define sets of special tags that are styled differently (like "proposal" and "idea" on the Site Proposals category on Meta).  I believe only Codidact admins can make these changes, but if moderators request them we'll make them for you.

- Unilateral close, reopen, delete, and undelete.

Meanwhile, one thing founding members can do right now is to start creating good questions and answers.  A site introduction is important too, but the first thing visitors will look at is the list of existing questions, and that doesn't take any special privileges to start building.