diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
index 087a0db..1fed689 100644
--- a/.github/workflows/links.yml
+++ b/.github/workflows/links.yml
@@ -19,17 +19,13 @@ jobs:
 
       - name: Build
         if: github.event_name == 'pull_request'
-        run: hugo --minify
-
-      - name: Serve
-        if: github.event_name == 'pull_request'
-        run: python3 -m http.server 8080 --directory public &
+        run: hugo --minify --destination public/docs
 
       - name: Check Links (PR)
         if: github.event_name == 'pull_request'
         uses: lycheeverse/lychee-action@v2
         with:
-          args: --config lychee.toml --base-url 'http://localhost:8080' --verbose --no-progress './public/**/*.html'
+          args: --config lychee.toml --root-dir '${{ github.workspace }}/public' --include '^file://' --verbose --no-progress './public/**/*.html'
 
       - name: Check Links (Scheduled)
         if: github.event_name == 'schedule'
diff --git a/content/references/datatypes/range.md b/content/references/datatypes/range.md
index bee7ce6..764a439 100644
--- a/content/references/datatypes/range.md
+++ b/content/references/datatypes/range.md
@@ -7,12 +7,12 @@ The range types are a convenient way to define a range of values between two bou
 
 CedarDB supports ranges with the following bound types:
 
-- `int4range` (range of [`int`](../integer.md))
-- `int8range` (range of [`bigint`](../integer.md))
-- `numrange` (range of [`bignumeric(38,6)`](../numeric.md))
-- `daterange` (range of [`date`](../date.md))
-- `tsrange` (range of [`timestamp`](../timestamp.md) without time zone)
-- `tstzrange` (range of [`timestamptz`](../timestamp.md))
+- `int4range` (range of [`int`](../integer/))
+- `int8range` (range of [`bigint`](../integer/))
+- `numrange` (range of [`bignumeric(38,6)`](../numeric/))
+- `daterange` (range of [`date`](../date/))
+- `tsrange` (range of [`timestamp`](../timestamp/) without time zone)
+- `tstzrange` (range of [`timestamptz`](../timestamp/))
 
 ## Usage example
 
@@ -97,6 +97,6 @@ Appletree | [2,13) -- The upper bound has been canonicalized
 In PostgreSQL, canonicalization is only applied to `int4range`, `int8range` and `daterange`.
 In CedarDB, this is possible for all range types.
 
-CedarDB restricts the precision and scale of [`numerics`](../numeric.md) for performance reason.
+CedarDB restricts the precision and scale of [`numerics`](../numeric/) for performance reason.
 As the `numeric` datatype is used for the bound values of `numranges`, the restrictions apply here as well.
 In this case, CedarDB stores the bounds as `bignumeric(38,6)`.
diff --git a/data/releasenotes.json b/data/releasenotes.json
index d4f5dfa..fad4b6a 100644
--- a/data/releasenotes.json
+++ b/data/releasenotes.json
@@ -2863,7 +2863,7 @@
 			},
 			{
 				"type": "feat",
-				"note": "Add support for most <tt>information_schema</tt> tables, as defined by the SQL standard. You can see the implementation progress <a href=../compatibility/backend>here</a>."
+				"note": "Add support for most <tt>information_schema</tt> tables, as defined by the SQL standard. You can see the implementation progress <a href=../compatibility/system_table/>here</a>."
 			},
 			{
 				"type": "feat",
@@ -3887,11 +3887,11 @@
 			},
 			{
 				"type": "feat",
-				"note": "Added support for <a href=/docs/references/sqlreference/statements/upsert target=_blank>upserts</a> through <tt>ON CONFLICT DO UPDATE</tt> and <tt>ON CONFLICT DO NOTHING</tt>."
+				"note": "Added support for <a href=../references/dml/upsert/ target=_blank>upserts</a> through <tt>ON CONFLICT DO UPDATE</tt> and <tt>ON CONFLICT DO NOTHING</tt>."
 			},
 			{
 				"type": "feat",
-				"note": "Added support for additional <a href=/docs/references/sqlreference/functions/aggregation/ target=_blank>aggregation functions</a>."
+				"note": "Added support for additional <a href=../references/functions/aggregation/ target=_blank>aggregation functions</a>."
 			},
 			{
 				"type": "fix",