We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(Reported by Bryan Taylor in the CNCF slack channel)
The documentation pages have mixed rendering results where sometimes the extension .html works and sometimes it doesn't
https://argoproj.github.io/argo-rollouts/features/traffic-management/istio/ -> renders a broken page https://argoproj.github.io/argo-rollouts/features/traffic-management/istio.html -> works ok
But on the other hand
https://argoproj.github.io/argo-rollouts/getting-started/istio/ -> works ok https://argoproj.github.io/argo-rollouts/getting-started/istio.html -> renders a broken page.
The issue here (apart from the inconsistency) is that the broken links are indexed by Google confusing users.
We should either fix all links to have a consistent rendering or make the wrong ones return 404 instead of broken renderings
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Fixed in #1321 and #1322
Sorry, something went wrong.
No branches or pull requests
(Reported by Bryan Taylor in the CNCF slack channel)
The documentation pages have mixed rendering results where sometimes the extension .html works and sometimes it doesn't
https://argoproj.github.io/argo-rollouts/features/traffic-management/istio/ -> renders a broken page
https://argoproj.github.io/argo-rollouts/features/traffic-management/istio.html -> works ok
But on the other hand
https://argoproj.github.io/argo-rollouts/getting-started/istio/ -> works ok
https://argoproj.github.io/argo-rollouts/getting-started/istio.html -> renders a broken page.
The issue here (apart from the inconsistency) is that the broken links are indexed by Google confusing users.
We should either fix all links to have a consistent rendering or make the wrong ones return 404 instead of broken renderings
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: