Fix broken links

iromanycheva-eng · iromanycheva-eng · commit cdbe928f6a6b · 2026-04-17T04:45:09.000Z
Also upgrade version of hugo and docsy
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -17,7 +17,7 @@
 6. If this PR includes a new GEP please make sure you've followed the process
    outlined in our GEP overview, as this will help the community to ensure the
    best chance of positive outcomes for your proposal:
-   https://gateway-api.sigs.k8s.io/geps/overview/#process
+   https://gateway-api.sigs.k8s.io/enhancements/overview/#process
 -->
 
 **What type of PR is this?**
diff --git a/geps/_index.md b/geps/_index.md
@@ -7,6 +7,6 @@ cascade:
     ui:
       breadcrumb_disable: false
 
-_build:
+build:
   list: never
 ---
diff --git a/geps/gep-1323/index.md b/geps/gep-1323/index.md
@@ -60,7 +60,7 @@ type HTTPHeaderModifier struct {
 
 Given the fact that this functionality is offered by only a few projects that currently implement Gateway API when using their own traffic routing CRDs, it’s better to support `ResponseHeaderModifier` as an _Extended_ feature, unlike `RequestHeaderModifier` which is a _Core_ feature. This will also not increase the difficulty of implementing Gateway API for any future ingress or service mesh.
 
-This feature can be further extended via [Policy Attachment](../../reference/policy-attachment.md). The mechanism and use cases of this may be explored in a future GEP.
+This feature can be further extended via [Policy Attachment](/reference/policy-attachment/). The mechanism and use cases of this may be explored in a future GEP.
 
 ## Usage
 Adding support for this unlocks a lot of real world use cases. Let’s review a couple of them:
diff --git a/geps/gep-1619/index.md b/geps/gep-1619/index.md
@@ -1090,7 +1090,7 @@ predicable way.
 - We need to clean up the [Implementations](#implementations) table to make it more organized and readable.
 - We need to revisit how to indicate to a user that a `BackendLBPolicy` configuration is being overridden by a route
 configuration via a warning status or log.
-    - This might require addressing as part of an update to [GEP-2648](../gep-2648/index.md).
+    - This might require addressing as part of an update to [GEP-2648](/geps/gep-2648/).
 
 ## Alternatives
 
@@ -1227,7 +1227,7 @@ Though session persistence is a ubiquitous name, session affinity is more incons
 - [LBPolicy](https://static.sched.com/hosted_files/kccnceu2023/c4/Autoscaling%20Elastic%20Kubernetes%20Infrastructure%20for%20Stateful%20Applications%20using%20Proxyless%20gRPC%20and%20Istio.pdf#page=25) (proposed extension for session persistence API)
 - [gRPC Stateful Session Affinity Proposal](https://github.com/grpc/proposal/blob/master/A55-xds-stateful-session-affinity.md) (info on session draining and session persistence in gRPC)
 - [Kube-Proxy Session Affinity](https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity)
-- [GEP-713: Metaresources and PolicyAttachment](../gep-713/index.md)
+- [GEP-713: Metaresources and PolicyAttachment](/enhancements/geps/gep-713/)
 - [RFC6265](https://www.rfc-editor.org/rfc/rfc6265)
 - [Policy Attachment](/reference/policy-attachment)
 - [Envoy Session Persistence Design Doc](https://docs.google.com/document/d/1IU4b76AgOXijNa4sew1gfBfSiOMbZNiEt5Dhis8QpYg/edit#heading=h.sobqsca7i45e)
diff --git a/geps/gep-1731/index.md b/geps/gep-1731/index.md
@@ -239,8 +239,11 @@ TODO
 
 ## API
 
-!!! warning
-    Expectations for how implementations should handle connection errors are currently UNRESOLVED due to inconsistency between data planes, including how connections are established or maintained, granularity of how different types of errors are bucketed, default behavior and expected user needs. Please see comment thread at <https://github.com/kubernetes-sigs/gateway-api/pull/3199#discussion_r1697201266> for more detail.
+{{% alert color="warning" %}}
+
+Expectations for how implementations should handle connection errors are currently UNRESOLVED due to inconsistency between data planes, including how connections are established or maintained, granularity of how different types of errors are bucketed, default behavior and expected user needs. Please see comment thread at <https://github.com/kubernetes-sigs/gateway-api/pull/3199#discussion_r1697201266> for more detail.
+
+{{% /alert %}}
 
 ### Go
 
diff --git a/geps/gep-1867/index.md b/geps/gep-1867/index.md
@@ -57,7 +57,7 @@ While there is value out of providing class-wide options as defaults, there is a
 
 Some parallels in existing APIs:
 
-[Policy Attachment](../../reference/policy-attachment.md) offers a hierarchy of defaults and overrides, allowing attachment to GatewayClass and Gateway.
+[Policy Attachment](/reference/policy-attachment/) offers a hierarchy of defaults and overrides, allowing attachment to GatewayClass and Gateway.
 This is similar to our needs here, but representing infrastructure configuration as a "Policy" is a bit problematic, and the existing mechanisms have no hierarchy.
 
 In core Kubernetes, Pods declare their requirements (for example, CPU requests) inline in the Pod resource; there is not a `ResourceClass` API that abstracts these further.
@@ -78,7 +78,7 @@ For example, if I wanted to represent a `version` field and change that to trigg
 In order to address the concerns above, I propose a standard `infrastructure` API is added to `Gateway`.
 
 The exact fields are out of scope for this GEP and will be handled by additional GEPs.
-One example GEP already depending on this is [GEP-1651](../gep-1651/index.md).
+One example GEP already depending on this is [GEP-1651](/geps/gep-1651/).
 
 The fields as defined below are, at time of writing, the existing fields covered by this GEP. More fields may be added as needed.
 
@@ -140,8 +140,11 @@ type GatewayClassInfrastructure struct {
 }
 ```
 
-!!! warning
-    Modifying pod labels via `infrastructure.labels` could result in data plane pods being replaced (depending on the implementation). The way in which the pods are replaced is implementation specific and may result in downtime. Implementations should document how they handle changes to `infrastructure.labels`.
+{{% alert color="warning" %}}
+
+Modifying pod labels via `infrastructure.labels` could result in data plane pods being replaced (depending on the implementation). The way in which the pods are replaced is implementation specific and may result in downtime. Implementations should document how they handle changes to `infrastructure.labels`.
+
+{{% /alert %}}
 
 ### API Principles
 
diff --git a/geps/gep-1897/index.md b/geps/gep-1897/index.md
@@ -143,7 +143,7 @@ This GEP is the outcome of the TLS use case #4 in
 
 ## BackendTLSPolicy is a union feature
 
-BackendTLSPolicy complies with the definition of [Union feature](../../site-src/guides/implementers.md#union-feature-conformance).
+BackendTLSPolicy complies with the definition of [Union feature](/guides/implementers/#union-feature-conformance).
 This means that this feature is used in combination with other features. Some examples:
 
 * An implementation that claims support for `GRPCRoute` and `BackendTLSPolicy` MUST support 
@@ -837,7 +837,7 @@ of the first standard Policy type.
 
 [Gateway API TLS Use Cases](https://docs.google.com/document/d/17sctu2uMJtHmJTGtBi_awGB0YzoCLodtR6rUNmKMCs8/edit#heading=h.cxuq8vo8pcxm)
 
-[GEP-713: Metaresources and PolicyAttachment](../gep-713/index.md)
+[GEP-713: Metaresources and PolicyAttachment](/geps/gep-713/)
 
 [Gateway API TLS](/guides/user-guides/tls)
 
diff --git a/geps/gep-2643/index.md b/geps/gep-2643/index.md
@@ -29,7 +29,7 @@ based on the SNI identification that should pass the traffic to N load balanced
 ## Non-Goals
 
 * Provide an interface for users to define different listeners or ports for the
-`TLSRoute` - This will be covered by the [ListenerSet enhancement](/gep-1713/index.md).
+`TLSRoute` - This will be covered by the [ListenerSet enhancement](/geps/gep-1713/).
 * When using `TLSRoute` passthrough, support `PROXY` protocol on the gateway listener.
 * When using `TLSRoute` passthrough, support `PROXY` protocol on the communication
 between the Gateway and the backend.
@@ -591,4 +591,4 @@ the field can be considered too complex.
 * [TLSRoute intersecting hostnames issue](https://github.com/kubernetes-sigs/gateway-api/issues/3541)
 * [TLSRoute termination feature request](https://github.com/kubernetes-sigs/gateway-api/issues/2111)
 * [GatewayAPI TLS Use Cases](https://docs.google.com/document/d/17sctu2uMJtHmJTGtBi_awGB0YzoCLodtR6rUNmKMCs8)
-* [Union Features](../../site-src/guides/implementers.md#union-feature-conformance)
+* [Union Features](/guides/implementers/#union-feature-conformance)
diff --git a/geps/gep-2648/index.md b/geps/gep-2648/index.md
@@ -7,10 +7,13 @@
 
 ## TLDR
 
-!!! warning
-    This GEP has been merged back into [GEP-713](/geps/gep-713/)
-    and now it's now obsolete. Please refer the original specification of Metaresources
-    and Policy Attachment for the current state of the pattern.
+{{% alert color="warning" %}}
+
+This GEP has been merged back into [GEP-713](/geps/gep-713/)
+and now it's now obsolete. Please refer the original specification of Metaresources
+and Policy Attachment for the current state of the pattern.
+
+{{% /alert %}}
 
 Describe and specify a design pattern for a class of metaresource that can
 affect specific settings across a single target object.
diff --git a/geps/gep-2649/index.md b/geps/gep-2649/index.md
@@ -7,10 +7,13 @@
 
 ## TLDR
 
-!!! warning
-    This GEP has been merged back into [GEP-713](/geps/gep-713/)
-    and now it's now obsolete. Please refer the original specification of Metaresources
-    and Policy Attachment for the current state of the pattern.
+{{% alert color="warning" %}}
+
+This GEP has been merged back into [GEP-713](/geps/gep-713/)
+and now it's now obsolete. Please refer the original specification of Metaresources
+and Policy Attachment for the current state of the pattern.
+
+{{% /alert %}}
 
 Describe and specify a design pattern for a class of metaresource that can
 affect specific settings across a multiple target objects.
diff --git a/geps/gep-709/index.md b/geps/gep-709/index.md
@@ -3,9 +3,12 @@
 * Issue: [#709](https://github.com/kubernetes-sigs/gateway-api/issues/709)
 * Status: Standard
 
-!!! note
-    This resource was originally named "ReferencePolicy". It was renamed
-    to "ReferenceGrant" to avoid any confusion with policy attachment.
+{{% alert color="note" %}}
+
+This resource was originally named "ReferencePolicy". It was renamed to
+"ReferenceGrant" to avoid any confusion with policy attachment.
+
+{{% /alert %}}
 
 ## TLDR
 
diff --git a/geps/gep-713/index.md b/geps/gep-713/index.md
@@ -333,8 +333,11 @@ spec:
 
 Policies can opt for allowing instances to target objects across Kubernetes namespaces, in which case an optional `namespace` field MUST be defined with the target reference.
 
-!!! warning
-    Although not strictly forbidden, this is in general discouraged due to [discoverability](#policy-discoverability) issues and security implications. Cross namespace references can often lead to escalation of privileges associated with the [Confused deputy problem](https://en.wikipedia.org/wiki/Confused_deputy_problem).
+{{% alert color="warning" %}}
+
+Although not strictly forbidden, this is in general discouraged due to [discoverability](#policy-discoverability) issues and security implications. Cross namespace references can often lead to escalation of privileges associated with the [Confused deputy problem](https://en.wikipedia.org/wiki/Confused_deputy_problem).
+
+{{% /alert %}}
 
 Implementations that opt for designing policies that allow for cross namespace references MUST support one of the following combined approaches, to address the security concern:
 
diff --git a/geps/gep-91/index.md b/geps/gep-91/index.md
@@ -19,7 +19,7 @@ Gateway API standard defines a `Listener` as "the concept of a logical endpoint
 * Define an API field to specify the CA Certificate within the Gateway configuration that can be used as a trust anchor to validate the certificates presented by the client.
 This use case has been highlighted in the [TLS Configuration GEP][] under segment 1 and in the [Gateway API TLS Use Cases][] document under point 7.
 * Introduce explicit client certificate validation modes that reflect common TLS behaviors (e.g., optional vs. required client certs)
-* Ensure the configuration mitigates the authentication bypass risks associated with HTTP/2 connection coalescing as described in [GEP-3567](geps/gep-3567/#interaction-with-client-cert-validation).
+* Ensure the configuration mitigates the authentication bypass risks associated with HTTP/2 connection coalescing as described in [GEP-3567](/geps/gep-3567/#interaction-with-client-cert-validation).
 
 ## Non-Goals
 * Define other fields that can be used to verify the client certificate such as the Certificate Hash.
@@ -387,6 +387,6 @@ This GEP aims to standardize this behavior as an official part of the upstream s
 [TLS Handshake Protocol]: https://www.rfc-editor.org/rfc/rfc5246#section-7.4
 [Certificate Path Validation]: https://www.rfc-editor.org/rfc/rfc5280#section-6
 [BackendTLSPolicy]: /reference/api-types/policy/backendtlspolicy
-[TLS Configuration GEP]: geps/gep-2907
+[TLS Configuration GEP]: /geps/gep-2907/
 [Gateway API TLS Use Cases]: https://docs.google.com/document/d/17sctu2uMJtHmJTGtBi_awGB0YzoCLodtR6rUNmKMCs8/edit?pli=1#heading=h.cxuq8vo8pcxm
-[GEP-3567]: /geps/gep-3567
+[GEP-3567]: /geps/gep-3567/
diff --git a/geps/gep-922/index.md b/geps/gep-922/index.md
@@ -3,11 +3,14 @@
 * Issue: [#922](https://github.com/kubernetes-sigs/gateway-api/issues/922)
 * Status: Memorandum
 
-!!! note
-    Although this GEP serves as a reference for how we developed the Gateway API
-    versioning model, it is not meant to be the current source of truth.
-    Instead, please refer to our [official Versioning
-    Policy](/docs/concepts/versioning) for the most up-to-date guidelines.
+{{% alert color="note" %}}
+
+Although this GEP serves as a reference for how we developed the Gateway API
+versioning model, it is not meant to be the current source of truth.
+Instead, please refer to our [official Versioning
+Policy](/docs/concepts/versioning) for the most up-to-date guidelines.
+
+{{% /alert %}}
 
 ## TLDR
 Each Gateway API release will be represented by a bundle version that represents
diff --git a/hack/verify-golint.sh b/hack/verify-golint.sh
@@ -28,6 +28,11 @@ mkdir -p cache
 
 failed=false
 for module in $(find . -name "go.mod" | xargs -n1 dirname); do
+  # Skip Hugo site directory as it uses Go modules for thematic mounts,
+  # but shouldn't be linted alongside core project features.
+  if [[ "${module}" == "./site" || "${module}" == ./site/* ]]; then
+    continue
+  fi
   echo "Linting ${module}"
 
   docker run --rm \
diff --git a/netlify.toml b/netlify.toml
@@ -5,10 +5,10 @@
 
 [build.environment]
     PYTHON_VERSION = "3.12"
-    GO_VERSION = "1.24.1"
+    GO_VERSION = "1.25.0"
     # node Active LTS
     NODE_VERSION = "20.20.0"
-    HUGO_VERSION = "0.148.0"
+    HUGO_VERSION = "0.160.1"
 
 # Standard Netlify redirects
 [[redirects]]
diff --git a/site/assets/scss/_styles_project.scss b/site/assets/scss/_styles_project.scss
@@ -0,0 +1,3 @@
+.td-navbar {
+  background-color: #007bff !important;
+}
diff --git a/site/content/en/contributing/enhancement-requests.md b/site/content/en/contributing/enhancement-requests.md
@@ -51,7 +51,7 @@ include reference to a discussion and/or recordings of discussion in our
 community meetings, please note that it _may_ get closed with a request to
 create an initial discussion first.
 
-[gep]: /geps/overview/
+[gep]: /enhancements/overview/
 [discussion]: https://github.com/kubernetes-sigs/gateway-api/discussions/new/choose
 [meetings]: /contributing/get-involved/#meetings
 
diff --git a/site/content/en/docs/concepts/versioning.md b/site/content/en/docs/concepts/versioning.md
@@ -18,7 +18,7 @@ point, these may graduate to the Standard release channel or be dropped from the
 API entirely.
 
 The following diagram provides a high level overview of the lifecycle of a
-feature or resource proposed by a new [GEP](/geps/overview/) (enhancement
+feature or resource proposed by a new [GEP](/enhancements/overview/) (enhancement
 proposal) in Gateway API:
 
 ```mermaid
diff --git a/site/content/en/docs/mesh/gamma.md b/site/content/en/docs/mesh/gamma.md
@@ -46,7 +46,7 @@ The simplest way to get started is to attend one of the regular Gateway API
 [service mesh]: /docs/glossary/#service-mesh
 [east/west traffic]: /docs/glossary/#eastwest-traffic
 [role-oriented]: /docs/concepts/roles-and-personas/
-[geps]: /geps/overview/
+[geps]: /enhancements/overview/
 [contributor-ladder]: /contributing/contributor-ladder/
 [meetings]: /contributing/get-involved/#meetings
 [GAMMA leads]: https://github.com/kubernetes-sigs/gateway-api/blob/main/OWNERS_ALIASES#L23
diff --git a/site/content/en/guides/user-guides/tls.md b/site/content/en/guides/user-guides/tls.md
@@ -41,7 +41,7 @@ from the client is not terminated at the Gateway, but rather passes through the
 encrypted.
 
 For upstream connections, `BackendTLSPolicy` is used, and neither listener protocol nor TLS mode apply to the
-upstream TLS configuration. `BackendTLSPolicy` is a [union feature](implementers.md#union-feature-conformance),
+upstream TLS configuration. `BackendTLSPolicy` is a [union feature](guides/implementers-guide/#union-feature-conformance),
 which means it applies to any route or filter that forwards traffic to a backend. For `HTTPRoute`, `GRPCRoute`,
 and `TLSRoute` (with `Terminate` mode), the use of `BackendTLSPolicy` enables what is commonly known as a
 connection that is terminated and then re-encrypted at the Gateway.
diff --git a/site/content/en/reference/api-types/policy/backendtlspolicy.md b/site/content/en/reference/api-types/policy/backendtlspolicy.md
@@ -89,12 +89,14 @@ flowchart LR
     service --> pod1 & pod2
 ```
 
-!!! note "Union feature"
+{{% alert color="info" title="Union Feature" %}}
 
-    While the diagram above shows an HTTPRoute, BackendTLSPolicy is a
-    [union feature](../guides/implementers.md#union-feature-conformance) and
-    works with any route type that forwards traffic to backends, including
-    GRPCRoute and TLSRoute (when in Terminate mode).
+While the diagram above shows an HTTPRoute, BackendTLSPolicy is a
+[union feature](/guides/implementers-guide/#union-feature-conformance) and
+works with any route type that forwards traffic to backends, including
+GRPCRoute and TLSRoute (when in Terminate mode).
+
+{{% /alert %}}
 
 ### Targeting backends
 
diff --git a/site/content/en/reference/policy-attachment.md b/site/content/en/reference/policy-attachment.md
@@ -17,5 +17,5 @@ A "Policy Attachment" is a specific type of _metaresource_ that can affect speci
 settings across either one object (this is "Direct Policy Attachment"), or objects
 in a hierarchy (this is "Inherited Policy Attachment").
 
-This pattern is EXPERIMENTAL, and is described in [GEP-713](../geps/gep-713/index.md).
+This pattern is EXPERIMENTAL, and is described in [GEP-713](/enhancements/geps/gep-713/index.md).
 Please see that document for technical details.
diff --git a/site/go.mod b/site/go.mod
@@ -1,9 +1,5 @@
 module github.com/kubernetes-sigs/gateway-api/site
 
-go 1.24.13
+go 1.25.0
 
-require (
-	github.com/FortAwesome/Font-Awesome v0.0.0-20241216213156-af620534bfc3 // indirect
-	github.com/google/docsy v0.13.0 // indirect
-	github.com/twbs/bootstrap v5.3.8+incompatible // indirect
-)
+require github.com/google/docsy v0.14.3 // indirect
diff --git a/site/go.sum b/site/go.sum
@@ -1,6 +1,4 @@
-github.com/FortAwesome/Font-Awesome v0.0.0-20241216213156-af620534bfc3 h1:/iluJkJiyTAdnqrw3Yi9rH2HNHhrrtCmj8VJe7I6o3w=
 github.com/FortAwesome/Font-Awesome v0.0.0-20241216213156-af620534bfc3/go.mod h1:IUgezN/MFpCDIlFezw3L8j83oeiIuYoj28Miwr/KUYo=
-github.com/google/docsy v0.13.0 h1:Y1oy5SmQ0ikJJsvkuefEVZMj0MTXLmVfpXbt7Ytc7rc=
-github.com/google/docsy v0.13.0/go.mod h1:1Fj1W1O3esZh7IBQ8XAYtxtg10udBXuGI89+LUQc1AU=
-github.com/twbs/bootstrap v5.3.8+incompatible h1:eK1fsXP7R/FWFt+sSNmmvUH9usPocf240nWVw7Dh02o=
+github.com/google/docsy v0.14.3 h1:4uFgPWTPj4NT79IboVkXGi49LLQadLVfU4WNOfD/s74=
+github.com/google/docsy v0.14.3/go.mod h1:1Fj1W1O3esZh7IBQ8XAYtxtg10udBXuGI89+LUQc1AU=
 github.com/twbs/bootstrap v5.3.8+incompatible/go.mod h1:fZTSrkpSf0/HkL0IIJzvVspTt1r9zuf7XlZau8kpcY0=
diff --git a/site/hugo.toml b/site/hugo.toml
@@ -42,13 +42,14 @@ defaultContentLanguage = "en"
   copyright = "The Linux Foundation"
   github_repo = "https://github.com/kubernetes-sigs/gateway-api"
   github_branch = "main"
-  github_subdir = "content" # Set this to wherever your markdown files live
+  github_subdir = "site/content/en" # Set this to wherever your markdown files live
 
   # Search settings
   offlineSearch = true
   
   # User Interface settings
   [params.ui]
+    navbar_theme = "dark"
     # Enable to make the sidebar menu foldable.
     sidebar_menu_foldable = true
     # Enable to show the side bar menu in its compact state.
diff --git a/site/static/_redirects b/site/static/_redirects
@@ -27,4 +27,3 @@
 
 
 
-
