Ensure new content introduced doesn't use hard links to jenkins.io

[NotMyFault]

Description:

Linking to other pages within the documentation is done like link:/projects/jcasc/. In this example, the target URL rendered on jenkins.io leads to https://www.jenkins.io/projects/jcasc/ Using the first figure ensures pages are resolved against the domain URL, regardless of the domain they are deployed at. For example, local deployment, netlify preview, etc.

Problem:

Occasionally, people use hard links like https://www.jenkins.io/projects/jcasc/ in AsciiDoc files. If you preview your changes made on netlify, the target URL leads to jenkins.io and redirects outside the domain you are currently at.

Solution:

I'm open for technical drafts and ideas. I didn't think too much about it yet, but a make target that checks if a file modified matches a certain condition could do the trick. No reason to overcomplicate this.