-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[docs] 2026 overhaul #14157
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
[docs] 2026 overhaul #14157
Conversation
adjust css make CSS nicer: color and top border remove flicker again
Metrics draft
…ngo-DefectDojo into staging-new-docs
mtesauro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
valentijnscholten
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@paulOsinski Some questions which are hard to answe myself as there are so many changes in the PR:
- Does this include all changes made to the docs recently in bugfix and dev branches? I notice this PR is based against master (and GH says it's out of date with master).
- Does this result in URL changes which will lead to users getting 404s when arriving via earlier published links to upgrade notes or via google?
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
@valentijnscholten good point regarding links. I have changed it to be based against bugfix. I have a tool that will check for internal 404s and I'll make sure I run that before reopening the PR. When this site is deployed it will include a sitemap which should hopefully eliminate 404s from Google, but I can't say the same for any other links - there is no redirect handling |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
@valentijnscholten links are all fixed! |
valentijnscholten
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if I can test this so approving assuming we will fix if anything is broken after merging.
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
This introduces a few changes to our documentation