Repository navigation
Description
While going through the vignettes in a start-to-finish or continuous manner, one thing that may pose a mild inconvenience is navigating amongst the vignettes in order, also given that the statements toward the end of those connected vignettes (.N - 1) mention continuity (as in saying '... in the next vignette ...'), and could do with links to the next one.
Since there are none, the only way for the reader to follow along (as far as I am aware of) is to either navigate back to the wiki page if following that, or back to here if following the documentation hosted on gitlab.io (and then from the 'Vignettes' dropdown, proceed to select the next one, going below one step at a time). This back-and-forth flow can be avoided.
And if not following those two starting points (highly unlikely, but could be possible), the specific order to sequentially follow among the connected vignettes is usually absent in the order they are enlisted by common commands (vignette(package="data.table"), browseVignettes("data.table"), tools::getVignetteInfo("data.table")[,3], etc.), which may be a tad confusing for beginners as to which one to jump to next (admittedly a rare case).
But again, navigating back one page and then hopping to the next one would only work assuming the reader began reading the vignette inside a browser in the first place, as going through the material within an R session (by say using vignette("datatable-intro", package="data.table”) inside RStudio) would invalidate this hyperlink to stay within, and move to the browser instead (perhaps this was a part of the rationale to not link?), although again there would be no direct way to navigate to the next vignette, and in this case even to go back to the 'Getting started' wiki or landing page for the gitlab.io hosted documentation.
Thus, I think it might be beneficial to include hyperlinks for at least transitioning between vignette chapters for user-friendliness.
Activity
tdhock commentedon Dec 18, 2023
order of vignettes on CRAN is alphabetical https://cloud.r-project.org/web/packages/data.table/
we could consider numbering the vignettes, to make them appear in a specific order. just prefix vignette name with 01 02 etc
jangorecki commentedon Dec 18, 2023
Numbering doesn't make sense because some are completely unrelated to each others. Better to just call them by the name rather than "next"/"previous".
MichaelChirico commentedon Dec 18, 2023
"Soon", R will support arbitrary vignette ordering:
https://bugs.r-project.org/show_bug.cgi?id=18576
The patch appears ready, it might be good to chime in & nudge that towards merge.
jangorecki commentedon Dec 18, 2023
@MichaelChirico question if that new feature will be backward compatible or will required to depends on R 4.4
MichaelChirico commentedon Dec 18, 2023
I guess you mean "is it an error to use this feature with an older version of R", I think worth asking in bugzilla.
ChristianWia commentedon Aug 20, 2024
so propagate also here the translation label from #6373
ChristianWia commentedon Aug 21, 2024
link value/format in standalone documents
As long as we stay in github or any cloned configuration vignettes can be bound using the directory tree but for standalone document such as an html generated by knitr or a pdf and sent in an email, there is no guarantee that the included links will still be active in the document at destination. This works for external URL leading to consider inter vignettes links as external ones (... referenced according to github repository).
jangorecki commentedon Aug 21, 2024
Vignettes are not standalone html. Using external links pointing to github will result bad linking for any non-github matching version of a package (installed from CRAN or a branch). Links have to be relative in vignettes.
HunterB433 commentedon Mar 25, 2026
Hello!
I'm interested in taking on this issue with @pizzadogsquared. It will be our first contribution to this repo, and it seems like a good first issue to warm up to the code base. I'm newer to OSS, so I'm not fully accustomed to the formalities of this process, but could a maintainer assign this issue to us to avoid duplicate work?
Sincerely, Hunter Beach
aitap commentedon Mar 26, 2026
HunterB433 commentedon Mar 26, 2026
Sounds like a good plan @pizzadogsquared and I will get on double checking : )