### Communities

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

77%
+5 −0

posted over 1 year ago by Monica Cellio‭  ·  edited 1y ago by Monica Cellio‭

#6: Post edited by Monica Cellio‭ · 2021-08-16T01:47:02Z (about 1 year ago)
clarification - the rep values are changes for the author of the post, not for the voter
• ## 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - Color theme
• 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - Color theme
• 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 (about 1 year ago)
noticed some duplication
• ## 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:
• - Whether to enable MathJax and/or syntax highlighting (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - Color theme
• 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - Color theme
• 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 (about 1 year ago)
• ## 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - 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
• - Color theme
• 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:
• - Whether to enable MathJax and/or syntax highlighting (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - Color theme
• 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 (over 1 year ago)
suggested in a comment
• ## 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - 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
• - 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - 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
• - Color theme
• 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 (over 1 year ago)
• ## 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - 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
• - 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:
• - Whether to enable MathJax (affects performance of rendering)
• - Whether to enable code syntax highlighting (affects performance of rendering)
• 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
• - 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
• - 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 (over 1 year ago)
## 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:
- Whether to enable MathJax (affects performance of rendering)
- Whether to enable code syntax highlighting (affects performance of rendering)

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