Gregsdennis/external links #1568
Conversation
There was a problem hiding this comment.
Reference style links might be a good choice for this. Especially if we end up making the same reference in multiple places.
## Blah
Blah, blah, [JSON Pointer][RFC6901], blah.
### Again
Some other reference to [JSON Poiner][RFC6901] elsewhere in the spec.
<!-- Reference links can go in one place at the bottom -->
[RFC6901]: https://www.rfc-editor.org/info/rfc6901
gregsdennis
force-pushed
the
gregsdennis/external-links
branch
from
146285b to
a3ba78a
Compare
|
Alright I think that's it for the primary changes of this PR. The only thing left is figuring out cross-document links. @jdesrosiers I'm not sure whether you want to support that as part of this PR. Alternatives are we merge this in the broken state or it gets supported in another PR and this is rebased. I'm happy with either, really, but the latter seems more proper. |
There was a problem hiding this comment.
Everything looks good so far.
The only thing left is figuring out cross-document links.
I don't think there's an easy way around this problem. I'm going to take another look, but if I don't find anything in a relatively short amount of time, I think we should merge this. It really bothers me to commit something that's breaking the build, but it might be all we can do right now.
|
I just remembered a solution I had in mind that I want to write down so I don't forget again. I think the best approach is to write links to the |
|
Rewriting the links was easy and works out great. Not only does it make the link checker work, but it also allows links to work both in Github, not just when built to HTML. |
What kind of change does this PR introduce?
editorial
Issue & Discussion References
Summary
Inline all of the links to external documents and remove the associated appendix.
Does this PR introduce a breaking change?
No