Fix external links, add github action

Author: rikatz

.github/workflows/verify-broken-links.yml

@@ -0,0 +1,21 @@
+name: Verify docs broken links
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+
+# Remove all permissions from GITHUB_TOKEN except metadata.
+permissions: {}
+
+jobs:
+  verify-docs:
+    name: Build website and run lychee
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # tag=v6.0.1
+        with:
+          persist-credentials: false
+      - name: Run validation
+        run: |
+          make verify-docs

Makefile

@@ -201,7 +201,7 @@ build-docs: update-geps api-ref-docs
 
 .PHONY: verify-docs
 verify-docs: build-docs
-	docker run -it --rm -w /input -v ${PWD}:/input $(DOCS_VERIFY_CONTAINER_IMAGE) --root-dir /input/site --exclude-path "overrides/partials/.*\.html" --exclude ".*" --include "k8s.io" --include "kubernetes.io" --include "github.com" /input/site/**/*.html
+	docker run -it --rm -w /input -v ${PWD}:/input $(DOCS_VERIFY_CONTAINER_IMAGE) --root-dir /input/site --exclude-path "overrides/partials/.*\.html" --exclude ".*" --include "k8s.io" --include "kubernetes.io" --include "github.com/kubernetes" /input/site/**/*.html
 
 .PHONY: build-docs-netlify
 build-docs-netlify: update-geps api-ref-docs

geps/gep-2162/index.md

@@ -28,7 +28,7 @@ This GEP proposes to enhance the [GatewayClassStatus](https://github.com/kuberne
 
 The current [GatewayClassStatus](https://github.com/kubernetes-sigs/gateway-api/blob/f2cd9bb92b4ff392416c40d6148ff7f76b30e649/apis/v1beta1/gatewayclass_types.go#L185) is only used to store conditions the controller publishes.
 
-Partnered with the [Conformance Profiles](https://github.com/kubernetes-sigs/gateway-api/blob/main/geps/gep-1709.md) work, we want to:
+Partnered with the [Conformance Profiles](/geps/gep-1709/) work, we want to:
 
 1. Improve UX by enabling users to easily see what features the implementation(GatewayClass) support.
 1. Standardize features and conformance tests names.
@@ -162,15 +162,15 @@ Before we make the changes we need to;
 
 ### Re-using ConformanceProfiles structs
 
-We could use the same structs as we do in conformance profile object, more specifically, the [ProfileReport](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/apis/v1alpha1/profilereport.go#LL24C6-L24C19) struct.
+We could use the same structs as we do in conformance profile object, more specifically, the [ProfileReport](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/apis/v1/conformancereport.go#LL28C6-L28C19) struct.
 
 Though it would be nice to have only one place to update, these structs seems to include much more data relevant to the conformance report but not for our use case.
 
 That said, conformance profiles are still at experimental stage, we could explore the option to create a shared struct that will be used both for the conformance reports and for the GatewayClass status.
 
 ### Instruct users to read from the future conformance profiles report
 
-The current plan for conformance profiles is to also include centralized reporting. (more info in [gep-1709](https://github.com/kubernetes-sigs/gateway-api/blob/main/geps/gep-1709.md))
+The current plan for conformance profiles is to also include centralized reporting. (more info in [gep-1709](/geps/gep-1709/))
 We could wait for this to be implemented and instruct users to read from that source to determine what features their installed GatewayClass support.
 
 However, having the supported features published in the GatewayClass Status adds the following values:

hack/mkdocs/generate.sh

@@ -43,8 +43,7 @@ for i in "${arr[@]}"; do
     tmpdir=$(mktemp -d --tmpdir=${PWD}/tmp)
 
     git fetch ${REMOTE} ${i} || 
-	    echo "You need a git remote pointing to upstream for API Ref generation.";
-            echo "To solve this issue locally, execute 'git remote add upstream [email protected]:kubernetes-sigs/gateway-api.git' and then call the script again with 'REMOTE=upstream <command>'"
+	    echo "You need a git remote pointing to upstream for API Ref generation. To solve this issue locally, execute 'git remote add upstream [email protected]:kubernetes-sigs/gateway-api.git' and then call the script again with 'REMOTE=upstream <command>'"
     git --work-tree=${tmpdir} checkout ${REMOTE}/${i} -- apis apisx
 
     # Start removing any "release-" prefix from docpath

site-src/blog/2022/graduating-to-beta.md

@@ -175,7 +175,7 @@ If there's something on this list you want to get involved in, or there's
 something not on this list that you want to advocate be on the roadmap
 please join us in the #sig-network-gateway-api channel on Kubernetes Slack or our weekly [community calls](../../contributing/index.md#meetings).
 
-[gep1016]:https://github.com/kubernetes-sigs/gateway-api/blob/master/geps/gep-1016.md
+[gep1016]:/geps/gep-1016/
 [grpc]:https://grpc.io/
 [pr1085]:https://github.com/kubernetes-sigs/gateway-api/pull/1085
 [tcpr]:https://github.com/kubernetes-sigs/gateway-api/blob/main/apis/v1alpha2/tcproute_types.go