fix(docker): normalize container CPU usage

.agents/skills/documentation-sync/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-sync
-description: Keep Homarr's Fumadocs documentation aligned with user-facing code. Use when adding or changing integrations, widgets, APIs, environment variables, CLI commands, authentication, permissions, cron jobs, settings, or UI behavior that users must understand.
+description: Keep Homarr's Docusaurus documentation aligned with user-facing code. Use when adding or changing integrations, widgets, APIs, environment variables, CLI commands, authentication, permissions, cron jobs, settings, or UI behavior that users must understand.
 ---
 
 # Documentation Sync
@@ -48,4 +48,4 @@ For a widget:
 2. Keep names, defaults, paths, screenshots, links, and prerequisites consistent with code.
 3. Update every affected page and remove superseded guidance.
 4. Run the narrowest useful docs validation. Use `pnpm turbo build --filter=@homarr/docs` when links, MDX, generated definitions, or navigation can fail; otherwise run the docs package formatter on touched files.
-5. Treat broken links and anchors as failures; run `pnpm --filter @homarr/docs validate:links` after the static build.
+5. Treat broken links and anchors as failures; Docusaurus checks them strictly.

.env.example

@@ -1,24 +1,22 @@
 # Since .env is gitignored, you can use .env.example to build a new `.env` file when you clone the repo.
-# Keep this file up-to-date when you add new variables to `.env`.
+# Keep this file up-to-date when you add new variables to \`.env\`.
 
 # This file will be committed to version control, so make sure not to have any secrets in it.
 # If you are cloning this repo, create a copy of this file named `.env` and populate it with your secrets.
 
-# Generate two different 64-character hex values with `openssl rand -hex 32` before starting Homarr.
-# Never reuse these values or commit the populated `.env` file.
-AUTH_SECRET=
+# The below secret is not used anywhere but required for Auth.js (Would encrypt JWTs and Mail hashes, both not used)
+AUTH_SECRET="supersecret"
 
 # The below secret is used to encrypt integration secrets in the database.
-# Homarr will reject an empty or invalid value and print a randomly generated candidate.
-SECRET_ENCRYPTION_KEY=
+# It should be a 32-byte string, generated by running `openssl rand -hex 32` on Unix
+# or starting the project without any (which will show a randomly generated one).
+SECRET_ENCRYPTION_KEY=0000000000000000000000000000000000000000000000000000000000000000
 
 LOG_LEVEL='info'
 
 # This is how you can use the sqlite driver:
 DB_DRIVER='better-sqlite3'
-# Safe local source-development path. SQLite files are ignored by Git.
-# Container images use /appdata/db/db.sqlite by default instead.
-DB_URL='./db.sqlite'
+DB_URL='FULL_PATH_TO_YOUR_SQLITE_DB_FILE'
 
 # Those are the two ways to use the mysql2 driver:
 # 1. Using the URL format:
@@ -65,8 +63,6 @@ UNSAFE_ENABLE_MOCK_INTEGRATION=true
 
 # Public URL contract. Values must be absolute HTTP(S) URLs without credentials,
 # query strings, or fragments. Trailing slashes are normalized at startup.
-# Public Homarr origin used by MCP OAuth metadata and redirects behind proxies.
-# BASE_URL=https://homarr.example.com
 HOMARR_WEBSITE_URL=https://homarr.dev
 # PocketBase API used by Homarr and by the standalone documentation site.
 # Defaults to HOMARR_WEBSITE_URL.

.github/pull_request_template.md

@@ -4,14 +4,14 @@
   <h3>Homarr</h3>
 </div>
 
-**Thank you for your contribution. Please ensure that your pull request meets the following requirements:**
+**Thank you for your contribution. Please ensure that your pull request meets the following pull request:**
 
-- [ ] Relevant checks pass without warnings or errors
-- [ ] Pull request targets the intended base branch (`dev` by default; `release/v2` for v2 release work)
+- [ ] Builds without warnings or errors (`pnpm build`, autofix with `pnpm format:fix`)
+- [ ] Pull request targets `dev` branch
 - [ ] Commits follow the [conventional commits guideline](https://www.conventionalcommits.org/en/v1.0.0/)
-- [ ] No shorthand variable names are used (for example, `x`, `y`, `i`, or abbreviations)
-- [ ] User-facing changes include matching documentation updates under `apps/docs`
-- [ ] When using AI, no temporary files are checked in and the code style follows the rest of the project
+- [ ] No shorthand variable names are used (eg. `x`, `y`, `i` or any abbrevation)
+- [ ] Documentation is up to date. Create a pull request [here](https://github.com/homarr-labs/documentation/).
+- [ ] When using AI; No temp files are checked in, the code style follows the rest of the project
 
 **When contributing a new integration or widget:**
 

.github/workflows/bot-auto-merge-reconcile.yml

@@ -20,7 +20,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_APPROVE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
           permission-pull-requests: write # required to enable auto-merge
 
       - name: Install GitHub CLI

.github/workflows/bot-pr-automerge.yml

@@ -28,7 +28,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_APPROVE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
           permission-pull-requests: write # required to approve a pull request and enable auto-merge
 
       - name: Install GitHub CLI

.github/workflows/crowdin-schedule-download.yml

@@ -22,7 +22,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.CROWDIN_APP_PRIVATE_KEY }}
-          client-id: ${{ vars.CROWDIN_CLIENT_ID }}
+          client-id: ${{ secrets.CROWDIN_APP_ID }}
           permission-contents: write # required to commit to crowdin branch
           permission-pull-requests: write # required to create pull request
 

.github/workflows/deployment-beta-release.yml

@@ -52,7 +52,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_APPROVE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
           permission-pull-requests: write
       - name: Approve PR
         env:
@@ -64,7 +64,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_MERGE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # write to beta branch (due to merge)
           permission-pull-requests: write # merge pull request
       - id: automerge

.github/workflows/deployment-docker-image.yml

@@ -40,7 +40,6 @@ jobs:
       version: ${{ steps.read-semver.outputs.version || steps.version-fallback.outputs.version }}
       git_ref: ${{ steps.read-git-ref.outputs.ref || steps.read-semver.outputs.version || github.ref }}
       skipped: ${{ env.SKIP_RELEASE }}
-      upstream_sync: ${{ steps.update-upstream.outcome }}
     steps:
       - run: echo "Manual dispatch redeploys the latest existing release without creating a new one"
         if: env.SKIP_RELEASE == 'true'
@@ -55,7 +54,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_MERGE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # required to commit package.json & changelog changes, merge them to dev / next and publish the release
 
       - uses: actions/checkout@v7
@@ -116,10 +115,8 @@ jobs:
         run: |
           echo "ref=$(git rev-parse HEAD)" >> "$GITHUB_OUTPUT"
       - name: Update dev / next branch
-        id: update-upstream
         if: env.SKIP_RELEASE == 'false'
-        # Finish publishing the already-created release, then fail in the publish job if synchronization did not work.
-        continue-on-error: true
+        continue-on-error: true # Prevent pipeline from failing when merge fails
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
           UPSTREAM_BRANCH: ${{ github.ref_name == 'main' && 'dev' || 'next' }}
@@ -277,7 +274,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_MERGE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # required to publish the release
 
       - name: Log in to the Container registry
@@ -314,12 +311,6 @@ jobs:
         run: |
           gh release edit --repo ${{ github.repository }} ${{ needs.release.outputs.version }} --draft=false
 
-      - name: Verify dev / next synchronization
-        if: needs.release.outputs.skipped == 'false' && needs.release.outputs.upstream_sync != 'success'
-        run: |
-          echo "::error::The released commit was not synchronized back to the upstream development branch."
-          exit 1
-
       - name: Discord notification
         if: github.event_name != 'workflow_dispatch' || inputs['send-notifications']
         env:
@@ -327,17 +318,3 @@ jobs:
         uses: Ilshidur/action-discord@0.4.0
         with:
           args: "Successfully deployed images for branch **${{ github.ref_name }}**. Tagged as **${{env.NEXT_VERSION}}**."
-
-  notify-failure:
-    name: Notify deployment failure
-    if: ${{ always() && (failure() || cancelled()) && (github.event_name != 'workflow_dispatch' || inputs['send-notifications']) }}
-    needs: [release, build-amd64, build-arm64, extract-asset-amd64, extract-asset-arm64, publish]
-    runs-on: ubuntu-latest
-    timeout-minutes: 2
-    steps:
-      - name: Discord failure notification
-        env:
-          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
-        with:
-          args: "The deployment for branch **${{ github.ref_name }}** failed or was cancelled: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"

.github/workflows/deployment-docs.yml

@@ -42,7 +42,7 @@ jobs:
       - name: Upload pages artifact
         uses: actions/upload-pages-artifact@v5
         with:
-          path: "apps/docs/out"
+          path: "apps/docs/build"
 
   deploy:
     runs-on: ubuntu-latest

.github/workflows/deployment-weekly-release.yml

@@ -19,10 +19,10 @@ permissions:
 jobs:
   create-and-merge-pr:
     runs-on: ubuntu-latest
-    timeout-minutes: 10
+    timeout-minutes: 2
     steps:
       - name: Discord notification
-        if: ${{ github.event_name == 'schedule' || inputs.send-notifications }}
+        if: ${{ github.event.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0
@@ -38,30 +38,13 @@ jobs:
         with:
           token: ${{ github.token }}
           branch: dev
-          noNewCommitBehavior: silent
-          noVersionBumpBehavior: silent
-      - name: No release needed
-        if: ${{ steps.semver.outputs.bump == '' || steps.semver.outputs.bump == 'none' }}
-        run: echo "No release-worthy commits were found since ${{ steps.semver.outputs.current }}." >> "$GITHUB_STEP_SUMMARY"
       - name: Create pull request
         id: create-pull-request
-        if: ${{ steps.semver.outputs.bump != '' && steps.semver.outputs.bump != 'none' }}
-        run: |
-          pr_url="$(gh pr list --base main --head dev --state open --json url --jq '.[0].url // empty')"
-          if [[ -z "$pr_url" ]]; then
-            pr_url="$(gh pr create \
-              --title "chore(release): automatic release ${{ steps.semver.outputs.next }}" \
-              --body "**This is an automatic release**.<br/>Manual action may be required for major bumps.<br/>Detected change to be ``${{ steps.semver.outputs.bump }}``<br/>Bump version from ``${{ steps.semver.outputs.current }}`` to ``${{ steps.semver.outputs.next }}``" \
-              --base main \
-              --head dev \
-              --label automerge)"
-          fi
-          echo "url=$pr_url" >> "$GITHUB_OUTPUT"
-          echo "pr_number=${pr_url##*/}" >> "$GITHUB_OUTPUT"
+        run: 'gh pr create --title "chore(release): automatic release ${{ steps.semver.outputs.next }}" --body "**This is an automatic release**.<br/>Manual action may be required for major bumps.<br/>Detected change to be ``${{ steps.semver.outputs.bump }}``<br/>Bump version from ``${{ steps.semver.outputs.current }}`` to ``${{ steps.semver.outputs.next }}``" --base main --head dev --label automerge'
         env:
           GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
       - name: Discord notification
-        if: ${{ steps.create-pull-request.outcome == 'success' && (github.event_name == 'schedule' || inputs.send-notifications) }}
+        if: ${{ github.event.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0
@@ -69,29 +52,26 @@ jobs:
           args: "Created a release PR ${{ steps.create-pull-request.outputs.url }} for version ${{ steps.semver.outputs.next }} (new behaviour: ${{ steps.semver.outputs.bump }})"
       - name: Obtain token
         id: obtainApprovalToken
-        if: ${{ steps.create-pull-request.outcome == 'success' }}
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_APPROVE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
           permission-pull-requests: write
       - name: Approve PR
-        if: ${{ steps.create-pull-request.outcome == 'success' }}
         env:
           GITHUB_TOKEN: ${{ steps.obtainApprovalToken.outputs.token }}
         run: |
-          gh pr review "${{ steps.create-pull-request.outputs.url }}" --approve --body "Automatically approved by GitHub Action"
+          gh pr review --approve --body "Automatically approved by GitHub Action"
       - name: Obtain token
         id: obtainMergeToken
-        if: ${{ steps.create-pull-request.outcome == 'success' }}
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_MERGE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # write to main branch (due to merge)
           permission-pull-requests: write # merge pull request
       - id: automerge
-        if: ${{ steps.create-pull-request.outcome == 'success' && steps.semver.outputs.bump != 'major' }}
+        if: ${{ steps.semver.outputs.bump != 'major' }}
         name: automerge
         uses: "pascalgn/automerge-action@v0.16.4"
         env:
@@ -105,21 +85,21 @@ jobs:
           MERGE_REQUIRED_APPROVALS: 0 # do not require approvals
 
       - name: Merged Discord notification
-        if: ${{ steps.automerge.outputs.mergeResult == 'merged' && (github.event_name == 'schedule' || inputs.send-notifications) }}
+        if: ${{ steps.automerge.outputs.mergeResult == 'merged' && github.event.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0
         with:
           args: "Merged PR ${{ steps.create-pull-request.outputs.url }} for release ${{ steps.semver.outputs.next }}"
       - name: Major Bump Discord notification
-        if: ${{ steps.semver.outputs.bump == 'major' && (github.event_name == 'schedule' || inputs.send-notifications) }}
+        if: ${{ steps.semver.outputs.bump == 'major' && github.event.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0
         with:
           args: "The release PR must be manually merged because the next version is a major version: ${{ steps.create-pull-request.outputs.url }} for release ${{ steps.semver.outputs.next }}"
       - name: Discord Fail Notification
-        if: ${{ failure() && (github.event_name == 'schedule' || inputs.send-notifications) }}
+        if: failure() && github.event.inputs.send-notifications
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0

.github/workflows/docs-algolia-recrawl.yml

@@ -0,0 +1,58 @@
+name: "[Docs] Algolia Recrawl"
+
+on:
+  workflow_run:
+    workflows: ["[Deployment] Documentation"]
+    types: [completed]
+    branches: [dev]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  recrawl:
+    if: >-
+      ${{
+        (github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'pull_request')
+        || github.event_name == 'workflow_dispatch'
+      }}
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Check Algolia crawler secrets
+        run: |
+          missing=0
+          for secret in ALGOLIA_CRAWLER_ID ALGOLIA_CRAWLER_USER_ID ALGOLIA_CRAWLER_API_KEY; do
+            if [ -z "${!secret}" ]; then
+              echo "::warning::Missing repository secret: $secret"
+              missing=1
+            fi
+          done
+          if [ "$missing" -eq 1 ]; then
+            echo "Add crawler secrets to enable automatic recrawls."
+            exit 1
+          fi
+        env:
+          ALGOLIA_CRAWLER_ID: ${{ secrets.ALGOLIA_CRAWLER_ID }}
+          ALGOLIA_CRAWLER_USER_ID: ${{ secrets.ALGOLIA_CRAWLER_USER_ID }}
+          ALGOLIA_CRAWLER_API_KEY: ${{ secrets.ALGOLIA_CRAWLER_API_KEY }}
+
+      - name: Wait for GitHub Pages to serve the new deployment
+        run: sleep 60
+
+      - name: Trigger Algolia DocSearch recrawl
+        uses: cssnr/algolia-crawler-action@v2
+        with:
+          crawler_id: ${{ secrets.ALGOLIA_CRAWLER_ID }}
+          crawler_user_id: ${{ secrets.ALGOLIA_CRAWLER_USER_ID }}
+          crawler_api_key: ${{ secrets.ALGOLIA_CRAWLER_API_KEY }}
+
+      - name: Verify search index
+        working-directory: apps/docs
+        run: pnpm verify:search

.github/workflows/docs-update-contributors.yml

@@ -33,7 +33,7 @@ jobs:
       - name: Commit updated contributors
         uses: EndBug/add-and-commit@v10
         with:
-          add: "apps/docs/public"
+          add: "apps/docs/static"
           default_author: github_actor
           message: "chore(docs): update contributors"
           push: true

.github/workflows/docs-update-openapi.yml

@@ -54,13 +54,13 @@ jobs:
             exit 1
           }
 
-          cp /tmp/openapi.json apps/docs/public/api/open-api-schema.json
+          cp /tmp/openapi.json apps/docs/static/api/open-api-schema.json
           echo "OpenAPI spec updated ($(jq '.paths | length' /tmp/openapi.json) paths)"
 
       - name: Commit updated spec
         uses: EndBug/add-and-commit@v10
         with:
-          add: "apps/docs/public/api/"
+          add: "apps/docs/static/api/"
           default_author: github_actor
           message: "chore(docs): update OpenAPI spec"
           push: true

.github/workflows/on-release.yml

@@ -5,6 +5,39 @@ on:
     types: [released]
 
 jobs:
+  trigger-docs-release:
+    name: Trigger Documentation Release
+    runs-on: ubuntu-latest
+    timeout-minutes: 2
+    steps:
+      - name: Obtain token
+        id: obtainToken
+        uses: actions/create-github-app-token@v3
+        with:
+          private-key: ${{ secrets.HOMARR_DOCS_RELEASE_APP_PRIVATE_KEY }}
+          client-id: ${{ vars.HOMARR_DOCS_RELEASE_APP_ID }}
+          owner: homarr-labs
+          repositories: |
+            documentation
+          permission-contents: write # required to dispatch repository workflow
+      - name: Trigger documentation release
+        env:
+          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
+          SOURCE_TAG: ${{ github.event.release.tag_name }}
+        run: |
+          curl -X POST \
+            -H "Authorization: token $GITHUB_TOKEN" \
+            -H "Accept: application/vnd.github+json" \
+            https://api.github.com/repos/homarr-labs/documentation/dispatches \
+            -d @- <<EOF
+          {
+            "event_type": "trigger-release",
+            "client_payload": {
+              "tag": "${SOURCE_TAG}"
+            }
+          }
+          EOF
+
   update-bug-report-template:
     name: Update Bug Report Template
     runs-on: ubuntu-latest
@@ -15,7 +48,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ vars.RENOVATE_MERGE_CLIENT_ID }}
+          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # required to commit to branch
           permission-pull-requests: write # required to create pr & enable automerge
       - name: Checkout code

.github/workflows/update-contributors.yml

@@ -21,7 +21,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.HOMARR_UPDATE_CONTRIBUTORS_PRIVATE_KEY }}
-          client-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_CLIENT_ID }}
+          client-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_APP_ID }}
           permission-contents: write # required to commit to branch
           permission-pull-requests: write # required to create pr & enable automerge
 

.github/workflows/update-integration-list.yml

@@ -24,7 +24,7 @@ jobs:
         uses: actions/create-github-app-token@v3
         with:
           private-key: ${{ secrets.HOMARR_UPDATE_CONTRIBUTORS_PRIVATE_KEY }}
-          client-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_CLIENT_ID }}
+          client-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_APP_ID }}
           permission-contents: write # required to commit to branch
           permission-pull-requests: write # required to create pr & enable automerge
       - name: Checkout code

.oxfmtrc.json

@@ -10,11 +10,7 @@
     "CHANGELOG.md",
     "apps/docs/.docusaurus/**",
     "apps/docs/build/**",
-    "apps/docs/blog/2022/**",
-    "apps/docs/blog/2023/**",
-    "apps/docs/blog/2024/**",
-    "apps/docs/blog/2025/**",
-    "apps/docs/blog/authors.yml",
+    "apps/docs/blog/**",
     "packages/custom-widgets/src/core/component-catalog.generated.json",
     "apps/docs/static/custom-widgets/component-catalog-v1.json"
   ]

AGENTS.md

@@ -6,7 +6,7 @@
 homarr/
 ├── apps/
 │   ├── nextjs/          # Main Next.js application (port 3000)
-│   ├── docs/            # Next.js + Fumadocs documentation site (@homarr/docs)
+│   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
 │   ├── tasks/           # Cron-job initialization and scheduling runtime
 │   ├── websocket/       # Standalone tRPC WebSocket server (port 3001)
 │   └── workshop/        # Go/PocketBase Workshop service
@@ -57,7 +57,7 @@ homarr/
 
 ## Documentation Sync
 
-The documentation site lives at `apps/docs/` (Next.js + Fumadocs, `@homarr/docs`).
+The documentation site lives at `apps/docs/` (Docusaurus 3, `@homarr/docs`).
 
 When modifying user-facing code, you MUST also update the corresponding documentation:
 
@@ -75,7 +75,7 @@ When modifying user-facing code, you MUST also update the corresponding document
 - `pnpm dev:cli -- dev` — run the developer CLI without installing a global binary
 - `pnpm db:seed` — seed default database data explicitly
 - `pnpm docker:dev:up` — start the Redis development service in the background
-- `pnpm dev:docs` — Fumadocs site only
+- `pnpm dev:docs` — Docusaurus docs site only
 - `pnpm turbo build` — build all packages
 - `pnpm turbo build --filter=@homarr/docs` — build docs only
 - `pnpm turbo typecheck` — typecheck all packages

apps/docs/.gitignore

@@ -13,7 +13,6 @@
 # next.js
 /.next/
 /out/
-/.source/
 
 # production
 /build
@@ -56,4 +55,4 @@ static/data/configs
 
 # CI Stuff
 screenshots
-test-results
+test-results

apps/docs/AGENTS.md

@@ -1,9 +0,0 @@
-<!-- BEGIN:nextjs-agent-rules -->
-
-# This is NOT the Next.js you know
-
-This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` (resolved from this file's directory; in monorepos the `next` package may not be visible from the repo root) before writing any code. Heed deprecation notices.
-
-This block is written and re-added by `next dev` — verify at `node_modules/next/dist/server/lib/generate-agent-files.js`. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
-
-<!-- END:nextjs-agent-rules -->

apps/docs/CLAUDE.md

@@ -1 +0,0 @@
-@AGENTS.md

apps/docs/PRODUCT.md

@@ -1,37 +0,0 @@
-# Homarr Documentation
-
-## Register
-
-product
-
-## Users
-
-People who run Homarr, administrators configuring self-hosted infrastructure, and contributors extending Homarr. They arrive with a concrete task such as installing Homarr, connecting a service, configuring a widget, managing users, or building a custom widget, and need an answer they can scan and apply quickly.
-
-## Product Purpose
-
-The documentation is the complete, authoritative operating guide for Homarr. It keeps setup steps, configuration contracts, screenshots, generated integration and widget metadata, API references, and Workshop tooling next to the application code. Success means a reader can find the right page quickly, understand the next action, copy reliable instructions, and verify the result without searching elsewhere.
-
-## Brand Personality
-
-Focused, dependable, and approachable. The writing is direct and practical. The interface should feel calm and familiar during long technical sessions while retaining Homarr's red identity.
-
-## Anti-references
-
-- Generic marketing layouts that replace Homarr's product identity with unrelated slogans or decorative conversion copy.
-- Decorative dashboard aesthetics that compete with reading, including glass effects, large radii, card grids, and gratuitous motion.
-- Generic generated-docs styling that obscures Homarr's identity or makes navigation feel detached from the main product.
-- Dense reference portals that expose structure without giving readers a clear path through a task.
-
-## Design Principles
-
-1. Put the reader's task first: search, navigation, page outline, and the answer must remain easy to reach.
-2. Preserve one source of truth: typed Homarr metadata and existing custom components stay connected to the monorepo.
-3. Prefer familiar documentation patterns: the interface should disappear while a reader scans, copies, and follows instructions.
-4. Make complete content feel manageable through strong hierarchy, progressive disclosure, and precise cross-links.
-5. Treat machine readers as users through canonical Markdown, structured metadata, and standard LLM discovery endpoints.
-6. Keep the root landing page recognizably Homarr: preserve its self-hosted dashboard promise and real product evidence while documentation routes remain task-first.
-
-## Accessibility & Inclusion
-
-Meet WCAG 2.2 AA for color contrast, keyboard operation, focus visibility, landmarks, headings, and interactive controls. Respect reduced-motion and system color-scheme preferences. Diagrams, screenshots, icons, and emoji must have meaningful text alternatives when they carry information.

apps/docs/README.md

@@ -1,52 +1,112 @@
-# Homarr documentation (`@homarr/docs`)
+# Homarr Documentation (`@homarr/docs`)
 
-The source for [homarr.dev](https://homarr.dev), built with Next.js and Fumadocs UI inside the Homarr monorepo.
+The official [homarr.dev](https://homarr.dev) documentation site, built with [Docusaurus 3](https://docusaurus.io/) and living inside the Homarr monorepo.
 
-## Develop
+## Why it's in the monorepo
 
-From the repository root:
+Having documentation alongside the application code enables:
+
+- **Two-way linking** — the docs app imports from `@homarr/definitions` for type-safe integration/widget metadata, and the main app references doc paths via generated sitemap types
+- **Atomic PRs** — code changes and their documentation updates ship in the same pull request
+- **Shared tooling** — same Node version, pnpm catalog, oxlint/oxfmt, CI pipeline
+- **Build-time validation** — Docusaurus strict mode catches broken links and references at build time
+
+## Development
+
+From the **monorepo root**:
 
 ```bash
+# Start the docs dev server (port 3003)
 pnpm dev:docs
-```
 
-The site runs on `http://127.0.0.1:3003`. To use a local Workshop API:
+# Or from within this directory
+pnpm dev
 
-```bash
+# Point the docs at a local PocketBase instance
 WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
 ```
 
-## Validate
+The standalone docs use `WORKSHOP_API_URL` for PocketBase and `HOMARR_WEBSITE_URL` for the public site origin. The old
+`WORKSHOP_URL` name is a deprecated one-release alias.
+
+## Build
 
 ```bash
-pnpm --filter @homarr/docs typecheck
-pnpm --filter @homarr/docs build
-pnpm --filter @homarr/docs validate:links
+# Build docs only
+pnpm turbo build --filter=@homarr/docs
+
+# Build everything (docs + main app + tasks + websocket)
+pnpm build
 ```
 
-The static export is written to `out/`. The build validates that every registered integration and widget has a docs
-page. The link check validates internal Markdown and MDX links against that export.
+## Lint & Format
 
-## Write content
+Uses oxlint and oxfmt (same as the rest of the monorepo):
 
-Documentation lives in `docs/`; project posts live in `blog/`. Navigation is controlled by the nearest `meta.json`.
-Integration and widget folders pair typed `index.ts` metadata with `index.mdx` content.
+```bash
+pnpm lint        # oxlint
+pnpm format      # oxfmt (check)
+pnpm format:fix    # oxfmt (fix)
+```
 
-Use standard Markdown and MDX. Shared components live in `src/components/`. Mermaid fences, tabs, callouts, zoomable
-images, and syntax-highlighted code are supported by the Fumadocs pipeline.
+## Typecheck
 
-When a user-facing change affects setup or behavior, update the matching page in the same pull request. See the
-[documentation-sync skill](../../.agents/skills/documentation-sync/SKILL.md) for the code-to-content map.
+```bash
+pnpm typecheck
+```
 
-## Published formats
+## Content Structure
 
-- `/docs` — searchable documentation with typed navigation
-- `/api-reference` — interactive reference generated from the OpenAPI schema
-- `/llms.txt` — compact documentation and blog index for agents
-- `/llms-full.txt` — complete processed Markdown corpus
-- `/llms.mdx/docs/.../content.md` — raw Markdown for each docs page
-- `/llms.mdx/blog/.../content.md` — raw Markdown for each blog post
-- `/blog/rss.xml` — RSS feed for project posts
+```
+docs/
+├── getting-started/    # Installation guides, glossary, prerequisites
+├── management/         # Boards, apps, users, integrations, settings, tasks, API
+├── integrations/       # 56 integration guides (one folder each)
+├── widgets/            # 43 widget guides (one folder each)
+├── advanced/           # SSO, env vars, proxy, styling, CLI, development
+└── community/          # FAQ, donate, license, translations, get-in-touch
+```
 
-Every docs page and blog post includes copy-Markdown and view-source actions. Search is generated at build time and
-runs locally in the browser; it does not depend on an external crawler.
+Each integration/widget doc follows a consistent pattern:
+
+- `index.ts` — typed metadata (`IntegrationDefinition` / `WidgetDefinition`)
+- `index.mdx` — content using shared React components (`IntegrationHeader`, `WidgetHeader`, etc.)
+
+## Importing from homarr packages
+
+The docs app has `@homarr/definitions` as a workspace dependency. You can import integration kinds, widget kinds, and other definitions directly:
+
+```typescript
+import { IntegrationKind } from "@homarr/definitions";
+```
+
+This enables type-safe references to homarr domain concepts within documentation code.
+
+## Search (Algolia DocSearch)
+
+Search uses the `Docusaurus` Algolia index (crawler `cd77a285-2756-4557-bf21-ee703748df15`). A separate `markdown` index is built for LLM markdown indexing.
+
+Crawler reference config: [`docsearch.config.js`](docsearch.config.js).
+
+**Verify search health:**
+
+```bash
+pnpm verify:search
+```
+
+## Tech Stack
+
+| Layer          | Technology                                  |
+| -------------- | ------------------------------------------- |
+| Site generator | Docusaurus 3 (`@docusaurus/preset-classic`) |
+| Styling        | Tailwind CSS 4 + Docusaurus Infima          |
+| Icons          | `@tabler/icons-react`                       |
+| Diagrams       | Mermaid (`@docusaurus/theme-mermaid`)       |
+| Search         | Algolia DocSearch                           |
+| Analytics      | PostHog                                     |
+| Charts         | @nivo/line                                  |
+
+## Contributing
+
+When a Homarr change affects user-facing behavior, update the corresponding documentation in this app. See the
+[documentation-sync skill](../../.agents/skills/documentation-sync/SKILL.md) for the code-to-documentation mapping.

apps/docs/blog/2022/06-22-documentation/index.mdx

@@ -1,7 +1,6 @@
 ---
 slug: documentation-migration
 title: Migration of Documentation
-date: 2022-06-22
 authors:
   - ajnart
   - manuel-rw
@@ -13,7 +12,7 @@ The documentation has been re-written partly and includes now many animations, g
 
 We are still figuring things out and highly depend on your feedback.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## Why we migrated
 
@@ -33,4 +32,4 @@ After we've reviewed your changes, we'll merge your PR and this documentation wi
 
 ## TL;DR
 
-The documentation on GitHub Wiki will soon disappear. It will be replaced with this Docusaurus-powered website. You'll find much more information here with higher detail and searchability.
+The documentation on GitHub Wiki will soon disappear. It will be replaced with this Docusaurus-powered website. You'll find much more information here with higher detail and searchability.

apps/docs/blog/2022/08-28-translation/index.mdx

@@ -1,7 +1,6 @@
 ---
 slug: translations
 title: Help us make Homarr multilingual
-date: 2022-08-28
 authors:
   - ajnart
   - manuel-rw
@@ -14,8 +13,8 @@ We've been working hard to offer Homarr in many languages. The next update of Ho
 ![](img/homarr-we-need-you.webp) <br/>
 Yes, we need **YOU**! We want to make Homarr accessible to as many people as possible. Thus, we need to translate all content into many different languages. We need your help for that! [You can help us now to translate Homarr into as many languages as possible](/docs/community/translations).
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ### About global translations / translations per user
 
-We are aware that many people would like to configure translations globally or configure language per user. Currently, translations are stored in the Cookies, which will expire after some time (currently, it's set to 30 days). We will implement more granular language settings in future versions of Homarr, since it requires major changes to Homarr. Stay tuned! 😎
+We are aware that many people would like to configure translations globally or configure language per user. Currently, translations are stored in the Cookies, which will expire after some time (currently, it's set to 30 days). We will implement more granular language settings in future versions of Homarr, since it requires major changes to Homarr. Stay tuned! 😎

apps/docs/blog/2023/01-11-version0.11/index.mdx

@@ -1,6 +1,5 @@
 ---
 title: "We present: Homarr 0.11 - the most complex Homarr version yet!"
-date: 2023-01-11
 authors:
   - ajnart
   - manuel-rw
@@ -21,7 +20,7 @@ It contains many breaking changes and huge improvements to your favourite dashbo
 - Huge design and usability improvements to older components to Homarr
 - Better handeling of exceptions and unexpected issues
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## Complete implementation of highly customizable drag and drop library "Gridstack"
 

apps/docs/blog/2023/04-16-version0.12-more-widgets/index.mdx

@@ -1,6 +1,5 @@
 ---
 title: "We present: Homarr 0.12 - The fastest homarr version ever!"
-date: 2023-04-16
 authors:
   - ajnart
   - manuel-rw
@@ -16,12 +15,14 @@ This applies to all widgets, but in the case of the IFrame widget, it enables yo
 - Integrate monitoring tools like Grafana, Splunk or Elasticsearch
 - Integrate your services (for example Sonarr, Radarr and Overseerr) directly into Homarr
 
+![](https://media.discordapp.net/attachments/988335098493542410/1094665745226539168/update-teaser.png?width=1046&height=666)
+
 ## Edit mode password
 We've added a setting to disable editing completely. This will allow you to restrict edit access without password-protection.
 use the `EDIT_MODE_PASSWORD` ENV variable to set a password for edit mode. 
 turn on `DISABLE_EDIT_MODE=TRUE` to disable edit mode on startup.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## 😎 Blazingly fast
 We've implemented a new caching system, that will cache all data in your browser, meaning that Homarr will load within milliseconds, as if it was *powered by rust and blazingly fast* !!!
@@ -71,4 +72,4 @@ Now, you can use the following environment variables to configure this:
 - ``DOCKER_HOST``
 - ``DOCKER_PORT``
 
-**Full Changelog**: https://github.com/ajnart/homarr/compare/v0.11.5...v0.12.0
+**Full Changelog**: https://github.com/ajnart/homarr/compare/v0.11.5...v0.12.0

apps/docs/blog/2023/11-10-authentication/index.mdx

@@ -1,6 +1,5 @@
 ---
 title: "Authentication in Homarr - 0.14 is here!"
-date: 2023-11-10
 authors:
   - ajnart
   - manuel-rw
@@ -24,7 +23,7 @@ provide you a viable solution today.
 - 📝 Overhauled notepad widget with a complex graphical editor that enables easy editing right from your browser.
 - :globe_with_meridians:  Live Translation on Crowdin that enable you to directly translate using images to see what exactly you're translating
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## Breaking changes
 
@@ -84,4 +83,4 @@ We are aware that this update has many breaking changes and may confuse some use
 For that reason, we updated our documentation and will enhance it further within the next few weeks.
 We've also added this small button at the bottom of the page were you can ask **your questions** to an AI assistant:
 
-![image](https://github.com/ajnart/homarr/assets/30572287/a56f721a-d022-42ad-813a-d85c89462a8c)
+![image](https://github.com/ajnart/homarr/assets/30572287/a56f721a-d022-42ad-813a-d85c89462a8c)

apps/docs/blog/2023/12-22-updated-documentation/index.mdx

@@ -1,6 +1,5 @@
 ---
 title: "Updated documentation with better organization & design"
-date: 2023-12-22
 authors:
   - manuel-rw
 tags: [homarr, documentation, design, docs]
@@ -9,7 +8,7 @@ tags: [homarr, documentation, design, docs]
 We'd like to let you know that we've updated our documentation and reorganized the pages.
 This means, that some links may no longer be valid - we apologise if this causes any inconvenience for you.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 A few highlights include:
 
@@ -19,4 +18,4 @@ A few highlights include:
 - Bug fixes for image zoom
 - Added documentation for management pages and [new CLI tool](/docs/advanced/command-line/password-recovery/)
 
-Please [let us know](/docs/community/get-in-touch) is something is not working as expected.
+Please [let us know](/docs/community/get-in-touch) is something is not working as expected.

apps/docs/blog/2024/09-23-version-1.0/index.mdx

@@ -1,10 +1,9 @@
 ---
-title: Homarr 1.0 - complete rewrite of all systems
-date: 2024-09-23
 authors:
   - manuel-rw
 ---
 
+# Homarr 1.0 - complete rewrite of all systems
 We proudly present to you - Homarr ``1.0``.
 We have started work on this new version back in 2023 and have worked tirelessly for months on this brand-new dashboard.
 
@@ -29,7 +28,7 @@ reliability and scalability compared to < ``1.0``.
 - **Improved performance**: We have upgraded the underlying framework of Homarr and take advantage
 of an in-memory message bus and websockets to deliver data near realtime to you.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## Breaking changes
 :::warning

apps/docs/blog/2024/12-17-open-beta-1.0/index.mdx

@@ -1,16 +1,16 @@
 ---
-title: Open Beta 1.0
-date: 2024-12-17
 authors:
   - meierschlumpf
 ---
 
+# Open Beta 1.0
+
 We are proud to announce the open beta of Homarr 1.0. This is a major milestone for us and we are excited to share it with you.
 The open beta allows us to polish the last rough edges and gather feedback from you.
 We are looking forward to your feedback and hope you enjoy the new features.
 Let us know throgh discord or a [github issues](https://github.com/homarr-labs/homarr/issues/new/choose) if you encounter any issues.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## How to use the beta with docker
 
@@ -36,4 +36,4 @@ services:
 
 Then, run `docker compose up -d` in the same directory. This will start the Homarr container in the background.
 Please note that the mounts have changed and it's not backwards compatible with versions before 1.0.0-beta.1.
-You can find a list of all breaking changes [here](/blog/2024/09/23/version-1.0)
+You can find a list of all breaking changes [here](/blog/2024/09/23/version-1.0)

apps/docs/blog/2025/01-19-migration-guide-1.0/index.mdx

@@ -1,14 +1,14 @@
 ---
-title: Migrate from 0.15.10+ to 1.0.0
-date: 2025-01-19
 authors:
   - meierschlumpf
 ---
 
+# Migrate from 0.15.10+ to 1.0.0
+
 In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
 If you are still on a version before 0.15.10, please update to 0.15.10 where we introduced the migration export page.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ## Preserve your old installation
 

apps/docs/blog/2025/08-02-using-argus/index.mdx

@@ -1,14 +1,14 @@
 ---
-title: How to use Argus with Homarr
-date: 2025-08-02
 authors:
   - meierschlumpf
 ---
 
+# How to use Argus with Homarr
+
 In `v1.32.0` we added the endpoint `/api/info` which returns the current version of Homarr and can therefore be used in Argus to watch for updates.
 This guide will show you how to set up a user with apiKey to access the endpoint without providing admin access through it.
 
-{/* Historical excerpt boundary. */}
+<!-- truncate -->
 
 ![Argus](./img/argus.png)
 
@@ -64,4 +64,4 @@ Now you can configure Argus to use the user and apiKey we created.
 
 ![Argus configuration](./img/argus-configuration.png)
 
-Replace the `<secret>` with the apiKey you created and the deployed version url with the url of your Homarr instance.
+Replace the `<secret>` with the apiKey you created and the deployed version url with the url of your Homarr instance.

apps/docs/blog/2026/09-03-homarr-2.0/index.mdx

@@ -1,164 +0,0 @@
----
-title: Homarr 2.0.0 - Workshop, Custom Widgets and a rebuilt board
-date: 2026-09-03
-authors:
-  - ajnart
-tags: [homarr, update, version, assistant, custom widgets, dashboards, docker]
-draft: false
----
-
-# Homarr 2.0.0 - Workshop, Custom Widgets and a rebuilt board
-
-First, thank you.
-
-Many of you used the v2 demo when it was still rough, found bugs and came back to test the next build. Others translated Homarr, answered questions, contributed code or simply kept using it. We would not be shipping this without you.
-
-We are also planning a small batch of **free, limited-edition Homarr swag** for Workshop contributors and a few randomly picked community members. It is not for sale and it is not for profit. No Homarr merch empire, sorry.
-
-Homarr 2.0 is an upgrade, not a brand-new app wearing the same logo. Here is what actually changed.
-
-![A populated Homarr 2.0 dashboard with compact widgets, an Assistant, and an application rail](./img/homarr-v2-dashboard.webp)
-
-{/* Historical excerpt boundary. */}
-
-:::warning Back up before upgrading
-
-Create a [Homarr backup](/docs/management/backup) first. Do not test a prerelease image on your only production volume. Backups are boring. Restores are worse.
-
-:::
-
-## Custom Widgets v2 and Workshop
-
-### Build almost any widget
-
-**This is the big one.** We think it is the most important Homarr update we have made.
-
-Custom Widgets v2 lets you build widgets from JSX, API requests, actions and typed settings. Write one yourself or describe it to Assistant, then test it in the workbench. We think this is enough to make almost any dashboard widget—even that oddly specific component only three people need. Those three people no longer have to wait for us.
-
-This was partly inspired by [Google's upcoming Create My Widget feature](https://blog.google/products-and-platforms/platforms/android/gemini-intelligence/): describe a widget in normal language and let AI make it. Coding knowledge is optional. Knowing what the API does still helps; AI has not fixed bad documentation. Yet.
-
-![The Custom Widget v2 workbench after a live exchange-rate request successfully renders its preview](./img/custom-widget-workbench.webp)
-
-A `homarr-custom-widget-v2` definition can use several fixed-origin API sources. Credentials are encrypted separately and stay out of exports and Workshop submissions. Actions support `GET`, `POST`, `PUT`, `PATCH` and `DELETE`; requests have host checks, timeouts, size limits, permissions and rate limits. Custom Widgets remain **Beta** in 2.0.
-
-### Share widgets and Custom CSS
-
-**Workshop is the other half.** Publish and install Custom Widgets, then update, vote on, comment on and report submissions. Workshop is not only for widgets: you can share your **Custom CSS** there too. Deployment URLs and credentials stay on your Homarr instance.
-
-![The Community Workshop catalog inside Custom Widget management](./img/community-workshop.webp)
-
-:::warning Workshop is moderated
-
-AI makes widgets easy to produce. It does not make the first thing it coughs up worth publishing. **Do not dump untested slop into Workshop.** Test it, add a useful screenshot and explain its setup. Workshop is moderated.
-
-:::
-
-### The ultimate Homarr update
-
-We have called this the **"ultimate Homarr update"**. Not because work stops, but because every new service or widget idea no longer needs a full Homarr release; the community can build and share it instead.
-
-## Board editing, rebuilt
-
-### Drag and drop
-
-We threw out the old drag-and-drop system and rebuilt it on [`dnd-kit`](https://dndkit.com/). Moves and eight-direction resizes are transactional: Homarr previews the result, checks collisions and only saves a valid layout. Bad moves roll back instead of wrecking the board. In short: less fighting with your own dashboard.
-
-![A Calendar tile moving across the rebuilt Homarr 2.0 board grid](./img/drag-and-drop.gif)
-
-### Goodbye Groups and sections, bonjour Containers
-
-Groups and dynamic sections did nearly the same job, so **Containers replace both**. They hold apps, widgets and other Containers. Hold <kbd>Ctrl</kbd> or <kbd>Command</kbd> to move several items at once.
-
-### One board, several layouts
-
-Boards also have Base and Mobile layouts, plus optional breakpoints. **Reset from Base** creates a Mobile starting point without duplicating the board.
-
-## Homarr Assistant
-
-### Work with live Homarr data
-
-Assistant reads live Homarr data and has tools for boards, apps, integrations, widgets, Docker and supported services. It can answer questions, make approved changes and build Custom Widgets. It follows your permissions: reads can run automatically, while changes require approval by default.
-
-![The Homarr Assistant expanded over a live dashboard with health, exploration, media, and board actions](./img/assistant-control-surface.webp)
-
-Open it with <kbd>Shift</kbd> + <kbd>A</kbd>. <kbd>Cmd</kbd>/<kbd>Ctrl</kbd> + <kbd>/</kbd> searches it.
-
-### The Homarr provider
-
-:::note
-
-Assistant ships with a **"Homarr provider"**. It is free, will never offer paid plans, and is paid for by [Ajnart](https://github.com/ajnart) using the ad revenue from this website.
-
-It only uses zero-data-retention (ZDR) providers. [The provider is open source](https://github.com/homarr-labs/homarr/blob/release/v2/apps/workshop/homarr_provider.go), and neither prompts nor responses are logged. We are not selling your data. Pinky promise.
-
-:::
-
-### External assistants through MCP
-
-External assistants can use the same permission-checked tools through `/api/mcp`, with an API key or OAuth 2.1 with PKCE.
-
-## The rest (there is a lot)
-
-### Brand-new onboarding
-
-A six-stage setup studio handles the first admin, core settings, Docker discovery, apps, integrations and the first board.
-
-![The Homarr 2.0 setup studio on its Essentials step, with all six setup stages shown](./img/onboarding-studio.webp)
-
-### Board switcher
-
-Boards now live in a searchable gallery with keyboard navigation. Open it from the header or press <kbd>Shift</kbd> + <kbd>C</kbd>.
-
-![A visual board card inside the searchable Homarr board switcher](./img/board-switcher.webp)
-
-### Command menu and keybinds
-
-<kbd>Cmd</kbd>/<kbd>Ctrl</kbd> + <kbd>K</kbd> finds resources, pages, settings, users, groups and commands. More
-keybinds cover Assistant, editing, selection and advanced widget views.
-
-### Customizable header
-
-Pick which buttons appear, put them on the left, center or right, and change their order.
-
-![The Header studio showing left, center, and right zones plus available controls](./img/header-studio.webp)
-
-### Instance branding
-
-Change the name, logo, favicon, colors, corner styles and login page. Global CSS applies instance-wide; board CSS can override it. Only give that power to admins you trust. CSS remains CSS.
-
-![Instance branding controls for application identity, palette, corner style, and global CSS](./img/instance-branding.webp)
-
-### Widgets
-
-Add content without leaving the board. Settings have live previews, and supported widgets have advanced views. Weather and Clock were redesigned; Air Quality, Countdown and Timer are new.
-
-### Docker and Podman
-
-`DOCKER_ENDPOINTS` supports several hosts. Assisted setup and container labels can create apps, integrations, Containers, widgets and health checks.
-
-![Assisted Docker setup listing discovered services that can become apps or integrations](./img/docker-assisted-setup.webp)
-
-Homepage-compatible labels work too.
-
-### Permissions
-
-Groups use a new Viewer, Editor and Admin matrix. The API, Assistant and MCP follow the same rules. LDAP can create users on first sign-in; OIDC can link verified accounts and synchronize groups.
-
-### Performance
-
-Board startup work runs in parallel, heavy screens load when opened, and identical integration requests share work instead of doing it twice.
-
-## Before upgrading
-
-- Keep a backup and use the final release image, not a prerelease tag.
-- Legacy Custom JSX definitions enter a migration state. Homarr keeps encrypted credentials and an archived copy until the v2 definition validates.
-- Mobile layouts place rail content in the main flow instead of displaying rails.
-- Custom Widgets remain Beta.
-- Assistant and MCP do not bypass permissions.
-
-## Links
-
-- Try the [Homarr 2.0 preview](https://app-v2.preview.homarr.dev).
-- Follow the [v2 release pull request](https://github.com/homarr-labs/homarr/pull/6545) and [public beta thread](https://github.com/homarr-labs/homarr/issues/6600).
-- Compare [v1.76.2 with the release/v2 branch](https://github.com/homarr-labs/homarr/compare/v1.76.2...release/v2).
-- Read the guides for [Boards](/docs/management/boards), [Custom Widgets](/docs/management/custom-widgets), [Assistant](/docs/management/assistant), [MCP](/docs/management/mcp) and [Docker labels](/docs/integrations/docker-labels).

apps/docs/components.json

@@ -5,7 +5,7 @@
   "tsx": true,
   "tailwind": {
     "config": "",
-    "css": "src/app/global.css",
+    "css": "src/css/custom.css",
     "baseColor": "mist",
     "cssVariables": true,
     "prefix": ""

apps/docs/docs/advanced/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Advanced",
+  "collapsed": true,
+  "position": 5,
+  "link": {
+    "type": "generated-index",
+    "title": "Advanced Concepts or features"
+  }
+}

apps/docs/docs/advanced/command-line/_category_.json

@@ -0,0 +1,4 @@
+{
+  "collapsed": true,
+  "label": "Command line interface"
+}

apps/docs/docs/advanced/command-line/index.mdx

@@ -14,31 +14,7 @@ docker exec -it <container-id> /bin/bash
 homarr <command>
 ```
 
-### QNAP Container Station
-
-1. Open **Container Station**.
-
-![Container Station in the QNAP application menu](./img/334116069-e7ec4726-3df7-4dc6-a3e0-b745e7eef17f.png)
-
-2. Select **Containers**.
-
-![Containers menu in QNAP Container Station](./img/334116205-aa09ce40-0701-4f7d-b9f9-b431b9d207c5.png)
-
-3. Select the Homarr container.
-
-![Homarr container selected in QNAP Container Station](./img/334116303-714b5e07-b9de-4ec0-a2bc-def7ee38750f.png)
-
-4. Select **Execute**.
-
-![Execute action for the Homarr container in QNAP Container Station](./img/334116411-df1482f9-3aa9-4686-b77f-e0dca09e60b2.png)
-
-5. Select `/bin/bash`, then select **Execute**.
-
-![Bash selected in the QNAP execute console](./img/334116518-e1ddb515-99c7-4159-81bf-76e889d1e808.png)
-
-6. Run `homarr <command>` in the console.
-
-![Bash console open for Homarr in QNAP Container Station](./img/334116642-08c4f204-5cd0-4e4e-a785-0142e1b279ca.png)
+In QNAP Container Station, open the Homarr container's **Execute** action and select `/bin/bash`.
 
 See the pages in this section for available commands.
 

apps/docs/docs/advanced/command-line/meta.json

@@ -1,4 +0,0 @@
-{
-  "title": "Command line interface",
-  "pages": ["index", "users", "integrations", "password-recovery", "fix-usernames", "development"]
-}

apps/docs/docs/advanced/development/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Developer guides",
+  "position": 6,
+  "collapsed": true,
+  "link": {
+    "type": "generated-index"
+  }
+}

apps/docs/docs/advanced/development/getting-started.mdx

@@ -57,8 +57,8 @@ Homarr becomes the instance administrator.
 Use `pnpm docker:dev:up` instead when you only need Redis in the background. Running the migration also seeds the
 default data; use `pnpm db:seed` to seed it explicitly later.
 
-Workshop contributors can set up PocketBase and Fumadocs with the dedicated
-[Workshop development guide](/docs/advanced/development/workshop).
+Workshop contributors can set up PocketBase and Docusaurus with the dedicated
+[Workshop development guide](./workshop).
 
 ### Useful commands
 
@@ -69,7 +69,7 @@ Workshop contributors can set up PocketBase and Fumadocs with the dedicated
 - `pnpm dev:cli -- build --pr <number>` — build a pull request from a temporary checkout.
 - `pnpm dev:cli -- rebuild <name>` — rebuild an image from its recorded checkout or pull request.
 - `pnpm dev:cli:install` — optionally install the developer CLI as a `homarr` binary.
-- `pnpm dev:docs` — Fumadocs on port 3003.
+- `pnpm dev:docs` — Docusaurus only on port 3003.
 - `pnpm docker:dev:up` — Redis development service in the background.
 - `pnpm cli` — Homarr operations CLI.
 - `pnpm db:migration:sqlite:run` — create or update a SQLite database.

apps/docs/docs/advanced/development/meta.json

@@ -1,4 +0,0 @@
-{
-  "title": "Developer guides",
-  "pages": ["getting-started", "widgets-and-integrations", "kubernetes", "workshop", "workshop-operator"]
-}

apps/docs/docs/advanced/development/workshop.mdx

@@ -4,13 +4,13 @@ sidebar_position: 4
 tags:
   - Workshop
   - Developer
-  - Fumadocs
+  - Docusaurus
   - PocketBase
 ---
 
 # Workshop development
 
-See the [main development guide](/docs/advanced/development/getting-started) for repository prerequisites.
+See the [main development guide](./getting-started) for repository prerequisites.
 
 Start PocketBase:
 
@@ -19,7 +19,7 @@ cp apps/workshop/.env.example apps/workshop/.env
 docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
 ```
 
-Start Fumadocs in another terminal:
+Start Docusaurus in another terminal:
 
 ```sh
 WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs

apps/docs/docs/advanced/environment-variables/index.mdx

@@ -30,8 +30,7 @@ Using the `PUID` and `PGID` will require you to set the correct permissions on t
 | `PUID`                   | User ID to run the container as                                                                                                                                                                                                        | Any valid user ID                   | `0`                           |
 | `PGID`                   | Group ID to run the container as                                                                                                                                                                                                       | Any valid group ID                  | `0`                           |
 | `LOG_LEVEL`              | Log level to use                                                                                                                                                                                                                       | `debug` / `info` / `warn` / `error` | `info`                        |
-| `BASE_URL`               | Public Homarr origin used by MCP OAuth metadata and redirects. Set this when a reverse proxy does not preserve the public host and protocol.                                                                                           | HTTP(S) origin without a path       | -                             |
-| `NO_EXTERNAL_CONNECTION` | Disables Homarr's internet-backed requests, including update checks, weather, location search, and RSS feeds                                                                                                                           | `true` or `false`                   | `false`                       |
+| `NO_EXTERNAL_CONNECTION` | Disables Homarr's internet-backed requests, including update checks, weather, and RSS feeds                                                                                                                                            | `true` or `false`                   | `false`                       |
 | `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag                                                     | `true` or `false`                   | `true`                        |
 | `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false`                       |
 | `HOMARR_WEBSITE_URL`     | Main Homarr documentation/site base used by runtime links. Must be an absolute HTTP(S) URL.                                                                                                                                            | HTTP(S) URL                         | `https://homarr.dev`          |
@@ -139,4 +138,4 @@ The advanced deployments environment variables should only be used if you know w
 | `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts. |
 
 All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
-trailing slashes when Homarr or the documentation site starts.
+trailing slashes when Homarr or Docusaurus starts.

apps/docs/docs/advanced/index.mdx

@@ -1,60 +0,0 @@
----
-title: Advanced configuration
-description: Configure deployment, authentication, networking, styling, automation, and development workflows.
----
-
-import {
-  IconCode,
-  IconIcons,
-  IconKey,
-  IconKeyboard,
-  IconNetwork,
-  IconPalette,
-  IconTerminal2,
-  IconUserCog,
-  IconVariable,
-} from "@tabler/icons-react";
-
-These guides cover changes that affect how Homarr is deployed, secured, operated, or extended.
-
-## Deploy and secure
-
-<Cards>
-  <Card icon={<IconVariable />} title="Environment variables" href="/docs/advanced/environment-variables">
-    Configure Homarr at deployment time.
-  </Card>
-  <Card icon={<IconKey />} title="Single sign-on" href="/docs/advanced/single-sign-on">
-    Connect an external identity provider.
-  </Card>
-  <Card icon={<IconNetwork />} title="Proxies and certificates" href="/docs/advanced/proxy">
-    Run Homarr behind a reverse proxy.
-  </Card>
-  <Card icon={<IconUserCog />} title="Run as a different user" href="/docs/advanced/running-as-different-user">
-    Change the user and group used by the container.
-  </Card>
-</Cards>
-
-## Customize
-
-<Cards>
-  <Card icon={<IconPalette />} title="Custom styling" href="/docs/advanced/styling">
-    Apply custom CSS to Homarr.
-  </Card>
-  <Card icon={<IconIcons />} title="Icons" href="/docs/advanced/icons">
-    Configure icon sources and behavior.
-  </Card>
-  <Card icon={<IconKeyboard />} title="Keyboard shortcuts" href="/docs/advanced/keyboard-shortcuts">
-    Navigate and operate Homarr with the keyboard.
-  </Card>
-</Cards>
-
-## Develop and automate
-
-<Cards>
-  <Card icon={<IconTerminal2 />} title="Command line interface" href="/docs/advanced/command-line">
-    Use administrative commands from the terminal.
-  </Card>
-  <Card icon={<IconCode />} title="Developer guides" href="/docs/advanced/development/getting-started">
-    Set up a development environment and contribute code.
-  </Card>
-</Cards>

apps/docs/docs/advanced/meta.json

@@ -1,19 +0,0 @@
-{
-  "title": "Advanced",
-  "defaultOpen": false,
-  "pages": [
-    "index",
-    "---Deploy and secure---",
-    "environment-variables",
-    "single-sign-on",
-    "proxy",
-    "running-as-different-user",
-    "---Customize---",
-    "styling",
-    "icons",
-    "keyboard-shortcuts",
-    "---Develop and automate---",
-    "command-line",
-    "development"
-  ]
-}

apps/docs/docs/advanced/proxy/index.mdx

@@ -9,14 +9,14 @@ tags:
   - Security
 ---
 
-import Tabs from "@/components/mdx/legacy-tabs";
-import { TabItem } from "@/components/mdx/legacy-tabs";
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
 
 ## Allowing self-signed certificates
 
 Some users may come across a barrier, where they're unable to receive a 200 response from the Ping widget for some apps, while using self-signed certificates or a local certificate authory.
 
-:::note[What's going on?]
+:::note What's going on?
 
 Homarr is trying to communicate to your apps via the integrations.
 It usually doesn't matter if Homarr is running on `http` or `https`.
@@ -40,7 +40,7 @@ services:
     volumes:
       - ./homarr/appdata:/appdata
     environment:
-      - BASE_URL=https://your.internal.dns.address.here.com
+      - BASE_URL=your.internal.dns.address.here.com
       - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
     networks:
       - proxy

apps/docs/docs/advanced/single-sign-on/index.mdx

@@ -10,6 +10,9 @@ tags:
   - Active Directory
 ---
 
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
+
 # Single Sign On
 
 Homarr supports multiple authentication options, from internal userbase (credentials), to LDAP (with Active directory support), and OIDC.
@@ -199,9 +202,9 @@ Homarr supports multiple authentication options, from internal userbase (credent
     | ``AUTH_OIDC_CLIENT_NAME``   | Display name of provider (in login screen)                 | OIDC          |
     | ``AUTH_OIDC_AUTO_LOGIN``    | Automatically redirect to OIDC login                       | false         |
     | ``AUTH_OIDC_SCOPE_OVERWRITE`` | Overwrite default scopes (openid, profile, email)        | openid email profile groups           |
-    | ``AUTH_OIDC_GROUPS_ATTRIBUTE`` | Attribute used for groups (roles) claim. Dot-separated paths such as `resource_access.homarr.roles` are supported. | groups        |
+    | ``AUTH_OIDC_GROUPS_ATTRIBUTE`` | Attribute used for groups (roles) claim                  | groups        |
     | ``AUTH_OIDC_GROUPS_LOCAL_MANAGEMENT`` | Stop syncing group memberships of OIDC users from the groups claim and manage them locally via the group members page instead | false |
-    | ``AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE`` | Overwrite name attribute. Dot-separated paths are supported. By default it will use preferred_username if it does not contain a `@` and otherwise name. | ---          |
+    | ``AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE`` | Overwrite name attribute. By default it will use preferred_username if it does not contain a `@` and otherwise name. | ---          |
     | ``AUTH_OIDC_FORCE_USERINFO`` | Force userinfo endpoint to be used for user information.    | false         |
     | ``AUTH_OIDC_ENABLE_DANGEROUS_ACCOUNT_LINKING`` | Enable account linking for OIDC provider. This will link the OIDC accounts by email. Be sure that you have verified emails to prevent stealing accounts. | false |
     | ``AUTH_OIDC_ENABLE_DANGEROUS_CREDENTIALS_LINKING`` | Link an OIDC identity to an existing credentials user with the same email. The credentials login and existing user data are preserved. Requires the OIDC profile to contain `email_verified: true`. | false |
@@ -241,21 +244,18 @@ Homarr supports multiple authentication options, from internal userbase (credent
         - Create a group (e.g., `homarr-admins`) and assign users who require admin access.
 
         **2. Example .env file:**
-
-        Generate `SECRET_ENCRYPTION_KEY` with `openssl rand -hex 32`; do not copy an example key between installs.
-
-        ```bash
-        OIDC_CLIENT_ID=<REPLACE_WITH_OIDC_CLIENT_ID>
-        OIDC_CLIENT_SECRET=<REPLACE_WITH_OIDC_CLIENT_SECRET>
+        ```env
+        OIDC_CLIENT_ID=identificationid #OIDC client ID
+        OIDC_CLIENT_SECRET=secretsecretsecret #OIDC client secret
         OIDC_SLUG=homarr #Application slug in Authentik
         AUTH_DOMAIN=auth.example.com #Authentik FQDN
         ADMIN_GROUP=homarr-admins #Authentik group for Homarr admins
         HOMARR_FQDN=homarr.example.com #Homarr FQDN
-        SECRET_ENCRYPTION_KEY=<REPLACE_WITH_64_HEX_CHARACTERS>
+        SECRET_ENCRYPTION_KEY=encryptencryptencrypt #Homarr encryption key
         ```
 
         **3. Example Docker Compose configuration:**
-        ```yaml {14-24}
+        ```yaml {14-26}
         services:
           homarr:
             image: ghcr.io/homarr-labs/homarr:latest
@@ -269,6 +269,8 @@ Homarr supports multiple authentication options, from internal userbase (credent
             environment:
               - TZ=America/Los_Angeles
               - SECRET_ENCRYPTION_KEY=${SECRET_ENCRYPTION_KEY}
+              - BASE_URL=https://${HOMARR_FQDN}
+              - NEXTAUTH_URL=https://${HOMARR_FQDN}
               - AUTH_PROVIDERS=oidc #(optional: include ',credentials' to keep local accounts as fallback)
               - AUTH_OIDC_CLIENT_ID=${OIDC_CLIENT_ID}
               - AUTH_OIDC_CLIENT_SECRET=${OIDC_CLIENT_SECRET}
@@ -320,18 +322,15 @@ Homarr supports multiple authentication options, from internal userbase (credent
         - Record the `Client-ID` and `Client Key` (secret).
 
         **2. Example .env file (Homarr):**
-
-        Generate `SECRET_ENCRYPTION_KEY` with `openssl rand -hex 32`; do not copy an example key between installs.
-
-        ```bash
-        OIDC_CLIENT_ID=<REPLACE_WITH_GOOGLE_CLIENT_ID>
-        OIDC_CLIENT_SECRET=<REPLACE_WITH_GOOGLE_CLIENT_SECRET>
+        ```env
+        OIDC_CLIENT_ID=identificationid #Google Client-ID
+        OIDC_CLIENT_SECRET=secretsecretsecret #Google Client Key (secret)
         HOMARR_FQDN=homarr.example.com #Homarr FQDN
-        SECRET_ENCRYPTION_KEY=<REPLACE_WITH_64_HEX_CHARACTERS>
+        SECRET_ENCRYPTION_KEY=encryptencryptencrypt #Homarr encryption key
         ```
 
         **3. Example Docker Compose configuration (Homarr):**
-        ```yaml {14-20}
+        ```yaml {16-22}
         services:
           homarr:
             image: ghcr.io/homarr-labs/homarr:latest
@@ -345,6 +344,8 @@ Homarr supports multiple authentication options, from internal userbase (credent
             environment:
               - TZ=Europe/Berlin
               - SECRET_ENCRYPTION_KEY=${SECRET_ENCRYPTION_KEY}
+              - BASE_URL=https://${HOMARR_FQDN}
+              - NEXTAUTH_URL=https://${HOMARR_FQDN}
               - AUTH_PROVIDERS=oidc #(optional: include ',credentials' to keep local accounts as fallback)
               - AUTH_OIDC_CLIENT_ID=${OIDC_CLIENT_ID}
               - AUTH_OIDC_CLIENT_SECRET=${OIDC_CLIENT_SECRET}

apps/docs/docs/community/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Community",
+  "position": 6,
+  "collapsed": true,
+  "link": {
+    "type": "generated-index"
+  }
+}

apps/docs/docs/community/index.mdx

@@ -1,10 +0,0 @@
----
-title: Community
-description: Get help, contribute to Homarr, and support the project.
----
-
-- [Frequently asked questions](/docs/community/faq): resolve common setup and operation issues.
-- [Get in touch](/docs/community/get-in-touch): choose the right support or discussion channel.
-- [Translations](/docs/community/translations): improve Homarr in your language.
-- [Donate](/docs/community/donate): support ongoing development.
-- [License](/docs/community/license): understand how Homarr is licensed.

apps/docs/docs/community/meta.json

@@ -1,5 +0,0 @@
-{
-  "title": "Community",
-  "defaultOpen": false,
-  "pages": ["index", "faq", "get-in-touch", "translations", "donate", "license"]
-}

apps/docs/docs/getting-started/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Getting started",
+  "position": 1,
+  "collapsed": false,
+  "link": {
+    "type": "generated-index",
+    "title": "Getting started"
+  }
+}

apps/docs/docs/getting-started/after-the-installation.mdx

@@ -6,68 +6,11 @@ tags:
   - Configuration
 ---
 
-import {
-  IconAdjustments,
-  IconChecklist,
-  IconLayoutDashboard,
-  IconPlugConnected,
-  IconSearch,
-  IconSparkles,
-} from "@tabler/icons-react";
+On first launch, onboarding creates the administrator, connects optional services, and builds the first board. A
+compatible SQLite backup can also be restored from the welcome screen.
 
-import onboardingWelcome from "./img/onboarding-v2-welcome.png";
-import onboardingBoard from "./img/onboarding-v2-board.png";
-import onboardingReview from "./img/onboarding-v2-review.png";
-
-After Homarr starts, open its URL. An unfinished installation redirects to the onboarding screen at `/init`. Choose
-**Get started** for a new installation or **Restore backup** to import a compatible SQLite backup.
-
-<Callout type="info" title="Persist /appdata before you continue">
-  Onboarding writes the administrator and board configuration to the database. If onboarding returns after a restart,
-  check that `/appdata` is writable and persisted. See the
-  [Docker installation guide](/docs/getting-started/installation/docker).
-</Callout>
-
-## Complete onboarding
-
-Onboarding is split into six short sections. Integrations, Workshop, Assistant, and MCP are optional; skip them when you
-only need a working board.
-
-<Cards>
-  <Card icon={<IconAdjustments />} title="1. Essentials">
-    Choose the language, theme, usual server address, and anonymous analytics preference.
-  </Card>
-  <Card icon={<IconSearch />} title="2. Discover">
-    Review the database, Docker, Kubernetes, Assistant, and Workshop capabilities Homarr can reach.
-  </Card>
-  <Card icon={<IconPlugConnected />} title="3. Connect">
-    Import detected services or add integrations manually. Unfinished integrations can be skipped.
-  </Card>
-  <Card icon={<IconLayoutDashboard />} title="4. Board">
-    Set the board name, colors, corner radius, column count, and optional sidebars.
-  </Card>
-  <Card icon={<IconSparkles />} title="5. Extend">
-    Optionally connect the Workshop, configure an Assistant provider, or review the MCP endpoint.
-  </Card>
-  <Card icon={<IconChecklist />} title="6. Review">
-    Check the final summary, then build the board. Homarr opens the exact board it configured.
-  </Card>
-</Cards>
-
-The final screen links directly to the new board and the management area. Board layout, integrations, apps, and
-appearance can all be changed later.
-
-<Cards>
-  <Card title="Start or restore">
-    <img src={onboardingWelcome.src} alt="Homarr onboarding welcome screen with Get started and Restore backup actions" />
-  </Card>
-  <Card title="Configure the board">
-    <img src={onboardingBoard.src} alt="Board onboarding section for colors, columns, corner radius, and sidebars" />
-  </Card>
-  <Card title="Review before building">
-    <img src={onboardingReview.src} alt="Onboarding review showing the board settings Homarr will create" />
-  </Card>
-</Cards>
+If onboarding returns after a restart, check that `/appdata` is writable and persisted. See the
+[Docker installation guide](/docs/getting-started/installation/docker).
 
 ## Core concepts
 
@@ -97,7 +40,7 @@ Docker. Integrations provide data and actions to widgets. They can also be linke
 ![Integration catalog with compatible widgets](./img/after-installation-integrations.png)
 
 See [Managing integrations](/docs/management/integrations) and the
-[integration catalog](/docs/integrations).
+[integration catalog](/docs/category/integrations).
 
 ### Widgets
 
@@ -106,7 +49,7 @@ supported integrations, and non-obvious limitations are documented on each widge
 
 ![Board in edit mode with the add-content menu](./img/after-installation-widgets.png)
 
-See the [widget catalog](/docs/widgets).
+See the [widget catalog](/docs/category/widgets).
 
 ### Containers and rails
 

apps/docs/docs/getting-started/installation/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Installation",
+  "position": 1,
+  "collapsed": true,
+  "link": {
+    "type": "generated-index",
+    "title": "Getting started"
+  }
+}

apps/docs/docs/getting-started/installation/helm.md

@@ -2,9 +2,9 @@
 
 <img src="https://raw.githubusercontent.com/homarr-labs/charts/refs/heads/main/charts/homarr/icon.svg" align="right" width="92" alt="homarr logo">
 
-![Version: 8.28.2](https://img.shields.io/badge/Version-8.28.2-informational?style=flat)
+![Version: 8.28.1](https://img.shields.io/badge/Version-8.28.1-informational?style=flat)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat)
-![AppVersion: v1.76.2](https://img.shields.io/badge/AppVersion-v1.76.2-informational?style=flat)
+![AppVersion: v1.76.1](https://img.shields.io/badge/AppVersion-v1.76.1-informational?style=flat)
 
 A Helm chart to deploy homarr for Kubernetes
 
@@ -437,7 +437,7 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 | httproute.rules[0].matches[0].path.value           | string | `"/"`                                                                                                                                                                                                                                            | Path value to match                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | image.pullPolicy                                   | string | `"IfNotPresent"`                                                                                                                                                                                                                                 | Image pull policy                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | image.repository                                   | string | `"ghcr.io/homarr-labs/homarr"`                                                                                                                                                                                                                   | Image repository                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| image.tag                                          | string | `"v1.76.2"`                                                                                                                                                                                                                                      | Overrides the image tag whose default is the chart appVersion                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| image.tag                                          | string | `"v1.76.1"`                                                                                                                                                                                                                                      | Overrides the image tag whose default is the chart appVersion                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | imagePullSecrets                                   | list   | `[]`                                                                                                                                                                                                                                             | Secrets for Docker registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | ingress.annotations                                | object | `{}`                                                                                                                                                                                                                                             | Ingress annotations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | ingress.enabled                                    | bool   | `false`                                                                                                                                                                                                                                          | Enable ingress                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

apps/docs/docs/getting-started/installation/index.mdx

@@ -1,84 +0,0 @@
----
-title: Install Homarr
-description: Choose the installation method that matches your infrastructure.
-full: true
----
-
-import {
-  IconApps,
-  IconBox,
-  IconBrandDocker,
-  IconBrandGithub,
-  IconCloud,
-  IconContainer,
-  IconDatabase,
-  IconHexagons,
-  IconHome,
-  IconLayoutDashboard,
-  IconServer2,
-  IconTrain,
-} from "@tabler/icons-react";
-
-Docker Compose is the best starting point for most self-hosters. Choose a platform-specific guide when Homarr will run inside an existing server manager or managed service.
-
-<Callout type="idea" title="Not sure which guide to choose?">
-  Start with **Docker Compose**. It is the recommended path, has the broadest community support, and makes updates and
-  backups straightforward.
-</Callout>
-
-## Recommended
-
-<Cards>
-  <Card icon={<IconBrandDocker />} title="Docker Compose" href="/docs/getting-started/installation/docker">
-    The recommended installation for most Linux and Windows servers.
-  </Card>
-  <Card icon={<IconHexagons />} title="Kubernetes with Helm" href="/docs/getting-started/installation/helm">
-    Deploy Homarr into an existing Kubernetes cluster.
-  </Card>
-  <Card icon={<IconBrandGithub />} title="Build from source" href="/docs/getting-started/installation/source">
-    Build and run Homarr directly from the repository.
-  </Card>
-</Cards>
-
-## Self-hosting platforms
-
-<Cards>
-  <Card icon={<IconServer2 />} title="Unraid" href="/docs/getting-started/installation/unraid">
-    Install Homarr from the Unraid Community Apps catalog.
-  </Card>
-  <Card icon={<IconDatabase />} title="Synology" href="/docs/getting-started/installation/synology">
-    Run Homarr on a Synology NAS with Container Manager.
-  </Card>
-  <Card icon={<IconServer2 />} title="Proxmox" href="/docs/getting-started/installation/proxmox">
-    Add Homarr to a Proxmox-based homelab.
-  </Card>
-  <Card icon={<IconHome />} title="Home Assistant Add-on" href="/docs/getting-started/installation/home-assistant">
-    Install Homarr alongside your Home Assistant environment.
-  </Card>
-  <Card icon={<IconContainer />} title="Portainer" href="/docs/getting-started/installation/portainer">
-    Deploy and manage Homarr through Portainer stacks.
-  </Card>
-  <Card icon={<IconDatabase />} title="QNAP" href="/docs/getting-started/installation/qnap">
-    Run Homarr on a QNAP NAS.
-  </Card>
-  <Card icon={<IconApps />} title="Runtipi" href="/docs/getting-started/installation/runtipi">
-    Add Homarr from the Runtipi app store.
-  </Card>
-</Cards>
-
-## Managed and app platforms
-
-<Cards>
-  <Card icon={<IconLayoutDashboard />} title="EasyPanel" href="/docs/getting-started/installation/easy-panel">
-    Deploy Homarr from an Easypanel template.
-  </Card>
-  <Card icon={<IconTrain />} title="Railway" href="/docs/getting-started/installation/railway">
-    Launch Homarr as a managed Railway service.
-  </Card>
-  <Card icon={<IconCloud />} title="PikaPods" href="/docs/getting-started/installation/pika-pods">
-    Use a hosted Homarr instance without managing a server.
-  </Card>
-  <Card icon={<IconBox />} title="Saltbox" href="/docs/getting-started/installation/saltbox">
-    Add Homarr to a Saltbox deployment.
-  </Card>
-</Cards>

apps/docs/docs/getting-started/installation/meta.json

@@ -1,24 +0,0 @@
-{
-  "title": "Installation",
-  "defaultOpen": false,
-  "pages": [
-    "index",
-    "---Recommended---",
-    "docker",
-    "helm",
-    "source",
-    "---Self-hosting platforms---",
-    "unraid",
-    "synology",
-    "proxmox",
-    "home-assistant",
-    "portainer",
-    "qnap",
-    "runtipi",
-    "---Managed and app platforms---",
-    "easy-panel",
-    "railway",
-    "pika-pods",
-    "saltbox"
-  ]
-}

apps/docs/docs/getting-started/installation/source.mdx

@@ -38,14 +38,13 @@ This method is only useful, when you want to develop on Homarr or extend it with
     Install all dependencies using <code>pnpm install</code>
   </li>
   <li>
-    Copy the `.env.example` file to `.env`. Its `DB_URL='./db.sqlite'` value is ready for local use and stores the
-    database in the cloned repository. Replace it with an absolute writable path such as
-    `DB_URL='/home/username/homarr/db.sqlite'` if you want to store the database elsewhere.
+    Copy the `.env.example` file to `.env` and replace `DB_URL` with the full path you want to use for the sqlite
+    database file. For example `DB_URL='/home/username/homarr/db.sqlite`
   </li>
   <li>
-    Run `openssl rand -hex 32` twice and set `AUTH_SECRET` and `SECRET_ENCRYPTION_KEY` to the two different generated
-    values. Keep both values secret and preserve `SECRET_ENCRYPTION_KEY` with your backups.
+    Replace `AUTH_SECRET` and `SECRET_ENCRYPTION_KEY` both with a secure random string by using `openssl rand -hex 32`
   </li>
+  <li>Replace `CRON_JOB_API_KEY` with a secure random string by using `openssl rand -base64 32`</li>
   <li>Run `pnpm run db:migration:sqlite:run` and wait that it completes</li>
   <li>Build the source using `pnpm build`</li>
   <li>

apps/docs/docs/getting-started/installation/unraid.mdx

@@ -1,4 +1,4 @@
-import Link from "@/components/mdx/link";
+import Link from "@docusaurus/Link";
 import { IconDownload } from "@tabler/icons-react";
 
 # Unraid

apps/docs/docs/getting-started/meta.json

@@ -1,5 +0,0 @@
-{
-  "title": "Getting started",
-  "defaultOpen": false,
-  "pages": ["index", "installation", "after-the-installation", "upgrade-v2", "glossary"]
-}

apps/docs/docs/getting-started/upgrade-v2.mdx

@@ -1,74 +0,0 @@
----
-title: Upgrade from v1 to v2
-sidebar_position: 2
-tags:
-  - Getting started
-  - Upgrade
-  - Migration
-  - Backup
----
-
-Homarr v2 upgrades the existing v1 database in place. Keep the same data storage, database configuration, and
-`SECRET_ENCRYPTION_KEY`; only change the Homarr image or package version for the first start.
-
-:::danger Back up before starting v2
-
-In Homarr v1, go to **Management → Tools → Backup**, export a backup, and keep the downloaded file somewhere safe
-before starting v2. See [Backup and restore](/docs/management/backup) for details.
-
-:::
-
-## Upgrade
-
-1. Pin the Homarr image to `ghcr.io/homarr-labs/homarr:v2.0.0` for the first v2 start.
-2. Keep the existing `/appdata` mount, database variables, Redis configuration, and `SECRET_ENCRYPTION_KEY` unchanged.
-3. Start one Homarr replica and follow its logs. Startup must reach `Migration complete`; Homarr aborts startup when a
-   database migration fails.
-4. Open Homarr and sign in. Confirm **Management → About** reports v2 before starting additional replicas.
-5. After validation, keep the version pinned or return to your normal stable release policy.
-
-For Docker Compose, the change is limited to the image tag before the usual update:
-
-```yaml
-services:
-  homarr:
-    image: ghcr.io/homarr-labs/homarr:v2.0.0
-```
-
-```sh
-docker compose pull
-docker compose up -d
-docker compose logs --follow homarr
-```
-
-Do not add `-v` when stopping the Compose deployment; that can remove named volumes.
-
-## What v2 migrates
-
-The startup migration:
-
-- creates the Custom Widget v2, Assistant, header preference, and branding storage;
-- adds Base/Mobile layout roles and left/right board gutters;
-- converts legacy Categories and dynamic sections into Containers and rails;
-- preserves legacy Custom Widget definitions, encrypted secrets, and board references for explicit migration.
-
-Legacy Custom Widgets are not silently rewritten. In **Management → Custom Widgets**, entries marked
-**Migration required** provide a credential-free migration prompt. Review and test the resulting v2 definition before
-removing the archived v1 version. See [Custom Widgets: Import and Workshop](/docs/management/custom-widgets#import-and-workshop).
-
-## Verify the upgraded instance
-
-- Sign in with each enabled authentication method and verify administrator access.
-- Open every important board on desktop and mobile. Check Containers, former Categories, rails, item placement, and
-  home-board assignments.
-- Test at least one read and one permitted action for each critical integration. Recheck integration and board access
-  for representative Viewer, Editor, and Admin groups.
-- Check Docker or Podman endpoints, search engines, uploaded media, trusted certificates, scheduled tasks, WebSockets,
-  and external Redis when used.
-- Review every legacy Custom Widget and migrate it only after its v2 preview and requests work.
-- Restart Homarr once more and confirm the logs contain no migration, database, Redis, authentication, or task errors.
-
-## Roll back
-
-Use the backup exported before the upgrade if you need to restore your v1 installation. Do not reuse a database that
-v2 has already migrated with v1.

apps/docs/docs/index.mdx

@@ -1,72 +0,0 @@
----
-title: Homarr documentation
-description: Install, configure, operate, and extend Homarr.
----
-
-import {
-  IconApi,
-  IconArrowUp,
-  IconBuildingStore,
-  IconChecklist,
-  IconCode,
-  IconComponents,
-  IconDownload,
-  IconLayoutDashboard,
-  IconPlugConnected,
-  IconSettings,
-  IconUsers,
-  IconVocabulary,
-} from "@tabler/icons-react";
-
-Use these guides to get Homarr running, connect your services, build useful boards, and manage an installation over time.
-
-## Install or upgrade
-
-<Cards>
-  <Card icon={<IconDownload />} title="Install Homarr" href="/docs/getting-started/installation">
-    Choose the installation method for your system.
-  </Card>
-  <Card icon={<IconArrowUp />} title="Upgrade from v1" href="/docs/getting-started/upgrade-v2">
-    Move an existing Homarr installation to v2.
-  </Card>
-  <Card icon={<IconChecklist />} title="Finish setup" href="/docs/getting-started/after-the-installation">
-    Add apps, integrations, and widgets after installation.
-  </Card>
-  <Card icon={<IconVocabulary />} title="Learn the concepts" href="/docs/getting-started">
-    Understand boards, apps, integrations, and widgets.
-  </Card>
-</Cards>
-
-## Configure Homarr
-
-<Cards>
-  <Card icon={<IconLayoutDashboard />} title="Boards and content" href="/docs/management">
-    Configure boards, apps, users, settings, and administration.
-  </Card>
-  <Card icon={<IconPlugConnected />} title="Connect services" href="/docs/integrations">
-    Find the setup guide for an integration.
-  </Card>
-  <Card icon={<IconComponents />} title="Choose widgets" href="/docs/widgets">
-    Find the content and controls available for boards.
-  </Card>
-  <Card icon={<IconSettings />} title="Advanced configuration" href="/docs/advanced">
-    Configure deployment, authentication, networking, and automation.
-  </Card>
-</Cards>
-
-## Extend and contribute
-
-<Cards>
-  <Card icon={<IconCode />} title="Custom Widgets" href="/docs/management/custom-widgets">
-    Author and publish Custom JSX widgets.
-  </Card>
-  <Card icon={<IconBuildingStore />} title="Community Workshop" href="/docs/workshop">
-    Use and operate the community extension registry.
-  </Card>
-  <Card icon={<IconApi />} title="API reference" href="/api-reference">
-    Inspect Homarr's HTTP API.
-  </Card>
-  <Card icon={<IconUsers />} title="Get help and contribute" href="/docs/community">
-    Find support and ways to contribute.
-  </Card>
-</Cards>

apps/docs/docs/integrations/_category_.json

@@ -0,0 +1,10 @@
+{
+  "label": "Integrations",
+  "collapsed": true,
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "title": "Integrations",
+    "description": "Integration are a principal part of homarr, it's where you can connect your other apps to interact with them with widgets or other capabilities, Homarr currently integrates with the following applications:"
+  }
+}

apps/docs/docs/integrations/coolify/index.mdx

@@ -21,7 +21,7 @@ import { coolifyWidget } from "../../widgets/coolify";
 
 <AddingIntegration />
 
-:::info[URL configuration]
+:::info URL configuration
 Use the root URL of your Coolify instance, for example `https://coolify.example.com`. Homarr calls Coolify endpoints under `/api` and `/api/v1` automatically.
 :::
 

apps/docs/docs/integrations/deluge/index.mdx

@@ -9,7 +9,7 @@ import { IntegrationCapabilites } from "@site/src/components/integrations/widget
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
 import { IconDownload } from "@tabler/icons-react";
-import Alert from "@/components/mdx/admonition";
+import Alert from "@theme/Admonition";
 import { delugeIntegration } from ".";
 import { downloadsWidget } from "@site/docs/widgets/downloads";
 

apps/docs/docs/integrations/docker/index.mdx

@@ -117,7 +117,7 @@ updating a Homarr resource still requires confirmation. If one endpoint is unava
 endpoints remain visible.
 
 The `homarr.hide` label excludes a container. Other `homarr.*` labels can provide apps, integrations, groups, and widgets
-during onboarding; see [Docker label discovery](/docs/integrations/docker-labels).
+during onboarding; see [Docker label discovery](../docker-labels).
 
 ## Security
 

apps/docs/docs/integrations/index.mdx

@@ -1,21 +0,0 @@
----
-title: Integrations
-description: Connect Homarr to the applications and infrastructure you operate.
----
-
-import { DocsDirectory } from "@/components/docs/docs-directory";
-
-An integration stores the connection and authentication details Homarr needs to communicate with another service. Widgets and management tools can then reuse that connection.
-
-Each guide identifies the required URL and credentials, supported capabilities, and the widgets that use the integration.
-
-<DocsDirectory section="integrations" />
-
-## Before you connect a service
-
-1. Confirm that Homarr can reach the service from its own network.
-2. Create the least-privileged account, token, or API key supported by the service.
-3. Add the integration in **Manage → Integrations**.
-4. Test the connection before adding dependent widgets.
-
-See [Manage integrations](/docs/management/integrations) for the shared workflow.

apps/docs/docs/integrations/meta.json

@@ -1,5 +0,0 @@
-{
-  "title": "Integrations",
-  "defaultOpen": false,
-  "pages": ["index", "..."]
-}

apps/docs/docs/integrations/nextcloud/index.mdx

@@ -9,7 +9,7 @@ import { IntegrationCapabilites } from "@site/src/components/integrations/widget
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
 import { IconCalendar } from "@tabler/icons-react";
-import Alert from "@/components/mdx/admonition";
+import Alert from "@theme/Admonition";
 import { nextcloudIntegration } from ".";
 import { calendarWidget } from "@site/docs/widgets/calendar";
 import { notificationsWidget } from "@site/docs/widgets/notifications";

apps/docs/docs/integrations/nzbget/index.mdx

@@ -10,7 +10,7 @@ import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
 import { IconDownload } from "@tabler/icons-react";
 import { nzbgetIntegration } from ".";
-import Alert from "@/components/mdx/admonition";
+import Alert from "@theme/Admonition";
 import { downloadsWidget } from "@site/docs/widgets/downloads";
 
 <IntegrationHeader integration={nzbgetIntegration} categories={["Usenet client"]} />

apps/docs/docs/integrations/open-media-vault/index.mdx

@@ -10,7 +10,7 @@ import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
 import { IconHeartRateMonitor } from "@tabler/icons-react";
 import { openMediaVaultIntegration } from ".";
-import Alert from "@/components/mdx/admonition";
+import Alert from "@theme/Admonition";
 import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
 import { systemResourcesWidget } from "@site/docs/widgets/system-resources";