You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our internal documentation we reference the official documentation pages a lot. Sometimes links break with newer versions of OpenShift, but this happens infrequently. We find this to be expected.
If docs.openshift.com moves to sso.redhat.com, we are not looking forward to replacing all of the links in our documentation; unfortunately our platform (Confluence) does not allow batch find/replace beyond hacking in the database or in an export and re-importing from the custom modified export.
Has there been thought about creating redirects or rewrites from docs.openshift.com to sso.redhat.com on all subpages? Otherwise this will create - in our mind preventable - significant overhead and annoyance in our team (and presumably a lot of other teams) making extensive use of these documentation sites.
Now I understand the desire (and perhaps need?) to merge these sites, but please take this into consideration before fully deprecating and removing the current site.
Thank you.
The text was updated successfully, but these errors were encountered:
Hello!
In our internal documentation we reference the official documentation pages a lot. Sometimes links break with newer versions of OpenShift, but this happens infrequently. We find this to be expected.
If docs.openshift.com moves to sso.redhat.com, we are not looking forward to replacing all of the links in our documentation; unfortunately our platform (Confluence) does not allow batch find/replace beyond hacking in the database or in an export and re-importing from the custom modified export.
Has there been thought about creating redirects or rewrites from docs.openshift.com to sso.redhat.com on all subpages? Otherwise this will create - in our mind preventable - significant overhead and annoyance in our team (and presumably a lot of other teams) making extensive use of these documentation sites.
Now I understand the desire (and perhaps need?) to merge these sites, but please take this into consideration before fully deprecating and removing the current site.
Thank you.
The text was updated successfully, but these errors were encountered: