-
Notifications
You must be signed in to change notification settings - Fork 9.1k
3.1.1: improved RFC section links #3973
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
3.1.1: improved RFC section links #3973
Conversation
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.
Looks good. 👍
I think this looks good, but I'm not sure how someone reading the markdown source can use these links. Are they just expected to know where to look for the replacements in our build scripts, or is there a better way to tackle it? |
If you mean ReSpec references like is unrelated to [[JSON-Schema-2020-12|JSON Schema]]. then the answer unfortunately is
In this example the answer is https://www.specref.org/?q=JSON-Schema-2020-12. Current assumption is
We can keep the markdown "reader-friendly" and educate editors to (1) stick to reference patterns recognized by the build script, and (2) adjust the build script for any new external reference that is not an RFC. Which way do we want to go? |
Discussion in TDC this week, we are overall not concerned about the destination of the hyperlinks being behind another level of abstraction |
…ed-RFC-section-links
…ed-RFC-section-links
Closed in favor of #3996 |
#section-x
instead of#autoid-y
or#page-z