NGINX Ingress Controller: Clarify product differences on About page

[travisamartin]

Doc URL:
https://docs.nginx.com/nginx-ingress-controller/overview/about/

Avg Rating:
3.96 (70 responses — 2nd highest engagement in survey)

Direct User Feedback:

"Kindly help what is the difference between Nginx and Nginx Ingress Controller?"

Audit Summary:
This high-traffic overview page is accurate but incomplete for the job users expect it to do.
Survey comments and external discussions (e.g., Reddit thread: https://www.reddit.com/r/kubernetes/comments/1k75bxk/is_nginxingresscontroller_the_best_out_there/) show persistent confusion between:

• NGINX (web server)
• NGINX Ingress Controller (enterprise product)
• ingress-nginx (Kubernetes community ingress controller)
• NGINX Gateway Fabric (related but different product)

Current content jumps straight to feature listing without clarifying these differences. This risks users selecting the wrong installation path or misunderstanding capabilities.

Proposed Fixes:

• Add comparison table covering NGINX vs NGINX Ingress Controller vs ingress-nginx vs NGINX Gateway Fabric.
• Add "Who is this for?" section at the top — audience fit and product scope.
• Include a visual diagram showing where NGINX Ingress Controller fits in Kubernetes networking.
• Cross-link to NGINX Gateway Fabric doc with guidance on when to choose each.
• Consider adding link to a “Choosing the right NGINX Kubernetes solution” explainer.

Priority:
P1 – High engagement + confusion risk on a key entry page.

References:

• Audit report (shared internally)
• Related product doc: https://docs.nginx.com/nginx-gateway-fabric
• Related discussion: https://www.reddit.com/r/kubernetes/comments/1k75bxk/is_nginxingresscontroller_the_best_out_there/

[mjang]

@ADubhlaoich you're probably most qualified to work this. I might try to take this on, but I have a tendency to overcommit myself