generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 105
Rewrite main landing page to be in markdown + updated card shortcode usage #818
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
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
nginx-jack
pushed a commit
that referenced
this pull request
Jul 23, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Jul 25, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
lamATnginx
added a commit
that referenced
this pull request
Jul 28, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Aug 14, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Aug 18, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
lamATnginx
added a commit
that referenced
this pull request
Aug 18, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Aug 20, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Aug 20, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Aug 22, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
nginx-jack
pushed a commit
that referenced
this pull request
Aug 25, 2025
…usage (#818) feat: Rewrote main landing page to be in markdown + updated card shortcode usage
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
enhancement
New feature or request
product/agent
Issues related to NGINX Agent
product/nginx-one
Issues related to NGINX One Console
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
Closes https://github.com/nginxinc/docs-platform/issues/556
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
Footnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩