简体中文
EnglishWhat to Know Before Posting on the NGINX Community Forum
Updated
Before posting on community.nginx.org, read the forum Guidelines and Terms of Service, then choose the single most relevant category for your topic. Use General Discussion only when nothing else fits, and use Site Experience only for feedback about the forum itself. Following these three steps — rules, category, scope — is what separates a post that gets answered from one that gets moved or ignored.
Start with the Guidelines and Terms of Service
The forum footer links directly to Guidelines, Terms of Service, and Privacy Policy. These are the rules that govern posting, moderation, and how your content is handled. Read them before your first post rather than after a moderator intervenes. The page evidence confirms these links exist on the forum home, but does not reproduce their contents — so treat the linked pages themselves as the authoritative source, not secondhand summaries.
Pick the right category
The forum is organized into a small number of top-level categories, each with a clear purpose. Matching your question to the right one is the most reliable way to reach people who can help.
| Category | Use it for | Notes from the forum |
|---|---|---|
| Announcements | News from the NGINX team | Read-only in practice; 43 topics listed |
| Projects | Project-specific questions | Subcategories include ingress-nginx, Migration Help, NGINX Ingress Controller, NGINX Gateway Fabric, NGINX Commercial Products, and Other Projects |
| Community | Community content and events | Includes Community Showcase (demos, projects, modules) and Events |
| General Discussion | NGINX and related technologies that don't fit elsewhere | 53 topics — the catch-all, not the default |
| Site Experience | Feedback about the forum itself | 12 topics |
| Uncategorized | — | 1 topic; a sign that posts land here when no category is chosen |
Two practical readings of this table:
- Product questions belong in Projects, not General Discussion. If you're asking about ingress-nginx, the Ingress Controller, Gateway Fabric, or a commercial product, the dedicated subcategory puts you in front of people watching that area.
- "General Discussion" is a fallback, not a shortcut. The forum describes it as the place for questions that "do not fit neatly into other categories." Posting a specific product question there reduces the chance the right person sees it.
Know what each category is not for
- Site Experience is explicitly for feedback about the forum itself — layout, behavior, moderation, features. A question about NGINX configuration does not belong there.
- Community Showcase is for discovering or sharing NGINX-related content, demos, projects, and modules. It is a sharing space, not a support queue.
- Announcements is the NGINX team's channel. Don't post questions there expecting a reply thread.
A pre-post checklist
Run through this before hitting submit:
- Have you read the Guidelines and Terms of Service? They're linked in the footer of every page.
- Is your question already answered? Search the relevant Projects subcategory first — the forum is a gathering place for "all things NGINX," and common configuration questions recur.
- Does your topic map to a named subcategory? If yes, post there. If no, General Discussion.
- Is your post about the forum rather than NGINX? Then Site Experience.
- Are you sharing rather than asking? Community Showcase or Events, depending on whether it's content or a happening.
What to expect from the platform itself
The forum runs on Discourse and states it is "best viewed with JavaScript enabled." If pages render incompletely or controls don't respond, check that JavaScript is active in your browser before assuming the forum is broken — and if it genuinely is, that's a legitimate Site Experience post.
The short version
Read the rules, choose the narrowest category that fits, and keep Site Experience for forum feedback only. The forum's own structure — with dedicated subcategories for each NGINX project and a General Discussion explicitly framed as the leftover bucket — tells you the community expects topical posts. Matching that expectation is the cheapest way to get a useful answer.