Conversation
troyraen
added
bug
| This tutorial is an introduction to the content and format of the Euclid Q1 Merged Objects HATS Catalog. | ||
| Later tutorials in this series will show how to load quality samples. | ||
| See [Euclid Tutorial Notebooks: Catalogs](../../euclid_access/euclid.md#catalogs) for a list of tutorials in this series. | ||
| See [Euclid Tutorial Notebooks](../../euclid_access/euclid.md) for a complete list of Euclid tutorials. |
There was a problem hiding this comment.
I think you better not rely on relative paths. I see why you would prefer to use filepaths instead of references to link to other notebooks, but we don't ship the landing pages into fornax, and one may just open up a notebook on its own, so this link with be broken in those cases anyway.
And using a path will make it more likely to break when things are moved around. And IMO the hover preview can be useful for links like this as opposed to a link that takes the user away from their notebook (compare the preview here with the version we have on the website right now).
There was a problem hiding this comment.
Ah, good point that we don't ship the landing pages to fornax. I think I'll just remove this line entirely.
There was a problem hiding this comment.
Cross links like this could still be useful for the HTMLs.
There was a problem hiding this comment.
Because of the way we've decided to set up the landing page, the link I wanted to put here doesn't exist, and the generic "all Euclid tutorials" that I'd have to use instead is not nearly as helpful here. It's ok that the link I wanted doesn't exist. But I think it's better to just remove this line.
Re: the larger question of whether to use xrefs or relative paths, l thought we had come to a consensus a couple of months ago that relative paths are preferable in notebooks repos because they work in all the same important places that xrefs do and they also work in a couple other important places where xrefs don't. It sounds like I misunderstood your position.
2 participants
Resolves #243
Thanks for spotting this @bsipocz