Categories

Content on a community is organized into categories. Categories and post types are orthogonal. Each category defines what post types are permitted in that category.

Every site will have at least two categories: Q&A and meta. Meta is not a separate site. Meta is something like another tab across the top of the page, and clicking on it shows you meta content instead of main content. Sites might define other categories, like "blog" or "critiques". Because categories have implications for the UI and could cause confusion if numerous, sites are strongly encouraged to keep the number of categories small. Categories are not tags.

To define a category, one must specify:

• name (this is the name to be shown in the UI)
• permitted types of top-level posts (question, discussion, article (blog post), etc) -- note that for MVP we have not defined these additional post types and question is the only option initially
• tag set to use (same as main or category-specific)

Use cases

1. Every site has a meta category. By default the meta category permits question and discussion posts. Meta uses its its own tag set.

2. A site has an active blog. Blog posts use the same tags as main Q&A. The blog is a tab right there on the site, not an off-site, separate system.

3. Another site has an infrequently-updated blog. It has a blog category like #2, but the site also shows blog posts on the main site even though they're not questions, 'cause that's how that community likes it.

4. A site allows users to post work for review or critique. The critique category uses the discussion post type only -- no questions with answers, just posts with feedback (comments). Tags for critiques are separate from main tags.

5. A site has a collection of canonical posts on important topics. They are collected in a "wiki" category, which accepts only article post types. The category uses the same tag set as main.

Meta

Meta is a category.

The meta area (question list), meta posts, and meta tags have clear visual differences from main-site analogues.

There is a clear way to make a meta post. This could be a separate “ask on meta” affordance or a choice on the “ask question” page or something else. Encouraged: in addition to any other affordances, plan for an "ask on meta about this question" link from main-site questions (to make it easier for people to ask, e.g., why this question was closed).

Meta posts use a tag set that is separate from the main-site tag set.

Meta by default permits top-level post types of "question" and (when available) "discussion".

(Source)

Discussion post type (not MVP)

(Putting this here for reference.)

A discussion is a top-level post (like a question), but the only supported responses are comments (which will be threaded, same as elsewhere).

Comments on discussion posts will not be as aggressively collapsed as on questions and answers. (Ideally comments are expanded by default unless there’s a ridiculously large number.)

A discussion can be resolved by either the author or a moderator. Resolving a discussion adds an answer in which the resolver describes the resolution.

Discussion posts may be used for meta posts, sandbox or other uses as determined by each community.

(Source)