nais · thokra-nav · Nov 25, 2025 · Nov 25, 2025 · Nov 25, 2025 · Nov 25, 2025
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
diff --git a/.github/workflows/deploy-pages.yml b/.github/workflows/deploy-pages.yml
@@ -0,0 +1,54 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - ds-svelte
+
+jobs:
+  build_site:
+    if: github.repository_owner == 'thokra-nav'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0 # Fetch all history for accurate git timestamps
+
+      - uses: jdx/mise-action@v3
+
+      - name: Install dependencies
+        working-directory: ./svdoc
+        run: bun i
+
+      - name: build
+        working-directory: ./svdoc
+        env:
+          BASE_PATH: "/${{ github.event.repository.name }}"
+          TENANT: "nav"
+        run: |
+          bun run build
+
+      - name: Upload Artifacts
+        uses: actions/upload-pages-artifact@v4
+        with:
+          # this should match the `pages` option in your adapter-static options
+          path: "svdoc/build/"
+
+  deploy:
+    needs: build_site
+    if: github.repository_owner == 'thokra-nav'
+    runs-on: ubuntu-latest
+
+    permissions:
+      pages: write
+      id-token: write
+
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    steps:
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v4
diff --git a/.tool-versions b/.tool-versions
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -0,0 +1,3 @@
+{
+  "editor.formatOnSave": false
+}
diff --git a/docs/README.md b/docs/README.md
@@ -5,12 +5,6 @@ hide:
   - footer
   - toc
 ---
-<!-- This hides the edit button on the start page -->
-<style>
-  .md-content__button {
-    display: none;
-  }
-</style>
 
 # :wave: **Welcome to the Nais developer documentation!**
 

diff --git a/docs/auth/README.md b/docs/auth/README.md
@@ -40,9 +40,9 @@ See the different scenarios below to identify which service(s) you need for your
 
 Depending on who your users are, you can use the following services to log them in:
 
-:person_standing: Log in _employees_ :octicons-arrow-right-24: [Entra ID]
+:standing_person: Log in _employees_ :octicons-arrow-right-24: [Entra ID]
 
-:person_standing: Log in _citizens_ :octicons-arrow-right-24: [ID-porten]
+:standing_person: Log in _citizens_ :octicons-arrow-right-24: [ID-porten]
 
 ## Validating inbound requests
 
@@ -63,9 +63,9 @@ graph TD
 
 The graph above can also be described as:
 
-:material-server::person_standing: Validate requests from _internal_ application acting on behalf of _employee_ :octicons-arrow-right-24: [Entra ID]
+:material-server::standing_person: Validate requests from _internal_ application acting on behalf of _employee_ :octicons-arrow-right-24: [Entra ID]
 
-:material-server::person_standing: Validate requests from _internal_ application acting on behalf of _citizen_:octicons-arrow-right-24: [TokenX]
+:material-server::standing_person: Validate requests from _internal_ application acting on behalf of _citizen_:octicons-arrow-right-24: [TokenX]
 
 :material-server: Validate requests from _internal_ application :octicons-arrow-right-24: [Entra ID]
 
@@ -87,9 +87,9 @@ graph TD
 
 The graph above can also be described as:
 
-:material-server::person_standing: Make requests to _internal_ API on behalf of _employee_ :octicons-arrow-right-24: [Entra ID]
+:material-server::standing_person: Make requests to _internal_ API on behalf of _employee_ :octicons-arrow-right-24: [Entra ID]
 
-:material-server::person_standing: Make requests to _internal_ API on behalf of _citizen_ :octicons-arrow-right-24: [TokenX]
+:material-server::standing_person: Make requests to _internal_ API on behalf of _citizen_ :octicons-arrow-right-24: [TokenX]
 
 :material-server: Make requests to _internal_ API :octicons-arrow-right-24: [Entra ID]
 

diff --git a/docs/auth/how-to/login.md b/docs/auth/how-to/login.md
@@ -62,7 +62,7 @@ Before you begin, ensure that you have:
     :   The client secret for your application.
 
 4. Optionally, add additional environment variables to the secret to configure the login proxy further.
-See the [Wonderwall configuration reference :octicons-link-external-16:](https://github.com/nais/wonderwall/blob/master/docs/configuration.md) for all available options.
+See the [Wonderwall configuration reference](https://github.com/nais/wonderwall/blob/master/docs/configuration.md) for all available options.
 
 ## Configure your application
 

diff --git a/docs/explanations/under-the-hood.md b/docs/explanations/under-the-hood.md
@@ -10,9 +10,9 @@ In this explanation, we will go through some of the underlying technologies we u
 
 ### Runtime implementation
 
-Each _environment_ is its own [Kubernetes :octicons-link-external-16:](https://kubernetes.io) cluster using [Google Kubernetes Engine (GKE) :octicons-link-external-16:](https://cloud.google.com/kubernetes-engine?hl=en).
+Each _environment_ is its own [Kubernetes](https://kubernetes.io) cluster using [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine?hl=en).
 
-Inside each environment, every team has their own [namespace :octicons-link-external-16:](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
+Inside each environment, every team has their own [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
 
 A namespace can contain one or more [workloads](../workloads/README.md).
 Only members of the team have access to the namespace and its resources.
@@ -33,13 +33,13 @@ In the example above, the team has an application and a job running in the `dev`
 
 All workloads are deployed in a team namespace.
 
-Every workload is isolated from _all_ other workloads with [Kubernetes network policies :octicons-link-external-16:](https://kubernetes.io/docs/concepts/services-networking/network-policies/).
+Every workload is isolated from _all_ other workloads with [Kubernetes network policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/).
 
 Access is denied by default, unless [explicitly allowed](../workloads/explanations/zero-trust.md).
 
 ## Google Cloud Platform (GCP) resources
 
-Each team has a dedicated [GCP project :octicons-link-external-16:](https://cloud.google.com/resource-manager/docs/creating-managing-projects) for _each_ environment.
+Each team has a dedicated [GCP project](https://cloud.google.com/resource-manager/docs/creating-managing-projects) for _each_ environment.
 
 When your workload requests resources e.g. a bucket, it will be provisioned in the team's project for the matching environment.
 

diff --git a/docs/persistence/opensearch/how-to/create.md b/docs/persistence/opensearch/how-to/create.md
@@ -12,7 +12,7 @@ This guide will show you how to create a OpenSearch instance for your team using
 
 ## Steps
 
-1. Open [Nais Console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) in your browser
+1. Open [Nais Console](https://console.<<tenant()>>.cloud.nais.io) in your browser
 2. Select your team
 3. Select **OpenSearch** in the sidebar menu
 4. Click the **Create OpenSearch** button

diff --git a/docs/persistence/opensearch/how-to/upgrade-major-version.md b/docs/persistence/opensearch/how-to/upgrade-major-version.md
@@ -28,7 +28,7 @@ Ensure that your workload is compatible with the new major version of OpenSearch
 
 ### 2. Upgrade the OpenSearch instance
 
-1. Open [Nais Console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) in your browser
+1. Open [Nais Console](https://console.<<tenant()>>.cloud.nais.io) in your browser
 2. Select your team
 3. Select **OpenSearch** in the sidebar menu
 4. Select the OpenSearch instance you want to upgrade

diff --git a/docs/persistence/valkey/how-to/create.md b/docs/persistence/valkey/how-to/create.md
@@ -12,7 +12,7 @@ This guide will show you how to create a Valkey instance for your team using [Na
 
 ## Steps
 
-1. Open [Nais Console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) in your browser
+1. Open [Nais Console](https://console.<<tenant()>>.cloud.nais.io) in your browser
 2. Select your team
 3. Select **Valkey** in the sidebar menu
 4. Click the **Create Valkey** button

diff --git a/docs/services/secrets/README.md b/docs/services/secrets/README.md
@@ -12,6 +12,7 @@ Secrets are kept separate from the codebase and configuration files that are usu
 There are two types of secrets on the Nais platform:
 
 <div class="grid cards" markdown>
+
 -   :construction_worker: **Platform-provided secrets**
 
     ---
@@ -22,6 +23,7 @@ There are two types of secrets on the Nais platform:
 </div>
 
 <div class="grid cards" markdown>
+
 - :technologist: **User-defined secrets**
 
     ---

diff --git a/docs/services/secrets/how-to/console.md b/docs/services/secrets/how-to/console.md
@@ -12,7 +12,7 @@ This how-to guide shows you how to create and manage a [secret](../README.md) in
 
 ## List secrets
 
-1. Open [Nais console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) in your browser
+1. Open [Nais console](https://console.<<tenant()>>.cloud.nais.io) in your browser
 2. Select your team
 3. Select the `Secrets` tab
 

diff --git a/docs/services/secrets/reference/README.md b/docs/services/secrets/reference/README.md
@@ -8,7 +8,7 @@ This is the reference documentation for [secrets](../README.md) on the Nais plat
 
 ## Console
 
-Visit [Nais Console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) to find and manage your team's user-defined secrets.
+Visit [Nais Console](https://console.<<tenant()>>.cloud.nais.io) to find and manage your team's user-defined secrets.
 
 ## Workloads
 

diff --git a/docs/tutorials/README.md b/docs/tutorials/README.md
@@ -12,10 +12,10 @@ Tutorials are lessons that focuses on _learning by doing_.
 These give you hands-on experience with various parts of Nais, where we carefully guide you each step of the way.
 
 <div class="grid cards" markdown>
--   :octicons-rocket-24:{ .lg .middle } [**Hello Nais**](./hello-nais.md)
+
+-   :rocket: [**Hello Nais**](./hello-nais.md)
 
     ---
-
     Get your first application up and running on Nais.
 
   </div>
diff --git a/docs/workloads/application/how-to/delete.md b/docs/workloads/application/how-to/delete.md
@@ -10,7 +10,7 @@ tags: [application, how-to]
 
 ## Delete your application
 
-1. Open [Nais console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) in your browser
+1. Open [Nais console](https://console.<<tenant()>>.cloud.nais.io) in your browser
 2. Select your team
 3. Select the `Apps` tab
 4. Select the application that you want to delete

diff --git a/docs/workloads/job/how-to/delete.md b/docs/workloads/job/how-to/delete.md
@@ -10,7 +10,7 @@ tags: [job, how-to]
 
 ## Delete your job
 
-1. Open [Nais console :octicons-link-external-16:](https://console.<<tenant()>>.cloud.nais.io) in your browser
+1. Open [Nais console](https://console.<<tenant()>>.cloud.nais.io) in your browser
 2. Select your team
 3. Select the `Job` tab
 4. Select the job that you want to delete

diff --git a/mise.toml b/mise.toml
@@ -0,0 +1,6 @@
+[settings]
+pin = true
+
+[tools]
+bun = "1.3.12"
+poetry = "2.0.0"
diff --git a/svdoc/.env.example b/svdoc/.env.example
@@ -0,0 +1,5 @@
+# Tenant configuration
+# The tenant name (e.g., "nav", "test-nais")
+TENANT=nav
+NOT_TENANT=not-nav
+CONTENT_STORE_LOG_LEVEL=info
diff --git a/svdoc/.gitignore b/svdoc/.gitignore
@@ -0,0 +1,23 @@
+node_modules
+
+# Output
+.output
+.vercel
+.netlify
+.wrangler
+/.svelte-kit
+/build
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Env
+.env
+.env.*
+!.env.example
+!.env.test
+
+# Vite
+vite.config.js.timestamp-*
+vite.config.ts.timestamp-*
diff --git a/svdoc/.npmrc b/svdoc/.npmrc
@@ -0,0 +1 @@
+engine-strict=true
diff --git a/svdoc/.prettierignore b/svdoc/.prettierignore
@@ -0,0 +1,9 @@
+# Package Managers
+package-lock.json
+pnpm-lock.yaml
+yarn.lock
+bun.lock
+bun.lockb
+
+# Miscellaneous
+/static/
diff --git a/svdoc/.prettierrc b/svdoc/.prettierrc
@@ -0,0 +1,15 @@
+{
+	"useTabs": true,
+	"singleQuote": false,
+	"trailingComma": "all",
+	"printWidth": 100,
+	"plugins": ["prettier-plugin-svelte", "prettier-plugin-tailwindcss"],
+	"overrides": [
+		{
+			"files": "*.svelte",
+			"options": {
+				"parser": "svelte"
+			}
+		}
+	]
+}
diff --git a/svdoc/.vscode/settings.json b/svdoc/.vscode/settings.json
@@ -0,0 +1,5 @@
+{
+	"files.associations": {
+		"*.css": "tailwindcss"
+	}
+}