Tags used in Meta

Use for questions that are not about bugs or feature-requests, but rather about subjective aspects.

A special tag indicating an issue that has been resolved (implementation or bugfix).

For questions dealing with tags management (e.g. merging or removing a certain tag).

Tag questions that are bug reports. The posts should indicate a reproducible problem on the site that might be due to a ...

For questions asking for help about the site's features.

For posts asking for a new platform feature or improving an existing one. Such posts do not behave as normal questions, ...

For posts that ask about content being on-topic or off-topic for a non-meta category (Q&A or Code Reviews).

For posts related to comments added for the posts (e.g. what is recommended to add as a comment).

For questions related to properly displaying of code in posts (questions, answers, comments).

For posts that raise an issue about one or multiple questions from the non-meta categories.

For questions about answers: how to provide an answer, what kind of answers should be avoided etc.

For questions about the syntax highlighting performed inside the code blocks.

For questions whether something is on-topic or not. Consider using [scope] instead.

For questions about the main platform editor used for editing questions and answers.

For questions or discussions about the scope of the site (i.e. if a question topic is fit for this site or not).

For questions about improving site content, improve exposure in order to increase the visitor count.

Questions about users with moderator privilege (what they can do, discuss about their actions etc.).

For questions about how appropriate is a certain type of questions or answer for the community.

For questions about etiquette and proper behavior toward other users or in handling certain topics.

About posts being off-topic, Use [scope] instead.

A special tag indicating that the described behaviour is intended (or "by design"), not a bug.

For questions about writing posts or using various associated functionality.

For questions related to the voting process (on posts) or the points generated by votes.

For questions about how code is rendered in posts or about it appears in the answer (e.g. code only answers or what type ...

A special tag that indicates that the requested feature will not be implemented in the near future.

For questions about various types of notifications that can be received on the site (internal, e-mail, etc.).

Used by Codidact team to inform the community about the latest changes etc.

For questions related to Code Review site category (e.g. proper categorization of posts as code review vs. Q&A).

Do NOT use this tag. Consider using [support] or [discussion] instead.

For questions or discussions about suggested edits flow (which is the default option for edits coming from users that are ...

For questions related to reactions that can be raised on answers.

For questions about the design of the Software Development site.

For questions about using the search functionality.

For questions related to either migrating posts from a community to another or migrating content from other Q&A ...

For questions about downvoting of questions and answers.

For questions related to potentially abusive content (questions, answers, comments, etc.)

For questions about mentioning a user in a post or in a comment.

For questions about the notifications that the user can receive from the site.

For questions about code obfuscation, a code alteration that makes the source code very hard to understand.

For meta posts dealing with handling duplicate questions.

For posts about usage of highlightjs for code syntax highlight. Consider using [syntax-highlighting] instead.

Use for questions dealing with imported content from other platforms such Stack Exchange sites.

For posts that deal with the scope of architecture related questions.

A special tag indicating that the requested feature or bug will not be fixed in the near future.

For questions about using gaming techniques to encourage engagement in Software Codidact. This may include privileges, ...

A special tag that indicates that a proposal (e.g. feature request) was briefly analyzed, but further analysis is ...

A special tag indicating that the requested feature will be implemented in the near future.