-
Notifications
You must be signed in to change notification settings - Fork 92
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
Clean up links.md #31
Comments
So, is this going to be a file with lots of entries like:
So that markdown links elsewhere can take the form It would be good to articulate some policy around:
I also just read that you can use reference style links with just the link text, which is pretty interesting. I suspect that if a link gets used often enough to set up for reference style links, we might also be able to label it with link text that is what you want ~90% of the time. To be clear, continuing the above example, I think that means that this definition:
would allow inline links like |
Oh wow, just in case it baffles anyone else. This file: https://github.com/rstudio-education/stat545/blob/master/links.md must be viewed on GitHub as raw. Otherwise it renders as markdown and there's nothing visible to look at. So this: https://raw.githubusercontent.com/rstudio-education/stat545/master/links.md |
Yes, exactly. This is what the
I think that this sounds good, I can add this to the top of
I just tested this in a practice bookdown and it seems to work the way you suggested! I will incorporate that into this bookdown. |
@jennybc What do you think of this set up? If a link appears in 2 or more
Otherwise, put it at the end of the
So for example:
Using numbers instead of labels would make it easy to distinguish between which are "global" links and which aren't. My only worry with using a mixture of inline style links (i.e. |
I think for things that appear to be a one-off (one usage in one file) at the time of writing, inline or reference-style is acceptable. You're right that reference-style has some maintenance advantages, but it has other disadvantages re: readability and not concentrating info in one place, which is nice when writing. Not sure either is globally optimal. I like your proposal and rationale for the single-file reference-style links, i.e. to use the numbers as an additional signal re: where the link is defined. Also 👍 on the proposal for multi-file links in |
Oops nevermind, using numbers for the reference-style links won't work in bookdown 😕 . I tested it out and the labels have to be unique across all of the So the revised set up: If a link appears in 2 or more
If it appears in only one
If it appears in only one
|
Looking good. I'll expand on a few things. I think you should record these "attitudes" somewhere ... maybe initiate a contributing guide in the appendix? It's OK if it feels half-baked and only has this section at first. Still an improvement.
Yeah, but spell out the idea is that the
I'd signal that this is acceptable. But a reference-style link, in that file or in
Yeah, but it's contributor's discretion whether to include in |
High-level advice: imagine yourself reviewing a PR and something's not quite right with the link style. I want to be able to link to a specific section of a specific appendix page that tells someone how we think about this. |
File to edit: https://github.com/rstudio-education/stat545/blob/master/links.md (must be viewed on GitHub as raw to see the contents! See here)
Only include links that are used in at least two
.Rmds
Look into a way to save base urls that appear multiple times as strings to recycle - e.g.https://happygitwithr.com/install-git.html
,https://happygitwithr.com/git-client.html
Change CRAN link from
https://cran.r-project.org
-->https://cloud.r-project.org
Use rdrr.io instead of rdocumentation.org -- Use rdrr.io instead of rdocumentation.org #29
Standardize formatting of link references in
.Rmds
Formalize the link reference formatting rules & add in a Contributing Guidelines section in the Appendix
The text was updated successfully, but these errors were encountered: