-
Notifications
You must be signed in to change notification settings - Fork 708
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
Links in Getting Started page are broken #3180
Comments
Thanks @josemaia , yes the docs were recently restructured and we'd missed that we need to be careful with the relative links due to the docs site using clean URLs (the link to the dashboard is also similarly broken at the end of the page). We need to either:
Thoughts @antgamdia , @ppbaena ? |
I'd rather avoid extra patches or checks, and directly go with what other projects are doing: either serving the docs via Github pages or set up a Netlify static site. But the key point is that we really should maintain a single repo, not a website and the main kubeapps repo separately (when they're using the same info). Perhaps after these intense iterations, we could set some time for this in sept ? |
+1 - that's what I meant with the second point. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
+1 to the second approach too. |
I've been checking kubeapps.com and there are broken links at: |
Current https://kubeapps.com website will be deprecated and replaced by a new website fully integrated in the kubeapps repo as described in #3953 |
Description:
Internal links in Getting Started page are redirecting wrongly, to a 404 page.
Steps to reproduce the issue:
Additional information you deem important (e.g. issue happens only occasionally):
Link appears to be rewriting partially, e.g. https://kubeapps.com/docs/getting-started/using-an-OIDC-provider instead of the correct https://kubeapps.com/docs/using-an-OIDC-provider
The text was updated successfully, but these errors were encountered: