Knowledge Base entry

How can you structure flairs for recurring content (Q&A, Discussion, News, Tutorial)?

A practical answer page built from the knowledge base source.

Recurring content categories benefit from a consistent, predictable flair structure that members learn quickly and apply correctly. The goal is to make the flair system feel intuitive rather than bureaucratic — members should reach for the right flair because it accurately describes their post, not because a moderator will remove the post if they do not. For a generic knowledge-sharing community, four flair categories cover most of the common content types well. "Question" or "Q&A" captures posts where the author is seeking information or assistance. These posts serve a specific function — they generate answer-oriented responses — and separating them from open discussion makes it easier for members who want to help others to find them quickly. "Discussion" covers open-ended posts that invite multiple perspectives without seeking a single correct answer. "News" or "Article" applies to external links reporting on events, developments, or announcements relevant to the community's topic. "Tutorial" or "Guide" marks instructional content authored by community members. Each of these categories can be refined with subcategories using AutoModerator or through community convention. For example, a programming subreddit might split "Question" into "Beginner Question" and "Advanced Question" to help members self-sort and to prevent experienced members from dismissing beginner posts as noise. In a community with very high volume, hierarchical flair — a primary category plus a secondary tag — allows finer filtering without multiplying the number of top-level flair options. Weekly or monthly recurring threads deserve their own dedicated flairs, typically labeled with the thread name and day: "Weekly Discussion Thread," "Monthly Showcase," or "Friday Q&A." Pinning the AutoModerator message that creates these threads means the flair is applied consistently, which trains members to recognize the recurring format and navigate to it reliably. Periodically review whether members are applying flairs accurately. If "Discussion" is being used as a catch-all for posts that do not fit other categories, the remaining flair options may need clearer descriptions. Flair labels should describe what the post contains, not what the author hopes people will do with it, which keeps the system grounded in observable content rather than intent.