generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 106
feat: Update old call-outs to use new style #925
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
Merged
Merged
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
This commit replaces all instances of the old call-out style with the new one. The new style is more generic, with contributors using a parameter to denote the type of call-out. Instances of the new call-out style are also more consistent to our general Hugo formatting style: previously, empty space usage was highly inconsistent. These changes should address the terminal warnings, and are more futureproof for updates to the theme in the future.
✅ Deploy Preview will be available once build job completes!
|
ADubhlaoich
commented
Aug 6, 2025
JTorreG
approved these changes
Aug 6, 2025
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
process documentation
Documentation related to how the repository or documention itself is managed.
product/agent
Issues related to NGINX Agent
product/amplify
Issues related to NGINX Amplify (EOS product)
product/controller
Issues related to NGINX Controller (EOS product)
product/mesh
Issues related to NGINX Service Mesh (EOS product)
product/modsec-waf
Issues related to Modsecurity-WAF (EOS product)
product/nap-dos
Issues related to NGINX App Protect DOS
product/nap-waf
Issues related to NGINX App Protect WAF
product/ngf
Issues related to NGINX Gateway Fabric
product/nginx-one
Issues related to NGINX One Console
product/nginx-plus
Issues related to NGINX Plus (and NGINX Open Source in docs.nginx.com)
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)
product/unit
NGINX Unit
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
This commit replaces all instances of the old call-out style with the new one. The new style is more generic, with contributors using a parameter to denote the type of call-out.
Instances of the new call-out style are also more consistent to our general Hugo formatting style: previously, empty space usage was highly inconsistent.
These changes should address the terminal warnings, and are more futureproof for updates to the theme in the future.
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. ↩