community.nginx.org

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.

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:

1. Have you read the Guidelines and Terms of Service? They're linked in the footer of every page.
2. 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.
3. Does your topic map to a named subcategory? If yes, post there. If no, General Discussion.
4. Is your post about the forum rather than NGINX? Then Site Experience.
5. 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.

The Arts & Recreation Foundation of Overland Park is a nonprofit organization that raises money and builds community partnerships to support arts, culture, and recreation in Overland Park, Kansas. If you live in or near the city, its work shows up in places you may already visit: Deanna Rose Children's Farmstead, the Overland Park Arboretum & Botanical Gardens, and public art projects across the community. The foundation itself is not a city department; it works alongside the city and donors to fund enhancements, programs, and special projects that go beyond what tax dollars alone cover.

What the Foundation Actually Does

Think of the foundation as a charitable partner for Overland Park's cultural and recreational assets. Its role generally includes:

• Fundraising: Accepting donations and gifts that are directed toward specific attractions, programs, or public art.
• Community partnerships: Working with businesses, civic groups, and residents who want to support local amenities.
• Events: Hosting or supporting events that both raise funds and give the community a reason to gather.
• Project support: Helping pay for improvements, additions, and experiences at the destinations it serves.

Because it is a nonprofit, money raised goes back into the community rather than to private owners. That structure is what allows residents and local businesses to contribute directly to the places they care about.

The Destinations and Initiatives It Supports

Deanna Rose Children's Farmstead

Deanna Rose Children's Farmstead is a family-oriented attraction that gives children and adults a hands-on look at farm life, animals, and Kansas history. Foundation support for the Farmstead typically means helping fund enhancements, educational experiences, and community events that keep the site engaging for repeat visitors and first-timers alike.

Overland Park Arboretum & Botanical Gardens

The Arboretum & Botanical Gardens is a living collection of gardens, trails, and natural areas. Supporting it can involve funding plantings, garden features, educational programming, and long-term care that keeps the grounds beautiful and accessible through the seasons.

Public Art Projects

Public art is another core focus. The foundation helps bring sculptures, installations, and other artistic works into shared spaces, making art part of everyday life rather than something you only see in a museum. These projects often depend on donations and partnerships to move from idea to installation.

How Community Partnerships and Events Fit In

The foundation's model relies on the community, not just on institutional funding. Local businesses may sponsor an event or a project. Residents may attend a fundraiser, buy a ticket, or make a donation. Civic organizations may partner on a specific initiative.

Events serve two purposes at once: they raise money and they build awareness. A well-attended event introduces new people to the Farmstead, the Arboretum, or a public art effort, and some of those people become ongoing supporters. Over time, this cycle of participation and giving is what sustains projects that a city budget alone might not fully fund.

Practical Ways Residents Can Get Involved

If you want to support this work, you do not need to be a major donor. Here are realistic starting points:

1. Visit the attractions. Attendance and word-of-mouth support matter. Spend a day at the Farmstead or the Arboretum and bring friends or family.
2. Attend a foundation event. Events are the easiest entry point. You get an experience, and your ticket or participation helps fund projects.
3. Donate. Contributions can often be directed toward a specific area, such as the Farmstead, the Arboretum, or public art. Check the foundation's website for current giving options.
4. Volunteer. Nonprofits frequently need help with events, outreach, and administrative tasks. Volunteering is a low-cost way to contribute time and skills.
5. Partner as a business. If you own or manage a local business, sponsorship or in-kind support can align your brand with community assets people genuinely value.
6. Spread the word. Sharing events and projects with neighbors, school groups, or community boards helps the foundation reach people who might want to help.

For current details on events, donation methods, and volunteer needs, go directly to the foundation's website, since programs and opportunities change over time.

Why This Matters for Local Quality of Life

Arts, culture, and recreation are not extras. They shape how a city feels to live in. A children's farmstead gives families a shared destination. Botanical gardens provide green space and seasonal beauty. Public art makes ordinary streets and parks more interesting. When residents and businesses invest in these things through a foundation, they are effectively choosing the kind of community they want.

The Arts & Recreation Foundation of Overland Park exists to make that choice easier and more organized. It connects people who care about these places with the projects that need support, and it keeps the benefits local.

A Simple Way to Think About It

If you are trying to understand the foundation in one sentence: it is the community's fundraising and partnership arm for Overland Park's arts, culture, and recreation, with a focus on Deanna Rose Children's Farmstead, the Overland Park Arboretum & Botanical Gardens, and public art. You benefit from its work when you visit these places, and you can contribute by attending, donating, volunteering, or partnering. Start with a visit, then decide how you want to take part.

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:

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

1. 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.
2. Search before posting. Because topics are threaded and categorized, an existing thread may already cover your question.
3. 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.
4. 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.

The NGINX Community Forum (community.nginx.org) is organized into a small set of categories so that questions and discussions land where the right people will see them. If you are unsure where to post, start with General Discussion; if your topic is about a specific NGINX project, use that project's category. The forum is powered by Discourse and is described as "a gathering place for all things NGINX."

Project Categories

These categories cover specific NGINX projects and products. Use them when your question, bug report, or configuration discussion is tied to one of these components.

The forum listing also groups Migration Help alongside these project areas, which is where migration-related questions are collected.

How to choose among them

• If your issue involves Kubernetes ingress behavior, decide first whether you are using ingress-nginx or NGINX Ingress Controller — they are listed as separate categories, so posting in the correct one matters.
• If you are working with Gateway API resources, use NGINX Gateway Fabric.
• If your question concerns a paid/commercial NGINX product rather than an open-source project, use NGINX Commercial Products.
• Anything project-related that has no dedicated category belongs in Other Projects.

Community Categories

These categories are about the community itself rather than technical support.

• Community Showcase — "discover or share NGINX-related content, demos, projects, and modules." Use this to post something you built or to browse what others have shared.
• Events — "Find upcoming NGINX-related events." Use this to locate events; it is not a support channel.
• Announcements — "Keep an eye out for announcements from the NGINX team." This is a read-oriented category for official news.

General and Meta Categories

• General Discussion — "Discuss topics about NGINX and related technologies here. If your question or thoughts do not fit neatly into other categories, this is the right place." This is the catch-all for technical discussion that spans projects or does not match a specific category.
• Site Experience — "If you have any feedback about this forum specifically, let us know here!" Use this for forum bugs, layout issues, or suggestions about community.nginx.org itself — not for NGINX configuration questions.
• Uncategorized — a residual bucket for posts that have not been placed in a category. It is better to pick a real category so your post reaches the right readers.

A Quick Decision Path

1. Is your question about the forum itself (layout, bugs, feedback)? → Site Experience
2. Is it about a specific NGINX project or product? → the matching project category (ingress-nginx, Ingress Controller, Gateway Fabric, Commercial Products, or Other Projects).
3. Are you sharing content, a demo, or a module? → Community Showcase
4. Are you looking for an event? → Events
5. None of the above? → General Discussion

Before posting, it is also worth reading the forum's Guidelines and Terms of Service, which are linked from the forum home page.

The NGINX Community Forum (community.nginx.org) is a Discourse-based gathering place for "all things NGINX." You can read official NGINX team announcements, browse or share NGINX-related demos, projects, and modules in the Community Showcase, find upcoming NGINX events, and discuss NGINX and related technologies in General Discussion. It suits anyone who wants community knowledge, project examples, or a place to ask general NGINX questions; it is not a formal support portal or a sales channel.

Main Categories and What They Hold

The forum's home page lists these categories:

The page also shows topic counts next to some categories (for example, Announcements shows 43 topics and General Discussion 53), which gives a rough sense of activity volume.

What You Can Share

• Showcase material: The Community Showcase explicitly invites NGINX-related content, demos, projects, and modules. If you built something with NGINX, this is the intended place to post it.
• Event information: The Events category is where NGINX-related events are listed, so you can add or find happenings there.
• Questions and discussion: General Discussion is described as the place for topics about NGINX and related technologies that don't fit other categories.
• Project-specific posts: If your question concerns ingress-nginx, the Ingress Controller, Gateway Fabric, migration, or commercial products, use the matching Projects subcategory rather than General Discussion.
• Forum feedback: Comments about the forum itself belong in Site Experience.

What to Expect Before Posting

• It is a community space, not a guaranteed support desk. The description frames it as "a gathering place," and the page does not state response-time or support commitments.
• Categorize deliberately. Because there is an Uncategorized section and several project subcategories, choosing the closest category improves the chance your post reaches the right readers.
• Check the guidelines first. The footer links to Guidelines, Terms of Service, and Privacy Policy; reading the guidelines before your first post is the practical way to avoid moderation issues.
• JavaScript is required. The page notes it is "best viewed with JavaScript enabled," so plan to use a browser with JavaScript active.

A Practical Way to Start

1. Open community.nginx.org and scan the category list on the home page.
2. If you want to share work, go to Community > Community Showcase; if you want to ask a technical question, pick General Discussion or the relevant Projects subcategory.
3. Read the Guidelines link in the footer, then create your post in the chosen category.
4. To verify your post landed correctly, return to the category page and confirm the topic appears there rather than in Uncategorized.

A common snag is posting a product-specific question in General Discussion when a Projects subcategory exists; moving it to the specific subcategory is the fix.