Skip to content

Commit c987dbd

Browse files
ADubhlaoichlamATnginx
authored andcommitted
feat: Add NGINX Ingress Controller landing page (#929)
This commit adds a custom landing page for NGINX Ingress Controller using a relatively new landing page archetype. The landing page is intended to give an impression of the product and provide links to some of the more commonly visited pages of both new and returning readers. The addition of these landing pages is a requirement for the new documentation theme's release, which receives ongoing updates.
1 parent b596820 commit c987dbd

File tree

1 file changed

+35
-0
lines changed

1 file changed

+35
-0
lines changed

content/nic/_index.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,41 @@
11
---
2+
# The title is the product name
23
title: NGINX Ingress Controller
4+
# The URL is the base of the deployed path, becoming "docs.nginx.com/<url>/<other-pages>"
35
url: /nginx-ingress-controller/
6+
# The cascade directive applies its nested parameters down the page tree until overwritten
47
cascade:
8+
# The logo file is resolved from the theme, in the folder /static/images/icons/
59
logo: NGINX-Ingress-Controller-product-icon.svg
10+
# The subtitle displays directly underneath the heading of a given page
11+
nd-subtitle:
12+
# Indicates that this is a custom landing page
13+
nd-landing-page: true
14+
# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
15+
nd-content-type: landing-page
16+
# Intended for internal catalogue and search, case sensitive:
17+
# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
18+
nd-product: NIC
619
---
20+
21+
## About
22+
23+
NGINX Ingress Controller is an [Ingress Controller]({{< ref "/nic/glossary.md#ingress-controller">}}) implementation for NGINX that can load balance Websocket, gRPC, TCP and UDP applications.
24+
25+
It supports standard [Ingress]({{< ref "/nic/glossary.md#ingress">}}) features such as content-based routing and TLS/SSL termination. Several NGINX and NGINX Plus features are available as extensions to Ingress resources through [Annotations]({{< ref "/nic/configuration/ingress-resources/advanced-configuration-with-annotations">}}) and the [ConfigMap]({{< ref "/nic/configuration/global-configuration/configmap-resource">}}) resource.
26+
27+
## Featured content
28+
29+
{{<card-layout>}}
30+
{{<card-section showAsCards="true" isFeaturedSection="true">}}
31+
{{<card title="Install NGINX Ingress Controller with Helm" titleUrl="/nginx-ingress-controller/installation/installing-nic/installation-with-helm">}}
32+
Use Helm to deploy and configure a NGINX Ingress Controller cluster
33+
{{</card>}}
34+
{{<card title="Migrate from Ingress-NGINX Controller" titleUrl="/nginx-ingress-controller/installation/ingress-nginx">}}
35+
Replace an Ingress-NGINX cluster with NGINX Ingress Controller
36+
{{</card>}}
37+
{{<card title="Releases" titleUrl="/nginx-ingress-controller/releases">}}
38+
Review the changes from the latest NGINX Ingress Controller releases
39+
{{</card>}}
40+
{{</card-section>}}
41+
{{</card-layout>}}

0 commit comments

Comments
 (0)