chore(ops): build with bun and ship v2's .output/standalone

v2 replaces pnpm with bun and moves the standalone build to
apps/nextjs/.output/standalone, which already carries static assets,
public and next.config.ts. Next still writes an incomplete
.next/standalone, so the assembler now refuses to run without the v2
output rather than silently shipping that one.

The notes now list v2's registration points, the tests that already
fail on the upstream tag, and the one-way v1 to v2 database migration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.agents/skills/codebase-context/SKILL.md

@@ -17,11 +17,11 @@ Orient from the current checkout before editing. Treat package manifests, export
 
 ## Current toolchain
 
-- Use Node `24.18.0` from `mise.toml` and pnpm `11.15.1` from `package.json`.
-- Use pnpm workspaces with Turborepo. Workspace packages use the `@homarr/` scope and catalog-managed dependencies.
+- Use Node `24.18.0` for application runtimes and Bun `1.4.2` for package management, pinned in `mise.toml` and `package.json`.
+- Use Bun workspaces with Turborepo and a shared hoisted install. Workspace packages use the `@homarr/` scope and catalog-managed dependencies.
 - Use Next.js App Router, TypeScript, tRPC, Drizzle, Mantine v9, Tabler icons, Jotai, TanStack Query, next-intl, Vitest, and Playwright.
 - Use oxlint and oxfmt. Mantine is the application UI system; Tailwind is limited to the docs app.
-- `pnpm dev` starts only `@homarr/nextjs`. Start a standalone runtime explicitly when the task needs it.
+- `bun run dev` starts only `@homarr/nextjs`. Start a standalone runtime explicitly when the task needs it.
 
 ## High-value seams
 
@@ -29,7 +29,7 @@ Orient from the current checkout before editing. Treat package manifests, export
 - Client tRPC hooks: `@homarr/api/client`
 - Main router: `packages/api/src/root.ts`
 - MCP eager router: `packages/api/src/mcp.ts`
-- Database schemas: `packages/db/schema/{sqlite,mysql,postgresql}.ts`
+- Database schemas: `packages/db/schema/{sqlite,postgresql}.ts`
 - Widget registry: `packages/widgets/src/registry.ts`
 - Widget loading manifest: `packages/widgets/src/manifest.ts`
 - Integration definitions: `packages/definitions/src/integration.ts`
@@ -37,4 +37,4 @@ Orient from the current checkout before editing. Treat package manifests, export
 - Cron jobs: `packages/cron-jobs/src/jobs/`
 - App routes: `apps/nextjs/src/app/[locale]/`
 
-Invoke `documentation-sync` when hidden capabilities or information not evident to an advanced user change, or existing guidance becomes inaccurate; follow the Documentation Sync criteria in `AGENTS.md`. When exposing tRPC through MCP, invoke `mcp-integration`.
+Invoke `documentation-sync` only when users need new or corrected information to set up, use, or troubleshoot Homarr; follow the Documentation Sync criteria in `AGENTS.md`. When exposing tRPC through MCP, invoke `mcp-integration`.

.agents/skills/codebase-context/references/architecture.md

@@ -13,14 +13,14 @@
 | Path             | Role                                                                                     |
 | ---------------- | ---------------------------------------------------------------------------------------- |
 | `apps/nextjs`    | Main Next.js application and HTTP APIs on port 3000                                      |
-| `apps/docs`      | Docusaurus documentation site on port 3003                                               |
+| `apps/docs`      | Next.js and Fumadocs documentation site on port 3003                                     |
 | `apps/tasks`     | Cron-job initialization and scheduling runtime; it does not expose the old port-3002 API |
 | `apps/websocket` | tRPC WebSocket subscriptions on port 3001                                                |
 | `apps/workshop`  | Go/PocketBase Workshop service and provider integration                                  |
 
-`pnpm dev` runs only `@homarr/nextjs`. Use `pnpm --filter @homarr/tasks dev`, `pnpm --filter @homarr/websocket dev`, or `pnpm dev:docs` when a task needs those runtimes.
+`bun run dev` runs only `@homarr/nextjs`. Use `bun run --filter @homarr/tasks dev`, `bun run --filter @homarr/websocket dev`, or `bun run dev:docs` when a task needs those runtimes.
 
-In production, `apps/nextjs/src/instrumentation-node.ts` starts the tasks and WebSocket runtimes inside the Node process. Nginx listens on port 7575, proxies `/websockets` to port 3001, and sends other traffic to port 3000. Redis can run internally or externally.
+In production, `apps/nextjs/src/instrumentation-node.ts` starts the tasks and WebSocket runtimes inside the Bun process. Nginx listens on port 7575, proxies `/websockets` to port 3001, and sends other traffic to port 3000. Redis can run internally or externally.
 
 ## Package map
 
@@ -34,7 +34,7 @@ In production, `apps/nextjs/src/instrumentation-node.ts` starts the tasks and We
 
 ### Data, identity, and transport
 
-- `db`: Drizzle schemas, queries, migrations, and three database drivers.
+- `db`: Drizzle schemas, queries, migrations, and SQLite and PostgreSQL drivers.
 - `auth`: Auth.js/NextAuth configuration, sessions, providers, and API keys.
 - `api`: tRPC routers, contexts, MCP metadata extraction, OpenAPI, and client/server entrypoints.
 - `redis`: Redis clients, pub/sub channels, and caches.
@@ -57,7 +57,7 @@ In production, `apps/nextjs/src/instrumentation-node.ts` starts the tasks and We
 - `settings`, `spotlight`, `notifications`, `onboarding`: cross-feature UI flows.
 - `widgets`: widget definitions, dynamic component loaders, and shared widget UI.
 - `translation`: next-intl configuration and locale catalogs.
-- `cli`: Node operations CLI. `tools/homarr-dev` is the separate Go developer CLI.
+- `cli`: Bun operations CLI. `tools/homarr-dev` is the separate Go developer CLI.
 
 ## Dependency direction
 
@@ -78,7 +78,7 @@ Prefer these directions; verify the exact dependency in package manifests before
 
 ### Databases
 
-Drizzle schemas live in parallel files under `packages/db/schema/`. `DB_DRIVER` selects `better-sqlite3`, `mysql2`, or `node-postgres`; migrations live in matching directories under `packages/db/migrations/`. Apply schema behavior consistently across all supported drivers unless the task is explicitly driver-specific.
+Drizzle schemas live in `packages/db/schema/`. `DB_DRIVER` selects `better-sqlite3` or `node-postgres`; MySQL and MariaDB are no longer runtime drivers in v2. Existing MySQL installations must use the documented converter before upgrading. Migrations live under `packages/db/migrations/sqlite/` and `packages/db/migrations/postgresql/`.
 
 ### Widgets
 
@@ -103,8 +103,8 @@ User routes live below `apps/nextjs/src/app/[locale]/`; the locale segment does
 ## Commands and conventions
 
 - Read current scripts from the root or package `package.json`; avoid caching commands that do not exist.
-- Use `pnpm dev` for Next.js, `pnpm dev:docs` for docs, and `pnpm dev:cli -- <args>` for the Go developer CLI.
-- Use `pnpm docker:dev:up` for the Redis development dependency.
-- Use package-filtered typechecks or focused tests for the touched behavior.
+- Use `bun run dev` for Next.js, `bun run dev:docs` for docs, and `bun run dev:cli -- <args>` for the Go developer CLI.
+- Use `bun run docker:dev:up` for the Redis development dependency.
+- Follow the Testing section in `AGENTS.md` for test creation and validation scope.
 - Use `~/*` only inside the Next.js app. Use public `@homarr/*` entrypoints across package boundaries.
 - Keep Mantine application styles separate from the Tailwind-based docs app.

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

@@ -1,11 +1,11 @@
 ---
 name: documentation-sync
-description: Write concise Homarr docs for advanced users, covering only hidden capabilities and information not evident from the UI. Use when that information changes or existing guidance becomes inaccurate; skip obvious controls and routine fixes.
+description: Write Homarr docs only when users need information to set up, use, or troubleshoot the app. Skip routine, obvious, or self-explanatory changes.
 ---
 
 # Documentation Sync
 
-Apply the audience and scope rules in `AGENTS.md` first. Before adding a passage, identify what an advanced user could not learn directly from the interface. If there is no such information, omit it.
+Apply the audience and scope rules in `AGENTS.md` first. Documentation exists only for information users need to set up, use, or troubleshoot Homarr. A code, UI, or API change alone does not warrant documentation; if a user does not need to know it, do not add it.
 
 For hidden capabilities such as the advanced widget feature, explain discovery, activation, and non-obvious behavior. For visible standard controls such as Delete, omit narration of what the label already conveys. Use the shortest explanation that preserves necessary technical detail; remove redundant prose in the passage being edited.
 
@@ -13,6 +13,8 @@ When an update is warranted, inspect adjacent pages for structure and types, not
 
 ## Locate a needed update
 
+These are destinations for warranted updates, not triggers to add documentation:
+
 | Code change                         | Documentation target                                                 |
 | ----------------------------------- | -------------------------------------------------------------------- |
 | New integration                     | `apps/docs/docs/integrations/<slug>/index.mdx` and `index.ts`        |
@@ -48,8 +50,8 @@ For a widget:
 
 ## Completion criteria
 
-1. Every passage adds information an advanced user cannot reasonably infer from the interface. Remove obvious, repetitive, or unnecessary prose.
+1. Every passage adds information a user needs and cannot reasonably infer from the interface. Remove obvious, repetitive, or unnecessary prose.
 2. Keep names, defaults, paths, screenshots, links, and prerequisites consistent with code.
 3. Update every affected page and remove superseded guidance.
-4. Run the narrowest useful docs validation. Use `pnpm turbo build --filter=@homarr/docs` when links, MDX, generated definitions, or navigation can fail; otherwise run the docs package formatter on touched files.
-5. Treat broken links and anchors as failures; Docusaurus checks them strictly.
+4. Run the narrowest useful docs validation. Use `bun run turbo build --filter=@homarr/docs` when links, MDX, generated definitions, or navigation can fail; otherwise run the docs package formatter on touched files.
+5. Treat broken links and anchors as failures; run `bun run --filter @homarr/docs validate:links` after the static build.

.agents/skills/documentation-sync/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Homarr Documentation Sync"
-  short_description: "Keep user-facing docs aligned with code"
-  default_prompt: "Use $documentation-sync to map this Homarr code change to the required documentation updates."
+  short_description: "Document only what users need to know"
+  default_prompt: "Use $documentation-sync only when users need new or corrected information to set up, use, or troubleshoot Homarr."

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

@@ -5,39 +5,54 @@ description: Author, validate, preview, test, install, or configure API-backed H
 
 # Homarr Custom Widget
 
-Author one widget or a coordinated set of widgets. Load only needed release-matched context. Run lifecycle tools alone; independent reads may run together. For a set, research once and finish each widget's validation, evidence, and persistence before the next.
+Author requested widgets with release context; validate, test, persist, and return artifacts.
 
-1. Read primary API documentation. Use web search when documentation is not supplied or may have changed.
-2. Create credential-free definitions with keyed `sources`, `requests`, optional `options`, and safe JSX `template`.
-3. While drafting, use `customWidget_validateTemplate` for focused JSX diagnostics without resending the manifest.
-4. Send the definition once to `customWidget_previewCreate` and test its queries/actions. For a JSX-only fix, validate, call `customWidget_previewReviseTemplate` with its session, and retest; it inherits the manifest and resets evidence. Create a preview only for source/request/option changes.
-5. Configure deployment-specific source URLs and credentials through Homarr; never repeat plaintext.
-6. Persist each exact final tested preview with `customWidget_createFromPreview`. Do not resend a large definition through `customWidget_create` when a preview session is available.
+- Read primary API docs when missing/changed. Samples and successful previews are binding; load only needed schema, runtime,
+  security, or component context.
+- Batch unknown component searches/details. `contextAlreadyLoaded` reuses context; `phaseComplete` advances. Stop only for
+  genuine provider/model, lifecycle-service, or workbench-closure failure.
+- Community widgets use `customWidget_workshopSearch`, `customWidget_workshopGet`, and
+  `customWidget_workshopInstall`; configure and persist.
 
-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. Humanize numeric enums with indexed literal label arrays, omit absent numeric values instead of inventing zero, and label timestamp timezones. Give recoverable load errors and empty states a clear refresh or retry path.
+Return one fenced `json` block with the complete definition; keep evidence prose outside it. The definition has keyed
+`sources`, `requests`, `template`, and optional `options`; actions are requests with `kind: "action"`.
 
-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. Render load queries from `data` and `status` with `RefreshButton`; reserve `SubFetch` for manual parameterized queries. Templates read `data`, `status`, `options`, and temporary `inputs`.
+- `sources.default` is required. HTTP has `baseUrl`, `networkScope`, and credential-free `auth`; localhost/loopback requires
+  `networkScope: "loopback"`; never widen an explicit scope. Saved sources use `type: "integration"`/`integrationKind`;
+  Homarr holds credentials.
+- Saved integrations: discover kinds/full-access entries with `integration_getKinds`/`integration_all`, bind `integrationId`
+  before preview, omit URL/auth, and keep non-GET requests as actions.
+- Paths are slash-prefixed: strings use `{option:name}`/`{param:name}`; query/body uses `{"$option":"name"}`/`{"$param":"name"}`.
+  Loads use `trigger: "load"`; manual helpers use `trigger: "manual"`.
+- Actions stay manual; preserve `confirmation`, `permission`, and `invalidates`; DELETE requires full permission/confirmation.
+  `$param` is manual-only; `$option` may drive loads.
+- Load data.requestId/status.requestId with RefreshButton; status.requestId?.ok === false is error. Manual SubFetch never
+  populates data/status; its child receives (result, metadata) and renders its fields.
+- Options have `label`, `control`, `default`; installation config is `options.name`, never `inputs`. Request-bound TextInput,
+  Select, NumberInput, Pagination use literal `bind` + default and manual `SubFetch params` map `inputs.<name>` to `$param`.
+  Dependent pagination uses `defaultValue={1}`/`resetKey={inputs.query}`. Remove controls without an option/request/helper; guard arrays/nested with `??`;
+  preserve documented timezone values; use UTC only when the contract says UTC.
+- Templates are one expression: no imports, hooks, refs, raw HTML/events, browser requests, eval, recursion, IIFEs,
+  statement blocks, or arbitrary functions. Use registered component names; `Icon` may alias `TablerIcon`. Keep hierarchy,
+  theme tokens, useful states, and narrow/wide layouts purposeful.
 
-For a bound control that depends on another input, declare its default and set `resetKey` to that scalar dependency. For example, `<Pagination bind="page" defaultValue={1} resetKey={inputs.search} />` restores page 1 when a search changes without fetching by itself.
+## Bounded lifecycle
 
-`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)`; callback names must not shadow the reserved roots `data`, `status`, `options`, or `inputs`. Never author `onClick` or a fetch callback. Use `Icon` or `TablerIcon` with a `name`; never invent an `IconFoo` component.
+1. Build a credential-free definition from request, verified context, and sample. Preserve a migration's API path, method,
+   body, options, and behavior; omit unknown requests rather than guessing.
+2. Send the coherent complete definition directly to `customWidget_previewCreate`; it validates both manifest and JSX.
+   Use `customWidget_validateTemplate` only for isolated JSX diagnostics, never as a preview prerequisite. Use
+   `customWidget_previewReviseTemplate` for JSX-only corrections after a preview exists. In the Assistant wrapper, multiline
+   JSX uses `templateLines` and preview creation receives the complete definition.
+3. Test every returned query/simulated action once, batching independent queries. On a concrete schema/preview error, fix only
+   that field and retry `customWidget_previewCreate` with the corrected definition; use `customWidget_previewReviseTemplate`
+   only for JSX errors after a preview exists. Stop only for genuine provider/model, lifecycle-service, or
+   workbench-closure failure.
+4. If `previewCreate` used `definitionId`, persist with `customWidget_updateFromPreview`; otherwise use
+   `customWidget_createFromPreview`. Follow create `nextAction` once. Configure credentials in Homarr; never repeat plaintext
+   secrets.
 
-Plan capabilities. Use one `customWidget_findComponents` search per job. Batch selected non-obvious binding or interaction documentation with `customWidget_getComponents`; reserve `customWidget_getComponent` for one unknown-prop repair. Failed validation reopens discovery; otherwise search only for a missing capability. The full catalog is for broad exploration; load at most one example. Context never limits composition. Prefer clear hierarchy, responsive grids, divided lists, and aligned actions over nested row cards.
+## Delivery
 
-Do not simplify a useful workflow merely because the template is interpreted. Freely compose any supported installed components with multiple sources, requests, options, `choicesFrom`, bound filters, charts, responsive detail areas, manual queries, and safe actions when they improve the user's job. Complexity must remain purposeful rather than decorative.
-
-Polish with a divided list or responsive media grid. Make one metric/action asymmetrically primary; keep headers compact, identity/state clear, metadata quiet, and one badge. At base artwork fills its row and caps above xs; never combine full-width media and nowrap.
-
-Make initial states actionable and wrap variable labels/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.
-
-For a community widget, use `customWidget_workshopSearch`, `customWidget_workshopGet`, then `customWidget_workshopInstall`; configure its source securely. Preview configuration expires, so create before persisting configuration.
-
-Reference routing:
-
-- Load `schema` once before a new manifest; otherwise only for concrete request or option ambiguity.
-- Load `runtime` for bound inputs, manual queries, actions, or other interaction.
-- Load `security` once for any authenticated source or mutation, or to resolve a URL or interpreter limitation.
-
-Repository installations expose these as files under `references/`. MCP clients can call `customWidget_getReference` or read `homarr://custom-widgets/references/{name}` instead of loading every reference.
+Report actual lifecycle results. If unavailable, add one post-artifact `Unverified:` line naming missing validation, preview,
+renderer, or persistence. Never claim rendering/persistence from schema checks.

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

@@ -1,13 +1,13 @@
 # Runtime
 
-Templates read `data.requestId`, `status.requestId`, `options.name`, and temporary `inputs.name`. Status is `{ loading, ok, status, statusText, error }`. Render load queries directly from `data` and `status` with `RefreshButton`; never wrap them in `SubFetch`.
+Load-query templates read `data.requestId` and `status.requestId`, plus `options.name` and temporary `inputs.name`. Manual `SubFetch` results stay local to that instance and never populate `data`/`status`; render them in its child callback. Status is `{ loading, ok, status, statusText, error }`. Render load queries directly from `data` and `status` with `RefreshButton`; never wrap them in `SubFetch`.
 
-`bind="search"` creates an in-memory input. It is never persisted. Supply invocation values only through `params`, for example:
+`bind` is temporary; manual request values go in `params` and map to `$param`:
 
 ```jsx
 <TextInput bind="search" label="Search" />
-<Pagination bind="page" resetKey={inputs.search} defaultValue={1} total={5} />
-<SubFetch requestId="search" trigger="manual" params={{ query: inputs.search }}>
+<NumberInput bind="page" label="Page" defaultValue={1} resetKey={inputs.search} min={1} />
+<SubFetch requestId="search" trigger="manual" params={{ query: inputs.search ?? "", page: inputs.page ?? 1 }}>
   {(result) => <Stack>{(result.results ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
 </SubFetch>
 ```
@@ -18,11 +18,11 @@ Manual queries require `trigger: "manual"` on request and `SubFetch`; otherwise
 
 Inside a successful manual result, `<RefreshButton requestId="search" label="Run again" />` reruns the same parameters.
 
-When a manual SubFetch request ID, parameters, or effective definition changes, Homarr immediately hides its prior result and returns to the trigger. It cannot fetch the new parameters until the user triggers it again.
+When a manual SubFetch ID, params, or definition changes, Homarr hides the prior result and returns to the trigger; new params fetch only after triggering again.
 
-The `SubFetch` callback receives the entire JSON response exactly as previewed. If the response is `{ "results": [...] }`, render and map `result.results`; never map the envelope itself. Trace every rendered field from the preview response before persistence.
+Exact paths: load request ID `q` with raw preview body `B` -> `data.q === B`. `q=events` body`{"events":[...]}` -> `data.events.events`; do not flatten repeated keys. Manual `SubFetch` receives `B` as result -> `result.events`. Before persistence inspect core paths against preview; revise JSX and retest if mismatched
 
-Format timestamps with safe static helpers; never use `new Date`. Never invent a formatter component. Use `Date.toLocaleString(value, "en-US", "UTC")` plus a visible `UTC` label. Also available: `Date.toISOString`, `Date.toLocaleDateString`, and `Date.toLocaleTimeString`.
+Format timestamps with safe static helpers; never use `new Date`. Never invent a formatter component. Use `Date.toLocaleString(value, "en-US", documentedTimezone)` and label the documented timezone; if no timezone is documented, preserve the source value or omit any timezone label; use UTC only when the response contract says UTC. Also available: `Date.toISOString`, `Date.toLocaleDateString`, and `Date.toLocaleTimeString`.
 
 For compact numeric enums, index a literal label array with a fallback:
 
@@ -30,8 +30,8 @@ For compact numeric enums, index a literal label array with a fallback:
 <Text>{["Unknown", "Pending", "Ready"][(item.status ?? 1) - 1] ?? "Unknown"}</Text>
 ```
 
-Every stateful control must use `bind`, and its `inputs.<name>` value must feed a supported request/helper when it is meant to change remote data. For dependent pagination, declare `defaultValue={1}` and use `resetKey={inputs.search}` to restore page 1 when the query changes. If a control cannot affect the workflow through a binding, option, or runtime helper, render concise context instead of a dead control.
+Request-bound controls use literal `bind` plus a default (`defaultChecked` for Switch/Checkbox); pass `inputs.<name>` through manual `SubFetch params` to matching `$param`. Options are installation config via `options.name`, never `inputs`; dependent pagination uses `defaultValue={1}`/`resetKey={inputs.query}`. Remove dead controls.
 
-Callback parameters must not shadow the reserved roots `data`, `status`, `options`, or `inputs`. Use `<Icon name="refresh" />` or `<TablerIcon name="refresh" />`; never invent components such as `<IconFoo />`.
+Callback parameters must not shadow the reserved roots `data`, `status`, `options`, or `inputs`. Use registered component names returned by discovery; `Icon` is an accepted alias for canonical `TablerIcon`. Never invent components such as `<IconFoo />`.
 
 Use expression callbacks for supported collections and trusted slots. No callback blocks, IIFEs, authored recursion, or raw events. Regex is limited to safe string operations.

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

@@ -13,7 +13,7 @@ interface HomarrCustomWidgetV2 {
 }
 ```
 
-The object key `default` is the required source ID; `default` is not a property on a source. Source properties are `name?`, `baseUrl`, `networkScope`, and `auth?`:
+Key `default` is the required source ID, not a source property. Fields: `name?`, `baseUrl`, `networkScope`, `auth?`; localhost/loopback URLs require `networkScope: "loopback"`; never widen explicit scope:
 
 ```json
 {
@@ -40,10 +40,14 @@ The object key `default` is the required source ID; `default` is not a property
 }
 ```
 
-Auth is `none`, `bearer`, `basic`, `{ "type": "apiKeyHeader", "name": "X-Api-Key" }`, or `{ "type": "apiKeyQuery", "name": "api_key" }`. A request defaults to source `default`, kind `query`, method `GET`, trigger `load`, inherited auth, and view permission. Set `trigger: "manual"` for a parameterized query. An action defaults to manual and modify permission. DELETE uses full permission and confirmation. Do not use `load: false`.
+Saved sources use `{"type":"integration","integrationKind":"sonarr","integrationId":"saved-id"}`. Discover and bind a full-access entry before preview. Omit URL/auth; paths append to its URL, non-GET requests are actions, and exports omit `integrationId`.
 
-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.
+Auth is `none`, `bearer`, `basic`, `apiKeyHeader`, or `apiKeyQuery`. Requests default to source `default`, query/GET/load, inherited auth, and view permission. Use `load` for initial/current display and `manual` only for explicit interactions or invocation params. Actions are manual/modify; DELETE requires full permission and confirmation.
 
-Paths use `{option:name}` and `{param:name}`; query/body references use `{ "$option": "name" }` and `{ "$param": "name" }`. Constants stay primitive (`take: 10`); `$param` is only for manual helpers, never load queries. Names and types are inferred.
+JSON responses become their decoded value. Responses with `application/x-ndjson` become an array with one decoded object per non-empty line.
+
+Use real public API URLs and clear self-hosted placeholders. Homarr collects URL, scope, and credentials outside the manifest.
+
+Paths use `{option:name}`/`{param:name}`; query/body objects use `{"$option":"name"}`/`{"$param":"name"}`. `$param` is manual-only; `$option` may drive loads. Constants stay primitive.
 
 Every option has `label`, `control`, and `default`. Optional fields are `description`, `choices`, `choicesFrom`, `min`, `max`, `step`, `advanced`, and `group`.

.agents/skills/mcp-integration/SKILL.md

@@ -93,6 +93,6 @@ Register the smallest router that owns the enabled procedures. If a parent route
 1. Confirm the procedure still enforces its ordinary auth and permission boundary.
 2. Confirm `packages/api/src/mcp.ts` eagerly includes the procedure.
 3. Confirm the generated tool name, description, and JSON schema are unambiguous.
-4. Run the focused API MCP spec when the tool list or extraction changes: `pnpm test packages/api/src/test/mcp.spec.ts`.
-5. Run the focused route spec when protocol or transport behavior changes: `pnpm test apps/nextjs/src/app/api/mcp/[transport]/route.spec.ts`.
+4. When validating tool-list or extraction changes, use the focused API MCP spec: `bun run test packages/api/src/test/mcp.spec.ts`.
+5. When validating protocol or transport changes, use the focused route spec: `bun run test apps/nextjs/src/app/api/mcp/[transport]/route.spec.ts`.
 6. If manually probing `/api/mcp/<transport>`, use a scoped API key and avoid printing credentials or secret-bearing results.

.dockerignore

@@ -5,9 +5,18 @@ node_modules
 npm-debug.log
 README.md
 .next
+**/.output
 .turbo
-.pnpm-store
-**/.pnpm-store
+**/.turbo
+**/next-env.d.ts
+packages/db/migrations/*/migrate.cjs
+packages/cli/cli.cjs
+apps/tasks/tasks.cjs
+apps/tasks/tasks.css
+apps/websocket/wssServer.cjs
+apps/websocket/wssServer.css
+.bun-cache
+**/.bun-cache
 coverage
 **/coverage
 **/.docusaurus
@@ -23,3 +32,8 @@ apps/nextjs/.next
 .env
 .env.*
 !.env.example
+
+benchmark-results
+scripts/benchmarks/results
+**/__pycache__
+**/*.tsbuildinfo

.env.example

@@ -21,18 +21,6 @@ DB_DRIVER='better-sqlite3'
 # Container images use /appdata/db/db.sqlite by default instead.
 DB_URL=
 
-# Those are the two ways to use the mysql2 driver:
-# 1. Using the URL format:
-# DB_DRIVER='mysql2'
-# DB_URL='mysql://user:password@host:port/database'
-# 2. Using the connection options format:
-# DB_DRIVER='mysql2'
-# DB_HOST='localhost'
-# DB_PORT='3306'
-# DB_USER='username'
-# DB_PASSWORD='password'
-# DB_NAME='name-of-database'
-
 # The following is an example on how to use the node-postgres driver:
 # DB_DRIVER='node-postgres'
 # DB_URL='postgres://user:password@host:port/database'
@@ -91,6 +79,6 @@ HOMARR_WEBSITE_URL=https://homarr.dev
 # 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).
+# Whether demo mode is read-only. Defaults to true; Assistant conversation history remains writable for canned chats.
 # Set to false for writable preview deployments so the demo user can modify the dashboard.
 # DEMO_READ_ONLY=false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -25,6 +25,18 @@ body:
     attributes:
       label: Additional information
       description: Add any other information related to the bug here, screenshots if applicable.
+  - type: input
+    id: exactBuild
+    attributes:
+      label: Exact build or image
+      description: For preview or development builds, include the commit SHA or image digest. A moving tag such as v2 is not enough to identify the build.
+      placeholder: "Commit SHA, image digest, or release version"
+  - type: input
+    id: lastWorkingVersion
+    attributes:
+      label: Last working version
+      description: If this worked before, include the last version or build where you tried the same action. Leave blank if unknown.
+      placeholder: "Version or commit SHA"
   - type: dropdown
     id: version
     attributes:
@@ -33,6 +45,10 @@ body:
       options:
         # The below comment is used to insert a new version with on-release.yml
         #NEXT_VERSION#
+        - 2.2.0
+        - 2.1.2
+        - 2.0.0
+        - 1.77.0
         - 1.76.2
         - 1.76.1
         - 1.76.0

.github/ISSUE_TEMPLATE/custom_widget_bug.yml

@@ -0,0 +1,48 @@
+name: 🐞 Custom Widget bug
+description: Report a problem with a Custom JSX widget, its requests, preview, or editor
+title: "bug: custom widget "
+labels: ["needs triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Share a small reproduction so we can distinguish widget code, upstream API, and Homarr problems.
+        Remove API keys, passwords, tokens, cookies, authorization headers, private URLs, and personal data from everything you share, including exports and screenshots. Replace private hosts with `https://example.invalid` while preserving relevant paths and response structure.
+  - type: textarea
+    id: behavior
+    attributes:
+      label: Actual and expected behavior
+      description: Describe what happens and what you expected. Include the exact error text and a sanitized screenshot if useful.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Include the affected request or control, relevant widget options, and whether this occurs in Test, preview, or on the dashboard. For layout issues, include the widget size and desktop or mobile viewport.
+    validations:
+      required: true
+  - type: textarea
+    id: definition
+    attributes:
+      label: Sanitized widget definition
+      description: Paste or attach the exported JSON with sources, requests, options, and JSX template. Prefer the smallest definition that reproduces the problem. If export fails, include the relevant JSX and request configuration. Check for private URLs and sensitive data before sharing.
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Include the exact Homarr release, commit SHA, or image digest; installation method; browser/version; and desktop or mobile OS. For request issues, include the source type (HTTP or integration), integration kind, and upstream service version. Do not include server URLs or credentials.
+      placeholder: |
+        Homarr version / commit / image digest:
+        Installation method:
+        Browser and OS:
+        Source type, integration kind, and service version:
+    validations:
+      required: true
+  - type: textarea
+    id: diagnostics
+    attributes:
+      label: Sanitized API response and logs
+      description: For request or data issues, include the request ID, method, relative API path, HTTP status, and a small response sample preserving field names and types. Add relevant Homarr or browser console errors. Remove sensitive values and private URLs; leave blank for purely visual issues.

.github/act/README.md

@@ -3,18 +3,20 @@
 Install [Act](https://nektosact.com/installation/index.html) and ensure Docker is running, then use:
 
 ```bash
-pnpm ci:act:fast
-pnpm ci:act:docker
-pnpm ci:act:all
-pnpm ci:act:cleanup
+bun run ci:act:fast
+bun run ci:act:docker
+bun run ci:act:all
+bun run ci:act:cleanup
 ```
 
-`fast` runs the quality gate. `docker` and `all` run the gate followed by the single container build, E2E suite, and memory regression test. `cleanup` validates the manual cleanup path without calling GitHub. The wrapper supports regular clones and Git worktrees, including non-default Docker contexts. Linux dependencies are kept in Docker volumes instead of overwriting host `node_modules`. The first run downloads the Act runner and Playwright browser dependencies.
+`fast` runs the database checks and quality gate and requires an `origin/dev` tracking ref. `docker` and `all` use the manual validation event to run those checks, build the container once, and run the converter boot/restart smoke test. `cleanup` validates the manual cleanup path without calling GitHub. The wrapper supports regular clones and Git worktrees, including non-default Docker contexts. Linux dependencies are kept in Docker volumes instead of overwriting host `node_modules`. The first run downloads the Act runner and Playwright browser dependencies.
+
+For rootless Docker, set `ACT_TESTCONTAINERS_HOST` to a host address reachable from the runner when loopback callbacks are unavailable.
 
 Remote caching is optional locally. Copy `.github/act/.secrets.example` to `.github/act/.secrets`, populate it with rotated credentials, and run with:
 
 ```bash
-ACT_SECRET_FILE=.github/act/.secrets pnpm ci:act:all
+ACT_SECRET_FILE=.github/act/.secrets bun run ci:act:all
 ```
 
 Act never publishes or deletes GHCR images. The secret file is ignored by Git.

.github/actions/extract-build-artifact/action.yaml

@@ -19,11 +19,6 @@ inputs:
 runs:
   using: "composite"
   steps:
-    - name: Prebuilt debian dependencies
-      uses: ./.github/actions/prebuilt-debian
-      id: prebuilt-debian
-      with:
-        architecture: ${{ inputs.architecture }}
     - name: Start docker container for ${{ inputs.architecture }}
       run: |
         docker run --name homarr \
@@ -43,8 +38,6 @@ runs:
       shell: bash
     - name: Extract source from ${{ inputs.architecture }} container (debian)
       run: |
-        docker cp ${{ steps.prebuilt-debian.outputs.path }}/. homarr:/app/build && \
-        docker cp ${{ steps.prebuilt-debian.outputs.path }}/. homarr:/app/node_modules/better-sqlite3/build/Release && \
         docker exec homarr tar -czf extraction-debian.tar.gz -C /app . && \
         docker cp homarr:/app/extraction-debian.tar.gz ${{ runner.temp }}/extraction/${{ inputs.architecture }}/build-debian-${{ inputs.architecture }}.tar.gz
       shell: bash

.github/pull_request_template.md

@@ -10,7 +10,7 @@
 - [ ] Pull request targets the intended base branch (`dev` by default; `release/v2` for v2 release work)
 - [ ] Commits follow the [conventional commits guideline](https://www.conventionalcommits.org/en/v1.0.0/)
 - [ ] No shorthand variable names are used (for example, `x`, `y`, `i`, or abbreviations)
-- [ ] User-facing changes include matching documentation updates under `apps/docs`
+- [ ] Documentation under `apps/docs` is updated only when users need new or corrected information to use the app
 - [ ] When using AI, no temporary files are checked in and the code style follows the rest of the project
 
 **When contributing a new integration or widget:**

.github/renovate.json5

@@ -6,11 +6,6 @@
       matchPackageNames: ["^@homarr/"],
       enabled: false,
     },
-    // Reenable once https://github.com/privatenumber/tsx/issues/737 is fixed
-    {
-      matchPackageNames: ["tsx"],
-      enabled: false,
-    },
     // Reenable once bug with undici v8 is fixed (https://github.com/homarr-labs/homarr/issues/5467)
     {
       matchPackageNames: ["undici"],
@@ -22,11 +17,10 @@
       automerge: true,
     },
     {
-      // disallow automerge for allowBuilds dependencies (native builds need manual verification)
+      // disallow automerge for trustedDependencies (native builds need manual verification)
       matchPackageNames: [
         "@tree-sitter-grammars/tree-sitter-yaml",
         "bcrypt",
-        "better-sqlite3",
         "cpu-features",
         "esbuild",
         "sharp",
@@ -37,12 +31,6 @@
       automerge: false,
     },
   ],
-  // Updates lockfile for prebuilt-debian after if package.json is updated, otherwise only root lockfile is updated
-  postUpgradeTasks: {
-    commands: ["cd deployments/prebuilt-debian && pnpm install --ignore-workspace --lockfile-only"],
-    fileFilters: ["deployments/prebuilt-debian/pnpm-lock.yaml"],
-    executionMode: "update",
-  },
   updateInternalDeps: true,
   rangeStrategy: "bump",
   automerge: false,

.github/workflows/autofix.yml

@@ -32,4 +32,4 @@ jobs:
         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 --
+            | xargs -0 -r bun x oxfmt --check --no-error-on-unmatched-pattern --

.github/workflows/ci.yml

@@ -10,6 +10,8 @@ on:
   push:
     branches: [main, dev, beta, next, v2, release/v2]
   merge_group:
+  release:
+    types: [published]
   workflow_dispatch:
     inputs:
       operation:
@@ -47,9 +49,15 @@ env:
   PREVIEW_IMAGE: ghcr.io/homarr-labs/homarr-test
 
 jobs:
+  database-validation:
+    name: Database validation
+    if: github.event_name != 'pull_request_target' && (github.event_name != 'release' || startsWith(github.event.release.tag_name, 'v2.')) && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
+    uses: ./.github/workflows/database.yml
+
   fast-gate:
     name: Fast gate
-    if: github.event_name != 'pull_request_target' && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
+    needs: database-validation
+    if: ${{ !cancelled() && github.event_name != 'pull_request_target' && (github.event_name != 'release' || startsWith(github.event.release.tag_name, 'v2.')) && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup') }}
     runs-on: ubuntu-latest
     timeout-minutes: 20
     env:
@@ -59,8 +67,12 @@ jobs:
       TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
       TURBO_SCM_BASE: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before || 'HEAD~1' }}
       TURBO_SCM_HEAD: ${{ github.sha }}
-      TURBO_PLATFORM: linux/amd64
     steps:
+      - name: Require database validation
+        env:
+          DATABASE_RESULT: ${{ needs.database-validation.result }}
+        run: test "$DATABASE_RESULT" = success
+
       - uses: actions/checkout@v7
         if: "!env.ACT"
         with:
@@ -79,44 +91,47 @@ jobs:
 
       - name: Setup
         uses: ./tooling/github/setup
+        with:
+          next-cache: "all"
+          turbo-cache: "true"
 
       - name: Copy environment defaults
         run: cp .env.example .env
 
-      - name: Lint, typecheck, and build affected workspaces
-        run: pnpm turbo run lint typecheck build --affected --continue=dependencies-successful --concurrency=2
+      - name: Lint, typecheck, and build workspaces
+        run: |
+          scope=(--affected)
+          if [[ "$GITHUB_EVENT_NAME" == "workflow_dispatch" ]]; then
+            scope=()
+          fi
+          bun run turbo run lint typecheck build "${scope[@]}" --continue=dependencies-successful --concurrency=2
 
       - name: Validate workspace configuration
-        run: pnpm lint:ws
+        run: bun run lint:ws
 
       - name: Validate Custom Widget architecture
-        run: pnpm check:custom-widgets
+        run: bun run check:custom-widgets
 
       - name: Validate checked-in OpenAPI schema
-        run: pnpm check:openapi
+        run: bun run check:openapi
 
       - name: Validate Custom Widget bundle budget
         run: |
-          pnpm turbo run build --filter=@homarr/nextjs
-          pnpm check:custom-widget-bundle
+          bun run turbo run build --filter=@homarr/nextjs
+          bun run check:custom-widget-bundle
 
   container:
-    name: Container build
-    # Same-repository previews already build amd64; only build a fallback when no digest is available.
+    name: Container and migration smoke
+    # Legacy converter verification is opt-in, not a release publication gate.
     needs: [fast-gate, preview-amd64]
     if: |
       !cancelled() && needs.fast-gate.result == 'success' &&
-      needs.preview-amd64.result != 'failure' && needs.preview-amd64.outputs.digest == '' &&
-      (
-        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 == 'workflow_dispatch' && inputs.operation == 'validate'
     runs-on: ubuntu-latest
-    timeout-minutes: 20
+    timeout-minutes: 30
     permissions:
       contents: read
+      packages: read
     steps:
       - uses: actions/checkout@v7
         if: "!env.ACT"
@@ -124,6 +139,18 @@ jobs:
           persist-credentials: false
           ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
 
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - 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-e2e
+
       - name: Set up Docker Buildx
         if: needs.preview-amd64.outputs.digest == '' && !env.ACT
         uses: docker/setup-buildx-action@v4
@@ -137,7 +164,9 @@ jobs:
           platforms: linux/amd64
           load: true
           push: false
-          tags: homarr-ci
+          tags: |
+            homarr-ci
+            homarr-e2e
           labels: |
             org.opencontainers.image.source=${{ github.server_url }}/${{ github.repository }}
             org.opencontainers.image.revision=${{ github.sha }}
@@ -158,14 +187,41 @@ jobs:
           TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
           TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
         run: |
-          secret_args=()
-          for secret in TURBO_API TURBO_TEAM TURBO_TOKEN TURBO_REMOTE_CACHE_SIGNATURE_KEY; do
-            if [ -n "${!secret:-}" ]; then
-              secret_args+=(--secret "id=${secret},env=${secret}")
-            fi
-          done
-          DOCKER_BUILDKIT=1 docker build --platform linux/amd64 \
-            --tag homarr-ci "${secret_args[@]}" .
+          bash tooling/github/docker-build.sh --platform linux/amd64 \
+            --tag homarr-ci --tag homarr-e2e .
+
+      - name: Cache Playwright browsers
+        if: "!env.ACT"
+        id: playwright-cache
+        uses: actions/cache@v6
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-${{ runner.os }}-${{ hashFiles('bun.lock') }}
+
+      - name: Install Playwright Chromium
+        if: steps.playwright-cache.outputs.cache-hit != 'true' || env.ACT
+        run: bun x playwright install --with-deps chromium
+
+      - name: Install Playwright system deps
+        if: steps.playwright-cache.outputs.cache-hit == 'true'
+        run: bun x playwright install-deps chromium
+
+      - name: Install standalone converter test dependencies
+        run: bun install --cwd tools/mysql-to-sqlite --frozen-lockfile
+
+      - name: Verify converted database boots and survives restart
+        env:
+          NODE_ENV: development
+          CI: "true"
+        run: bun x vitest run --project e2e e2e/mysql-conversion.spec.ts --maxWorkers 1
+
+      - name: Upload E2E artifacts
+        if: failure() && !env.ACT
+        uses: actions/upload-artifact@v7
+        with:
+          name: playwright-report
+          path: e2e/test-results/
+          retention-days: 7
 
   preview-amd64:
     name: Build amd64 preview image

.github/workflows/database.yml

@@ -0,0 +1,103 @@
+name: Database migrations
+
+on:
+  workflow_call:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+env:
+  NODE_ENV: development
+  CI: "true"
+  SKIP_ENV_VALIDATION: "true"
+  TURBO_TELEMETRY_DISABLED: "1"
+
+jobs:
+  changes:
+    runs-on: ubuntu-latest
+    outputs:
+      migrations: ${{ steps.select.outputs.migrations }}
+    steps:
+      - uses: actions/checkout@v7
+        if: "!env.ACT"
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+      - name: Select database checks
+        id: select
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          BASE_SHA: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before }}
+        shell: bash
+        run: |
+          migrations=false
+          if [[ "$EVENT_NAME" != pull_request && "$EVENT_NAME" != merge_group && "$EVENT_NAME" != push ]] ||
+             [[ -z "$BASE_SHA" || "$BASE_SHA" =~ ^0+$ ]] ||
+             ! git cat-file -e "$BASE_SHA^{commit}" 2>/dev/null; then
+            migrations=true
+          else
+            changed_files=$(mktemp)
+            trap 'rm -f "$changed_files"' EXIT
+            comparison="$BASE_SHA...HEAD"
+            if [[ "$EVENT_NAME" = push ]]; then comparison="$BASE_SHA..HEAD"; fi
+            git diff --name-only -z "$comparison" > "$changed_files"
+            while IFS= read -r -d '' file; do
+              case "$file" in
+                packages/db/*|packages/core/src/infrastructure/db/*|packages/core/src/infrastructure/certificates/*|packages/auth/*|packages/api/src/router/onboard*|packages/api/src/router/test/onboard*|packages/onboarding/*|apps/nextjs/src/app/api/backup/*|apps/nextjs/src/app/*/init/*|Dockerfile|scripts/run.sh|scripts/entrypoint.sh|deployments/*|package.json|packages/core/package.json|packages/common/package.json|packages/definitions/package.json|packages/server-settings/package.json|packages/validation/package.json|mise.toml|bun.lock|bunfig.toml|patches/*|vitest*|tooling/github/*|.github/workflows/database.yml|.github/workflows/ci.yml)
+                  migrations=true
+                  ;;
+              esac
+            done < "$changed_files"
+          fi
+          echo "migrations=$migrations" >> "$GITHUB_OUTPUT"
+
+  journals:
+    name: Migration journals
+    needs: changes
+    if: needs.changes.outputs.migrations == 'true'
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+        if: "!env.ACT"
+        with:
+          persist-credentials: false
+      - uses: ./tooling/github/setup
+      - run: bun x vitest run --project db-node packages/db/test/migration-journal.spec.ts
+
+  migrations:
+    name: SQLite and PostgreSQL migrations
+    needs: changes
+    if: needs.changes.outputs.migrations == 'true'
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v7
+        if: "!env.ACT"
+        with:
+          persist-credentials: false
+      - uses: ./tooling/github/setup
+      - name: Reject retired database configuration
+        run: bun x vitest run --project dom packages/core/src/infrastructure/db/env.spec.ts
+      - run: bun x vitest run --project db-node --project integration packages/db/test/sqlite-migration.spec.ts packages/db/test/postgresql-migration.spec.ts packages/db/proxy-reader.integration.spec.ts --maxWorkers 1
+
+  database-gate:
+    name: Database gate
+    needs: [changes, journals, migrations]
+    if: always()
+    runs-on: ubuntu-latest
+    steps:
+      - name: Require selected database checks
+        env:
+          CHANGES: ${{ needs.changes.result }}
+          JOURNALS: ${{ needs.journals.result }}
+          MIGRATIONS: ${{ needs.migrations.result }}
+          RUN_MIGRATIONS: ${{ needs.changes.outputs.migrations }}
+        run: |
+          test "$CHANGES" = success
+          test "$RUN_MIGRATIONS" = true || test "$RUN_MIGRATIONS" = false
+          if [ "$RUN_MIGRATIONS" = true ]; then
+            test "$JOURNALS" = success
+            test "$MIGRATIONS" = success
+          fi

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

@@ -63,13 +63,10 @@ jobs:
         with:
           fetch-depth: 0
           persist-credentials: false
-      - uses: pnpm/action-setup@v6
-        if: env.SKIP_RELEASE == 'false'
-      - uses: actions/setup-node@v6
+      - uses: oven-sh/setup-bun@v2
         if: env.SKIP_RELEASE == 'false'
         with:
-          node-version: 24.18.0
-          package-manager-cache: false
+          bun-version: 1.4.2
       - name: Verify major release intent
         if: env.SKIP_RELEASE == 'false'
         run: |
@@ -92,7 +89,7 @@ jobs:
           exit 1
       - name: Install dependencies
         if: env.SKIP_RELEASE == 'false'
-        run: pnpm install --frozen-lockfile
+        run: bun install --frozen-lockfile
       - name: Run Semantic Release
         if: env.SKIP_RELEASE == 'false'
         env:
@@ -102,7 +99,7 @@ jobs:
           GIT_COMMITTER_NAME: "Releases Homarr"
           GIT_COMMITTER_EMAIL: "175486441+homarr-releases[bot]@users.noreply.github.com"
         run: |
-          pnpm release
+          bun run release
       - name: Read semver output
         # We read the last tag either from the created release or from the current branch, this is to rerun the deployment job for the currently released version when it failed
         if: env.SKIP_RELEASE == 'false' || github.ref_name == 'main' || github.ref_name == 'beta'
@@ -123,15 +120,19 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
           UPSTREAM_BRANCH: ${{ github.ref_name == 'main' && 'dev' || 'next' }}
+          RELEASE_REF: ${{ steps.read-git-ref.outputs.ref }}
         run: |
           git config user.name "Releases Homarr"
           git config user.email "175486441+homarr-releases[bot]@users.noreply.github.com"
-          git remote set-url origin https://x-access-token:${{ steps.obtainToken.outputs.token }}@github.com/${{ github.repository }}.git
-          git fetch origin ${{ env.UPSTREAM_BRANCH }}
-          git checkout ${{ env.UPSTREAM_BRANCH }}
-          git pull origin ${{ env.UPSTREAM_BRANCH }}
-          git rebase ${{ github.ref_name }}
-          git push origin ${{ env.UPSTREAM_BRANCH }}
+          git remote set-url origin "https://x-access-token:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
+          git fetch origin "$UPSTREAM_BRANCH"
+
+          # Dependency installation can modify generated files in the release checkout.
+          sync_dir="$(mktemp -d "${RUNNER_TEMP}/homarr-release-sync.XXXXXX")"
+          trap 'git worktree remove --force "$sync_dir"' EXIT
+          git worktree add --detach "$sync_dir" FETCH_HEAD
+          git -C "$sync_dir" merge --no-edit "$RELEASE_REF"
+          git -C "$sync_dir" push origin "HEAD:${UPSTREAM_BRANCH}"
   build-amd64:
     name: Build docker image for amd64
     needs: release

.github/workflows/deployment-docs.yml

@@ -5,7 +5,13 @@ on:
     branches: ["dev"]
     paths:
       - "apps/docs/**"
-      - "packages/definitions/src/docs/**"
+      - "packages/**"
+      - "tooling/**"
+      - "tools/motion-reel/three/**"
+      - "package.json"
+      - "bun.lock"
+      - "bunfig.toml"
+      - "turbo.json"
       - ".github/workflows/deployment-docs.yml"
   workflow_dispatch:
 
@@ -33,16 +39,24 @@ jobs:
       - uses: actions/checkout@v7
       - name: Setup
         uses: ./tooling/github/setup
+        with:
+          next-cache: "docs"
+          turbo-cache: "true"
       - name: Build docs
-        run: pnpm turbo build --filter=@homarr/docs
+        run: bun run turbo run build --filter=@homarr/docs
         env:
           CI: "true"
+      - name: Validate exported links and search
+        run: |
+          bun run --filter @homarr/docs validate:links
+          bun run --filter @homarr/docs verify:search
+          bun run --filter @homarr/docs verify:seo
       - name: Setup Pages
         uses: actions/configure-pages@v6
       - name: Upload pages artifact
         uses: actions/upload-pages-artifact@v5
         with:
-          path: "apps/docs/build"
+          path: "apps/docs/out"
 
   deploy:
     runs-on: ubuntu-latest

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

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

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

@@ -28,12 +28,12 @@ jobs:
 
       - name: Dump contributors
         working-directory: apps/docs
-        run: pnpm api-dump-contributors
+        run: bun run api-dump-contributors
 
       - name: Commit updated contributors
         uses: EndBug/add-and-commit@v10
         with:
-          add: "apps/docs/static"
+          add: "apps/docs/public"
           default_author: github_actor
           message: "chore(docs): update contributors"
           push: true

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

@@ -27,12 +27,12 @@ jobs:
         run: cp .env.example .env
 
       - name: Generate and validate OpenAPI spec
-        run: pnpm scripts:update-openapi
+        run: bun run scripts:update-openapi
 
       - name: Commit updated spec
         uses: EndBug/add-and-commit@v10
         with:
-          add: "apps/docs/static/api/"
+          add: "apps/docs/public/api/"
           default_author: github_actor
           message: "chore(docs): update OpenAPI spec"
           push: true

.github/workflows/on-pr-renovate-validate.yml

@@ -12,8 +12,15 @@ jobs:
   renovate-validate:
     runs-on: ubuntu-latest
     timeout-minutes: 2
+    env:
+      # The optional RE2 addon uses V8 APIs; validation can use JavaScript regexes.
+      RENOVATE_X_IGNORE_RE2: "true"
     steps:
       - uses: actions/checkout@v7
+        if: "!env.ACT"
+      - uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.4.2
       - run: |
-          npx --yes --package renovate -- \
+          bun x --package renovate \
               renovate-config-validator --strict .github/renovate.json5

.github/workflows/on-release.yml

@@ -25,7 +25,7 @@ jobs:
           ref: dev
       - name: Setup
         uses: ./tooling/github/setup
-      - run: pnpm run scripts:update-bug-report-template
+      - run: bun run scripts:update-bug-report-template
         env:
           NEXT_VERSION: ${{ github.event.release.tag_name }}
 

.github/workflows/update-contributors.yml

@@ -29,16 +29,12 @@ jobs:
         uses: actions/checkout@v7
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-
-      - uses: pnpm/action-setup@v6
-      - name: Use Node.js
-        uses: actions/setup-node@v6
+      - uses: oven-sh/setup-bun@v2
         with:
-          node-version: 24.18.0
-          cache: "pnpm"
+          bun-version: 1.4.2
 
       - name: Run update script
-        run: node ./scripts/update-contributors.mjs
+        run: bun ./scripts/update-contributors.mjs
 
       - name: Commit changes
         env:

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

@@ -33,7 +33,7 @@ jobs:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
       - name: Setup
         uses: ./tooling/github/setup
-      - run: pnpm run scripts:update-readme-integrations
+      - run: bun run scripts:update-readme-integrations
       - name: Commit changes
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}

.github/workflows/validate-docs.yml

@@ -0,0 +1,65 @@
+name: Validate documentation
+
+on:
+  pull_request:
+    paths:
+      - "apps/docs/**"
+      - "apps/nextjs/src/app/api/**"
+      - "packages/definitions/src/**"
+      - "packages/widgets/src/**"
+      - "packages/custom-widgets/src/**"
+      - "packages/ui/src/**"
+      - "packages/workshop/src/**"
+      - "packages/api/src/**"
+      - "packages/auth/src/**"
+      - "packages/integrations/src/**"
+      - "tools/motion-reel/three/**"
+      - "tooling/**"
+      - "bun.lock"
+      - "package.json"
+      - "bunfig.toml"
+      - "turbo.json"
+      - ".github/workflows/deployment-docs.yml"
+      - ".github/workflows/validate-docs.yml"
+
+permissions:
+  contents: read
+
+concurrency:
+  group: validate-docs-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  docs:
+    name: Build and validate docs
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    env:
+      SKIP_ENV_VALIDATION: true
+      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 }}
+    steps:
+      - uses: actions/checkout@v7
+        if: "!env.ACT"
+        with:
+          persist-credentials: false
+      - name: Setup
+        uses: ./tooling/github/setup
+        with:
+          next-cache: "docs"
+          turbo-cache: "true"
+      - name: Validate the published API schema against the application
+        run: bun run check:openapi
+      - name: Validate browser access and API schema rendering
+        run: bun x vitest run 'apps/nextjs/src/app/api/[...trpc]/route.spec.ts' apps/docs/src/lib/openapi.spec.ts
+      - name: Build docs
+        run: bun run turbo run build --filter=@homarr/docs
+        env:
+          CI: "true"
+      - name: Validate exported links, search, and metadata
+        run: |
+          bun run --filter @homarr/docs validate:links
+          bun run --filter @homarr/docs verify:search
+          bun run --filter @homarr/docs verify:seo

.github/workflows/workshop.yml

@@ -4,34 +4,50 @@ on:
   pull_request:
     paths:
       - ".github/workflows/workshop.yml"
+      - "tooling/github/**"
       - "apps/workshop/**"
       - "apps/docs/**"
+      - "packages/common/**"
+      - "packages/core/**"
       - "packages/custom-widgets/**"
       - "packages/definitions/**"
+      - "packages/db/**"
+      - "packages/server-settings/**"
+      - "packages/settings/**"
+      - "packages/translation/**"
+      - "packages/ui/**"
+      - "packages/validation/**"
       - "packages/workshop/**"
       - "tooling/typescript/**"
       - "patches/**"
       - "package.json"
-      - "pnpm-lock.yaml"
-      - "pnpm-workspace.yaml"
+      - "bun.lock"
+      - "bunfig.toml"
       - "turbo.json"
-      - ".npmrc"
   push:
     branches: [dev, v2, release/v2, main]
     paths:
       - ".github/workflows/workshop.yml"
+      - "tooling/github/**"
       - "apps/workshop/**"
       - "apps/docs/**"
+      - "packages/common/**"
+      - "packages/core/**"
       - "packages/custom-widgets/**"
       - "packages/definitions/**"
+      - "packages/db/**"
+      - "packages/server-settings/**"
+      - "packages/settings/**"
+      - "packages/translation/**"
+      - "packages/ui/**"
+      - "packages/validation/**"
       - "packages/workshop/**"
       - "tooling/typescript/**"
       - "patches/**"
       - "package.json"
-      - "pnpm-lock.yaml"
-      - "pnpm-workspace.yaml"
+      - "bun.lock"
+      - "bunfig.toml"
       - "turbo.json"
-      - ".npmrc"
 
 permissions:
   contents: read
@@ -41,11 +57,67 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
+  production-smoke:
+    if: github.event_name == 'pull_request'
+    name: Production image smoke (${{ matrix.arch }})
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - arch: amd64
+            runner: ubuntu-24.04
+          - arch: arm64
+            runner: ubuntu-24.04-arm
+    runs-on: ${{ matrix.runner }}
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v7
+        if: "!env.ACT"
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 24.18.0
+      - name: Set up Docker Buildx
+        if: "!env.ACT"
+        uses: docker/setup-buildx-action@v4
+      - name: Build the production image
+        if: "!env.ACT"
+        uses: docker/build-push-action@v7
+        with:
+          context: .
+          file: apps/workshop/Dockerfile
+          target: production
+          platforms: linux/${{ matrix.arch }}
+          load: true
+          tags: homarr-workshop:smoke
+          cache-from: type=gha,scope=workshop-linux-${{ matrix.arch }}
+          cache-to: type=gha,scope=workshop-linux-${{ matrix.arch }},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 }}
+      - name: Exercise the production image
+        if: "!env.ACT"
+        env:
+          WORKSHOP_IMAGE_TEST_IMAGE: homarr-workshop:smoke
+        run: sh apps/workshop/test-image.sh
+      - name: Build and exercise the production image with Act
+        if: env.ACT
+        env:
+          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 }}
+        run: sh apps/workshop/test-image.sh
+
   validate:
     runs-on: ubuntu-24.04
     timeout-minutes: 5
     steps:
       - uses: actions/checkout@v7
+        if: "!env.ACT"
       - run: docker compose --env-file apps/workshop/.env.staging.example -f apps/workshop/docker-compose.staging.yml config --quiet
 
   publish-amd64:
@@ -60,6 +132,7 @@ jobs:
       digest: ${{ steps.build.outputs.digest }}
     steps:
       - uses: actions/checkout@v7
+        if: "!env.ACT"
       - uses: docker/setup-buildx-action@v4
       - uses: docker/login-action@v4
         with:
@@ -76,6 +149,11 @@ jobs:
           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
+          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-arm64:
     if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
@@ -89,6 +167,7 @@ jobs:
       digest: ${{ steps.build.outputs.digest }}
     steps:
       - uses: actions/checkout@v7
+        if: "!env.ACT"
       - uses: docker/setup-buildx-action@v4
       - uses: docker/login-action@v4
         with:
@@ -105,6 +184,11 @@ jobs:
           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
+          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:
     if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')

.gitignore

@@ -2,7 +2,7 @@
 
 # dependencies
 node_modules
-.pnpm-store/
+.bun-cache/
 .pnp
 .pnp.js
 .idea/
@@ -36,7 +36,7 @@ tools/homarr-dev/homarr-dev
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
-.pnpm-debug.log*
+bun-debug.log*
 
 # local env files
 .env
@@ -81,7 +81,7 @@ skills-lock.json
 # docusaurus
 apps/docs/.docusaurus
 apps/docs/build
-.pnpm-store
+.bun-cache
 benchmark-results
 
 # local performance investigation (never ship benchmark data or restored backups)

.mcp.json

@@ -1,8 +1,8 @@
 {
   "mcpServers": {
     "mantine": {
-      "command": "npx",
-      "args": ["-y", "@mantine/mcp-server@9.6.0"]
+      "command": "bun",
+      "args": ["x", "@mantine/mcp-server@9.6.0"]
     }
   }
 }

.mise.toml

@@ -1,2 +0,0 @@
-[tools]
-node = "24.18.0"

.npmrc

@@ -1,2 +0,0 @@
-# pnpm v11: non-auth settings moved to pnpm-workspace.yaml
-# Keep this file for any future registry/auth configuration

.oxfmtrc.json

@@ -8,15 +8,15 @@
     "**/lang/**",
     "static-data/**",
     "CHANGELOG.md",
-    "apps/docs/.docusaurus/**",
-    "apps/docs/build/**",
+    "apps/docs/.next/**",
+    "apps/docs/out/**",
     "apps/docs/blog/2022/**",
     "apps/docs/blog/2023/**",
     "apps/docs/blog/2024/**",
     "apps/docs/blog/2025/**",
     "apps/docs/blog/authors.yml",
-    "apps/docs/static/api/open-api-schema.json",
+    "apps/docs/public/api/open-api-schema.json",
     "packages/custom-widgets/src/core/component-catalog.generated.json",
-    "apps/docs/static/custom-widgets/component-catalog-v1.json"
+    "apps/docs/public/custom-widgets/component-catalog-v1.json"
   ]
 }

.releaserc.json

@@ -26,16 +26,11 @@
         "changelogFile": "CHANGELOG.md"
       }
     ],
-    [
-      "@semantic-release/npm",
-      {
-        "npmPublish": false
-      }
-    ],
+    "./scripts/release-version.mjs",
     [
       "@semantic-release/git",
       {
-        "assets": ["package.json", "CHANGELOG.md"],
+        "assets": ["package.json", "bun.lock", "CHANGELOG.md"],
         "message": "chore(release): ${nextRelease.version} [skip ci]"
       }
     ],

.run/db_migration_mysql_generate.run.xml

@@ -1,13 +0,0 @@
-<component name="ProjectRunConfigurationManager">
-  <configuration default="false" name="db:migration:mysql:generate" type="js.build_tools.npm">
-    <package-json value="$PROJECT_DIR$/package.json" />
-    <command value="run" />
-    <scripts>
-      <script value="db:migration:mysql:generate" />
-    </scripts>
-    <node-interpreter value="project" />
-    <package-manager value="pnpm" />
-    <envs />
-    <method v="2" />
-  </configuration>
-</component>

.run/db_migration_postgresql_generate.run copy.xml

@@ -6,7 +6,7 @@
       <script value="db:migration:postgresql:generate" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/db_migration_sqlite_generate.run.xml

@@ -6,7 +6,7 @@
       <script value="db:migration:sqlite:generate" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/db_push.run.xml

@@ -6,7 +6,7 @@
       <script value="db:push" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/db_studio.run.xml

@@ -6,7 +6,7 @@
       <script value="db:studio" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/dev.run.xml

@@ -6,7 +6,7 @@
       <script value="dev" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/docker_dev.run.xml

@@ -6,7 +6,7 @@
       <script value="docker:dev" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/format.run.xml

@@ -6,7 +6,7 @@
       <script value="format" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/format_fix.run.xml

@@ -6,7 +6,7 @@
       <script value="format:fix" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/test.run.xml

@@ -6,7 +6,7 @@
       <script value="test" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/test_ui.run.xml

@@ -6,7 +6,7 @@
       <script value="test:ui" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.run/typecheck.run.xml

@@ -6,7 +6,7 @@
       <script value="typecheck" />
     </scripts>
     <node-interpreter value="project" />
-    <package-manager value="pnpm" />
+    <package-manager value="bun" />
     <envs />
     <method v="2" />
   </configuration>

.vscode/launch.json

@@ -5,7 +5,7 @@
       "name": "dev",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm dev",
+      "command": "bun run dev",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -13,7 +13,7 @@
       "name": "docker dev",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm docker:dev",
+      "command": "bun run docker:dev",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -21,7 +21,7 @@
       "name": "lint fix",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm lint:fix",
+      "command": "bun run lint:fix",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -29,7 +29,7 @@
       "name": "format fix",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm format:fix",
+      "command": "bun run format:fix",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -37,7 +37,7 @@
       "name": "db push",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm db:push",
+      "command": "bun run db:push",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -45,7 +45,7 @@
       "name": "db studio",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm db:studio",
+      "command": "bun run db:studio",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -53,7 +53,7 @@
       "name": "db migration run",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm db:migration:run",
+      "command": "bun run db:migration:sqlite:run",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -61,7 +61,7 @@
       "name": "test",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm test",
+      "command": "bun run test",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     },
@@ -69,7 +69,7 @@
       "name": "test ui",
       "type": "node-terminal",
       "request": "launch",
-      "command": "pnpm test:ui",
+      "command": "bun run test:ui",
       "cwd": "${workspaceFolder}",
       "skipFiles": ["<node_internals>/**"]
     }

AGENTS.md

@@ -6,14 +6,14 @@
 homarr/
 ├── apps/
 │   ├── nextjs/          # Main Next.js application (port 3000)
-│   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
+│   ├── docs/            # Next.js + Fumadocs documentation site (@homarr/docs)
 │   ├── tasks/           # Cron-job initialization and scheduling runtime
 │   ├── websocket/       # Standalone tRPC WebSocket server (port 3001)
 │   └── workshop/        # Go/PocketBase Workshop service
 ├── packages/
 │   ├── api/             # tRPC appRouter, procedures, OpenAPI
 │   ├── auth/            # NextAuth config, providers, session, API keys
-│   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
+│   ├── db/              # SQLite and PostgreSQL schemas, migrations, queries
 │   ├── core/            # Env validation, DB/Redis driver factories, logging
 │   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
 │   ├── widgets/         # Dashboard widget definitions and components
@@ -55,17 +55,13 @@ homarr/
 └── Dockerfile           # Multi-stage production build
 ```
 
-## Documentation Sync
+## Documentation
 
-The documentation site lives at `apps/docs/` (Docusaurus 3, `@homarr/docs`).
+Add documentation only when users need the information to set up, use, or troubleshoot Homarr and cannot reasonably discover it from the UI or generated API schema. If a user does not need to know it, do not document it. A code, UI, or API change alone is never a reason to add docs.
 
-Write for smart, curious, advanced users. Documentation should contain only information they cannot reasonably discover or understand directly from the interface: hidden capabilities, non-obvious behavior, prerequisites, constraints, configuration contracts, and migration requirements.
+Keep warranted documentation concise. Omit UI walkthroughs, visible control descriptions, internal implementation details, and anything already clear from the interface or schema.
 
-Keep docs concise. Every paragraph must add knowledge beyond visible labels and standard UI conventions. Explain how to discover and use a hidden advanced widget feature; omit explanations that the Delete button deletes an item in edit mode. Avoid UI walkthroughs, exhaustive control descriptions, and repetition. When editing a passage, remove obvious or redundant prose rather than preserving verbosity as a precedent.
-
-Update docs only when a change introduces or alters that non-obvious information, or makes existing guidance inaccurate. Routine fixes and self-explanatory UI changes need no docs update. A new feature alone does not require a page; apply the same reader-value test.
-
-When documentation is needed, use these locations:
+Only after this user-need test passes, use these locations:
 
 - New integration → `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts`
 - New widget → `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`
@@ -77,34 +73,52 @@ When documentation is needed, use these locations:
 
 ## Monorepo Commands
 
-- `pnpm dev` — Next.js app only
-- `pnpm dev:cli -- dev` — run the developer CLI without installing a global binary
-- `pnpm db:seed` — seed default database data explicitly
-- `pnpm docker:dev:up` — start the Redis development service in the background
-- `pnpm dev:docs` — Docusaurus docs site only
-- `pnpm turbo build` — build all packages
-- `pnpm turbo build --filter=@homarr/docs` — build docs only
-- `pnpm turbo typecheck` — typecheck all packages
-- `pnpm lint` / `pnpm format` — oxlint / oxfmt
+- `bun run dev` — Next.js app only
+- `bun run dev:cli -- dev` — run the developer CLI without installing a global binary
+- `bun run db:seed` — seed default database data explicitly
+- `bun run docker:dev:up` — start the Redis development service in the background
+- `bun run dev:docs` — Fumadocs site only
+- `bun run turbo build` — build all packages
+- `bun run turbo build --filter=@homarr/docs` — build docs only
+- `bun run turbo typecheck` — typecheck all packages
+- `bun run lint` / `bun run format` — oxlint / oxfmt
 
 ## Code Style
 
 - Lint: oxlint (not ESLint)
 - Format: oxfmt (not Prettier)
 - UI: Mantine (not Tailwind) — Tailwind is only used in docs app
-- Mantine: use the project-scoped MCP server in `.mcp.json` for current v9 APIs, and check `packages/ui/` before creating a new primitive.
+- Mantine: use the `mantine` MCP server in `.mcp.json` for current v9 APIs before writing component code. Prefer built-in primitives (`Combobox`/`useCombobox`, the polymorphic `component` prop, `@mantine/hooks`) and check `packages/ui/` for existing conventions first.
 - Icons: @tabler/icons-react
 - Docs app can import from `@homarr/definitions` for shared types
-- Run `pnpm dev:cli -- dev` to browse local `homarr:*` images and remote PR images.
-- Run `pnpm dev:cli -- build <name>` from a Homarr checkout to build `homarr:<name>` with rebuild provenance.
-- Run `pnpm dev:cli -- build --pr <number>` to build a PR locally from a temporary checkout.
-- Run Go checks from `tools/homarr-dev` with `go test ./...` and `go vet ./...`.
+- Run `bun run dev:cli -- dev` to browse local `homarr:*` images and remote PR images.
+- Run `bun run dev:cli -- build <name>` from a Homarr checkout to build `homarr:<name>` with rebuild provenance.
+- Run `bun run dev:cli -- build --pr <number>` to build a PR locally from a temporary checkout.
+
+## Testing
+
+Add tests only when requested, and only when the test is extremely relevant and will plausibly prevent a future regression in user-visible behavior or a security boundary. Do not add tests that restate implementation details or duplicate stronger coverage. For focused changes, run only the relevant existing or newly requested checks when validation is needed. Do not run broad test, Docker, or E2E suites by default.
+
+## MCP servers
+
+`.mcp.json` declares project-scoped MCP servers. Keep only keyless definitions there; credentials belong in local dotfiles. See [Mantine LLM tooling](https://mantine.dev/guides/llms/) for client-specific setup.
 
 ## Agent Skills
 
 Portable skills live in `.agents/skills/`. Read the relevant `SKILL.md` before working in that domain; detailed references are loaded only when needed. Claude-compatible discovery is provided through `.claude/skills`.
 
 - `codebase-context` — architecture, package boundaries, and shared utilities
-- `documentation-sync` — documentation for changes users need explained
+- `documentation-sync` — user-critical documentation only
 - `mcp-integration` — safe tRPC-to-MCP exposure
 - `homarr-custom-widget` — safe Custom JSX v2 authoring
+
+<!-- BEGIN:turborepo-agent-rules -->
+
+# This is NOT the Turborepo you know
+
+Turborepo configuration, task behavior, and CLI commands can vary between installed versions and may differ from your training data. Resolve the `turbo` package from this file's directory or relevant workspace; in monorepos, it may not be visible from the repository root. For example, run `node -p "require.resolve('turbo/package.json')"` from a workspace that depends on `turbo`.
+
+Read `docs/README.md` inside that installed package first, then read the relevant pages from its `docs/` directory before changing Turborepo configuration or commands. Heed deprecation notices. These bundled docs match the installed package version and are available without network access.
+
+This block is written and re-added by `turbo` before repository-scoped commands when an AI agent is detected. In the Turborepo source repository, its template is defined in `crates/turborepo-cli/src/cli/agent_guidance.rs`. Removing the managed block while updates are enabled means a later qualifying invocation will add it again. Set `"agentGuidance": false` in the root `turbo.json` or `turbo.jsonc` to opt out; this does not remove an existing block. When agent guidance is enabled, keep the block committed to avoid an uncommitted change on the next agent invocation. This repository disables agent guidance in `turbo.json`.
+<!-- END:turborepo-agent-rules -->

CHANGELOG.md

@@ -1,3 +1,19 @@
+## [2.3.0](https://github.com/homarr-labs/homarr/compare/v2.2.0...v2.3.0) (2026-10-07)
+
+## [2.2.0](https://github.com/homarr-labs/homarr/compare/v2.1.2...v2.2.0) (2026-10-05)
+
+## [2.1.2](https://github.com/homarr-labs/homarr/compare/v2.1.1...v2.1.2) (2026-10-04)
+
+## [2.1.1](https://github.com/homarr-labs/homarr/compare/v2.1.0...v2.1.1) (2026-10-03)
+
+## [2.1.0](https://github.com/homarr-labs/homarr/compare/v2.0.0...v2.1.0) (2026-10-03)
+
+## [2.0.0](https://github.com/homarr-labs/homarr/compare/v1.77.2...v2.0.0) (2026-10-02)
+
+## [1.77.1](https://github.com/homarr-labs/homarr/compare/v1.77.0...v1.77.1) (2026-09-11)
+
+## [1.77.0](https://github.com/homarr-labs/homarr/compare/v1.76.2...v1.77.0) (2026-09-06)
+
 ## [1.76.2](https://github.com/homarr-labs/homarr/compare/v1.76.1...v1.76.2) (2026-08-27)
 
 ## [1.76.1](https://github.com/homarr-labs/homarr/compare/v1.76.0...v1.76.1) (2026-08-26)

CODEOWNERS

@@ -1,234 +0,0 @@
-# ── CODEOWNERS ───────────────────────────────────────
-* @homarr-labs/maintainers
-
-# Specific features / integrations
-# These owners come from the PR that introduced each integration implementation.
-# Specific rules override the global fallback because CODEOWNERS uses the last
-# matching pattern; do not include @homarr-labs/maintainers here unless they
-# should also be requested for that integration.
-
-# AdGuard Home - introduced in https://github.com/homarr-labs/homarr/pull/929 by @hillaliy
-apps/docs/docs/integrations/adguard-home @hillaliy
-packages/integrations/src/adguard-home @hillaliy
-
-# Anchor - introduced in https://github.com/homarr-labs/homarr/pull/5040 by @ohmzi
-apps/docs/docs/integrations/anchor @ohmzi
-packages/integrations/src/anchor @ohmzi
-
-# ArchiveTeam Warrior - introduced in https://github.com/homarr-labs/homarr/pull/5784 by @darbyjack
-apps/docs/docs/integrations/archive-team-warrior @darbyjack
-packages/integrations/src/archive-team-warrior @darbyjack
-
-# Bazarr - introduced in https://github.com/homarr-labs/homarr/pull/6156 by @Ayush7614
-apps/docs/docs/integrations/bazarr @Ayush7614
-apps/docs/docs/widgets/bazarr @Ayush7614
-packages/api/src/router/widgets/bazarr.ts @Ayush7614
-packages/integrations/src/bazarr @Ayush7614
-packages/request-handler/src/bazarr.ts @Ayush7614
-packages/widgets/src/bazarr @Ayush7614
-
-# Audiobookshelf - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/audiobookshelf @ajnart
-packages/integrations/src/audiobookshelf @ajnart
-
-# Beszel - introduced in https://github.com/homarr-labs/homarr/pull/5900 by @ajnart
-apps/docs/docs/integrations/beszel @ajnart
-packages/integrations/src/beszel @ajnart
-
-# Codeberg - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/codeberg @Aandree5
-packages/integrations/src/codeberg @Aandree5
-
-# Coolify - introduced in https://github.com/homarr-labs/homarr/pull/4789 by @Rhiz3K
-apps/docs/docs/integrations/coolify @Rhiz3K
-packages/integrations/src/coolify @Rhiz3K
-
-# Dash. - introduced in https://github.com/homarr-labs/homarr/pull/1541 by @manuel-rw
-apps/docs/docs/integrations/dash-dot @manuel-rw
-packages/integrations/src/dashdot @manuel-rw
-
-# Docker Hub - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/docker-hub @Aandree5
-packages/integrations/src/docker-hub @Aandree5
-
-# Emby - introduced in https://github.com/homarr-labs/homarr/pull/2466 by @Meierschlumpf
-apps/docs/docs/integrations/emby @Meierschlumpf
-packages/integrations/src/emby @Meierschlumpf
-
-# GitHub - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/github @Aandree5
-packages/integrations/src/github @Aandree5
-
-# GitHub Container Registry - introduced in https://github.com/homarr-labs/homarr/pull/3727 by @Aandree5
-apps/docs/docs/integrations/github-containerregistry @Aandree5
-packages/integrations/src/github-container-registry @Aandree5
-
-# GitLab - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/gitlab @Aandree5
-packages/integrations/src/gitlab @Aandree5
-
-# Glances - introduced in https://github.com/homarr-labs/homarr/pull/5102 by @manuel-rw
-apps/docs/docs/integrations/glances @manuel-rw
-packages/integrations/src/glances @manuel-rw
-
-# Gluetun - introduced in https://github.com/homarr-labs/homarr/pull/5812 by @Lok3sh-kumar
-apps/docs/docs/integrations/gluetun @Lok3sh-kumar
-packages/integrations/src/gluetun @Lok3sh-kumar
-
-# Gotify - introduced in https://github.com/homarr-labs/homarr/pull/5847 by @Nerdy-Technician
-apps/docs/docs/integrations/gotify @Nerdy-Technician
-packages/integrations/src/gotify @Nerdy-Technician
-
-# Home Assistant - introduced in https://github.com/homarr-labs/homarr/pull/578 by @manuel-rw
-apps/docs/docs/integrations/home-assistant @manuel-rw
-packages/integrations/src/homeassistant @manuel-rw
-
-# ICal - introduced in https://github.com/homarr-labs/homarr/pull/3980 by @NicolasNewman
-apps/docs/docs/integrations/ical @NicolasNewman
-packages/integrations/src/ical @NicolasNewman
-
-# Immich - introduced in https://github.com/homarr-labs/homarr/pull/5165 by @manuel-rw
-apps/docs/docs/integrations/immich @manuel-rw
-packages/integrations/src/immich @manuel-rw
-
-# Jellyfin - introduced in https://github.com/homarr-labs/homarr/pull/672 by @manuel-rw
-apps/docs/docs/integrations/jellyfin @manuel-rw
-packages/integrations/src/jellyfin @manuel-rw
-
-# Jellyseerr - introduced in https://github.com/homarr-labs/homarr/pull/774 by @manuel-rw
-apps/docs/docs/integrations/jellyseerr @manuel-rw
-packages/integrations/src/jellyseerr @manuel-rw
-
-# LinuxServer.io - introduced in https://github.com/homarr-labs/homarr/pull/3607 by @Aandree5
-apps/docs/docs/integrations/linux-server-io @Aandree5
-packages/integrations/src/linuxserverio @Aandree5
-
-# Navidrome - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/navidrome @ajnart
-packages/integrations/src/navidrome @ajnart
-
-# Nextcloud - introduced in https://github.com/homarr-labs/homarr/pull/2501 by @manuel-rw
-apps/docs/docs/integrations/nextcloud @manuel-rw
-packages/integrations/src/nextcloud @manuel-rw
-
-# npm - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/npm @Aandree5
-packages/integrations/src/npm @Aandree5
-
-# ntfy - introduced in https://github.com/homarr-labs/homarr/pull/2900 by @itzTheMeow
-apps/docs/docs/integrations/ntfy @ajnart @manuel-rw
-packages/integrations/src/ntfy @ajnart @manuel-rw
-
-# OpenMediaVault - introduced in https://github.com/homarr-labs/homarr/pull/1142 by @hillaliy
-apps/docs/docs/integrations/open-media-vault @hillaliy
-packages/integrations/src/openmediavault @hillaliy
-
-# OPNsense - introduced in https://github.com/homarr-labs/homarr/pull/3424 by @Oupsman
-apps/docs/docs/integrations/opnsense @Oupsman
-packages/integrations/src/opnsense @Oupsman
-
-# Overseerr - introduced in https://github.com/homarr-labs/homarr/pull/774 by @manuel-rw
-apps/docs/docs/integrations/overseerr @manuel-rw
-packages/integrations/src/overseerr @manuel-rw
-
-# Paperless-ngx - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/paperless-ngx @ajnart
-packages/integrations/src/paperless-ngx @ajnart
-
-# PatchMon - introduced in https://github.com/homarr-labs/homarr/pull/6119 by @mrjoshuap
-apps/docs/docs/integrations/patchmon @mrjoshuap
-packages/integrations/src/patchmon @mrjoshuap
-packages/widgets/src/patchmon @mrjoshuap
-packages/api/src/router/widgets/patchmon.ts @mrjoshuap
-packages/request-handler/src/patchmon.ts @mrjoshuap
-
-# PeaNUT - introduced in https://github.com/homarr-labs/homarr/pull/5862 by @afonsojramos
-apps/docs/docs/integrations/peanut @afonsojramos
-packages/integrations/src/peanut @afonsojramos
-
-# Pi-hole - introduced in https://github.com/homarr-labs/homarr/pull/521 by @Meierschlumpf
-apps/docs/docs/integrations/pi-hole @Meierschlumpf
-packages/integrations/src/pi-hole @Meierschlumpf
-
-# Plex - introduced in https://github.com/homarr-labs/homarr/pull/1342 by @hillaliy
-apps/docs/docs/integrations/plex @hillaliy
-packages/integrations/src/plex @hillaliy
-
-# Prowlarr - introduced in https://github.com/homarr-labs/homarr/pull/965 by @hillaliy
-apps/docs/docs/integrations/prowlarr @hillaliy
-packages/integrations/src/prowlarr @hillaliy
-
-# Proxmox - introduced in https://github.com/homarr-labs/homarr/pull/1969 by @Meierschlumpf
-apps/docs/docs/integrations/proxmox @Meierschlumpf
-packages/integrations/src/proxmox @Meierschlumpf
-
-# Quay - introduced in https://github.com/homarr-labs/homarr/pull/3607 by @Aandree5
-apps/docs/docs/integrations/quay @Aandree5
-packages/integrations/src/quay @Aandree5
-
-# search.ch - introduced in https://github.com/homarr-labs/homarr/pull/5180 by @Meierschlumpf
-apps/docs/docs/integrations/search-ch @Meierschlumpf
-packages/integrations/src/search-ch @Meierschlumpf
-
-# Speedtest Tracker - introduced in https://github.com/homarr-labs/homarr/pull/5363 by @kylegrieder
-apps/docs/docs/integrations/speedtest-tracker @kylegrieder
-packages/integrations/src/speedtest-tracker @kylegrieder
-
-# Synology - introduced in https://github.com/homarr-labs/homarr/pull/6121 by @mrjoshuap
-apps/docs/docs/integrations/synology @mrjoshuap
-packages/integrations/src/synology @mrjoshuap
-
-# Technitium DNS - introduced in https://github.com/homarr-labs/homarr/pull/5832 by @lopsch
-apps/docs/docs/integrations/technitium-dns @lopsch
-packages/integrations/src/technitium @lopsch
-
-# Tracearr - introduced in https://github.com/homarr-labs/homarr/pull/5060 by @StrandedTurtle
-apps/docs/docs/integrations/tracearr @StrandedTurtle
-packages/integrations/src/tracearr @StrandedTurtle
-
-# TrueNAS - introduced in https://github.com/homarr-labs/homarr/pull/3745 by @manuel-rw
-apps/docs/docs/integrations/truenas @manuel-rw @afonsojramos
-packages/integrations/src/truenas @manuel-rw @afonsojramos
-
-# Umami - introduced in https://github.com/homarr-labs/homarr/pull/5362 by @febrile42
-apps/docs/docs/integrations/umami @febrile42
-packages/integrations/src/umami @febrile42
-
-# UniFi Controller - introduced in https://github.com/homarr-labs/homarr/pull/2236 by @pitschi
-apps/docs/docs/integrations/unifi-controller @pitschi
-packages/integrations/src/unifi-controller @pitschi
-
-# Unraid - introduced in https://github.com/homarr-labs/homarr/pull/4439 by @manuel-rw
-apps/docs/docs/integrations/unraid @manuel-rw
-packages/integrations/src/unraid @manuel-rw
-
-# Uptime Kuma - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/uptime-kuma @ajnart
-packages/integrations/src/uptime-kuma @ajnart
-
-# What's Up Docker (WUD) - introduced in https://github.com/homarr-labs/homarr/pull/6523 by @tiimonn
-apps/docs/docs/integrations/whats-up-docker @tiimonn
-apps/docs/docs/widgets/whats-up-docker @tiimonn
-packages/api/src/router/widgets/wud.ts @tiimonn
-packages/integrations/src/wud @tiimonn
-packages/request-handler/src/wud.ts @tiimonn
-packages/widgets/src/wud @tiimonn
-
-# Traefik - by @Nerdy-Technician
-apps/docs/docs/integrations/traefik @Nerdy-Technician
-apps/docs/docs/widgets/traefik @Nerdy-Technician
-packages/api/src/router/widgets/traefik.ts @Nerdy-Technician
-packages/integrations/src/traefik @Nerdy-Technician
-packages/request-handler/src/traefik.ts @Nerdy-Technician
-packages/widgets/src/traefik @Nerdy-Technician
-
-# Exempt Renovate-managed files (no owners)
-package.json
-**/package.json
-package-lock.json
-**/package-lock.json
-pnpm-lock.yaml
-**/pnpm-lock.yaml
-pnpm-workspace.yaml
-Dockerfile
-docker-compose.yml

Dockerfile

@@ -1,100 +1,62 @@
 # syntax=docker/dockerfile:1.25
 
+FROM oven/bun:1.4.2-alpine AS bun-tool
+
 FROM node:24.18.0-alpine AS base
 
 FROM base AS builder
 ARG TARGETPLATFORM
 WORKDIR /app
-# Native dependencies normally use prebuilds, but the build must remain
-# reproducible when a prebuild download times out and compilation is required.
-RUN apk add --no-cache libc6-compat curl bash python3 make g++
-
-RUN corepack enable pnpm
-COPY .npmrc pnpm-lock.yaml pnpm-workspace.yaml package.json ./
+COPY --from=bun-tool /usr/local/bin/bun /usr/local/bin/bun
+# Compiler tools stay in the builder for optional native dependency fallbacks.
+RUN apk add --no-cache libstdc++ python3 make g++
+COPY bun.lock bunfig.toml package.json ./
 COPY patches ./patches
 COPY --parents ./apps/*/package.json ./packages/*/package.json ./tooling/*/package.json ./
-# @homarr/definitions generates documentation types during install.
-COPY --parents ./packages/definitions/src ./
-# Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
-# are configured with nodeLinker: hoisted. The applyPatchToDir function tries
-# to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
-# content-addressable store is populated). By temporarily switching to the
-# 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 \
-    pnpm config set store-dir /pnpm/store && \
-    sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
-    pnpm fetch --ignore-scripts && \
-    sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml
-
-# 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 \
-    npm_config_nodedir=/usr/local pnpm install --recursive --offline --frozen-lockfile --child-concurrency=1
+RUN --mount=type=cache,id=homarr-bun-cache,target=/root/.bun/install/cache,sharing=locked \
+    npm_config_nodedir=/usr/local bun install --frozen-lockfile --concurrent-scripts=1
 
 COPY . .
-
 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
 ARG DISABLE_REDIS_LOGS='true'
 ARG TARGETPLATFORM
-
 RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
     --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \
     --mount=type=secret,id=TURBO_TOKEN,env=TURBO_TOKEN \
     --mount=type=secret,id=TURBO_REMOTE_CACHE_SIGNATURE_KEY,env=TURBO_REMOTE_CACHE_SIGNATURE_KEY \
     --mount=type=cache,id=homarr-next-build-${TARGETPLATFORM},target=/app/apps/nextjs/.next/cache,sharing=locked \
-    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" \
-    pnpm turbo build --filter=@homarr/nextjs... --filter=@homarr/cli
+    --mount=type=cache,id=homarr-turbo-${TARGETPLATFORM},target=/app/.turbo,sharing=locked \
+    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}/musl/node-24.18.0" \
+    bun run turbo run build --filter=@homarr/nextjs... --filter=@homarr/cli
 
-FROM base AS runner
+FROM alpine:3.24.1 AS runner
 WORKDIR /app
-
-# gettext is required for envsubst, openssl for generating AUTH_SECRET, su-exec for running application as non-root
-RUN apk add --no-cache redis nginx bash gettext su-exec openssl
-RUN mkdir /appdata
+COPY --from=base /usr/local/bin/node /usr/local/bin/node
+# envsubst, privilege drop and AUTH_SECRET generation are used by the entrypoint.
+RUN apk add --no-cache libstdc++ ca-certificates redis nginx bash gettext su-exec openssl && \
+    mkdir -p /appdata /var/cache/nginx /var/log/nginx /var/lib/nginx \
+      /run/nginx /etc/nginx/templates /etc/nginx/ssl/certs && \
+    touch /run/nginx/nginx.pid
 VOLUME /appdata
-
-# Enable homarr cli
 COPY --from=builder /app/packages/cli/cli.cjs /app/apps/cli/cli.cjs
-RUN echo $'#!/bin/bash\ncd /app/apps/cli && node ./cli.cjs "$@"' > /usr/bin/homarr
-RUN chmod +x /usr/bin/homarr
-
-# Don't run production as root
-RUN mkdir -p /var/cache/nginx && \
-    mkdir -p /var/log/nginx && \
-    mkdir -p /var/lib/nginx && \
-    touch /run/nginx/nginx.pid && \
-    mkdir -p /etc/nginx/templates /etc/nginx/ssl/certs
-
-COPY --from=builder /app/apps/nextjs/next.config.ts .
-COPY --from=builder /app/apps/nextjs/package.json .
-COPY --from=builder /app/pnpm-workspace.yaml ./pnpm-workspace.yaml
-
+# Bundled CLI/migrations resolve the native binding from the application root.
 COPY --from=builder /app/node_modules/better-sqlite3/build/Release/better_sqlite3.node /app/build/better_sqlite3.node
-
+RUN printf '#!/bin/sh\ncd /app/apps/cli && exec node ./cli.cjs "$@"\n' > /usr/bin/homarr && \
+    chmod +x /usr/bin/homarr
 COPY --from=builder /app/packages/db/migrations ./db/migrations
-
-# Automatically leverage output traces to reduce image size
-# https://nextjs.org/docs/advanced-features/output-file-tracing
-COPY --from=builder /app/apps/nextjs/.next/standalone ./
-COPY --from=builder /app/apps/nextjs/.next/static ./apps/nextjs/.next/static
-COPY --from=builder /app/apps/nextjs/public ./apps/nextjs/public
+# Ship only Next's traced production dependencies and application assets.
+COPY --from=builder /app/apps/nextjs/.output/standalone ./
 COPY scripts/run.sh ./run.sh
 COPY --chmod=755 scripts/entrypoint.sh ./entrypoint.sh
 COPY packages/redis/redis.conf /app/redis.conf
 COPY nginx.conf /etc/nginx/templates/nginx.conf
-
-
 ENV DB_URL='/appdata/db/db.sqlite'
 ENV DB_DIALECT='sqlite'
 ENV DB_DRIVER='better-sqlite3'
 ENV AUTH_PROVIDERS='credentials'
 ENV REDIS_IS_EXTERNAL='false'
 ENV NODE_ENV='production'
-
 EXPOSE 7575
-ENTRYPOINT [ "/app/entrypoint.sh" ]
+ENTRYPOINT ["/app/entrypoint.sh"]
 CMD ["sh", "run.sh"]

PRODUCT.md

@@ -0,0 +1,33 @@
+# Product
+
+## Register
+
+brand
+
+## Users
+
+Self-hosted Homarr users who need to evaluate the project, install it, connect services, find extensions, and reference its APIs. They move between the homepage, documentation, Workshop, API reference, and project updates as one continuous experience.
+
+## Product Purpose
+
+The site explains what Homarr does and gives users reliable paths to install, configure, extend, and operate it. Success means users can identify where they are, move between major surfaces without relearning the navigation, and read technical content comfortably.
+
+## Brand Personality
+
+Practical, technical, welcoming.
+
+## Anti-references
+
+Avoid disconnected microsites, marketing-heavy copy, ornamental dashboards, hidden navigation, and dense long-form pages without visible structure.
+
+## Design Principles
+
+- Keep one recognizable Homarr identity across every surface.
+- Let navigation topology match the task while keeping labels and behavior consistent.
+- Prioritize readable line lengths, strong heading hierarchy, and visible document structure.
+- Make primary paths obvious without adding decorative UI.
+- Preserve useful functionality on mobile, keyboard navigation, and reduced-motion settings.
+
+## Accessibility & Inclusion
+
+Target WCAG 2.2 AA. Maintain keyboard access, visible focus states, sufficient contrast, semantic landmarks, touch-friendly controls, responsive layouts, and reduced-motion behavior.

apps/docs/.gitignore

@@ -5,7 +5,7 @@
 /node_modules
 /.pnp
 .pnp.js
-.pnpm-store/
+.bun-cache/
 
 # testing
 /coverage
@@ -13,6 +13,7 @@
 # next.js
 /.next/
 /out/
+/.source/
 
 # production
 /build
@@ -55,4 +56,4 @@ static/data/configs
 
 # CI Stuff
 screenshots
-test-results
+test-results

apps/docs/AGENTS.md

@@ -0,0 +1,18 @@
+<!-- BEGIN:nextjs-agent-rules -->
+
+# This is NOT the Next.js you know
+
+This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` (resolved from this file's directory; in monorepos the `next` package may not be visible from the repo root) before writing any code. Heed deprecation notices.
+
+This block is written and re-added by `next dev` — verify at `node_modules/next/dist/server/lib/generate-agent-files.js`. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
+
+<!-- END:nextjs-agent-rules -->
+
+## Fumadocs workflow
+
+- Start with `README.md`, `src/lib/source.ts`, `source.config.ts`, and the matching route under `src/app/`.
+- Read current [Fumadocs documentation](https://fumadocs.dev/docs) with Context7 before changing framework APIs. Check the installed version and types; latest examples may use a different search adapter.
+- Preserve static export: search uses `staticGET` with the matching static client. Do not introduce a request-time search server into this app.
+- Keep integration/widget metadata in the existing typed definitions. Check both rendered HTML and processed Markdown when changing MDX components; JSX alone does not guarantee readable search or AI output.
+- Run the README validation commands after content or navigation changes. Search results and table-of-contents links must resolve to rendered anchors.
+- Kapa is an independent hosted assistant. Keep its keyboard shortcut disabled so it does not override docs search; follow the README for its build configuration and crawler setup.

apps/docs/PRODUCT.md

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

apps/docs/README.md

@@ -1,112 +1,168 @@
-# Homarr Documentation (`@homarr/docs`)
+# Homarr documentation (`@homarr/docs`)
 
-The official [homarr.dev](https://homarr.dev) documentation site, built with [Docusaurus 3](https://docusaurus.io/) and living inside the Homarr monorepo.
+The source for [homarr.dev](https://homarr.dev), built with Next.js and Fumadocs UI inside the Homarr monorepo.
 
-## Why it's in the monorepo
+## Develop
 
-Having documentation alongside the application code enables:
-
-- **Two-way linking** — the docs app imports from `@homarr/definitions` for type-safe integration/widget metadata, and the main app references doc paths via generated sitemap types
-- **Atomic PRs** — code changes and their documentation updates ship in the same pull request
-- **Shared tooling** — same Node version, pnpm catalog, oxlint/oxfmt, CI pipeline
-- **Build-time validation** — Docusaurus strict mode catches broken links and references at build time
-
-## Development
-
-From the **monorepo root**:
+From the repository root:
 
 ```bash
-# Start the docs dev server (port 3003)
-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
+bun run 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
+The site runs on `http://127.0.0.1:3003`. To use a local Workshop API:
 
 ```bash
-# Build docs only
-pnpm turbo build --filter=@homarr/docs
-
-# Build everything (docs + main app + tasks + websocket)
-pnpm build
+WORKSHOP_API_URL=http://127.0.0.1:8090 bun run dev:docs
 ```
 
-## Lint & Format
-
-Uses oxlint and oxfmt (same as the rest of the monorepo):
+## Validate
 
 ```bash
-pnpm lint        # oxlint
-pnpm format      # oxfmt (check)
-pnpm format:fix    # oxfmt (fix)
+bun run --filter @homarr/docs typecheck
+bun run --filter @homarr/docs build
+bun run --filter @homarr/docs validate:links
+bun run --filter @homarr/docs verify:search
+bun run --filter @homarr/docs verify:seo
 ```
 
-## Typecheck
+The static export is written to `out/`. The build validates docs pages and typed metadata for integrations and widgets
+that declare a documentation slug. Set the slug to `null` when a page would add no useful information for advanced users.
+CI enforces coverage alongside schema drift and export validation. The link check validates internal Markdown and MDX
+links and rendered anchors against the export.
+The search check exercises the exported index with title, heading, and body queries and verifies result destinations.
+The SEO check validates canonical URLs, descriptions, social metadata, heading structure, and sitemap coverage in the
+exported HTML. These tags are generated at build time; set `HOMARR_WEBSITE_URL` before building for a different origin.
+
+## Preview the static export with PocketBase
+
+After building the docs, run from the repository root:
 
 ```bash
-pnpm typecheck
+sh apps/workshop/preview-docs.sh
 ```
 
-## Content Structure
+Open `http://127.0.0.1:8093/docs/`. This starts an isolated PocketBase container with temporary local data and serves
+the export directly, including search, Markdown, and the custom 404 page. Workshop browser requests use the configured
+backend; a trailing `/api/` is removed because the PocketBase SDK appends its API paths. The preview does not copy or
+migrate another database. Set `WORKSHOP_API_URL` to a remote PocketBase origin when testing against one;
+`WORKSHOP_REMOTE_API_URL` can override the server-side metadata source independently. Direct item links then use that
+source for titles and social metadata. Missing remote items return 404; an unavailable backend returns 503.
 
-```
-docs/
-├── getting-started/    # Installation guides, glossary, prerequisites
-├── management/         # Boards, apps, users, integrations, settings, tasks, API
-├── integrations/       # 56 integration guides (one folder each)
-├── widgets/            # 43 widget guides (one folder each)
-├── advanced/           # SSO, env vars, proxy, styling, CLI, development
-└── community/          # FAQ, donate, license, translations, get-in-touch
-```
-
-Each integration/widget doc follows a consistent pattern:
-
-- `index.ts` — typed metadata (`IntegrationDefinition` / `WidgetDefinition`)
-- `index.mdx` — content using shared React components (`IntegrationHeader`, `WidgetHeader`, etc.)
-
-## Importing from homarr packages
-
-The docs app has `@homarr/definitions` as a workspace dependency. You can import integration kinds, widget kinds, and other definitions directly:
-
-```typescript
-import { IntegrationKind } from "@homarr/definitions";
-```
-
-This enables type-safe references to homarr domain concepts within documentation code.
-
-## Search (Algolia DocSearch)
-
-Search uses the `Docusaurus` Algolia index (crawler `cd77a285-2756-4557-bf21-ee703748df15`). A separate `markdown` index is built for LLM markdown indexing.
-
-Crawler reference config: [`docsearch.config.js`](docsearch.config.js).
-
-**Verify search health:**
+Verify public item pages without changing the remote database:
 
 ```bash
-pnpm verify:search
+REMOTE_WORKSHOP_URL=https://workshop.example.com
+WORKSHOP_TEST_URL=http://127.0.0.1:8093 WORKSHOP_REMOTE_API_URL="$REMOTE_WORKSHOP_URL" \
+  bun apps/workshop/tests/remote-workshop.integration.mjs
 ```
 
-## Tech Stack
+Stop it with `docker stop homarr-docs-static-preview`. Rebuild and restart the preview after changing source files;
+startup recreates the runtime configuration. `DOCS_PREVIEW_PORT`, `DOCS_PREVIEW_HOST`, and `DOCS_PREVIEW_NAME` override
+the defaults. Set the host to this machine's Tailscale address to access it from your other devices.
 
-| 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                                  |
+## Write content
 
-## Contributing
+Documentation lives in `docs/`; project posts live in `blog/`. Navigation is controlled by the nearest `meta.json`.
+Integration and widget folders pair typed `index.ts` metadata with `index.mdx` content.
 
-When a Homarr change affects user-facing behavior, update the corresponding documentation in this app. See the
-[documentation-sync skill](../../.agents/skills/documentation-sync/SKILL.md) for the code-to-documentation mapping.
+Use standard Markdown and MDX. Shared components live in `src/components/`. Mermaid fences, tabs, callouts, zoomable
+images, and syntax-highlighted code are supported by the Fumadocs pipeline.
+
+Update docs in the same pull request only when a smart, advanced user cannot infer the changed behavior from the UI or
+generated API schema. Routine or self-explanatory changes need no docs update. See the
+[documentation-sync skill](../../.agents/skills/documentation-sync/SKILL.md) for target paths.
+
+## Published formats
+
+- `/docs` — searchable documentation with typed navigation
+- `/api-reference` — interactive reference generated from the OpenAPI schema
+- `/llms.txt` — compact documentation and blog index for agents
+- `/llms-full.txt` — complete processed Markdown corpus
+- `/llms.mdx/docs/.../content.md` — raw Markdown for each docs page
+- `/llms.mdx/blog/.../content.md` — raw Markdown for each blog post
+- `/llms.mdx/api-reference/.../content.md` — operation parameters, bodies, responses, and authentication
+- `/blog/rss.xml` — RSS feed for project posts
+- `/search?q=...` — opens documentation search with the supplied query, including existing Homarr search-engine links
+
+Every docs page and blog post includes copy-Markdown and view-source actions. Search is generated at build time and
+runs locally in the browser; it does not depend on an external crawler. Markdown exports and search resolve
+integration credentials and widget defaults from the same typed metadata used by the pages.
+The search dialog and its client-side engine load when search is first opened. Fumadocs caches the downloaded index
+for subsequent queries. The docs index, individual Markdown pages, and full corpus share the `llms()` renderer.
+API operations are indexed alongside docs and exported as Markdown from the same OpenAPI schema. The reference uses
+Fumadocs with Scalar: select an instance URL and API key, then explicitly send a request. Authentication is not
+persisted in local storage. Browser access requires the documented REST CORS configuration.
+
+The Custom JSX guide includes a lazily loaded, editable example using the application renderer and real component
+registry. Its bindings work locally; configured widget queries and actions do not run.
+
+The getting-started overview and complete Custom JSX component catalog are also included, with property types,
+binding contracts, and blocked capabilities taken from the published catalog JSON.
+
+Published Docusaurus `/docs/category/...` addresses remain available as static compatibility pages. They forward to
+the corresponding overview or developer setup guide, preserving query strings and anchors, and provide a direct
+link when JavaScript is disabled. Their canonical metadata points to the destination; compatibility pages are
+excluded from search and the sitemap.
+
+## Fumadocs upgrade notes
+
+The September 2026 update moves Core/UI from 16.15.4 to 16.15.12, MDX from 15.4.0 to 15.4.3, and OpenAPI from
+11.3.5 to 12.0.1. Review the upstream [Core](https://github.com/fuma-nama/fumadocs/blob/dev/packages/core/CHANGELOG.md),
+[UI](https://github.com/fuma-nama/fumadocs/blob/dev/packages/radix-ui/CHANGELOG.md),
+[MDX](https://github.com/fuma-nama/fumadocs/blob/dev/packages/mdx/CHANGELOG.md), and
+[OpenAPI](https://github.com/fuma-nama/fumadocs/blob/dev/packages/openapi/CHANGELOG.md) changelogs when upgrading.
+
+- Core/UI and MDX now declare side effects for better tree shaking. UI also fixes tabs reverting to the URL hash.
+- Core's `llms({ renderPage })` API provides the shared `index()`, `page()`, and `full()` exports.
+- OpenAPI 12 replaces several custom renderer options and hooks. This site uses `createOpenAPIPage()` and
+  `getOpenAPIPageProps()` without those removed overrides; the built-in renderer retains all request languages.
+  The Scalar adapter receives an equivalent nonrecursive union for unconstrained JSON values to avoid recursive
+  schema expansion during rendering. The generated public OpenAPI document remains unchanged.
+- MDX 15.4.3 fixes duplicate compilation output when its experimental build cache is enabled. We leave that cache
+  disabled: its current key checks source content without accounting for all compiler configuration changes.
+- The existing macro collections, processed-Markdown component adapters, and static search remain supported.
+  Typed version roots and server-side MCP tools are available upstream but are not needed by this static site.
+
+## Kapa AI
+
+The compact Homarr mascot in the bottom-right opens **Ask AI**. It slowly spins when idle and gives a subtle claw movement and wink on hover. Animation respects reduced motion.
+
+The launcher uses Homarr's existing public Kapa Website ID. The root layout loads the widget once across
+client-side navigation and follows the docs light or dark theme. **Search** and `Ctrl+K` / `Cmd+K` always use Fumadocs search, including when Kapa is unavailable.
+
+Set `KAPA_WEBSITE_ID` at build time to use a different Kapa Website Widget integration. An explicitly empty value
+disables the widget, for example `KAPA_WEBSITE_ID= bun run --filter @homarr/docs build`. This is a public integration ID
+included in exported pages, not a Kapa API key. Rebuild the static export after changing it.
+
+In the Kapa dashboard, confirm the integration is live and enable the production and preview domains. Restoring the
+script does not verify that the historical integration is still active. Follow the
+[Kapa widget setup](https://docs.kapa.ai/integrations/website-widget/quickstart) for domain restrictions and CSP settings.
+
+After changing the documentation structure, review the Website Crawl source in Kapa: use the deployed `/docs` URL as
+the start URL and preview `main` as the content selector. Replace any old Docusaurus-specific selector and check that
+titles, headings, code samples, and integration details appear in the extracted Markdown. Docs are exported as HTML;
+the site also publishes `/sitemap.xml` and permits crawling in `/robots.txt`. The `/llms.txt` exports do not configure
+Kapa ingestion automatically. See [Kapa source setup](https://docs.kapa.ai/getting-started/index-your-first-source).
+
+Before publishing, check that Ask AI opens after navigating between pages, ask a documentation question, and verify
+its citations point to the current docs. In a separate check, block `widget.kapa.ai` and confirm search still works.
+
+## Release verification
+
+The production image compiles the docs itself; it does not depend on a host `out/` directory.
+Build-time `HOMARR_WEBSITE_URL` controls canonical metadata. Runtime URL overrides configure Workshop connections
+but do not rewrite already-exported canonical URLs.
+
+PostHog records SPA pageviews, installation clicks, searches with no results (including the search query), and Workshop
+content downloads and submission starts/completions through `hog.homarr.dev`. Downloads include JSON files and
+successful JSON/CSS clipboard copies. All events carry `site` and `source_path`. Autocapture, page-leave events, and
+session replay are disabled; tracked URL query strings and fragments are removed. Localhost and `?analytics_test`
+traffic carries `verification=true`; exclude it from production reports.
+
+Carbon loads one visible placement after the desktop TOC, below API examples, or below content on other layouts.
+The homepage is excluded at every viewport size. Navigation reloads the ad script; resizing changes placement only when crossing its breakpoint. Ad blockers
+or no-fill responses must not prevent content, navigation, or search from working.
+
+To preview Carbon locally, start docs with `NEXT_PUBLIC_ENABLE_CARBON_ADS=true bun run dev:docs`. Production builds
+enable ads automatically. When the TOC collapses into a toggle, the ad appears below the content before “Edit this page”.

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1,9 +1,10 @@
 ---
+title: Homarr 1.0 - complete rewrite of all systems
+date: 2024-09-23
 authors:
   - manuel-rw
 ---
 
-# Homarr 1.0 - complete rewrite of all systems
 We proudly present to you - Homarr ``1.0``.
 We have started work on this new version back in 2023 and have worked tirelessly for months on this brand-new dashboard.
 
@@ -28,14 +29,14 @@ reliability and scalability compared to < ``1.0``.
 - **Improved performance**: We have upgraded the underlying framework of Homarr and take advantage
 of an in-memory message bus and websockets to deliver data near realtime to you.
 
-<!-- truncate -->
+{/* Historical excerpt boundary. */}
 
 ## Breaking changes
-:::warning
+<Alert type="warning">
 
 Please consult the breaking changes list & upgrade guide if you used third-party installation methods.
 
-:::
+</Alert>
 
 - Docker Image
   - Removed support for ``arm/v7`` -> upgrade to newer architectures as an alternative

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

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

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

@@ -1,14 +1,14 @@
 ---
+title: Migrate from 0.15.10+ to 1.0.0
+date: 2025-01-19
 authors:
   - meierschlumpf
 ---
 
-# Migrate from 0.15.10+ to 1.0.0
-
 In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
 If you are still on a version before 0.15.10, please update to 0.15.10 where we introduced the migration export page.
 
-<!-- truncate -->
+{/* Historical excerpt boundary. */}
 
 ## Preserve your old installation
 
@@ -22,17 +22,17 @@ Plan to recreate your apps, integrations, and boards manually in the new install
 
 We highly recommend to create a parallel installation of Homarr 1.0.0.
 So if something with for example the import does not quite work, the data in the old installation is still available.
-To do this you can follow the appropriate [installation guide](https://homarr.dev/docs/category/installation-1) for your system.
+To do this you can follow the appropriate [installation guide](/docs/getting-started) for your system.
 Please note that if you are using docker you need to specify a diffrent external port for the new installation as the old one had the same port.
 So in your compose file the ports would be `7576:7575` instead of `7575:7575`.
 
 ## Import your data
 
-:::warning Legacy guide
+<Alert type="warning" title="Legacy guide">
 
 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.
 
-:::
+</Alert>
 
 ## Remove the old installation
 

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

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

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

@@ -1,27 +1,64 @@
 ---
+title: Homarr 2.0.0 - Workshop, Custom Widgets and a rebuilt board
+date: 2026-10-02
 authors:
   - ajnart
-tags: [homarr, update, version, assistant, custom widgets, dashboards, docker]
-description: Homarr 2.0 introduces Custom Widgets and Workshop, rebuilt board editing, Assistant tooling, responsive layouts, onboarding, and more.
-image: ./img/homarr-v2-dashboard.webp
+tags: [homarr, update, version, assistant, custom widgets, dashboards, docker, mcp]
+description: Homarr 2.0 introduces Custom Widgets and Workshop, rebuilt board editing, Assistant and MCP tooling that turns Homarr into the front door to your homelab, responsive layouts, onboarding, and more.
+image: ./img/homarr-v2-recap.webp
 draft: false
 ---
 
 # Homarr 2.0.0 - Workshop, Custom Widgets and a rebuilt board
 
+![Homarr v2 release recap showing Custom Widgets v2, Workshop, Homarr Assistant, advanced views and 31 new integrations](./img/homarr-v2-recap.webp)
+
 First, thank you.
 
 Many of you used the v2 demo when it was still rough, found bugs and came back to test the next build. Others translated Homarr, answered questions, contributed code or simply kept using it. We would not be shipping this without you.
 
 We are also planning a small batch of **free, limited-edition Homarr swag** for Workshop contributors and a few randomly picked community members. It is not for sale and it is not for profit. No Homarr merch empire, sorry.
 
+If you're thinking, “I ain't reading all dat,” don't worry. We made a video for your short attention span.
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    playsInline
+    preload="metadata"
+    poster={require("./img/homarr-v2-recap.webp").default.src}
+    width={1920}
+    height={1080}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Homarr 2.0 feature overview."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/homarr-v2-showreel.mp4" type="video/mp4" />
+  </video>
+  <figcaption>Homarr 2.0 in under two minutes.</figcaption>
+</figure>
+
 Homarr 2.0 builds on the dashboard you already use. Here is what changed.
 
 ![A populated Homarr 2.0 dashboard with compact widgets, an Assistant, and an application rail](./img/homarr-v2-dashboard.webp)
 
-<!-- truncate -->
+{/* Historical excerpt boundary. */}
 
-Update your Homarr image as usual. Homarr runs database migrations automatically when the updated container starts; no manual database migration or separate v2 upgrade procedure is needed. Workshop uses the production service by default, with no preview URL configuration required.
+**Back up before upgrading:** database migrations run automatically at startup and change the existing database in place. Follow the [upgrade and rollback guidance](/docs/getting-started/installation/docker#update), including the note on board sizing. **MySQL users must convert before upgrading**, as explained below. Workshop uses the production service by default, with no preview URL configuration required.
+
+## Database support in v2
+
+Homarr v2 drops MySQL support and keeps SQLite (the default) and PostgreSQL. Supporting fewer database engines lets us focus migration testing on those two. Existing MySQL installations have a standalone conversion script to move their data to SQLite before upgrading.
+
+<details>
+<summary>Using MySQL? How to migrate</summary>
+
+1. Update to the latest stable v1 release, then back up your MySQL database, appdata, and encryption key.
+2. Stop Homarr and run the MySQL-to-SQLite converter. It checks the copied data and leaves MySQL unchanged.
+3. Start v2 with the converted database, your existing appdata, and the **same `SECRET_ENCRYPTION_KEY`**.
+
+The converter is verified against the v1.77.1 schema and rejects unknown schemas. See the [migration guide](/docs/advanced/mysql-to-sqlite) for commands, supported inputs, and rollback instructions.
+
+</details>
 
 ## Custom Widgets v2 and Workshop
 
@@ -33,9 +70,11 @@ Custom Widgets v2 lets you build widgets from JSX, API requests, actions and typ
 
 This was partly inspired by [Google's upcoming Create My Widget feature](https://blog.google/products-and-platforms/platforms/android/gemini-intelligence/): describe a widget in normal language and let AI make it. Coding knowledge is optional. Knowing what the API does still helps; AI has not fixed bad documentation. Yet.
 
-![The Custom Widget v2 workbench after a live exchange-rate request successfully renders its preview](./img/custom-widget-workbench.webp)
+![The Custom Widget workbench displaying a Sonarr response through a saved integration](./img/custom-widget-workbench.png)
 
-A `homarr-custom-widget-v2` definition can use several fixed-origin API sources. Credentials are encrypted separately and stay out of exports and Workshop submissions. Actions support `GET`, `POST`, `PUT`, `PATCH` and `DELETE`; requests have host checks, timeouts, size limits, permissions and rate limits. Custom Widgets remain **Beta** in 2.0.
+![A working Pokédex Custom Widget on a local Homarr dashboard, with a search field, Pokémon artwork and stats](./img/custom-widget-dashboard.webp)
+
+A `homarr-custom-widget-v2` definition can use several fixed-origin API sources. Credentials are encrypted separately and stay out of exports and Workshop submissions. Actions support `GET`, `POST`, `PUT`, `PATCH` and `DELETE`; requests have host checks, timeouts, size limits, permissions and rate limits.
 
 ### Share widgets and Custom CSS
 
@@ -43,11 +82,17 @@ A `homarr-custom-widget-v2` definition can use several fixed-origin API sources.
 
 ![The Community Workshop catalog inside Custom Widget management](./img/community-workshop.webp)
 
-:::warning Workshop is moderated
+<Alert type="warning" title="Workshop is moderated">
 
 AI makes widgets easy to produce. It does not make the first thing it coughs up worth publishing. **Do not dump untested slop into Workshop.** Test it, add a useful screenshot and explain its setup. Workshop is moderated.
 
-:::
+</Alert>
+
+### Docusaurus + PocketBase for the docs and Workshop
+
+Our docs and Workshop now share a Docusaurus + PocketBase deployment. Docusaurus compiles the website into static HTML, CSS and JavaScript at build time. A Go service built on PocketBase serves those files and provides the Workshop backend for accounts, submissions, votes, comments and moderation.
+
+The production image packages both together under the same origin. Node.js is used to build the website, but is not needed to serve it in production. Workshop's persistent data lives separately in `/pb_data`, so replacing the image does not replace community content. This is the website and Workshop architecture; your self-hosted Homarr dashboard remains a separate application.
 
 ### The ultimate Homarr update
 
@@ -59,16 +104,110 @@ We have called this the **"ultimate Homarr update"**. Not because work stops, bu
 
 We threw out the old drag-and-drop system and rebuilt it on [`dnd-kit`](https://dndkit.com/). Moves and eight-direction resizes are transactional: Homarr previews the result, checks collisions and only saves a valid layout. Bad moves roll back instead of wrecking the board. In short: less fighting with your own dashboard.
 
-![A Calendar tile moving across the rebuilt Homarr 2.0 board grid](./img/drag-and-drop.gif)
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/drag-and-resize-poster.webp").default.src}
+    width={1770}
+    height={706}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Move and resize a tile with the new drag-and-drop system."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/drag-and-resize.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/drag-and-resize.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Move and resize a tile with the new drag-and-drop system.</figcaption>
+</figure>
 
 ### Goodbye Groups and sections, bonjour Containers
 
-Groups and dynamic sections did nearly the same job, so **Containers replace both**. They hold apps, widgets and other Containers. Hold <kbd>Ctrl</kbd> or <kbd>Command</kbd> to move several items at once.
+Groups and dynamic sections did nearly the same job, so **Containers replace both**. They hold apps, widgets and other Containers. Move a Container with its contents, or collapse it when you need the space.
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/containers-poster.webp").default.src}
+    width={1770}
+    height={716}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Move, collapse and reopen a Container without rearranging its contents."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/containers.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/containers.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Move, collapse and reopen a Container without rearranging its contents.</figcaption>
+</figure>
+
+Hold <kbd>Ctrl</kbd> or <kbd>Command</kbd> while clicking to select several items, then use **Move to** to put them in a Container.
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/multi-select-poster.webp").default.src}
+    width={1770}
+    height={716}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Command-click two apps, then move them into the same Container."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/multi-select.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/multi-select.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Command-click two apps, then move them into the same Container.</figcaption>
+</figure>
 
 ### One board, several layouts
 
 Boards also have Base and Mobile layouts, plus optional breakpoints. **Reset from Base** creates a Mobile starting point without duplicating the board.
 
+### Fixed sidebars
+
+Keep app shortcuts or widgets in a sidebar while the main board scrolls. Enable a sidebar and choose its width in board settings.
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/sidebar-settings-poster.webp").default.src}
+    width={1600}
+    height={700}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Enable the right sidebar and set its width."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/sidebar-settings.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/sidebar-settings.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Enable the right sidebar and set its width.</figcaption>
+</figure>
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/fixed-sidebar-poster.webp").default.src}
+    width={1580}
+    height={640}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="The board scrolls; the app shortcuts stay in place."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/fixed-sidebar.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/fixed-sidebar.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>The board scrolls; the app shortcuts stay in place.</figcaption>
+</figure>
+
 ## Homarr Assistant
 
 ### Work with live Homarr data
@@ -81,17 +220,70 @@ Open it with <kbd>Shift</kbd> + <kbd>A</kbd>. <kbd>Cmd</kbd>/<kbd>Ctrl</kbd> + <
 
 ### The Homarr provider
 
-:::note
+<Alert type="note">
 
 Assistant ships with a **"Homarr provider"**. It is free, will never offer paid plans, and is paid for by [Ajnart](https://github.com/ajnart) using the ad revenue from this website.
 
 It only uses zero-data-retention (ZDR) providers. [The provider is open source](https://github.com/homarr-labs/homarr/blob/release/v2/apps/workshop/homarr_provider.go), and neither prompts nor responses are logged. We are not selling your data. Pinky promise.
 
-:::
+</Alert>
 
 ### External assistants through MCP
 
 External assistants can use the same permission-checked tools through `/api/mcp`, with an API key or OAuth 2.1 with PKCE.
+The most powerful one gets its own section.
+
+## The front door to your homelab
+
+Homarr already knows how to reach your services: their URLs, API keys and auth headers. v2 adds one API endpoint that
+lets you use them without ever seeing them.
+
+`POST /api/integrations/request` calls **any HTTP endpoint** on a saved integration. It is also available as tRPC
+`integration.request` and MCP `integration_request`. You send the integration, a method and a path, authenticated with
+your Homarr API key or session. Homarr checks your access, adds the credentials it stores and hands back the service's
+answer:
+
+![A request from a Custom Widget or an agent goes to Homarr with your API key. Homarr authenticates you, checks full integration access, adds the saved Sonarr API key from its encrypted vault, calls Sonarr on its saved URL and returns the response](./img/front-door-diagram.gif)
+
+The secrets stay in Homarr. API keys, passwords and tokens are stored encrypted, no API returns them, and Homarr redacts
+them from responses. If a service's API can do something, you can do it through Homarr, even when Homarr has no button
+for it:
+
+- **Custom Widgets** bind a saved integration as a [source](/docs/management/integrations#beyond-native-widgets) and call
+  its endpoints, so you never paste credentials into widget code.
+- **Agents** act on your behalf through MCP. The agent reads the service's official API docs, tells you which integration
+  it will use and what the call changes, then reports the result.
+
+It stays inside the lines:
+
+- Paths stay within the saved integration URL, and redirects are rejected.
+- Every request needs **full integration access**. `DELETE` needs explicit confirmation, and in Assistant every request,
+  even a `GET`, waits for your approval.
+
+### One prompt, seven services
+
+We asked a local model, through Homarr's MCP server:
+
+> Could you install a notification provider and then set it up everywhere it's supported in my installed integrations?
+
+It checked the Docker endpoint, asked which provider to use (it recommended ntfy), deployed ntfy and reported back:
+
+| Service     | How                                                                       | Verified                                   |
+| ----------- | ------------------------------------------------------------------------- | ------------------------------------------ |
+| Sonarr      | Native ntfy connection for grabs, downloads, upgrades and health          | Test fired ✓                               |
+| Radarr      | Native ntfy connection, plus movie added                                  | Test fired ✓                               |
+| Seerr       | Webhook with a JSON payload for readable titles                           | Fires on request, approve, available, fail |
+| SABnzbd     | 5.1.3 has no ntfy support, so a completion script on the default category | Dry run ✓                                  |
+| qBittorrent | `[AutoRun]` completion hook in `qBittorrent.conf`                         | Persisted after restart                    |
+| Bazarr      | ntfy provider enabled for subtitle events                                 | Restarted ✓                                |
+| Beszel      | Webhook with status, CPU, memory and disk alerts on all eight systems     | 29 alerts created                          |
+
+Two test notifications later, the phone buzzed. It cost $0: Qwen3.8-27B ran locally through MLX. The only side effect
+was warm feet.
+
+See [authenticated integration requests](/docs/management/mcp#authenticated-integration-requests) and the
+[API contract](/docs/management/api#call-any-integration-api-endpoint) for selectors, limits and the services that
+cannot use it.
 
 ## The rest (there is a lot)
 
@@ -105,7 +297,23 @@ A six-stage setup studio handles the first admin, core settings, Docker discover
 
 Boards now live in a searchable gallery with keyboard navigation. Open it from the header or press <kbd>Shift</kbd> + <kbd>C</kbd>.
 
-![A visual board card inside the searchable Homarr board switcher](./img/board-switcher.webp)
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/board-switcher-poster.webp").default.src}
+    width={1920}
+    height={778}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Open the switcher, filter by name and press Enter to open a board."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/board-switcher.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/board-switcher.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Open the switcher, filter by name and press Enter to open a board.</figcaption>
+</figure>
 
 ### Command menu and keybinds
 
@@ -114,10 +322,17 @@ keybinds cover Assistant, editing, selection and advanced widget views.
 
 ### Customizable header
 
-Pick which buttons appear, put them on the left, center or right, and change their order.
+Add direct links to boards and shortcuts to features such as search, Docker and settings. Put them on the left, center or right, and change their order.
+
+![A customized header with a board link on the left, board switching and search in the center, and Docker, theme and settings on the right](./img/customized-header.webp)
+
+<details>
+<summary>Arrange it in the Header studio</summary>
 
 ![The Header studio showing left, center, and right zones plus available controls](./img/header-studio.webp)
 
+</details>
+
 ### Instance branding
 
 Change the name, logo, favicon, colors, corner styles and login page. Global CSS applies instance-wide; board CSS can override it. Only give that power to admins you trust. CSS remains CSS.
@@ -126,7 +341,65 @@ Change the name, logo, favicon, colors, corner styles and login page. Global CSS
 
 ### Widgets
 
-Add content without leaving the board. Settings have live previews, and supported widgets have advanced views. Weather and Clock were redesigned; Air Quality, Countdown and Timer are new.
+Add content without leaving the board. Settings have live previews. Weather and Clock were redesigned; Air Quality, Countdown and Timer are new.
+
+![The Air Quality widget showing the current AQI and a location trend](./img/air-quality.webp)
+
+![The Countdown widget showing time remaining until an event](./img/countdown.webp)
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/timer-poster.webp").default.src}
+    width={950}
+    height={500}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Start, pause and reset Timer without leaving the board."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/timer.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/timer.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Start, pause and reset Timer without leaving the board.</figcaption>
+</figure>
+
+Supported widgets also have **advanced views**. Hover over a widget and hold <kbd>Shift</kbd> for **half a second** to open one.
+
+<figure style={{ margin: "1.5rem 0" }}>
+  <video
+    controls
+    muted
+    playsInline
+    preload="none"
+    poster={require("./img/advanced-widget-poster.webp").default.src}
+    width={864}
+    height={600}
+    style={{ width: "100%", height: "auto", borderRadius: "0.5rem" }}
+    aria-label="Hold Shift for half a second over Downloads to open its advanced view."
+  >
+    <source src="https://media.homarr.dev/videos/homarr-2.0/advanced-widget.mp4" type="video/mp4" />
+    <track kind="captions" src="/media/homarr-2.0/advanced-widget.vtt" srcLang="en" label="English" />
+  </video>
+  <figcaption>Hold Shift for half a second over Downloads to open its advanced view.</figcaption>
+</figure>
+
+### Statistics and 31 new integrations
+
+The new [Statistics widget](/docs/widgets/stats) combines fields from different services in one grid: Sonarr shows beside Paperless-ngx documents, Navidrome songs or Homebox inventory. Choose cards, compact rows or tables grouped by integration. Click a metric for related fields, or open **Advanced view** from the context menu to see every available field from the selected sources.
+
+Add your services in **Management → Integrations**, then select them and their metrics in Statistics settings. Labels, order and abbreviated values are configurable; the widget's local view controls let you try a different arrangement without changing the shared board. The demo board includes mocked cards, rows and tables.
+
+This release adds:
+
+- **Media and libraries:** Autobrr, FileFlows, Jackett, Jellystat, Komga, Maintainerr, RomM, Stash, Tube Archivist, Unmanic, xTeVe and Your Spotify.
+- **Monitoring and networking:** Caddy, Changedetection.io, Frigate, Gatus, Healthchecks, NetAlertX, Netdata, Prometheus, Scrutiny and Syncthing Relay.
+- **Collections and home:** Homebox, Karakeep, Linkwarden, Mealie, Miniflux, Plant-it, Spoolman, Tandoor and Trilium.
+
+The [integration and metric reference](/docs/widgets/stats#new-service-integrations-in-v2) links to each setup guide. Jackett also joins the Indexer Manager widget. Existing supported integrations reuse their Homarr clients.
+
+Statistics keeps saved snapshots until you refresh them. Multiple metrics from one source share retrieval, and dashboard loads read cached data instead of refetching every service. **Right-click → Refresh** retrieves new source data and shows the oldest saved snapshot's age; unsuccessful refreshes keep the previous values. These are on-demand snapshots, not live monitoring.
 
 ### Docker and Podman
 
@@ -144,11 +417,16 @@ Groups use a new Viewer, Editor and Admin matrix. The API, Assistant and MCP fol
 
 Board startup work runs in parallel, heavy screens load when opened, and identical integration requests share work instead of doing it twice.
 
+## Deploy on Hostinger
+
+[Hostinger now offers a one-click Docker deployment of Homarr](https://www.hostg.xyz/aff_c?offer_id=815&aff_id=244277&url_id=6861) on its VPS plans. They maintain the deployment template, and you manage the resulting VPS and Homarr instance. Our new [Hostinger installation guide](/docs/getting-started/installation/hostinger) walks through deployment and first setup.
+
+We deploy the Homarr Workshop and the compiled documentation website on the VPS provided by Hostinger. Thank you for hosting this part of Homarr's infrastructure. We have an affiliate partnership as well: purchases through a referral link may support Homarr.
+
 ## Compatibility notes
 
 - Legacy Custom JSX definitions enter a migration state. Homarr keeps encrypted credentials and an archived copy until the v2 definition validates.
 - Mobile layouts place rail content in the main flow instead of displaying rails.
-- Custom Widgets remain Beta.
 - Assistant and MCP do not bypass permissions.
 
 ## Links

apps/docs/components.json

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

apps/docs/docs/advanced/_category_.json

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

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

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

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

@@ -1,8 +1,8 @@
 # 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 with non-blocking background operations. Run it directly from a checkout with `bun run 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 `bun run 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.
 
 ## Requirements
 
@@ -14,7 +14,7 @@ To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your
 ## Interactive Development Browser
 
 ```bash
-pnpm dev:cli --
+bun run dev:cli --
 # or with global binary:
 homarr
 ```
@@ -66,7 +66,7 @@ Pulls and builds run asynchronously in the background. Press `t` to open the tas
 ```bash
 homarr dash
 # or
-pnpm dev:cli -- dash
+bun run dev:cli -- dash
 ```
 
 The instance dashboard displays all running and stopped Homarr containers, published ports, health states, and resource volumes.
@@ -81,7 +81,7 @@ The instance dashboard displays all running and stopped Homarr containers, publi
 
 ## 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`).
+The commands below use the installed `homarr` binary. Without global installation, prefix each command with `bun run dev:cli --` (for example, `bun run dev:cli -- list`).
 
 ### Launch Instances
 
@@ -133,7 +133,7 @@ homarr ci 6441 --watch
 homarr shell homarr-dev
 
 # Run specific command in container
-homarr shell homarr-dev pnpm db:migration:sqlite:run
+homarr shell homarr-dev bun run db:migration:sqlite:run
 ```
 
 ### Image & Volume Management

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

@@ -1,10 +1,10 @@
 # Fix usernames
 
-:::info
+<Alert type="info">
 
 This guide requires that you understand [how to access the CLI](../).
 
-:::
+</Alert>
 
 If you somehow get into a situation where you have users with usernames that contain uppercase characters and you are no longer able to log in, you can use the following command to fix the usernames.
 

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

@@ -50,20 +50,20 @@ The repository's host-side CLI can build the current checkout and run it as a na
 ![Homarr developer CLI showing pull requests, local images, and PR CI status](./img/homarr-dev-cli.png)
 
 ```sh
-pnpm cli harness setup feature-board
+bun run cli harness setup feature-board
 ```
 
 This creates `homarr:feature-board`, starts it with persistent demo data, and prints the assigned URL. Query the port
 again with:
 
 ```sh
-pnpm cli harness port feature-board
+bun run cli harness port feature-board
 ```
 
 Pass environment overrides with repeated `--env` options:
 
 ```sh
-pnpm cli harness setup feature-board \
+bun run cli harness setup feature-board \
   --env WORKSHOP_WEB_URL=https://example.test \
   --env FEATURE_FLAG=true
 ```

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

@@ -1,10 +1,10 @@
 # Integrations
 
-:::info
+<Alert type="info">
 
 This guide requires that you understand [how to access the CLI](../).
 
-:::
+</Alert>
 
 Using these commands, you can manage the integrations from the CLI:
 

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

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

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

@@ -1,10 +1,10 @@
 # Password Recovery
 
-:::info
+<Alert type="info">
 
 This guide requires that you understand [how to access the CLI](../).
 
-:::
+</Alert>
 
 Using this command, you can forcefully reset the password of a user.
 It will be set to a random value and the hash for the user will be updated.

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

@@ -1,10 +1,10 @@
 # Users
 
-:::info
+<Alert type="info">
 
 This guide requires that you understand [how to access the CLI](../).
 
-:::
+</Alert>
 
 Using these commands, you can manage the users from the CLI:
 

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

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

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

@@ -12,22 +12,22 @@ sidebar_position: 1
 
 ### 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.
+- **Node.js 24.18.0**: application and tooling runtime, pinned in `mise.toml`.
+- **Bun 1.4.2**: Install the version pinned in `mise.toml` from the [official website](https://bun.sh/docs/installation).
 - **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:
+Install dependencies once at the repository root. Bun uses a hoisted workspace installation, so compatible dependencies
+are shared across packages. Catalog versions, patches and overrides live in the root `package.json`.
 
 ```sh
-corepack enable
-corepack install
-pnpm install --frozen-lockfile
+bun install --frozen-lockfile
 ```
 
+Next.js, operational commands and SQLite run on Node.js. Bun installs dependencies and dispatches package scripts.
+
 ### Run the Homarr application
 
 1. Copy `.env.example` to `.env`.
@@ -46,79 +46,98 @@ cp .env.example .env
 Terminal 1:
 
 ```sh
-pnpm docker:dev
+bun run docker:dev
 ```
 
 Terminal 2:
 
 ```sh
-pnpm db:migration:sqlite:run
-pnpm dev
+bun run db:migration:sqlite:run
+bun run dev
 ```
 
 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.
+Use `bun run docker:dev:up` instead when you only need Redis in the background. Running the migration also seeds the
+default data; use `bun run db:seed` to seed it explicitly later.
 
-`pnpm dev` starts only Next.js. When your work needs scheduled tasks or live subscriptions, run the relevant service
+`bun run dev` starts only Next.js. When your work needs scheduled tasks or live subscriptions, run the relevant service
 in a separate terminal alongside it:
 
 ```sh
-pnpm --filter @homarr/tasks dev
+bun run --filter @homarr/tasks dev
 ```
 
 ```sh
-pnpm --filter @homarr/websocket dev
+bun run --filter @homarr/websocket dev
 ```
 
 The WebSocket service listens on port 3001. Production startup embeds both services, so these extra commands are
 only needed for development.
 
-Workshop contributors can set up PocketBase and Docusaurus with the dedicated
-[Workshop development guide](./workshop).
+Workshop contributors can set up PocketBase and Fumadocs with the dedicated
+[Workshop development guide](/docs/advanced/development/workshop).
 
 ### Useful commands
 
-- `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.
+- `bun run dev` — Next.js on port 3000.
+- `bun run dev:benchmark` — authenticated-board benchmark; readiness-only `--smoke` runs are not performance claims.
+- `bun run dev:cli -- dev` — browse and run local images and remote pull-request images.
+- `bun run dev:cli -- build <name>` — build the current checkout as `homarr:<name>`.
+- `bun run dev:cli -- build --pr <number>` — build a pull request from a temporary checkout.
+- `bun run dev:cli -- rebuild <name>` — rebuild an image from its recorded checkout or pull request.
+- `bun run dev:cli:install` — optionally install the developer CLI as a `homarr` binary.
+- `bun run dev:docs` — Fumadocs on port 3003.
+- `bun run docker:dev:up` — Redis development service in the background.
+- `bun run cli` — Homarr operations CLI.
+- `bun run db:migration:sqlite:run` — create or update a SQLite database.
+- `bun run db:seed` — seed the default database data explicitly.
+- `bun run db:studio` — inspect the database.
+- `bun run format` / `bun run format:fix` — check or apply oxfmt.
+- `bun run lint` / `bun run lint:fix` — check or apply oxlint.
+- `bun run typecheck` — typecheck all workspaces.
+- `bun run test` — unit and contract suites.
+- `bun run build` — production monorepo build.
 - `docker build -t homarr:local .` — build a production Docker image.
 - `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:local` — run it.
 
 ## CI and focused validation
 
-The main CI workflow runs lint, typechecking, affected workspace builds, workspace configuration checks, OpenAPI validation, and Custom Widget architecture and bundle checks. Unit and E2E suites do not run in CI. Preview images publish after the Fast gate and both architecture builds succeed; browser tests do not block publication. The container job builds an amd64 image when no preview image was built.
+The main CI workflow validates SQLite and PostgreSQL migrations before lint, typechecking, affected workspace builds, workspace configuration, OpenAPI, and Custom Widget architecture and bundle checks. Manual container validation builds an amd64 image and exercises MySQL conversion, authentication, and restart persistence. Preview publication requires the Fast gate and both architecture builds.
 
-Workshop CI runs only when its workflow or Docker build inputs change. It validates Compose configuration and publishes production images on its configured release branches. Its Docker integration and image tests are manual; workspace typechecks run in the main Fast gate.
+Workshop CI runs when its workflow or Docker build inputs change. Pull requests exercise production images on amd64 and arm64; release branches publish them after Compose validation. Workspace typechecks run in the main Fast gate.
 
 Choose the smallest relevant suite when changing behavior:
 
-| Command                                           | Scope                                                          | Requirements                                                          |
-| ------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------- |
-| `pnpm test <file>`                                | Focused unit or contract tests                                 | Workspace dependencies                                                |
-| `pnpm test`                                       | All unit and contract tests, without Docker integration suites | Workspace dependencies                                                |
-| `pnpm test:coverage`                              | Unit and contract tests with coverage                          | Workspace dependencies                                                |
-| `pnpm test:integration <file>`                    | Docker-backed service and database compatibility tests         | Docker                                                                |
-| `pnpm test:e2e <file>`                            | Browser and container scenarios                                | Docker; Playwright Chromium and system dependencies for browser tests |
-| `pnpm test:docs-screenshots`                      | Regenerate Assistant documentation screenshots                 | Same browser prerequisites                                            |
-| `pnpm test:workshop` / `pnpm test:workshop-image` | Workshop integration / production-image validation             | Docker                                                                |
+| Command                                                 | Scope                                                          | Requirements                                                          |
+| ------------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------- |
+| `bun run test <file>`                                   | Focused unit or contract tests                                 | Workspace dependencies                                                |
+| `bun run test`                                          | All unit and contract tests, without Docker integration suites | Workspace dependencies                                                |
+| `bun run test:coverage`                                 | Unit and contract tests with coverage                          | Workspace dependencies                                                |
+| `bun run test:integration <file>`                       | Docker-backed service and database compatibility tests         | Docker                                                                |
+| `bun run test:e2e <file>`                               | Browser and container scenarios                                | Docker; Playwright Chromium and system dependencies for browser tests |
+| `bun run test:docs-screenshots`                         | Regenerate Assistant documentation screenshots                 | Same browser prerequisites                                            |
+| `bun run test:workshop` / `bun run test:workshop-image` | Workshop integration / production-image validation             | Docker                                                                |
 
 Omit `<file>` to run all tests in that command's scope. E2E and screenshot commands use a local image tagged `homarr-e2e`, or an image selected with `HOMARR_E2E_IMAGE`. The default commands run once without automatic retries; coverage is opt-in. The screenshot generator is excluded from both unit and E2E commands.
 
 Keep behavioral coverage for authorization, migrations, persistence, and widget execution. Avoid tests that only search source code for particular component names, JSX, CSS, or documentation wording.
+
+## Documentation development
+
+Run `bun run dev:docs` to open the Next.js and Fumadocs site at `http://127.0.0.1:3003`. Content lives in
+`apps/docs/docs/`; the nearest `meta.json` controls navigation. Keep integration and widget setup metadata in their
+typed `index.ts` files alongside the page.
+
+After changing content, navigation, or shared MDX components, run:
+
+```sh
+bun run --filter @homarr/docs build
+bun run --filter @homarr/docs validate:links
+bun run --filter @homarr/docs verify:search
+bun run --filter @homarr/docs verify:seo
+```
+
+The build writes a static site to `apps/docs/out/`. Check heading links, search results, and the page's Markdown export
+when changing shared components. The [Fumadocs documentation](https://fumadocs.dev/docs) describes supported components
+and source APIs; match examples to the versions installed in this repository.

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

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