-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Switch to reference style links #680
Conversation
5e11b78
to
9dfa207
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @wolf99! Thanks for this. In principal I like the idea!
However I think that we should always try to give a "proper name" to the reference links, except where the word is self-descriptive (like libsecret
) and is a simple ASCII A-Z string without punctuation*.
For example [.NET][]
should be [.NET][dotnet]
and [managed in the keychain][]
should be [managed in the keychain][macos-keychain]
.
Keeps the prose less verbose, whilst also still making the reference link section at the bottom organised, easier to scan.
*except for the many many many credential.foo
config links.. I really like the reference links here for cleaning these up!
Ha ha, I actually started out the first file or two with something very like this! 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few more links/references that I'd like to see changed from prose to a short kebab-case ID and should be good to go! Thanks 😁
There's a good few files yet to get through converting to any reference style, I haven't got to those yet but planning to add to this PR as I get the time 🙂 |
Thanks for the heads up @wolf99! No rush at all. |
1697b10
to
9164efa
Compare
Squashed commits because rebase is painful 😢 |
6001804
to
a128cae
Compare
Hey @wolf99! I see this version bump PR is failing with a few issues, some related to bare links. Wanted to reach out and see if you'd like some assistance finishing out the conversion to reference style links here? |
Hi @ldennington I have not had much time to focus on FOSS things recently 😔. |
fff626c
to
d905c6d
Compare
d905c6d
to
f472dc7
Compare
Do you think this ToC could be removed? Preference to remove it is due to the large amount of duplication that would be involved in changing these heading links to reference style links. The front matter is ~10% of the overall document.
|
I'm fine with removing it! |
Now it's ready 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a TON of work - thank you so much for doing it! ⭐
I left a couple small comments, but looks great overall!
Thanks for reviewing @ldennington. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Looks awesome 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! Thanks @wolf99 😁
Changes: - Check for broken links in documentation (#700) - Support macOS `arm64` installs via Homebrew (#798) - Validate installers before publishing (#813) - Auto-generate maintainer away notification issues (#842) - Install dotnet via Jammy feeds on Ubuntu 22.04 and greater (#839) - Access Azure storage account using service principle credentials (#851) - Update documentation to use reference-style links (#680) - Unify documentation line length (#862) - Add generic username/password UI (#871) - Bitbucket DC OAuth support (#607) - Distribute GCM as a dotnet tool (#886) - Drop `-core` suffix from entry executable #551 - Speed up build graph (#924)
Changing markdown URLs to markdown reference style links as suggested by @ldennington on #668 .
In some places, I have changed link text from strings like "here" as in
download here
to be more descriptive (and thus better URL reference IDs) likedownload at the .NET website
.Also on #668 I proposed that where
aka.ms
links are linking to other documents or files in this same repository, then they are replaced with relative links for the following benefits:@ldennington agreed with this, but requested a check with @mjcheetham (#668 (comment))
Can you confirm if you are happy with this, Mathew? If not, I will remove that from this PR.