Rewrite "Security recommendations" page. #5342
Merged
Conversation
This file contains 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
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…rnetes-ingress into docs/security-improvements
for more information, see https://pre-commit.ci
ADubhlaoich
changed the title
shaun-nx
reviewed
Apr 10, 2024
Co-authored-by: Shaun <s.odonovan@f5.com> Signed-off-by: Alan Dooley <github@adubhlaoi.ch>
vepatel
reviewed
Apr 16, 2024
Signed-off-by: Alan Dooley <a.dooley@f5.com>
vepatel
approved these changes
May 8, 2024
danielnginx
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Part of #5330.
This pull request rewrites and restructures the Security page in the configuration folder of the documentation.
The main body of text has been reduced to the critical information: Hugo elements and contemporary formatting has been used to emphasize important considerations for each sub-topic, and the topics have been reordered to match the most likely user journey when going through the installation process.
Checklist
Before creating a PR, run through this checklist and mark each as complete.