Skip to content
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

Use Markdown reference-style links in documents. [ci skip] #696

Merged
merged 1 commit into from
Nov 25, 2023

Conversation

junaruga
Copy link
Member

I find the Markdown's reference-style links are helpful for a better readability when seeing the text file directly by an editor, or when referring to one link from multiple parts. And I see the reference-style links are used in some parts, but not in some other parts. So, I used the reference-style links for all the parts in README.md and CONTRIBUTING.md.

In the README.md, the references are written in the end of the each session. In the CONTRIBUTING.md, the references are written in the end of the file. So, I followed the existing style for each file.

I also checked all the links availability as a result, I changed the link of the [DeveloperHowTo] and removed the unused [History.md].

My idea of the references is the link item names in the reference area at the end of the file should describe what it is without ambiguity. For example, not [Security] but [Ruby Security], and not [INSTALL] but [OpenSSL INSTALL].

You can check the modified documents.


Use Markdown reference-style links due to a better readability. See https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#links for details.

@junaruga
Copy link
Member Author

I was also inspired from Sway window manager's README.md using the reference-style links.

@rhenium
Copy link
Member

rhenium commented Nov 25, 2023

Yes, we should have been consistently using one of them. Thank you!

@rhenium rhenium merged commit ee740bf into ruby:master Nov 25, 2023
@junaruga junaruga deleted the wip/doc-markdown-ref branch November 27, 2023 07:31
@junaruga
Copy link
Member Author

You are welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants