What Is the NGINX Community Forum (community.nginx.org)?
Updated
The NGINX Community Forum at community.nginx.org is a discussion board for people who work with NGINX and related technologies. It is a place to ask questions, share projects, and follow announcements from the NGINX team — not a download page or the official documentation site. If you want to read or post in threaded discussions about NGINX, this is the right site; if you need product downloads, installers, or reference docs, you should look elsewhere.
What the forum is built on
The site runs on Discourse, a threaded discussion platform. That shapes how you use it:
- Threaded topics — each question or announcement is its own topic, and replies stay grouped under it.
- Categories — content is organized into categories rather than a single feed, so browsing by area of interest works better than scrolling everything.
- JavaScript required — the site states it is best viewed with JavaScript enabled, so a browser with JS blocked will not render the forum properly.
The main categories
The forum's front page lists these categories, each with its own topic count:
| Category | What it covers |
|---|---|
| Announcements | News from the NGINX team |
| Projects | Sub-areas for NGINX Ingress Controller, ingress-nginx, NGINX Gateway Fabric, NGINX Commercial Products, Migration Help, and Other Projects |
| Community | Community Showcase (demos, projects, modules) and Events |
| General Discussion | NGINX and related technologies that don't fit elsewhere |
| Site Experience | Feedback about the forum itself |
| Uncategorized | Topics not yet placed in a category |
The Projects category is the most structured: it splits into product-specific sub-categories, so a question about the Ingress Controller and a question about Gateway Fabric land in different places. General Discussion is the catch-all when a topic doesn't fit a product area.
When to use it, and when not to
Use the forum when you want:
- Peer discussion — asking how others have approached a configuration or migration problem.
- Project discovery — browsing Community Showcase for demos, modules, and shared work.
- Event awareness — checking the Events category for NGINX-related events.
- Official announcements — following the Announcements category for updates from the NGINX team.
Look elsewhere when you need:
- Product downloads or installers — the forum is described as a gathering place, not a distribution point.
- Reference documentation — the forum is for discussion; authoritative docs live on the documentation site.
- Account or billing help for commercial products — the forum has a Commercial Products area for discussion, but it is not a support portal.
Practical tips for first-time visitors
- Pick the narrowest matching category. A question about ingress-nginx belongs in its Projects sub-category, not General Discussion — it is more likely to be seen by people who know that project.
- Search before posting. Because topics are threaded and categorized, an existing thread may already cover your question.
- Check the pinned guidelines. The site links Guidelines, Terms of Service, and Privacy Policy in the footer; reading the guidelines first avoids common posting mistakes.
- Expect JavaScript-dependent navigation. If pages look empty or menus don't respond, check whether a script blocker is active.
A concrete example
Suppose you are migrating from the community ingress-nginx controller to NGINX Ingress Controller and want to know what others hit along the way. The forum gives you two relevant places: the Migration Help sub-category under Projects, and the NGINX Ingress Controller sub-category. Reading existing topics there shows you the problems other users raised; posting a new topic in the matching sub-category puts your question in front of the people watching that area. The same question posted in General Discussion would be less likely to reach that audience.
In short: treat community.nginx.org as the conversation layer around NGINX — organized by category, built for threaded discussion, and best used when you have a specific project area in mind.