Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

75%
+4 −0
Q&A New site setup process?

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 communit...

posted 4y ago by Monica Cellio‭  ·  edited 4y ago by ArtOfCode‭

Answer
#2: Post edited by user avatar ArtOfCode‭ · 2020-06-07T23:28:04Z (almost 4 years ago)
  • 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.
  • 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. 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.
#1: Initial revision by user avatar Monica Cellio‭ · 2020-06-07T20:33:06Z (almost 4 years ago)
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.