Actually this isn't related to the plugin-site but the normal website. I'm not sure if this should be Tyler or Daniel so I'll just change it to automatic and see what happens.

Right, we probably should have an option that can be set and removes the link for the few special pages that cannot be edited for whatever reason.

Same issue once we actually generate Pipeline step doc properly there.

Daniel Beck, if we were to provide an "edit" link for the generated step documentation, where would it point?

If we point to the pipeline-steps-doc-generator, I'm not sure that would be useful to a contributor like Florian Gilcher.

Would it be better to just link to the GitHub repository which contains the step, or try to navigate all the way to the source file which contains the javadocs?

To clarify, you actually want an edit link everywhere? Because what I tried to say is that we should just have a method to remove that link on certain pages, and remove it from those without a real 'source' file.

I would prefer to maintain the link in some form, everywhere, since all the content is editable somewhere, otherwise potential contributions go to /dev/null.

I'll pester Kristin Whetstone about this and see what we can come up with

Well, whether it's a boolean disable or a String sourceUrlOverride shouldn't make a huge difference from an implementation POV – both require customization of the link, and both would resolve the brokenness.

Linking somewhere useful would be preferable over just removing the link.

Marking this as done (https://github.com/jenkins-infra/jenkins.io/pull/643 )