-
Notifications
You must be signed in to change notification settings - Fork 394
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
doc: shorter links to user-guide #2967
Comments
These shortlinks will be used for ui messages on `exp init`. Fixes #2967.
I think we should use something like learn.dvc.org for user guide links (similar to man.dvc.org for the cmd ref). It would probably need some more customization options so you don't have to use the entire path after /user-guide/ which can be pretty long... The configuration could be part of the doc engine though, stored as a new field in sidebar.json (cc @rogermparent) |
Since learn.dvc.org doesn't exist currently, IIRC we'll have to add another CloudFlare site with a page rule pointing to the desired page and then add a I'm always of the "simplest is best" school of thought which would entail just adding That said, if the consensus is that we want a subdomain, we should be able to figure it out. |
Making the global URL namespace ( I would recommend to come up with something like: s.dvc.org/something (s stands for short) it can be a general mechanism of short links that we'll have a way to maintain separately and use for different things w/o affecting the website regular workflow |
Yes some sort of internal short perma-linking system would be nice (outside of the docs enfine). Even maybe on link.iterative.ai |
Unrelated: we used to have a general |
It should be dvc specific though since we'll include into the help message. |
maybe |
there wasn't a general eng label when I have modified. We had In general, I didn't delete the labels if there are issues with them. content => team/docs |
Instead of a domain, I'd recommend to have redirects:
We can also have two letter redirects /gs, /uc, /cr for other sections. These probably won't cause much conflicts. |
I'd say "user guide" needn't show up in the URL at all ever ( |
I think I miss your point. What if we have
I won's solve the I still think we need to create a simple custom url shortener which anyone could use to their benefit. I don't see a particular reason to keep it about docs specifically (leak very specific docs structure into it). |
|
Seems like the way we're talking about this entails a more elaborate system that just throwing in some |
sounds good to me!
we are still polluting the global URL space with the docs structure. Let's use some common third-level URL After that it will up to the author to put a link they like there. It can be even |
I was replying to a tangential discussion (#2967 (comment)). In terms of this mostly unrelated issue (#2967, i.e. bespoke one-off shortlink), DVC team should open a PR?
I'd say that's another separate tangential meta issue, but fully agree. |
Ok. We can use |
|
Is it a |
Yep |
Hi. So is this closed by #3001? I don't see those 2 specific redirects in there. Cc @skshetry @iesahin thanks |
https://dvc.org/doc/user-guide/experiment-management/running-experiments is now https://s.dvc.org/g/exp/run https://dvc.org/doc/user-guide/project-structure/pipelines-files is https://s.dvc.org/g/project-structure/pipelines-files If you need shorter versions to these, please let me know or just submit a PR with s.dvc.org domain. @skshetry |
Hi, I need a few shortlinks for the following, which I need for
dvc exp init
.I'd prefer something like
https://dvc.org/doc/pipelines-files
or evenhttps://dvc.org/pipelines-files
. Or, something else that is much shorter and still readable/understandable.Here's how we display it right now in
dvc exp init
:Looking at the dvc's code, we only seem to have short links for
man.dvc.org
which redirects to command-reference. We could also have something similar likehttps://guide.dvc.org/running-experiments
(though it's 2 characters lengthier thanhttps://dvc.org/doc/running-experiments
).The text was updated successfully, but these errors were encountered: