Fix broken links (#7185)

* fix some broken links

* add ebook3-opengraph - use correct svg

content/blog/2018/09/2018-09-18-automatically-upgrading-with-evergreen.adoc

@@ -17,7 +17,7 @@ be sharing more details on the philosophy behind Jenkins Evergreen, show off
 how far we have come, and discuss where we're going with this radical
 distribution of Jenkins.
 
-image:/images/evergreen/magician_256.png[Jenkins Evergreen, role=center, float=right]
+image:/images/logos/magician/256.png[Jenkins Evergreen, role=center, float=right]
 
 As discussed in my first blog post, and
 link:https://github.com/jenkinsci/jep/tree/master/jep/300[JEP-300],

content/blog/2019/10/2019-10-21-plugin-docs-on-github.adoc

@@ -100,7 +100,7 @@ Migrating documentation:
 
 
 If you have any questions about contributing to the documentation, 
-please see link:/participate/#document[this page] or reach out to us in the link:https://app.gitter.im/#/room/#jenkins/docs:matrix.org[Docs SIG Gitter chat].
+please see link:/participate/\#document[this page] or reach out to us in the link:https://app.gitter.im/#/room/#jenkins/docs:matrix.org[Docs SIG Gitter chat].
 
 
 

content/blog/2020/10/2020-10-28-election-candidates.adoc

@@ -95,7 +95,7 @@ https://devopsworldjenkinsworld2018.sched.com/event/FD6C/auto-cascading-security
 Justin Harringa and I wrote and open sourced the https://plugins.jenkins.io/config-driven-pipeline/[Config Driven Pipeline Plugin].
 For two years running, I've been a mentor for two Google Summer of Code projects:
 link:/blog/2020/06/27/external-fingerprint-storage/[External Fingerprint Storage Project] and
-link:./projects/gsoc/2019/remoting-over-apache-kafka-docker-k8s-features/[Remoting over Apache Kafka with Kubernetes features].
+link:/projects/gsoc/2019/remoting-over-apache-kafka-docker-k8s-features/[Remoting over Apache Kafka with Kubernetes features].
 
 
 With this nomination, I hope to continue helping strengthen and

content/blog/2021/07/2021-07-31-remoting-monitoring-phase-1.adoc

@@ -11,7 +11,7 @@ authors:
 description: >
   Remoting Monitoring: Summary of coding phase 1 of Google Summer of Code
 opengraph:
-  image: /images/post-images/2021-07-31-remoting-monitoring-phase-1/remoting-monitoring-phase-1-opengraph.png
+  image: /images/post-images/2021-07-31-remoting-monitoring-phase-1/opengraph.png
 ---
 
 image:/images/post-images/2021-07-31-remoting-monitoring-phase-1/opengraph.png[Remoting Monitoring with OpenTelemetry]

content/blog/2022/12/2022-12-27-run-jenkins-agent-as-a-service.adoc

@@ -219,7 +219,7 @@ curl -sO http://my_ip:8080/jnlpJars/agent.jar
 java -jar agent.jar -jnlpUrl http://my_ip:8080/computer/My%20New%20Ubuntu%2022%2E04%20Node%20with%20Java%20and%20Docker%20installed/jenkins-agent.jnlp -secret my_secret -workDir "/home/jenkins"
 ----
 
-image:/images/post-images/2022-12-02-run-jenkins-agent-as-a-service/curl-and-java-launch-agent.svg[Terminal,title="New agent starting"]
+image:/images/post-images/2022-12-27-run-jenkins-agent-as-a-service/curl-and-java-launch-agent.svg[Terminal,title="New agent starting"]
 
 You can now go back into Jenkins’ UI, select the *Back to List* menu item on the left side of the screen, and see that your new agent is running.
 

content/blog/2023/07/10/2023-07-10-jenkins-june-newsletter.adoc

@@ -43,7 +43,7 @@ There is no new security release per se for Jenkins Core, but an advisory and as
 * Special thanks to the GitHub Security Lab for their reports
 ** This is the second time in a row that vulnerabilities they reported were corrected in the advisory.
 ** Kudos to Alvaro Muñoz and Tony Torralba for their work on this.
-** In collaboration with them, the Jenkins Security team will improve the link:blog/2020/11/04/codeql/[CodeQL scanning tool].
+** In collaboration with them, the Jenkins Security team will improve the link:/blog/2020/11/04/codeql/[CodeQL scanning tool].
 
 
 [[Governance]]
@@ -132,10 +132,10 @@ image:/images/post-images/2023/02/07/2023-02-07-jenkins-newsletter/documentation
 Contributed by: author:kmartens27[Kevin Martens]
 
 During the month of June, three blog posts were published on the Jenkins blog.
-This included the link:blog/2023/06/20/jenkins-may-newsletter/[May newsletter], an link:blog/2023/06/22/mirrors-jenkins-new-IP/[update announcement for Jenkins mirrors], and instructions on link:blog/2023/06/20/remove-outdated-plugins-while-using-docker/[removing deprecated plugins from Jenkins when using Docker].
+This included the link:/blog/2023/06/20/jenkins-may-newsletter/[May newsletter], an link:/blog/2023/06/22/mirrors-jenkins-new-IP/[update announcement for Jenkins mirrors], and instructions on link:/blog/2023/06/20/remove-outdated-plugins-while-using-docker/[removing deprecated plugins from Jenkins when using Docker].
 
 The documentation has also started to transition to using Java 17 in the installation documentation for various platforms.
-The link:doc/book/installing/linux/[Linux installation documentation] has been updated accordingly and includes a note regarding the Debian 12 release (as it does not deliver OpenJDK 11).
+The link:/doc/book/installing/linux/[Linux installation documentation] has been updated accordingly and includes a note regarding the Debian 12 release (as it does not deliver OpenJDK 11).
 This note will be present on any page that is part of the transition so that users are aware of the updates.
 
 As always, we appreciate all the documentation contributions from new and existing users.

content/blog/2023/07/22/2023-07-22-gsoc-2023-midterm.adoc

@@ -45,7 +45,7 @@ Following my mentors' advice, I began by writing test cases to accurately reprod
 During the implementation, I utilized the JGit library and familiarized myself with its features.
 However, I encountered some challenges due to a lack of depth in Git concepts, which required me to delve deeper and strengthen my understanding of Git concepts along the way.
 
-Read the link:blog/2023/07/16/unreleased-production-changes-probe.adoc[unreleased production changes] blog post for more details on the probe.
+Read the link:/blog/2023/07/16/unreleased-production-changes-probe[unreleased production changes] blog post for more details on the probe.
 
 === The Third-Party Repository Detection Probe
 
@@ -61,7 +61,7 @@ Certain edge-case scenarios were not initially taken into account while specifyi
 
 Throughout the process, I extensively read the Maven documentation to gain a better understanding of how to test POM structure, inheritance, and Maven API.
 
-Read the link:blog/2023/07/20/third-party-repository-detection-probe.adoc[third party repository detection probe] blog post for more details on the probe.
+Read the link:/blog/2023/07/20/third-party-repository-detection-probe[third party repository detection probe] blog post for more details on the probe.
 
 === GitHub Security Scan Workflow Probe
 
@@ -77,7 +77,7 @@ Throughout this process, I have gained knowledge in leveraging the class hierarc
 
 The findings of this probe will be highly beneficial to the security team, as it helps identify any gaps and enables the improvement of the overall security of the Jenkins plugin ecosystem.
 
-Read the link:blog/2023/07/16/security-scan-probe-blog.adoc[security scan probe] blog post for more details on the probe.
+Read the link:/blog/2023/07/16/security-scan-probe-blog[security scan probe] blog post for more details on the probe.
 
 === What about the second-half of GSoC?
 

content/blog/2023/08/24/2023-08-24-gitlab-plugin-modernization-report.adoc

@@ -68,7 +68,7 @@ The results of this phase will be showcased in in the Final Presentation in the
 == Acknowledgments
 
 My gratitude knows no bounds that I got the opportunity to contribute to such impactful project under Google Summer of Code with such kind mentors.
-I would like to thank my mentors, link:/blog/authors/krisstern/[Kris Stern] and link:/blog/authors/MarkEWaite/[Mark Waite] for their constant support and guidance throughout the project.
+I would like to thank my mentors, link:/blog/authors/krisstern/[Kris Stern] and link:/blog/authors/markewaite/[Mark Waite] for their constant support and guidance throughout the project.
 They put in a lot of effort in interactively testing the migrated plugin and providing me with valuable feedback.
 They never let me be stuck in any difficulty for too long and always helped me in finding the solution to the problem.
 I would also like to thank link:/blog/authors/basil/[Basil Crow] for the guidance he provided me with during the initial phase of the project, which helped the team shape the project.

content/blog/2023/09/20/2023-09-20-renovate-bot-probe-blog.adoc

@@ -43,7 +43,7 @@ Implementing the solution with the correct class design was a major challenge wh
 
 == Outcome and Conclusion
 
-Having implemented a similar class in the link:../../07/16/2023-07-16-security-scan-probe-blog.adoc[Security Scan] probe, this probe was easy to complete.
+Having implemented a similar class in the link:/blog/2023/07/16/security-scan-probe-blog/[Security Scan] probe, this probe was easy to complete.
 The probe has been successfully merged and pushed into production.
 The probe will help identify usage of Renovate in plugins.
 

content/doc/developer/publishing/releasing-cd.adoc

@@ -2,7 +2,7 @@
 title: Setting up automated plugin release
 layout: developer
 references:
-- url: /jep/229
+- url: https://github.com/jenkinsci/jep/blob/master/jep/229/README.adoc
   title: 'JEP-229: Continuous Delivery of Jenkins Components and Plugins'
 ---
 

content/doc/developer/publishing/requesting-hosting.adoc

@@ -29,7 +29,7 @@ If your repository already has a significant number of forks, issues, pull reque
 Log in to link:https://github.com/[GitHub] and create a new issue link:https://github.com/jenkins-infra/repository-permissions-updater/issues/new?assignees=&labels=hosting-request&template=1-hosting-request.yml[in the repository-permissions-updater] repository.
 Make sure to fill out all fields as described.
 
-A member of the link:../../../project/teams/hosting.adoc[Hosting team] will review your request within a few days.
+A member of the link:/project/teams/hosting[Hosting team] will review your request within a few days.
 If any changes are requested, please implement them.
 
 Once all requirements have been satisfied, your repository will be forked into the `jenkinsci` organization and you will be invited to join it.

content/events/fosdem/archive/2020.adoc

@@ -15,7 +15,7 @@ Jenkins project has participated in FOSDEM 2020.
 This event is coordinated by the link:/sigs/advocacy-and-outreach/[Jenkins Advocacy and Outreach SIG].
 Current plan:
 
-* **Jan 30** - Jenkins Pipeline Fundamentals training led by link:/blog/authors/MarkEWaite/[Mark Waite] (link:https://www.eventbrite.com/e/jenkins-pipeline-fundamentals-training-tickets-87080214265[Register here])
+* **Jan 30** - Jenkins Pipeline Fundamentals training led by link:/blog/authors/markewaite/[Mark Waite] (link:https://www.eventbrite.com/e/jenkins-pipeline-fundamentals-training-tickets-87080214265[Register here])
 * **Jan 31** - Jenkins Contributor Summit (link:https://www.meetup.com/jenkinsmeetup/events/267684785/[RSVP here])
 ** This is a small event for active contributors and those who are interested in working on foundation projects: key architecture changes (UX, JCasC, Cloud native Jenkins, etc.), governance and infrastructure
 * **Feb 01-02** - Conference dates (no registration needed)