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
We deploy multiple versions of our content and occasionally we need to make cross-references between the versions. For instance, I might have versions 1.11 and 1.14 deployed to the same server. Both versions have a docs/content.md file. With both versions deployed, I can browse to /1.11/content.html and /1.14/content.html. Then in another 1.14 page I want to refer to /1.11/content.html with something like this (on a docs/parent.md file in 1.14):
[1.11 content](/1.11/content.html)
Unfortunately this results in a link to /1.14/parent.html#/1.11/content.html. Note these references must still be relative to the server they are deploy to (can't start with https://).
We tried using the attrs_inline MyST extension and adding {.external} to the end of the markdown reference as in:
[1.11 content](/1.11/content.html){.external}
This got rid of the myst.xref_missing warning (which was good) but the link was still /1.14/parent.html#/1.11/content.html.
What should our markdown look like to form a proper cross-version reference?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We deploy multiple versions of our content and occasionally we need to make cross-references between the versions. For instance, I might have versions 1.11 and 1.14 deployed to the same server. Both versions have a
docs/content.md
file. With both versions deployed, I can browse to/1.11/content.html
and/1.14/content.html
. Then in another 1.14 page I want to refer to/1.11/content.html
with something like this (on adocs/parent.md
file in 1.14):Unfortunately this results in a link to
/1.14/parent.html#/1.11/content.html
. Note these references must still be relative to the server they are deploy to (can't start withhttps://
).We tried using the
attrs_inline
MyST extension and adding{.external}
to the end of the markdown reference as in:This got rid of the
myst.xref_missing
warning (which was good) but the link was still/1.14/parent.html#/1.11/content.html
.What should our markdown look like to form a proper cross-version reference?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions