docs: cherry-pick all changes from the docs-1.12 branch #1942
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.
Cherry-pick and squash all changes from the docs-1.12 branch since they diverted
fix: Updates to f5-theme
fix issues with raw html code tags in docs
Update netlify.toml
Add branch deploy config for release branch
Auto-update theme, go.mod from gitlab.com/f5/nginx/controller/poc/f5-hugo. (#1842)
Co-authored-by: Travis Martin [email protected]
Merge branch 'staging' into add-kic-left-nav-toc
Merge pull request #1848 from nginxinc/add-kic-left-nav-toc
fix: Add left nav TOC to KIC docs (docs-1.12)
fix: updated baseURL for prod and staging; fixes sitemap issues
Merge pull request #1904 from nginxinc/fix-kic-sitemap-baseurl
fix: updated baseURL for prod and staging; fixes sitemap issues
fix: DOCOPS-122 fix broken links in KIC
Merge pull request #1936 from nginxinc/DOCOPS-122b
fix: DOCOPS-122 fix broken links in KIC and KIC-407 remove old TOCs
fix: remove toc from globalconfiguration-resource
Merge pull request #1937 from nginxinc/DOCOPS-122b
KIC-407 remove old TOC (redundant)
fix: DOCOPS-232 broken link
Merge pull request #1938 from nginxinc/DOCOPS-232
Docops 232 - Broken link in App-protect configuration doc
Proposed changes
Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue here in this description (not in the title of the PR).
Checklist
Before creating a PR, run through this checklist and mark each as complete.