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
The main motivation to publishing to gh-pages would be uniformity, distinct page paths (making analytics easier to manage), and eventually a potentially smoother transition to the Argo domain, argoproj.io.
Per argoproj/argo-workflows#11390, Workflows specifically moved to RTD as it supports versioned documentation out-of-the-box.
CD did this migration earlier for the same reason, which is why the GH Pages link for CD has a redirect as per #5031, #5099, #5535, #5457
So there is no plan to revert back.
and eventually a potentially smoother transition to the Argo domain, argoproj.io.
I don't know if this was planned, but we can probably add subdomains for each of the docs that use RTD.
I'm not sure if using subpaths would be the most appropriate either as there is no uniform headers or footers that link to the other Argo projects from each subproject's individual docs.
The main site and other Argo docs are published via gh-pages:
In contrast, Argo CD docs are available from:
Have you considered publishing to gh-pages?
The main motivation to publishing to gh-pages would be uniformity, distinct page paths (making analytics easier to manage), and eventually a potentially smoother transition to the Argo domain, argoproj.io.
/cc @alexmt
The text was updated successfully, but these errors were encountered: