Codidact Meta

#8: Post edited by

Monica Cellio‭ · 2023-12-05T03:11:58Z (12 months ago)

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- How much reputation the author gains or loses for received upvotes/downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "create post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
## Moderator settings
The following can be changed by moderators and do not require admin access:
- Close reasons
- Reactions
- Featured posts (on the local community)
- Promoted posts (these can show up as "ads" on other communities)
~~- Tags: creating hierarchies, merging tags~~
- Creating and editing help topics
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- How much reputation the author gains or loses for received upvotes/downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Reputation for upvotes and downvotes, per post type
- Text for the "create post" button
- Minimum lengths for post title and body
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Default filter for the category post list
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
- Maximum length of tag names
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
## Moderator settings
The following can be changed by moderators and do not require admin access:
- Close reasons
- Reactions
- Featured posts (on the local community)
- Promoted posts (these can show up as "ads" on other communities)
- Tags: creating hierarchies, merging tags, creating synonyms
- Creating and editing help topics
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#7: Post edited by

Monica Cellio‭ · 2023-01-13T18:20:47Z (almost 2 years ago)
added some things that don't require admin access

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- How much reputation the author gains or loses for received upvotes/downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "create post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- How much reputation the author gains or loses for received upvotes/downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "create post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
## Moderator settings
The following can be changed by moderators and do not require admin access:
- Close reasons
- Reactions
- Featured posts (on the local community)
- Promoted posts (these can show up as "ads" on other communities)
- Tags: creating hierarchies, merging tags
- Creating and editing help topics
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#6: Post edited by

Monica Cellio‭ · 2021-08-16T01:47:02Z (over 3 years ago)
clarification - the rep values are changes for the author of the post, not for the voter

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
~~- Reputation earned for upvotes and downvotes (can be per category)~~
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "create post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- How much reputation the author gains or loses for received upvotes/downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "create post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#5: Post edited by

Monica Cellio‭ · 2021-08-15T21:05:48Z (over 3 years ago)
noticed some duplication

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- How many "hot" questions to show, and minimum score for inclusion
~~- Sidebar notice (like the "rabbinic advice" notice on Judaism), if any~~
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
~~- Whether to enable MathJax and/or syntax highlighting (affects performance of rendering)~~
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
~~- Text for the "post" button~~
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
~~- Required tags: a list of tags, one of which must be included (used on metas)~~
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- Default category (usually Q&A, but see Code Golf for an example where it's not)
- How many "hot" questions to show, and minimum score for inclusion
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "create post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (see meta categories for examples)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#4: Post edited by

Monica Cellio‭ · 2021-07-19T22:59:51Z (over 3 years ago)

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
~~- Whether to enable MathJax (affects performance of rendering)~~
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
~~- Reputation earned for upvotes and downvotes~~
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
- How many "hot" questions to show, and minimum score for inclusion
- Sidebar notice (like the "rabbinic advice" notice on Judaism), if any
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax and/or syntax highlighting (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes (can be per category)
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#3: Post edited by

Monica Cellio‭ · 2021-02-09T15:00:03Z (almost 4 years ago)
suggested in a comment

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
## Ad-hoc changes
Sometimes we can support other requests from communities. This could be a community-specific change, like the Sefaria linker on Judaism that automatically generates links to sources. Or it could be a community need that prompts a more general change, like the table of contents which grew out of Code Golf's desire for a leaderboard on challenges. It's hard to generalize about these, beyond that we'll consider impact on performance, ease of implementation, and (if using a third-party library) code review. Describe what you're looking for on Meta, either here or on your community, and we'll be happy to work with you to figure out what's possible.
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#2: Post edited by

Monica Cellio‭ · 2021-02-09T02:04:17Z (almost 4 years ago)

Copy Link

Raw

Markdown

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme

## Site-level settings
These settings apply across all parts of a community. Unless the category-level settings say otherwise, they can't be overridden for individual categories.
General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)
Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)
Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show
User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)
Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview. If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.
Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)
## Category-level settings
General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising
Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators
Overrides:
- Guidance to show for asking a question
- Default license
- Color theme
----
Don't see what you're looking for? Please ask in comments; I've almost certainly missed some things.

#1: Initial revision by

Monica Cellio‭ · 2021-02-09T01:52:36Z (almost 4 years ago)

Copy Link

Raw

Markdown

## Site-level settings

These settings apply across all parts of a community.  Unless the category-level settings say otherwise, they can't be overridden for individual categories.

General:
- Name
- Color scheme (there's a menu; we can't change to arbitrary color values)

Guidance:
- First-visit guidance: a dismissible notice explaining what the community is about (see Meta while logged out for an example)
- Default guidance to show for asking a question
- Sidebar "notice" text, like a professional-services disclaimer (see Judaism for an example)

Content settings:
- Default license
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)
- Number of answers to trigger showing a table of contents on questions, and how long an excerpt to show

User-related settings:
- What to show in [user cards](https://meta.codidact.com/posts/280005)
- Lots of rate limits (daily limits on votes, suggested edits, flags, comments, some other things -- ask if there's something in particular you want to know about)

Abilities:
- Thresholds for all the abilities; this is complicated, but the [technical design](https://meta.codidact.com/posts/278536) gives an overview.  If you think it's too easy or too hard for users to earn some ability on your community, let us know and we'll be happy to discuss all the details.

Posts -- for each post type:
- Name and short description
- Reputation earned for upvotes and downvotes
- Whether posts are freely editable (like the [Wiki](https://meta.codidact.com/posts/280058) post type)
- Whether posts can be voted on
- For a top-level post, whether it has children (questions and answers are the only case of this right now)



## Category-level settings

General:
- Name
- Short description (appears at the top of the posts list)
- Position in the order of categories
- Which post types are permitted (for example, a blog might use only articles; a resources category might use wikis)
- Text for the "post" button
- Ability needed to post or to see a category (for example, to limit blog posting to curators or to show a category only to logged-in users)
- Whether to include the category in community advertising

Tags:
- Tag set (for example, use the same tag set as Q&A)
- Topic tags: these behave like ordinary tags but are visually differentiated, so "main" divisions can stand out (see Photo & Video for an example)
- Required tags: a list of tags, one of which must be included (used on metas)
- Tags that can only be added by moderators

Overrides:
- Guidance to show for asking a question 
- Default license 
- Color theme

Communities

Post History