revert(perf): drop the dockerode and docker-modem pnpm patches

Both patches came out of this work and both are removed at the maintainer's
request. The finding was real - ssh2's WASM heap costs +14.0 MiB RSS on require,
and @grpc/grpc-js another 14.6 MiB across 61 files, neither of which a
socket-based Docker install ever uses - but patching a dependency means every
future dockerode or docker-modem bump fails until someone regenerates the patch,
and that recurring cost is not worth roughly 25 MiB.

The finding stays on record in SERVER-MEMORY.md because the fix belongs upstream:
both packages require a module at file scope while using it in exactly one
already-guarded branch, so a PR to each would fix it for every consumer with no
patch to maintain here.

The two remaining patches, @types/node-unifi and trpc-to-openapi, predate this
work and are untouched. allowUnusedPatches was already set on dev and is left
alone. Lockfile regenerated: patchedDependencies now lists only those two.

Also sharpens the Cache Components entry. The SqliteError was simply an unmigrated
build database, which is fixable - but feeding the build a database would be the
wrong fix, because serverSetting is per-installation data on the user's volume and
a shell prerendered against the build machine's database would bake one install's
settings into every other install's first paint. The error was Next.js correctly
reporting a request-time read sitting in the shell path.

.agents/skills/homarr-custom-widget/SKILL.md

@@ -1,36 +0,0 @@
----
-name: homarr-custom-widget
-description: Author safe Homarr Custom JSX v2 widgets from API documentation.
----
-
-# Homarr Custom Widget
-
-Author one widget at a time. When connected to Homarr, retrieve `homarr://custom-widgets/schema` and only the component resources needed for the design. The live resources are authoritative for the installed release.
-
-Keep documentation retrieval targeted: fetch at most eight named component documents before the first validation, or at most four after loading a complete example. Fetch another component only when a validation issue or a concrete missing interaction requires it; never load the catalog component-by-component.
-
-1. Read the API documentation.
-2. Create one credential-free widget with keyed `sources`, keyed `requests`, optional keyed `options`, and safe JSX `template`.
-3. Validate, preview, test queries and simulated actions, visually inspect, and iterate.
-4. Configure deployment-specific source URLs and request credentials through Homarr; never repeat plaintext.
-5. Save only after narrow/wide, light/dark, loading, empty, error, and success states work. When connected through MCP, persist the exact final tested preview with `customWidget_createFromPreview`; do not resend a large template through `customWidget_create` unless no preview session is available.
-
-Treat a supplied sample or successful preview response as the binding contract. Render every core requested field, guard optional arrays and nested values before indexing, and do not silently drop returned items. Show concise freshness context when the API supplies a timestamp. Give recoverable load errors and empty states a clear refresh or retry path.
-
-Use `{option:name}` or `$option` for saved options. Use `{param:name}` or `$param` for values supplied by `SubFetch`, `ActionButton`, or `ToggleSwitch`. Load queries cannot use invocation parameters. Templates read `data`, `status`, `options`, and temporary `inputs`.
-
-`SubFetch` with `trigger="manual"` renders its own load button. Pass a card or image through `triggerContent` with `triggerAriaLabel` when that content should launch the request. Its callback is `(result, meta)`; never author `onClick` or a fetch callback.
-
-Use standard Mantine compound names and deliberate visual hierarchy, spacing, restrained semantic color, and responsive layouts. Avoid excessive nested cards.
-
-Aim for distinctive polish without decorative gradients or fragile custom styling: use one semantic accent, clear surface contrast, purposeful typography, and compact rows that remain scannable in narrow tiles. Give standalone icons an accessible label or pair them with visible text.
-
-Make initial states actionable with an example, useful hint, or clear next step. Use wrapping groups for variable-length labels and values on narrow tiles. Do not use an unlabeled decorative icon as an empty state.
-
-Do not use imports, hooks, refs, raw HTML, raw event callbacks, browser requests, arbitrary functions, eval, bigint, npm packages, authored statement blocks, IIFEs, or recursion. Do not pretend MCP tools exist in an offline chat session.
-
-To install an existing widget, use `customWidget_workshopSearch`, inspect it with `customWidget_workshopGet`, then use `customWidget_workshopInstall`. Configure each self-hosted source afterward with `customWidget_sourceConfigure`, or call `customWidget_configurationRequestUser` so the user can enter the server URL and credentials directly in Homarr.
-
-Preview-scoped configuration expires with the preview. To persist user-entered values for a new widget, create the widget first, request configuration for its definition ID, then create a final preview with that definition ID so Homarr loads the stored credentials.
-
-When this skill is installed from the repository, optional offline details are in `references/schema.md`, `references/runtime.md`, and `references/security.md`. MCP-only clients should use the live Homarr resources instead.

.agents/skills/homarr-custom-widget/references/runtime.md

@@ -1,16 +0,0 @@
-# Runtime
-
-Templates read `data.requestId`, `status.requestId`, `options.name`, and temporary `inputs.name`. Status contains `loading`, `ok`, `status`, `statusText`, and `error`.
-
-`bind="search"` creates an in-memory input. It is never persisted. Supply invocation values only through `params`, for example:
-
-```jsx
-<TextInput bind="search" label="Search" />
-<SubFetch requestId="search" params={{ query: inputs.search }}>
-  {(items) => <Stack>{(items ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
-</SubFetch>
-```
-
-`SubFetch` with `trigger="manual"` renders its own load button. To make a card or image launch the request, pass that node through `triggerContent` and provide `triggerAriaLabel`; Homarr supplies the click and keyboard behavior. Its optional second callback argument contains `{ ok, status, statusText, loading: false }`; loading and request failures are rendered by `SubFetch` before the callback runs. Do not author `onClick` or a fetch callback.
-
-Use expression callbacks for supported collection methods and trusted slots. Do not use callback blocks, IIFEs, authored recursion, or raw events. Bounded regex literals work only with safe string matching/replacement operations.

.agents/skills/homarr-custom-widget/references/schema.md

@@ -1,22 +0,0 @@
-# Schema
-
-```ts
-interface HomarrCustomWidgetV2 {
-  $schema: "homarr-custom-widget-v2";
-  name: string;
-  description?: string;
-  iconUrl?: string;
-  sources: Record<string, CustomWidgetSource>;
-  requests: Record<string, CustomWidgetRequest>;
-  options?: Record<string, CustomWidgetOption>;
-  template: string;
-}
-```
-
-Sources require `default`. A request defaults to the default source, query, GET, load, inherited auth, and view permission. An action defaults to manual and modify permission. DELETE uses full permission and confirmation.
-
-Use stable real URLs for public APIs and clear suggested URLs for self-hosted services. Homarr collects the installer's server URL, network scope, and credentials as source setup; credentials remain outside the manifest.
-
-Paths use `{option:name}` and `{param:name}`. Query/body data uses `{ "$option": "name" }` and `{ "$param": "name" }`. Load queries cannot use params. Runtime parameter names and primitive values are inferred from references.
-
-Every option has `label`, `control`, and `default`. Optional fields are `description`, `choices`, `choicesFrom`, `min`, `max`, `step`, `advanced`, and `group`.

.agents/skills/homarr-custom-widget/references/security.md

@@ -1,7 +0,0 @@
-# Security
-
-All requests use Homarr's protected server executor. Source origin, network scope, DNS, redirects, SSRF, rate limits, permissions, size limits, timeouts, and encrypted credential injection remain enforced.
-
-The JSX interpreter blocks imports, hooks, refs, raw event callbacks, browser requests, eval, arbitrary functions, prototype access, unsafe URLs, global CSS escape, arbitrary portals, bigint, statement blocks, IIFEs, and recursion. Regex literals must be bounded and reject backreferences, lookbehind, nested quantifiers, excessive length, and unsupported flags.
-
-Credentials are stored separately and never exported or returned to an agent. A published self-hosted source URL is only a suggestion: installers must confirm or replace private and loopback URLs for their own Homarr deployment. Source origins cannot be controlled through widget options.

.cursor/rules/codebase-context.mdc

@@ -66,6 +66,8 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
+│   ├── old-import/      # Legacy Homarr import
+│   ├── old-schema/      # Legacy Homarr zod schemas
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig

.cursor/rules/mantine-datatable-migration.mdc

@@ -263,6 +263,15 @@ Even hidden options need translation keys or the translation test fails:
 "widget.mywidget.option.columnWidths.label": "Column widths"
 ```
 
+### Old-import mappings
+
+Add to `packages/old-import/src/widgets/options.ts`:
+
+```typescript
+columnOrder: () => undefined,
+columnWidths: () => undefined,
+```
+
 ### Dynamic storeKey
 
 Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
@@ -601,12 +610,13 @@ if (isEditMode) rowContextMenuHandler = undefined;
 4. Add CSS file for transparent backgrounds (if widget context)
 5. Add responsive column visibility (if widget context)
 6. Add hidden options + hydration logic (if column persistence needed)
-7. Add translation keys (including hidden option labels)
-8. Add context menu if row actions exist
-9. Add row expansion if detail view exists
-10. Add error handling on all mutations
-11. Add accessibility attributes
-12. Test at multiple widget widths
-13. Update docs in `apps/docs/docs/widgets/` if applicable
-14. Run `pnpm turbo typecheck`
-15. Run translation spec — catches missing keys
+7. Add old-import mappings for new options
+8. Add translation keys (including hidden option labels)
+9. Add context menu if row actions exist
+10. Add row expansion if detail view exists
+11. Add error handling on all mutations
+12. Add accessibility attributes
+13. Test at multiple widget widths
+14. Update docs in `apps/docs/docs/widgets/` if applicable
+15. Run `pnpm turbo typecheck` — catches old-import mismatches
+16. Run translation spec — catches missing keys

.deepsource.toml

@@ -0,0 +1,8 @@
+version = 1
+
+[[analyzers]]
+name = "javascript"
+
+[analyzers.meta]
+plugins = ["react"]
+environment = ["nodejs"]

.env.example

@@ -55,37 +55,19 @@ TURBO_TELEMETRY_DISABLED=1
 # Example: DOCKER_SOCKET_PATHS=/var/run/docker.sock,/run/user/1000/podman/podman.sock
 # DOCKER_SOCKET_PATHS=
 
+# Redis DB index for the Next.js cache handler (default: 1).
+# Must differ from REDIS_DATABASE_INDEX (default: 0) to avoid cache ops affecting app data.
+# REDIS_CACHE_DB=1
+
 # Enable kubernetes tool
 # ENABLE_KUBERNETES=true
 
 # Enable mock integration
 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.
-HOMARR_WEBSITE_URL=https://homarr.dev
-# PocketBase API used by Homarr and by the standalone documentation site.
-# Defaults to HOMARR_WEBSITE_URL.
-# WORKSHOP_API_URL=https://homarr.dev
-# Public Workshop website used by links in Homarr, Custom Widgets, onboarding,
-# and assistant context. Defaults to HOMARR_WEBSITE_URL/workshop.
-# WORKSHOP_WEB_URL=https://homarr.dev/workshop
-
-# Documentation and PocketBase deployment settings.
-# WORKSHOP_PUBLIC_ORIGIN=https://homarr.dev
-# PB_ALLOWED_ORIGINS=*
-
-# Local Workshop stack:
-# HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-# WORKSHOP_API_URL=http://127.0.0.1:8090
-# WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-# WORKSHOP_PUBLIC_ORIGIN=http://127.0.0.1:3003
-# Optional: GITHUB_CLIENT_ID=
-# Optional: GITHUB_CLIENT_SECRET=
-
 # Enable demo mode (seeds a demo user "demo"/"demo", a sample board and a mock integration)
 # DEMO_MODE=true
 
 # Whether demo mode is read-only. Defaults to true (the public demo blocks all mutations).
 # Set to false for writable preview deployments so the demo user can modify the dashboard.
-# DEMO_READ_ONLY=false
+# DEMO_READ_ONLY=false

.github/pull_request_template.md

@@ -16,6 +16,6 @@
 **When contributing a new integration or widget:**
 
 - [ ] I confirmed manually that the integration or widget is working with a real system and performed basic smoke
-      tests (e.g. what happens if it is offline)
+  tests (e.g. what happens if it is offline)
 - [ ] Optional but recommended: I confirm that I am willing to be added to the `CODEOWNERS` of this feature and will
-      provide support and maintain the integration (e.g. in case of breaking or failure)
+  provide support and maintain the integration (e.g. in case of breaking or failure)

.github/workflows/autofix.yml

@@ -1,4 +1,4 @@
-name: Formatting
+name: Auto-fix lint and format
 
 on:
   pull_request:
@@ -6,30 +6,42 @@ on:
     branches: ["*"]
 
 permissions:
-  contents: read
+  contents: write
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
   cancel-in-progress: true
 
 jobs:
-  format:
-    name: Check formatting
+  autofix:
+    name: Auto-fix
+    if: github.event.pull_request.head.repo.id == github.repository_id
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
       - uses: actions/checkout@v7
         with:
           fetch-depth: 0
-          persist-credentials: false
+          ref: ${{ github.head_ref }}
 
       - name: Setup
         uses: ./tooling/github/setup
 
-      - name: Check changed files
+      - name: Get changed files
+        id: changed
         env:
           BASE_REF: ${{ github.base_ref }}
         run: |
-          git diff --name-only --diff-filter=ACMR -z "origin/${BASE_REF}...HEAD" -- \
-            '*.css' '*.js' '*.json' '*.jsonc' '*.jsx' '*.md' '*.mdx' '*.scss' '*.ts' '*.tsx' '*.yaml' '*.yml' \
-            | xargs -0 -r pnpm exec oxfmt --check --
+          git diff --name-only --diff-filter=ACMR "origin/${BASE_REF}...HEAD" -- '*.ts' '*.tsx' '*.js' '*.jsx' > /tmp/changed-files
+          echo "count=$(wc -l < /tmp/changed-files | tr -d '[:space:]')" >> $GITHUB_OUTPUT
+
+      - name: Auto-fix lint + format
+        if: steps.changed.outputs.count != '0'
+        run: |
+          xargs -r -a /tmp/changed-files pnpm exec oxlint --fix || true
+          xargs -r -a /tmp/changed-files pnpm exec oxfmt --write
+
+      - name: Commit fixes
+        uses: stefanzweifel/git-auto-commit-action@v7
+        with:
+          commit_message: "style: auto-fix lint and format"

.github/workflows/ci.yml

@@ -3,12 +3,12 @@ name: CI
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["**"]
+    branches: ["*"]
   pull_request_target:
     types: [closed]
-    branches: ["**"]
+    branches: ["*"]
   push:
-    branches: [main, dev, beta, next, v2, release/v2]
+    branches: [main, dev, beta, next]
   merge_group:
   workflow_dispatch:
     inputs:
@@ -34,10 +34,8 @@ permissions:
   contents: read
 
 concurrency:
-  # Every event for a PR shares one group so a close event cancels stale image
-  # publication and a newer synchronize run cannot be overwritten by an older run.
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
-  cancel-in-progress: ${{ github.event_name == 'pull_request' || github.event_name == 'pull_request_target' || github.event_name == 'workflow_dispatch' || github.ref != 'refs/heads/main' }}
+  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
 
 env:
   FORCE_COLOR: 3
@@ -89,36 +87,21 @@ jobs:
       - name: Validate workspace configuration
         run: pnpm lint:ws
 
-      - name: Validate Custom Widget architecture
-        run: pnpm check:custom-widgets
-
-      - name: Validate checked-in OpenAPI schema
-        run: pnpm check:openapi
-
-      - name: Validate Custom Widget bundle budget
-        run: |
-          pnpm --filter nextjs build
-          pnpm check:custom-widget-bundle
-
       - name: Run unit tests
         run: pnpm test
 
   container:
     name: Container and E2E
-    needs: [fast-gate, preview-amd64]
+    needs: fast-gate
     if: |
-      !cancelled() && needs.fast-gate.result == 'success' &&
-      (
-        github.event_name == 'merge_group' ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
-        (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-        (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
-      )
+      github.event_name == 'merge_group' ||
+      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
+      (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
     runs-on: ubuntu-latest
     timeout-minutes: 30
     permissions:
       contents: read
-      packages: read
+      packages: write
     steps:
       - uses: actions/checkout@v7
         if: "!env.ACT"
@@ -133,18 +116,8 @@ jobs:
         if: "!env.ACT"
         uses: docker/setup-buildx-action@v4
 
-      - name: Reuse amd64 preview image
-        if: needs.preview-amd64.outputs.digest != '' && !env.ACT
-        env:
-          DIGEST: ${{ needs.preview-amd64.outputs.digest }}
-        run: |
-          echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u "${{ github.actor }}" --password-stdin
-          docker pull "${PREVIEW_IMAGE}@${DIGEST}"
-          docker tag "${PREVIEW_IMAGE}@${DIGEST}" homarr-ci
-          docker tag "${PREVIEW_IMAGE}@${DIGEST}" homarr-e2e
-
       - name: Build container once
-        if: needs.preview-amd64.outputs.digest == '' && !env.ACT
+        if: "!env.ACT"
         uses: docker/build-push-action@v7
         with:
           context: .
@@ -159,8 +132,8 @@ jobs:
             org.opencontainers.image.source=${{ github.server_url }}/${{ github.repository }}
             org.opencontainers.image.revision=${{ github.sha }}
             org.opencontainers.image.ref.name=pr-${{ github.event.pull_request.number || inputs.pr_number || 'none' }}
-          cache-from: type=gha,scope=homarr-e2e
-          cache-to: type=gha,scope=homarr-e2e,mode=max
+          cache-from: type=gha,scope=homarr-linux-amd64
+          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
           secrets: |
             TURBO_API=${{ secrets.TURBO_API }}
             TURBO_TEAM=${{ secrets.TURBO_TEAM }}
@@ -201,10 +174,7 @@ jobs:
         run: pnpm exec playwright install-deps chromium
 
       - name: Run E2E tests
-        env:
-          NODE_ENV: development
-          CI: "true"
-        run: pnpm exec vitest e2e --retry 1 --maxWorkers 4
+        run: pnpm test:e2e
 
       - name: Upload E2E artifacts
         if: failure() && !env.ACT
@@ -214,191 +184,37 @@ jobs:
           path: e2e/test-results/
           retention-days: 7
 
-  preview-amd64:
-    name: Build amd64 preview image
-    needs: fast-gate
-    if: |
-      (
-        (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
-        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-      )
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.preview-build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Log in to GHCR
-        if: "!env.ACT"
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build and push amd64 preview image by digest
-        id: preview-build
-        if: "!env.ACT"
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/amd64
-          outputs: type=image,"name=${{ env.PREVIEW_IMAGE }}",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=homarr-linux-amd64
-          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-
-  preview-arm64:
-    name: Build arm64 preview image
-    needs: fast-gate
-    if: |
-      (
-        (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
-        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-      )
-    runs-on: ubuntu-24.04-arm
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.preview-build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Log in to GHCR
-        if: "!env.ACT"
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build and push arm64 preview image by digest
-        id: preview-build
-        if: "!env.ACT"
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/arm64
-          outputs: type=image,"name=${{ env.PREVIEW_IMAGE }}",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=homarr-linux-arm64
-          cache-to: type=gha,scope=homarr-linux-arm64,mode=max
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-
-  publish-preview:
-    name: Publish multi-platform preview image
-    needs: [preview-amd64, preview-arm64]
-    if: |
-      (
-        (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
-        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-      )
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    permissions:
-      contents: read
-      packages: write
-      pull-requests: read
-    env:
-      PREVIEW_TAG: ${{ github.event_name == 'push' && 'v2' || format('pr-{0}', github.event.pull_request.number || inputs.pr_number) }}
-    steps:
-      - name: Log in to GHCR
-        if: "!env.ACT"
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Verify PR head before publication
-        if: github.event_name == 'pull_request'
-        uses: actions/github-script@v8
+      - name: Determine preview tag
+        id: preview
+        if: |
+          !env.ACT &&
+          (
+            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
+            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
+          )
         env:
-          EXPECTED_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+          PR_NUMBER: ${{ github.event.pull_request.number || inputs.pr_number }}
+        run: echo "tag=pr-${PR_NUMBER}" >> "$GITHUB_OUTPUT"
+
+      - name: Log in to GHCR
+        if: steps.preview.outputs.tag != ''
+        uses: docker/login-action@v4
         with:
-          script: |
-            const { data: pull } = await github.rest.pulls.get({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              pull_number: context.payload.pull_request.number,
-            });
-            if (pull.state !== "open") {
-              core.setFailed(`PR #${pull.number} is ${pull.state}; refusing to publish its preview.`);
-              return;
-            }
-            if (pull.head.sha !== process.env.EXPECTED_HEAD_SHA) {
-              core.setFailed(`PR #${pull.number} moved from ${process.env.EXPECTED_HEAD_SHA} to ${pull.head.sha}.`);
-            }
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Publish preview manifest
-        if: "!env.ACT"
+      - name: Push preview image
+        if: steps.preview.outputs.tag != ''
         env:
-          AMD64_DIGEST: ${{ needs.preview-amd64.outputs.digest }}
-          ARM64_DIGEST: ${{ needs.preview-arm64.outputs.digest }}
+          PREVIEW_TAG: ${{ steps.preview.outputs.tag }}
         run: |
-          tags=(-t "${PREVIEW_IMAGE}:${PREVIEW_TAG}")
-          if [[ "${GITHUB_EVENT_NAME}" == "push" && "${GITHUB_REF}" == "refs/heads/release/v2" ]]; then
-            tags+=(-t "${PREVIEW_IMAGE}:pr-6545")
-          fi
-          docker buildx imagetools create "${tags[@]}" \
-            "${PREVIEW_IMAGE}@${AMD64_DIGEST}" \
-            "${PREVIEW_IMAGE}@${ARM64_DIGEST}"
+          docker tag homarr-ci "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
+          docker push "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
 
-      - name: Verify preview manifest platforms
-        if: "!env.ACT"
-        run: |
-          tags=("${PREVIEW_TAG}")
-          if [[ "${GITHUB_EVENT_NAME}" == "push" && "${GITHUB_REF}" == "refs/heads/release/v2" ]]; then
-            tags+=("pr-6545")
-          fi
-          for tag in "${tags[@]}"; do
-            image="${PREVIEW_IMAGE}:${tag}"
-            manifest="$(docker buildx imagetools inspect "$image" --raw)"
-            for architecture in amd64 arm64; do
-              jq --exit-status --arg architecture "$architecture" \
-                'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
-                <<<"$manifest" >/dev/null
-            done
-            docker buildx imagetools inspect "$image"
-          done
+      - name: Show Act publication result
+        if: env.ACT
+        run: echo "Act validated the publication path; external GHCR writes are disabled locally."
 
   cleanup:
     name: Clean up preview image

.github/workflows/skip-renovate-stability-days.yml

@@ -1,6 +1,5 @@
 permissions:
   statuses: write
-  contents: read
 
 on:
   pull_request:
@@ -17,20 +16,12 @@ jobs:
         env:
           GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
         run: |
-          for attempt in 1 2 3 4 5; do
-            if gh api \
-              --method POST \
-              -H "Accept: application/vnd.github+json" \
-              -H "X-GitHub-Api-Version: 2022-11-28" \
-              /repos/${{github.repository}}/statuses/${{github.event.pull_request.head.sha}} \
-              -f 'state=success' \
-              -f 'target_url=https://docs.renovatebot.com/configuration-options#minimumreleaseage' \
-              -f 'description=Skipped for non renovate branches' \
-              -f 'context=renovate/stability-days' \
-              --silent; then
-              exit 0
-            fi
-            echo "status POST failed (attempt $attempt/5), retrying in 5s"
-            sleep 5
-          done
-          exit 1
+          gh api \
+          --method POST \
+          -H "Accept: application/vnd.github+json" \
+          -H "X-GitHub-Api-Version: 2022-11-28" \
+          /repos/${{github.repository}}/statuses/${{github.event.pull_request.head.sha}} \
+          -f 'state=success' \
+          -f 'target_url=https://docs.renovatebot.com/configuration-options#minimumreleaseage' \
+          -f 'description=Skipped for non renovate branches' \
+          -f 'context=renovate/stability-days'

.github/workflows/workshop.yml

@@ -1,129 +0,0 @@
-name: Workshop
-
-on:
-  pull_request:
-  push:
-    branches: [dev, v2, release/v2, main]
-
-permissions:
-  contents: read
-
-jobs:
-  validate:
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    steps:
-      - uses: actions/checkout@v7
-      - uses: actions/setup-node@v6
-        with:
-          node-version: 24.18.0
-      - uses: pnpm/action-setup@v6
-        with:
-          run_install: false
-      - run: pnpm install --frozen-lockfile
-      - run: pnpm --filter @homarr/workshop typecheck
-      - run: pnpm --filter @homarr/docs typecheck
-      - run: docker compose --env-file apps/workshop/.env.staging.example -f apps/workshop/docker-compose.staging.yml config --quiet
-      - run: pnpm test:workshop
-      - run: pnpm test:workshop-image
-
-  publish-amd64:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: validate
-    runs-on: ubuntu-24.04
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/build-push-action@v7
-        id: build
-        with:
-          context: .
-          file: apps/workshop/Dockerfile
-          target: production
-          platforms: linux/amd64
-          outputs: type=image,"name=ghcr.io/homarr-labs/workshop",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=workshop-linux-amd64
-          cache-to: type=gha,scope=workshop-linux-amd64,mode=max
-
-  publish-arm64:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: validate
-    runs-on: ubuntu-24.04-arm
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/build-push-action@v7
-        id: build
-        with:
-          context: .
-          file: apps/workshop/Dockerfile
-          target: production
-          platforms: linux/arm64
-          outputs: type=image,"name=ghcr.io/homarr-labs/workshop",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=workshop-linux-arm64
-          cache-to: type=gha,scope=workshop-linux-arm64,mode=max
-
-  publish:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: [publish-amd64, publish-arm64]
-    runs-on: ubuntu-24.04
-    timeout-minutes: 5
-    permissions:
-      contents: read
-      packages: write
-    env:
-      WORKSHOP_IMAGE: ghcr.io/homarr-labs/workshop
-    steps:
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - name: Publish multi-platform image
-        env:
-          AMD64_DIGEST: ${{ needs.publish-amd64.outputs.digest }}
-          ARM64_DIGEST: ${{ needs.publish-arm64.outputs.digest }}
-        run: |
-          tags=(-t "${WORKSHOP_IMAGE}:sha-${GITHUB_SHA}")
-          if [[ "${GITHUB_REF_NAME}" == "v2" || "${GITHUB_REF_NAME}" == "release/v2" ]]; then
-            tags+=(-t "${WORKSHOP_IMAGE}:v2")
-          fi
-          if [[ "${GITHUB_REF_NAME}" == "main" ]]; then
-            tags+=(-t "${WORKSHOP_IMAGE}:latest")
-          fi
-          docker buildx imagetools create "${tags[@]}" \
-            "${WORKSHOP_IMAGE}@${AMD64_DIGEST}" \
-            "${WORKSHOP_IMAGE}@${ARM64_DIGEST}"
-      - name: Verify multi-platform image
-        run: |
-          image="${WORKSHOP_IMAGE}:sha-${GITHUB_SHA}"
-          manifest="$(docker buildx imagetools inspect "$image" --raw)"
-          for architecture in amd64 arm64; do
-            jq --exit-status --arg architecture "$architecture" \
-              'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
-              <<<"$manifest" >/dev/null
-          done
-          docker buildx imagetools inspect "$image"

.gitignore

@@ -16,7 +16,6 @@ out/
 next-env.d.ts
 
 # artifacts
-.ai-evaluations/
 packages/db/migrations/*/migrate.cjs
 
 # nitro
@@ -25,8 +24,6 @@ packages/db/migrations/*/migrate.cjs
 
 # production
 build
-tools/homarr-dev/homarr
-tools/homarr-dev/homarr-dev
 
 # misc
 .DS_Store
@@ -74,11 +71,7 @@ apps/nextjs/public/images/background.png
 
 # personal agent config
 .opencode
-.agents/*
-!.agents/skills/
-.agents/skills/*
-!.agents/skills/homarr-custom-widget/
-!.agents/skills/homarr-custom-widget/**
+.agents/
 skills-lock.json
 
 # docusaurus
@@ -86,14 +79,11 @@ apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
 benchmark-results
-
-# local performance investigation (never ship benchmark data or restored backups)
-.widget-performance/
 .bench/
+
+# Homarr backups used by scripts/benchmarks/stress-restore.mts. These contain
+# real integration secrets and an encryption key — never commit one.
 homarr-backup*.zip
+*.sqlite
 *.sqlite-wal
 *.sqlite-shm
-/scripts/benchmarks/
-
-# PR description screenshots belong on the pull request, not in the repository
-.screenshots/

.oxfmtrc.json

@@ -3,15 +3,5 @@
   "printWidth": 120,
   "endOfLine": "lf",
   "sortPackageJson": true,
-  "ignorePatterns": [
-    "**/*.cjs",
-    "**/lang/**",
-    "static-data/**",
-    "CHANGELOG.md",
-    "apps/docs/.docusaurus/**",
-    "apps/docs/build/**",
-    "apps/docs/blog/**",
-    "packages/custom-widgets/src/core/component-catalog.generated.json",
-    "apps/docs/static/custom-widgets/component-catalog-v1.json"
-  ]
+  "ignorePatterns": ["**/*.cjs", "**/lang/**", "static-data/**", "CHANGELOG.md", "apps/docs/.docusaurus/**", "apps/docs/build/**", "apps/docs/blog/**"]
 }

.oxlintrc.json

@@ -30,35 +30,7 @@
   "options": {
     "reportUnusedDisableDirectives": "off"
   },
-  "overrides": [
-    {
-      "files": ["apps/nextjs/src/**/*.ts", "apps/nextjs/src/**/*.tsx"],
-      "excludeFiles": ["**/*.spec.ts", "**/*.spec.tsx"],
-      "rules": {
-        "eslint/no-restricted-imports": [
-          "error",
-          {
-            "paths": [
-              {
-                "name": "@homarr/widgets",
-                "allowTypeImports": true,
-                "message": "Import a narrow @homarr/widgets export to preserve widget lazy loading."
-              }
-            ]
-          }
-        ]
-      }
-    }
-  ],
-  "ignorePatterns": [
-    "**/*.config.js",
-    "**/*.config.mjs",
-    "**/*.cjs",
-    "**/lang/*.d.json.ts",
-    ".next/**",
-    "apps/docs/.docusaurus/**",
-    "apps/docs/build/**"
-  ],
+  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", "**/lang/*.d.json.ts", ".next/**", "apps/docs/.docusaurus/**", "apps/docs/build/**"],
   "settings": {
     "react": { "version": "19" }
   }

AGENTS.md

@@ -40,6 +40,8 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
+│   ├── old-import/      # Legacy Homarr import
+│   ├── old-schema/      # Legacy Homarr zod schemas
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig

CHANGES.md

@@ -0,0 +1,96 @@
+# Changes
+
+## Goal
+
+Remove widget-only services from Homarr's global Integration system.
+
+The affected services are release providers and Search.ch. They are only used by specific widgets, so keeping them as global integrations added unnecessary setup, UI, database rows, docs pages, and integration package code.
+
+ArchiveTeam Warrior remains a proper integration but is no longer auto-seeded on first install.
+
+## Why
+
+These services do not need shared integration state.
+
+- Release providers are selected per Releases widget repository.
+- Search.ch is only used by the Timetable widget.
+
+Moving them into widget options makes configuration simpler and removes dead-weight integration code from `packages/integrations`.
+
+## What Changed
+
+### Release Providers
+
+- Added release provider definitions in `packages/definitions/src/release-provider.ts`.
+- Removed release providers from `IntegrationKind`.
+- Moved release-fetching code out of `packages/integrations` and into `packages/request-handler/src/release-providers.ts`.
+- Updated the Releases widget to store provider configuration directly in widget options:
+  - `provider`
+  - `identifier`
+  - `versionFilter`
+  - `providerUrl`
+- Updated the Releases widget editor to use a provider select instead of an integration select.
+- Updated Docker import mapping so `ghcr.io` maps to `gitHubContainerRegistry`.
+- GitHub Container Registry now uses the public OCI registry API and accepts full image references such as `ghcr.io/homarr-labs/homarr:latest`.
+
+### Timetable / Search.ch
+
+- Removed Search.ch as an integration.
+- Added a Timetable widget `baseUrl` option, defaulting to `https://search.ch`.
+- Moved Search.ch request/parsing logic into `packages/request-handler/src/timetable.ts`.
+- Updated the Timetable API to receive `baseUrl` directly from widget options.
+
+### ArchiveTeam Warrior
+
+- Kept as a proper integration (not removed).
+- Removed `defaultUrl` from the integration definition to prevent auto-seeding on first install.
+
+### Integration Cleanup
+
+- Removed creators, exports, docs references, and implementation files for the deleted integrations.
+- Removed unused dependencies from `packages/integrations/package.json`.
+
+### Database Migration
+
+- Added `packages/db/migrations/custom/0003_remove_widget_only_integrations.ts`.
+- The migration moves old integration-linked widget config into widget options, then deletes the old widget-only integration rows.
+- Updated the earlier release widget migration to use the new `provider` field instead of `providerIntegrationId`.
+
+### Docs
+
+- Updated Releases widget docs to describe providers instead of integrations.
+- Updated Timetable docs to remove Search.ch integration setup.
+- Removed obsolete integration docs pages for the deleted integration kinds.
+- Updated docs sitemap and integration docs mappings.
+
+### Translations
+
+- Added English labels for the new widget options:
+  - `widget.timetable.option.baseUrl.label`
+  - `widget.releases.option.repositories.providerUrl.label`
+
+## How It Works Now
+
+Release provider configuration lives on each Releases widget repository entry. The request handler resolves provider metadata and fetches releases directly from the provider-specific endpoint. GHCR uses anonymous OCI registry access for public packages.
+
+Timetable passes its widget URL option directly to its API router and request handler. No global integration lookup is needed.
+
+ArchiveTeam Warrior continues to use the standard integration system, but users must manually add the integration (it is not auto-created on install).
+
+## Deliberate Non-Goals
+
+- No provider secret/token support was added.
+- No new secret storage model was introduced.
+- No compatibility layer was kept in `packages/integrations`.
+
+Widget options are client-visible, so storing provider credentials there would be wrong. If authenticated provider requests are needed later, they need a separate secret-storage design.
+
+## Verification So Far
+
+- Focused typechecks passed for affected packages.
+- Full `pnpm turbo typecheck` passed.
+- Full `pnpm lint` passed with existing warnings.
+- Focused release provider normalization tests passed.
+- Widget translation test passed.
+- Live GHCR smoke checks passed for `ghcr.io/muchobien/pocketbase:latest` and `ghcr.io/homarr-labs/homarr:latest`.
+- `pnpm test packages/integrations/test/pi-hole.spec.ts` passed earlier, but failed on rebased reruns because Pi-hole reported `domainsBeingBlocked` as `-2`/`0` instead of `> 1`.

Dockerfile

@@ -22,7 +22,7 @@ COPY --parents ./packages/definitions/src ./
 # isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
 # which IS created by pnpm fetch. The original hoisted linker is restored
 # before the install step so the final node_modules layout stays flat.
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
     pnpm config set store-dir /pnpm/store && \
     sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
     pnpm fetch --ignore-scripts && \
@@ -31,7 +31,7 @@ RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
 # Install only from the fetched, committed lockfile so local and Docker builds
 # resolve the same dependency graph. Serial lifecycle builds avoid esbuild's
 # atomic binary replacement racing across the hoisted workspace (pnpm/pnpm#8200).
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
     npm_config_nodedir=/usr/local pnpm install --recursive --offline --frozen-lockfile --child-concurrency=1
 
 COPY . .
@@ -40,6 +40,25 @@ ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
 ARG DISABLE_REDIS_LOGS='true'
 ARG TARGETPLATFORM
+# Opt-in React profiling build + browser source maps, for React DevTools' Profiler
+# and for readable names in heap snapshots. See next.config.ts.
+ARG HOMARR_PROFILING='false'
+ENV HOMARR_PROFILING=${HOMARR_PROFILING}
+
+# React ships a separate profiling renderer; the production one omits the hooks
+# DevTools needs, which is what makes it report "Profiling not supported". Next only
+# swaps it via a webpack alias (create-compiler-aliases.js), so under Turbopack both
+# `next build --profile` and `reactProductionProfiling` silently produce a normal
+# build. Point the vendored client entry at the profiling bundle instead — the same
+# swap webpack's alias performs, done where Turbopack cannot miss it.
+RUN if [ "$HOMARR_PROFILING" = "true" ]; then \
+      set -e; \
+      entry=node_modules/next/dist/compiled/react-dom/client.js; \
+      grep -q "react-dom-client.production.js" "$entry" || { echo "profiling patch: unexpected $entry"; exit 1; }; \
+      sed -i "s#./cjs/react-dom-client.production.js#./cjs/react-dom-profiling.profiling.js#" "$entry"; \
+      grep -q "react-dom-profiling.profiling.js" "$entry" || { echo "profiling patch failed"; exit 1; }; \
+      echo "profiling patch applied to $entry"; \
+    fi
 
 RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
     --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \

MANTINE.md

@@ -1,475 +0,0 @@
-# Mantine UI - LLM Documentation
-
-This index lists Mantine documentation pages formatted for LLMs.
-Each link points to a standalone Markdown file under the /llms path.
-
-For a single consolidated file with all content, use:
-
-- https://mantine.dev/llms-full.txt
-
-## FAQ
-
-- [Are Mantine components accessible?](https://mantine.dev/llms/q-are-mantine-components-accessible.md): Learn about Mantine components accessibility features
-- [Browser zooms in when input is focused. What should I do?](https://mantine.dev/llms/q-browser-zooms-on-focus.md): Use meta tag to disable browser scaling or increase input size
-- [Can I have color schemes other than light and dark?](https://mantine.dev/llms/q-light-dark-is-not-enough.md): Learn about the difference between color scheme and theme
-- [Can I have different primary color for light and dark color schemes?](https://mantine.dev/llms/q-primary-virtual-color.md): Learn how to use virtual color with primary color in theme object
-- [Can I remove MultiSelect placeholder when the component has selected values?](https://mantine.dev/llms/q-multiselect-value-placeholder.md): Learn why MultiSelect placeholder is not removed when values are selected and how to remove it with CSS
-- [Can I use an array of strings as a list in use-form?](https://mantine.dev/llms/q-list-of-strings-in-use-form.md): Learn about use-form lists limitations
-- [Can I use Mantine components as server components?](https://mantine.dev/llms/q-server-components.md): Learn about use client directive and server components usage
-- [Can I use Mantine with Astro?](https://mantine.dev/llms/q-can-i-use-mantine-with-astro.md): No, Astro does not support React context
-- [Can I use Mantine with Create React App (CRA)?](https://mantine.dev/llms/q-can-i-use-mantine-with-cra.md): Learn how to use Mantine without postcss-preset-mantine or how to eject CRA and customize webpack.config.js and use postcss-preset-mantine
-- [Can I use Mantine with Emotion/styled-components/tailwindcss?](https://mantine.dev/llms/q-third-party-styles.md): Learn about limitations of third-party styles
-- [Can I use Mantine with Vue/Svelte/Angular/etc.?](https://mantine.dev/llms/q-vue-svelte-angular.md): No, Mantine is a React library and does not support other frameworks/libraries
-- [Can I use nested inline styles with Mantine components?](https://mantine.dev/llms/q-nested-inline-styles.md): Nested styles are supported only in CSS files
-- [Can I use PostCSS function in inline styles?](https://mantine.dev/llms/q-postcss-fns-inline.md): Learn where PostCSS functions can be used in Mantine
-- [Can I use private CSS variables to style components?](https://mantine.dev/llms/q-private-css-variables.md): No, it is not safe and will not work with future versions of Mantine.
-- [Can I use SegmentedControl with empty value?](https://mantine.dev/llms/q-segmented-control-no-value.md): SegmentedControl cannot be used without a value
-- [How can I add dynamic CSS styles?](https://mantine.dev/llms/q-dynamic-css-styles.md): Use data attributes, CSS variables or inline styles
-- [How can I add fuzzy search to Select component?](https://mantine.dev/llms/q-select-fuzzy.md): Learn how to integrate third-party fuzzy search libraries with Mantine Select component
-- [How can I add hover styles to an element?](https://mantine.dev/llms/q-how-to-add-hover-styles.md): Learn how to add hover classes to an element with CSS modules, &:hover or @mixin hover
-- [How can I apply styles to all Mantine components?](https://mantine.dev/llms/q-apply-styles-to-all.md): Learn how to use attribute selector to apply styles to all Mantine components
-- [How can I change body background color?](https://mantine.dev/llms/q-body-background.md): Use CSS to change body background color
-- [How can I change component color prop value depending on the color scheme?](https://mantine.dev/llms/q-color-scheme-color.md): Learn how to use CSS variables resolver to change color value depending on the color scheme
-- [How can I change input focus styles?](https://mantine.dev/llms/q-input-focus-styles.md): Learn how to use Styles API with Mantine inputs
-- [How can I change Tabs border color?](https://mantine.dev/llms/q-tabs-border-color.md): Learn how to use Styles API with Tabs component
-- [How can I contribute to the library?](https://mantine.dev/llms/q-how-can-i-contribute.md): There are multiple ways to contribute even without writing code
-- [How can I disable all inputs/input groups inside a form?](https://mantine.dev/llms/q-disable-all-inputs-in-form.md): Learn how to disable all inputs/input groups inside a form with the unstyled Fieldset component
-- [How can I display different elements in light and dark color schemes?](https://mantine.dev/llms/q-light-dark-elements.md): Learn how to hide/show elements based on color scheme
-- [How can I focus the first input with error with use-form?](https://mantine.dev/llms/q-focus-first-input-with-error.md): Learn how to handle focus with use-form hook
-- [How can I get current color scheme value in JavaScript?](https://mantine.dev/llms/q-how-to-get-color-scheme-value-in-js.md): How to use useMantineColorScheme and useComputedColorScheme hooks to get current color scheme value in JavaScript
-- [How can I lint CSS files?](https://mantine.dev/llms/q-how-to-setup-stylelint.md): Learn how to set up Stylelint for Mantine postcss syntax
-- [How can I load fonts in Next.js?](https://mantine.dev/llms/q-next-load-fonts.md): A guide to load custom fonts in Next.js with CSS and next/font package
-- [How can I load fonts in React Router?](https://mantine.dev/llms/q-react-router-load-fonts.md): A guide to load custom fonts in React Router
-- [How can I load fonts in Vite?](https://mantine.dev/llms/q-vite-load-fonts.md): A guide to load custom fonts in Vite
-- [How can I lock scroll in my application?](https://mantine.dev/llms/q-how-to-lock-scroll.md): Use react-remove-scroll library to lock scroll in your application
-- [How can I submit a template to Mantine documentation?](https://mantine.dev/llms/q-submit-template.md): Learn how to create and submit a template to Mantine documentation
-- [How can I test Modal/Drawer/Popover components?](https://mantine.dev/llms/q-portals-testing.md): Learn how to use react-testing-library to test components that use portals and transitions.
-- [How can I test Select/MultiSelect components?](https://mantine.dev/llms/q-combobox-testing.md): Learn how to use react-testing-library to test Select and MultiSelect components.
-- [How can I upload files from Dropzone component?](https://mantine.dev/llms/q-dropzone-upload.md): Learn how to process files dropped into Dropzone component
-- [How is that thing done on the mantine.dev website?](https://mantine.dev/llms/q-how-that-thing-is-done.md): Learn how various elements are implemented on the mantine.dev website
-- [How to align input with a button in a flex container?](https://mantine.dev/llms/q-align-input-button.md): Learn how to align Mantine inputs with buttons using Group component
-- [How to call a function when Modal/Drawer closes and animation completes?](https://mantine.dev/llms/q-how-to-call-function-when-modal-closes.md): How to use transitionProps in Modal/Drawer components
-- [How to change background color for FiveM?](https://mantine.dev/llms/q-fivem-background-color.md): Unset body background color and color-scheme styles for FiveM
-- [How to change input placeholder color?](https://mantine.dev/llms/q-inputs-placeholder-color.md): Learn how to change placeholder color with Styles API
-- [How to integrate custom input with use-form hook?](https://mantine.dev/llms/q-custom-input-use-form.md): Learn how to add use-form support for custom inputs
-- [How to prevent Modal from closing?](https://mantine.dev/llms/q-how-to-prevent-modal-from-closing.md): Learn how to prevent Modal from closing when the user clicks outside of it or presses the Escape key
-- [How to scroll to the top of the form if the form is submitted with errors?](https://mantine.dev/llms/q-scroll-to-the-top-of-the-form.md): Learn how to call a function when the form is submitted with errors
-- [How to update Mantine dependencies?](https://mantine.dev/llms/q-how-to-update-dependencies.md): Learn how to update `@mantine/*`, `@mantinex/*` and `postcss-preset-mantine` dependencies manually or with ncu script
-- [How to use Dropzone with @mantine/form?](https://mantine.dev/llms/q-how-to-use-dropzone-with-form.md): Learn how to use Dropzone with @mantine/form to handle file selection state
-- [How to use Mantine template on GitHub?](https://mantine.dev/llms/q-templates-usage.md): Learn how to create a new repository based on Mantine template
-- [I get hydration warning about data-mantine-color-scheme attribute, what does it mean?](https://mantine.dev/llms/q-color-scheme-hydration-warning.md): Learn how hydration works and how to fix warnings
-- [Is there a comparison with other libraries?](https://mantine.dev/llms/q-other-libs.md): Comparison with other libraries is not provided, you are trusted to make your own decision based on documentation examples
-- [Is there a floating action button component?](https://mantine.dev/llms/q-floating-action-button.md): No, but you can build it with Affix and ActionIcon components
-- [Is there DataGrid component that I can use with Mantine?](https://mantine.dev/llms/q-data-grid-i-need.md): A list of community packages that provide DataGrid component that can be used with Mantine.
-- [It is not possible to pinch to zoom when a Modal is opened. What should I do?](https://mantine.dev/llms/q-pinch-to-zoom-modal.md): Use removeScrollProps to configure react-remove-scroll options
-- [MantineProvider was not found in component tree. What should I do?](https://mantine.dev/llms/q-mantine-provider-missing.md): Learn how to resolve MantineProvider issues
-- [My buttons are transparent and the background is visible only on hover, what is wrong?](https://mantine.dev/llms/q-transparent-buttons.md): You have installed a third-party library that overrides Mantine styles
-- [My Popover dropdown closes when I click on the dropdown of a nested Popover](https://mantine.dev/llms/q-nested-popover-closes.md): Popover dropdown is closed when it detects click-outside events
-- [My styles are broken with disabled JavaScript. What should I do?](https://mantine.dev/llms/q-disabled-js.md): Learn how to use Mantine without JavaScript enabled
-- [My styles are overridden by Mantine components styles, what should I do?](https://mantine.dev/llms/q-styles-order.md): Learn how to use CSS layers to control styles order and prevent Mantine components from overriding your styles
-- [Native browser validation does not work in some components, what should I do?](https://mantine.dev/llms/q-native-required.md): Learn why native browser validation does not work in some components
-- [The use-local-storage hook returns the real value only after mounting. Is it a bug?](https://mantine.dev/llms/q-local-storage-effect.md): Learn how Mantine retrieves local storage value
-- [What is the difference between searchable Select and Autocomplete?](https://mantine.dev/llms/q-select-autocomplete-difference.md): Searchable Select and Autocomplete are similar components, but they serve different purposes.
-- [Where can I find the roadmap?](https://mantine.dev/llms/q-roadmap.md): The roadmap is private and only available to the team.
-- [Why are my Carousel slides in vertical orientation?](https://mantine.dev/llms/q-carousel-missing-styles.md): You forgot to import carousel styles
-- [Why are my notifications displayed at the wrong position?](https://mantine.dev/llms/q-notifications-missing-styles.md): Because you did not import styles
-- [Why can I not use one polymorphic component in the component prop of another polymorphic component?](https://mantine.dev/llms/q-polymorphic-in-polymorphic.md): Learn how polymorphic components types work
-- [Why can I not use value/label data structure with Autocomplete/TagsInput?](https://mantine.dev/llms/q-autocomplete-value-label.md): Learn the difference between Autocomplete and Select components
-- [Why can VSCode not autoimport the Text component?](https://mantine.dev/llms/q-why-vscode-cannot-autoimport-text.md): It is confused by the native Text constructor
-- [Why do I see color scheme flickering on page load?](https://mantine.dev/llms/q-color-scheme-flickering.md): Color scheme flickering is caused by incorrect usage of ColorSchemeScript
-- [Why do my dates components look broken?](https://mantine.dev/llms/q-dates-missing-styles.md): Because you did not import styles
-- [Why does FileButton not work in Menu?](https://mantine.dev/llms/q-file-button-in-menu.md): Learn how to use FileButton in Menu component
-- [Why is it required to have 10 shades per color?](https://mantine.dev/llms/q-ten-shades-per-color.md): Learn how Mantine uses theme colors
-- [Why is my screen completely empty after I](https://mantine.dev/llms/q-notifications-empty-screen.md): You have used Notifications component incorrectly
-
-## Core
-
-- [Accordion](https://mantine.dev/llms/core-accordion.md): Divide content into collapsible sections
-- [ActionIcon](https://mantine.dev/llms/core-action-icon.md): Icon button
-- [Affix](https://mantine.dev/llms/core-affix.md): Renders children inside portal at fixed position
-- [Alert](https://mantine.dev/llms/core-alert.md): Attract user attention with important static message
-- [AlphaSlider](https://mantine.dev/llms/core-alpha-slider.md): Slider component for selecting alpha channel in color pickers (0 – 1)
-- [Anchor](https://mantine.dev/llms/core-anchor.md): Display link with theme styles
-- [AngleSlider](https://mantine.dev/llms/core-angle-slider.md): Pick angle value between 0 and 360
-- [AppShell](https://mantine.dev/llms/core-app-shell.md): Responsive shell for your application with header, navbar, aside and footer
-- [AspectRatio](https://mantine.dev/llms/core-aspect-ratio.md): Maintain responsive consistent width/height ratio
-- [Autocomplete](https://mantine.dev/llms/core-autocomplete.md): Autocomplete user input with any list of options
-- [Avatar](https://mantine.dev/llms/core-avatar.md): Display user profile image, initials or fallback icon
-- [BackgroundImage](https://mantine.dev/llms/core-background-image.md): Displays image as background
-- [Badge](https://mantine.dev/llms/core-badge.md): Display badge, pill or tag
-- [Blockquote](https://mantine.dev/llms/core-blockquote.md): Blockquote with optional cite
-- [Box](https://mantine.dev/llms/core-box.md): Base component for all Mantine components
-- [Breadcrumbs](https://mantine.dev/llms/core-breadcrumbs.md): Separates list of react nodes with given separator
-- [Burger](https://mantine.dev/llms/core-burger.md): Open/close navigation button
-- [Button](https://mantine.dev/llms/core-button.md): Button component to render button or link
-- [Card](https://mantine.dev/llms/core-card.md): Card with sections
-- [Cascader](https://mantine.dev/llms/core-cascader.md): Select a path from hierarchical data with cascading columns
-- [Center](https://mantine.dev/llms/core-center.md): Centers content vertically and horizontally
-- [Checkbox](https://mantine.dev/llms/core-checkbox.md): Capture boolean input from user
-- [Chip](https://mantine.dev/llms/core-chip.md): Pick one or multiple values with inline controls
-- [CloseButton](https://mantine.dev/llms/core-close-button.md): Button with close icon
-- [Code](https://mantine.dev/llms/core-code.md): Inline and block code
-- [Collapse](https://mantine.dev/llms/core-collapse.md): Animate presence with slide down/up transition
-- [ColorInput](https://mantine.dev/llms/core-color-input.md): Capture color from user
-- [ColorPicker](https://mantine.dev/llms/core-color-picker.md): Pick colors in hex(a), rgb(a), hsl(a) and hsv(a) formats
-- [ColorSwatch](https://mantine.dev/llms/core-color-swatch.md): Displays color
-- [Combobox](https://mantine.dev/llms/core-combobox.md): Create custom select, autocomplete or multiselect inputs
-- [ComboboxPopover](https://mantine.dev/llms/core-combobox-popover.md): Add combobox dropdown to any button element
-- [Container](https://mantine.dev/llms/core-container.md): Center content with padding and max-width
-- [CopyButton](https://mantine.dev/llms/core-copy-button.md): Copies given text to clipboard
-- [CorePackage](https://mantine.dev/llms/core-package.md)
-- [DataList](https://mantine.dev/llms/core-data-list.md): Display label-value pairs as a description list
-- [Dialog](https://mantine.dev/llms/core-dialog.md): Display a fixed overlay dialog at any side of the screen
-- [Divider](https://mantine.dev/llms/core-divider.md): Horizontal line with optional label or vertical divider
-- [Drawer](https://mantine.dev/llms/core-drawer.md): Display overlay area at any side of the screen
-- [EmptyState](https://mantine.dev/llms/core-empty-state.md): Display a placeholder for no data, empty results and first-run states
-- [Fieldset](https://mantine.dev/llms/core-fieldset.md): Group related elements in a form
-- [FileButton](https://mantine.dev/llms/core-file-button.md): Open file picker with a button click
-- [FileInput](https://mantine.dev/llms/core-file-input.md): Capture files from user
-- [Flex](https://mantine.dev/llms/core-flex.md): Compose elements in a flex container
-- [FloatingIndicator](https://mantine.dev/llms/core-floating-indicator.md): Display a floating indicator over a group of elements
-- [FloatingWindow](https://mantine.dev/llms/core-floating-window.md): Draggable floating area
-- [FocusTrap](https://mantine.dev/llms/core-focus-trap.md): Trap focus at child node
-- [Grid](https://mantine.dev/llms/core-grid.md): Responsive 12 columns grid system
-- [Group](https://mantine.dev/llms/core-group.md): Compose elements and components in a horizontal flex container
-- [Highlight](https://mantine.dev/llms/core-highlight.md): Highlight given part of a string with mark
-- [HoverCard](https://mantine.dev/llms/core-hover-card.md): Display popover section when target element is hovered
-- [HueSlider](https://mantine.dev/llms/core-hue-slider.md): Slider component for selecting hue channel in color pickers (0 – 360 degrees)
-- [Image](https://mantine.dev/llms/core-image.md): Image with optional fallback
-- [Indicator](https://mantine.dev/llms/core-indicator.md): Display element at the corner of another element
-- [Input](https://mantine.dev/llms/core-input.md): Base component to create custom inputs
-- [JsonInput](https://mantine.dev/llms/core-json-input.md): Capture json data from user
-- [Kbd](https://mantine.dev/llms/core-kbd.md): Display keyboard key
-- [List](https://mantine.dev/llms/core-list.md): Display ordered or unordered list
-- [Loader](https://mantine.dev/llms/core-loader.md): Indicate loading state
-- [LoadingOverlay](https://mantine.dev/llms/core-loading-overlay.md): An overlay with centered loader
-- [Mark](https://mantine.dev/llms/core-mark.md): Highlight part of the text
-- [Marquee](https://mantine.dev/llms/core-marquee.md): Create continuous scrolling animation for content
-- [MaskInput](https://mantine.dev/llms/core-mask-input.md): Input with mask pattern for formatted text entry
-- [Menu](https://mantine.dev/llms/core-menu.md): Combine a list of secondary actions into single interactive area
-- [Menubar](https://mantine.dev/llms/core-menubar.md): Desktop application style menubar with a row of menu triggers
-- [Modal](https://mantine.dev/llms/core-modal.md): An accessible overlay dialog
-- [MultiSelect](https://mantine.dev/llms/core-multi-select.md): Custom searchable multi select
-- [NativeSelect](https://mantine.dev/llms/core-native-select.md): Native select element based on Input
-- [NavLink](https://mantine.dev/llms/core-nav-link.md): Navigation link
-- [Notification](https://mantine.dev/llms/core-notification.md): Show dynamic notifications and alerts to user, part of notifications system
-- [NumberFormatter](https://mantine.dev/llms/core-number-formatter.md): Format number with thousands/decimal separators and suffix/prefix
-- [NumberInput](https://mantine.dev/llms/core-number-input.md): Capture number from user
-- [OverflowList](https://mantine.dev/llms/core-overflow-list.md): Hide items that do not fit in a container and display them as a single collapsed item
-- [Overlay](https://mantine.dev/llms/core-overlay.md): Overlays parent element with div element with any color and opacity
-- [Pagination](https://mantine.dev/llms/core-pagination.md): Display active page and navigate between multiple pages
-- [Paper](https://mantine.dev/llms/core-paper.md): Renders white or dark background depending on color scheme
-- [PasswordInput](https://mantine.dev/llms/core-password-input.md): Capture password data from user
-- [Pill](https://mantine.dev/llms/core-pill.md): Removable and non-removable tags
-- [PillsInput](https://mantine.dev/llms/core-pills-input.md): Base component for custom tags inputs and multi selects
-- [PinInput](https://mantine.dev/llms/core-pin-input.md): Capture pin code or one time password from the user
-- [Popover](https://mantine.dev/llms/core-popover.md): Display popover section relative to given target element
-- [Portal](https://mantine.dev/llms/core-portal.md): Renders component outside of parent element tree
-- [Progress](https://mantine.dev/llms/core-progress.md): Give user feedback for status of the task
-- [Radio](https://mantine.dev/llms/core-radio.md): Wrapper for input type radio
-- [RangeSlider](https://mantine.dev/llms/core-range-slider.md): RangeSlider component
-- [Rating](https://mantine.dev/llms/core-rating.md): Pick and display rating
-- [RingProgress](https://mantine.dev/llms/core-ring-progress.md): Give user feedback for status of the task with circle diagram
-- [RollingNumber](https://mantine.dev/llms/core-rolling-number.md): Animate value changes with rolling digits
-- [ScrollArea](https://mantine.dev/llms/core-scroll-area.md): Area with custom scrollbars
-- [Scroller](https://mantine.dev/llms/core-scroller.md): Horizontal scroll container with navigation controls
-- [SegmentedControl](https://mantine.dev/llms/core-segmented-control.md): A linear set of two or more segments
-- [Select](https://mantine.dev/llms/core-select.md): Custom searchable select
-- [SemiCircleProgress](https://mantine.dev/llms/core-semi-circle-progress.md): Represent progress with semi circle diagram
-- [SimpleGrid](https://mantine.dev/llms/core-simple-grid.md): Responsive grid in which each item takes equal amount of space
-- [Skeleton](https://mantine.dev/llms/core-skeleton.md): Indicate content loading state
-- [Slider](https://mantine.dev/llms/core-slider.md): Slider component
-- [Space](https://mantine.dev/llms/core-space.md): Add horizontal or vertical spacing from theme
-- [Splitter](https://mantine.dev/llms/core-splitter.md): Resizable split pane layout
-- [Spoiler](https://mantine.dev/llms/core-spoiler.md): Hide long sections of content under a spoiler
-- [Stack](https://mantine.dev/llms/core-stack.md): Compose elements and components in a vertical flex container
-- [Stepper](https://mantine.dev/llms/core-stepper.md): Display content divided into a steps sequence
-- [Switch](https://mantine.dev/llms/core-switch.md): Capture boolean input from user
-- [Table](https://mantine.dev/llms/core-table.md): Render table with theme styles
-- [TableOfContents](https://mantine.dev/llms/core-table-of-contents.md): Renders a list of headings on the page and tracks current heading visible in the viewport
-- [Tabs](https://mantine.dev/llms/core-tabs.md): Switch between different views
-- [TagsInput](https://mantine.dev/llms/core-tags-input.md): Capture a list of values from user with free input and suggestions
-- [Text](https://mantine.dev/llms/core-text.md): Display text
-- [Textarea](https://mantine.dev/llms/core-textarea.md): Autosize or regular textarea
-- [TextInput](https://mantine.dev/llms/core-text-input.md): Capture string input from user
-- [ThemeIcon](https://mantine.dev/llms/core-theme-icon.md): Render icon inside element with theme colors
-- [Timeline](https://mantine.dev/llms/core-timeline.md): Display list of events in chronological order
-- [Title](https://mantine.dev/llms/core-title.md): h1-h6 heading
-- [Tooltip](https://mantine.dev/llms/core-tooltip.md): Renders tooltip at given element on mouse over or other event
-- [Transition](https://mantine.dev/llms/core-transition.md): Animate presence of component with pre-made animations
-- [Tree](https://mantine.dev/llms/core-tree.md): Display a Tree structure
-- [TreeSelect](https://mantine.dev/llms/core-tree-select.md): Select with hierarchical tree data
-- [Typography](https://mantine.dev/llms/core-typography.md): Styles provider for html content
-- [UnstyledButton](https://mantine.dev/llms/core-unstyled-button.md): Unstyled polymorphic button
-- [VisuallyHidden](https://mantine.dev/llms/core-visually-hidden.md): Hide element visually but keep it accessible for screen readers
-
-## Hooks
-
-- [HooksPackage](https://mantine.dev/llms/hooks-package.md)
-- [use-element-size](https://mantine.dev/llms/hooks-use-element-size.md): Returns element width and height and observes changes with ResizeObserver
-- [useClickOutside](https://mantine.dev/llms/hooks-use-click-outside.md)
-- [useClipboard](https://mantine.dev/llms/hooks-use-clipboard.md)
-- [useCollapse](https://mantine.dev/llms/hooks-use-collapse.md)
-- [useColorScheme](https://mantine.dev/llms/hooks-use-color-scheme.md)
-- [useCounter](https://mantine.dev/llms/hooks-use-counter.md)
-- [useDebouncedCallback](https://mantine.dev/llms/hooks-use-debounced-callback.md)
-- [useDebouncedState](https://mantine.dev/llms/hooks-use-debounced-state.md)
-- [useDebouncedValue](https://mantine.dev/llms/hooks-use-debounced-value.md)
-- [useDidUpdate](https://mantine.dev/llms/hooks-use-did-update.md)
-- [useDisclosure](https://mantine.dev/llms/hooks-use-disclosure.md)
-- [useDocumentTitle](https://mantine.dev/llms/hooks-use-document-title.md)
-- [useDocumentVisibility](https://mantine.dev/llms/hooks-use-document-visibility.md)
-- [useDrag](https://mantine.dev/llms/hooks-use-drag.md)
-- [useEventListener](https://mantine.dev/llms/hooks-use-event-listener.md)
-- [useEyeDropper](https://mantine.dev/llms/hooks-use-eye-dropper.md)
-- [useFavicon](https://mantine.dev/llms/hooks-use-favicon.md)
-- [useFetch](https://mantine.dev/llms/hooks-use-fetch.md)
-- [useFileDialog](https://mantine.dev/llms/hooks-use-file-dialog.md)
-- [useFloatingWindow](https://mantine.dev/llms/hooks-use-floating-window.md)
-- [useFocusReturn](https://mantine.dev/llms/hooks-use-focus-return.md)
-- [useFocusTrap](https://mantine.dev/llms/hooks-use-focus-trap.md)
-- [useFocusWithin](https://mantine.dev/llms/hooks-use-focus-within.md)
-- [useForceUpdate](https://mantine.dev/llms/hooks-use-force-update.md)
-- [useFullscreen](https://mantine.dev/llms/hooks-use-fullscreen.md)
-- [useHash](https://mantine.dev/llms/hooks-use-hash.md)
-- [useHeadroom](https://mantine.dev/llms/hooks-use-headroom.md)
-- [useHotkeys](https://mantine.dev/llms/hooks-use-hotkeys.md)
-- [useHover](https://mantine.dev/llms/hooks-use-hover.md)
-- [useId](https://mantine.dev/llms/hooks-use-id.md)
-- [useIdle](https://mantine.dev/llms/hooks-use-idle.md)
-- [useInputState](https://mantine.dev/llms/hooks-use-input-state.md)
-- [useIntersection](https://mantine.dev/llms/hooks-use-intersection.md)
-- [useInterval](https://mantine.dev/llms/hooks-use-interval.md)
-- [useInViewport](https://mantine.dev/llms/hooks-use-in-viewport.md)
-- [useIsFirstRender](https://mantine.dev/llms/hooks-use-is-first-render.md)
-- [useIsomorphicEffect](https://mantine.dev/llms/hooks-use-isomorphic-effect.md)
-- [useListState](https://mantine.dev/llms/hooks-use-list-state.md)
-- [useLocalStorage](https://mantine.dev/llms/hooks-use-local-storage.md)
-- [useLogger](https://mantine.dev/llms/hooks-use-logger.md)
-- [useLongPress](https://mantine.dev/llms/hooks-use-long-press.md)
-- [useMap](https://mantine.dev/llms/hooks-use-map.md)
-- [useMask](https://mantine.dev/llms/hooks-use-mask.md)
-- [useMediaQuery](https://mantine.dev/llms/hooks-use-media-query.md)
-- [useMergedRef](https://mantine.dev/llms/hooks-use-merged-ref.md)
-- [useMounted](https://mantine.dev/llms/hooks-use-mounted.md)
-- [useMouse](https://mantine.dev/llms/hooks-use-mouse.md)
-- [useMove](https://mantine.dev/llms/hooks-use-move.md)
-- [useMutationObserver](https://mantine.dev/llms/hooks-use-mutation-observer.md)
-- [useNetwork](https://mantine.dev/llms/hooks-use-network.md)
-- [useOrientation](https://mantine.dev/llms/hooks-use-orientation.md)
-- [useOs](https://mantine.dev/llms/hooks-use-os.md)
-- [usePageLeave](https://mantine.dev/llms/hooks-use-page-leave.md)
-- [usePagination](https://mantine.dev/llms/hooks-use-pagination.md)
-- [usePrevious](https://mantine.dev/llms/hooks-use-previous.md)
-- [useQueue](https://mantine.dev/llms/hooks-use-queue.md)
-- [useRadialMove](https://mantine.dev/llms/hooks-use-radial-move.md)
-- [useReducedMotion](https://mantine.dev/llms/hooks-use-reduced-motion.md)
-- [useResizeObserver](https://mantine.dev/llms/hooks-use-resize-observer.md)
-- [useRovingIndex](https://mantine.dev/llms/hooks-use-roving-index.md)
-- [useScrollDirection](https://mantine.dev/llms/hooks-use-scroll-direction.md)
-- [useScroller](https://mantine.dev/llms/hooks-use-scroller.md)
-- [useScrollIntoView](https://mantine.dev/llms/hooks-use-scroll-into-view.md)
-- [useScrollSpy](https://mantine.dev/llms/hooks-use-scroll-spy.md)
-- [useSelection](https://mantine.dev/llms/hooks-use-selection.md)
-- [useSet](https://mantine.dev/llms/hooks-use-set.md)
-- [useSetState](https://mantine.dev/llms/hooks-use-set-state.md)
-- [useShallowEffect](https://mantine.dev/llms/hooks-use-shallow-effect.md)
-- [useSplitter](https://mantine.dev/llms/hooks-use-splitter.md)
-- [useStateHistory](https://mantine.dev/llms/hooks-use-state-history.md)
-- [useTextSelection](https://mantine.dev/llms/hooks-use-text-selection.md)
-- [useThrottledCallback](https://mantine.dev/llms/hooks-use-throttled-callback.md)
-- [useThrottledState](https://mantine.dev/llms/hooks-use-throttled-state.md)
-- [useThrottledValue](https://mantine.dev/llms/hooks-use-throttled-value.md)
-- [useTimeout](https://mantine.dev/llms/hooks-use-timeout.md)
-- [useToggle](https://mantine.dev/llms/hooks-use-toggle.md)
-- [useUncontrolled](https://mantine.dev/llms/hooks-use-uncontrolled.md)
-- [useValidatedState](https://mantine.dev/llms/hooks-use-validated-state.md)
-- [useViewportSize](https://mantine.dev/llms/hooks-use-viewport-size.md)
-- [useWindowEvent](https://mantine.dev/llms/hooks-use-window-event.md)
-- [useWindowScroll](https://mantine.dev/llms/hooks-use-window-scroll.md)
-
-## Form
-
-- [Form context](https://mantine.dev/llms/form-create-form-context.md): Add context support to use-form with createFormContext
-- [formActions](https://mantine.dev/llms/form-actions.md)
-- [formAllInputs](https://mantine.dev/llms/form-all-inputs.md)
-- [formErrors](https://mantine.dev/llms/form-errors.md)
-- [formGetInputProps](https://mantine.dev/llms/form-get-input-props.md)
-- [formNested](https://mantine.dev/llms/form-nested.md)
-- [FormPackage](https://mantine.dev/llms/form-package.md)
-- [formRecipes](https://mantine.dev/llms/form-recipes.md)
-- [formSchemaValidation](https://mantine.dev/llms/form-schema-validation.md)
-- [formStatus](https://mantine.dev/llms/form-status.md)
-- [formUncontrolled](https://mantine.dev/llms/form-uncontrolled.md)
-- [formValidation](https://mantine.dev/llms/form-validation.md)
-- [formValidators](https://mantine.dev/llms/form-validators.md)
-- [formValues](https://mantine.dev/llms/form-values.md)
-- [use-field](https://mantine.dev/llms/form-use-field.md): use-field hook – manage single field state
-- [use-form](https://mantine.dev/llms/form-use-form.md): Manage form state
-
-## Dates
-
-- [Calendar](https://mantine.dev/llms/dates-calendar.md): Base component for custom date pickers
-- [DateInput](https://mantine.dev/llms/dates-date-input.md): Free form date input
-- [DatePicker](https://mantine.dev/llms/dates-date-picker.md): Inline date, multiple dates and dates range picker
-- [DatePickerInput](https://mantine.dev/llms/dates-date-picker-input.md): Date, multiple dates and dates range picker input
-- [DateTimePicker](https://mantine.dev/llms/dates-date-time-picker.md): Capture datetime from the user
-- [GettingStartedDates](https://mantine.dev/llms/dates-getting-started.md)
-- [InlineDateTimePicker](https://mantine.dev/llms/dates-inline-date-time-picker.md): Inline date and time picker with range support
-- [MiniCalendar](https://mantine.dev/llms/dates-mini-calendar.md): Compact calendar to display a small number of days in a row
-- [MonthPicker](https://mantine.dev/llms/dates-month-picker.md): Inline month, multiple months and months range picker
-- [MonthPickerInput](https://mantine.dev/llms/dates-month-picker-input.md): Month, multiple months and months range picker input
-- [TimeGrid](https://mantine.dev/llms/dates-time-grid.md): Captures time value from the user with a predefined set of options
-- [TimeInput](https://mantine.dev/llms/dates-time-input.md): Capture time from the user
-- [TimePicker](https://mantine.dev/llms/dates-time-picker.md): Captures time value from the user
-- [TimeValue](https://mantine.dev/llms/dates-time-value.md): Display a formatted time value
-- [YearPicker](https://mantine.dev/llms/dates-year-picker.md): Inline year, multiple years and years range picker
-- [YearPickerInput](https://mantine.dev/llms/dates-year-picker-input.md): Inline year, multiple years and years range picker
-
-## Charts
-
-- [AreaChart](https://mantine.dev/llms/charts-area-chart.md): Area chart component with stacked, percent and split variants
-- [BarChart](https://mantine.dev/llms/charts-bar-chart.md): Bar chart component with stacked and percent variants
-- [BarsList](https://mantine.dev/llms/charts-bars-list.md): Display a list of bars with names and values
-- [BubbleChart](https://mantine.dev/llms/charts-bubble-chart.md): Bubble chart component
-- [BulletChart](https://mantine.dev/llms/charts-bullet-chart.md): Compact KPI chart with value, target, and qualitative ranges
-- [CompositeChart](https://mantine.dev/llms/charts-composite-chart.md): Composed chart with support for Area, Bar and Line charts
-- [DonutChart](https://mantine.dev/llms/charts-donut-chart.md): Donut chart component
-- [FunnelChart](https://mantine.dev/llms/charts-funnel-chart.md): Funnel chart component
-- [GettingStartedCharts](https://mantine.dev/llms/charts-getting-started.md)
-- [Heatmap](https://mantine.dev/llms/charts-heatmap.md): Heatmap chart component
-- [LineChart](https://mantine.dev/llms/charts-line-chart.md): Line chart component
-- [PieChart](https://mantine.dev/llms/charts-pie-chart.md): Pie chart component
-- [RadarChart](https://mantine.dev/llms/charts-radar-chart.md): Radar chart component
-- [RadialBarChart](https://mantine.dev/llms/charts-radial-bar-chart.md): Radial bar chart component
-- [SankeyChart](https://mantine.dev/llms/charts-sankey-chart.md): Sankey diagram component
-- [ScatterChart](https://mantine.dev/llms/charts-scatter-chart.md): Scatter chart component
-- [Sparkline](https://mantine.dev/llms/charts-sparkline.md): Simplified area chart to show trends
-- [SunburstChart](https://mantine.dev/llms/charts-sunburst-chart.md): Sunburst chart component for hierarchical data
-- [Treemap](https://mantine.dev/llms/charts-treemap.md): Treemap chart component
-
-## Schedule
-
-- [AgendaView](https://mantine.dev/llms/schedule-agenda-view.md): Vertical list view of events grouped by date
-- [DayView](https://mantine.dev/llms/schedule-day-view.md): Standalone schedule day view component
-- [GettingStartedSchedule](https://mantine.dev/llms/schedule-getting-started.md)
-- [MobileMonthView](https://mantine.dev/llms/schedule-mobile-month-view.md): Mobile-optimized schedule month view component
-- [MonthView](https://mantine.dev/llms/schedule-month-view.md): Standalone schedule month view component
-- [RecurringEventsSchedule](https://mantine.dev/llms/schedule-recurring-events.md)
-- [ResourcesDayView](https://mantine.dev/llms/schedule-resources-day-view.md): Day view with resource columns for scheduling across resources
-- [ResourcesMonthView](https://mantine.dev/llms/schedule-resources-month-view.md): Month view with resource lanes for scheduling across resources
-- [ResourcesSchedule](https://mantine.dev/llms/schedule-resources-schedule.md): Schedule wrapper component that combines resource day, week and month views
-- [ResourcesWeekView](https://mantine.dev/llms/schedule-resources-week-view.md): Week view with resource rows for scheduling across resources
-- [Schedule](https://mantine.dev/llms/schedule-schedule.md): Schedule component with day, week, month and year views
-- [ScheduleEventsData](https://mantine.dev/llms/schedule-events-data.md)
-- [WeekView](https://mantine.dev/llms/schedule-week-view.md): Standalone schedule week view component
-- [YearView](https://mantine.dev/llms/schedule-year-view.md): Standalone schedule year view component
-
-## Guides
-
-- [ControlledVsUncontrolled](https://mantine.dev/llms/guides-controlled-vs-uncontrolled.md)
-- [CustomComponents](https://mantine.dev/llms/guides-custom-components.md)
-- [EightToNine](https://mantine.dev/llms/guides-8x-to-9x.md)
-- [FunctionsReference](https://mantine.dev/llms/guides-functions-reference.md)
-- [Gatsby](https://mantine.dev/llms/guides-gatsby.md)
-- [Icons](https://mantine.dev/llms/guides-icons.md)
-- [JavaScript](https://mantine.dev/llms/guides-javascript.md)
-- [Jest](https://mantine.dev/llms/guides-jest.md)
-- [LLMDocumentation](https://mantine.dev/llms/guides-llms.md)
-- [NextJs](https://mantine.dev/llms/guides-next.md)
-- [Polymorphic](https://mantine.dev/llms/guides-polymorphic.md)
-- [ReactRouter](https://mantine.dev/llms/guides-react-router.md)
-- [Redwood](https://mantine.dev/llms/guides-redwood.md)
-- [SevenToEight](https://mantine.dev/llms/guides-7x-to-8x.md)
-- [SixToSeven](https://mantine.dev/llms/guides-6x-to-7x.md)
-- [Storybook](https://mantine.dev/llms/guides-storybook.md)
-- [Tiptap3Migration](https://mantine.dev/llms/guides-tiptap-3-migration.md)
-- [TypeScript](https://mantine.dev/llms/guides-typescript.md)
-- [Vite](https://mantine.dev/llms/guides-vite.md)
-- [Vitest](https://mantine.dev/llms/guides-vitest.md)
-
-## Theming
-
-- [Colors](https://mantine.dev/llms/theming-colors.md)
-- [ColorSchemes](https://mantine.dev/llms/theming-color-schemes.md)
-- [DefaultProps](https://mantine.dev/llms/theming-default-props.md)
-- [MantineProvider](https://mantine.dev/llms/theming-mantine-provider.md)
-- [ThemeObject](https://mantine.dev/llms/theming-theme-object.md)
-- [Typography](https://mantine.dev/llms/theming-typography.md): Styles provider for html content
-
-## Styles
-
-- [ColorFunctions](https://mantine.dev/llms/styles-color-functions.md)
-- [CSSFilesList](https://mantine.dev/llms/styles-css-files-list.md)
-- [CSSModules](https://mantine.dev/llms/styles-css-modules.md)
-- [CssVariables](https://mantine.dev/llms/styles-css-variables.md)
-- [CSSVariablesList](https://mantine.dev/llms/styles-css-variables-list.md)
-- [DataAttributes](https://mantine.dev/llms/styles-data-attributes.md)
-- [Emotion](https://mantine.dev/llms/styles-emotion.md)
-- [GlobalStyles](https://mantine.dev/llms/styles-global-styles.md)
-- [MantineStyles](https://mantine.dev/llms/styles-mantine-styles.md)
-- [PostCSSPreset](https://mantine.dev/llms/styles-postcss-preset.md)
-- [Rem](https://mantine.dev/llms/styles-rem.md)
-- [ResponsiveStyles](https://mantine.dev/llms/styles-responsive.md)
-- [Rtl](https://mantine.dev/llms/styles-rtl.md)
-- [StyleProp](https://mantine.dev/llms/styles-style.md)
-- [StyleProps](https://mantine.dev/llms/styles-style-props.md)
-- [StylesApi](https://mantine.dev/llms/styles-styles-api.md)
-- [StylesOverview](https://mantine.dev/llms/styles-styles-overview.md)
-- [StylesPerformance](https://mantine.dev/llms/styles-styles-performance.md)
-- [UnstyledComponents](https://mantine.dev/llms/styles-unstyled.md)
-- [UsageWithSass](https://mantine.dev/llms/styles-sass.md)
-- [VanillaExtract](https://mantine.dev/llms/styles-vanilla-extract.md)
-- [VariantsAndSizes](https://mantine.dev/llms/styles-variants-sizes.md)
-
-## X
-
-- [Carousel](https://mantine.dev/llms/x-carousel.md): Embla based carousel component
-- [CodeHighlight](https://mantine.dev/llms/x-code-highlight.md): Highlight code with shiki or highlight.js
-- [Dropzone](https://mantine.dev/llms/x-dropzone.md): Capture files from user with drag and drop
-- [ExtensionsPackage](https://mantine.dev/llms/x-extensions.md)
-- [Modals manager](https://mantine.dev/llms/x-modals.md): Centralized modals manager with option to handle state of multi-step modals
-- [NavigationProgress](https://mantine.dev/llms/x-nprogress.md): Navigation progress bar
-- [Notifications system](https://mantine.dev/llms/x-notifications.md): Mantine notifications system
-- [Rich text editor](https://mantine.dev/llms/x-tiptap.md): Tiptap based rich text editor
-- [Spotlight](https://mantine.dev/llms/x-spotlight.md): Command center for your application
-
-## Other
-
-- [About](https://mantine.dev/llms/about.md)
-- [AllReleases](https://mantine.dev/llms/changelog-all-releases.md)
-- [BrowserSupport](https://mantine.dev/llms/browser-support.md)
-- [Changelog700](https://mantine.dev/llms/changelog-7-0-0.md)
-- [Changelog710](https://mantine.dev/llms/changelog-7-1-0.md)
-- [Changelog7100](https://mantine.dev/llms/changelog-7-10-0.md)
-- [Changelog7110](https://mantine.dev/llms/changelog-7-11-0.md)
-- [Changelog7120](https://mantine.dev/llms/changelog-7-12-0.md)
-- [Changelog7130](https://mantine.dev/llms/changelog-7-13-0.md)
-- [Changelog7140](https://mantine.dev/llms/changelog-7-14-0.md)
-- [Changelog7150](https://mantine.dev/llms/changelog-7-15-0.md)
-- [Changelog7160](https://mantine.dev/llms/changelog-7-16-0.md)
-- [Changelog7170](https://mantine.dev/llms/changelog-7-17-0.md)
-- [Changelog720](https://mantine.dev/llms/changelog-7-2-0.md)
-- [Changelog730](https://mantine.dev/llms/changelog-7-3-0.md)
-- [Changelog740](https://mantine.dev/llms/changelog-7-4-0.md)
-- [Changelog750](https://mantine.dev/llms/changelog-7-5-0.md)
-- [Changelog760](https://mantine.dev/llms/changelog-7-6-0.md)
-- [Changelog770](https://mantine.dev/llms/changelog-7-7-0.md)
-- [Changelog780](https://mantine.dev/llms/changelog-7-8-0.md)
-- [Changelog790](https://mantine.dev/llms/changelog-7-9-0.md)
-- [Changelog800](https://mantine.dev/llms/changelog-8-0-0.md)
-- [Changelog810](https://mantine.dev/llms/changelog-8-1-0.md)
-- [Changelog820](https://mantine.dev/llms/changelog-8-2-0.md)
-- [Changelog830](https://mantine.dev/llms/changelog-8-3-0.md)
-- [Changelog900](https://mantine.dev/llms/changelog-9-0-0.md)
-- [Changelog910](https://mantine.dev/llms/changelog-9-1-0.md)
-- [Changelog920](https://mantine.dev/llms/changelog-9-2-0.md)
-- [Changelog930](https://mantine.dev/llms/changelog-9-3-0.md)
-- [Changelog940](https://mantine.dev/llms/changelog-9-4-0.md)
-- [Changelog950](https://mantine.dev/llms/changelog-9-5-0.md)
-- [Contribute](https://mantine.dev/llms/contribute.md)
-- [GettingStarted](https://mantine.dev/llms/getting-started.md)
-- [NotFound](https://mantine.dev/llms/404.md)
-- [OxcConfig](https://mantine.dev/llms/oxc-config-mantine.md)
-- [PreviousChangelogs](https://mantine.dev/llms/changelog-previous-versions.md)
-- [Support](https://mantine.dev/llms/support.md)

PHASE2-FINDINGS.md

@@ -0,0 +1,28 @@
+# Performance findings
+
+This file grew past 1,200 lines covering server memory, client rendering, methodology and a long
+list of rejected ideas at once. It has been split by subject under [`docs/perf/`](./docs/perf/):
+
+| document | subject |
+| --- | --- |
+| [docs/perf/README.md](./docs/perf/README.md) | Headline results and the change-by-change ratio table |
+| [docs/perf/SERVER-MEMORY.md](./docs/perf/SERVER-MEMORY.md) | What the container's RAM is made of, layer by layer, and what reduced it |
+| [docs/perf/CLIENT-PERFORMANCE.md](./docs/perf/CLIENT-PERFORMANCE.md) | Dashboard cost in Chrome: DOM, fibers, images, paint |
+| [docs/perf/REJECTED.md](./docs/perf/REJECTED.md) | Ideas implemented, measured, and abandoned — with their numbers |
+| [docs/perf/METHODOLOGY.md](./docs/perf/METHODOLOGY.md) | The tools, and the measurement traps that produced wrong answers |
+
+## Result in one table
+
+Server RAM, merge-base `06724cfeb` vs this branch, two alternated runs per side, cgroup **anonymous**
+memory — the figure that counts against a container limit:
+
+| stage | before | after | change |
+| --- | --- | --- | --- |
+| **peak** | 376.6 MiB | **279.3 MiB** | **−26%** |
+| boot idle | 130.5 MiB | **62.4 MiB** | **−52%** |
+| after sign-in | 247.4 MiB | **142.9 MiB** | **−42%** |
+| dashboard loaded | 293.4 MiB | **170.4 MiB** | **−42%** |
+| 4 tabs, 2 boards | 366.5 MiB | **258.2 MiB** | **−30%** |
+| after 2 min idle soak | 323.7 MiB | **200.8 MiB** | **−38%** |
+
+No before/after range overlaps at any stage. Cost: **+18% CPU**, solid and non-overlapping.

apps/docs/.vscode/settings.json

@@ -1,3 +1,10 @@
 {
-  "cSpell.words": ["Homarr", "Lidarr", "Nextcloud", "Radarr", "Readarr", "Sonarr"]
-}
+    "cSpell.words": [
+        "Homarr",
+        "Lidarr",
+        "Nextcloud",
+        "Radarr",
+        "Readarr",
+        "Sonarr"
+    ]
+}

apps/docs/README.md

@@ -21,14 +21,8 @@ pnpm dev:docs
 
 # Or from within this directory
 pnpm dev
-
-# Point the docs at a local PocketBase instance
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
 ```
 
-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
@@ -46,7 +40,7 @@ Uses oxlint and oxfmt (same as the rest of the monorepo):
 ```bash
 pnpm lint        # oxlint
 pnpm format      # oxfmt (check)
-pnpm format:fix    # oxfmt (fix)
+pnpm format -- --write  # oxfmt (fix)
 ```
 
 ## Typecheck
@@ -77,7 +71,7 @@ Each integration/widget doc follows a consistent pattern:
 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";
+import { IntegrationKind } from '@homarr/definitions';
 ```
 
 This enables type-safe references to homarr domain concepts within documentation code.
@@ -96,15 +90,15 @@ pnpm verify:search
 
 ## Tech Stack
 
-| Layer          | Technology                                  |
-| -------------- | ------------------------------------------- |
+| 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                                  |
+| Styling | Tailwind CSS 3 + Docusaurus Infima |
+| Icons | `@tabler/icons-react` |
+| Diagrams | Mermaid (`@docusaurus/theme-mermaid`) |
+| Search | Algolia DocSearch |
+| Analytics | PostHog |
+| Charts | @nivo/line |
 
 ## Contributing
 

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

@@ -13,6 +13,8 @@ This will be a one time occurrence and version > ``1.0`` will have less breaking
 This time more important than every; **read the breaking changes** list and **create a backup** before updating.
 Some third party installation methods may take multiple days or weeks to update to the new version.
 
+See [this guide on how to import your previous Homarr dashboard](/docs/getting-started/after-the-installation#importing-a-zip-from-version-before-100)
+
 ## Changes at a glance
 - **Asynchronous integrations system**: In versions prior to ``1.0``, we fetched data upon each request synchronously.
 This means that the user had to wait for the requests to finish so any data would appear.

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

@@ -10,11 +10,12 @@ If you are still on a version before 0.15.10, please update to 0.15.10 where we
 
 <!-- truncate -->
 
-## Preserve your old installation
+## Export your data
 
-Homarr 1.0 is a complete rewrite and cannot reuse the old Docker mounts. Keep the 0.15 installation and its data intact while you build the replacement. The historical `Management` > `Tools` > `Migrate to 1.0` export can still be kept as a record, but current Homarr releases cannot import that ZIP or its secret key.
-
-Plan to recreate your apps, integrations, and boards manually in the new installation. A SQLite database backup can be restored from the onboarding welcome screen only when it was created by a compatible current Homarr release; it is not a conversion path for a 0.15 database.
+As 1.0 is a complete rewrite of Homarr and therefor not compatible with the old docker mounts, we need to export your data first.
+For this you can navigate to the `Migrate to 1.0` page which you can find under `Management` > `Tools` > `Migrate to 1.0`.
+Here you can select which things you want to export and download the zip file.
+It will also show you a secret key which you will need to import the secret data like user password hashes, salts and integration secrets.
 
 ![Export page](./img/old-homarr-export-data.png)
 
@@ -27,15 +28,28 @@ Please note that if you are using docker you need to specify a diffrent external
 So in your compose file the ports would be `7576:7575` instead of `7575:7575`.
 
 ## Import your data
+Once the installation is completed you can access the new installation. During the onboarding you'll need to select `Import from Homarr before 1.0`.
 
-:::warning Legacy guide
+![Onboarding initial step](./img/onboarding-step-1.png)
 
-The pre-1.0 ZIP importer is no longer included in current Homarr releases. Keep the old installation available until you have manually verified the replacement. Compatible SQLite backups from current releases can still be restored from the onboarding welcome screen.
+After that you can upload the zip file you downloaded in the first step.
 
-:::
+![Onboarding import dropzone](./img/old-homarr-import-dropzone.png)
+
+After that you'll get a list with all your boards that can be imported. You can configure how it should be imported and can select which screensizes it should import.
+
+![Onboarding import list](./img/old-homarr-import-choose-imported-data.png)
+
+Once you have selected everything you can click on `Confirm import and continue` which will open the encryption key input dialog where you can input the secret key you got during the export.
+
+![Onboarding import key input](./img/old-homarr-import-decryption-token.png)
+
+After that you can continue the onboarding and you should see all your boards and data in the new installation.
+
+See [After the installation](https://homarr.dev/docs/getting-started/after-the-installation) for more information.
 
 ## Remove the old installation
 
 After you are happy with the new installation and everything is working as expected you can remove the old installation.
 Please make sure to backup the data before you remove the old installation.
-Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.
+Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.

apps/docs/components.json

@@ -1,24 +0,0 @@
-{
-  "$schema": "https://ui.shadcn.com/schema.json",
-  "style": "base-nova",
-  "rsc": false,
-  "tsx": true,
-  "tailwind": {
-    "config": "",
-    "css": "src/css/custom.css",
-    "baseColor": "mist",
-    "cssVariables": true,
-    "prefix": ""
-  },
-  "aliases": {
-    "components": "@/components",
-    "utils": "@/lib/utils",
-    "ui": "@/components/ui",
-    "lib": "@/lib",
-    "hooks": "@/hooks"
-  },
-  "iconLibrary": "tabler",
-  "rtl": false,
-  "menuColor": "default",
-  "menuAccent": "subtle"
-}

apps/docs/docs/advanced/_category_.json

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

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

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

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

@@ -1,175 +1,41 @@
 # Developer Docker CLI
 
-The host-side developer CLI builds and runs local Homarr images and pull-request previews with non-blocking background operations. Run it directly from a checkout with `pnpm dev:cli -- ...`; no shell-specific setup script is required. It is separate from the recovery CLI included in production images.
+The host-side developer CLI builds and runs local Homarr images and pull-request previews. Run it directly from a checkout with `pnpm dev:cli -- ...`; no shell-specific setup script is required. It is separate from the recovery CLI included in production images.
 
-To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your Go bin directory available on `PATH`. GitHub CLI authentication (`gh auth login`) is only needed for pull-request features.
+To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your Go bin directory available on `PATH`. GitHub CLI authentication is only needed for pull-request features.
 
-## Requirements
-
-- Docker or OrbStack
-- Go 1.25+ (when building the CLI from source)
-- GitHub CLI authenticated with `gh auth login` (for pull-request and CI features)
-- A [Nerd Font](https://www.nerdfonts.com/) enabled in your terminal (recommended for icons, status indicators, and TUI glyphs)
-
-## Interactive Development Browser
+## Browse development images
 
 ```bash
 pnpm dev:cli --
-# or with global binary:
-homarr
 ```
 
-The main browser combines local `homarr:*` images with open pull requests and their GHCR preview status. Select an image to start or stop it, use `R` to build a remote pull request locally in the background or rebuild a local image, or use `p` to force a remote preview pull. Press `d` (or `1`/`2`) to toggle between the image browser and the instance dashboard.
+The main screen combines local `homarr:*` images with open pull requests and their GHCR preview status. Select an image to start or stop it, use `R` to build a remote pull request locally in the background or rebuild a local image, or use `p` to force a remote preview pull. Press `d` to switch to the instance dashboard and `d` again to return without losing the browser state. The explicit `dev` and `dash` subcommands start on either screen.
 
-A locally built PR image is folded into its remote PR row only when its recorded revision matches the current GitHub head SHA (marked `◆ local`). When the matching GHCR image is also available, pressing `Enter` opens a local/remote selector with local preselected. Outdated local builds remain separate rows.
+A locally built PR image is folded into its remote PR row only when its recorded revision exactly matches the current GitHub head SHA. The row is marked `◆ local`, and starting it prefers that local image without a registry pull. Outdated local builds remain separate rows. Navigation and dashboard switching remain available during background builds.
 
-### Multi-Source Sidebar
-
-Press `Tab` to cycle between sidebar tabs:
-
-- **`[logs]`**: Live container output streams (press `f` to follow/pause, `L` to pin to the selected container, `Page Up`/`Page Down` to scroll).
-- **`[build]`**: Real-time BuildKit step streaming for active local builds.
-- **`[ci]`**: GitHub Actions CI check statuses, run duration, and workflow links for pull requests.
-
-### Background Task Overlay
-
-Pulls and builds run asynchronously in the background. Press `t` to open the tasks overlay, showing:
-
-- Layer-by-layer download progress and transfer speeds (via Docker Engine API).
-- Active build stages and logs.
-- Task cancellation and status.
-
-### Browser Shortcuts
-
-| Key                    | Action                                                                                        |
-| ---------------------- | --------------------------------------------------------------------------------------------- |
-| `/`                    | Filter rows by PR number, title, author, branch, CI, image, state, or port                    |
-| `↑` / `↓` or `j` / `k` | Navigate rows                                                                                 |
-| `Enter` or `Space`     | Start the available image; choose local or remote when both exist; stop if running            |
-| `R`                    | Build locally in background (or rebuild local image)                                          |
-| `p`                    | Pull remote PR image in background and start container                                        |
-| `m`                    | Manage mode (`b` rebuild, `i` delete image, `d` delete data, `c` remove container, `p` prune) |
-| `t`                    | Toggle background tasks overlay                                                               |
-| `Tab`                  | Cycle sidebar tabs (`[logs]`, `[build]`, `[ci]`)                                              |
-| `l` / `L`              | Toggle sidebar visibility / Pin logs to selected instance                                     |
-| `f`                    | Follow or pause logs                                                                          |
-| `M`                    | Toggle demo mode for next launch                                                              |
-| `b`                    | Toggle bot pull requests                                                                      |
-| `o` / `a`              | Open PR on GitHub / Open running instance in browser                                          |
-| `c`                    | Copy instance URL to clipboard                                                                |
-| `r`                    | Refresh data                                                                                  |
-| `1` / `2` / `d`        | Switch screen (development browser / instance dashboard)                                      |
-| `?` / `q`              | Help overlay / Quit (cancels active background tasks)                                         |
-
-## Instance Dashboard
+## Build images
 
 ```bash
-homarr dash
-# or
-pnpm dev:cli -- dash
+pnpm dev:cli -- build <name>
+pnpm dev:cli -- build --pr <number> [name]
 ```
 
-The instance dashboard displays all running and stopped Homarr containers, published ports, health states, and resource volumes.
+The first command builds the current checkout as `homarr:<name>`. The pull-request form uses a depth-one clone in a temporary directory and defaults to `homarr:pr-<number>` when `name` is omitted.
 
-| Key                | Action                                   |
-| ------------------ | ---------------------------------------- |
-| `Enter` or `Space` | Start or stop selected instance          |
-| `s` / `S`          | Stop / Restart instance                  |
-| `x`                | Remove container (preserves data volume) |
-| `m`                | Manage mode for selected instance        |
-| `R`                | Rebuild from recorded build provenance   |
-
-## CLI Commands
-
-The commands below use the installed `homarr` binary. Without global installation, prefix each command with `pnpm dev:cli --` (for example, `pnpm dev:cli -- list`).
-
-### Launch Instances
+## Rebuild images
 
 ```bash
-homarr run dev
-homarr run --detach dev
-homarr run --pr 6441
-homarr run --pr 6441 --demo
-homarr --pr 6441 --env WORKSHOP_WEB_URL=https://app-v2.preview.homarr.dev/
+pnpm dev:cli -- rebuild <name>
 ```
 
-- `--pr <number>`: Pull and run a PR image from GHCR (shorthand: `homarr --pr <number>`).
-- `--demo` (`-m`): Start with mock integrations and sample data.
-- `--detach`: Start container in background.
-- `--env` (`-e`): Pass additional environment variables (repeatable: `--env KEY=VALUE`).
+Images built by this CLI record their source checkout, revision, and optional pull-request number. Rebuild uses that provenance to select the original checkout or create a fresh temporary pull-request checkout.
 
-### Build & Rebuild
+## Run images
 
 ```bash
-# Build current checkout as homarr:<name>
-homarr build feature
-
-# Build a pull request locally in a temporary checkout
-homarr build --pr 6441
-
-# Rebuild an existing image from recorded provenance
-homarr rebuild feature
+homarr run <name>
+homarr run --pr <number>
 ```
 
-Images built with the CLI record their source checkout, revision SHA, and optional PR number. `homarr rebuild` reads this provenance to reconstruct the build without manual configuration.
-
-### GitHub CI Checks
-
-```bash
-# View CI checks for a specific PR
-homarr ci 6441
-
-# View CI checks for the current branch
-homarr ci
-
-# Watch CI checks until completion
-homarr ci 6441 --watch
-```
-
-### Interactive Shell
-
-```bash
-# Open interactive shell in running container
-homarr shell homarr-dev
-
-# Run specific command in container
-homarr shell homarr-dev pnpm db:migration:sqlite:run
-```
-
-### Image & Volume Management
-
-```bash
-# List local images with build provenance (source, revision, PR)
-homarr images
-
-# Delete local image
-homarr images rm feature
-
-# List data volumes with owner PR/tag and in-use status
-homarr data
-
-# Delete data volume (safely stops and removes owning container first)
-homarr data rm homarr_feature_data
-
-# Remove stopped containers (prompts without --force)
-homarr prune --force
-```
-
-### Instance Operations & Diagnostics
-
-```bash
-# List instances in a script-friendly table
-homarr list
-
-# Follow container logs
-homarr logs homarr-dev
-
-# Stop, restart, remove, or open container in browser
-homarr stop homarr-dev
-homarr restart homarr-dev
-homarr remove homarr-dev
-homarr open homarr-dev
-
-# Verify Docker daemon, Engine API, GHCR access, and gh CLI authentication
-homarr doctor
-```
+Add `--detach` to run in the background, `--demo` to enable demo data, or repeat `--env KEY=VALUE` to provide additional environment variables.

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

@@ -14,4 +14,4 @@ homarr fix-usernames
 
 This will convert all credential usernames to lowercase and update the database accordingly.
 
-![](./img/screenshot-cli.png)
+![](./img/screenshot-cli.png)

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

@@ -1,7 +1,7 @@
 # Command line interface
 
 The Homarr image ships with a built-in recovery tool. This can be useful, if you do not have access to Homarr or if something is not working.
-Please note that the CLI is an _emergency tool_, not an API tool.
+Please note that the CLI is an *emergency tool*, not an API tool.
 
 :::caution
 
@@ -12,10 +12,10 @@ You should also create a backup of the database, in case you break something.
 
 ## Execute CLI with Docker
 
-1. Execute `docker ps | grep homarr` on the root system with Docker to find the container ID of your Homarr container.
-2. Run `docker exec -it <container-id> /bin/bash homarr <your-command-goes-here>`. \
-   Replace `<container-id>` with your container ID from step 1. \
-   Replace `<your-command-goes-here>` with the command you want to execute (see sub-pages).
+1. Execute ``docker ps | grep homarr`` on the root system with Docker to find the container ID of your Homarr container.
+2. Run ``docker exec -it <container-id> homarr <your-command-goes-here>``. \
+Replace ``<container-id>`` with your container ID from step 1. \
+Replace ``<your-command-goes-here>`` with the command you want to execute (see sub-pages).
 
 ## Execute CLI with QNAP
 
@@ -25,29 +25,3 @@ You should also create a backup of the database, in case you break something.
 4. Click "Execute" in the top right of the Window. ![](img/334116411-df1482f9-3aa9-4686-b77f-e0dca09e60b2.png)
 5. Select /bin/bash and click Execute ![](img/334116518-e1ddb515-99c7-4159-81bf-76e889d1e808.png)
 6. Run the Homarr command and press enter (eg. homarr reset-owner-password) ![](img/334116642-08c4f204-5cd0-4e4e-a785-0142e1b279ca.png)
-
-## Build a local branch harness
-
-The host-side operations CLI can build the current checkout and run it as a named, browser-ready Docker harness. This is separate from the recovery CLI described above and does not open the interactive developer TUI.
-
-```sh
-pnpm cli harness setup feature-board
-```
-
-The command builds `homarr:feature-board`, starts a container with a persistent data volume, enables demo mode, and keeps demo mutations writable (`DEMO_READ_ONLY=false`). Docker assigns a free host port by default; use the URL printed by the command or query it later:
-
-The demo board includes every widget kind. Integration-backed widgets use the bundled mock integration; media widgets use public stock assets.
-
-```sh
-pnpm cli harness port feature-board
-```
-
-Pass environment overrides by repeating `--env`:
-
-```sh
-pnpm cli harness setup feature-board \
-  --env WORKSHOP_WEB_URL=https://example.test \
-  --env FEATURE_FLAG=true
-```
-
-Other commands are `harness build <name>`, `harness run <name>`, and `harness stop <name>`. Use the returned URL with a browser automation harness for feature validation; do not assume the host port is `7575`.

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

@@ -7,7 +7,6 @@ This guide requires that you understand [how to access the CLI](../).
 :::
 
 Using these commands, you can manage the integrations from the CLI:
-
 ```bash
 Group of commands to manage integrations
 
@@ -44,7 +43,7 @@ Flags:
 ## Delete Integration
 
 - Requires a database connection
-- Requires one parameter: `id` or `name`
+- Requires one parameter: ``id`` or ``name``
 - Deletes an integration permanently from the database
 
 ```bash
@@ -58,4 +57,4 @@ Flags:
   -n, --name string   Name of the integration
   -h, --help          help for integrations delete
   -v, --version       version for homarr-cli
-```
+```

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

@@ -12,8 +12,8 @@ All sessions for that user will be terminated and the user must re-login.
 
 ![](./img/screenshot-cli.png)
 
-Using the `--username` parameter, you can specify who you want to reset the password for.
+Using the ``--username`` parameter, you can specify who you want to reset the password for.
 Executing the command will create a new random password, update the database and display the new password.
 All sessions for this user will be terminated and they must re-login.
 
-![](./img/screenshot-cli-result.png)
+![](./img/screenshot-cli-result.png)

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

@@ -7,7 +7,6 @@ This guide requires that you understand [how to access the CLI](../).
 :::
 
 Using these commands, you can manage the users from the CLI:
-
 ```bash
 Group of commands to manage users
 
@@ -43,7 +42,7 @@ yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
 ## Delete User
 
 - Requires a database connection
-- Requires one parameter: `id` or `username`
+- Requires one parameter: ``id`` or ``username``
 
 ```bash
 Delete a user by id or username
@@ -77,4 +76,4 @@ Flags:
   -p, --password          New password
   -h, --help              help for users update-password
   -v, --version           version for homarr-cli
-```
+```

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

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

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

@@ -8,77 +8,74 @@ tags:
 sidebar_position: 1
 ---
 
-## Set up your development environment
+## Setting up your development environment
+
+This guide will help you set up your development environment to start contributing to homarr.
 
 ### Prerequisites
 
 - **Node.js 24.18 or newer**: You can download it from the [official website](https://nodejs.org/).
-- **Corepack**: Run `corepack enable` so the repository selects its pinned pnpm 11 version.
+- **Corepack**: Run `corepack enable` so the repository selects its pinned pnpm version.
 - **Git**: You can download it from the [official website](https://git-scm.com/).
 - **Docker or Docker Desktop**: Required for the Redis service and the developer Docker CLI.
 - **Go 1.25+**: Required only for the developer Docker CLI. You can download it from the [official website](https://go.dev/).
 - **GitHub CLI**: Required only for pull-request image features. Install it from the [official website](https://cli.github.com/), then authenticate with `gh auth login`.
 
-The versions in the root `package.json` are the supported baseline. Let Corepack select the repository version instead
-of installing an unrelated global pnpm:
+### Setting up the project
 
-```sh
-corepack enable
-corepack install
-pnpm install --frozen-lockfile
-```
+1. Fork the repository by clicking on the "Fork" button on the top right corner of the repository page.
 
-### Run the Homarr application
+![Fork button](./img/fork.png)
 
-1. Copy `.env.example` to `.env`.
-2. Set `DB_URL` to an absolute writable SQLite file path.
-3. Keep Redis and the optional local databases running in one terminal.
-4. Apply migrations and start Next.js in another terminal.
+2. Clone the repository to your local machine with `git clone`. You can find the url to use by clicking on the "Code" button on the top right corner of your forks repository page.
 
-```sh
-cp .env.example .env
-```
+![Clone button](./img/clone.png)
 
-Terminal 1:
+3. Change directory to the project folder with `cd homarr`.
 
-```sh
-pnpm docker:dev
-```
+4. Install the dependencies with `pnpm install`.
 
-Terminal 2:
+5. Create `.env` from `.env.example`. In a POSIX shell, run `cp .env.example .env`; in PowerShell, run `Copy-Item .env.example .env`. Set `DB_URL` to an absolute path for your SQLite file.
 
-```sh
-pnpm db:migration:sqlite:run
-pnpm dev
-```
+6. Start Redis in the background with `pnpm docker:dev:up` if your development workflow needs it.
 
-The infrastructure command remains in the foreground. Open `http://127.0.0.1:3000`; the first user created through
-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.
+7. Create or update the database with `pnpm db:migration:sqlite:run`. This also seeds the default data. To run the seed explicitly later, use `pnpm db:seed`.
 
-Workshop contributors can set up PocketBase and Docusaurus with the dedicated
-[Workshop development guide](../../workshop/development).
+8. Start the development server with `pnpm dev` and wait for a message that says `✓ Ready in 10.7s`
 
-### Useful commands
+9. Open your browser and navigate to [http://localhost:3000](http://localhost:3000). (Loading the page might take up to 2 minutes the first time)
 
-- `pnpm dev` — Next.js on port 3000.
-- `pnpm dev:benchmark` — authenticated-board benchmark; readiness-only `--smoke` runs are not performance claims.
-- `pnpm dev:cli -- dev` — browse and run local images and remote pull-request images.
-- `pnpm dev:cli -- build <name>` — build the current checkout as `homarr:<name>`.
-- `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` — 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.
-- `pnpm db:seed` — seed the default database data explicitly.
-- `pnpm db:studio` — inspect the database.
-- `pnpm format` / `pnpm format:fix` — check or apply oxfmt.
-- `pnpm lint` / `pnpm lint:fix` — check or apply oxlint.
-- `pnpm typecheck` — typecheck all workspaces.
-- `pnpm test` — unit and contract suites.
-- `pnpm build` — production monorepo build.
-- `docker build -t homarr .` — build a production Docker image.
-- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>` — run it.
+### Useful npm scripts
+
+#### During development
+
+- `pnpm dev`: Start the Next.js development server.
+- `pnpm dev:benchmark`: Run the local authenticated-board benchmark. Set `DEV_BENCHMARK_BOARD_URL` and
+  `DEV_BENCHMARK_STORAGE_STATE`; readiness-only measurements require the explicit `--smoke` flag and are not
+  suitable for performance claims.
+- `pnpm dev:cli -- dev`: Browse and run local images and remote pull-request images.
+- `pnpm dev:cli -- build <name>`: Build the current checkout as `homarr:<name>`.
+- `pnpm dev:cli -- build --pr <number>`: Build a pull request locally from a temporary checkout.
+- `pnpm dev:cli -- rebuild <name>`: Rebuild a local image from its recorded checkout or pull request.
+- `pnpm dev:cli:install`: Optionally install the developer CLI as a `homarr` binary.
+- `pnpm cli`: Run cli commands.
+- `pnpm db:migration:sqlite:run`: Run the migrations to create or update the sqlite db file.
+- `pnpm db:seed`: Explicitly seed the default database data.
+- `pnpm docker:dev:up`: Start the Redis development service in the background.
+- `pnpm db:migration:sqlite:generate`: Generate a new migration file for the sqlite db. Also works with `mysql`.
+- `pnpm db:studio`: Open a visual studio for the database.
+- `pnpm package:new`: Create a new package in the monorepo.
+
+#### Checking code quality
+
+- `pnpm lint`: Run the linter to check for code quality issues.
+- `pnpm format:fix`: Run the formatter to fix code style issues.
+- `pnpm test`: Run the tests. You can also use `pnpm test:ui` to get a UI for the tests.
+- `pnpm typecheck`: Run the typescript type checker.
+
+#### Building the project
+
+- `pnpm build`: Build the project for production.
+- `pnpm dev:cli -- build <name>`: Build a `homarr:<name>` image and record its checkout for later rebuilds.
+- `docker build -t homarr .`: Build a docker image for the project.
+- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>`: Run the created docker image.

apps/docs/docs/advanced/development/kubernetes.mdx

@@ -132,4 +132,4 @@ This command should return CPU and memory usage statistics for each node.
 
 ## Conclusion
 
-You have successfully set up a multi-node Kubernetes cluster using kind and installed the Metrics Server for monitoring resource usage. This setup is useful for local development and testing Kubernetes workloads before deploying them to a production environment.
+You have successfully set up a multi-node Kubernetes cluster using kind and installed the Metrics Server for monitoring resource usage. This setup is useful for local development and testing Kubernetes workloads before deploying them to a production environment.

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

@@ -25,20 +25,14 @@ This is especially useful for [docker secrets](https://docs.docker.com/engine/sw
 Using the `PUID` and `PGID` will require you to set the correct permissions on the mounted volumes and if used the docker socket. See more in the [Running as a different user](/docs/advanced/running-as-different-user) documentation.
 :::
 
-| Environment Variable     | Description                                                                                                                                                                                                                            | Possible values                     | Default                       |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ----------------------------- |
-| `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`                        |
-| `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`          |
-| `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone documentation.                                                                                                                                                                            | HTTP(S) URL                         | `HOMARR_WEBSITE_URL`          |
-| `WORKSHOP_WEB_URL`       | Public Workshop website used by links in Homarr, Custom Widgets, onboarding, and assistant context.                                                                                                                                    | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
-
-Workshop service operators can find its server-only configuration in the
-[Workshop operator guide](../../workshop/operator#environment-variables).
+| Environment Variable     | Description                                                                                                                                                                                                                            | Possible values                     | Default |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------- |
+| `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`  |
+| `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` |
 
 ## Authentication
 
@@ -58,12 +52,11 @@ A random secret can be generated by using the following command: `openssl rand -
 
 ## Docker
 
-| Environment Variable  | Description                                                                                                                                                                                                          | Possible values                                         | Default |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
-| `DOCKER_SOCKET_PATHS` | Comma-separated mounted Docker-compatible socket paths. Homarr discovers each path as a selectable Docker environment                                                                                                | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
-| `DOCKER_HOSTNAMES`    | Comma-separated plaintext TCP hostnames. Pair each hostname with the port in the same position in `DOCKER_PORTS`                                                                                                     | For example `localhost,docker.example.com`              | -       |
-| `DOCKER_PORTS`        | Comma-separated plaintext TCP ports paired with `DOCKER_HOSTNAMES`                                                                                                                                                   | For example `2375,2376`                                 | -       |
-| `DOCKER_ENDPOINTS`    | Optional advanced JSON configuration for custom names, TLS, or restricted capabilities. It takes precedence over the simple variables above. See the [Docker and Podman connection guide](/docs/integrations/docker) | A JSON array of endpoint descriptors                    | -       |
+| Environment Variable  | Description                                                                                                                              | Possible values                                         | Default |
+| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
+| `DOCKER_HOSTNAMES`    | Comma-separated list of hostnames to connect to                                                                                          | For example `localhost,docker.example.com`              | -       |
+| `DOCKER_PORTS`        | Comma-separated list of ports to connect to                                                                                              | For example `2375,2376`                                 | -       |
+| `DOCKER_SOCKET_PATHS` | Comma-separated list of mounted Docker-compatible socket paths. See the [Docker and Podman integration guide](/docs/integrations/docker) | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
 
 ## Database
 
@@ -113,9 +106,6 @@ External redis is currently not supported with Proxmox Community Scripts
 The advanced deployments environment variables should only be used if you know what you are doing.
 :::
 
-| Environment Variable     | Description                                         |
-| ------------------------ | --------------------------------------------------- |
-| `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 Docusaurus starts.
+| Environment Variable     | Description                                        |
+| ------------------------ | -------------------------------------------------- |
+| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts |

apps/docs/docs/advanced/keyboard-shortcuts/index.mdx

@@ -6,66 +6,11 @@ tags:
 
 Homarr has the following keyboard shortcuts:
 
-| Shortcut                                            | Description                                                                                                                |
-| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| `MOD` + `K`                                         | Opens search, including local apps, boards, integrations, pages, commands, and preferences                                 |
-| `MOD` + `P`                                         | Opens app search                                                                                                           |
-| `MOD` + `/`                                         | Opens Homarr Assistant inside search                                                                                       |
-| `MOD` + `Shift` + `/` (`MOD` + `?`)                 | Opens preference search                                                                                                    |
-| `Shift` + `A`                                       | Opens the full Homarr Assistant                                                                                            |
-| `MOD` + `J`                                         | Toggles Dark Mode                                                                                                          |
-| `MOD` + `E`                                         | Toggles Edit Mode                                                                                                          |
-| Hold `Shift` for 500 ms over a supported widget     | Opens its temporary advanced view                                                                                          |
-| Hold `Shift` + `Ctrl`/`Cmd` over a supported widget | Keeps its advanced view open until it is closed                                                                            |
-| `Esc`                                               | Stops keyboard tile editing, cancels an active pointer or touch move/resize, or closes an open advanced view or board menu |
-
-## Search and commands
-
-Search is designed as the fastest route to Homarr. Start typing after `MOD` + `K` to find local apps, boards,
-integrations, pages, commands, and preferences without entering a separate mode first. Local Homarr results appear
-before configured search-engine actions and Assistant fallbacks. Commands include opening the board switcher without
-leaving the keyboard. Type `!` to enter Web mode when you want to browse configured engine shortcuts or discover
-DuckDuckGo bangs; bang discovery is excluded from ordinary Search results.
-
-Use the dedicated shortcuts above to start in apps, Assistant, or preferences. Inside search, choose a mode to narrow
-the same query when needed. Media request search is available only when a supported Seerr integration is configured.
-
-## Widget advanced view
-
-Supported widgets open a temporary advanced view when you hold `Shift` over them for 500 ms. Hold `Shift` plus `Ctrl`
-on Windows/Linux or `Cmd` on macOS over the widget to keep the advanced view open, or use its menu.
-
-## Board editing
-
-`MOD` + `E` enters edit mode. Homarr keeps the current board visible while the editor prepares; movement and resizing become available when it is ready.
-
-When a tile is focused in edit mode:
-
-| Shortcut             | Description                                                                 |
-| -------------------- | --------------------------------------------------------------------------- |
-| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
-| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
-| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
-| `Esc`                | Stops keyboard editing without undoing its changes                          |
-
-Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
-Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
-
-On touch screens, press and hold a tile before moving it; a quick tap does not start a drag. Resize handles accept direct touch input. During a pointer or touch move or resize, `Esc` cancels the interaction and restores the layout from before it started.
-
-## Board editing
-
-When a tile is focused in edit mode:
-
-| Shortcut             | Description                                                                 |
-| -------------------- | --------------------------------------------------------------------------- |
-| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
-| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
-| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
-| `Esc`                | Stops keyboard editing without undoing its changes                          |
-
-Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
-Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
+| Shortcut | Description |
+| -------- | ----------- |
+| `MOD` + `K` | Opens the search bar |
+| `MOD` + `J` | Toggles Dark Mode |
+| `MOD` + `E` | Toggles Edit Mode |
 
 :::tip
 

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

@@ -9,17 +9,16 @@ tags:
   - Security
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+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?
 
 Homarr is trying to communicate to your apps via the integrations.
-It usually doesn't matter if Homarr is running on `http` or `https`.
+It usually doesn't matter if Homarr is running on ``http`` or ``https``.
 Your apps have a self-signed certificate - Homarr will recognize that the certificate was signed by an unknown authority and requests will be blocked.
 
 :::
@@ -29,9 +28,8 @@ To allow self-signed certificates, you can configure them on the certificates ma
 ## Securing Homarr with Traefik
 
 Copying the configuration straight from the docker-compose file won't work if you are running Homarr behind Traefik, such as a Portainer setup, or docker-swarm. In that case, you should use the following slightly modified configuration:
-
 ```yaml
-version: "3"
+version: '3'
 services:
   homarr:
     container_name: homarr
@@ -55,12 +53,11 @@ networks:
     external: true
 ```
 
-<br />
+<br/>
 
 A sample Traefik docker-compose.yml using Cloudflare for certificate generation that works with the configuration above would be:
-
 ```yaml
-version: "3"
+version: '3'
 
 apps:
   traefik:
@@ -106,6 +103,7 @@ networks:
     external: true
 ```
 
+
 :::tip
 Of particular note here is that both configurations explicitly define which network they are using, in this case "proxy", but it can be named anything. It just has to be the same across all apps for which Traefik is serving as a proxy. These are marked as external because the proxy network was manually created by running: `docker network create proxy` but this might be unnecessary depending on HOW exactly you are running Traefik. For example, if running [Traefik with Portainer](https://docs.portainer.io/advanced/reverse-proxy/traefik#deploying-in-a-docker-standalone-scenario), you can follow their official docs on how to set up Traefik and Portainer together, and you can just focus on the Homarr docker labels instead.
 :::
@@ -116,6 +114,7 @@ If you are using Caddy as the reverse proxy for your setup, your `docker-compose
 
 ```yaml
 services:
+  
   # <-- [Homarr installation]
 
   caddy:
@@ -141,17 +140,14 @@ networks:
   proxy:
     external: true
 ```
-
 :::important
 Homarr needs to be on the same network so you will need to add the following property to your homarr install:
-
 ```yaml
 homarr:
   ...
   networks:
     - proxy
 ```
-
 :::
 
 Next, create a file named `Caddyfile` at the same level as your `docker-compose.yml` file with the following content:

apps/docs/docs/advanced/running-as-different-user/index.mdx

@@ -8,7 +8,7 @@ tags:
   - PUID
 ---
 
-By default the container is running with user `root` and group `root`.
+By default the container is running with user `root` and group `root`. 
 You can change the user and group by using the `PUID` and `PGID` environment variables.
 Important to note is, that you'll also need to change the permissions for the mounted directories accordingly.
 
@@ -32,11 +32,11 @@ services:
     volumes:
       - ./homarr/appdata:/appdata
     environment:
-      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
-      - PUID=1000
-      - PGID=1000
+        - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
+        - PUID=1000
+        - PGID=1000
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
 After that you'll need to create the appdata directory and set the correct permissions:
@@ -76,11 +76,11 @@ services:
       - /var/run/docker.sock:/var/run/docker.sock
       - ./homarr/appdata:/appdata
     environment:
-      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
-      - PUID=1000
-      - PGID=999
+        - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
+        - PUID=1000
+        - PGID=999
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
 And set the permissions for the mounted directories:
@@ -90,4 +90,4 @@ mkdir -p ./homarr/appdata
 chown -R 1000:999 ./homarr/appdata
 ```
 
-Important here is that the group ID is set to `999` as we created the `docker` group with this ID.
+Important here is that the group ID is set to `999` as we created the `docker` group with this ID.

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

@@ -10,21 +10,20 @@ tags:
   - Active Directory
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+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.
 
 ### Auth configuration common variables
-
-| Environment Variable     | Description                                                                                                                                                                                                                                                                                                             | Default Value |
-| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
-| AUTH_PROVIDERS           | Select Which provider to use between _credentials_, _ldap_ and _oidc_. <br /> Multiple providers can be enabled with by separating them with `,`, (ex. `AUTH_PROVIDERS=credentials,oidc`, it is highly recommended to just enable one provider).                                                                        | credentials   |
-| AUTH_LOGOUT_REDIRECT_URL | URL to redirect to after clicking logging out.                                                                                                                                                                                                                                                                          | ---           |
-| AUTH_SESSION_EXPIRY_TIME | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m")                                                                                                                                  | "30d"         |
-| AUTH_COOKIE_PREFIX       | Prefix used for all authentication cookies (session, csrf, callback, pkce, state, nonce). Change this if you run another Auth.js/NextAuth app on the same hostname as Homarr (browsers scope cookies by host, not by port) to avoid cookie name collisions. Only letters, numbers, hyphens and underscores are allowed. | `homarr`      |
+| Environment Variable      | Description | Default Value |
+|---------------------------|-------------|---------------|
+| AUTH_PROVIDERS             | Select Which provider to use between *credentials*, *ldap* and *oidc*. <br /> Multiple providers can be enabled with by separating them with `,`, (ex. `AUTH_PROVIDERS=credentials,oidc`, it is highly recommended to just enable one provider).  |  credentials  |
+| AUTH_LOGOUT_REDIRECT_URL  | URL to redirect to after clicking logging out.  | --- |
+| AUTH_SESSION_EXPIRY_TIME  | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m") | "30d"  |
+| AUTH_COOKIE_PREFIX  | Prefix used for all authentication cookies (session, csrf, callback, pkce, state, nonce). Change this if you run another Auth.js/NextAuth app on the same hostname as Homarr (browsers scope cookies by host, not by port) to avoid cookie name collisions. Only letters, numbers, hyphens and underscores are allowed. | `homarr`  |
 
 <Tabs>
   <TabItem value="credentials" label="Credentials Provider" default>

apps/docs/docs/advanced/styling/index.mdx

@@ -19,14 +19,12 @@ Homarr uses https://mantine.dev/ under the hood. You can change the look & feel
 using custom CSS, that extends or overwrites the styles from Mantine.
 
 ## Getting into CSS
-
 If you don't have any experience with CSS,
 we strongly recommend you to go through the courses here: https://www.w3schools.com/css/.
 Due to the infinite scenarios and setups possible with custom CSS,
 our support team will not provide any support with your own written CSS.
 
 ## Limitations and dangers
-
 When using custom CSS, you can break the page or certain functionalities.
 Although CSS can improve the design & feel of the page, it **<ins>cannot do any of the following</ins>**:
 
@@ -35,23 +33,21 @@ Although CSS can improve the design & feel of the page, it **<ins>cannot do any
 - Completely revamp the design of the page, only smaller changes are possible
 
 Here are some dangers of using custom CSS:
-
 - Updates may contain breaking changes in the structure, built-in styling or how styling is processed. Therefore,
-  custom CSS may break unexpectedly without any warning
+custom CSS may break unexpectedly without any warning
 - Custom CSS may make certain elements invisible or not possible to click / interact with
 - Custom CSS could make readability and accessibility worse for impaired people
 
 ## How to inspect the page
-
-When styling the page, you can use the `Inspector` to inspect elements on the page and try out styles.
+When styling the page, you can use the ``Inspector`` to inspect elements on the page and try out styles.
 This may vary depending on your browser and operating system, but the workflow usually goes like this:
 
 - Open the Homarr page
-- Press `Ctrl` + `Shift` + `I` at the same time.
-  Alternatively, right-click on the page and choose `Inspect` or `Inspect element`.
-- Open the tab `Elements` if it isn't open yet.
+- Press ``Ctrl`` + ``Shift`` + ``I`` at the same time.
+Alternatively, right-click on the page and choose ``Inspect`` or ``Inspect element``.
+- Open the tab ``Elements`` if it isn't open yet.
 - Search the element you want to change in the DOM tree or use the element picker (usually at the top left)
-  to select it by clicking on the page.
+to select it by clicking on the page.
 - Experiment by changing the CSS code on the right side
 
 When writing custom CSS, it is important to also remember or create a selector, which tells the browser
@@ -59,19 +55,17 @@ which element to apply the styles to. If you accidentally broke something or wan
 simply reload the page.
 
 ## Using Homarr's classes
-
 Homarr's elements will already have a lot of classes and styles pre-applied.
 You can reuse those classes to apply additional styles or overwrite them.
-When overwriting, remember to add the `!important` flag to your CSS property to tell the browser to use our instruction instead.
+When overwriting, remember to add the ``!important`` flag  to your CSS property to tell the browser to use our instruction instead.
 
-Classes with random number suffixes, such as `mantine-Card-x2fske`, should be avoided, since those are dynamic
+Classes with random number suffixes, such as ``mantine-Card-x2fske``, should be avoided, since those are dynamic
 CSS classes that will change with every build. This means, every time you update Homarr,
 your styles will no longer apply to them
 
 ## Defining custom classes for widgets
-
 If you want to apply the styles only for one widget, you can define custom class names only for that widget.
-To do that, enter edit mode on your board, click the three dots of your widget, click `Edit item` and click `Advanced options`.
+To do that, enter edit mode on your board, click the three dots of your widget, click ``Edit item`` and click ``Advanced options``.
 Then, you can enter as many custom classes as you'd like:
 
 ![](./img/widget-custom-classes.png)
@@ -79,24 +73,22 @@ Then, you can enter as many custom classes as you'd like:
 To save them, click `Save changes` on both modals and exit edit mode.
 
 ## Where to enter custom CSS
-
 After you wrote your custom CSS, it is time to permanently save it, so you don't need to use the inspector anymore.
 To do this, enter the board settings:
 
 ![](./img/enter-board-settings.png)
 
-Scroll to the **Custom CSS** section on the board settings page. It is part of the unified settings form; enter your CSS
-there and save the board settings to apply it to that board.
+Scroll down a bit and click on custom CSS.
+Here you can enter your CSS code, which will be applied on the respective board page.
 
 ![](./img/custom-css-setting.png)
 
 ## Using variables
-
 You can also change the values of the theme variables, which are located here: https://mantine.dev/styles/css-variables-list/.
 To do this, see the following example CSS:
 
 ```css
 :root {
-  --mantine-primary-color-filled: #ffbb00;
+    --mantine-primary-color-filled: #ffbb00;
 }
-```
+```

apps/docs/docs/community/_category_.json

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

apps/docs/docs/community/donate.mdx

@@ -7,15 +7,12 @@ tags:
 ---
 
 # Donate
-
 ## Why to donate
-
 Our team of 4 developers is working on Homarr in their free time.
 Homarr has become a big part of our daily things we work on - and therefore we invest a lot of time into maintaining Homarr,
 providing support and implementing new features.
 We also incur monetary costs while developing Homarr for the tools that we need.
 A few examples include:
-
 - Renting for a Cloud VPS for our cloud services (status page, monitoring, email, analytics, [demo instance](https://demo.homarr.dev/), ...)
 - Paying for (IDE-) licenses
 
@@ -23,7 +20,6 @@ Using a donation, you help us to cover these expenses and enable the development
 Homarr is completely free to use. We'd highly appreciate if you consider donating, especially if you use Homarr in a commercial environment.
 
 ## Where to donate
-
 We accept donations on our official [OpenCollective](https://opencollective.com/homarr).
 You may also sponsor us directly by providing a useful service / product to us other means.
-You can get into contact with us [here](/docs/community/get-in-touch).
+You can get into contact with us [here](/docs/community/get-in-touch).

apps/docs/docs/community/faq.mdx

@@ -5,57 +5,43 @@ tags:
   - Help
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 ### Can I install Homarr on a Raspberry Pi?
-
 Yes, Homarr is compatible with the architecture of the Raspberry Pi. Have a look in our <a href="/docs/category/installation-1">installation guide</a> on how to do so.
 
 ### I have a suggestion / idea for improvement or want to report a bug
-
 You can report issues, suggestions, or ideas for improvements <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
 
 ### Can I use my own custom icons for apps?
-
 Yes, check out our guide on <a href="/docs/advanced/customizations/icons">how to add your custom icons</a>.
 
 ### Some of my online icons are not working (anymore)
-
 It seems the `cdn.jsdelivr.net` database of icon sometimes appear in the lists for DNS-Holes (PiHole, AdGuard Home...). <br />
 So make sure to manually whitelist this address.
 
 ### Can I add my own widgets? Do I need programming skills?
+We have decided, not to support custom widgets, until Homarr is in a stable and highly polished state.
+Enabling users to write their own widgets is easy at the first glance, but there are some major issues with it:
 
-Yes. A [Custom Widget](/docs/management/custom-widgets) can read a public or private HTTP API.
+- There are mainly two options for adding plugins or custom widgets to Homarr. The first option is, to allow and inject custom code in Homarr. Apps like Nextcloud can do this easily, because they use the Runtime to render all components of the application (In reality, the process is still a bit more complicated). In contrast, Homarr is using Next.js - a framework that needs to be compiled in production. That means, that each time you would modify a custom widget or plugin, the app would have to be restarted. There are options to avoid this, but they are quite flakey and bring disadvantages in our experience. The second option is, to write widgets declaratively instead of imperatively. This way, we would be able to render and modify widgets without any restarting at all. However, we'd have to write our own interpreter for said declarative schema. This is totally possible, but requires a lot of planning and architecture design to function properly. The required work to implement either option is therefore quite substantial.
+- Custom widgets would need to be able to request data, so they work properly. We use tRPC for this. Many APIs use different formats and we'd have to convert and read those.
+- Using custom widgets, one could easily create harmful widgets, leak your personal data (potentially including your tokens) and trick your users. A proper implementation (eg. official plugin store, where we can ban harmful widgets from) would resolve this problem to a certain extent, but again requires additional work and time to be put in.
 
-It can show responsive Mantine JSX. It can also use widget options and actions with board permission checks.
-
-Custom JSX v2 is the only Custom Widget format. Write the JSON and JSX in the workbench.
-
-You can also use the AI copy prompt. An MCP agent can validate and preview a definition before it saves the definition.
-
-The workbench reads a pasted AI response. It shows request capabilities and redacted diagnostics.
-
-A template cannot import packages or run arbitrary JavaScript. It cannot call browser `fetch`.
-
-Named requests use the Homarr server. The server applies board permissions and the network policy.
-
-Before installation, examine the origins, methods, permissions, and actions. Use the same review before publication.
+If you still want to add a widget, please consider to contribute it directly to Homarr. For that, basic programming skills are required. Our [Developer Guides](/docs/advanced/development/getting-started) explain this even more detailed.
 
 ### Is it secure to expose Homarr to the web?
 
-Yes, since v0.14.0, we are confident that Homarr is secure enough to be exposed to the web.
+Yes, since v0.14.0, we are confident that Homarr is secure enough to be exposed to the web. 
 Make sure to enable the "allow anonymous access" [option in the settings](/docs/management/boards#access-control), if you want to allow people without an account to be able to see your dashboard (not edit)
 
 ### How do I open the console / log?
-
 There are two different sources of information:
-
 - console: This is your client (browser). It can tell us, if there is an issue on the client (crash, bug, ...).
 - log: This is your server. It will tell us, if there are issues with connections for the integrations, crashes and errors.
 
-Both variants _can_ contain personal data. It's recommended, that you don't post them publicly or remove personal data from it.
+Both variants *can* contain personal data. It's recommended, that you don't post them publicly or remove personal data from it.
 
 <Tabs>
   <TabItem value="apple" label="Read console" default>
@@ -63,45 +49,39 @@ Both variants _can_ contain personal data. It's recommended, that you don't post
 > Note: This will not work on most mobile browsers.
 
 Open your browser and ensure, that Homarr is your current tab.
-Press `CTRL` + `SHIFT` + `I` on your keyboard. If this shortcut doesn't work, please use one of the alternatives: https://developer.chrome.com/docs/devtools/open/.
-Click on `Console` in the new window, that opened. There, you should see white, orange and sometimes red messages. You can use the Windows Snip & Sketch tool (or your respective tool on Linux / MacOS) to screenshot those messages.
+Press ``CTRL`` + ``SHIFT`` + ``I`` on your keyboard. If this shortcut doesn't work, please use one of the alternatives: https://developer.chrome.com/docs/devtools/open/.
+Click on ``Console`` in the new window, that opened. There, you should see white, orange and sometimes red messages. You can use the Windows Snip & Sketch tool (or your respective tool on Linux / MacOS) to screenshot those messages.
 
 > Please never execute any commands in the console. Scammers are using the console to let you execute harmful commands. If you want to resolve an issue in Homarr, **you'll never have to execute any commands here**
 
   </TabItem>
   <TabItem value="orange" label="Read log">
 
-This depends on your installation method. If you use Unraid, you can simply click on the App and on `Log`. If you have a bare Docker install, use `docker container logs homarr`. If you used a different name than `homarr` for your container, you need to replace said argument. Here is some additional information about the command: https://geekflare.com/check-docker-logs/.
+This depends on your installation method. If you use Unraid, you can simply click on the App and on ``Log``. If you have a bare Docker install, use ``docker container logs homarr``. If you used a different name than ``homarr`` for your container, you need to replace said argument. Here is some additional information about the command: https://geekflare.com/check-docker-logs/.
 
   </TabItem>
 </Tabs>
 
 ### How do I post logs?
-
 Please check [the section above](#how-do-i-open-the-console--log), on how to obtain logs. Logs should always be posted to https://pastebin.com/ or https://rentry.co/.
 
 ### Can I use Homarr at my company?
-
 Yes, you can! But please consider a donation, if our work has been useful to you.
 
 ### I think I found a bug. What can I do?
-
 If you think, that you found a bug, please create an issue <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
 
 ### Why can't I use my custom icons?
-
 You need to restart the Homarr Docker container after adding icons.
 
 ### Why can't homarr see/ping containers running locally behind GluetunVPN?
-
 This is because GluetunVPN, and many other docker VPN services, secure their VPN connections with strict firewalls. These firewalls often block access to local containers, even on the same docker network. The workaround for <a href="https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md">GluetunVPN</a> is to add "- FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24" into the environmental variables of the docker compose file. If you are using a firewall on your system, you will need to add a rule that allows requests from ip's in the range of 192.168.xxx.xxx . If you are using UFW the command would be "sudo ufw allow from 192.168.0.0/16".
 Tip: If you are running your torrent client behind a VPN, and running Sonarr (or something similar) normally, make sure to open your torrent client's port in your firewall. If you don't, Sonarr will not be able to see it. Furthermore, use your machines IP (192.168.x.x) rather then 127.0.0.1 or localhost.
 
 ### Can I get in touch with you?
-
 Yes, go <a href="/docs/community/get-in-touch">here</a> to get with us in touch.
 
-<hr />
+<hr/>
 
 :::tip
 

apps/docs/docs/community/get-in-touch.mdx

@@ -9,16 +9,16 @@ tags:
 We're happy to talk with you! Shoot us a message at the following places:
 
 ## E-Mail
-
 We are open to discuss sponsorships, security vulnerabilities and other private requests through our email.
 Please do not report any bugs / feature requests here - they will be ignored and deleted.
 
 [homarr-labs@proton.me](mailto:homarr-labs@proton.me)
 
 ## Discord
-
 We have a Discord Server, where we announce new releases, discuss features and bugs and show off our dashboards.
 There are over 4'000 members and we're happy to answer your questions or concerns.
 You're also open to discuss new / upcoming features and any offtopic selfhosting content.
 
 [_![](https://discordapp.com/api/guilds/972958686051962910/widget.png?style=banner2)_](https://discord.gg/aCsmEV5RgA)
+
+

apps/docs/docs/community/license.mdx

@@ -7,7 +7,6 @@ tags:
 Homarr is licensed under [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0).
 
 ## TL;DR
-
 | Action         | Allowed |
 | -------------- | ------- |
 | Copy           | ✅      |
@@ -25,6 +24,8 @@ Please consider [making a donation](/docs/community/donate) to Homarr, if this p
 
 :::
 
+
+
 ## Full License
 
 ```txt

apps/docs/docs/community/translations.mdx

@@ -5,31 +5,30 @@ tags:
   - Translations
 ---
 
-We want to make Homarr accessible for everyone.
-But to do that, we need your help.
-We are running a community program that enables everyone to translate Homarr into their language – no programming required.
-We are using [Crowdin](https://crowdin.com/) to manage our translations.
+We want to make Homarr accessible for everyone. 
+But to do that, we need your help. 
+We are running a community program that enables everyone to translate Homarr into their language – no programming required. 
+We are using [Crowdin](https://crowdin.com/) to manage our translations. 
 You can find the translations [here](https://translate.homarr.dev/).
 
 ## How to translate
 
-### Using crowdin's online platform
 
-Go to the [Crowdin translations](https://translate.homarr.dev/) and select a language you want to translate.
-You can then enter the translation mode and start translating.
-After you've submitted your translations, a Proofreader will review your changes.
-After a translation has been approved, it will be merged to the language development branch.
-We merge this one periodically to the development branch.
+### Using crowdin's online platform
+Go to the [Crowdin translations](https://translate.homarr.dev/) and select a language you want to translate. 
+You can then enter the translation mode and start translating. 
+After you've submitted your translations, a Proofreader will review your changes. 
+After a translation has been approved, it will be merged to the language development branch. 
+We merge this one periodically to the development branch. 
 After the next update of Homarr, all changes from the development branch will be merged, including the changes in the translations.
 
 ### Using live translate
-
 You can also help translate homarr directly from the app!
 For this you can simply change your language to "Crowdin (live translations)"
 
 ![](./img/crowdin-language-select.png)
 
-Then you'll be prompted to connect to your Crowdin account and choose the language in which you want to transalte.
+Then you'll be prompted to connect to your Crowdin account and choose the language in which you want to transalte. 
 You can then start translating directly from the app by selecting some text on the app.
 If some text cannot be selected to be edited with the live translation tool, you can still translate it inside of the In-Context popup at the Home tab, it will be red if it's not translated yet.
 
@@ -48,8 +47,7 @@ Do you want to become a proofreader? [Let us know on our Discord](/docs/communit
 :::
 
 ## Guidelines
-
 1. Translate with context: Some translations can't be translated 1:1 - they need context. Ensure that your translations make sense in the context.
 2. Keep things simple and original - no additional characters are needed.
 3. Don't translate the same thing twice - if you see a translation that is already translated, don't translate it again unless you have a better translation.
-4. Keep your translations as close to the original as possible.
+5. Keep your translations as close to the original as possible.

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

@@ -6,16 +6,18 @@ tags:
   - Configuration
 ---
 
+import imageStartFromScratchStepServerSettings from "./img/onboarding-from-scratch-step-server-settings.png";
+import imageStartFromScratchStepAdminUser from "./img/onboarding-from-scratch-step-admin-user.png";
+import imageStartFromScratchStepExternalAdminGroup from "./img/onboarding-from-scratch-step-external-admin-group.png";
+import imageStartFromScratchStepFinish from "./img/onboarding-from-scratch-step-finish.png";
+import manageBoardHeaderEditMode from "./img/manage-board-header-edit-mode.png";
+import manageBoardHeaderAddItem from "./img/manage-board-header-add-item-menu.png";
+import manageBoardHeaderChooseItem from "./img/manage-board-header-choose-item.png";
 import manageBoardNoApp from "./img/manage-board-no-app.png";
-import currentKeyboardTileEditing from "../management/boards/img/keyboard-tile-editing.png";
-import boardDesktopCurrent from "./img/onboarding-board-desktop-current.png";
-import boardEditModeCurrent from "./img/onboarding-board-edit-mode-current.png";
-import addContentMenuCurrent from "./img/onboarding-add-content-menu-current.png";
-import chooseItemCurrent from "./img/onboarding-choose-item-current.png";
-import editItemCurrent from "./img/onboarding-edit-item-current.png";
-import boardsHomeMobileMenu from "./img/onboarding-boards-home-mobile-menu.png";
-import moveResizeMenuCurrent from "./img/onboarding-move-resize-menu-current.png";
-import currentBoardMobileView from "./img/onboarding-board-mobile-current.png";
+import manageExportOldHomarr from "./img/old-homarr-export-data.png";
+import manageImportOldHomarrDropzone from "./img/old-homarr-import-dropzone.png";
+import manageImportOldHomarrChooseData from "./img/old-homarr-import-choose-imported-data.png";
+import manageImportDecryptionToken from "./img/old-homarr-import-decryption-token.png";
 
 :::tip
 
@@ -27,50 +29,128 @@ Congratulations on installing Homarr. Now it's time to get yourself familiar wit
 
 ## Onboarding
 
-Onboarding appears the first time Homarr starts. Its goal is to create a useful responsive board, not merely an
-administrator account. The setup uses one guided studio, so you can keep the safe defaults and finish quickly or review
-every detected service before anything is added to the board.
+The onboard will show the first time you start Homarr.
+This process will help you with your first steps and adding some initial data, such as the administrator account.
 
 :::note
 
-If you see this screen repeatedly after restarting the Homarr container, your Docker mounting paths may be missing,
+If you see this screen repeatitly after you restarted the Homarr container, your Docker mounting paths may be missing,
 incorrect or read-only. Read [our installation instructions](/docs/getting-started/installation/docker) again to fix this issue.
 
 :::
 
-### Restore or start fresh
+You can either import a previous dashboard using the ZIP archive or start from scratch:
 
-SQLite installations can restore a complete Homarr database backup from the welcome screen. This restores current
-boards, people, apps, integrations, and settings. The pre-1.0 ZIP importer is no longer included.
+![Screenshot of Step 1 onboarding](./img/onboarding-step-1.png)
 
-For a new installation, Homarr first creates either a credentials administrator or an administrator group matching your
-LDAP/OIDC provider. The browser that starts setup claims the first-run session; refreshes are safe, while another browser
-cannot change credentials or integrations during that setup.
+You may refresh anytime and continue from a different device - the onboarding is saved immediately on the server for your convenience.
 
-### Setup studio
+### Starting from scratch
 
-The studio keeps related choices together:
+Depending on your auth provider configuration you will either first see the admin user creation form or the external group creation form.
+If the credentials provider was selected, you'll be prompted to create an admin user for Homarr.
+This user cannot be deleted and has full control over Homarr and all of its boards.
+You must choose a username and password (both can later be changed).
+We enforce strict password requirements when you enter your password to protect your instance if you accidentally
+expose it to the internet.
 
-1. **Essentials** sets the default language, color scheme, analytics preference, and the usual host, IP address, domain, or reverse-proxy path used by your services. URL suggestions can use separate ports, subdomains, or one path per service.
-2. **Discover** checks the actual database, Docker-compatible sockets, Kubernetes configuration, Workshop, and Assistant capabilities. Unavailable sources never block manual setup.
-3. **Connect** shows detected integrations and apps first, identifying whether each app came from an explicit [`homarr.*` or Homepage Docker label](/docs/integrations/docker-labels) or image matching. Select several integrations and apps at once, review every URL, and use the service-specific link to open its API-key settings when one is available. If a container has no published port or URL label, add its HTTP or HTTPS address before importing it.
-4. **Board** previews the Base layout, colors, widget radius, sidebars, selected apps, and widgets inferred from integrations or Docker labels. Choose 8 columns for a focused board, 10 for a balanced board, 12 for a wide board, or use the slider for a custom width up to 24 columns. Homarr still creates and reflows the protected Mobile layout automatically. A fast setup adds the integration-free Clock, Weather, and Bookmarks starter widgets.
-5. **Extend** explains and optionally configures Assistant, the community Workshop, and the separate Homarr MCP endpoint.
-6. **Review** tests the selected connections, then saves integrations, apps, widgets, settings, and the exact first board together. If any part fails, the database changes are rolled back and your form stays available to correct.
+<img
+  src={imageStartFromScratchStepAdminUser}
+  alt={"Screenshot form to create admin user"}
+  width={300}
+/>
 
-Docker discovery reports each configured host separately. Results from reachable hosts remain selectable if another socket
-is unavailable, which is useful for remote Docker, rootless Docker, Synology, and mixed deployments. On Kubernetes or
-bare-metal installations without a Docker socket, enter services manually and use the same integration catalog.
+If you selected external providers (such as LDAP or OIDC), you'll be prompted to create an admin group.
+This group will be used to synchronize users from your provider to Homarr.
+When a user logs in through the provider, any of their groups that match groups in Homarr will be assigned to the user.
+The name of the group must match exactly the name of the group in the provider.
 
-After setup, **Open my board** takes you directly to the configured board. The in-product tour then introduces edit mode,
-responsive layouts, widgets, and search without delaying completion.
+<img
+  src={imageStartFromScratchStepExternalAdminGroup}
+  alt={"Screenshot form to create external admin group"}
+  width={300}
+/>
 
-## Creating another board
+Next, you can configure some basic settings for Homarr. We recommend to leave all settings at default for most users.
+Here you can also disable analytics. Please note that our analytics are completly anonymous and is fully compliant with GDPR and PECR.
+
+<img
+  src={imageStartFromScratchStepServerSettings}
+  alt={"Screenshot of analytics and indexing settings in the onboarding"}
+  width={300}
+/>
+
+### Setting up integrations
+
+After configuring server settings, the onboarding guides you through setting up your integrations.
+
+#### Docker service discovery
+
+If Docker is available (socket mounted), Homarr automatically detects running containers and matches them to known integration types.
+Matching integrations are pre-selected in the integration list, saving you from manually picking each one.
+
+#### URL templating
+
+You can define a base URL template to auto-fill integration URLs in bulk.
+Two modes are supported:
+
+- **Subdomain mode** - e.g. `{app}.example.com` where `{app}` is replaced with the integration name
+- **Port mode** - e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port
+
+#### API key helper links
+
+For integrations that require API keys (such as Sonarr, Radarr, SABnzbd, or Seerr), a helper link opens the relevant settings page in the target application so you can quickly copy your key.
+
+#### Creating apps from Docker containers
+
+You can optionally auto-create bookmark apps for all discovered Docker containers, making them immediately available on your board.
+
+:::note
+
+Release providers and Search.ch are configured directly in their widgets instead of the integrations page.
+
+:::
+
+After this step, you finished the onboarding.
+The onboarding can no longer be started again.
+From here you can click on one of the provided links to continue your journey.
+We recommend you to continue with the section [creating your first board on this page](#creating-your-first-board).
+
+<img
+  src={imageStartFromScratchStepFinish}
+  alt={"Screenshot of the finish onboarding process with links"}
+  width={300}
+/>
+
+### Importing a ZIP from version before 1.0.0
+
+This is recommended when you used Homarr before and want to re-import your data.
+It is important that you first migrate correctly using [the list of breaking changes for 1.0](/blog/2024/09/23/version-1.0).
+
+<img
+  src={manageExportOldHomarr}
+  alt="Export from old Homarr"
+  style={{ maxWidth: 500 }}
+/>
+
+**How to export and import data**
+
+1. Navigate to your old Homarr, open your management pages, open the tools submenu and open `Migrate to 1.0`.
+2. Check the contents that you want to export. We recommend you to export all data.
+3. Click on the export data button
+4. Save the ZIP file, that is being downloaded, on your device. If you selected "integrations" or "users", you also get an encryption / decryption key.
+   Copy it and do not loose it!
+5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose `Import from Homarr before 1.0`
+6. Drag and drop your previously downloaded ZIP archive into the file upload: <br/><img src={manageImportOldHomarrDropzone} style={{ maxWidth: 500 }} />
+7. Next, choose the data that you want to import and how to import it. Since screen sizes were removed in 1.0, we create a new board for every screen size by default. We recommend you to only keep the best layout and adjust it later in 1.0.0 - but you can also import all of them and pick later.<br/><img src={manageImportOldHomarrChooseData} style={{ maxWidth: 500 }} />
+8. If you previously exported integrations or users, you will be asked to decrypt the data safely using your obtained encryption token. Paste into the modal and confirm your action.<br/><img src={manageImportDecryptionToken} style={{ maxWidth: 500 }} />
+9. Next, you can [follow the same setup as when starting from scratch](#starting-from-scratch). After you completed the onboarding, all of your data will be migrated and available.
+
+## Creating your first board
 
 In Homarr, you organize your apps and widgets on boards.
-Boards use fixed-size tiles so the same widget keeps the same proportions on every screen.
-Drag, resize, and section controls are available in edit mode.
-Onboarding already created the first board. To create another one, navigate to `Manage` > `Boards` > `New board`:
+Boards can be organized using the interactive drag and drop.
+Let's create your first board by navigating here: `Manage` > `Boards` > `New board`:
 ![](./img/manage-create-board-button.png)
 
 A board must always have a name and can either be public or private.
@@ -78,25 +158,9 @@ Public boards are also accessible for users, that are not logged in ([see access
 
 ![](./img/manage-create-board-modal.png)
 
-Congratulations - you've just created another board. You can see the boards you have access to on this page:
+Congratulations - you've just created your first board. You can see boards, that you have access to, on this page:
 
-<figure>
-  <img
-    src={boardsHomeMobileMenu}
-    alt="Boards management page showing a Home badge and separate desktop and mobile home-board menu entries"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>The Boards page selects the board opened from Home separately for desktop and mobile.</figcaption>
-</figure>
-
-The board marked **Home** is the board opened from the desktop Home route. **Set as your mobile board** selects which board
-opens on phones. This is separate from the **Mobile** layout: the home-board setting chooses a board, while **Mobile** and
-**Base** are responsive layouts inside that board. A phone can therefore open a different home board and still use that
-board's Mobile layout.
-
-New boards start with **Mobile** and **Base** responsive layouts automatically, so you can edit the board for phones and
-desktops without creating extra layouts first. Mobile starts at `0px` with 3 columns and Base at `768px` with 10 columns.
-Each layout keeps its own tile positions and sizes.
+![](./img/manage-view-board.png)
 
 ## Add your first app to Homarr
 
@@ -120,126 +184,77 @@ After you created the app, you'll see in on the apps page:
 Let's add your freshly created app, from the previous step, to the board.
 To do this, edit your previously created board by clicking on the big `Open board` button:
 
-<figure>
-  <img src={boardDesktopCurrent} alt="Current Homarr board opened from the Boards page" style={{ maxWidth: "100%" }} />
-  <figcaption>Open a board to view its dashboard, then enter edit mode to arrange its content.</figcaption>
-</figure>
+![](./img/manage-view-board.png)
 
 Here you have the following options in the header:
 
 ![](./img/manage-board-header.png)
 
 - **Search**: Here you can search for data. You can search for integrations, boards, actions, sites and much more. Some actions may be context dependent (eg. will only show when certain widgets are on your page)
-- **Edit board**: Clicking this button will toggle edit mode. In this mode you can edit the contents of your board.
+- **Edit mode**: Clicking this button will toggle the edit mode. In this mode you can edit the contents of your board.
 - **Settings**: Clicking this button will redirect you to a settings page where you can adjust the board settings (page title, colors, ...).
-- **Profile**: This avatar will be visible on every page. Its menu includes the board switcher; press `Shift+C` to open
-  it directly. The current board is left out of the results.
+- **Profile**: This avatar will be visible on every page. Clicking it will show a menu with actions.
 
 When entering the edit mode, you'll get some additional buttons to work with:
 
-<figure>
-  <img
-    src={boardEditModeCurrent}
-    alt="Current Homarr board editor with tile controls visible"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>The current editor keeps the board visible while its editing controls are available.</figcaption>
-</figure>
+<img
+  src={manageBoardHeaderEditMode}
+  alt={"Screenshot of buttons in the edit mode"}
+  width={200}
+/>
 
-- **Add board content**: Click this button to create a new item, app, integration, or Container.
-- **Save board**: Click this button to save your changes and leave edit mode. If you leave with unsaved changes, Homarr asks whether to discard them.
+- **Add item**: Click this button to add new elements to your page.
+- **Exit edit mode**: Click this btuton to save your changes and exit edit mode.
 
-Outside edit mode, right-click a widget for its live status, refresh, settings, quick options, and supported actions.
-Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the rest of the board
-stays visible but dimmed. Release `Shift` to close it. Hold `Shift` plus `Ctrl` on Windows/Linux or `Cmd` on macOS to
-keep its advanced view open until you close it. Widgets without a distinct advanced experience adapt in place.
+To continue, click the option "New Item":
 
-To continue, click **New item** in the add-content menu. New content is placed at the first available position on the main
-canvas; it is not inserted at a clicked empty cell or directly into a rail or Container:
-
-<figure>
-  <img
-    src={addContentMenuCurrent}
-    alt="Current add board content menu with item, app, integration, and Container actions"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>The add-content menu provides the four supported ways to place new content on the board.</figcaption>
-</figure>
+<img
+  src={manageBoardHeaderAddItem}
+  alt={"Screenshot of the add item menu"}
+  width={200}
+/>
 
 Next, you can choose what item you'd like to add.
 We will discuss the other options in the following sections - for now choose "App" to continue.
 
-<figure>
-  <img
-    src={chooseItemCurrent}
-    alt="Current item picker showing the App card and other item types"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>Choose the App item from the current picker to add an app tile.</figcaption>
-</figure>
+<img
+  src={manageBoardHeaderChooseItem}
+  alt={"Screenshot of choosing the app item in the modal"}
+  width={300}
+/>
 
 As soon as you chose the app, the modal will close and you'll get the following item on your board:
 
-<img src={manageBoardNoApp} alt="Screenshot of the No app element on the board" />
+<img
+  src={manageBoardNoApp}
+  alt="Screenshot of the No app element on the board"
+/>
 
 This is expected, because you haven't told Homarr what app it should show in this item.
 To configure this, click on the small 3 dots at the top of the item in the edit mode and choose "Edit item" in the menu.
 
-<figure>
-  <img
-    src={moveResizeMenuCurrent}
-    alt="Current board tile menu showing Edit item and Move or resize item"
-    style={{ maxWidth: "450px" }}
-  />
-  <figcaption>The tile menu contains the item editor and the separate move-and-resize tools.</figcaption>
-</figure>
+![](./img/manage-board-edit-app.gif)
 
 In the modal you can edit the app that you want to display:
 
-<figure>
-  <img src={editItemCurrent} alt="Current Edit item modal for an App tile" style={{ maxWidth: "620px" }} />
-  <figcaption>
-    The Edit item workspace previews option changes as you configure the tile. Save changes to apply them to the board.
-  </figcaption>
-</figure>
-
-When adding a widget, set its initial grid width and height directly in the preview. These size controls are only shown before the widget is added.
+![](./img/manage-board-choose-app.png)
 
 As soon as you save your changes, the tile on the board will refresh and display your app.
-Resize from any visible edge or corner handle. For a Container, activate its top-left grip before using its resize handles.
-Press and hold a handle, move the pointer, and release it when the tile has the size you want.
+Using the small bidirectional arrow at the bottom right you can resize the element.
+Start pressing with your mouse button down, move your mouse to resize and release your finger as soon your you're happy with the size.
 
-To move a tile in edit mode, press and hold its inert content area, move it to the desired position, and release it.
-Widget content is disabled while editing so its controls do not intercept the drag; use the tile's settings button for edit actions.
-The tile snaps to the grid. A single compatible collision may swap the two items when both resulting placements fit;
-otherwise the collision chain reflows neighboring tiles automatically.
+![](./img/resize-item.gif)
 
-Every `1 × 1` tile has a logical content size of `200 × 200` pixels.
-Larger tiles use multiples of that fixed unit, with a consistent gap between cells.
-Homarr scales the complete board uniformly, like zooming a page.
-The complete canvas always fits the available width without horizontal board scrolling. Below 100%, Homarr preserves the
-widget's readable typography and control density instead of shrinking each widget independently.
-It does not squeeze or reflow the content of individual widgets, so a widget keeps the same design and proportions across screen sizes.
+To move your item to a different position on the board, simply hold the mouse button anywhere on the item and move with the mouse to the desired position.
+As soon as you release your finger, the item will snap in place in the grid.
 
-On a narrow screen, Homarr uses the **Mobile layout** for the selected board and stacks the board content vertically while
-preserving each widget's fixed logical proportions:
-
-<figure>
-  <img
-    src={currentBoardMobileView}
-    alt="Homarr's Mobile layout in a 390-pixel-wide viewport, with tiles scaled to fit and stacked vertically"
-    style={{ maxWidth: "390px" }}
-  />
-  <figcaption>
-    At phone width, the selected board uses its Mobile layout and fits the complete canvas to the viewport.
-  </figcaption>
-</figure>
+![](./img/move-item.gif)
 
 :::note
 
-Viewing a board initially uses the lightweight, non-interactive layout.
-For users with edit access, Homarr prepares drag-and-drop and resize controls in the background after the board becomes interactive.
-If you enter edit mode before that finishes, the existing board stays visible until the editor is ready.
+You cannot move items freely on the vertical axis.
+We always align all items to the top of the page to simply organization.
+To move items to the bottom, you must add more items or resize items.
 
 :::
 
@@ -250,17 +265,14 @@ This helps you to explore the capabilities of Homarr before you build your board
 
 :::
 
-Keyboard users can focus a tile, press Enter or Space, then use arrow keys to move and Shift plus arrow keys to resize
-within its current canvas, rail, or Container. Press Escape to stop keyboard editing. Touch dragging starts after a short
-hold of about `200 ms`; resize handles accept direct touch input. During a pointer or touch move or resize, press Escape
-to cancel and restore the previous layout. For cross-grid moves or precise numeric controls, choose **Move / resize item**
-from the tile's edit menu.
-Keyboard commands at a grid boundary or minimum tile size are ignored and announced; they do not move or shrink the tile.
+Users on touch or mobile devices may not be able to drag and drop or move items.
+They can use the "Move / resize item" option in the edit menu of items instead:
 
-<img src={currentKeyboardTileEditing} alt="A board tile focused for keyboard editing" style={{ maxWidth: "100%" }} />
+![](./img/manage-board-move-resize-item-menu.png)
 
-Open **Move / resize item** from the tile menu to move the tile to another section or rail and enter precise numeric
-coordinates and dimensions. After making changes, click **Save board** to persist them and leave edit mode.
+Be sure to save your changes by exiting edit mode!
+
+![](./img/exit-edit-mode.png)
 
 ## Adding your first integration
 
@@ -295,14 +307,7 @@ Let's add your integration, that you have configured in the section above, as a
 First, navigate back to your board that you want to add it to.
 Next, enter edit mode again and add another item to your board:
 
-<figure>
-  <img
-    src={addContentMenuCurrent}
-    alt="Current add board content menu with item, app, integration, and Container actions"
-    style={{ maxWidth: "100%" }}
-  />
-  <figcaption>Use the same add-content menu to place an integration widget on the board.</figcaption>
-</figure>
+![](./img/manage-board-header-add-item-menu.png)
 
 Instead of choosing an app, let's choose `System Health Monitoring` this time.
 Click on "Add to board":
@@ -329,38 +334,47 @@ Editing a widget will trigger a data update and data will soon appear:
 
 ![](./img/widget-system-health.png)
 
-As with every change, click **Save board** to persist your board changes and leave edit mode.
+As with every change, don't forget to save your changes using the exit edit mode button:
 
-## Organizing items with Containers
+![](./img/exit-edit-mode.png)
 
-Containers are resizable areas for apps, widgets, and nested Containers.
-The same Container works on the main canvas, inside a fixed rail, or inside another Container.
-Each Container can configure:
+## Grouping your items
 
-- Its label and whether that label is visible.
-- Allow or disable collapsing.
-- Show or hide **Open all in new tabs**.
-- Change its border color and custom CSS classes.
+As the last step, let's organize your freshly created items using two different options.
+You can choose either or both of them on your boards.
 
-Open the add-content menu and choose **New container**.
-In edit mode, move and resize it like any other item, then drag items into or out of it.
-Nested content stays within the Container's bounds.
-While resizing, the solid outline follows the pointer continuously and the dashed grid preview shows the size that will be saved on release.
+### Using dynamic sections
 
-### Collapsing and opening apps
+Dynamic sections are a simple, resizable visual group to group items.
 
-Users can collapse an eligible Container like an accordion in view mode without changing its saved expanded size.
-The full-width header becomes the compact expansion bar, so the half-row state has no empty pill-shaped spacer.
-Expanding it restores its bounds and makes room for its contents.
-If **Open all in new tabs** is enabled, the Container menu can open every app link it contains.
+![](./img/create-dynamic-section.png)
 
-### Fixed rails
+After adding a dynamic section, you can simply drag and drop items into the section:
 
-Open the board's **Layout** settings to enable the left or right rail for each responsive layout.
-Choose one, two, or three columns with the slider and use the preview to check the remaining canvas width.
-The rail reserves those columns from the dashboard, so Homarr moves canvas items into the next available positions.
-Rail content stays visible while the page scrolls and remains editable.
-Each responsive layout keeps its own rail widths, item positions, and item sizes.
+![](./img/dynamic-section.gif)
+
+### Using categories
+
+Categories are more advanced and complicated than dynamic sections.
+To create a category, open the add item modal and choose "new category":
+
+![](./img/add-category.png)
+
+Every category must have a name. After you click "Add category", you will get a new item on your board:
+
+![](./img/category.gif)
+
+You can drag and drop items in to this category in the edit mode.
+Categories will have a big space before and after them in the edit mode to
+enable you to drag and drop items outside the category.
+You can also collapse or open categories in edit mode to facilitate your editing process.
+
+:::note
+
+A current limitation of categories is, that they will always have a width of 100%.
+You cannot reduce their horizontal width.
+
+:::
 
 ## Guided tours
 
@@ -373,7 +387,7 @@ Each page highlights the list view and the create action so you know where to fi
 
 ### Board tour
 
-When you first open a board, a tour highlights the board header elements: search, edit mode, settings, and the user menu.
+When you first open a board, a tour highlights the board header elements: search, edit mode, settings, board switcher, and user menu.
 
 ### Tour controls
 

apps/docs/docs/getting-started/glossary.mdx

@@ -1,13 +1,12 @@
 # Glossary
+In the glossary, you'll learn the different components and their names of Homarr.
 
-This glossary explains Homarr's main components and the terms used for them.
-
-| Term        | Definition                                                                              |
-| ----------- | --------------------------------------------------------------------------------------- |
-| Apps        | A piece of software that you or a third party hosts (for example, Google)               |
-| Integration | A connection to a service outside of Homarr                                             |
-| Container   | A resizable area that can hold apps, widgets, and nested Containers                     |
-| Widget      | A tile that uses your integrations to display data or enables you to interact with them |
-| Edit mode   | A temporary state where you can drag, resize, edit, or customize your board             |
-| Board       | A customizable page where apps, widgets, and Containers are arranged                    |
-| Tasks       | Workloads that are performed in the background, even if no user is present              |
+| Term            | Definition                                                                                                     |
+|-----------------|----------------------------------------------------------------------------------------------------------------|
+| Apps            | An piece of software that you or a third party hosts (eg. Google)                                              |
+| Integration     | A connection to a service outside of Homarr                                                                    |
+| Dynamic section | Resizeable area where items on your board can be placed and grouped                                            |
+| Widget          | A tile that uses your integrations to display data or enables you to interact with with them                   |
+| Edit mode       | Temporary state that you can enter where you can drag and drop, edit or customize your board                   |
+| Board           | Customizable page which can be edited using the edit mode. This is where apps, sections and widgets are placed |
+| Tasks           | Workloads that are performed in the background - even if there is no user present                              |

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

@@ -8,14 +8,13 @@ tags:
   - Unraid
 ---
 
-import Link from "@docusaurus/Link";
-import { IconArrowRight } from "@tabler/icons-react";
+import Link from '@docusaurus/Link';
+import { IconArrowRight } from '@tabler/icons-react';
 
 Before you try to install Homarr, please review if your device meets the requirements.
 Installing on an unsupported device may lead to unstable behaviour and no support will be provided.
 
 ## Hardware
-
 - At least 500MB RAM
 - At least 600MB of free disk space for the Docker image. SSD is preferred.
 - Single or dual core CPU
@@ -25,8 +24,8 @@ Installing on an unsupported device may lead to unstable behaviour and no suppor
 
 We build Homarr for a bunch of different architectures, including ARM. Please ensure that your device architecture is supported by Homarr. We won't be able to provide support for unusual or outdated architectures.
 
-| Architecture | Supported        |
-| ------------ | ---------------- |
+| Architecture | Supported       |
+|--------------|-----------------|
 | linux/amd64  | ✅ Supported     |
 | linux/arm64  | ✅ Supported     |
 | linux/arm/v7 | ❌ Not supported |
@@ -35,10 +34,10 @@ We build Homarr for a bunch of different architectures, including ARM. Please en
 
 <Link
   data-attr="Go to installation"
-  className={"button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800"}
+  className={'button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800'}
   to="/docs/category/installation-1"
 >
-  <div className={"flex items-center gap-3"}>
+  <div className={'flex items-center gap-3'}>
     <span className={"dark:text-gray-200"}>Go to Installation</span>
     <IconArrowRight className={"dark:text-gray-200"} size={20} />
   </div>

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

@@ -1,23 +1,21 @@
-import { DockerInstallSnippet } from "@site/src/components/pages/installation/docker/dynamic-docker-install";
+import { DockerInstallSnippet } from '@site/src/components/pages/installation/docker/dynamic-docker-install'
 
 # Docker
-
 Docker is our recommended installation method for beginners and professionals.
 It is easy to use, ships with all dependencies inside a single container and is easy to use and maintain.
 It requires at least some basic knowledge of [Docker](https://www.docker.com/).
 We recommend [NetworkChuck's Docker Containers 101](https://www.youtube.com/watch?v=eGz9DS-aIeY) as a good start for complete beginners.
 
 ## Docker compose
-
 ### Prerequisites
 
 - A Linux or Windows based system that meets the [hardware prerequisites](/docs/getting-started/#hardware) and [architecture prerequisites](/docs/getting-started/#architecture).
 - [Docker](https://docs.docker.com/get-docker/)
-- [Docker Compose](https://docs.docker.com/compose/install/) - _preinstalled on many systems nowadays_
+- [Docker Compose](https://docs.docker.com/compose/install/) - *preinstalled on many systems nowadays*
 
 ### Installation
 
-<DockerInstallSnippet data-visual-test="blackout" />
+<DockerInstallSnippet data-visual-test="blackout"/>
 Finally, run ``docker compose up -d`` in the same directory. This will start the Homarr container in the background.
 
 :::caution
@@ -28,26 +26,27 @@ Docker compose creates a network by default. Some integrations may not work (spe
 
 ### Updating
 
-To update, navigate to the directory with the `docker-compose.yaml` located.
+To update, navigate to the directory with the ``docker-compose.yaml`` located.
 
-- Stop Homarr using `docker compose down`
-- Pull the newest image of Homarr using `docker compose pull`
-- Start Homarr again using `docker compose up -d` (`-d` for detached mode - start in background)
-- Delete the old image using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+- Stop Homarr using ``docker compose down``
+- Pull the newest image of Homarr using ``docker compose pull``
+- Start Homarr again using ``docker compose up -d`` (``-d`` for detached mode - start in background)
+- Delete the old image using ``docker image prune`` (*Warning: this also removes you other unused images - not just Homarr*)
 
 You can automate this process using [Watchtower](https://containrrr.dev/watchtower/).
 
 ### Uninstalling
 
-To uninstall, navigate to the directory with the `docker-compose.yaml` located.
+To uninstall, navigate to the directory with the ``docker-compose.yaml`` located.
 
-- Stop Homarr using `docker compose down`
-- Delete the created directories & files on your root file system (check `docker-compose.yaml` file for your specific locations)
-- Delete compose file using `rm docker-compose.yaml`
-- Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+- Stop Homarr using ``docker compose down``
+- Delete the created directories & files on your root file system (check ``docker-compose.yaml`` file for your specific locations)
+- Delete compose file using ``rm docker-compose.yaml``
+- Prune unused Docker images using ``docker image prune`` (*Warning: this also removes you other unused images - not just Homarr*)
 - (Optional): Prune any network or volumes if you use any.
 - (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.
 
+
 ## Docker standalone
 
 :::caution
@@ -78,16 +77,15 @@ docker run  \
 
 :::note
 
-Docker will mount the configuration files and icons to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
+Docker will mount the configuration files and icons to your host machine. Please make sure to replace ``<your-path>`` from the docker run command with your desired storage location. The path must be absolute.
 
 :::
 
 ### Updating
-
 To update Homarr, you must remove your container first. Make sure that you've mounted your data and that you have access to it, so your configuration doesn't get lost.
 
-1. Run `docker rm homarr` to remove the container.
-2. Pull the latest Homarr image `docker pull ghcr.io/homarr-labs/homarr:latest`.
+1. Run ``docker rm -f homarr`` to stop and remove the container.
+2. Pull the latest Homarr image ``docker pull ghcr.io/homarr-labs/homarr:latest``.
 3. Re-run the command you used to install Homarr.
 
 This process can get tideous, if you update frequently. Thus, we recommend [using docker-compose](#docker-compose)
@@ -100,8 +98,8 @@ Want to update all your containers automatically? Checkout [Watchtower](https://
 
 ### Uninstalling
 
-1. Obtain the container ID of your Homarr container using `docker ps | grep homarr`.
-2. Delete the container using `docker rm <your-container-id>`
-3. Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+1. Obtain the container ID of your Homarr container using ``docker ps -a | grep homarr``.
+2. Delete the container using ``docker rm -f <your-container-id>``
+3. Prune unused Docker images using ``docker image prune`` (*Warning: this also removes you other unused images - not just Homarr*)
 4. (Optional): Prune any network or volumes if you use any.
 5. (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.

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

@@ -12,7 +12,7 @@ A Helm chart to deploy homarr for Kubernetes
 
 ## Source Code
 
-- <https://github.com/homarr-labs/homarr>
+* <https://github.com/homarr-labs/homarr>
 
 ## Requirements
 
@@ -76,38 +76,38 @@ To avoid including sensitive information in plain text within your version contr
 
 Below is an exhaustive list of all secrets:
 
-| FEATURE  | SECRET NAME      | SECRET KEYS                          | Required |
-| -------- | ---------------- | ------------------------------------ | -------- |
-| OIDC     | auth-oidc-secret | oidc-client-id<br>oidc-client-secret | No       |
-| LDAP     | auth-ldap-secret | bind-password                        | No       |
-| DATABASE | db-secret        | db-url                               | No       |
-| DATABASE | db-encryption    | db-encryption-key                    | yes      |
+| FEATURE   | SECRET NAME             | SECRET KEYS                             | Required |
+|-----------|-------------------------|-----------------------------------------|----------|
+| OIDC      | auth-oidc-secret        | oidc-client-id<br>oidc-client-secret    | No       |
+| LDAP      | auth-ldap-secret        | bind-password                           | No       |
+| DATABASE  | db-secret               | db-url                                  | No       |
+| DATABASE  | db-encryption           | db-encryption-key                       | yes      |
 
 ### Database
 
 You have multiple options for configuring the database:
 
-| DRIVER TYPE    | Persistence mode             |
-| -------------- | ---------------------------- |
-| better-sqlite3 | Pod disk                     |
-| better-sqlite3 | homarr-database PVC          |
-| mysql2         | External MySql database      |
-| node-postgres  | External Postgresql database |
+| DRIVER TYPE    | Persistence mode                |
+|----------------|---------------------------------|
+| better-sqlite3 | Pod disk                        |
+| better-sqlite3 | homarr-database PVC             |
+| mysql2         | External MySql database         |
+| node-postgres  | External Postgresql database    |
 
 #### Pod disk
 
-No additional configuration is required. However, keep in mind that if the pod restarts, all data will be lost. This setup is not _recommended_ for production use.
+No additional configuration is required. However, keep in mind that if the pod restarts, all data will be lost. This setup is not *recommended* for production use.
 
 To create the necessary database secret, execute the following command:
 
 <details>
 <summary>Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
 </details>
 
@@ -120,11 +120,11 @@ Associated secret to create :
 <details>
 <summary>DB Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
 </details>
 
@@ -133,13 +133,13 @@ Bellow an example of the override value file :
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrDatabase:
     enabled: true
     storageClassName: "default"
     size: "1Gi"
-```
+````
 
 </details>
 
@@ -150,18 +150,17 @@ To create the necessary database secrets, execute the following command:
 <details>
 <summary>Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
-```yaml
+````yaml
 kubectl create secret generic db-secret \
 --from-literal=db-url='mysql://user:password@host:port/homarrdb' \
 --namespace homarr
-```
-
+````
 </details>
 
 Below is an example of the override values file:
@@ -169,11 +168,10 @@ Below is an example of the override values file:
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 database:
   type: mysql
-```
-
+````
 </details>
 
 #### External Postgresql database
@@ -183,17 +181,17 @@ To create the necessary database secrets, execute the following command:
 <details>
 <summary>Required Secrets</summary>
 
-```yaml
+````yaml
 kubectl create secret generic db-encryption \
 --from-literal=db-encryption-key='<SECRET_ENCRYPTION_KEY_SECRET_TO_CHANGE>' \
 --namespace homarr
-```
+````
 
-```yaml
+````yaml
 kubectl create secret generic db-secret \
 --from-literal=db-url='postgresql://user:password@host:port/homarrdb' \
 --namespace homarr
-```
+````
 
 </details>
 
@@ -202,11 +200,10 @@ Below is an example of the override values file:
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 database:
   type: postgresql
-```
-
+````
 </details>
 
 ### Ingress
@@ -216,7 +213,7 @@ The ingress section in the values.yaml file allows you to configure how external
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 service:
   enabled: true # Ensure the service is enabled for Ingress to route traffic
 ingress:
@@ -234,8 +231,7 @@ ingress:
         - "homarr.homelab.dev"
         - "www.homarr.homelab.dev"
       secretName: homelab-tls
-```
-
+````
 </details>
 
 ### HTTPRoute (Gateway API)
@@ -246,9 +242,9 @@ This provides a more expressive and future-proof alternative to Ingress, with su
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 service:
-  enabled: true # must be enabled for HTTPRoute to forward traffic
+  enabled: true  # must be enabled for HTTPRoute to forward traffic
 httproute:
   enabled: true
   parentRefs:
@@ -264,15 +260,14 @@ httproute:
       backendRefs:
         - name: homarr
           port: 7575
-```
-
+````
 </details>
 
 #### Notes:
 
 - parentRefs: the Gateway(s) this route attaches to. Gateways must already exist.
 - hostnames: domain names this route applies to.
-- rules: each rule can define matches (paths, headers, queries), optional filters, and backendRefs to services
+- rules:  each rule can define matches (paths, headers, queries), optional filters, and backendRefs to services
 - TLS must be configured on the Gateway (not on HTTPRoute). For example, the Gateway can have a TLS listener for homarr.homelab.dev, and this route will automatically apply once matched.
 
 ### Certificates
@@ -289,7 +284,7 @@ Use inline certificates to generate a ConfigMap, mounted as individual files.
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrTrustedCerts:
     enabled: true
@@ -303,8 +298,7 @@ persistence:
         -----BEGIN CERTIFICATE-----
         MIID...EFGH==
         -----END CERTIFICATE-----
-```
-
+````
 </details>
 
 Behavior:
@@ -319,7 +313,7 @@ Use inline certificates to generate a Kubernetes Secret, mounted as files.
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrTrustedCerts:
     enabled: true
@@ -333,8 +327,7 @@ persistence:
         -----BEGIN CERTIFICATE-----
         MIIC...XYZ==
         -----END CERTIFICATE-----
-```
-
+````
 </details>
 
 Behavior:
@@ -349,17 +342,16 @@ Use an existing Kubernetes Secret, assuming its keys are filenames.
 <details>
 <summary>values.yaml</summary>
 
-```yaml
+````yaml
 persistence:
   homarrTrustedCerts:
     enabled: true
     type: existingSecret
     existingSecretName: "existingSecretName"
     existingSecretKeys:
-      - cert3.crt
-      - cert4.crt
-```
-
+        - cert3.crt
+        - cert4.crt
+````
 </details>
 
 Behavior:
@@ -380,115 +372,114 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 
 ## Values
 
-| Key                                                | Type   | Default                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| -------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| additionalObjects                                  | list   | `[]`                                                                                                                                                                                                                                             | Additional resources to deploy. These objects are templated.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| affinity                                           | object | `{}`                                                                                                                                                                                                                                             | Node affinity for pod scheduling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| autoscaling.enabled                                | bool   | `false`                                                                                                                                                                                                                                          | Enable autoscaling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| autoscaling.maxReplicas                            | int    | `100`                                                                                                                                                                                                                                            | Maximum replicas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| autoscaling.minReplicas                            | int    | `1`                                                                                                                                                                                                                                              | Minimum replicas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| autoscaling.targetCPUUtilizationPercentage         | int    | `80`                                                                                                                                                                                                                                             | Target CPU utilization for autoscaling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| containerPorts                                     | object | `{"http":{"port":7575,"protocol":"TCP"}}`                                                                                                                                                                                                        | containerPorts defines the ports to open on the container. It is a map where each entry specifies: - `port` (int) (required): The port number to expose inside the container. - `protocol` (string) (required): The network protocol (TCP or UDP) used for the port. - `disabled` (bool) : Optional flag to disable this port (defaults to false). Can be overridden via Helm values. By default, this configuration exposes TCP port 7575 with the name `http`.                                                                                         |
-| database.migrationEnabled                          | bool   | `true`                                                                                                                                                                                                                                           | Database migration configuration. DB_MIGRATIONS_DISABLED Set to `true` to disable database migrations. Migrations are enabled by default (`false`).                                                                                                                                                                                                                                                                                                                                                                                                      |
-| database.type                                      | string | `"sqlite"`                                                                                                                                                                                                                                       | Database type: sqlite, mysql or postgresql                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| env.AUTH_COOKIE_PREFIX                             | string | `"homarr"`                                                                                                                                                                                                                                       | Prefix used for all authentication cookies. Change if you run another Auth.js/NextAuth app on the same hostname to avoid cookie name collisions. Only letters, numbers, hyphens and underscores.                                                                                                                                                                                                                                                                                                                                                         |
-| env.AUTH_LDAP_BASE                                 | string | `nil`                                                                                                                                                                                                                                            | Base dn of your LDAP server                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| env.AUTH_LDAP_BIND_DN                              | string | `nil`                                                                                                                                                                                                                                            | User used for finding users and groups                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| env.AUTH_LDAP_GROUP_CLASS                          | string | `"groupOfUniqueNames"`                                                                                                                                                                                                                           | Class used for querying groups                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| env.AUTH_LDAP_GROUP_FILTER_EXTRA_ARG               | string | `nil`                                                                                                                                                                                                                                            | Extra arguments for user's groups search filter (& based)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| env.AUTH_LDAP_GROUP_MEMBER_ATTRIBUTE               | string | `"member"`                                                                                                                                                                                                                                       | Attribute used for querying group member                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| env.AUTH_LDAP_GROUP_MEMBER_USER_ATTRIBUTE          | string | `"dn"`                                                                                                                                                                                                                                           | User attribute used for comparing with group member                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| env.AUTH_LDAP_SEARCH_SCOPE                         | string | `"base"`                                                                                                                                                                                                                                         | LDAP search scope between base, one or sub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| env.AUTH_LDAP_URI                                  | string | `nil`                                                                                                                                                                                                                                            | URI of your LDAP server                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| env.AUTH_LDAP_USERNAME_ATTRIBUTE                   | string | `"uid"`                                                                                                                                                                                                                                          | Attribute used for username                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| env.AUTH_LDAP_USERNAME_FILTER_EXTRA_ARG            | string | `nil`                                                                                                                                                                                                                                            | Extra arguments for user search filter (& based)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| env.AUTH_LDAP_USER_MAIL_ATTRIBUTE                  | string | `"mail"`                                                                                                                                                                                                                                         | Attribute used for mail field                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| env.AUTH_LOGOUT_REDIRECT_URL                       | string | `nil`                                                                                                                                                                                                                                            | URL to redirect to after clicking logging out.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| env.AUTH_OIDC_AUTO_LOGIN                           | string | `"false"`                                                                                                                                                                                                                                        | Automatically redirect to OIDC login                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| env.AUTH_OIDC_CLIENT_NAME                          | string | `"OIDC"`                                                                                                                                                                                                                                         | Display name of provider (in login screen)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| env.AUTH_OIDC_GROUPS_ATTRIBUTE                     | string | `"groups"`                                                                                                                                                                                                                                       | Attribute used for groups (roles) claim                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| env.AUTH_OIDC_ISSUER                               | string | `nil`                                                                                                                                                                                                                                            | Issuer URI of OIDC provider without trailing slash (/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| env.AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE             | string | `nil`                                                                                                                                                                                                                                            | Overwrite name attribute. By default, it will use preferred_username if it does not contain a @ and otherwise name.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| env.AUTH_OIDC_SCOPE_OVERWRITE                      | string | `"openid email profile groups"`                                                                                                                                                                                                                  | Override the OIDC scopes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| env.AUTH_PROVIDERS                                 | string | `"credentials"`                                                                                                                                                                                                                                  | Enabled authentication methods. Multiple providers can be enabled with by separating them with , (ex. AUTH_PROVIDERS=credentials,oidc, it is highly recommended to just enable one provider).                                                                                                                                                                                                                                                                                                                                                            |
-| env.AUTH_SESSION_EXPIRY_TIME                       | string | `"30d"`                                                                                                                                                                                                                                          | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m")                                                                                                                                                                                                                                                                                                                                                                   |
-| env.ENABLE_DNS_CACHING                             | string | `"false"`                                                                                                                                                                                                                                        | Enables dns caching. This is not yet working for all users. See #4006                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| env.LOG_LEVEL                                      | string | `"info"`                                                                                                                                                                                                                                         | Log level to use. Possible values: debug/info/warn/error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| env.NO_EXTERNAL_CONNECTION                         | string | `"false"`                                                                                                                                                                                                                                        | Disables some requests that need internet connection                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| env.TZ                                             | string | `"Europe/Paris"`                                                                                                                                                                                                                                 | Your local time zone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| envSecrets.authLdapCredentials.existingSecret      | string | `"auth-ldap-secret"`                                                                                                                                                                                                                             | Name of existing secret containing LDAP credentials                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| envSecrets.authLdapCredentials.ldapBindingPassword | string | `"bind-password"`                                                                                                                                                                                                                                | Password for bind user secret key                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| envSecrets.authOidcCredentials.existingSecret      | string | `"auth-oidc-secret"`                                                                                                                                                                                                                             | Name of existing secret containing OIDC credentials                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| envSecrets.authOidcCredentials.oidcClientId        | string | `"oidc-client-id"`                                                                                                                                                                                                                               | ID of OIDC client (application) secret key                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| envSecrets.authOidcCredentials.oidcClientSecret    | string | `"oidc-client-secret"`                                                                                                                                                                                                                           | Secret of OIDC client (application) secret key                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| envSecrets.dbCredentials.dbUrlKey                  | string | `"db-url"`                                                                                                                                                                                                                                       | Secret key for DB_URL Example for external database: `mysql://username:password@host:port/homarrdb` or `postgresql://username:password@host:port/homarrdb`                                                                                                                                                                                                                                                                                                                                                                                               |
-| envSecrets.dbCredentials.existingSecret            | string | `"db-secret"`                                                                                                                                                                                                                                    | Name of existing secret containing DB credentials                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| envSecrets.dbEncryption.existingSecret             | string | `"db-encryption"`                                                                                                                                                                                                                                | Name of existing secret containing DB encryption                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| envSecrets.dbEncryption.key                        | string | `"db-encryption-key"`                                                                                                                                                                                                                            | Secret key for SECRET_ENCRYPTION_KEY can be generated with `openssl rand -hex 32`                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| fullnameOverride                                   | string | `""`                                                                                                                                                                                                                                             | Overrides chart's fullname                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| hostAliases                                        | list   | `[]`                                                                                                                                                                                                                                             | Add static entries to /etc/hosts in the Pod. This is useful in the following cases: - You are running in a dual-stack cluster (IPv4 + IPv6) and want to force usage of IPv4 for specific hostnames - Your application is having DNS resolution issues or IPv6 preference issues - You need to override or simulate DNS entries without changing global DNS - You are running in an air-gapped or isolated environment without external DNS Example: hostAliases: - ip: "192.168.1.10" hostnames: - "example.com" - "example.internal"                    |
-| httproute                                          | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| httproute.enabled                                  | bool   | `false`                                                                                                                                                                                                                                          | Enable HTTPRoute                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| httproute.hostnames                                | list   | `["chart-example.local"]`                                                                                                                                                                                                                        | Hostnames this route matches (similar to ingress.hosts.host)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| httproute.parentRefs                               | list   | `[{"name":"my-gateway","namespace":"default"}]`                                                                                                                                                                                                  | References to the parent Gateway(s) this route attaches to. Each item must include at least a `name`, and optionally a `namespace`.                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| httproute.rules                                    | list   | `[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]`                                                                                                                          | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to                                                                                                                                                                                                                                                                                                                     |
-| httproute.rules[0].filters                         | list   | `[]`                                                                                                                                                                                                                                             | Optional filters for this rule (default: empty)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| httproute.rules[0].matches[0].path.type            | string | `"PathPrefix"`                                                                                                                                                                                                                                   | Path match type. One of: Exact, PathPrefix, RegularExpression                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| 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.74.0"`                                                                                                                                                                                                                                      | 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ingress.hosts                                      | list   | `[{"host":"chart-example.local","paths":[{"path":"/"}]}]`                                                                                                                                                                                        | Ingress hosts configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ingress.ingressClassName                           | string | `""`                                                                                                                                                                                                                                             | Ingress class name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| ingress.tls                                        | list   | `[]`                                                                                                                                                                                                                                             | Ingress TLS configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| livenessProbe.failureThreshold                     | int    | `3`                                                                                                                                                                                                                                              | Failure threshold for liveness probe - number of consecutive failures before pod is restarted                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| livenessProbe.httpGet.path                         | string | `"/api/health/live"`                                                                                                                                                                                                                             | This is the liveness check endpoint used by Kubernetes to determine if the application is still running.                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| livenessProbe.httpGet.port                         | int    | `7575`                                                                                                                                                                                                                                           | The port on which the liveness check will be performed. This must be the same as the container port exposed by the application.                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| livenessProbe.initialDelaySeconds                  | int    | `10`                                                                                                                                                                                                                                             | Initial delay in seconds before the liveness probe starts                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| livenessProbe.periodSeconds                        | int    | `10`                                                                                                                                                                                                                                             | Period in seconds between liveness probe checks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| livenessProbe.timeoutSeconds                       | int    | `1`                                                                                                                                                                                                                                              | Timeout in seconds for each liveness probe check                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| nameOverride                                       | string | `""`                                                                                                                                                                                                                                             | Overrides chart's name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| nodeSelector                                       | object | `{}`                                                                                                                                                                                                                                             | Node selectors for pod scheduling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| persistence.homarrDatabase.accessMode              | string | `"ReadWriteOnce"`                                                                                                                                                                                                                                | homarr-database access mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| persistence.homarrDatabase.enabled                 | bool   | `false`                                                                                                                                                                                                                                          | Enable homarr-database persistent storage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| persistence.homarrDatabase.mountPath               | string | `"/appdata"`                                                                                                                                                                                                                                     | homarr-database mount path inside the pod                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| persistence.homarrDatabase.name                    | string | `"homarr-database"`                                                                                                                                                                                                                              | homarr-database persistent storage name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| persistence.homarrDatabase.size                    | string | `"50Mi"`                                                                                                                                                                                                                                         | homarr-database storage size                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| persistence.homarrDatabase.storageClassName        | string | `"local-path"`                                                                                                                                                                                                                                   | homarr-database storage class name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| persistence.homarrDatabase.volumeClaimName         | string | `""`                                                                                                                                                                                                                                             | homarr-database optional volumeClaimName to target specific PV                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| persistence.homarrTrustedCerts.certificates        | string | `nil`                                                                                                                                                                                                                                            | homarr-trusted-certificates certificates, each entry will become a new trusted certificate as a dedicated file (works only for "configmap" and "secret" mode)                                                                                                                                                                                                                                                                                                                                                                                            |
-| persistence.homarrTrustedCerts.enabled             | bool   | `false`                                                                                                                                                                                                                                          | Enable trusted certificates persistence                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| persistence.homarrTrustedCerts.existingSecretKeys  | string | `nil`                                                                                                                                                                                                                                            | List of keys (filenames) to mount from the existing secret (used only when type is "existingSecret")                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| persistence.homarrTrustedCerts.existingSecretName  | string | `""`                                                                                                                                                                                                                                             | Name of the existing Kubernetes Secret to mount (required if type is "existingSecret")                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| persistence.homarrTrustedCerts.mountPath           | string | `"/appdata/trusted-certificates"`                                                                                                                                                                                                                | homarr-trusted-certificates mount path inside the pod                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| persistence.homarrTrustedCerts.type                | string | `"configmap"`                                                                                                                                                                                                                                    | Persistence mode can be : configmap (declarative), secret (declarative) or existingSecret (mount an existing Kubernetes Secret by name and specify which keys to mount as files)                                                                                                                                                                                                                                                                                                                                                                         |
-| podAnnotations                                     | object | `{}`                                                                                                                                                                                                                                             | Pod annotations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| podLabels                                          | object | `{}`                                                                                                                                                                                                                                             | Pod labels                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| podSecurityContext                                 | object | `{}`                                                                                                                                                                                                                                             | Pod security context                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| rbac                                               | object | `{"enabled":false}`                                                                                                                                                                                                                              | Enable RBAC resources for Kubernetes integration Creates Role, ClusterRole, and associated bindings for Homarr's Kubernetes features                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| rbac.enabled                                       | bool   | `false`                                                                                                                                                                                                                                          | Enable to create RBAC resources and activate Kubernetes integration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| readinessProbe.failureThreshold                    | int    | `3`                                                                                                                                                                                                                                              | Failure threshold for readiness probe - number of consecutive failures before pod is considered unready                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| readinessProbe.httpGet.path                        | string | `"/api/health/ready"`                                                                                                                                                                                                                            | This is the readiness check endpoint used by Kubernetes to determine if the application is ready to handle traffic.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| readinessProbe.httpGet.port                        | int    | `7575`                                                                                                                                                                                                                                           | The port on which the readiness check will be performed. This must match the container's exposed port.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| readinessProbe.initialDelaySeconds                 | int    | `10`                                                                                                                                                                                                                                             | Initial delay in seconds before the readiness probe starts. increase this value if the pod is slow to fully start.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| readinessProbe.periodSeconds                       | int    | `10`                                                                                                                                                                                                                                             | Period in seconds between readiness probe checks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| readinessProbe.timeoutSeconds                      | int    | `1`                                                                                                                                                                                                                                              | Timeout in seconds for each readiness probe check                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| replicaCount                                       | int    | `1`                                                                                                                                                                                                                                              | Number of replicas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| resources                                          | object | `{}`                                                                                                                                                                                                                                             | Resource configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| securityContext                                    | object | `{}`                                                                                                                                                                                                                                             | Security context                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| service.enabled                                    | bool   | `true`                                                                                                                                                                                                                                           | Enable service                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| service.ipFamilies                                 | list   | `[]`                                                                                                                                                                                                                                             | List of IP families to use for the service. Examples: - ["IPv4"] - ["IPv6"] - ["IPv4", "IPv6"] for dual-stack Leave empty to use cluster default behavior                                                                                                                                                                                                                                                                                                                                                                                                |
-| service.ipFamilyPolicy                             | string | `"SingleStack"`                                                                                                                                                                                                                                  | Defines how the service assigns IP families (IPv4/IPv6) Possible values: - SingleStack (default): Only one IP family, usually IPv4 - PreferDualStack: Use dual-stack if the cluster supports it, fallback to single - RequireDualStack: Fail if dual-stack cannot be assigned                                                                                                                                                                                                                                                                            |
-| service.ports.app.port                             | int    | `7575`                                                                                                                                                                                                                                           | Service port                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| service.ports.app.protocol                         | string | `"TCP"`                                                                                                                                                                                                                                          | Service protocol                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| service.ports.app.targetPort                       | string | `"http"`                                                                                                                                                                                                                                         | Service target port                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| service.type                                       | string | `"ClusterIP"`                                                                                                                                                                                                                                    | Service type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| strategyType                                       | string | `"RollingUpdate"`                                                                                                                                                                                                                                | `strategyType` specifies the strategy used to replace old Pods by new ones. `strategyType` can be `"Recreate"` or `"RollingUpdate"`. `"RollingUpdate"` is the default value and updates Pods in a rolling update fashion. `"Recreate"` will kill all existing Pods before new ones are created. The `"Recreate"` strategy is necessary when persistent volume's `accessMode` is set to `"ReadWriteOnce"` when using `helm upgrade`, as pod volume attachments to an existing PersistentVolumeClaim need to be cleared before a new pod can attach to it. |
-| tolerations                                        | list   | `[]`                                                                                                                                                                                                                                             | Node tolerations for pod scheduling                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Key | Type | Default | Description |
+|-----|------|---------|-------------|
+| additionalObjects | list | `[]` | Additional resources to deploy. These objects are templated. |
+| affinity | object | `{}` | Node affinity for pod scheduling |
+| autoscaling.enabled | bool | `false` | Enable autoscaling |
+| autoscaling.maxReplicas | int | `100` | Maximum replicas |
+| autoscaling.minReplicas | int | `1` | Minimum replicas |
+| autoscaling.targetCPUUtilizationPercentage | int | `80` | Target CPU utilization for autoscaling |
+| containerPorts | object | `{"http":{"port":7575,"protocol":"TCP"}}` | containerPorts defines the ports to open on the container. It is a map where each entry specifies:    - `port`     (int)    (required): The port number to expose inside the container.    - `protocol` (string) (required): The network protocol (TCP or UDP) used for the port.    - `disabled` (bool)              : Optional flag to disable this port (defaults to false). Can be overridden via Helm values.  By default, this configuration exposes TCP port 7575 with the name `http`. |
+| database.migrationEnabled | bool | `true` | Database migration configuration. DB_MIGRATIONS_DISABLED Set to `true` to disable database migrations. Migrations are enabled by default (`false`). |
+| database.type | string | `"sqlite"` | Database type: sqlite, mysql or postgresql |
+| env.AUTH_COOKIE_PREFIX | string | `"homarr"` | Prefix used for all authentication cookies. Change if you run another Auth.js/NextAuth app on the same hostname to avoid cookie name collisions. Only letters, numbers, hyphens and underscores. |
+| env.AUTH_LDAP_BASE | string | `nil` | Base dn of your LDAP server |
+| env.AUTH_LDAP_BIND_DN | string | `nil` | User used for finding users and groups |
+| env.AUTH_LDAP_GROUP_CLASS | string | `"groupOfUniqueNames"` | Class used for querying groups |
+| env.AUTH_LDAP_GROUP_FILTER_EXTRA_ARG | string | `nil` | Extra arguments for user's groups search filter (& based) |
+| env.AUTH_LDAP_GROUP_MEMBER_ATTRIBUTE | string | `"member"` | Attribute used for querying group member |
+| env.AUTH_LDAP_GROUP_MEMBER_USER_ATTRIBUTE | string | `"dn"` | User attribute used for comparing with group member |
+| env.AUTH_LDAP_SEARCH_SCOPE | string | `"base"` | LDAP search scope between base, one or sub |
+| env.AUTH_LDAP_URI | string | `nil` | URI of your LDAP server |
+| env.AUTH_LDAP_USERNAME_ATTRIBUTE | string | `"uid"` | Attribute used for username |
+| env.AUTH_LDAP_USERNAME_FILTER_EXTRA_ARG | string | `nil` | Extra arguments for user search filter (& based) |
+| env.AUTH_LDAP_USER_MAIL_ATTRIBUTE | string | `"mail"` | Attribute used for mail field |
+| env.AUTH_LOGOUT_REDIRECT_URL | string | `nil` | URL to redirect to after clicking logging out. |
+| env.AUTH_OIDC_AUTO_LOGIN | string | `"false"` | Automatically redirect to OIDC login |
+| env.AUTH_OIDC_CLIENT_NAME | string | `"OIDC"` | Display name of provider (in login screen) |
+| env.AUTH_OIDC_GROUPS_ATTRIBUTE | string | `"groups"` | Attribute used for groups (roles) claim |
+| env.AUTH_OIDC_ISSUER | string | `nil` | Issuer URI of OIDC provider without trailing slash (/) |
+| env.AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE | string | `nil` | Overwrite name attribute. By default, it will use preferred_username if it does not contain a @ and otherwise name. |
+| env.AUTH_OIDC_SCOPE_OVERWRITE | string | `"openid email profile groups"` | Override the OIDC scopes |
+| env.AUTH_PROVIDERS | string | `"credentials"` | Enabled authentication methods. Multiple providers can be enabled with by separating them with , (ex. AUTH_PROVIDERS=credentials,oidc, it is highly recommended to just enable one provider). |
+| env.AUTH_SESSION_EXPIRY_TIME | string | `"30d"` | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m") |
+| env.ENABLE_DNS_CACHING | string | `"false"` | Enables dns caching. This is not yet working for all users. See #4006 |
+| env.LOG_LEVEL | string | `"info"` | Log level to use. Possible values: debug/info/warn/error |
+| env.NO_EXTERNAL_CONNECTION | string | `"false"` | Disables some requests that need internet connection |
+| env.TZ | string | `"Europe/Paris"` | Your local time zone |
+| envSecrets.authLdapCredentials.existingSecret | string | `"auth-ldap-secret"` | Name of existing secret containing LDAP credentials |
+| envSecrets.authLdapCredentials.ldapBindingPassword | string | `"bind-password"` | Password for bind user secret key |
+| envSecrets.authOidcCredentials.existingSecret | string | `"auth-oidc-secret"` | Name of existing secret containing OIDC credentials |
+| envSecrets.authOidcCredentials.oidcClientId | string | `"oidc-client-id"` | ID of OIDC client (application) secret key |
+| envSecrets.authOidcCredentials.oidcClientSecret | string | `"oidc-client-secret"` | Secret of OIDC client (application) secret key |
+| envSecrets.dbCredentials.dbUrlKey | string | `"db-url"` | Secret key for DB_URL Example for external database: `mysql://username:password@host:port/homarrdb` or `postgresql://username:password@host:port/homarrdb` |
+| envSecrets.dbCredentials.existingSecret | string | `"db-secret"` | Name of existing secret containing DB credentials |
+| envSecrets.dbEncryption.existingSecret | string | `"db-encryption"` | Name of existing secret containing DB encryption |
+| envSecrets.dbEncryption.key | string | `"db-encryption-key"` | Secret key for SECRET_ENCRYPTION_KEY can be generated with `openssl rand -hex 32` |
+| fullnameOverride | string | `""` | Overrides chart's fullname |
+| hostAliases | list | `[]` | Add static entries to /etc/hosts in the Pod. This is useful in the following cases: - You are running in a dual-stack cluster (IPv4 + IPv6) and want to force usage of IPv4 for specific hostnames - Your application is having DNS resolution issues or IPv6 preference issues - You need to override or simulate DNS entries without changing global DNS - You are running in an air-gapped or isolated environment without external DNS Example: hostAliases:   - ip: "192.168.1.10"     hostnames:       - "example.com"       - "example.internal" |
+| httproute | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration |
+| httproute.enabled | bool | `false` | Enable HTTPRoute |
+| httproute.hostnames | list | `["chart-example.local"]` | Hostnames this route matches (similar to ingress.hosts.host) |
+| httproute.parentRefs | list | `[{"name":"my-gateway","namespace":"default"}]` | References to the parent Gateway(s) this route attaches to. Each item must include at least a `name`, and optionally a `namespace`. |
+| httproute.rules | list | `[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]` | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to |
+| httproute.rules[0].filters | list | `[]` | Optional filters for this rule (default: empty) |
+| httproute.rules[0].matches[0].path.type | string | `"PathPrefix"` | Path match type. One of: Exact, PathPrefix, RegularExpression |
+| 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.74.0"` | 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 |
+| ingress.hosts | list | `[{"host":"chart-example.local","paths":[{"path":"/"}]}]` | Ingress hosts configuration |
+| ingress.ingressClassName | string | `""` | Ingress class name |
+| ingress.tls | list | `[]` | Ingress TLS configuration |
+| livenessProbe.failureThreshold | int | `3` | Failure threshold for liveness probe - number of consecutive failures before pod is restarted |
+| livenessProbe.httpGet.path | string | `"/api/health/live"` | This is the liveness check endpoint used by Kubernetes to determine if the application is still running. |
+| livenessProbe.httpGet.port | int | `7575` | The port on which the liveness check will be performed. This must be the same as the container port exposed by the application. |
+| livenessProbe.initialDelaySeconds | int | `10` | Initial delay in seconds before the liveness probe starts |
+| livenessProbe.periodSeconds | int | `10` | Period in seconds between liveness probe checks |
+| livenessProbe.timeoutSeconds | int | `1` | Timeout in seconds for each liveness probe check |
+| nameOverride | string | `""` | Overrides chart's name |
+| nodeSelector | object | `{}` | Node selectors for pod scheduling |
+| persistence.homarrDatabase.accessMode | string | `"ReadWriteOnce"` | homarr-database access mode |
+| persistence.homarrDatabase.enabled | bool | `false` | Enable homarr-database persistent storage |
+| persistence.homarrDatabase.mountPath | string | `"/appdata"` | homarr-database mount path inside the pod |
+| persistence.homarrDatabase.name | string | `"homarr-database"` | homarr-database persistent storage name |
+| persistence.homarrDatabase.size | string | `"50Mi"` | homarr-database storage size |
+| persistence.homarrDatabase.storageClassName | string | `"local-path"` | homarr-database storage class name |
+| persistence.homarrDatabase.volumeClaimName | string | `""` | homarr-database optional volumeClaimName to target specific PV |
+| persistence.homarrTrustedCerts.certificates | string | `nil` | homarr-trusted-certificates certificates, each entry will become a new trusted certificate as a dedicated file (works only for "configmap" and "secret" mode) |
+| persistence.homarrTrustedCerts.enabled | bool | `false` | Enable trusted certificates persistence |
+| persistence.homarrTrustedCerts.existingSecretKeys | string | `nil` | List of keys (filenames) to mount from the existing secret (used only when type is "existingSecret") |
+| persistence.homarrTrustedCerts.existingSecretName | string | `""` | Name of the existing Kubernetes Secret to mount (required if type is "existingSecret") |
+| persistence.homarrTrustedCerts.mountPath | string | `"/appdata/trusted-certificates"` | homarr-trusted-certificates  mount path inside the pod |
+| persistence.homarrTrustedCerts.type | string | `"configmap"` | Persistence mode can be : configmap (declarative), secret (declarative) or existingSecret (mount an existing Kubernetes Secret by name and specify which keys to mount as files) |
+| podAnnotations | object | `{}` | Pod annotations |
+| podLabels | object | `{}` | Pod labels |
+| podSecurityContext | object | `{}` | Pod security context |
+| rbac | object | `{"enabled":false}` | Enable RBAC resources for Kubernetes integration Creates Role, ClusterRole, and associated bindings for Homarr's Kubernetes features |
+| rbac.enabled | bool | `false` | Enable to create RBAC resources and activate Kubernetes integration |
+| readinessProbe.failureThreshold | int | `3` | Failure threshold for readiness probe - number of consecutive failures before pod is considered unready |
+| readinessProbe.httpGet.path | string | `"/api/health/ready"` | This is the readiness check endpoint used by Kubernetes to determine if the application is ready to handle traffic. |
+| readinessProbe.httpGet.port | int | `7575` | The port on which the readiness check will be performed. This must match the container's exposed port. |
+| readinessProbe.initialDelaySeconds | int | `10` | Initial delay in seconds before the readiness probe starts. increase this value if the pod is slow to fully start. |
+| readinessProbe.periodSeconds | int | `10` | Period in seconds between readiness probe checks |
+| readinessProbe.timeoutSeconds | int | `1` | Timeout in seconds for each readiness probe check |
+| replicaCount | int | `1` | Number of replicas |
+| resources | object | `{}` | Resource configuration |
+| securityContext | object | `{}` | Security context |
+| service.enabled | bool | `true` | Enable service |
+| service.ipFamilies | list | `[]` | List of IP families to use for the service. Examples: - ["IPv4"] - ["IPv6"] - ["IPv4", "IPv6"] for dual-stack Leave empty to use cluster default behavior |
+| service.ipFamilyPolicy | string | `"SingleStack"` | Defines how the service assigns IP families (IPv4/IPv6) Possible values: - SingleStack (default): Only one IP family, usually IPv4 - PreferDualStack: Use dual-stack if the cluster supports it, fallback to single - RequireDualStack: Fail if dual-stack cannot be assigned |
+| service.ports.app.port | int | `7575` | Service port |
+| service.ports.app.protocol | string | `"TCP"` | Service protocol |
+| service.ports.app.targetPort | string | `"http"` | Service target port |
+| service.type | string | `"ClusterIP"` | Service type |
+| strategyType | string | `"RollingUpdate"` | `strategyType` specifies the strategy used to replace old Pods by new ones. `strategyType` can be `"Recreate"` or `"RollingUpdate"`. `"RollingUpdate"` is the default value and updates Pods in a rolling update fashion. `"Recreate"` will kill all existing Pods before new ones are created. The `"Recreate"` strategy is necessary when persistent volume's `accessMode` is set to `"ReadWriteOnce"` when using `helm upgrade`, as pod volume attachments to an existing PersistentVolumeClaim need to be cleared before a new pod can attach to it. |
+| tolerations | list | `[]` | Node tolerations for pod scheduling |
 
 ---
-
 Autogenerated from chart metadata using [helm-docs](https://github.com/norwoodj/helm-docs)

apps/docs/docs/getting-started/installation/home-assistant.mdx

@@ -14,7 +14,7 @@ Homarr can be seamlessly integrated into your Home Assistant setup with this add
 ## Installation
 
 1. **Add Repository**: Navigate to your Home Assistant Supervisor panel, and go to the Add-on Store. Add the following repository URL: `https://github.com/Wiggen94/ha-homarr-v1-server` or click this button
-   [![Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2FWiggen94%2Fha-homarr-v1-server)
+[![Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2FWiggen94%2Fha-homarr-v1-server)
 
 2. **Install the Add-on**: Search for "Homarr Server" in the Add-on Store and select it. Click on "Install" to start the installation process.
 

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

@@ -1,7 +1,5 @@
 # Portainer
-
 ## Portainer Stacks
-
 ### Prerequisites
 
 - [Portainer Stacks](https://www.portainer.io/blog/stacks-docker-compose-the-portainer-way)
@@ -25,14 +23,15 @@ services:
     environment:
       - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
+
 :::note
-Portainer will mount the files to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
+Portainer will mount the files to your host machine. Please make sure to replace ``<your-path>`` from the docker run command with your desired storage location. The path must be absolute.
 :::
 
-Then, click on `Deploy the stack` and wait until the container has started.
+Then, click on ``Deploy the stack`` and wait until the container has started.
 
 :::tip
 
@@ -44,5 +43,5 @@ If you're unsure how to create a stack, checkout the [Portainer Documentation](h
 
 To update Homarr using Docker Compose or Portainer Stacks, simply pull the latest image and restart the container.
 
-1. Run `docker pull ghcr.io/homarr-labs/homarr:latest` to pull the latest image.
-2. Re-run `docker-compose up -d` or re-deploy the stack in Portainer.
+1. Run ``docker pull ghcr.io/homarr-labs/homarr:latest`` to pull the latest image.
+2. Re-run ``docker-compose up -d`` or re-deploy the stack in Portainer.

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

@@ -31,7 +31,7 @@ After you've installed Homarr, you can find a new LXC "homarr".
 
 # Updating
 
-Updating is as simple as executing
+Updating is as simple as executing 
 
 ```bash
 update
@@ -49,19 +49,17 @@ Some Homarr features require setting environment variables. When installing Homa
 
 # Troubleshooting
 
-If something does not work after an update, please first try rebooting the LXC or the homarr Service with
+If something does not work after an update, please first try rebooting the LXC or the homarr Service with 
 
 ```bash
 systemctl restart homarr
 ```
 
 # Getting help
-
 - If you are looking for help with the script, updating the LXC or troubleshooting the installer, please get in contact with the support of the community scripts. They provide support on their [Discord](https://discord.gg/2wvnMDgdnU). If you found vulnerabilities, bugs or have a request for the script, [create a new issue here](https://github.com/community-scripts/ProxmoxVE/issues/new/choose).
 - If you are looking to report a bug, vulnerability or request a new feature, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.
 
 # How to find logs
-
 Homarr runs under a system service called `homarr`, so getting the logs is a simple as using the following command inside the LXC (Container) Shell
 
 ```bash

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

@@ -4,6 +4,6 @@
 QNAP installation guide has not updated to 1.0 yet. There guide is still for 0.15.10.
 :::
 
-When installing on QNAP, we recommend you to install Homarr using [Container Station](https://www.qnap.com/en/software/container-station) or [this third-party image](https://www.myqnap.org/product/homarr/).
+When installing on QNAP, we recommend you to install Homarr using [Container Station]( https://www.qnap.com/en/software/container-station) or [this third-party image](https://www.myqnap.org/product/homarr/).
 
 There is also a guide available, but note that it is written in Chinese: https://post.smzdm.com/p/awzm7op2/

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

@@ -1,4 +1,4 @@
-# Runtipi
+#  Runtipi
 
 Runtipi is a self-hosted orchestrator that makes it easy to manage and run multiple services on a single server. It is based on Docker and comes with a simple web interface to manage your services. Runtipi is designed to be easy to use, so you don't have to worry about manual configuration or networking.
 
@@ -11,7 +11,6 @@ https://runtipi.io
 # Installation
 
 Installing Homarr is pretty untuitive, the app is available in the default appstore :
-
 1. Search for **"Homarr"** in the App-Store page and select it
 2. Click on **"Install"**.
 3. Choose the method you want to access Homarr, through any port or domain name then select **"Install"**
@@ -19,15 +18,13 @@ Installing Homarr is pretty untuitive, the app is available in the default appst
 # Maintenance
 
 After installation, all you need is available from the WebUI in **"My apps"** > **"Homarr"** :
-
-- Start/Stop
-- Update
-- Backup
-- Logs
-
+ - Start/Stop
+ - Update
+ - Backup
+ - Logs
+ 
 If you like to tinker with your apps, you can also edit your app's docker-compose with a [user-config](https://runtipi.io/docs/guides/customize-app-config).
 
 # Getting help
-
 - If you are looking for help with anything in Runtipi. They provide support on their [Discord](https://discord.gg/Bu9qEPnHsc) and [forums](https://forums.runtipi.io/). If you found vulnerabilities or bugs, [create a new issue here](https://github.com/runtipi/runtipi-appstore/issues).
-- If you are looking to report a bug, vulnerability or request a new feature for Homarr, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.
+- If you are looking to report a bug, vulnerability or request a new feature for Homarr, use https://github.com/homarr-labs/homarr . You can ask for help on our Discord.

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

@@ -5,7 +5,6 @@ Saltbox installation command has not updated to 1.0 yet. There command still run
 :::
 
 You can also use this to install on Saltbox:
-
 ```bash
 sb install sandbox-homarr
-```
+```

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

@@ -28,29 +28,15 @@ This method is only useful, when you want to develop on Homarr or extend it with
 ## Steps
 
 <ol>
-  <li>
-    Clone the Repository using <code>git clone https://github.com/homarr-labs/homarr.git</code>
-  </li>
-  <li>
-    Enter the created directory using <code>cd homarr</code>
-  </li>
-  <li>
-    Install all dependencies using <code>pnpm install</code>
-  </li>
-  <li>
-    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>
-    Replace `AUTH_SECRET` and `SECRET_ENCRYPTION_KEY` both with a secure random string by using `openssl rand -hex 32`
-  </li>
+  <li>Clone the Repository using <code>git clone https://github.com/homarr-labs/homarr.git</code></li>
+  <li>Enter the created directory using <code>cd homarr</code></li>
+  <li>Install all dependencies using <code>pnpm install</code></li>
+  <li>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>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>
-    Copy better-sqlite3.node files with `mkdir build` and `cp
-    ./node_modules/better-sqlite3/build/Release/better_sqlite3.node ./build/better_sqlite3.node`
-  </li>
+  <li>Copy better-sqlite3.node files with `mkdir build` and `cp ./node_modules/better-sqlite3/build/Release/better_sqlite3.node ./build/better_sqlite3.node`</li>
   <li>Start a redis server using `redis-server`</li>
   <li>Run the server using `pnpm start`</li>
   <li>Open `http://localhost:3000` in your browser</li>

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

@@ -1,5 +1,5 @@
-import Link from "@docusaurus/Link";
-import { IconDownload } from "@tabler/icons-react";
+import Link from '@docusaurus/Link';
+import { IconDownload } from '@tabler/icons-react';
 
 # Unraid
 
@@ -14,17 +14,17 @@ You can install Homarr directly from your Unraid Dashboard, no terminal required
 
 <Link
   data-attr="Install Unraid Community Apps"
-  className={"button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800"}
+  className={'button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800'}
   to="https://forums.unraid.net/topic/38582-plug-in-community-applications/"
 >
-  <div className={"flex items-center gap-3"}>
+  <div className={'flex items-center gap-3'}>
     <span className={"dark:text-gray-200"}>Install community applications plugin</span>
     <IconDownload className={"dark:text-gray-200"} size={20} />
   </div>
 </Link>
 
-<br />
-<br />
+<br/>
+<br/>
 
 :::tip
 
@@ -46,3 +46,4 @@ After you've installed the Community Apps Plugin, you can install Homarr from th
 After you've installed Homarr, you can find it under the tab "Docker".
 
 The official support thread is located [here](https://forums.unraid.net/topic/123478-support-smartphonelover-homarr/), but we prefer to communicate over GitHub and Discord instead.
+

apps/docs/docs/integrations/adguard-home/index.mdx

@@ -1,44 +1,37 @@
 ---
-title: "AdGuard Home"
+title: 'AdGuard Home'
 description: "AdGuard Home is a network-wide software for blocking ads and trackers, providing a safer and faster internet experience."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconAd, IconDeviceGamepad } from "@tabler/icons-react";
-import { adguardHomeIntegration } from ".";
-import { dnsHoleSummaryWidget } from "@site/docs/widgets/dns-hole-summary";
-import { dnsHoleControlsWidget } from "@site/docs/widgets/dns-hole-controls";
+import { adguardHomeIntegration } from '.';
+import { dnsHoleSummaryWidget } from '@site/docs/widgets/dns-hole-summary';
+import { dnsHoleControlsWidget } from '@site/docs/widgets/dns-hole-controls';
 
-<IntegrationHeader integration={adguardHomeIntegration} categories={["DNS Hole"]} />
+<IntegrationHeader
+    integration={adguardHomeIntegration}
+    categories={['DNS Hole']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: dnsHoleSummaryWidget,
-    },
-    {
-      widget: dnsHoleControlsWidget,
-    },
-  ]}
+    items={[{
+        widget: dnsHoleSummaryWidget,
+    },{
+        widget: dnsHoleControlsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: []
+}]} />

apps/docs/docs/integrations/anchor/index.mdx

@@ -1,45 +1,40 @@
 ---
-title: "Anchor"
+title: 'Anchor'
 description: "Anchor is a self-hosted note-taking application."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { anchorIntegration } from ".";
-import { anchorNoteWidget } from "@site/docs/widgets/anchor-note";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { anchorIntegration } from '.';
+import { anchorNoteWidget } from '@site/docs/widgets/anchor-note';
 
-<IntegrationHeader integration={anchorIntegration} categories={["Notes"]} />
+
+<IntegrationHeader
+  integration={anchorIntegration}
+  categories={['Notes']}
+/>
 
 The Anchor integration lets Homarr connect to your Anchor instance so you can display and edit selected notes directly from your dashboard.
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: anchorNoteWidget,
-    },
-  ]}
+  items={[{
+    widget: anchorNoteWidget
+  }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Anchor instance.",
-        "Generate or copy an API key from Anchor settings.",
-        "Paste that key into the API Key secret field in Homarr.",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+  credentials: ['apiKey'],
+  steps: [
+    'Open your Anchor instance.',
+    'Generate or copy an API key from Anchor settings.',
+    'Paste that key into the API Key secret field in Homarr.'
+  ]
+}]} />

apps/docs/docs/integrations/aria2/index.mdx

@@ -1,43 +1,38 @@
 ---
-title: "Aria2"
+title: 'Aria2'
 description: "Lightweight multiprotocol & multi-source command-line download utility. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink"
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { aria2Integration } from ".";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { aria2Integration } from '.';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={aria2Integration} categories={["Download", "Multiprotocol", "Multi-source"]} />
+<IntegrationHeader
+  integration={aria2Integration}
+  categories={['Download', 'Multiprotocol', 'Multi-source']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: downloadsWidget,
-    },
-  ]}
+  items={[{
+    widget: downloadsWidget,
+  }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    {
-      credentials: [],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[
+  {
+    credentials: ['apiKey'],
+    steps: []
+  },
+  {
+    credentials: [],
+    steps: []
+  }]} />

apps/docs/docs/integrations/audiobookshelf/index.mdx

@@ -1,40 +1,41 @@
 ---
-title: "Audiobookshelf"
+title: 'Audiobookshelf'
 description: "Audiobookshelf is a self-hosted audiobook and podcast server that lets you manage and stream your audio library."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { audiobookshelfIntegration } from ".";
-import { audioStatsWidget } from "@site/docs/widgets/audio-stats";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { audiobookshelfIntegration } from '.';
+import { audioStatsWidget } from '@site/docs/widgets/audio-stats';
 
-<IntegrationHeader integration={audiobookshelfIntegration} categories={["Media"]} />
+
+<IntegrationHeader
+    integration={audiobookshelfIntegration}
+    categories={['Media']}
+/>
 
 Audiobookshelf provides library statistics including audiobook and podcast counts, listening time, and active sessions.
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: audioStatsWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: audioStatsWidget },
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Audiobookshelf instance",
-        "Go to Settings → Users",
-        "Click on your user account",
-        "Copy the API token from the user details",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
+        'Open your Audiobookshelf instance',
+        'Go to Settings → Users',
+        'Click on your user account',
+        'Copy the API token from the user details',
+    ]
+}]} />

apps/docs/docs/integrations/bazarr/index.mdx

@@ -1,30 +1,31 @@
 ---
-title: "Bazarr"
+title: 'Bazarr'
 description: "Bazarr is a companion application to Sonarr and Radarr that manages and downloads subtitles."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { bazarrIntegration } from ".";
-import { bazarrWidget } from "@site/docs/widgets/bazarr";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { bazarrIntegration } from '.';
+import { bazarrWidget } from '@site/docs/widgets/bazarr';
 
-<IntegrationHeader integration={bazarrIntegration} categories={["Subtitles", "Media"]} />
+<IntegrationHeader
+  integration={bazarrIntegration}
+  categories={['Subtitles', 'Media']}
+/>
 
 Bazarr complements Sonarr and Radarr by managing subtitle downloads. The Homarr integration uses your Bazarr API key to fetch missing subtitle counts and health badges.
 
 ### Screenshots
 
-import apiKeySettings from "./img/api-key-settings.png";
-import widgetOverview from "@site/docs/widgets/bazarr/img/widget-overview.png";
+import apiKeySettings from './img/api-key-settings.png';
+import widgetOverview from '@site/docs/widgets/bazarr/img/widget-overview.png';
 
 <div className="flex flex-col gap-4">
   <div>
-    <p>
-      API key location in Bazarr (<strong>Settings → General → Security</strong>):
-    </p>
+    <p>API key location in Bazarr (<strong>Settings → General → Security</strong>):</p>
     <img src={apiKeySettings} alt="bazarr-api-key-settings" width={128 * 4} />
   </div>
   <div>
@@ -34,25 +35,20 @@ import widgetOverview from "@site/docs/widgets/bazarr/img/widget-overview.png";
 </div>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: bazarrWidget }]} />
+<IntegrationCapabilites
+    items={[{ widget: bazarrWidget }]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
 You can find your Bazarr API key under **Settings → General → Security**.
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open Bazarr and go to Settings → General → Security.",
-        "Copy the API key and paste it into Homarr when creating the integration.",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
+      "Open Bazarr and go to Settings → General → Security.",
+      "Copy the API key and paste it into Homarr when creating the integration.",
+    ],
+}]} />

apps/docs/docs/integrations/beszel/index.mdx

@@ -1,22 +1,25 @@
 ---
-title: "Beszel"
+title: 'Beszel'
 description: "Beszel is a lightweight server monitoring platform with Docker stats, historical data, and alert functions."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { beszelIntegration } from ".";
-import { beszelSystemStatsWidget } from "@site/docs/widgets/beszel-system-stats";
-import { beszelSystemGridWidget } from "@site/docs/widgets/beszel-system-grid";
-import { beszelSystemTableWidget } from "@site/docs/widgets/beszel-system-table";
-import { beszelAlertsWidget } from "@site/docs/widgets/beszel-alerts";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { beszelIntegration } from '.';
+import { beszelSystemStatsWidget } from '@site/docs/widgets/beszel-system-stats';
+import { beszelSystemGridWidget } from '@site/docs/widgets/beszel-system-grid';
+import { beszelSystemTableWidget } from '@site/docs/widgets/beszel-system-table';
+import { beszelAlertsWidget } from '@site/docs/widgets/beszel-alerts';
 
-import beszelDashboard from "./img/beszel-dashboard.png";
+import beszelDashboard from './img/beszel-dashboard.png';
 
-<IntegrationHeader integration={beszelIntegration} categories={["System Monitoring"]} />
+<IntegrationHeader
+    integration={beszelIntegration}
+    categories={['System Monitoring']}
+/>
 
 Beszel monitors your servers in real time via lightweight agents, collecting CPU, memory, disk, network, GPU, temperature, and Docker container metrics. It stores historical data and supports configurable alerts.
 
@@ -25,33 +28,26 @@ Beszel monitors your servers in real time via lightweight agents, collecting CPU
 <img src={beszelDashboard} alt="Beszel dashboard overview showing all four widgets" />
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    { widget: beszelSystemStatsWidget },
-    { widget: beszelSystemGridWidget },
-    { widget: beszelSystemTableWidget },
-    { widget: beszelAlertsWidget },
-  ]}
+    items={[
+        { widget: beszelSystemStatsWidget },
+        { widget: beszelSystemGridWidget },
+        { widget: beszelSystemTableWidget },
+        { widget: beszelAlertsWidget },
+    ]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Open your Beszel hub instance (default port 8090)",
-        "Use the same credentials you use to log in to the Beszel web UI",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [
+        'Open your Beszel hub instance (default port 8090)',
+        'Use the same credentials you use to log in to the Beszel web UI',
+    ]
+}]} />
 
 :::tip
 Beszel uses PocketBase under the hood. The default admin credentials are set during the initial Beszel setup.

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

@@ -1,24 +1,29 @@
 ---
-title: "Coolify"
-description: "Self-hosted PaaS and deployment platform"
+title: 'Coolify'
+description: 'Self-hosted PaaS and deployment platform'
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { coolifyIntegration } from ".";
-import { coolifyWidget } from "../../widgets/coolify";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { coolifyIntegration } from '.';
+import { coolifyWidget } from '../../widgets/coolify';
 
-<IntegrationHeader integration={coolifyIntegration} categories={["System monitoring", "Deployment"]} />
+<IntegrationHeader
+  integration={coolifyIntegration}
+  categories={['System monitoring', 'Deployment']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: coolifyWidget }]} />
+<IntegrationCapabilites
+  items={[
+    { widget: coolifyWidget }
+  ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 :::info URL configuration
@@ -26,28 +31,16 @@ Use the root URL of your Coolify instance, for example `https://coolify.example.
 :::
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Open your Coolify instance and make sure you are in the team you want Homarr to monitor.",
-        <span>
-          Enable API access under <strong>Settings &gt; Advanced</strong> if it is disabled.
-        </span>,
-        <span>
-          Go to <strong>Security &gt; API Tokens</strong>.
-        </span>,
-        'Enter a name, e.g. "Homarr".',
-        <span>
-          Select the <code>read</code> permission. The Coolify widget only reads version, server, project, application,
-          and service data.
-        </span>,
-        'Click "Create".',
-        "Copy the generated token immediately. Coolify only shows it once.",
-        "Paste the token into the API Key field in Homarr.",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+  credentials: ['apiKey'],
+  steps: [
+    'Open your Coolify instance and make sure you are in the team you want Homarr to monitor.',
+    (<span>Enable API access under <strong>Settings &gt; Advanced</strong> if it is disabled.</span>),
+    (<span>Go to <strong>Security &gt; API Tokens</strong>.</span>),
+    'Enter a name, e.g. "Homarr".',
+    (<span>Select the <code>read</code> permission. The Coolify widget only reads version, server, project, application, and service data.</span>),
+    'Click "Create".',
+    'Copy the generated token immediately. Coolify only shows it once.',
+    'Paste the token into the API Key field in Homarr.'
+  ]
+}]} />

apps/docs/docs/integrations/dash-dot/index.mdx

@@ -1,33 +1,32 @@
 ---
-title: "Dash."
+title: 'Dash.'
 description: "Dash. is a system performance and resource monitoring tool"
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconHeartRateMonitor } from "@tabler/icons-react";
-import { dashDotIntegration } from ".";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
+import { dashDotIntegration } from '.';
+import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
+import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
 
-<IntegrationHeader integration={dashDotIntegration} categories={["System monitoring"]} />
+
+<IntegrationHeader
+  integration={dashDotIntegration}
+  categories={['System monitoring']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: healthMonitoringWidget,
-    },
-    {
-      widget: systemResourcesWidget,
-    },
-  ]}
+    items={[{
+      widget: healthMonitoringWidget
+    }, {
+      widget: systemResourcesWidget
+    }]}
 />
 
 ### Adding the integration
-
-<AddingIntegration />
+<AddingIntegration />

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

@@ -1,41 +1,36 @@
 ---
-title: "Deluge"
+title: 'Deluge'
 description: "Deluge is a lightweight, Free Software, cross-platform BitTorrent client."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+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 "@theme/Admonition";
-import { delugeIntegration } from ".";
-import { downloadsWidget } from "@site/docs/widgets/downloads";
+import Alert from '@theme/Admonition';
+import { delugeIntegration } from '.';
+import { downloadsWidget } from '@site/docs/widgets/downloads';
 
-<IntegrationHeader integration={delugeIntegration} categories={["Torrent client"]} />
+
+<IntegrationHeader
+    integration={delugeIntegration}
+    categories={['Torrent client']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: downloadsWidget,
-    },
-  ]}
+    items={[{
+        widget: downloadsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['password'],
+    steps: [],
+}]} />

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

@@ -1,95 +0,0 @@
----
-title: "Docker labels"
-description: "Discover apps, integrations, and widgets from container labels during Homarr onboarding."
----
-
-# Docker label discovery
-
-During onboarding, Homarr scans running containers on every reachable
-[Docker-compatible host](/docs/integrations/docker). Labels let you provide exact app metadata instead of relying on
-image-name matching. You can review and deselect every result before Homarr creates anything.
-
-A container with valid Homarr labels takes priority over image-based discovery. Containers without valid labels can
-still be suggested from their image and published ports.
-
-## Homarr labels
-
-`homarr.name` and `homarr.href` are required for label discovery. All other labels are optional.
-
-| Label                | Purpose                                                                    |
-| -------------------- | -------------------------------------------------------------------------- |
-| `homarr.name`        | App or integration display name                                            |
-| `homarr.href`        | Address opened by the app and used as the suggested integration address    |
-| `homarr.group`       | Container section that receives the selected app and compatible widget     |
-| `homarr.icon`        | App icon URL                                                               |
-| `homarr.description` | App description                                                            |
-| `homarr.ping`        | Address used for app status checks                                         |
-| `homarr.id`          | Stable source identifier; defaults to the Docker container ID              |
-| `homarr.board`       | Intended board name; see [Board targeting](#board-targeting)               |
-| `homarr.integration` | Homarr integration kind, for example `sonarr`                              |
-| `homarr.widget`      | Homarr widget kind to add when it supports the selected integration        |
-| `homarr.hide`        | Excludes the container when this label is present, regardless of its value |
-
-Unknown integration and widget kinds are ignored. Do not put API keys, passwords, or other secrets in labels. Enter
-credentials in onboarding, where Homarr stores them using its normal encrypted integration-secret flow.
-
-## Compose example
-
-```yaml
-services:
-  sonarr:
-    image: lscr.io/linuxserver/sonarr:latest
-    labels:
-      homarr.name: "Sonarr"
-      homarr.href: "http://server.local:8989"
-      homarr.group: "Media"
-      homarr.icon: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/sonarr.svg"
-      homarr.description: "TV library"
-      homarr.ping: "http://server.local:8989"
-      homarr.integration: "sonarr"
-      homarr.widget: "calendar"
-```
-
-Use an address that is reachable where it is needed. A Docker service name can work for server-side integration
-requests, while an app link opened in a browser usually needs a LAN hostname, IP address, or reverse-proxy address.
-Onboarding accepts these self-hosted address formats directly and only requires the field to be non-empty.
-
-## Homepage label fallback
-
-When `homarr.name` is absent, onboarding also understands these Homepage labels:
-
-- `homepage.name`
-- `homepage.href`
-- `homepage.group`
-- `homepage.icon`
-- `homepage.description`
-
-`homepage.name` and `homepage.href` are required for the fallback. Homarr does not combine partial Homarr metadata with
-Homepage metadata: once `homarr.name` is present, use `homarr.*` labels for the remaining fields too.
-
-## What onboarding creates
-
-In **Connect**, label-discovered apps and integrations appear before image-based suggestions. You can import multiple
-services in one pass and edit every suggested address. For image-matched apps, Homarr uses the detected service type
-when building host, subdomain, or reverse-proxy path suggestions.
-
-When setup completes, Homarr rechecks the selected container sources and then:
-
-- creates an app with its name, address, icon, description, and ping address;
-- creates the requested integration and links its app after you provide required credentials;
-- places grouped apps in a board container named by `homarr.group`;
-- places ungrouped apps in the main board area;
-- adds `homarr.widget` only when the widget kind is valid and compatible with the selected integration;
-- keeps image-based discovery available for unlabeled containers.
-
-If a selected container disappears, targets another board, or requests an incompatible widget, setup finishes with a
-warning instead of creating an invalid board item.
-
-## Board targeting
-
-On a fresh installation with one seeded `dashboard` board, one unique selected `homarr.board` value can name that first
-board. Otherwise, the label must match the board selected in onboarding. Services labeled for another board are skipped
-and reported in the completion warning.
-
-Onboarding configures one board at a time. Run normal board management after setup if you want to distribute services
-across several boards.

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

@@ -1,34 +1,36 @@
 ---
-title: "Docker"
+title: 'Docker'
 description: "Docker is a platform where you can run your applications in containers, allowing for easy deployment and management of applications."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconBrandDocker, IconTool } from "@tabler/icons-react";
-import { dockerIntegration } from ".";
-import { dockerContainersWidget } from "@site/docs/widgets/docker-containers";
+import { dockerIntegration } from '.';
+import { dockerContainersWidget } from '@site/docs/widgets/docker-containers';
 
-<IntegrationHeader integration={dockerIntegration} categories={["Containers"]} />
 
-### Widgets & Capabilities
-
-<IntegrationCapabilites
-  items={[
-    {
-      widget: dockerContainersWidget,
-      note: "This widget can only be used with administrator privileges",
-    },
-  ]}
+<IntegrationHeader
+  integration={dockerIntegration}
+  categories={['Containers']}
 />
 
-## Connecting Docker to Homarr
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+      widget: dockerContainersWidget,
+      note: "This widget can only be used with administrator privileges"
+    }]}
+/>
 
-Docker connections come directly from Homarr's environment variables. They are automatically available in the Docker management table and Docker widget; you do not create a Docker integration under **Management → Integrations**.
 
-If Homarr runs directly on a host with Docker installed, it uses `/var/run/docker.sock` by default. When Homarr runs in a container, mount the [Docker socket](https://docs.docker.com/engine/security/protect-access/) into it so Homarr can interact with Docker.
+## Enabling the Docker integration
+This integration must first be enabled.
+If you directly run on the host system and you have docker installed, it will be enabled by default.
+Otherwise, you'll need to mount the [docker socket](https://docs.docker.com/engine/security/protect-access/) to the Homarr container,
+so Homarr can interact with the Docker service.
 
 In Docker Compose, you can simply add this line:
 
@@ -47,7 +49,7 @@ services:
     environment:
       - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
     ports:
-      - "7575:7575"
+      - '7575:7575'
 ```
 
 With docker run, add this parameter: `-v /var/run/docker.sock:/var/run/docker.sock`.
@@ -121,91 +123,9 @@ services:
       DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
 ```
 
-For remote socket proxies, list the hostnames and matching ports in the same order:
-
-```yaml
-environment:
-  DOCKER_HOSTNAMES: docker-proxy-home,docker-proxy-lab
-  DOCKER_PORTS: 2375,2375
-```
-
-Homarr automatically discovers each comma-separated entry as a separate Docker environment. All environments are selected by default; the Docker widget lets you select one or more without any additional setup.
-
-:::warning[Plaintext TCP]
-Plaintext Docker TCP can grant unauthenticated control of the Docker host. Prefer a local socket, a least-privilege socket proxy on a private Docker network, or TLS.
-:::
-
-### Advanced endpoint configuration
-
-Most users should use the comma-separated variables above. Use `DOCKER_ENDPOINTS` only when you need custom names, TLS, or restricted capabilities. It is a JSON array where every endpoint declares its identity, transport, and capabilities:
-
-```yaml
-services:
-  homarr:
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - ./docker-ca.pem:/run/secrets/docker-ca.pem:ro
-    environment:
-      DOCKER_ENDPOINTS: >-
-        [
-          {
-            "id": "local",
-            "name": "Local Docker",
-            "kind": "docker",
-            "transport": { "type": "socket", "path": "/var/run/docker.sock" },
-            "capabilities": ["inventory", "logs", "lifecycle", "remove"]
-          },
-          {
-            "id": "remote-read-only",
-            "name": "Production inventory",
-            "kind": "docker",
-            "transport": {
-              "type": "tls",
-              "host": "docker.example.com",
-              "port": 2376,
-              "caPath": "/run/secrets/docker-ca.pem"
-            },
-            "capabilities": ["inventory", "logs"]
-          }
-        ]
-```
-
-The stable `id` keeps containers from different endpoints distinct. `name` is shown in the interface, and `kind` can be `docker` or `podman`. Every endpoint must include the `inventory` capability; optionally add `logs`, `lifecycle`, and `remove`. Homarr hides or disables actions the endpoint does not allow and also enforces the same capabilities on the server.
-
-Supported transports are:
-
-- `socket`: an absolute in-container `path`
-- `tls`: `host`, `port`, and an absolute `caPath`; add both `certPath` and `keyPath` for mutual TLS
-- `tcp`: `host`, `port`, and the explicit acknowledgement `allowInsecure: true`
-
-The structured configuration refuses TCP unless `allowInsecure` is explicitly set to `true`. When `DOCKER_ENDPOINTS` is set, it takes precedence over `DOCKER_SOCKET_PATHS`, `DOCKER_HOSTNAMES`, and `DOCKER_PORTS`.
-
 ### Managing your Docker containers within Homarr
-
 Homarr allows you to interact with Docker containers running on your system.
-The collapsed **Assisted Docker setup** helper optionally compares visible containers with your existing Homarr apps and integrations. Open it only when you want setup suggestions; it never blocks normal container management. Every service stays distinct by Docker endpoint and container ID, including multiple containers that use the same integration type.
-
-Homarr can show a service as:
-
-- **Ready to connect** when its image or name matches a supported integration
-- **New service** when it can be added as an app but no integration is recognized
-- **Already represented** or **Linked** when an app or integration already matches
-- **Address changed** when a service appears to match an integration but its reachable address has changed
-
-Set the usual server address once, then choose whether services normally use different ports, subdomains, or paths. Homarr uses that pattern to prefill every detected service. Each suggestion has one editable URL field with the generated and Docker-reported addresses available as autocomplete options, so you can select a suggestion or type any address directly.
-
-:::info[Review before changing]
-Service discovery is read-only. Homarr never creates or changes an app or integration automatically. **Set up integration** opens the standard prefilled integration form, while **Create app** opens the existing Docker app form, so you can review and confirm the final setup.
-:::
-
-Suggestions appear as a compact task list. Expand an item only when you want to edit its URL or inspect relevant setup statuses. Use the filters to focus on services that need attention or those already represented in Homarr. Refresh runs discovery again. Dismissed suggestions are stored in the current browser using their endpoint-qualified service identity and can be restored from the same helper. If multiple existing items could match, Homarr marks the result as ambiguous and does not choose one automatically.
-
-Compact status icons summarize the setup information Homarr can act on. Unknown and non-applicable runtime layers are omitted to keep the helper focused; use the integration form's connection test or the relevant board action for live diagnostics.
-
-If one Docker endpoint is unavailable, Homarr reports that endpoint while continuing to show services from healthy endpoints. An unavailable endpoint is not treated as an empty Docker installation.
-
 Each container row has an action menu with the following options:
-
 - **View logs** - opens a dedicated logs page with a live terminal
 - **Start** - start a stopped container
 - **Stop** - stop a running container
@@ -227,10 +147,6 @@ This opens a dedicated page with an xterm.js terminal that streams the container
 The Docker management table supports optional **CPU usage** and **Memory usage** columns.
 These columns are hidden by default and can be toggled on from the table column visibility settings.
 
-#### Choosing Docker environments in the widget
-
-The Docker widget can show one or more configured Docker environments. Leave **Docker environments** empty to include every endpoint, which is also the default for existing widgets. Selecting one or more entries limits container and statistics requests to those endpoints.
-
 #### Add apps from containers
 
 Homarr also lets you add apps from containers. You can simply select all containers you want to add an app for and then click the `Add to Homarr` button.
@@ -243,22 +159,18 @@ They are then available in the app list and can be used as normally added apps.
 
 ![Apps added from containers](img/add-to-homarr-apps.png)
 
-### Container labels
+### Configuration
 
-`homarr.hide` excludes a container from the Docker Containers widget, tools page, and onboarding discovery whenever the
-label is present.
+Currently Homarr supports one label for configuration of the containers:
 
-During first-run onboarding, Homarr can also discover apps, integrations, groups, and compatible widgets from
-`homarr.*` labels, with Homepage labels as a fallback. See the complete [Docker label reference](/docs/integrations/docker-labels).
+- **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
 
 ### Security
-
 Mounting docker sockets can be risky, as they permit full control over your docker service.
 As an example, a thread actor could abuse Homarr use the socket to start, stop or delete containers on your system.
 
 Therefore we recommend the usage of a socket proxy, which can prohibit certain actions.
 A few examples include:
-
 - https://github.com/linuxserver/docker-socket-proxy
 - https://github.com/Tecnativa/docker-socket-proxy
 
@@ -266,44 +178,36 @@ See documentation of the respective proxies on how to configure them.
 Homarr may behave in unexpected ways when you use proxies.
 
 #### Permissions
-
 Homarr needs the following permissions from the Docker API:
-
 - Containers/Start
 - Containers/Stop
 - Containers/Restart
 - Containers/Remove
 
 For socket proxies, you will need these permissions:
-
 - `CONTAINERS=1`
 - `POST=1`
 
 **Caution:** `POST` access is security critical as it provides extensive capabilities to modify your docker environment. Please leave it disabled if you're concerned about this.
 
 As a workaround, you can use [LSIO's socket proxy](https://github.com/linuxserver/docker-socket-proxy) and set the following:
-
 - ALLOW_START=1
 - ALLOW_STOP=1
 - ALLOW_RESTARTS=1
 
-These will work even with `POST=0`.
+These will work even with `POST=0`. 
 
 You lose the ability to remove containers, but start, stop and restarts should work just fine.
 
 #### Connecting to Docker via Socket Proxies
-
 To connect to Docker via a socket proxy, you'll need to add these two environment variables in the compose file:
-
 - `DOCKER_HOSTNAMES=<name of the socket proxy container>`
 - `DOCKER_PORTS=<socket proxy port, usually 2375>`
 
 Refer: https://homarr.dev/docs/advanced/environment-variables/
 
 You will also need to add Homarr to the network of your socket proxy. You can do it like this:
-
 1. Add the network to your compose file (with appropriate changes):
-
 ```yaml
 networks:
   socket-proxy:
@@ -312,7 +216,6 @@ networks:
 ```
 
 2. Add the network to the homarr service in the compose file:
-
 ```yaml
 networks:
   - socket-proxy

apps/docs/docs/integrations/emby/index.mdx

@@ -1,35 +1,37 @@
 ---
-title: "Emby"
+title: 'Emby'
 description: "Emby is a media server platform that allows you to organize, manage, and stream your personal media collection."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconVideo, IconTicket } from "@tabler/icons-react";
-import { embyIntegration } from ".";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
-import { mediaReleasesWidget } from "@site/docs/widgets/media-releases";
+import { embyIntegration } from '.';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
+import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
 
-<IntegrationHeader integration={embyIntegration} categories={["Media server"]} />
+
+<IntegrationHeader
+    integration={embyIntegration}
+    categories={['Media server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: mediaServerWidget }, { widget: mediaReleasesWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: mediaServerWidget }, 
+        { widget: mediaReleasesWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/glances/index.mdx

@@ -1,43 +1,37 @@
 ---
-title: "Glances"
+title: 'Glances'
 description: "Glances is a cross-platform system monitoring tool."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { glancesIntegration } from ".";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { glancesIntegration } from '.';
+import { systemResourcesWidget } from '@site/docs/widgets/system-resources';
+import { healthMonitoringWidget } from '@site/docs/widgets/health-monitoring';
 
-<IntegrationHeader integration={glancesIntegration} categories={["System Monitoring"]} />
+
+<IntegrationHeader
+    integration={glancesIntegration}
+    categories={['System Monitoring']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: systemResourcesWidget,
-    },
-    {
-      widget: healthMonitoringWidget,
-    },
-  ]}
+    items={[{
+        widget: systemResourcesWidget
+    }, {
+        widget: healthMonitoringWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}]} />

apps/docs/docs/integrations/gluetun/index.mdx

@@ -1,17 +1,20 @@
 ---
-title: "Gluetun"
-description: "Connect Gluetun to Homarr as a VPN integration."
+title: 'Gluetun'
+description: 'Connect Gluetun to Homarr as a VPN integration.'
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { gluetunIntegration } from ".";
-import { vpnWidget } from "@site/docs/widgets/vpn";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { gluetunIntegration } from '.';
+import { vpnWidget } from '@site/docs/widgets/vpn';
 
-<IntegrationHeader integration={gluetunIntegration} categories={["VPN", "Network"]} />
+<IntegrationHeader
+  integration={gluetunIntegration}
+  categories={['VPN', 'Network']}
+/>
 
 [Gluetun](https://github.com/qdm12/gluetun) exposes a control server that Homarr can query to report the VPN tunnel
 status, DNS status, public IP address, and active provider details in the VPN widget.
@@ -19,11 +22,9 @@ status, DNS status, public IP address, and active provider details in the VPN wi
 ### Widgets & Capabilities
 
 <IntegrationCapabilites
-  items={[
-    {
-      widget: vpnWidget,
-    },
-  ]}
+  items={[{
+    widget: vpnWidget,
+  }]}
 />
 
 ### Setting up the Gluetun control server
@@ -39,20 +40,13 @@ Refer to the [Gluetun control server documentation](https://github.com/qdm12/glu
 Gluetun's control server can be left unprotected or secured with either an API key or HTTP Basic authentication.
 Choose the option that matches how your Gluetun instance integration is set up.
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    ,
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+  credentials: [],
+  steps: [],
+},{
+  credentials: ['username', 'password'],
+  steps: [],
+},{
+  credentials: ['apiKey'],
+  steps: [],
+},,]} />

apps/docs/docs/integrations/gotify/index.mdx

@@ -1,39 +1,33 @@
 ---
-title: "Gotify"
+title: 'Gotify'
 description: "Gotify is a simple, self-hosted server for sending and receiving messages in real time."
 hide_title: true
 ---
 
-import { notificationsWidget } from "@site/docs/widgets/notifications";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { gotifyIntegration } from ".";
+import { notificationsWidget } from '@site/docs/widgets/notifications';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { gotifyIntegration } from '.';
 
-<IntegrationHeader integration={gotifyIntegration} categories={["Notifications", "Messaging"]} />
+<IntegrationHeader
+    integration={gotifyIntegration}
+    categories={['Notifications', 'Messaging']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: notificationsWidget,
-    },
-  ]}
+    items={[{
+        widget: notificationsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: []
+}]} />

apps/docs/docs/integrations/home-assistant/index.mdx

@@ -1,51 +1,45 @@
 ---
-title: "Home Assistant"
+title: 'Home Assistant'
 description: "Home Assistant is an open-source home automation platform that focuses on privacy and local control, allowing you to automate and control your smart home devices."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconBinaryTree } from "@tabler/icons-react";
-import { homeAssistantIntegration } from ".";
-import { smartHomeEntityStateWidget } from "@site/docs/widgets/smart-home-entity-state";
-import { smartHomeExecuteAutomationWidget } from "@site/docs/widgets/smart-home-execute-automation";
+import { homeAssistantIntegration } from '.';
+import { smartHomeEntityStateWidget } from '@site/docs/widgets/smart-home-entity-state';
+import { smartHomeExecuteAutomationWidget } from '@site/docs/widgets/smart-home-execute-automation';
 
-<IntegrationHeader integration={homeAssistantIntegration} categories={["Smart Home", "Automation"]} />
+
+<IntegrationHeader
+    integration={homeAssistantIntegration}
+    categories={['Smart Home', 'Automation']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: smartHomeEntityStateWidget,
-    },
-    {
-      widget: smartHomeExecuteAutomationWidget,
-    },
-  ]}
+    items={[{
+        widget: smartHomeEntityStateWidget
+    }, {
+        widget: smartHomeExecuteAutomationWidget,
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: [
         "Click on your profile in the bottom left corner of Home Assistant.",
         "Switch to the Security tab.",
         "Scroll down to the Long-lived access tokens section.",
         "Click on the Create Token button.",
         "Enter a name for the token (e.g., 'Homarr Integration') and click Create.",
         "Copy the generated token and paste it into the Homarr integration settings.",
-      ],
-    },
-  ]}
-/>
+    ]
+}]} />

apps/docs/docs/integrations/ical/index.mdx

@@ -1,44 +1,38 @@
 ---
-title: "iCal"
+title: 'iCal'
 description: "iCal is a standard for calendar data exchange, allowing users to share and manage calendar events across different platforms."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
-import { icalIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { icalIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={icalIntegration} categories={["Calendar"]} />
+<IntegrationHeader
+  integration={icalIntegration}
+  categories={['Calendar']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: calendarWidget,
-    },
-  ]}
+    items={[{
+      widget: calendarWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["url"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['url'],
+    steps: []
+}]} />
 
 ## Using the iCal integration
 
-The iCal integration allows you to add external calendars to Homarr. Any calendar that provides a public iCal URL can be integrated, such as Google Calendar, Apple Calendar, or Outlook.
+The iCal integration allows you to add external calendars to Homarr. Any calendar that provides a public iCal URL can be integrated, such as Google Calendar, Apple Calendar, or Outlook.

apps/docs/docs/integrations/immich/index.mdx

@@ -1,29 +1,36 @@
 ---
-title: "Immich"
+title: 'Immich'
 description: "Self-hosted photo and video management solution"
 hide_title: true
 ---
 
-import { immichAlbumCarouselWidget } from "../../widgets/immich-album-carousel";
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { immichIntegration } from ".";
-import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
+import { immichAlbumCarouselWidget } from '../../widgets/immich-album-carousel';import {
+  IntegrationHeader
+} from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { immichIntegration } from '.';
+import { immichServerStatsWidget } from '../../widgets/immich-server-stats';
 
-<IntegrationHeader integration={immichIntegration} categories={["Photo server"]} />
+
+<IntegrationHeader
+  integration={immichIntegration}
+  categories={['Photo server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: immichAlbumCarouselWidget }, { widget: immichServerStatsWidget }]} />
+<IntegrationCapabilites
+  items={[
+    { widget: immichAlbumCarouselWidget },
+    { widget: immichServerStatsWidget }
+  ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
 <IntegrationSecrets secrets={[{
   credentials: ['apiKey'],
   steps: [
@@ -48,10 +55,9 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
     <code>asset.statistics</code>,{" "}
     <code>server.statistics</code>,{" "}
     <code>server.about</code>.
-
   </span>
 
 ),
-'Create the integration in Homarr and copy the API key to there'
-]
+    'Create the integration in Homarr and copy the API key to there'
+    ]
 }]} />

apps/docs/docs/integrations/jellyfin/index.mdx

@@ -1,39 +1,40 @@
 ---
-title: "Jellyfin"
+title: 'Jellyfin'
 description: "Jellyfin is a free and open-source media server software that allows you to organize, manage, and share your media files."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconVideo, IconTicket } from "@tabler/icons-react";
-import { jellyfinIntegration } from ".";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
-import { mediaReleasesWidget } from "@site/docs/widgets/media-releases";
+import { jellyfinIntegration } from '.';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
+import { mediaReleasesWidget } from '@site/docs/widgets/media-releases';
 
-<IntegrationHeader integration={jellyfinIntegration} categories={["Media server"]} />
+
+<IntegrationHeader
+    integration={jellyfinIntegration}
+    categories={['Media server']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: mediaServerWidget }, { widget: mediaReleasesWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: mediaServerWidget }, 
+        { widget: mediaReleasesWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+},{
+    credentials: ['username', 'password'],
+    steps: []
+}]} />

apps/docs/docs/integrations/jellyseerr/index.mdx

@@ -1,52 +1,45 @@
 ---
-title: "Jellyseerr"
+title: 'Jellyseerr'
 description: "Jellyseerr is a self-hosted media request management system that integrates with Jellyfin and other media servers."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
-import { jellyseerrIntegration } from ".";
-import { mediaRequestListWidget } from "@site/docs/widgets/media-request-list";
-import { mediaRequestStatsWidget } from "@site/docs/widgets/media-request-stats";
+import { jellyseerrIntegration } from '.';
+import { mediaRequestListWidget } from '@site/docs/widgets/media-request-list';
+import { mediaRequestStatsWidget } from '@site/docs/widgets/media-request-stats';
 
-<IntegrationHeader integration={jellyseerrIntegration} categories={["Media requests"]} />
+
+<IntegrationHeader
+  integration={jellyseerrIntegration}
+  categories={['Media requests']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: mediaRequestListWidget,
-    },
-    {
-      widget: mediaRequestStatsWidget,
-    },
-    {
-      capability: {
-        icon: IconSearch,
-        name: "Media Search",
-        description: "Search for movies and TV shows directly from Spotlight and request them.",
-        path: "../../management/search-engines/#media-request-search",
-      },
-    },
-  ]}
+    items={[{
+        widget: mediaRequestListWidget,
+    },{
+        widget: mediaRequestStatsWidget,
+    }, {
+        capability: {
+            icon: IconSearch,
+            name: "Media Search",
+            description: "Search for movies and TV shows directly from Spotlight and request them.",
+            path: "../../management/search-engines/#media-request-search"
+        }
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/kubernetes/index.mdx

@@ -1,21 +1,23 @@
 ---
-title: "Kubernetes"
+title: 'Kubernetes'
 description: "Kubernetes is a powerful container orchestration platform that automates the deployment, scaling, and management of containerized applications."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconBrandDocker, IconTool } from "@tabler/icons-react";
-import { kubernetesIntegration } from ".";
+import { kubernetesIntegration } from '.';
 
-<IntegrationHeader integration={kubernetesIntegration} categories={["Containers"]} />
+
+<IntegrationHeader
+  integration={kubernetesIntegration}
+  categories={['Containers']}
+/>
 
 Homarr provides a user-friendly Kubernetes dashboard that offers an overview of your cluster’s resources in a clear and structured interface. It allows users to view key Kubernetes objects, including `Pods`, `Services`, `Ingresses`, `Nodes`, `ConfigMaps`, `Secrets`, `Namespaces`, and `Volumes`, as well as basic metrics when the Kubernetes Metrics Server is enabled.
 
-Docker service discovery does not convert Kubernetes resources into Homarr apps or integrations. Kubernetes remains a separate, read-only operational view, so a cluster resource is never changed or linked automatically.
-
 :::warning[Read only]
 This integration is read-only, meaning Homarr does not modify or manage cluster resources but serves as an informational tool to enhance visibility into your Kubernetes environment.
 :::
@@ -27,7 +29,7 @@ This integration is read-only, meaning Homarr does not modify or manage cluster
 Before deploying Homarr in Kubernetes, ensure the following prerequisites are met:
 
 - Kubernetes (Version >= 1.24.0)
-- Metrics Server ([install from here](https://github.com/kubernetes-sigs/metrics-server)) is optional. Without it, Homarr still shows cluster inventory, node status, and reserved capacity, and identifies live CPU and memory usage as unavailable.
+- Metrics Server ([Install from here](https://github.com/kubernetes-sigs/metrics-server))
 - RBAC Enabled (Required for Homarr Helm chart)
 
 ### Configuring RBAC in Helm Chart
@@ -45,26 +47,7 @@ Enabling RBAC in the Helm chart creates the necessary Kubernetes Role-Based Acce
 - Service Account: A dedicated service account for Homarr.
 - Role & RoleBinding: Grants permissions within a specific namespace to list, watch, and get pods, services, secrets, configmaps, and more.
 - ClusterRole & ClusterRoleBinding: Extends the same permissions cluster-wide for additional flexibility.
-  :::
-
-### Multiple Kubernetes contexts
-
-When Homarr runs outside a cluster, set `KUBECONFIG` explicitly so Homarr loads the contexts from the referenced kubeconfig file or files. Mount the kubeconfig read-only and set the standard `KUBECONFIG` environment variable to its path inside the Homarr container:
-
-```yaml
-services:
-  homarr:
-    volumes:
-      - ./kubeconfig:/app/config/kubeconfig:ro
-    environment:
-      KUBECONFIG: /app/config/kubeconfig
-```
-
-The Kubernetes management pages include a context selector. The selected context is stored in the page URL, so each React Query cache entry and every API request remains context-specific. Resources with the same namespace and name in two contexts therefore remain separate.
-
-Context status is checked independently. If one context is unavailable, the selector still lists healthy contexts. A context is shown as **Metrics unavailable** when its Kubernetes API is reachable but Metrics Server is not; inventory remains available without live CPU and memory usage.
-
-When Homarr runs inside Kubernetes without `KUBECONFIG`, it keeps using the in-cluster service account as the single default context.
+:::
 
 ### Homarr Dashboard Overview
 

apps/docs/docs/integrations/lidarr/index.mdx

@@ -1,40 +1,35 @@
 ---
-title: "Lidarr"
+title: 'Lidarr'
 description: "Lidarr is a music management tool that automates the process of downloading, sorting, and renaming music."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import {IntegrationSecrets} from '@site/src/components/integrations/secrets';
 import { IconCalendar } from "@tabler/icons-react";
-import { lidarrIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
+import { lidarrIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
 
-<IntegrationHeader integration={lidarrIntegration} categories={["Media manager", "Servarr"]} />
+
+<IntegrationHeader
+    integration={lidarrIntegration}
+    categories={['Media manager', "Servarr"]}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: calendarWidget,
-    },
-  ]}
+    items={[{
+        widget: calendarWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['apiKey'],
+    steps: []
+}]} />

apps/docs/docs/integrations/navidrome/index.mdx

@@ -1,39 +1,41 @@
 ---
-title: "Navidrome"
+title: 'Navidrome'
 description: "Navidrome is a self-hosted music server and streamer compatible with the Subsonic API."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { navidromeIntegration } from ".";
-import { audioStatsWidget } from "@site/docs/widgets/audio-stats";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { navidromeIntegration } from '.';
+import { audioStatsWidget } from '@site/docs/widgets/audio-stats';
+import { mediaServerWidget } from '@site/docs/widgets/media-server';
 
-<IntegrationHeader integration={navidromeIntegration} categories={["Media", "Media server"]} />
+
+<IntegrationHeader
+    integration={navidromeIntegration}
+    categories={['Media', 'Media server']}
+/>
 
 Navidrome provides music library statistics including artist, album, and song counts, as well as now playing audio streams via the Subsonic API.
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: audioStatsWidget }, { widget: mediaServerWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: audioStatsWidget },
+        { widget: mediaServerWidget },
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Use the same credentials you use to log in to Navidrome",
-        "The user must have access to the Subsonic API (enabled by default)",
-      ],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [
+        'Use the same credentials you use to log in to Navidrome',
+        'The user must have access to the Subsonic API (enabled by default)',
+    ]
+}]} />

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

@@ -1,43 +1,40 @@
 ---
-title: "Nextcloud"
+title: 'Nextcloud'
 description: "Nextcloud is a self-hosted productivity platform that provides file storage, collaboration tools, and more."
 hide_title: true
 ---
 
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+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 "@theme/Admonition";
-import { nextcloudIntegration } from ".";
-import { calendarWidget } from "@site/docs/widgets/calendar";
-import { notificationsWidget } from "@site/docs/widgets/notifications";
+import Alert from '@theme/Admonition';
+import { nextcloudIntegration } from '.';
+import { calendarWidget } from '@site/docs/widgets/calendar';
+import { notificationsWidget } from '@site/docs/widgets/notifications';
 
-<IntegrationHeader integration={nextcloudIntegration} categories={["Calendar", "Notifications"]} />
+<IntegrationHeader
+  integration={nextcloudIntegration}
+  categories={['Calendar', 'Notifications']}
+/>
 
 ### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: calendarWidget }, { widget: notificationsWidget }]} />
+<IntegrationCapabilites
+    items={[
+        { widget: calendarWidget },
+        { widget: notificationsWidget }
+    ]}
+/>
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [],
-      header: (
-        <Alert type="info">
-          Users who use 2FA will have to use Nextcloud's App Password tool to grant Homarr access, as 2FA breaks the
-          traditional process. For more information, see [Nextcloud's
-          Documentation](https://docs.nextcloud.com/server/stable/admin_manual/configuration_user/authentication.html#app-passwords)
-        </Alert>
-      ),
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['username', 'password'],
+    steps: [],
+    header: <Alert type="info">
+      Users who use 2FA will have to use Nextcloud's App Password tool to grant Homarr access, as 2FA breaks the traditional process. For more information, see [Nextcloud's Documentation](https://docs.nextcloud.com/server/stable/admin_manual/configuration_user/authentication.html#app-passwords)
+    </Alert>,
+}]} />

apps/docs/docs/integrations/ntfy/index.mdx

@@ -1,44 +1,37 @@
 ---
-title: "Ntfy"
+title: 'Ntfy'
 description: "Ntfy is a simple, open-source notification service that allows you to send and receive notifications across devices."
 hide_title: true
 ---
 
-import { notificationsWidget } from "@site/docs/widgets/notifications";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
+import { notificationsWidget } from '@site/docs/widgets/notifications';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
 import { IconMessage } from "@tabler/icons-react";
-import { ntfyIntegration } from ".";
+import { ntfyIntegration } from '.';
 
-<IntegrationHeader integration={ntfyIntegration} categories={["Notifications", "Messaging"]} />
+<IntegrationHeader
+    integration={ntfyIntegration}
+    categories={['Notifications', 'Messaging']}
+/>
 
 ### Widgets & Capabilities
-
 <IntegrationCapabilites
-  items={[
-    {
-      widget: notificationsWidget,
-    },
-  ]}
+    items={[{
+        widget: notificationsWidget
+    }]}
 />
 
 ### Adding the integration
-
 <AddingIntegration />
 
 ### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["topic"],
-      steps: [],
-    },
-    {
-      credentials: ["topic", "apiKey"],
-      steps: [],
-    },
-  ]}
-/>
+<IntegrationSecrets secrets={[{
+    credentials: ['topic'],
+    steps: []
+}, {
+    credentials: ['topic', 'apiKey'],
+    steps: []
+}]} />