generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 105
Update naming of NGINX WAF and DoS #983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
* feat: Rewrote main landing page to be in markdown + updated card shortcode usage * Update card params correctly * chore: Refactored icon usage to use new shortcode * Removed brand icons * Removed final few brand icons
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.
As part of the 2.1 release, an invalid call-out style was reintroduced to the NGINX Gateway Fabric documentation. This commit removes it, and also restructures an instance of a double call-out pattern, which we avoid due to visual clutter. --------- Co-authored-by: Jon Torre <[email protected]>
* chore: Remove card-layout shortcode usage * chore: Update NIC docs
4 tasks
This branch is completely broken |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
product/controller
Issues related to NGINX Controller (EOS product)
product/nap-dos
Issues related to NGINX App Protect DOS
product/nap-waf
Issues related to NGINX App Protect WAF
product/nginx-one
Issues related to NGINX One Console
product/nginxaas
Issues related to NGINX as a Service for Azure
product/nic
Issues related to NGINX Ingress Controller
product/nim
Issues related to NGINX Instance Manager
product/nms
Issues related to NGINX Management Suite (EOS product)
tooling
Back end, repository, Hugo, and all things not related to content
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
WAF
orDoS
.Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩