style: format merged dev files

* feat: announce Homarr v2 beta

* chore: refine v2 beta announcement

* feat: expand v2 beta guidance

* chore: refine v2 beta resources

* chore: simplify v2 beta modal

* chore: improve v2 beta feedback links

* fix: keep v2 modal above header

* chore: sharpen v2 beta message

* fix: clear header for v2 modal

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

@@ -1,40 +1,195 @@
 ---
 name: codebase-context
-description: Navigate Homarr's monorepo architecture and reuse shared packages. Use when locating code, choosing a package boundary, understanding runtime services, tRPC, databases, widgets, integrations, cron jobs, Custom Widgets, Workshop, or checking @homarr/common before creating a utility.
+description: Comprehensive Homarr codebase architecture and conventions reference. Use when orienting in the monorepo, understanding package dependency layers, the three runtime services and ports, tRPC router structure, multi-database support, widget/integration/cron system architecture, routing, auth providers, env vars, or key patterns before writing code.
 ---
 
 # Homarr Codebase Context
 
-Orient from the current checkout before editing. Treat package manifests, exports, and source as authoritative when they differ from this snapshot.
+Homarr is an open-source, self-hosted dashboard for managing homelab services. It integrates with 50+ self-hosted apps (media servers, download clients, DNS, NAS, etc.) and provides a drag-and-drop widget-based UI.
 
-## Workflow
+## Tech Stack
 
-1. Confirm the branch and inspect the nearest `package.json`, existing sibling modules, and package exports.
-2. Search `@homarr/common` before creating a general-purpose helper. Read [references/common.md](references/common.md) for every public entrypoint and export.
-3. Read [references/architecture.md](references/architecture.md) when the task crosses packages, runtimes, routing, data, widgets, integrations, cron jobs, Custom Widgets, or Workshop.
-4. Keep the change in the deepest package that owns the behavior. Reuse public entrypoints rather than deep-importing implementation files.
-5. Re-run targeted searches before documenting counts, consumers, or dependency edges; these change faster than the architectural seams.
+- **Monorepo**: pnpm workspaces + Turborepo
+- **Framework**: Next.js (App Router, `output: "standalone"`) — T3 Stack
+- **Language**: TypeScript throughout
+- **ORM**: Drizzle (supports SQLite via better-sqlite3, MySQL, PostgreSQL)
+- **API**: tRPC (HTTP + WebSocket subscriptions) with superjson + OpenAPI bridge via `trpc-to-openapi`
+- **Auth**: NextAuth v5 (database sessions, Credentials/LDAP/OIDC providers)
+- **UI**: Mantine v9 (not Tailwind) + Tabler icons
+- **State**: Jotai (atoms), TanStack Query (server state via tRPC)
+- **Realtime**: WebSocket server (`ws`) for tRPC subscriptions, backed by Redis pub/sub
+- **Cron**: `node-cron` in a standalone Fastify service (`apps/tasks`)
+- **i18n**: next-intl with `[locale]` dynamic segment (prefix mode: `"never"`, locale from cookie)
+- **Testing**: Vitest + jsdom, Playwright for E2E
+- **Lint/Format**: oxlint + oxfmt (not ESLint/Prettier)
+- **Docs**: Docusaurus 3 in `apps/docs/` (`@homarr/docs`)
+- **Package manager**: pnpm 10.34.1, Node >= 24.16.0
 
-## Current toolchain
+## Repository Structure
 
-- 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 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.
+```text
+homarr/
+├── apps/
+│   ├── nextjs/          # Main Next.js application (port 3000)
+│   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
+│   ├── tasks/           # Cron job runner + Fastify tRPC API (port 3002)
+│   └── websocket/       # Standalone tRPC WebSocket server (port 3001)
+├── packages/
+│   ├── api/             # tRPC appRouter, procedures, OpenAPI
+│   ├── auth/            # NextAuth config, providers, session, API keys
+│   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
+│   ├── core/            # Env validation, DB/Redis driver factories, logging
+│   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
+│   ├── widgets/         # All 39 dashboard widgets (definitions + components)
+│   ├── integrations/    # Integration classes (HTTP clients to external apps)
+│   ├── redis/           # Redis pub/sub channels, caching abstractions
+│   ├── translation/     # next-intl setup, locale configs, lang JSON files
+│   ├── ui/              # Shared Mantine components, theme, hooks
+│   ├── validation/      # Shared zod schemas for API/forms
+│   ├── common/          # Shared utilities, IDs, errors
+│   ├── cron-jobs/       # Cron job implementations (25+ jobs)
+│   ├── cron-jobs-core/  # Cron scheduling primitives
+│   ├── cron-job-api/    # tRPC router for job management (start/stop/trigger)
+│   ├── cron-job-status/ # Cron status via Redis
+│   ├── boards/          # Board context, edit mode, cache updater
+│   ├── modals/          # Modal primitives on Mantine
+│   ├── modals-collection/ # Feature modals (apps, boards, docker, etc.)
+│   ├── form/            # useZodForm (Mantine + zod resolver)
+│   ├── forms-collection/# Reusable form UIs (new app, icon picker, upload)
+│   ├── spotlight/       # Command palette / search with multiple modes
+│   ├── request-handler/ # Server request handlers (feeds, integrations)
+│   ├── notifications/   # Mantine notifications wrapper
+│   ├── docker/          # Dockerode-based Docker access
+│   ├── icons/           # Icon DB/repo integration
+│   ├── image-proxy/     # Image proxy + caching
+│   ├── ping/            # Reachability / ping utilities
+│   ├── analytics/       # Server-side analytics (Umami)
+│   ├── server-settings/ # Server setting keys/types
+│   ├── settings/        # User-facing settings UI context
+│   └── cli/             # Node CLI for ops (brocli)
+├── tooling/
+│   ├── typescript/      # Base tsconfig
+│   └── github/          # CI setup action
+├── development/         # Dev docker-compose (Redis, MySQL, PostgreSQL)
+├── e2e/                 # E2E test specs
+└── Dockerfile           # Multi-stage production build
+```
 
-## High-value seams
+## Three Runtime Services
 
-- Server/RSC tRPC: `@homarr/api/server`
-- 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`
-- Widget registry: `packages/widgets/src/registry.ts`
-- Widget loading manifest: `packages/widgets/src/manifest.ts`
-- Integration definitions: `packages/definitions/src/integration.ts`
-- Integration factory: `packages/integrations/src/base/creator.ts`
-- Cron jobs: `packages/cron-jobs/src/jobs/`
-- App routes: `apps/nextjs/src/app/[locale]/`
+| Service   | Port | Role                                         |
+| --------- | ---- | -------------------------------------------- |
+| Next.js   | 3000 | Main web app (SSR + API routes)              |
+| WebSocket | 3001 | tRPC subscriptions via `ws`                  |
+| Tasks     | 3002 | Cron job runner + management API via Fastify |
 
-When a code change affects users, invoke `documentation-sync`. When exposing tRPC through MCP, invoke `mcp-integration`.
+In Docker, nginx listens on **7575** and proxies to all three. The tasks service authenticates via `CRON_JOB_API_KEY` header.
+
+## Package Dependency Layers
+
+1. **Foundation**: `core` (env, DB drivers, Redis client, logging) → no `@homarr` deps
+2. **Domain**: `definitions` → `common` → `core`
+3. **Data**: `db` → `core`, `definitions`, `common`
+4. **Auth**: `auth` → `db`, `definitions`, `core`, `validation`
+5. **Cross-cutting**: `translation`, `validation`, `redis`, `server-settings`
+6. **Feature backends**: `integrations`, `request-handler`, `cron-jobs`, `docker`, `ping`
+7. **API surface**: `api` → pulls in auth, db, redis, integrations, etc.
+8. **UI stack**: `ui`, `modals`, `form`, `notifications`, `boards`, `spotlight`
+9. **Composed features**: `widgets`, `modals-collection`, `forms-collection`
+
+## Key Patterns
+
+### tRPC
+
+- **Server caller** (RSC): `import { api } from "@homarr/api/server"` → cached caller with auth context
+- **Client hooks**: `import { clientApi } from "@homarr/api/client"` → React Query hooks
+- **Router structure**: `packages/api/src/root.ts` defines top-level namespaces (`user`, `board`, `widget`, `integration`, `docker`, `kubernetes`, etc.)
+- **Procedures**: `publicProcedure`, `protectedProcedure`, `permissionRequiredProcedure`, `onboardingProcedure`
+- **WebSocket subscriptions**: Client uses `wsLink` when `type === "subscription"`, connects to port 3001
+
+### Multi-Database Support
+
+Drizzle schemas exist in three parallel implementations:
+
+- `packages/db/schema/sqlite.ts`
+- `packages/db/schema/mysql.ts`
+- `packages/db/schema/postgresql.ts`
+
+Selected at runtime via `DB_DRIVER` env (`better-sqlite3` | `mysql2` | `node-postgres`). Migrations are per-engine in `packages/db/migrations/{sqlite,mysql,postgresql}/`.
+
+### Widget System
+
+Widgets are registered in `packages/widgets/src/index.tsx` as `widgetImports` (must satisfy `Record<WidgetKind, ...>`). Each widget:
+
+- Has a `definition` created via `createWidgetDefinition(kind, { icon, createOptions, supportedIntegrations? })`
+- Uses `optionsBuilder.from(factory => ({ ... }))` for typed options
+- Loads dynamically via `next/dynamic`
+- Fetches data via tRPC client hooks (backed by cron job caches)
+
+### Integration System
+
+Integrations are defined in `packages/definitions/src/integration.ts` (`integrationDefs`) and instantiated via `createIntegrationAsync` in `packages/integrations/src/base/creator.ts`. Each extends abstract `Integration` class with `testConnectionAsync` and typed methods.
+
+### Cron Job System
+
+Jobs defined in `packages/cron-jobs/src/jobs/`. Each job:
+
+- Uses `createCronJob` with a cron expression
+- Publishes results to Redis channels
+- Widget subscriptions consume those channels via tRPC subscriptions
+- Job management (start/stop/trigger) via `cronJobApi` HTTP client to port 3002
+
+### Modals
+
+Created with `createModal(component).withOptions({ defaultTitle })` from `@homarr/modals`. Opened via `useModalAction(SomeModal)`. Feature modals live in `packages/modals-collection/`.
+
+### Forms
+
+`useZodForm` from `@homarr/form` wraps Mantine `useForm` with zod validation. Shared form UIs in `packages/forms-collection/`.
+
+### Routing (App Router)
+
+- `apps/nextjs/src/app/[locale]/` — all UI routes under locale segment
+- Route groups: `(home)`, `(content)`, `(board)` — don't affect URLs
+- Key routes: `boards/[name]`, `manage/...` (admin), `auth/login`, `init` (onboarding), `widgets/[kind]`
+- Locale driven by cookie (no URL prefix)
+
+### Auth Providers
+
+Configured via `AUTH_PROVIDERS` env. Supports: `credentials` (local), `ldap`, `oidc`. Database sessions with httpOnly cookies. API key auth for programmatic access.
+
+## Environment Variables
+
+Key env vars (from `.env.example`):
+
+- `DB_DRIVER`: `better-sqlite3` | `mysql2` | `node-postgres`
+- `DB_URL`: Database connection string
+- `AUTH_SECRET`: NextAuth secret
+- `SECRET_ENCRYPTION_KEY`: AES-256-CBC for integration secrets
+- `AUTH_PROVIDERS`: Comma-separated (`credentials`, `ldap`, `oidc`)
+- `CRON_JOB_API_KEY`: Shared key between Next.js and tasks service
+- `REDIS_*`: Redis connection (host, port, password)
+- `ENABLE_KUBERNETES`: Optional Kubernetes integration
+
+## Development Commands
+
+- `pnpm dev` — runs all three services in parallel via Turborepo
+- `pnpm docker:dev` — starts Redis + MySQL + PostgreSQL containers
+- `pnpm db:push` — push schema to SQLite (dev)
+- `pnpm db:studio` — Drizzle Studio
+- `pnpm test` — Vitest unit tests
+- `pnpm test:e2e` — Playwright E2E
+- `pnpm lint` / `pnpm format` — oxlint + oxfmt
+- `pnpm dev:docs` — Docusaurus docs site (port 3003)
+- `pnpm typecheck` — tsc --noEmit across all packages
+
+## Conventions
+
+- Workspace packages use `@homarr/` scope
+- All versions managed via pnpm `catalog:` in workspace
+- Path alias `~/*` → `./src/*` in Next.js app
+- Mantine for all UI (no Tailwind) — primary color is red, `autoContrast: true`
+- Icons from `@tabler/icons-react`
+- Drag-and-drop via `@dnd-kit/*`
+- `typescript.ignoreBuildErrors: true` in next.config (types checked separately via `typecheck`)
+- `serverExternalPackages`: `dockerode`, `isomorphic-dompurify`, `jsdom`

.agents/skills/codebase-context/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Homarr Codebase Context"
-  short_description: "Navigate Homarr architecture and shared APIs"
-  default_prompt: "Use $codebase-context to locate the right Homarr package and reuse existing shared APIs."

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

@@ -1,110 +0,0 @@
-# Homarr architecture
-
-## Contents
-
-- [Applications and runtimes](#applications-and-runtimes)
-- [Package map](#package-map)
-- [Dependency direction](#dependency-direction)
-- [Core patterns](#core-patterns)
-- [Commands and conventions](#commands-and-conventions)
-
-## Applications and runtimes
-
-| Path             | Role                                                                                     |
-| ---------------- | ---------------------------------------------------------------------------------------- |
-| `apps/nextjs`    | Main Next.js application and HTTP APIs on port 3000                                      |
-| `apps/docs`      | Docusaurus 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.
-
-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.
-
-## Package map
-
-### Foundation and domain
-
-- `core`: environment validation, database and Redis factories, logging, infrastructure.
-- `definitions`: domain enums, integration definitions, widget kinds, permissions.
-- `common`: shared utilities with environment-specific entrypoints. Search it before adding helpers.
-- `validation`: shared Zod schemas.
-- `server-settings`: typed server-setting keys and access.
-
-### Data, identity, and transport
-
-- `db`: Drizzle schemas, queries, migrations, and three database 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.
-- `cron-jobs-core`, `cron-jobs`, `cron-job-status`: scheduling primitives, job implementations, and status transport.
-
-### Backends and external systems
-
-- `integrations`: typed clients for external applications.
-- `request-handler`: shared server request flows.
-- `docker`, `ping`, `image-proxy`, `icons`, `analytics`: bounded infrastructure capabilities.
-- `custom-widgets`: Custom JSX v2 schema, validation, runtime, and security contracts.
-- `workshop`: TypeScript Workshop client, backend contracts, and schemas used by Homarr.
-
-### UI and composed features
-
-- `ui`: shared Mantine components, theme, and hooks. Search here before creating a primitive.
-- `form`, `forms-collection`: Zod-backed form setup and reusable forms.
-- `modals`, `modals-collection`: modal primitives and feature modals.
-- `boards`: board state, edit mode, and cache coordination.
-- `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.
-
-## Dependency direction
-
-Prefer these directions; verify the exact dependency in package manifests before changing a boundary.
-
-1. Put infrastructure in `core` and stable domain names in `definitions`.
-2. Put reusable, dependency-light helpers in `common`; use its public environment-specific entrypoints.
-3. Build persistence in `db`, identity in `auth`, transport in `redis`, and external clients in `integrations`.
-4. Compose server behavior in `api`, `cron-jobs`, and request-handler packages.
-5. Build primitives in `ui`, `form`, and `modals`; compose product surfaces in widgets and collection packages.
-6. Keep app entrypoints in `apps/*` thin. Avoid moving reusable behavior into `apps/nextjs` when a package already owns it.
-
-## Core patterns
-
-### tRPC and MCP
-
-`packages/api/src/root.ts` lazily composes the application router. Server components use `@homarr/api/server`; client components use `@homarr/api/client`. MCP extraction requires the eager router in `packages/api/src/mcp.ts`, so MCP-enabled subrouters must be imported and registered there directly. Use the `mcp-integration` skill for exposure and security rules.
-
-### 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.
-
-### Widgets
-
-`packages/widgets/src/registry.ts` owns the explicit widget-module and component-loader registries. `packages/widgets/src/manifest.ts` caches those loaders and exposes definitions, components, and combined resources. Widget modules use `createWidgetDefinition` and typed option builders. Data commonly comes from tRPC queries or Redis-backed cron results. Use existing shared widget components before creating local variants.
-
-### Integrations
-
-`packages/definitions/src/integration.ts` owns `integrationDefs` and `IntegrationKind`. `packages/integrations/src/base/creator.ts` owns `createIntegrationAsync`; concrete integrations implement the shared base contract. Keep credentials and permission checks on server-owned paths.
-
-### Cron jobs
-
-Jobs live in `packages/cron-jobs/src/jobs/` and use `createCronJob`. `apps/tasks` initializes and starts the job group. Job results and status can flow through Redis and tRPC; the retired port-3002 management-API model is no longer part of the architecture.
-
-### Routing and localization
-
-User routes live below `apps/nextjs/src/app/[locale]/`; the locale segment does not add a URL prefix. Route groups organize home and board surfaces. Administrative routes live under `manage`, Custom Widget configuration has a token route, and Workshop has a management surface.
-
-### Custom Widgets and Workshop
-
-`packages/custom-widgets` owns the Custom JSX v2 contract. `packages/workshop` is the Homarr-side client/contract package; `apps/workshop` is the separate Go/PocketBase service. Use the `homarr-custom-widget` skill for authoring and security constraints.
-
-## 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 `~/*` 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/codebase-context/references/common.md

@@ -1,86 +0,0 @@
-# `@homarr/common` public API
-
-## Contents
-
-- [Reuse workflow](#reuse-workflow)
-- [Entrypoints](#entrypoints)
-- [Root exports](#root-exports)
-- [Types exports](#types-exports)
-- [Server exports](#server-exports)
-- [Client and environment exports](#client-and-environment-exports)
-
-## Reuse workflow
-
-Before writing a utility, search both the public name and the behavior:
-
-```bash
-rg -n "export (const|function|class|type|interface)|export \*" packages/common
-rg -n "@homarr/common" apps packages
-```
-
-Import only from an exported package entrypoint. Do not deep-import `@homarr/common/src/*`. Check `packages/common/package.json` and the source again when adding or renaming an export; this inventory describes the current repository tree.
-
-## Entrypoints
-
-| Import                  | Source                       | Environment                                                                         |
-| ----------------------- | ---------------------------- | ----------------------------------------------------------------------------------- |
-| `@homarr/common`        | `index.ts` -> `src/index.ts` | Shared root; includes React hooks and some Next/Mantine-aware helpers               |
-| `@homarr/common/types`  | `src/types.ts`               | Type-only utilities                                                                 |
-| `@homarr/common/server` | `src/server.ts`              | Node/server-only security, encryption, request, error, and bounded-response helpers |
-| `@homarr/common/client` | `src/client.ts`              | Client-facing Next server action export                                             |
-| `@homarr/common/env`    | `env.ts`                     | Validated package environment                                                       |
-
-## Root exports
-
-| Area              | Public exports                                                                                                                                       | Purpose                                                         |
-| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
-| Objects           | `objectKeys`, `objectEntries`, `hashObjectBase64`                                                                                                    | Typed key/entry iteration and stable query-key hashing          |
-| Strings           | `capitalize`, `isNullOrWhitespace`, `bestMatch`, `normalizeImageName`, `getImageMatchRank`                                                           | Text normalization and matching                                 |
-| Cookies           | `parseCookies`, `setClientCookie`                                                                                                                    | Cookie parsing and browser cookie serialization                 |
-| Arrays            | `splitToNChunks`, `splitToChunksWithNItems`                                                                                                          | Split by number of groups or maximum group size                 |
-| Dates             | `formatDuration`, `toValidDate`, `isDateWithin`                                                                                                      | Duration formatting, safe date coercion, relative-window checks |
-| Timing            | `Stopwatch`                                                                                                                                          | Elapsed-time measurement and formatting                         |
-| React hooks       | `useTimeAgo`, `useIntegrationConnected`                                                                                                              | Relative time and integration freshness state                   |
-| URLs              | `removeTrailingSlash`, `extractBaseUrlFromHeaders`, `getPortFromUrl`, `isAbsoluteUrl`, `SAFE_NEW_TAB_REL`, `getSafeApplicationUrl`, `getSafeAppHref` | URL normalization, safe navigation, ports, and new-tab policy   |
-| Numbers and bytes | `formatNumber`, `randomInt`, `formatBytes`, `formatBytesPair`, `formatByteRate`, `metricToImperial`, `imperialToMetric`                              | Compact numbers, byte displays, rates, and unit conversion      |
-| Legacy bytes      | `humanFileSize`                                                                                                                                      | Deprecated; use the `formatBytes*` helpers in new code          |
-| Byte types        | `ByteUnitSystem`, `FormatBytesOptions`                                                                                                               | Options for byte formatting                                     |
-| Errors            | `extractErrorMessage`, `FlattenError`                                                                                                                | Unknown-error messages and flattenable domain errors            |
-| Theme             | `getMantineColor`                                                                                                                                    | Resolve a Mantine color and shade                               |
-| Functions         | `isFunction`                                                                                                                                         | Unknown-value function guard                                    |
-| Grid              | `GridAlgorithmItem`, `generateResponsiveGridFor`                                                                                                     | Responsive nested-section grid placement                        |
-| IDs               | `createId`                                                                                                                                           | CUID2 ID creation                                               |
-
-The root deliberately does not re-export `types`, `server`, `client`, or `env`; use their named entrypoints.
-
-## Types exports
-
-`@homarr/common/types` exports:
-
-- `MaybePromise<T>`
-- `AtLeastOneOf<T>`
-- `Modify<T, R>`
-- `RemoveReadonly<T>`
-- `MaybeArray<T>`
-- `Inverse<T>`
-- `inferSearchParamsFromSchema<TSchema>`
-
-## Server exports
-
-`@homarr/common/server` exports:
-
-- Security: `generateSecureRandomToken`.
-- Encryption: `encryptSecret`, `decryptSecret`, `decryptSecretWithKey`, `createKeyedFingerprint`, `verifyKeyedFingerprint`.
-- Requests: `userAgent`, `DeviceType`, `ipAddressFromHeaders`.
-- Bounded bodies: `readBoundedJsonResponseAsync`.
-- Parse errors: `ParseError`, `ParseErrorHandler`, `ZodParseErrorHandler`, `JsonParseErrorHandler`.
-- HTTP handlers: `HttpErrorHandler`, `FetchHttpErrorHandler`, `matchErrorCode`, `OFetchHttpErrorHandler`, `AxiosHttpErrorHandler`, `TsdavHttpErrorHandler`, `OctokitHttpErrorHandler`.
-- HTTP errors: `RequestError`, `ResponseError`, `requestErrorMap`.
-- HTTP error types: `AnyRequestError`, `AnyRequestErrorInput`, `RequestErrorInput`, `RequestErrorType`, `RequestErrorReason`, `AnyRequestErrorReason`, `RequestErrorCode`.
-
-`NodeFetchHttpErrorHandler` exists as an implementation file but is not exported by the public server entrypoint. Add an intentional public export before using it across packages.
-
-## Client and environment exports
-
-- `@homarr/common/client` exports `revalidatePathActionAsync`, a Next server action for page revalidation.
-- `@homarr/common/env` exports `env` with validated `NODE_ENV`, `SECRET_ENCRYPTION_KEY`, and `NO_EXTERNAL_CONNECTION` values.

.agents/skills/datatable-migration/SKILL.md

@@ -0,0 +1,650 @@
+---
+name: datatable-migration
+description: Playbook for migrating tables from mantine-react-table (MRT) to mantine-datatable. Use when converting any table component from mantine-react-table to mantine-datatable, working on DataTable column/sort/expansion/context-menu code, or implementing responsive column visibility, column persistence, or transparent tables in widgets.
+---
+
+# Migrating Tables from mantine-react-table to mantine-datatable
+
+This document captures every pattern, fix, and decision from the downloads widget rework (PR #6430). Use it as a playbook when porting other tables.
+
+## Migration Candidates
+
+Current `mantine-react-table` consumers that could be migrated:
+
+**Widgets (in `packages/widgets/`):**
+
+- `docker/component.tsx` — Docker container table
+- `media-server/component.tsx` — Media server sessions
+
+**Admin pages (in `apps/nextjs/src/app/[locale]/manage/`):**
+
+- `tools/docker/docker-table.tsx`
+- `tools/tasks/_components/tasks-table.tsx`
+- `tools/api/components/api-keys.tsx`
+- `users/_components/user-list.tsx`
+- `users/invites/_components/invite-list.tsx`
+- `tools/kubernetes/` — 8 Kubernetes resource tables
+
+**Modals:**
+
+- `packages/modals-collection/src/search-engines/request-media-modal.tsx`
+
+**Shared hook to remove once all migrated:**
+
+- `packages/ui/src/hooks/use-translated-mantine-react-table.ts`
+
+## 1. Core Migration: mantine-react-table → mantine-datatable
+
+### Import changes
+
+```typescript
+// BEFORE
+import { MantineReactTable, useMantineReactTable } from "mantine-react-table";
+import type { MRT_ColumnDef } from "mantine-react-table";
+
+// AFTER
+import { DataTable, useDataTableColumns } from "mantine-datatable";
+import type { DataTableColumn, DataTableSortStatus } from "mantine-datatable";
+```
+
+### Column definition shape
+
+```typescript
+// BEFORE (MRT)
+const columns: MRT_ColumnDef<MyRow>[] = [
+  {
+    accessorKey: "name",
+    header: "Name",
+    size: 200,
+    enableSorting: true,
+    Cell: ({ row }) => <Text>{row.original.name}</Text>,
+  },
+];
+
+// AFTER (mantine-datatable)
+const columns: DataTableColumn<MyRow>[] = [
+  {
+    accessor: "name",           // not accessorKey
+    title: "Name",              // not header
+    width: 200,                 // not size
+    sortable: true,             // not enableSorting
+    render: (record) => <Text>{record.name}</Text>,  // not Cell
+  },
+];
+```
+
+Key differences:
+
+- `accessorKey` → `accessor`
+- `header` → `title`
+- `size` → `width`
+- `Cell: ({ row }) =>` → `render: (record) =>`
+- `enableSorting` → `sortable`
+- `enableColumnActions` → does not exist (no column action menus)
+- `mantineTableBodyCellProps` → `cellsStyle` in `defaultColumnProps`
+
+### Table component
+
+```typescript
+// BEFORE
+const table = useTranslatedMantineReactTable({ columns, data, ... });
+return <MantineReactTable table={table} />;
+
+// AFTER
+return (
+  <DataTable
+    records={data}
+    columns={columns}
+    sortStatus={sortStatus}
+    onSortStatusChange={setSortStatus}
+    ...
+  />
+);
+```
+
+### Sorting is manual
+
+mantine-datatable does NOT sort for you. You must sort the data yourself:
+
+```typescript
+const [sortStatus, setSortStatus] = useState<DataTableSortStatus<MyRow>>({
+  columnAccessor: "name",
+  direction: "asc",
+});
+
+const sortedData = useMemo(() => {
+  const mult = sortStatus.direction === "desc" ? -1 : 1;
+  return [...data].toSorted((a, b) => {
+    const aVal = a[sortStatus.columnAccessor];
+    const bVal = b[sortStatus.columnAccessor];
+    if (typeof aVal === "string") return aVal.localeCompare(bVal as string) * mult;
+    return ((aVal as number) - (bVal as number)) * mult;
+  });
+}, [data, sortStatus]);
+
+// Pass sortedData to records, not data
+<DataTable records={sortedData} sortStatus={sortStatus} onSortStatusChange={setSortStatus} />
+```
+
+## 2. Making Tables Transparent (Widget Context)
+
+Widgets sit inside board cards that have user-controlled opacity. The table must be fully transparent so the card background shows through. mantine-datatable defaults to `var(--mantine-color-body)` which is opaque.
+
+Create a CSS file alongside the component:
+
+```css
+/* styles.css */
+.my-table,
+.my-table .mantine-datatable-table,
+.my-table .mantine-datatable-table thead,
+.my-table .mantine-datatable-table tbody,
+.my-table .mantine-datatable-table tfoot,
+.my-table th,
+.my-table td {
+  background-color: transparent !important;
+}
+
+.my-table .mantine-datatable-table tr {
+  background-color: transparent;
+}
+
+/* Hover: translucent instead of opaque */
+.my-table .mantine-datatable-table tbody tr:hover {
+  background-color: color-mix(in srgb, var(--mantine-color-default-hover) 40%, transparent) !important;
+}
+
+/* Headers: frosted glass effect */
+.my-table th {
+  white-space: nowrap;
+  background-color: color-mix(in srgb, var(--mantine-color-body) 60%, transparent) !important;
+  backdrop-filter: blur(8px);
+}
+
+/* Cell overflow */
+.my-table td {
+  white-space: nowrap;
+  overflow: hidden;
+  text-overflow: ellipsis;
+}
+
+/* Hide sort icon until hover */
+.my-table .mantine-datatable-header-cell-sortable-icon {
+  opacity: 0;
+  transition: opacity 150ms;
+}
+.my-table th:hover .mantine-datatable-header-cell-sortable-icon {
+  opacity: 1;
+}
+
+/* Row expansion area */
+.my-table .mantine-datatable-row-expansion-cell {
+  background-color: color-mix(in srgb, var(--mantine-color-body) 40%, transparent) !important;
+}
+```
+
+Import it: `import "./styles.css";` and apply via `className="my-table"`.
+
+## 3. Responsive Column Visibility
+
+Use a lookup table of width breakpoints instead of media queries. The widget receives `width` as a prop.
+
+```typescript
+interface SizeConfig {
+  fontSize: "xs" | "sm";
+  iconSize: number;
+  cellPadding: number;
+  showSpeedColumns: boolean;
+  showTimeColumn: boolean;
+  showStateColumn: boolean;
+}
+
+const SIZE_BREAKPOINTS: { maxWidth: number; config: SizeConfig }[] = [
+  {
+    maxWidth: 300,
+    config: {
+      fontSize: "xs",
+      iconSize: 12,
+      cellPadding: 2,
+      showSpeedColumns: false,
+      showTimeColumn: false,
+      showStateColumn: false,
+    },
+  },
+  {
+    maxWidth: 500,
+    config: {
+      fontSize: "xs",
+      iconSize: 14,
+      cellPadding: 4,
+      showSpeedColumns: false,
+      showTimeColumn: true,
+      showStateColumn: false,
+    },
+  },
+];
+
+const DEFAULT_SIZE_CONFIG: SizeConfig = {
+  fontSize: "sm",
+  iconSize: 14,
+  cellPadding: 4,
+  showSpeedColumns: true,
+  showTimeColumn: true,
+  showStateColumn: true,
+};
+
+function getSizeConfig(width: number): SizeConfig {
+  for (const { maxWidth, config } of SIZE_BREAKPOINTS) {
+    if (width < maxWidth) return config;
+  }
+  return DEFAULT_SIZE_CONFIG;
+}
+
+// Usage: memoize it
+const size = useMemo(() => getSizeConfig(width), [width]);
+```
+
+Then use a visibility check lookup table for columns:
+
+```typescript
+const columnVisibilityChecks: Partial<Record<string, (ctx: ColumnContext) => boolean>> = {
+  upSpeed: (ctx) => ctx.hasTorrents && ctx.size.showSpeedColumns,
+  downSpeed: (ctx) => ctx.size.showSpeedColumns,
+  time: (ctx) => ctx.size.showTimeColumn,
+  state: (ctx) => ctx.size.showStateColumn,
+};
+
+function shouldIncludeColumn(accessor: string, ctx: ColumnContext): boolean {
+  if (!ctx.optionsColumnSet.has(accessor)) return false;
+  const check = columnVisibilityChecks[accessor];
+  if (check && !check(ctx)) return false;
+  return true;
+}
+```
+
+## 4. Column Persistence (Drag/Resize → Server)
+
+`useDataTableColumns` stores column order and widths in localStorage by default. For widgets, this must persist server-side so it works across devices.
+
+### Hidden widget options
+
+In `index.ts`, add hidden text options:
+
+```typescript
+columnOrder: factory.text({ defaultValue: "" }),
+columnWidths: factory.text({ defaultValue: "" }),
+```
+
+With visibility override:
+
+```typescript
+{
+  columnOrder: { shouldHide: () => true },
+  columnWidths: { shouldHide: () => true },
+}
+```
+
+### Translation keys required
+
+Even hidden options need translation keys or the translation test fails:
+
+```json
+"widget.mywidget.option.columnOrder.label": "Column order",
+"widget.mywidget.option.columnWidths.label": "Column widths"
+```
+
+### Dynamic storeKey
+
+Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
+
+```typescript
+const storeKey = `mytable-${itemId ?? "preview"}-${[...options.columns].toSorted().join(",")}`;
+```
+
+### Hydration from server → localStorage
+
+On mount, seed `useDataTableColumns` with server-persisted values. Use a `hydrated` ref to prevent the persist effect from immediately writing defaults back:
+
+```typescript
+const { effectiveColumns, columnsOrder, columnsWidth, setColumnsOrder, setMultipleColumnWidths } =
+  useDataTableColumns<MyRow>({ key: storeKey, columns });
+
+const lastStoreKey = useRef(storeKey);
+const hydrated = useRef(false);
+
+useEffect(() => {
+  if (lastStoreKey.current !== storeKey) {
+    lastStoreKey.current = storeKey;
+    hydrated.current = false;
+  }
+  if (hydrated.current) return;
+  if (savedOrder.length > 0) setColumnsOrder(savedOrder);
+  if (Object.keys(savedWidths).length > 0) {
+    setMultipleColumnWidths(
+      Object.entries(savedWidths).map(([accessor, w]) => ({
+        accessor,
+        width: w,
+      })),
+    );
+  }
+  requestAnimationFrame(() => {
+    hydrated.current = true;
+  });
+}, [storeKey, savedOrder, savedWidths, setColumnsOrder, setMultipleColumnWidths]);
+```
+
+### Persist localStorage → server
+
+Watch for changes and write back:
+
+```typescript
+const prevOrder = useRef(columnsOrder);
+const prevWidths = useRef(columnsWidth);
+
+useEffect(() => {
+  if (!hydrated.current) return;
+  const orderChanged = JSON.stringify(columnsOrder) !== JSON.stringify(prevOrder.current);
+  const widthsChanged = JSON.stringify(columnsWidth) !== JSON.stringify(prevWidths.current);
+  prevOrder.current = columnsOrder;
+  prevWidths.current = columnsWidth;
+
+  if (!orderChanged && !widthsChanged) return;
+
+  if (orderChanged) persistOption({ columnOrder: JSON.stringify(columnsOrder) });
+  if (widthsChanged) {
+    const widthMap: Record<string, number> = {};
+    for (const entry of columnsWidth) {
+      const key = Object.keys(entry)[0];
+      if (!key) continue;
+      const v = entry[key as keyof typeof entry];
+      if (typeof v === "number") widthMap[key] = v;
+      else if (typeof v === "string" && v.endsWith("px")) widthMap[key] = parseInt(v, 10);
+    }
+    persistOption({ columnWidths: JSON.stringify(widthMap) });
+  }
+}, [columnsOrder, columnsWidth, persistOption]);
+```
+
+The `persistOption` helper calls both `setOptions` (local state) and `saveItemOptions` (server mutation).
+
+## 5. Context Menu (Right-Click)
+
+Do NOT install `mantine-contextmenu`. Use Mantine's `Menu` + `Portal` directly:
+
+```typescript
+interface ContextMenuState {
+  x: number;
+  y: number;
+  item: MyRow;
+}
+
+const [contextMenu, setContextMenu] = useState<ContextMenuState | null>(null);
+
+const handleContextMenu = useCallback(
+  ({ record, event }: { record: MyRow; event: React.MouseEvent }) => {
+    event.preventDefault();
+    setContextMenu({ x: event.clientX, y: event.clientY, item: record });
+  },
+  [],
+);
+
+// On DataTable:
+<DataTable onRowContextMenu={handleContextMenu} />
+
+// Render:
+{contextMenu && <RowContextMenu state={contextMenu} onClose={closeContextMenu} />}
+```
+
+The menu component uses `Portal` for correct z-index:
+
+```tsx
+function RowContextMenu({ state, onClose }: { state: ContextMenuState; onClose: () => void }) {
+  return (
+    <Portal>
+      <Menu opened onClose={onClose} closeOnItemClick={false} position="right-start" offset={0}>
+        <Menu.Target>
+          <Box
+            style={{
+              position: "fixed",
+              left: state.x,
+              top: state.y,
+              width: 0,
+              height: 0,
+            }}
+          />
+        </Menu.Target>
+        <Menu.Dropdown>
+          <Menu.Item
+            onClick={() => {
+              /* action */ onClose();
+            }}
+          >
+            Action
+          </Menu.Item>
+        </Menu.Dropdown>
+      </Menu>
+    </Portal>
+  );
+}
+```
+
+**Key fix:** Use `closeOnItemClick={false}` if any menu item needs a two-step confirmation (like delete → confirm). Close the menu on scroll: `onScroll={() => { if (contextMenu) closeContextMenu(); }}`.
+
+## 6. Row Expansion
+
+```typescript
+<DataTable
+  rowExpansion={{
+    trigger: "click",
+    allowMultiple: true,
+    collapseProps: {
+      transitionDuration: 200,
+      animateOpacity: true,
+      transitionTimingFunction: "ease-out",
+    },
+    content: ({ record, collapse }) => <ExpandedRow item={record} collapse={collapse} />,
+  }}
+/>
+```
+
+**Critical:** Do NOT set `onRowClick` when using `rowExpansion` with `trigger: "click"`. They conflict and the expansion won't work.
+
+## 7. Common Pitfalls & Fixes
+
+### Status indicator dots
+
+Don't use `<Badge variant="dot" />` without children — it renders a pill with empty space. Use a plain `Box`:
+
+```tsx
+<Box
+  w={8}
+  h={8}
+  style={{
+    borderRadius: "50%",
+    backgroundColor: `var(--mantine-color-${color}-filled)`,
+    flexShrink: 0,
+  }}
+/>
+```
+
+### Tooltip overflow on long text columns
+
+When a column has `ellipsis: true`, the tooltip target element can still extend beyond the cell bounds if inner elements don't clip. Fix:
+
+```tsx
+<Tooltip position="bottom-start" ...>
+  <Group style={{ overflow: "hidden" }}>
+    ...
+  </Group>
+</Tooltip>
+```
+
+Use `position="bottom-start"` instead of `position="right"` so the tooltip never escapes the widget horizontally.
+
+### Dark mode tooltips
+
+Mantine tooltips default to the theme's tooltip color which may be white in light mode and stay white in dark mode. Always set `color="dark"` on informational tooltips inside widgets.
+
+### Division by zero
+
+Guard all ratio calculations:
+
+```typescript
+if (item.size > 0) ratio = item.sent / item.size;
+if (totalDown > 0) ratio = totalUp / totalDown;
+```
+
+### Composite idAccessor
+
+When rows can come from multiple integrations, IDs may collide. Use a composite key:
+
+```typescript
+idAccessor={(record) => `${record.integration.id}:${record.id}`}
+```
+
+### JSON option parsing
+
+Always wrap in try/catch:
+
+```typescript
+function parseJsonOption<T>(value: string | undefined, fallback: T): T {
+  if (!value) return fallback;
+  try {
+    return JSON.parse(value) as T;
+  } catch {
+    return fallback;
+  }
+}
+```
+
+### Clipboard API
+
+`navigator.clipboard.writeText()` can throw in non-HTTPS contexts. Always catch:
+
+```typescript
+void navigator.clipboard.writeText(text).catch(() => {});
+```
+
+### Sync sortStatus with widget options
+
+If the widget has configurable default sort, sync it:
+
+```typescript
+useEffect(() => {
+  setSortStatus({
+    columnAccessor: options.defaultSort,
+    direction: defaultSortDirection,
+  });
+}, [options.defaultSort, defaultSortDirection]);
+```
+
+## 8. Accessibility
+
+- All `ActionIcon` components need `aria-label`
+- Filter toggles (client badges, status badges) need `aria-pressed={isActive}`
+- `textSelectionDisabled` on DataTable prevents accidental text selection during drag/resize
+
+## 9. Error Handling
+
+- Every mutation needs an `onError` callback with `showErrorNotification`
+- The `saveItemOptions` mutation (column persistence) also needs `onError`
+- Check `isError` on the main query and show a fallback UI
+- Use a shared `mutationOptions` object to avoid repeating `onSettled`/`onError`:
+
+```typescript
+const mutationOptions = {
+  onSettled: () => void utils.myQuery.invalidate(),
+  onError: () =>
+    showErrorNotification({
+      title: t("errors.actionFailed"),
+      message: t("errors.actionFailedMessage"),
+    }),
+};
+```
+
+## 10. i18n
+
+- No hardcoded strings. Every user-visible string goes through `useScopedI18n`
+- Column titles: `t("items.{accessor}.columnTitle")`
+- Detail labels: `t("items.{accessor}.detailsTitle")`
+- States: `t("states.{state}")`
+- Actions: `t("actions.{action}")`
+- Errors: `t("errors.{errorKey}")`
+- Hidden options still need `.label` translation keys
+
+## 11. Edit Mode
+
+Disable pointer events on the table during edit mode to prevent conflicts with the board's drag-and-drop:
+
+```typescript
+let tablePointerEvents: React.CSSProperties["pointerEvents"];
+if (isEditMode) tablePointerEvents = "none";
+
+let rowContextMenuHandler = handleContextMenu;
+if (isEditMode) rowContextMenuHandler = undefined;
+
+<DataTable style={{ pointerEvents: tablePointerEvents }} />
+```
+
+## 12. DataTable Props Reference (Commonly Used)
+
+```typescript
+<DataTable
+  records={sortedData}
+  columns={effectiveColumns}
+  storeColumnsKey={storeKey}
+  withTableBorder={false}
+  borderRadius={0}
+  highlightOnHover
+  striped="odd"
+  stripedColor={{ dark: "dark.7", light: "gray.0" }}
+  highlightOnHoverColor={{ dark: "dark.5", light: "gray.1" }}
+  verticalAlign="center"
+  fetching={isFetching && data.length === 0}
+  loaderBackgroundBlur={2}
+  fz={size.fontSize}
+  textSelectionDisabled
+  sortStatus={sortStatus}
+  onSortStatusChange={setSortStatus}
+  noRecordsText={t("errors.noItems")}
+  idAccessor={(record) => record.uniqueKey}
+  height="100%"
+  className="my-table"
+  defaultColumnProps={{
+    noWrap: true,
+    draggable: true,
+    resizable: true,
+    cellsStyle: () => ({ padding: `${size.cellPadding}px 8px` }),
+  }}
+  scrollAreaProps={{ type: "auto", scrollbarSize: 6 }}
+  rowBackgroundColor={(record) => conditionalBgMap[record.state]}
+  onRowContextMenu={handleContextMenu}
+  rowExpansion={{ ... }}
+  onScroll={() => { if (contextMenu) closeContextMenu(); }}
+/>
+```
+
+## 13. Layout Stability
+
+- Don't use `table-layout: fixed` — it fights mantine-datatable's resize logic
+- Give non-name columns explicit `width` values so only the name column flexes
+- Use `ellipsis: true` on the name column — it handles `text-overflow: ellipsis` internally
+- Names should truncate at the cell boundary, not a character count, so the layout is stable regardless of content length
+- `flexShrink: 0` on badges/icons prevents them from being squeezed by long names
+
+## 14. Checklist for Each Migration
+
+1. Replace imports (`mantine-react-table` → `mantine-datatable`)
+2. Convert column definitions (`accessorKey` → `accessor`, `header` → `title`, `Cell` → `render`, etc.)
+3. Implement manual sorting with `useState` + `useMemo`
+4. Add CSS file for transparent backgrounds (if widget context)
+5. Add responsive column visibility (if widget context)
+6. Add hidden options + hydration logic (if column persistence needed)
+7. Add translation keys (including hidden option labels)
+8. Add context menu if row actions exist
+9. Add row expansion if detail view exists
+10. Add error handling on all mutations
+11. Add accessibility attributes
+12. Test at multiple widget widths
+13. Update docs in `apps/docs/docs/widgets/` if applicable
+14. Run `pnpm turbo typecheck`
+15. Run translation spec — catches missing keys

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

@@ -1,51 +1,44 @@
 ---
 name: documentation-sync
-description: Keep Homarr's Docusaurus documentation aligned with user-facing code. Use when adding or changing integrations, widgets, APIs, environment variables, CLI commands, authentication, permissions, cron jobs, settings, or UI behavior that users must understand.
+description: Keep Homarr documentation in sync with code changes. Use when modifying code that affects user-facing behavior, or when adding/modifying widgets, integrations, cron jobs, API routes, env vars, permissions, auth providers, or UI in apps/docs. Covers the docs/ mapping table, integration doc pattern, and widget doc pattern.
 ---
 
 # Documentation Sync
 
-Update `apps/docs/` in the same change as user-facing behavior. Inspect adjacent pages and the docs types before copying a pattern; the source and docs evolve together.
+When modifying code that affects user-facing behavior, you MUST also update the documentation in `apps/docs/`.
 
-## Map the change
+## What triggers a doc update
 
-| Code change                         | Documentation target                                                 |
-| ----------------------------------- | -------------------------------------------------------------------- |
-| New integration                     | `apps/docs/docs/integrations/<slug>/index.mdx` and `index.ts`        |
-| New widget                          | `apps/docs/docs/widgets/<slug>/index.mdx` and `index.ts`             |
-| Changed public or management API    | `apps/docs/docs/management/api/index.mdx`                            |
-| New or changed environment variable | Relevant page under `apps/docs/docs/advanced/` or installation docs  |
-| New or changed CLI command          | `apps/docs/docs/advanced/command-line/`                              |
-| Authentication/provider change      | Relevant SSO or authentication page under `apps/docs/docs/advanced/` |
-| UI or workflow change               | Relevant getting-started, management, widget, or integration page    |
-| Cron-job behavior                   | `apps/docs/docs/management/tasks.mdx`                                |
-| Permission behavior                 | `apps/docs/docs/management/users.mdx` and the affected feature page  |
-| Custom Widget or Workshop behavior  | Relevant Custom Widget, Assistant, or Workshop documentation         |
+| Code change            | Doc location                                                |
+| ---------------------- | ----------------------------------------------------------- |
+| New integration        | `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts` |
+| New widget             | `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`      |
+| Changed API surface    | `apps/docs/docs/management/api.mdx`                         |
+| New/changed env vars   | `apps/docs/docs/advanced/`                                  |
+| New CLI commands       | `apps/docs/docs/advanced/command-line/`                     |
+| Changed auth providers | `apps/docs/docs/advanced/` SSO pages                        |
+| UI/UX changes          | Relevant getting-started or management pages                |
+| New cron job           | `apps/docs/docs/management/tasks.mdx`                       |
+| Changed permissions    | `apps/docs/docs/management/users.mdx`                       |
 
-If no existing row fits, search by the user-visible term and update the page where a user would look for the behavior:
+## Integration doc pattern
 
-```bash
-rg -n "<term>" apps/docs/docs apps/docs/src
-```
+Each integration has a folder under `apps/docs/docs/integrations/<slug>/`:
 
-## Follow existing typed patterns
+- `index.ts` — exports a typed `IntegrationDefinition` with name, description, iconUrl, path
+- `index.mdx` — uses shared components: `IntegrationHeader`, `IntegrationCapabilites`, `IntegrationSecrets`
+- Import metadata from `@homarr/definitions` where possible
 
-For an integration:
+## Widget doc pattern
 
-- Add or update `apps/docs/docs/integrations/<slug>/index.ts` with the local `IntegrationDefinition` pattern.
-- Add or update `index.mdx` with the established `IntegrationHeader`, `IntegrationCapabilites`, and `IntegrationSecrets` components as applicable.
-- Reuse metadata from `@homarr/definitions` when the docs app already exposes it.
+Each widget has a folder under `apps/docs/docs/widgets/<slug>/`:
 
-For a widget:
+- `index.ts` — exports a typed `WidgetDefinition` with icon, name, description, path, configuration
+- `index.mdx` — uses shared components: `WidgetHeader`, `WidgetConfig`, `WidgetAdding`
 
-- Add or update `apps/docs/docs/widgets/<slug>/index.ts` with the local `WidgetDefinition` pattern.
-- Add or update `index.mdx` with the established `WidgetHeader`, `WidgetConfig`, and `AddingWidget` components as applicable.
-- Document options, required integrations, permissions, empty states, and changed behavior that affect setup or use.
+## Development
 
-## Completion criteria
-
-1. Describe the shipped behavior, not an implementation plan.
-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.
+- Run docs locally: `pnpm dev:docs` from root
+- Build docs: `pnpm turbo build --filter=@homarr/docs`
+- The docs app can import from `@homarr/definitions` for type-safe integration/widget metadata
+- Docusaurus strict mode throws on broken links — fix any broken references before committing

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

@@ -1,4 +0,0 @@
-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."

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

@@ -1,43 +1,28 @@
 ---
 name: homarr-custom-widget
-description: Author, validate, preview, test, install, or configure API-backed Homarr Custom JSX v2 widgets.
+description: Author safe Homarr Custom JSX v2 widgets from API documentation.
 ---
 
 # 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 one widget at a time. When connected to Homarr, retrieve `homarr://custom-widgets/schema` and only the component resources needed for the design. The live resources are authoritative for the installed release.
 
-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.
+1. Read the API documentation.
+2. Create one credential-free widget with keyed `sources`, keyed `requests`, optional keyed `options`, and safe JSX `template`.
+3. Validate, preview, test queries and simulated actions, visually inspect, and iterate.
+4. Configure deployment-specific source URLs and request credentials through Homarr; never repeat plaintext.
+5. Save only after narrow/wide, light/dark, loading, empty, error, and success states work.
 
-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.
+Use `{option:name}` or `$option` for saved options. Use `{param:name}` or `$param` for values supplied by `SubFetch`, `ActionButton`, or `ToggleSwitch`. Load queries cannot use invocation parameters. Templates read `data`, `status`, `options`, and temporary `inputs`.
 
-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`.
+`SubFetch` with `trigger="manual"` renders its own load button. Pass a card or image through `triggerContent` with `triggerAriaLabel` when that content should launch the request. Its callback is `(result, meta)`; never author `onClick` or a fetch callback.
 
-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.
-
-`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.
-
-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.
-
-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.
+Use standard Mantine compound names and deliberate visual hierarchy, spacing, restrained semantic color, and responsive layouts. Avoid excessive nested cards.
 
 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.
+To install an existing widget, use `customWidget_workshopSearch`, inspect it with `customWidget_workshopGet`, then use `customWidget_workshopInstall`. Configure each self-hosted source afterward with `customWidget_sourceConfigure`, or call `customWidget_configurationRequestUser` so the user can enter the server URL and credentials directly in Homarr.
 
-Reference routing:
+Preview-scoped configuration expires with the preview. To persist user-entered values for a new widget, create the widget first, request configuration for its definition ID, then create a final preview with that definition ID so Homarr loads the stored credentials.
 
-- 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.
+When this skill is installed from the repository, optional offline details are in `references/schema.md`, `references/runtime.md`, and `references/security.md`. MCP-only clients should use the live Homarr resources instead.

.agents/skills/homarr-custom-widget/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Homarr Custom Widget"
-  short_description: "Build and deploy safe Custom JSX widgets"
-  default_prompt: "Use $homarr-custom-widget to author, validate, preview, and configure a safe Custom JSX v2 widget."

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

@@ -1,37 +1,16 @@
 # 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`.
+Templates read `data.requestId`, `status.requestId`, `options.name`, and temporary `inputs.name`. Status contains `loading`, `ok`, `status`, `statusText`, and `error`.
 
 `bind="search"` creates an in-memory input. It is never persisted. Supply invocation values only through `params`, for example:
 
 ```jsx
 <TextInput bind="search" label="Search" />
-<Pagination bind="page" resetKey={inputs.search} defaultValue={1} total={5} />
-<SubFetch requestId="search" trigger="manual" params={{ query: inputs.search }}>
-  {(result) => <Stack>{(result.results ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
+<SubFetch requestId="search" params={{ query: inputs.search }}>
+  {(items) => <Stack>{(items ?? []).map(item => <Text key={item.id}>{item.name}</Text>)}</Stack>}
 </SubFetch>
 ```
 
-Manual queries require `trigger: "manual"` on request and `SubFetch`; otherwise they run automatically. `triggerContent` with `triggerAriaLabel` makes custom content the launcher. `SubFetch` owns loading/error/retry; its child receives success plus `{ ok, status, statusText, loading: false }`. Never author `onClick` or fetch callbacks.
+`SubFetch` with `trigger="manual"` renders its own load button. To make a card or image launch the request, pass that node through `triggerContent` and provide `triggerAriaLabel`; Homarr supplies the click and keyboard behavior. Its optional second callback argument contains `{ ok, status, statusText, loading: false }`; loading and request failures are rendered by `SubFetch` before the callback runs. Do not author `onClick` or a fetch callback.
 
-`SubFetch`, `ActionButton`, and `ToggleSwitch` need literal `requestId`; validation rejects missing/computed IDs.
-
-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.
-
-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.
-
-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`.
-
-For compact numeric enums, index a literal label array with a fallback:
-
-```jsx
-<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.
-
-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 />`.
-
-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.
+Use expression callbacks for supported collection methods and trusted slots. Do not use callback blocks, IIFEs, authored recursion, or raw events. Bounded regex literals work only with safe string matching/replacement operations.

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

@@ -13,37 +13,10 @@ 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?`:
-
-```json
-{
-  "sources": {
-    "default": {
-      "name": "Service",
-      "baseUrl": "http://service.local:5055/api/v1",
-      "networkScope": "private",
-      "auth": { "type": "apiKeyHeader", "name": "X-Api-Key" }
-    }
-  },
-  "requests": {
-    "summary": { "path": "/summary" },
-    "search": { "trigger": "manual", "path": "/search", "query": { "q": { "$param": "query" } } },
-    "create": {
-      "kind": "action",
-      "method": "POST",
-      "path": "/items",
-      "body": { "id": { "$param": "id" } },
-      "confirmation": "Create this item?",
-      "invalidates": ["search"]
-    }
-  }
-}
-```
-
-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`.
+Sources require `default`. A request defaults to the default source, query, GET, load, inherited auth, and view permission. An action defaults to manual and modify permission. DELETE uses full permission and confirmation.
 
 Use stable real URLs for public APIs and clear suggested URLs for self-hosted services. Homarr collects the installer's server URL, network scope, and credentials as source setup; credentials remain outside the manifest.
 
-Paths use `{option:name}` and `{param:name}`; query/body 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.
+Paths use `{option:name}` and `{param:name}`. Query/body data uses `{ "$option": "name" }` and `{ "$param": "name" }`. Load queries cannot use params. Runtime parameter names and primitive values are inferred from references.
 
 Every option has `label`, `control`, and `default`. Optional fields are `description`, `choices`, `choicesFrom`, `min`, `max`, `step`, `advanced`, and `group`.

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

@@ -1,98 +1,110 @@
 ---
 name: mcp-integration
-description: Expose Homarr tRPC procedures safely through MCP. Use when adding or changing tRPC procedures under packages/api, adding MCP metadata, registering an eager MCP router, shaping tool inputs and descriptions, or reviewing MCP authorization, sensitive data, and destructive actions.
+description: Expose tRPC procedures as MCP tools for AI clients. Use when modifying procedures in packages/api/src/router, adding a new tRPC procedure or router, or deciding what to expose via Homarr's MCP interface. Covers .meta({ mcp }), router registration in packages/api/src/mcp.ts, input schema rules, and what to expose vs skip.
 ---
 
 # MCP Integration
 
-Expose a procedure only when an AI client should call it. Preserve the procedure's existing authorization and add MCP-specific safeguards for sensitive or destructive behavior.
+Every new tRPC procedure that provides useful functionality should be exposed as an MCP tool so AI assistants (Claude, Cursor, etc.) can use it. This is a first-class feature of Homarr.
 
-## Assess exposure
+Exposing a procedure makes it callable by any AI client with an API key. Before adding `.meta({ mcp })`, review what the tool exposes: authorization requirements, sensitive data, tenant isolation, auditability, and whether the action is destructive. Prefer exposing read-only queries over mutations unless the mutation is safe and permission-scoped. When in doubt, ask for a security review before shipping a new MCP tool.
 
-Prefer:
+## Adding MCP to a procedure
 
-- Data queries: list, search, get, health, stats, and summaries.
-- User-requested actions with explicit permission checks and bounded inputs.
-- Serializable results that do not reveal credentials or internal-only state.
-
-Skip subscriptions, session/onboarding internals, file streams, blobs, credential values, and procedures whose authorization or audit behavior is unclear. Ask for a security review when a mutation is destructive, tenant boundaries are ambiguous, or returned data is sensitive.
-
-## Add metadata
-
-Place `.meta()` before `.input()` and `.query()` or `.mutation()`:
+Add `.meta({ mcp: { enabled: true, description: "..." } })` to the procedure chain:
 
 ```typescript
-getAll: protectedProcedure
-  .meta({
-    mcp: {
-      enabled: true,
-      description: "List resources the current user can access, including stable IDs used by resource_get",
-    },
-  })
-  .input(z.object({ limit: z.number().int().min(1).max(100).default(50) }))
-  .query(async ({ ctx, input }) => {
-    // Preserve normal procedure authorization.
-  });
-```
+// Read-only tool (query)
+myProcedure: protectedProcedure
+  .meta({ mcp: { enabled: true, description: "Get all items with their status and metadata" } })
+  .input(z.object({ limit: z.number().default(10) }))
+  .query(async ({ ctx, input }) => { ... })
 
-No-input procedures can omit `.input()`; the MCP extractor accepts an empty object for them.
-
-For mutations, state the effect and required permission in the description:
-
-```typescript
-remove: permissionRequiredProcedure
-  .meta({
-    mcp: {
-      enabled: true,
-      description: "Delete one resource by ID. Requires full access; get the ID from resource_all",
-    },
-  })
+// Write tool (mutation)
+myAction: protectedProcedure
+  .meta({ mcp: { enabled: true, description: "Delete an item by ID. Requires interact permission on the integration" } })
   .input(z.object({ id: z.string() }))
-  .mutation(async ({ ctx, input }) => {
-    // Perform the permission-scoped action.
-  });
+  .mutation(async ({ ctx, input }) => { ... })
+
+// No-input procedure (z.void) — works fine, no .input() needed
+getAll: protectedProcedure
+  .meta({ mcp: { enabled: true, description: "List all resources" } })
+  .query(async ({ ctx }) => { ... })
 ```
 
-## Write discoverable descriptions
+The `.meta()` call must come **before** `.input()` and `.query()`/`.mutation()` in the chain.
 
-Include every item that applies:
+## Writing good descriptions
 
-- What the tool returns or changes.
-- Supported integrations or services.
-- Required IDs and the tool that returns them.
-- Permission requirements and the meaning of permission fields.
-- Important bounds, confirmation semantics, or irreversible effects.
+The description is the **only thing** an AI sees to decide when and how to use the tool. Write it like you're explaining to a colleague who has never used Homarr.
 
-Use precise domain language. A description such as `Get calendar events` is insufficient because it omits supported services, required IDs, and result scope.
+**Must include:**
 
-## Shape inputs for clients
+- What the tool returns or does
+- Which integrations/services it works with (if applicable)
+- How to get required IDs (e.g., "Use integration_all to get the integrationId")
+- Permission requirements (if non-obvious)
 
-- Use a top-level `z.object({...})` for parameterized tools.
-- Bound strings, arrays, numeric ranges, pagination, and payload sizes.
-- Use defaults where a safe, unsurprising value exists.
-- Prefer explicit fields over a top-level union or discriminated union.
-- Keep identifiers stable and describe how to obtain them.
-- Keep secrets out of inputs unless the procedure is explicitly a credential-configuration flow with server-owned encryption and non-return guarantees.
+**Good:**
 
-## Register the eager router
+```text
+"Get calendar events for upcoming and recent media releases. Fetches from all connected Sonarr (TV), Radarr (movies), Lidarr (music), and Readarr (books) integrations. Requires integrationIds from integration_all"
+```
 
-The application router in `packages/api/src/root.ts` is lazy. MCP tool extraction is synchronous, so add an eager import and registration in `packages/api/src/mcp.ts`:
+**Bad:**
+
+```text
+"Get calendar events"
+```
+
+**For tools that return permission fields**, explain what they mean:
+
+```text
+"List all integrations. Returns permissions.hasUseAccess (read) and permissions.hasInteractAccess (actions) — false means the API key lacks that permission, not an error"
+```
+
+## Registering in the MCP router
+
+After adding `.meta()` to procedures, you must register the router in `packages/api/src/mcp.ts`. This file uses **eager imports** (no `lazy()`) because MCP tool extraction requires synchronous access to all procedure definitions.
 
 ```typescript
-import { resourceRouter } from "./router/resource";
+// packages/api/src/mcp.ts
+import { myNewRouter } from "./router/my-new-feature";
 
 export const mcpRouter = createTRPCRouter({
-  resource: resourceRouter,
+  // ... existing routers
+  myFeature: myNewRouter,
 });
 ```
 
-Register the smallest router that owns the enabled procedures. If a parent router uses `lazy()`, import the needed subrouter directly. Metadata on a procedure is not enough; a procedure absent from `mcpRouter` is not exposed.
+**If your router is nested** (e.g., widget sub-routers), import and register the sub-router directly — do not import a parent that uses `lazy()`.
 
-## Validate the tool surface
+## What to expose vs. what to skip
 
-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`.
-6. If manually probing `/api/mcp/<transport>`, use a scoped API key and avoid printing credentials or secret-bearing results.
+**Expose:**
+
+- Data queries (list, search, get by ID)
+- Actions users would ask an AI to do (toggle, create, delete, approve)
+- Status checks (health, stats, summaries)
+
+**Skip:**
+
+- Subscriptions (WebSocket-only, not supported by MCP)
+- Internal procedures (session management, onboarding steps)
+- File upload/download procedures
+- Procedures that return non-serializable data (streams, blobs)
+
+## Input schema rules
+
+- Use `z.object({...})` for inputs — this maps cleanly to MCP tool parameters
+- `z.void()` (no `.input()`) works — the MCP handler patches these to accept empty objects
+- Avoid `z.union()` or `z.discriminatedUnion()` at the top level — AI clients struggle with these
+- Use `.default()` on optional fields so the AI doesn't need to guess values
+
+## Checklist for new features
+
+1. Add `.meta({ mcp: { enabled: true, description: "..." } })` to relevant procedures
+2. Import and register the router in `packages/api/src/mcp.ts` (eager, no lazy)
+3. Write descriptions that explain what the tool does, what it needs, and what it returns
+4. If the tool requires an ID from another tool, say which one in the description
+5. Test with `curl` against `/api/mcp/mcp` to verify the tool appears in `tools/list`

.agents/skills/mcp-integration/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Homarr MCP Integration"
-  short_description: "Expose tRPC procedures safely through MCP"
-  default_prompt: "Use $mcp-integration to expose this Homarr tRPC procedure as a safe, discoverable MCP tool."

.deepsource.toml

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

.env.example

@@ -67,8 +67,7 @@ HOMARR_WEBSITE_URL=https://homarr.dev
 # PocketBase API used by Homarr and by the standalone documentation site.
 # Defaults to HOMARR_WEBSITE_URL.
 # WORKSHOP_API_URL=https://homarr.dev
-# Public Workshop website used by links in Homarr, Custom Widgets, onboarding,
-# and assistant context. Defaults to HOMARR_WEBSITE_URL/workshop.
+# Public Workshop page opened from Homarr. Defaults to HOMARR_WEBSITE_URL/workshop.
 # WORKSHOP_WEB_URL=https://homarr.dev/workshop
 
 # Documentation and PocketBase deployment settings.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -33,6 +33,7 @@ body:
       options:
         # The below comment is used to insert a new version with on-release.yml
         #NEXT_VERSION#
+        - 1.77.0
         - 1.76.2
         - 1.76.1
         - 1.76.0

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

@@ -20,7 +20,7 @@ runs:
   using: "composite"
   steps:
     - name: Prebuilt debian dependencies
-      uses: ./.github/actions/prebuilt-debian
+      uses: homarr-labs/homarr/.github/actions/prebuilt-debian@dev
       id: prebuilt-debian
       with:
         architecture: ${{ inputs.architecture }}

.github/actions/prebuilt-debian/action.yaml

@@ -11,6 +11,9 @@ outputs:
 runs:
   using: "composite"
   steps:
+    - uses: actions/checkout@v7
+      with:
+        persist-credentials: false
     - name: Set up Docker Buildx
       uses: docker/setup-buildx-action@v4
 

.github/workflows/autofix.yml

@@ -3,7 +3,7 @@ name: Formatting
 on:
   pull_request:
     types: [opened, synchronize, reopened]
-    branches: ["**"]
+    branches: ["*"]
 
 permissions:
   contents: read

.github/workflows/ci.yml

@@ -3,12 +3,12 @@ name: CI
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["**"]
+    branches: ["*"]
   pull_request_target:
     types: [closed]
-    branches: ["**"]
+    branches: ["*"]
   push:
-    branches: [main, dev, beta, next, v2, release/v2]
+    branches: [main, dev, beta, next, v2]
   merge_group:
   workflow_dispatch:
     inputs:
@@ -51,7 +51,7 @@ jobs:
     name: Fast gate
     if: github.event_name != 'pull_request_target' && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
     runs-on: ubuntu-latest
-    timeout-minutes: 20
+    timeout-minutes: 15
     env:
       TURBO_API: ${{ secrets.TURBO_API }}
       TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
@@ -105,20 +105,18 @@ jobs:
 
   container:
     name: Container and E2E
-    needs: [fast-gate, preview-amd64]
+    needs: fast-gate
     if: |
-      !cancelled() && needs.fast-gate.result == 'success' &&
-      (
-        github.event_name == 'merge_group' ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
-        (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-        (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
-      )
+      github.event_name == 'merge_group' ||
+      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
+      (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
     runs-on: ubuntu-latest
     timeout-minutes: 30
     permissions:
       contents: read
-      packages: read
+      packages: write
+    outputs:
+      digest: ${{ steps.preview-build.outputs.digest }}
     steps:
       - uses: actions/checkout@v7
         if: "!env.ACT"
@@ -133,18 +131,8 @@ jobs:
         if: "!env.ACT"
         uses: docker/setup-buildx-action@v4
 
-      - name: Reuse amd64 preview image
-        if: needs.preview-amd64.outputs.digest != '' && !env.ACT
-        env:
-          DIGEST: ${{ needs.preview-amd64.outputs.digest }}
-        run: |
-          echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u "${{ github.actor }}" --password-stdin
-          docker pull "${PREVIEW_IMAGE}@${DIGEST}"
-          docker tag "${PREVIEW_IMAGE}@${DIGEST}" homarr-ci
-          docker tag "${PREVIEW_IMAGE}@${DIGEST}" homarr-e2e
-
       - name: Build container once
-        if: needs.preview-amd64.outputs.digest == '' && !env.ACT
+        if: "!env.ACT"
         uses: docker/build-push-action@v7
         with:
           context: .
@@ -159,8 +147,8 @@ jobs:
             org.opencontainers.image.source=${{ github.server_url }}/${{ github.repository }}
             org.opencontainers.image.revision=${{ github.sha }}
             org.opencontainers.image.ref.name=pr-${{ github.event.pull_request.number || inputs.pr_number || 'none' }}
-          cache-from: type=gha,scope=homarr-e2e
-          cache-to: type=gha,scope=homarr-e2e,mode=max
+          cache-from: type=gha,scope=homarr-linux-amd64
+          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
           secrets: |
             TURBO_API=${{ secrets.TURBO_API }}
             TURBO_TEAM=${{ secrets.TURBO_TEAM }}
@@ -201,10 +189,7 @@ jobs:
         run: pnpm exec playwright install-deps chromium
 
       - name: Run E2E tests
-        env:
-          NODE_ENV: development
-          CI: "true"
-        run: pnpm exec vitest e2e --retry 1 --maxWorkers 4
+        run: pnpm test:e2e
 
       - name: Upload E2E artifacts
         if: failure() && !env.ACT
@@ -214,44 +199,27 @@ jobs:
           path: e2e/test-results/
           retention-days: 7
 
-  preview-amd64:
-    name: Build amd64 preview image
-    needs: fast-gate
-    if: |
-      (
-        (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
-        (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-      )
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.preview-build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Log in to GHCR
-        if: "!env.ACT"
+      - name: Log in to GHCR for preview publication
+        if: |
+          !env.ACT &&
+          (
+            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
+            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
+          )
         uses: docker/login-action@v4
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build and push amd64 preview image by digest
+      - name: Push amd64 preview image by digest
         id: preview-build
-        if: "!env.ACT"
+        if: |
+          !env.ACT &&
+          (
+            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
+            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
+          )
         uses: docker/build-push-action@v7
         with:
           context: .
@@ -259,20 +227,22 @@ jobs:
           platforms: linux/amd64
           outputs: type=image,"name=${{ env.PREVIEW_IMAGE }}",push-by-digest=true,name-canonical=true,push=true
           cache-from: type=gha,scope=homarr-linux-amd64
-          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
           secrets: |
             TURBO_API=${{ secrets.TURBO_API }}
             TURBO_TEAM=${{ secrets.TURBO_TEAM }}
             TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
             TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
 
+      - name: Show Act publication result
+        if: env.ACT
+        run: echo "Act validated the publication path; external GHCR writes are disabled locally."
+
   preview-arm64:
     name: Build arm64 preview image
     needs: fast-gate
     if: |
       (
         (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
         (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
       )
     runs-on: ubuntu-24.04-arm
@@ -320,15 +290,10 @@ jobs:
 
   publish-preview:
     name: Publish multi-platform preview image
-    needs: [container, preview-amd64, preview-arm64]
+    needs: [container, preview-arm64]
     if: |
-      !cancelled() &&
-      needs.container.result == 'success' &&
-      needs.preview-amd64.result == 'success' &&
-      needs.preview-arm64.result == 'success' &&
       (
         (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-        (github.event_name == 'push' && github.ref == 'refs/heads/release/v2') ||
         (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
       )
     runs-on: ubuntu-latest
@@ -338,7 +303,7 @@ jobs:
       packages: write
       pull-requests: read
     env:
-      PREVIEW_TAG: ${{ github.event_name == 'push' && 'v2' || format('pr-{0}', github.event.pull_request.number || inputs.pr_number) }}
+      PREVIEW_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
     steps:
       - name: Log in to GHCR
         if: "!env.ACT"
@@ -375,28 +340,24 @@ jobs:
       - name: Publish preview manifest
         if: "!env.ACT"
         env:
-          AMD64_DIGEST: ${{ needs.preview-amd64.outputs.digest }}
+          AMD64_DIGEST: ${{ needs.container.outputs.digest }}
           ARM64_DIGEST: ${{ needs.preview-arm64.outputs.digest }}
         run: |
-          tags=(-t "${PREVIEW_IMAGE}:${PREVIEW_TAG}")
-          docker buildx imagetools create "${tags[@]}" \
+          docker buildx imagetools create -t "${PREVIEW_IMAGE}:${PREVIEW_TAG}" \
             "${PREVIEW_IMAGE}@${AMD64_DIGEST}" \
             "${PREVIEW_IMAGE}@${ARM64_DIGEST}"
 
       - name: Verify preview manifest platforms
         if: "!env.ACT"
         run: |
-          tags=("${PREVIEW_TAG}")
-          for tag in "${tags[@]}"; do
-            image="${PREVIEW_IMAGE}:${tag}"
-            manifest="$(docker buildx imagetools inspect "$image" --raw)"
-            for architecture in amd64 arm64; do
-              jq --exit-status --arg architecture "$architecture" \
-                'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
-                <<<"$manifest" >/dev/null
-            done
-            docker buildx imagetools inspect "$image"
+          image="${PREVIEW_IMAGE}:${PREVIEW_TAG}"
+          manifest="$(docker buildx imagetools inspect "$image" --raw)"
+          for architecture in amd64 arm64; do
+            jq --exit-status --arg architecture "$architecture" \
+              'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
+              <<<"$manifest" >/dev/null
           done
+          docker buildx imagetools inspect "$image"
 
   cleanup:
     name: Clean up preview image
@@ -433,14 +394,6 @@ jobs:
               core.info(`No package version found with tag "${tag}"`);
               return;
             }
-            const targetTags = target.metadata?.container?.tags ?? [];
-            const extraTags = targetTags.filter((targetTag) => targetTag !== tag);
-            if (extraTags.length > 0) {
-              core.warning(
-                `Package version ${target.id} also carries tag(s) ${extraTags.map((targetTag) => `"${targetTag}"`).join(", ")}; refusing cleanup.`,
-              );
-              return;
-            }
             await github.rest.packages.deletePackageVersionForOrg({
               package_type: "container",
               package_name: packageName,

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

@@ -13,7 +13,7 @@ on:
         type: boolean
         required: false
         default: true
-        description: Send notifications when redeploying an existing release
+        description: Send notifications
 
 permissions:
   contents: write # Required to update package.json version
@@ -38,10 +38,10 @@ jobs:
       SKIP_RELEASE: ${{ github.event_name == 'workflow_dispatch' || github.ref_name == 'dev' || github.ref_name == 'next' }}
     outputs:
       version: ${{ steps.read-semver.outputs.version || steps.version-fallback.outputs.version }}
-      git_ref: ${{ steps.read-git-ref.outputs.ref || steps.read-semver.outputs.version || github.ref }}
+      git_ref: ${{ steps.read-git-ref.outputs.ref || github.ref }}
       skipped: ${{ env.SKIP_RELEASE }}
     steps:
-      - run: echo "Manual dispatch redeploys the latest existing release without creating a new one"
+      - run: echo "Skipping release for workflow_dispatch event"
         if: env.SKIP_RELEASE == 'true'
         # The below generated version fallback represents a normalized branch name, for example "feature/branch-name" -> "feature-branch-name"
       - run: echo "version="$(echo ${{github.ref_name}} | sed 's/[^a-zA-Z0-9\-]/-/g') >> "$GITHUB_OUTPUT"
@@ -58,9 +58,8 @@ jobs:
           permission-contents: write # required to commit package.json & changelog changes, merge them to dev / next and publish the release
 
       - uses: actions/checkout@v7
-        if: env.SKIP_RELEASE == 'false' || github.ref_name == 'main' || github.ref_name == 'beta'
+        if: env.SKIP_RELEASE == 'false'
         with:
-          fetch-depth: 0
           persist-credentials: false
       - uses: pnpm/action-setup@v6
         if: env.SKIP_RELEASE == 'false'
@@ -69,29 +68,10 @@ jobs:
         with:
           node-version: 24.18.0
           package-manager-cache: false
-      - name: Verify major release intent
-        if: env.SKIP_RELEASE == 'false'
-        run: |
-          latest_tag="$(git describe --tags --abbrev=0)"
-          latest_major="${latest_tag#v}"
-          latest_major="${latest_major%%.*}"
-          package_version="$(jq --raw-output '.version' package.json)"
-          package_major="${package_version%%.*}"
-
-          if (( package_major <= latest_major )); then
-            exit 0
-          fi
-
-          if git log --format='%s%n%b' "${latest_tag}..HEAD" \
-            | grep --extended-regexp --quiet '(^[[:alnum:]-]+(\([^)]*\))?!:)|(^BREAKING[ -]CHANGE:)'; then
-            exit 0
-          fi
-
-          echo "::error::package.json declares ${package_version}, but commits since ${latest_tag} contain no breaking-change signal. Use a conventional ! commit or BREAKING CHANGE footer so Semantic Release creates the intended major version."
-          exit 1
       - name: Install dependencies
         if: env.SKIP_RELEASE == 'false'
-        run: pnpm install --frozen-lockfile
+        run: |
+          pnpm install
       - name: Run Semantic Release
         if: env.SKIP_RELEASE == 'false'
         env:
@@ -223,14 +203,9 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
-      - uses: actions/checkout@v7
-        if: needs.release.outputs.skipped == 'false'
-        with:
-          ref: ${{ needs.release.outputs.git_ref }}
-          persist-credentials: false
       - name: Extract amd64
         if: needs.release.outputs.skipped == 'false'
-        uses: ./.github/actions/extract-build-artifact
+        uses: homarr-labs/homarr/.github/actions/extract-build-artifact@dev
         with:
           digest: "${{ env.GHCR_REPO }}@${{ needs.build-amd64.outputs.digest }}"
           architecture: amd64
@@ -244,14 +219,9 @@ jobs:
     runs-on: ubuntu-24.04-arm
     timeout-minutes: 5
     steps:
-      - uses: actions/checkout@v7
-        if: needs.release.outputs.skipped == 'false'
-        with:
-          ref: ${{ needs.release.outputs.git_ref }}
-          persist-credentials: false
       - name: Extract arm64
         if: needs.release.outputs.skipped == 'false'
-        uses: ./.github/actions/extract-build-artifact
+        uses: homarr-labs/homarr/.github/actions/extract-build-artifact@dev
         with:
           digest: "${{ env.GHCR_REPO }}@${{ needs.build-arm64.outputs.digest }}"
           architecture: arm64
@@ -312,7 +282,6 @@ jobs:
           gh release edit --repo ${{ github.repository }} ${{ needs.release.outputs.version }} --draft=false
 
       - name: Discord notification
-        if: github.event_name != 'workflow_dispatch' || inputs['send-notifications']
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
         uses: Ilshidur/action-discord@0.4.0

.github/workflows/on-pr-prebuilt-debian-validate.yml

@@ -5,7 +5,7 @@ permissions:
 
 on:
   pull_request:
-    branches: ["**"]
+    branches: ["*"]
     paths: [".github/actions/prebuilt-debian/**", "deployments/prebuilt-debian/**"]
 
 jobs:

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

@@ -5,7 +5,7 @@ permissions:
 
 on:
   pull_request:
-    branches: ["**"]
+    branches: ["*"]
     paths: [".github/renovate.json5"]
 
 jobs:

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

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

.github/workflows/update-contributors.yml

@@ -15,6 +15,9 @@ jobs:
   update-contributors:
     runs-on: ubuntu-latest
     timeout-minutes: 2
+    strategy:
+      matrix:
+        node-version: [22]
     steps:
       - name: Obtain token
         id: obtainToken
@@ -31,10 +34,10 @@ jobs:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
 
       - uses: pnpm/action-setup@v6
-      - name: Use Node.js
+      - name: Use Node.js ${{ matrix.node-version }}
         uses: actions/setup-node@v6
         with:
-          node-version: 24.18.0
+          node-version: ${{ matrix.node-version }}
           cache: "pnpm"
 
       - name: Run update script

.github/workflows/workshop.yml

@@ -3,15 +3,11 @@ name: Workshop
 on:
   pull_request:
   push:
-    branches: [dev, v2, release/v2, main]
+    branches: [dev, v2, main]
 
 permissions:
   contents: read
 
-concurrency:
-  group: ${{ github.workflow }}-${{ (github.ref_name == 'v2' || github.ref_name == 'release/v2') && 'v2-preview' || github.ref }}
-  cancel-in-progress: true
-
 jobs:
   validate:
     runs-on: ubuntu-24.04
@@ -31,116 +27,37 @@ jobs:
       - run: pnpm test:workshop
       - run: pnpm test:workshop-image
 
-  publish-amd64:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: validate
-    runs-on: ubuntu-24.04
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/build-push-action@v7
-        id: build
-        with:
-          context: .
-          file: apps/workshop/Dockerfile
-          target: production
-          platforms: linux/amd64
-          outputs: type=image,"name=ghcr.io/homarr-labs/workshop",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=workshop-linux-amd64
-          cache-to: type=gha,scope=workshop-linux-amd64,mode=max
-
-  publish-arm64:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: validate
-    runs-on: ubuntu-24.04-arm
-    timeout-minutes: 20
-    permissions:
-      contents: read
-      packages: write
-    outputs:
-      digest: ${{ steps.build.outputs.digest }}
-    steps:
-      - uses: actions/checkout@v7
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/build-push-action@v7
-        id: build
-        with:
-          context: .
-          file: apps/workshop/Dockerfile
-          target: production
-          platforms: linux/arm64
-          outputs: type=image,"name=ghcr.io/homarr-labs/workshop",push-by-digest=true,name-canonical=true,push=true
-          cache-from: type=gha,scope=workshop-linux-arm64
-          cache-to: type=gha,scope=workshop-linux-arm64,mode=max
-
   publish:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: [publish-amd64, publish-arm64]
+    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'main')
+    needs: validate
     runs-on: ubuntu-24.04
-    timeout-minutes: 5
+    timeout-minutes: 30
     permissions:
       contents: read
       packages: write
-    env:
-      WORKSHOP_IMAGE: ghcr.io/homarr-labs/workshop
     steps:
+      - uses: actions/checkout@v7
+      - uses: docker/setup-qemu-action@v4
       - uses: docker/setup-buildx-action@v4
       - uses: docker/login-action@v4
         with:
           registry: ghcr.io
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
-      - name: Verify branch head before publication
-        uses: actions/github-script@v8
+      - uses: docker/metadata-action@v6
+        id: metadata
         with:
-          script: |
-            const branchName = context.ref.replace("refs/heads/", "");
-            const { data: branch } = await github.rest.repos.getBranch({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              branch: branchName,
-            });
-            if (branch.commit.sha !== context.sha) {
-              core.setFailed(`Branch ${branchName} moved from ${context.sha} to ${branch.commit.sha}.`);
-            }
-      - name: Publish multi-platform image
-        env:
-          AMD64_DIGEST: ${{ needs.publish-amd64.outputs.digest }}
-          ARM64_DIGEST: ${{ needs.publish-arm64.outputs.digest }}
-        run: |
-          tags=(-t "${WORKSHOP_IMAGE}:sha-${GITHUB_SHA}")
-          if [[ "${GITHUB_REF_NAME}" == "v2" || "${GITHUB_REF_NAME}" == "release/v2" ]]; then
-            tags+=(-t "${WORKSHOP_IMAGE}:v2")
-          fi
-          if [[ "${GITHUB_REF_NAME}" == "main" ]]; then
-            tags+=(-t "${WORKSHOP_IMAGE}:latest")
-          fi
-          docker buildx imagetools create "${tags[@]}" \
-            "${WORKSHOP_IMAGE}@${AMD64_DIGEST}" \
-            "${WORKSHOP_IMAGE}@${ARM64_DIGEST}"
-      - name: Verify multi-platform image
-        run: |
-          image="${WORKSHOP_IMAGE}:sha-${GITHUB_SHA}"
-          manifest="$(docker buildx imagetools inspect "$image" --raw)"
-          for architecture in amd64 arm64; do
-            jq --exit-status --arg architecture "$architecture" \
-              'any(.manifests[]; .platform.os == "linux" and .platform.architecture == $architecture)' \
-              <<<"$manifest" >/dev/null
-          done
-          docker buildx imagetools inspect "$image"
+          images: ghcr.io/homarr-labs/workshop
+          tags: |
+            type=sha,prefix=sha-,format=long
+            type=raw,value=v2,enable=${{ github.ref_name == 'v2' }}
+            type=raw,value=latest,enable=${{ github.ref_name == 'main' }}
+      - uses: docker/build-push-action@v7
+        with:
+          context: .
+          file: apps/workshop/Dockerfile
+          target: production
+          platforms: linux/amd64,linux/arm64
+          push: true
+          tags: ${{ steps.metadata.outputs.tags }}
+          labels: ${{ steps.metadata.outputs.labels }}

.gitignore

@@ -25,8 +25,6 @@ packages/db/migrations/*/migrate.cjs
 
 # production
 build
-tools/homarr-dev/homarr
-tools/homarr-dev/homarr-dev
 
 # misc
 .DS_Store
@@ -83,14 +81,3 @@ apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
 benchmark-results
-
-# local performance investigation (never ship benchmark data or restored backups)
-.widget-performance/
-.bench/
-homarr-backup*.zip
-*.sqlite-wal
-*.sqlite-shm
-/scripts/benchmarks/
-
-# PR description screenshots belong on the pull request, not in the repository
-.screenshots/

.impeccable/critique/2026-07-21T11-32-50Z__apps-docs-src-components-workshop.md

@@ -0,0 +1,116 @@
+---
+target: Workshop store in the docs
+total_score: 20
+p0_count: 1
+p1_count: 3
+timestamp: 2026-07-21T11-32-50Z
+slug: apps-docs-src-components-workshop
+---
+
+# Workshop Store Critique
+
+## Design Health Score
+
+| #         | Heuristic                           |     Score | Key issue                                                                                                                                                        |
+| --------- | ----------------------------------- | --------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1         | Visibility of system status         |       1/4 | Fetch failure can show beside an empty-store message, so the system communicates two incompatible states.                                                        |
+| 2         | Match between system and real world |       3/4 | Widget, CSS, voting, revisions, and comments use familiar language.                                                                                              |
+| 3         | User control and freedom            |       2/4 | Filters are reversible, but the crashed route and failed fetch state offer no useful recovery.                                                                   |
+| 4         | Consistency and standards           |       2/4 | The submission editor uses CodeMirror, while revision editing falls back to a textarea; several tiny custom controls do not follow the shared button vocabulary. |
+| 5         | Error prevention                    |       2/4 | Submission validation exists, but disabled progression does not explain what is missing and destructive actions use a brief inline confirmation.                 |
+| 6         | Recognition rather than recall      |       3/4 | Labels, type choices, and the submission stepper are understandable without documentation.                                                                       |
+| 7         | Flexibility and efficiency          |       2/4 | Search covers titles only, signed-out users can select Yours, and installation is reduced to ambiguous Copy and Download actions.                                |
+| 8         | Aesthetic and minimalist design     |       3/4 | The restrained visual system is clean, but the browse toolbar and card action rows become dense.                                                                 |
+| 9         | Help users recover from errors      |       0/4 | The production route crashes with React error 130; the fetch error has no retry action or useful context.                                                        |
+| 10        | Help and documentation              |       2/4 | The editor explains its fields, but the store does not teach the full inspect, trust, download, and install journey.                                             |
+| **Total** |                                     | **20/40** | **Needs work before release**                                                                                                                                    |
+
+## Anti-Patterns Verdict
+
+The surface does not look like obvious AI-generated decoration. Its visual restraint, familiar controls, and practical editor are credible product UI. The weakness is product behavior rather than styling: contradictory states, tiny action controls, an overloaded responsive toolbar, and a primary installation journey that is not explicit.
+
+The deterministic Impeccable scan returned zero findings for `apps/docs/src/components/workshop`. This is useful but incomplete. The detector did not catch runtime failures, semantic state conflicts, touch-target sizing, or responsive grouping. Browser evidence found a full route crash, React error 130, and an earlier state that rendered both `Something went wrong.` and `No submissions yet`.
+
+No visual overlay was injected because the available browser evaluation surface is read-only. Screenshots, DOM snapshots, console logs, and source inspection were used instead.
+
+## Overall Impression
+
+The submission modal is now one of the stronger parts of the Workshop. The store around it is not release-ready. The single biggest opportunity is to make discovery and installation a dependable, explicit path: load reliably, show one truthful state, help users evaluate a submission, and give them one obvious next action.
+
+## What Is Working
+
+1. The visual system is restrained and consistent with the Homarr documentation. Typography, color, radii, and spacing do not compete with the content.
+2. The submission flow chunks a complex task into Type, Details, and Media. The shared JSON/CSS editor, drag-and-drop import, metadata autofill, and capped media previews reduce creator effort.
+3. The detail design exposes revision, author, reports, changelog, source content, and comments. This supports inspection rather than treating community code as a blind install.
+
+## Priority Issues
+
+### P0: The Workshop route crashes in the production docs build
+
+**Why it matters:** No visual polish matters if the store becomes a Docusaurus error page. A fresh independent tab consistently reached `This page crashed` with React error 130. The console attributed the thrown error to the Kapa widget bundle.
+
+**Fix:** Isolate or disable the Kapa script on Workshop routes, prevent third-party widget failures from reaching the Docusaurus route boundary, and add a route-level Workshop boundary that preserves navigation and retry. Reproduce against the built Docker docs image, not only the development server.
+
+**Suggested command:** `$impeccable harden`
+
+### P1: Failure and empty states contradict each other
+
+**Why it matters:** Showing `Something went wrong.` followed by `No submissions yet` makes users believe the store is both broken and empty. The generic message gives no cause and no recovery.
+
+**Fix:** Make loading, failure, empty, and results mutually exclusive. The failure state should say that listings could not be loaded, preserve the current filters, and provide `Try loading again`. Do not render filters or an empty store as authoritative data after the initial request fails.
+
+**Suggested command:** `$impeccable harden`
+
+### P1: Mobile discovery controls are too dense and do not form a responsive hierarchy
+
+**Why it matters:** The toolbar's inner row contains four type choices, sorting, and outdated visibility without wrapping. Most controls are 24 to 28 pixels tall. At narrow widths this is difficult to scan, easy to clip, and below a comfortable touch target.
+
+**Fix:** Put a full-width search first on mobile, keep All, Widgets, and CSS as the primary segmented choice, move sorting and outdated visibility into a compact secondary row or popover, and hide Yours when signed out or make it a sign-in affordance. Use at least 40 to 44 pixel touch targets. Add `aria-pressed` or proper tab semantics to the type filter.
+
+**Suggested command:** `$impeccable adapt`
+
+### P1: The store does not make the install journey obvious
+
+**Why it matters:** A first-time user sees Copy and Download without knowing which is recommended, what will be copied, how to inspect safety, or where the file goes in Homarr. This weakens the store's main purpose.
+
+**Fix:** Make the detail page the decision surface. Use one primary action named for its result, such as `Download widget JSON` or `Copy CSS`, with a short `Install in Homarr` explanation linked to the correct in-app flow. Cards should prioritize title, preview, compatibility, score, and `View details`; secondary utilities should not compete with evaluation.
+
+**Suggested command:** `$impeccable clarify`
+
+### P2: Card and moderation actions are too small and too numerous
+
+**Why it matters:** Vote, copy, download, comment, delete, and report controls compete in a compact footer. Low-contrast icon buttons are hard to discover and hard to use by touch. CSS columns also create a top-to-bottom visual reading order that can differ from the expected row order.
+
+**Fix:** Use a regular responsive grid, remove hover scaling, keep one or two visible card actions, and move owner/moderation actions to a menu. Keep voting visible but increase its target size. Correct the report copy: reports and reporter identities are moderation data, not public social proof.
+
+**Suggested command:** `$impeccable distill`
+
+## Persona Red Flags
+
+### Jordan, first-time self-hoster
+
+Jordan opens Workshop to install a widget. The route can crash before any listing appears. In the partial failure state, Jordan sees both an error and an empty store. If listings load, Copy and Download do not explain the Homarr destination or recommended path. Jordan is likely to leave before installing anything.
+
+### Alex, experienced Homarr administrator
+
+Alex can understand the JSON and appreciates the source viewer, but title-only search and limited filtering make a larger catalog inefficient. Compatibility and required secret information are not prominent at browse time. Tiny moderation and owner controls slow repeated management tasks.
+
+### Morgan, mobile user
+
+Morgan encounters a toolbar with more controls than fit comfortably in one decision group, 24 to 28 pixel targets, and a signed-out Yours filter that leads to an unhelpful no-results state. Submission cards add another dense row of small actions.
+
+## Minor Observations
+
+- Future submission steps are focusable buttons even when clicking them does nothing. Disable them or render non-interactive progress markers.
+- The report textarea relies on placeholder text and needs a persistent accessible label.
+- The revision editor should reuse the same JSON/CSS CodeMirror component as creation.
+- Search should include title, description, and author at minimum.
+- The timed inline `Confirm?` deletion pattern is easy to miss and weak for keyboard and touch users.
+- The detail-page changelog uses an uppercase tracked label, which is unnecessary in this otherwise restrained interface.
+- Loading comments should use the same skeleton vocabulary as listings rather than centered status text.
+
+## Questions to Consider
+
+1. Is Workshop primarily a catalog for discovery, or a technical exchange for copying source? The primary card and detail actions should commit to one answer.
+2. Should users evaluate compatibility and required secrets before opening a listing, or only on the detail page?
+3. Does Workshop need every moderation and ownership action visible inline, or should those actions live behind a menu?

.impeccable/critique/2026-07-21T12-29-41Z__apps-docs-src-components-workshop.md

@@ -0,0 +1,64 @@
+---
+target: Workshop store in the docs
+total_score: 38
+p0_count: 0
+p1_count: 0
+timestamp: 2026-07-21T12-29-41Z
+slug: apps-docs-src-components-workshop
+---
+
+# Workshop Store Critique — Post-Polish
+
+## Design Health Score
+
+| #         | Heuristic                           |     Score | Evidence                                                                                                                                                         |
+| --------- | ----------------------------------- | --------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1         | Visibility of system status         |       4/4 | Loading, initial failure, stale refresh failure, empty, and results states are mutually exclusive; recovery actions are visible.                                 |
+| 2         | Match between system and real world |       4/4 | Actions describe their result: Download widget JSON, Copy CSS, View details, and Install in Homarr.                                                              |
+| 3         | User control and freedom            |       4/4 | Filters can be cleared, errors retried, dialogs cancelled, and destructive submission deletion requires explicit confirmation.                                   |
+| 4         | Consistency and standards           |       4/4 | Creation and revision editing share CodeMirror, buttons follow the shared system, and cards use a predictable responsive grid.                                   |
+| 5         | Error prevention                    |       3/4 | Validation, disabled progression, pending states, RLS, and confirmations are strong; disabled form progression could explain unmet requirements more explicitly. |
+| 6         | Recognition rather than recall      |       4/4 | Persistent labels, type descriptions, step status, source previews, and installation instructions minimize recall.                                               |
+| 7         | Flexibility and efficiency          |       4/4 | Search spans title, description, and author; signed-in filtering, sorting, responsive controls, and direct detail actions support repeat use.                    |
+| 8         | Aesthetic and minimalist design     |       3/4 | The catalog is restrained and scannable; long source documents and the complete creator form necessarily remain dense on small screens.                          |
+| 9         | Help users recover from errors      |       4/4 | Route, listing, edit, report, copy, OAuth, and detail failures remain local and provide a clear next action.                                                     |
+| 10        | Help and documentation              |       4/4 | The detail page explains the exact Homarr destination and links to updated Workshop documentation.                                                               |
+| **Total** |                                     | **38/40** | **Release-quality; minor polish remains**                                                                                                                        |
+
+## Anti-Patterns Verdict
+
+The surface is product-led rather than decorative. The redesign removes the overloaded card footer, hover scaling, tiny touch controls, public moderation details, contradictory states, and ambiguous install actions. The deterministic Impeccable detector reports zero findings.
+
+## What Improved
+
+1. The production route no longer collapses into the Docusaurus crash screen without recovery. A route-local boundary protects navigation, and the fresh-volume production path renders without console errors.
+2. Loading, failure, empty, stale-results, and populated states are truthful and mutually exclusive.
+3. Search and filters form a clear responsive hierarchy. Mobile targets are 40–44 pixels, signed-out users do not see Yours, and cards no longer overflow at 390 pixels.
+4. Cards prioritize evaluation: title, author, type, score, description, comments, and View details. Copy, download, reporting, editing, and deletion moved to the detail page.
+5. The detail page now teaches the installation journey and names its primary action precisely.
+6. Reports and reporter identities are admin-only through PocketBase rules. Public catalog UI no longer turns reports into social proof.
+7. The creator and revision dialogs share the CodeMirror editor, use bounded internal scrolling, expose pending/error states, and avoid step-selection layout shifts.
+
+## Remaining Minor Opportunities
+
+### P2: Explain disabled progression inline
+
+The Type and Details steps are understandable, but a disabled Next button could state the missing requirement for keyboard and first-time users. This is a refinement, not a blocker, because required fields and validation messages are already present.
+
+### P2: Consider a compact source summary on very small screens
+
+The read-only source viewer is intentionally complete and horizontally scrollable. A future collapse/expand summary could reduce page length for nontechnical visitors without hiding inspection entirely.
+
+## Verification Evidence
+
+- Fresh Docker Compose PocketBase volume and production docs image.
+- Populated catalog with widget, CSS, and outdated examples.
+- Desktop and 390px mobile layouts in light and dark themes.
+- Widget detail, installation instructions, CodeMirror source view, and comments.
+- Signed-in submission wizard through Type and Details, including the shared editor.
+- Zero browser console errors after the final fixes.
+- Impeccable deterministic detector: zero findings.
+
+## Compatibility Note
+
+An existing local development volume created from an earlier unreleased version of the reset migration still has a stale Workshop view. It is intentionally not migrated or deleted. A fresh volume created from the current unreleased migration is the supported validation target and works correctly.

.impeccable/critique/2026-07-22T15-58-15Z__apps-docs-src-components-workshop.md

@@ -0,0 +1,106 @@
+---
+target: Homarr Workshop docs UI
+total_score: 27
+p0_count: 0
+p1_count: 2
+timestamp: 2026-07-22T15-58-15Z
+slug: apps-docs-src-components-workshop
+---
+
+## Design Health Score
+
+| #         | Heuristic                       |     Score | Key Issue                                                                                                                                     |
+| --------- | ------------------------------- | --------: | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1         | Visibility of System Status     |         3 | Strong loading, retry, stale-data, pending, and copy states; successful report/edit actions still end silently.                               |
+| 2         | Match System / Real World       |         3 | Core Workshop language is clear, but `networkScope`, query/action, and schema terminology assumes technical fluency.                          |
+| 3         | User Control and Freedom        |         3 | Back, cancel, clear filters, vote toggling, and destructive confirmations are present; destructive actions have no undo.                      |
+| 4         | Consistency and Standards       |         3 | Shared primitives are coherent, though Docusaurus chrome and the denser app-store vocabulary still feel slightly stitched together.           |
+| 5         | Error Prevention                |         2 | Validation and confirmations are good, but install safety and credential context appears after download/copy actions on small screens.        |
+| 6         | Recognition Rather Than Recall  |         3 | Author, revision, source, filters, and capabilities are visible; installation still asks users to remember a separate Homarr navigation path. |
+| 7         | Flexibility and Efficiency      |         2 | Search, filters, sort, drag-and-drop, autofill, and comment shortcuts help; the install handoff remains manual.                               |
+| 8         | Aesthetic and Minimalist Design |         2 | Hierarchy is clear, but repeated panels, badges, uppercase metadata labels, and overlapping install actions add noise.                        |
+| 9         | Error Recognition and Recovery  |         3 | Errors are plain-language and usually preserve work; the global action error can be detached from the failed control.                         |
+| 10        | Help and Documentation          |         3 | The installation guide and source explanation are useful; security terminology lacks inline definitions.                                      |
+| **Total** |                                 | **27/40** | **Acceptable, significant improvements needed**                                                                                               |
+
+## Anti-Patterns Verdict
+
+**LLM assessment:** Moderate AI-assisted feel, not outright slop. Domain-specific copy, extensive state coverage, and transparent source/capability information make the feature credible. The generic card grid, repeated rounded panels, icon tiles, uppercase tracked labels, and decorative changelog stripe still expose a component-recipe grammar. It looks competent but not fully edited into a distinctive Homarr store.
+
+**Deterministic scan:** `detect.mjs --json apps/docs/src/components/workshop` exited 0 with exact output `[]`: zero findings, zero triggered rules, and no false positives. The scan found none of Impeccable's deterministic anti-patterns.
+
+**Visual overlays:** No reliable user-visible overlay is available. The independent detector agent had no browser backend. The parent fallback opened a fresh browser tab and visually inspected the listing, but the browser API did not expose a mutable evaluation method for the required preflight, so injection and `[Human]` visibility were correctly skipped. Browser/source evidence was used instead.
+
+## Overall Impression
+
+The Workshop is already substantially better than a generic gallery: it communicates authorship, source code, API capabilities, secrets, revision history, reports, and discussion. The biggest opportunity is to turn that information into a deliberate trust sequence. Today the interface lets the user act first and understand safety later, especially on mobile.
+
+## What's Working
+
+- **State coverage is unusually strong.** Listing failures, stale data, loading skeletons, empty results, filter recovery, comment errors, pending actions, and destructive confirmations have explicit UI.
+- **Pre-install transparency is excellent.** API hosts, methods, configurable options, network scope, and credential requirements are visible instead of hidden behind a download.
+- **The new primitive layer is coherent.** Search, filters, menus, switches, dialogs, and code presentation share one restrained interaction vocabulary across light and dark themes.
+
+## Priority Issues
+
+### [P1] Safety context arrives after the install action on mobile
+
+**Why it matters:** Download and copy actions appear in the header, while source capabilities, credential requirements, and installation guidance live in an aside that drops below the long source and discussion sections under the desktop breakpoint. A first-time mobile user can commit before understanding what the widget contacts or what secrets it needs.
+
+**Fix:** Put a compact “Before you install” summary immediately below the header on small screens: API hosts, network scopes, credential count, and action/query counts. Keep the full sticky details panel on desktop.
+
+**Suggested command:** `$impeccable layout`
+
+### [P1] Primary button and own-comment contrast misses AA
+
+**Why it matters:** The requested theme's primary red with white foreground is about 3.4:1, below 4.5:1 for small text. The same pairing affects primary buttons and the author's comment bubbles.
+
+**Fix:** Darken the primary red or use a dark foreground in light mode, then verify default buttons and comment bubbles in both themes.
+
+**Suggested command:** `$impeccable colorize`
+
+### [P2] The listing's server-rendered fallback is blank
+
+**Why it matters:** Before hydration, the listing renders an empty block instead of preserving the page's hierarchy and indicating progress. This creates a visible dead zone on slower self-hosted deployments.
+
+**Fix:** Render the listing heading, toolbar silhouette, and shared skeleton cards as the `BrowserOnly` fallback, matching the detail page's loading treatment.
+
+**Suggested command:** `$impeccable harden`
+
+### [P2] Download, copy, source, and install compete for the same task
+
+**Why it matters:** “Download widget,” “Copy JSON,” a full source viewer, and a separate installation panel all appear as parallel paths. Users must infer the recommended workflow.
+
+**Fix:** Make “Download widget JSON” the single primary header action. Keep copy beside the source viewer and place the next import step directly beside or immediately after download.
+
+**Suggested command:** `$impeccable clarify`
+
+### [P2] Repeated metadata scaffolding creates visual noise
+
+**Why it matters:** Card shells, badges, icon tiles, uppercase tracked labels, and the changelog stripe make the detail page feel assembled from recipes and slow scanning.
+
+**Fix:** Flatten the widget details into a compact definition list, reserve badges for status, and remove the decorative changelog stripe.
+
+**Suggested command:** `$impeccable distill`
+
+## Persona Red Flags
+
+**Jordan, first-timer:** “Network scope,” queries, actions, options, and the manifest schema appear without inline explanation. Download versus copy has no stated recommendation. On mobile, credential and installation context arrives after source and discussion.
+
+**Sam, accessibility-dependent user:** Primary controls and author comment bubbles miss small-text contrast. Copy, optimistic votes, filter result changes, and successful report/edit completion do not expose explicit live-region behavior. Gallery controls and dots are below comfortable touch-target sizes.
+
+**Casey, distracted mobile user:** The most important safety panel falls to the bottom, while primary actions stay at the top. Long source and discussion content separate the decision from its explanation. The submit type selector remains dense at narrow widths.
+
+## Minor Observations
+
+- The internal installation guide uses an external-link icon.
+- The final publication action says “Submit” rather than “Publish submission.”
+- Dark-theme tokens are declared in two blocks, increasing drift risk.
+- Screenshot dots rely on opacity alone and lack `aria-current`.
+- Successful report and edit actions deserve a small confirmation instead of silent dismissal.
+
+## Questions to Consider
+
+- If source review is important enough to say “Review exactly what will be installed,” why can users download before seeing the capability and credential summary?
+- Is Workshop primarily a code catalog or a safety-conscious app store? The current action hierarchy tries to be both.
+- Should the successful end state be a downloaded file, or a confident handoff into Homarr with the next step already visible?

.mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "mantine": {
       "command": "npx",
-      "args": ["-y", "@mantine/mcp-server@9.6.0"]
+      "args": ["-y", "@mantine/mcp-server"]
     }
   }
 }

.oxlintrc.json

@@ -30,26 +30,6 @@
   "options": {
     "reportUnusedDisableDirectives": "off"
   },
-  "overrides": [
-    {
-      "files": ["apps/nextjs/src/**/*.ts", "apps/nextjs/src/**/*.tsx"],
-      "excludeFiles": ["**/*.spec.ts", "**/*.spec.tsx"],
-      "rules": {
-        "eslint/no-restricted-imports": [
-          "error",
-          {
-            "paths": [
-              {
-                "name": "@homarr/widgets",
-                "allowTypeImports": true,
-                "message": "Import a narrow @homarr/widgets export to preserve widget lazy loading."
-              }
-            ]
-          }
-        ]
-      }
-    }
-  ],
   "ignorePatterns": [
     "**/*.config.js",
     "**/*.config.mjs",

AGENTS.md

@@ -7,23 +7,22 @@ homarr/
 ├── apps/
 │   ├── nextjs/          # Main Next.js application (port 3000)
 │   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
-│   ├── tasks/           # Cron-job initialization and scheduling runtime
-│   ├── websocket/       # Standalone tRPC WebSocket server (port 3001)
-│   └── workshop/        # Go/PocketBase Workshop service
+│   ├── tasks/           # Cron job runner + Fastify tRPC API (port 3002)
+│   └── websocket/       # Standalone tRPC WebSocket server (port 3001)
 ├── packages/
 │   ├── api/             # tRPC appRouter, procedures, OpenAPI
 │   ├── auth/            # NextAuth config, providers, session, API keys
 │   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
 │   ├── core/            # Env validation, DB/Redis driver factories, logging
 │   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
-│   ├── widgets/         # Dashboard widget definitions and components
+│   ├── widgets/         # All 39 dashboard widgets (definitions + components)
 │   ├── integrations/    # Integration classes (HTTP clients to external apps)
 │   ├── redis/           # Redis pub/sub channels, caching abstractions
 │   ├── translation/     # next-intl setup, locale configs, lang JSON files
 │   ├── ui/              # Shared Mantine components, theme, hooks
 │   ├── validation/      # Shared zod schemas for API/forms
 │   ├── common/          # Shared utilities, IDs, errors
-│   ├── cron-jobs/       # Cron job implementations
+│   ├── cron-jobs/       # Cron job implementations (25+ jobs)
 │   ├── cron-jobs-core/  # Cron scheduling primitives
 │   ├── cron-job-status/ # Cron status via Redis
 │   ├── boards/          # Board context, edit mode, cache updater
@@ -41,9 +40,8 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
-│   ├── custom-widgets/  # Custom JSX v2 schema, validation, and runtime
-│   ├── onboarding/      # Onboarding studio and setup flow
-│   ├── workshop/        # Homarr-side Workshop client and contracts
+│   ├── old-import/      # Legacy Homarr import
+│   ├── old-schema/      # Legacy Homarr zod schemas
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig
@@ -63,7 +61,7 @@ When modifying user-facing code, you MUST also update the corresponding document
 
 - New integration → `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts`
 - New widget → `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`
-- Changed API → `apps/docs/docs/management/api/index.mdx`
+- Changed API → `apps/docs/docs/management/api.mdx`
 - New/changed env vars → `apps/docs/docs/advanced/`
 - New CLI commands → `apps/docs/docs/advanced/command-line/`
 - Auth changes → `apps/docs/docs/advanced/` SSO pages
@@ -86,19 +84,19 @@ When modifying user-facing code, you MUST also update the corresponding document
 - 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 (configured in `.mcp.json`; tools `get_item_doc` / `get_item_props` / `search_docs`) for current v9 APIs before writing component code. Prefer built-in primitives (`Combobox`/`useCombobox` for selects, the polymorphic `component` prop, `@mantine/hooks`) over hand-rolled equivalents. Check `packages/ui/` for existing conventions first.
+
+## MCP servers
+
+`.mcp.json` at the repo root declares project-scoped MCP servers (the standard Claude Code layout; other tools can import the same `mcpServers` block). See the `mantine` entry there for the Mantine v9 server, and the upstream docs at https://mantine.dev/guides/llms/ for per-tool setup (OpenCode: `.opencode/opencode.json`, Codex: `.codex/config.toml`). Only keyless server definitions belong in `.mcp.json`; anything needing secrets stays in local dotfiles.
+
+## Agent Skills
+
+Portable agent skills live in `.agents/skills/` (the Agent Skills open standard). Cursor, Codex, and OpenCode read `.agents/skills/` natively. Claude Code does not scan it, so `.claude/skills/` is a symlink back to `.agents/skills/`. Install skills at `.agents/skills/<name>/SKILL.md` — that single copy is used everywhere. See `.agents/skills/` for available skills (documentation-sync, mcp-integration, codebase-context, datatable-migration).
+
 - 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 ./...`.
-
-## 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` — required user-facing documentation updates
-- `mcp-integration` — safe tRPC-to-MCP exposure
-- `homarr-custom-widget` — safe Custom JSX v2 authoring

CHANGELOG.md

@@ -1,3 +1,5 @@
+## [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)

CHANGES.md

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

PRODUCT.md

@@ -0,0 +1,33 @@
+# Product
+
+## Register
+
+product
+
+## Users
+
+Homarr is used by self-hosters and administrators who assemble dashboards for services running across home labs and private infrastructure. They need dense, reliable controls and status at a glance, with enough guidance to configure advanced features without hiding how they work.
+
+## Product Purpose
+
+Homarr provides one place to organize, observe, and operate self-hosted services. Success means a user can build a useful dashboard quickly, understand its state, recover from configuration errors, and extend it without requiring a bespoke Homarr feature for every service.
+
+## Brand Personality
+
+Direct, capable, and approachable. Copy should be concise and technical when precision matters, while the interface should remain familiar to users who are not developers.
+
+## Anti-references
+
+Avoid decorative admin dashboards, wizard flows that fight ordinary scrolling, hidden configuration magic, inconsistent controls, excessive modal usage, and interfaces that expose implementation complexity before the user needs it.
+
+## Design Principles
+
+1. Keep the user in control by making configuration and consequences visible.
+2. Prefer familiar product patterns and progressive disclosure over custom interaction concepts.
+3. Make simple tasks short without limiting advanced use cases.
+4. Isolate failures so one service or widget cannot disrupt the dashboard.
+5. Use the existing Mantine design language consistently across management and board surfaces.
+
+## Accessibility & Inclusion
+
+Target WCAG 2.2 AA. Support keyboard navigation, screen readers, visible focus, sufficient contrast, reduced motion, non-color status cues, responsive layouts, and actionable error messages.

apps/docs/README.md

@@ -108,5 +108,4 @@ pnpm verify:search
 
 ## Contributing
 
-When a Homarr change affects user-facing behavior, update the corresponding documentation in this app. See the
-[documentation-sync skill](../../.agents/skills/documentation-sync/SKILL.md) for the code-to-documentation mapping.
+When making changes to the homarr codebase that affect user-facing behavior, **always update the corresponding documentation in this app**. See `.cursor/rules/documentation-sync.mdc` for the complete mapping of code changes to doc locations.

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

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

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

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

apps/docs/docs/advanced/_category_.json

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

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

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

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

@@ -1,46 +1,27 @@
 # Command line interface
 
-The Homarr image includes a recovery CLI for operations that cannot be completed in the web interface. It is not an
-application API; use the [API](/docs/management/api) or [MCP endpoint](/docs/management/mcp) for automation.
+The Homarr image ships with a built-in recovery tool. This can be useful, if you do not have access to Homarr or if something is not working.
+Please note that the CLI is an _emergency tool_, not an API tool.
 
-Back up the database and stop Homarr before running a command that changes data.
+:::caution
 
-## Run the recovery CLI
+Using the recovery CLi tool can cause problems when requests are being sent to Homarr while the tool is running. \
+You should also create a backup of the database, in case you break something.
 
-Open a shell in the container, then pass a command to `homarr`:
+:::
 
-```sh
-docker exec -it <container-id> /bin/bash
-homarr <command>
-```
+## Execute CLI with Docker
 
-In QNAP Container Station, open the Homarr container's **Execute** action and select `/bin/bash`.
+1. Execute `docker ps | grep homarr` on the root system with Docker to find the container ID of your Homarr container.
+2. Run `docker exec -it <container-id> /bin/bash homarr <your-command-goes-here>`. \
+   Replace `<container-id>` with your container ID from step 1. \
+   Replace `<your-command-goes-here>` with the command you want to execute (see sub-pages).
 
-See the pages in this section for available commands.
+## Execute CLI with QNAP
 
-## Build a local branch harness
-
-The repository's host-side CLI can build the current checkout and run it as a named Docker harness:
-
-![Homarr developer CLI showing pull requests, local images, and PR CI status](./img/homarr-dev-cli.png)
-
-```sh
-pnpm 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
-```
-
-Pass environment overrides with repeated `--env` options:
-
-```sh
-pnpm cli harness setup feature-board \
-  --env WORKSHOP_WEB_URL=https://example.test \
-  --env FEATURE_FLAG=true
-```
-
-Related commands are `harness build <name>`, `harness run <name>`, and `harness stop <name>`.
+1. Open Container Station in the QNAP Web Interface ![](img/334116069-e7ec4726-3df7-4dc6-a3e0-b745e7eef17f.png)
+2. Select Containers in the menu bar on the left ![](img/334116205-aa09ce40-0701-4f7d-b9f9-b431b9d207c5.png)
+3. Select your Homarr Container ![](img/334116303-714b5e07-b9de-4ec0-a2bc-def7ee38750f.png)
+4. Click "Execute" in the top right of the Window. ![](img/334116411-df1482f9-3aa9-4686-b77f-e0dca09e60b2.png)
+5. Select /bin/bash and click Execute ![](img/334116518-e1ddb515-99c7-4159-81bf-76e889d1e808.png)
+6. Run the Homarr command and press enter (eg. homarr reset-owner-password) ![](img/334116642-08c4f204-5cd0-4e4e-a785-0142e1b279ca.png)

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

@@ -57,8 +57,50 @@ Homarr becomes the instance administrator.
 Use `pnpm docker:dev:up` instead when you only need Redis in the background. Running the migration also seeds the
 default data; use `pnpm db:seed` to seed it explicitly later.
 
-Workshop contributors can set up PocketBase and Docusaurus with the dedicated
-[Workshop development guide](./workshop).
+### Run PocketBase and documentation
+
+Start PocketBase in another terminal:
+
+```sh
+cp apps/workshop/.env.example apps/workshop/.env
+docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
+```
+
+Then start Docusaurus in a third terminal:
+
+```sh
+WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
+```
+
+PocketBase runs on port 8090 and Docusaurus on port 3003. Stopping the services preserves the PocketBase volume.
+
+Open `http://127.0.0.1:8090/_/` and create the first PocketBase superuser. The Workshop UI is available at
+`http://127.0.0.1:3003/workshop`.
+
+Point Homarr at the local services with:
+
+```dotenv
+HOMARR_WEBSITE_URL=http://127.0.0.1:3003
+WORKSHOP_API_URL=http://127.0.0.1:8090
+WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
+```
+
+Restart `pnpm dev` after changing `.env`. GitHub OAuth is optional locally. See
+[`apps/workshop/README.md`](https://github.com/homarr-labs/homarr/blob/HEAD/apps/workshop/README.md) for OAuth,
+Workshop moderator promotion, logs, tests, backup, restore, stopping, and intentional volume reset.
+
+### URL testing
+
+Docusaurus reads `HOMARR_WEBSITE_URL` and `WORKSHOP_API_URL` when it starts or builds. Homarr also reads
+`WORKSHOP_WEB_URL` when its server starts, so these values do not rely on `NEXT_PUBLIC_*` build variables. Test a
+separate API origin before release:
+
+```sh
+HOMARR_WEBSITE_URL=http://127.0.0.1:3003 \
+WORKSHOP_API_URL=http://127.0.0.1:8090 \
+WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop \
+pnpm dev:docs
+```
 
 ### Useful commands
 
@@ -70,6 +112,7 @@ Workshop contributors can set up PocketBase and Docusaurus with the dedicated
 - `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:workshop` — local PocketBase through Docker Compose.
 - `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.
@@ -79,6 +122,7 @@ Workshop contributors can set up PocketBase and Docusaurus with the dedicated
 - `pnpm lint` / `pnpm lint:fix` — check or apply oxlint.
 - `pnpm typecheck` — typecheck all workspaces.
 - `pnpm test` — unit and contract suites.
+- `pnpm test:workshop` — disposable Workshop integration suite.
 - `pnpm build` — production monorepo build.
 - `docker build -t homarr .` — build a production Docker image.
 - `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>` — run it.

apps/docs/docs/advanced/development/widgets-and-integrations.mdx

@@ -1,102 +0,0 @@
----
-title: Widgets and integrations
-tags:
-  - Developer
-  - Technical documentation
-  - Widgets
-  - Integrations
-sidebar_position: 2
----
-
-Homarr keeps feature registration explicit and typed. Feature registration has no generator or generated registry.
-A new feature is available when its typed metadata and lazy loader are registered.
-
-## Add a widget
-
-Keep the UI, options, helpers, and tests together in `packages/widgets/src/<widget>/`. The usual folder only needs an
-`index.ts` definition and a lazily imported `component.tsx`; complex widgets can add local files as needed.
-
-1. Add the stable kind to `packages/definitions/src/widget.ts` and its documentation slug to the direct typed map in
-   `packages/definitions/src/docs/widget-doc-slugs.ts`.
-2. Export `definition` and `componentLoader` from `packages/widgets/src/<widget>/index.ts` with
-   `createWidgetDefinition`. The local definition owns its icon, query keys, refresh interval, options, matchers, and
-   errors. Keep the component behind `withDynamicImport` so adding a widget does not load it on every dashboard.
-3. For an integration-backed widget, add its integration kinds and selection rules once to
-   `packages/definitions/src/widget-integration-map.ts`, then spread `getWidgetIntegrationConfig(kind)` into the local
-   definition. This server-safe config is also the API authorization boundary, avoiding a package cycle without
-   duplicating widget metadata.
-4. Register the widget in both explicit literal loader maps and the type-only module map in
-   `packages/widgets/src/registry.ts`, then add its icon to `packages/ui/src/widget-icons.ts`. The module and component
-   loaders must both use literal import paths. Keeping them separate lets a cold widget load request its definition
-   and component chunks in parallel; the type-only map preserves exact option and component inference. Keep all three
-   maps in the same order so drift is obvious in review.
-5. If the widget needs server data, add its tRPC router under `packages/api/src/router/widgets/` and add its explicit
-   lazy import to `packages/api/src/router/widgets/index.ts`. Keep upstream requests and Redis response caching in
-   `@homarr/request-handler`. Use the widget integration middleware for integration-backed procedures.
-6. Add canonical documentation in `apps/docs/docs/widgets/<slug>/`.
-
-Weather is the small integration-free example. Downloads shows integration selection, polling, server caching,
-mutations, partial upstream failures, and a larger options surface.
-
-## Add an integration
-
-Keep the HTTP client and its capability-specific types in `packages/integrations/src/<integration>/`.
-
-1. Add the typed definition to `packages/definitions/src/integration.ts`, including credential alternatives,
-   categories, documentation slug, ports, Docker aliases, and onboarding metadata when relevant.
-2. Add an explicit lazy creator to `packages/integrations/src/base/creator.ts`. The literal import keeps the
-   implementation out of the initial server bundle and makes the registration easy to find.
-3. Implement only the interfaces required by the widgets that use the service.
-4. Add canonical documentation in `apps/docs/docs/integrations/<slug>/`. Its `index.ts` must satisfy
-   `IntegrationDefinition` so invalid metadata fails type checking without widening the object. Use a type-only import
-   and `satisfies IntegrationDefinition`; do not cast the object.
-
-Beszel is a compact example with several widgets sharing one integration client.
-
-## Write user documentation
-
-Write for technically capable self-hosters. Keep each page short and operational.
-
-- Start with one sentence describing what the integration or widget adds to Homarr.
-- Include prerequisites, credentials, permissions, destructive actions, and non-obvious limits only when they matter.
-- Use numbered steps only when order matters. Prefer the exact UI labels a user must select.
-- Do not add marketing, implementation history, architecture internals, or explanations of basic self-hosting concepts.
-- End when the user can configure and verify the feature; do not repeat the same information in a summary.
-
-The usual page needs only an introduction and a `Configuration` section. Add `Notes` or `Troubleshooting` only for
-real caveats.
-
-## Data and errors
-
-- TanStack Query owns browser caching and refresh behavior. Redis owns shared server response caching for bounded key
-  spaces. Public handlers whose keys come from arbitrary URLs, domains, symbols, or coordinates stay in the bounded
-  process-local cache.
-- Cache raw service responses, never authorization decisions or decrypted credentials. Integration-backed cache keys
-  include keyed credential fingerprints and the complete integration identity, and are invalidated after mutations.
-  The fingerprints change with credentials without exposing their values in Redis keys.
-- Give upstream requests a finite deadline and pass the request handler's `AbortSignal` into clients that support it.
-  Admission is bounded per handler. Request deduplication and distributed lock ownership remain active until the
-  upstream settles or a bounded cleanup grace expires, while unresolved upstream work stays separately capped.
-- Keep validation and authorization on the server. Client-side checks improve UX but do not replace tRPC guards.
-- Use the shared logger with safe identifiers, operation names, duration, and the original error cause. Never log
-  secrets or full upstream payloads.
-- Multi-integration reads should return successful providers when one service fails and surface a clear error when all
-  providers fail.
-
-Registration files intentionally contain boring, explicit imports. This small amount of repetition preserves exact
-TypeScript inference, gives Next.js discoverable lazy chunks, and keeps Ctrl+click navigation reliable.
-
-## Registry imports
-
-Use `@homarr/widgets/manifest` to load registered widgets. `loadWidgetDefinition` is the metadata-only path;
-`loadWidgetComponent` loads only the UI module; and `loadWidgetResources` requests both paths in parallel. These
-loaders cache in-flight and successful promises and remove rejected promises so a later request can retry.
-
-The former root `widgetImports` and `loadWidgetDynamic` exports are intentionally not compatibility aliases.
-`widgetImports` synchronously imported every widget module, and `loadWidgetDynamic` depended on that eager map.
-Restoring them at the package root would defeat lazy definition chunks or add client-only runtime dependencies to
-every root consumer. Migrate metadata consumers to `loadWidgetDefinition`, renderers to `loadWidgetResources`, and
-type-only registry consumers from the removed internal `WidgetImportRecord` helper to the root `WidgetImports` type.
-
-`@homarr/widgets/catalog` remains as a deprecated compatibility subpath for `widgetCatalogIcons`. New imports should
-use `@homarr/ui/widget-icons`, which is the canonical server-safe icon catalog.

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

@@ -1,67 +0,0 @@
----
-title: Workshop operator guide
-sidebar_label: Operator guide
-sidebar_position: 3
-tags:
-  - Workshop
-  - Deployment
-  - Environment variables
-  - PocketBase
----
-
-# Workshop operator guide
-
-Workshop uses PocketBase. The production image serves the Workshop website and API from one origin and stores state in
-`/pb_data`.
-
-## Environment variables
-
-| Variable                               | Purpose                                      | Default                        |
-| -------------------------------------- | -------------------------------------------- | ------------------------------ |
-| `HOMARR_WEBSITE_URL`                   | Documentation/site base used by Homarr links | `https://homarr.dev`           |
-| `WORKSHOP_API_URL`                     | PocketBase API used by Homarr and docs       | `HOMARR_WEBSITE_URL`           |
-| `WORKSHOP_WEB_URL`                     | Public Workshop URL                          | `HOMARR_WEBSITE_URL/workshop`  |
-| `WORKSHOP_PUBLIC_ORIGIN`               | PocketBase-generated links and email         | Required in production         |
-| `PB_ALLOWED_ORIGINS`                   | Allowed browser origins                      | `*`                            |
-| `GITHUB_CLIENT_ID`                     | GitHub OAuth application ID                  | —                              |
-| `GITHUB_CLIENT_SECRET`                 | GitHub OAuth application secret              | —                              |
-| `OPENROUTER_API_KEY`                   | Enables the Homarr Assistant provider        | Provider disabled when empty   |
-| `HOMARR_AI_DAILY_REQUEST_LIMIT`        | Per-user daily request allowance             | `50`                           |
-| `HOMARR_AI_GLOBAL_DAILY_REQUEST_LIMIT` | Shared daily request ceiling                 | `10000`                        |
-| `HOMARR_AI_OPENROUTER_BASE_URL`        | OpenRouter-compatible upstream               | `https://openrouter.ai/api/v1` |
-| `HOMARR_AI_OPENROUTER_MODEL`           | Upstream model behind `homarr/model`         | Selected by the Homarr team    |
-
-Public URL variables accept HTTP(S) origins without embedded credentials, query strings, or fragments. Restart the
-container after changing runtime configuration.
-
-## Authentication and email
-
-Configure both GitHub OAuth variables and use `https://<workshop-host>/api/oauth2-redirect` as the callback. Supplying
-only one OAuth variable is a startup error. Configure SMTP for comment, report, and removal notifications.
-
-For the central community, `PB_ALLOWED_ORIGINS=*` permits requests from self-hosted Homarr origins. A private deployment
-can use a comma-separated allowlist.
-
-## Homarr provider
-
-`OPENROUTER_API_KEY` enables the [Homarr provider](/docs/workshop/homarr-provider). The Workshop server chooses the upstream model and
-enforces per-user and global daily limits. It requests zero-data-retention routing, disables data-collecting providers,
-and does not retain prompts or responses.
-
-Keep an OpenRouter account-level credit limit as the monetary backstop; request limits are not cost limits.
-
-## Deployment
-
-The v2 image is `ghcr.io/homarr-labs/workshop:v2`; immutable `sha-<commit>` tags are preferable for promotion. The
-service listens on port 8090.
-
-When using a reverse proxy, forward the complete hostname, including `/api`, `/_/`, and
-`/workshop-runtime-config.js`. Use a dedicated hostname when Homarr already occupies the intended origin.
-
-Verify `/api/health`, the Workshop page, a public listing request, GitHub sign-in, and one installation after deployment.
-
-## Backup and restore
-
-Stop writes and copy `/pb_data` for a consistent backup. A restore replaces the selected PocketBase data directory, so
-preserve the current volume and verify that the backup contains `data.db` first. Rehearse the restore outside production
-and verify sign-in and one installation afterward.

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

@@ -1,41 +0,0 @@
----
-title: Workshop development
-sidebar_position: 4
-tags:
-  - Workshop
-  - Developer
-  - Docusaurus
-  - PocketBase
----
-
-# Workshop development
-
-See the [main development guide](./getting-started) for repository prerequisites.
-
-Start PocketBase:
-
-```sh
-cp apps/workshop/.env.example apps/workshop/.env
-docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
-```
-
-Start Docusaurus in another terminal:
-
-```sh
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
-```
-
-PocketBase runs at `http://127.0.0.1:8090`; create the first superuser under `/_/`. Workshop is available at
-`http://127.0.0.1:3003/workshop`.
-
-To connect a local Homarr instance, set:
-
-```dotenv
-HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-WORKSHOP_API_URL=http://127.0.0.1:8090
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-```
-
-Restart the affected development process after changing these variables. See
-[`apps/workshop/README.md`](https://github.com/homarr-labs/homarr/blob/HEAD/apps/workshop/README.md) for OAuth,
-moderation, tests, and service maintenance.

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

@@ -35,30 +35,7 @@ Using the `PUID` and `PGID` will require you to set the correct permissions on t
 | `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false`                       |
 | `HOMARR_WEBSITE_URL`     | Main Homarr documentation/site base used by runtime links. Must be an absolute HTTP(S) URL.                                                                                                                                            | HTTP(S) URL                         | `https://homarr.dev`          |
 | `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone documentation.                                                                                                                                                                            | HTTP(S) URL                         | `HOMARR_WEBSITE_URL`          |
-| `WORKSHOP_WEB_URL`       | Public Workshop website used by links in Homarr, Custom Widgets, onboarding, and assistant context.                                                                                                                                    | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
-
-Workshop service operators can find its server-only configuration in the
-[Workshop operator guide](/docs/advanced/development/workshop-operator#environment-variables).
-
-### Workshop service
-
-These variables configure the separate Workshop service, not the Homarr application container.
-
-| Environment Variable                        | Description                                                               | Default                           |
-| ------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------- |
-| `WORKSHOP_PUBLIC_ORIGIN`                    | Public origin used in PocketBase links and email                          | Required in production            |
-| `PB_ALLOWED_ORIGINS`                        | Browser origins allowed to call PocketBase                                | `*` for the public community      |
-| `WORKSHOP_IMAGE`                            | Workshop image used by the staging Compose file                           | `ghcr.io/homarr-labs/workshop:v2` |
-| `WORKSHOP_EXPOSE_PORT`                      | Host port for the combined staging service                                | `8090`                            |
-| `PB_EXPOSE_PORT`                            | Host port for local PocketBase development                                | `8090`                            |
-| `DOCS_EXPOSE_PORT`                          | Host port for local documentation development                             | `3003`                            |
-| `GITHUB_CLIENT_ID` / `GITHUB_CLIENT_SECRET` | Optional GitHub OAuth application credentials                             | -                                 |
-| `OPENROUTER_API_KEY`                        | Server-only upstream key that enables the Homarr Assistant provider       | Provider disabled                 |
-| `HOMARR_AI_DAILY_REQUEST_LIMIT`             | Daily Assistant request units per user                                    | `50`                              |
-| `HOMARR_AI_GLOBAL_DAILY_REQUEST_LIMIT`      | Daily Assistant request units shared by all users                         | `10000`                           |
-| `HOMARR_AI_OPENROUTER_BASE_URL`             | OpenRouter-compatible provider endpoint                                   | `https://openrouter.ai/api/v1`    |
-| `HOMARR_AI_OPENROUTER_MODEL`                | Upstream model exposed through the stable `homarr/model` alias            | Selected by the Homarr team       |
-| `HOMARR_AI_ALLOW_INSECURE_UPSTREAM`         | Allows an HTTP upstream for local provider tests; never use in production | `false`                           |
+| `WORKSHOP_WEB_URL`       | Public Workshop page opened from Homarr.                                                                                                                                                                                               | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
 
 ## Authentication
 
@@ -78,12 +55,11 @@ A random secret can be generated by using the following command: `openssl rand -
 
 ## Docker
 
-| Environment Variable  | Description                                                                                                                                                                                                          | Possible values                                         | Default |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
-| `DOCKER_SOCKET_PATHS` | Comma-separated mounted Docker-compatible socket paths. Homarr discovers each path as a selectable Docker environment                                                                                                | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
-| `DOCKER_HOSTNAMES`    | Comma-separated plaintext TCP hostnames. Pair each hostname with the port in the same position in `DOCKER_PORTS`                                                                                                     | For example `localhost,docker.example.com`              | -       |
-| `DOCKER_PORTS`        | Comma-separated plaintext TCP ports paired with `DOCKER_HOSTNAMES`                                                                                                                                                   | For example `2375,2376`                                 | -       |
-| `DOCKER_ENDPOINTS`    | Optional advanced JSON configuration for custom names, TLS, or restricted capabilities. It takes precedence over the simple variables above. See the [Docker and Podman connection guide](/docs/integrations/docker) | A JSON array of endpoint descriptors                    | -       |
+| Environment Variable  | Description                                                                                                                              | Possible values                                         | Default |
+| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
+| `DOCKER_HOSTNAMES`    | Comma-separated list of hostnames to connect to                                                                                          | For example `localhost,docker.example.com`              | -       |
+| `DOCKER_PORTS`        | Comma-separated list of ports to connect to                                                                                              | For example `2375,2376`                                 | -       |
+| `DOCKER_SOCKET_PATHS` | Comma-separated list of mounted Docker-compatible socket paths. See the [Docker and Podman integration guide](/docs/integrations/docker) | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
 
 ## Database
 
@@ -133,9 +109,12 @@ External redis is currently not supported with Proxmox Community Scripts
 The advanced deployments environment variables should only be used if you know what you are doing.
 :::
 
-| Environment Variable     | Description                                         |
-| ------------------------ | --------------------------------------------------- |
-| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts. |
+| Environment Variable     | Description                                                                                                                                                                                                       |
+| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts.                                                                                                                                                               |
+| `WORKSHOP_PUBLIC_ORIGIN` | Origin used in PocketBase-generated links and email. It must be set explicitly in production and must match the externally reachable Workshop origin.                                                             |
+| `PB_ALLOWED_ORIGINS`     | Browser origins accepted by PocketBase. Use `*` for the central public community so arbitrary self-hosted Homarr instances can use the API and OAuth; private staging may use a comma-separated origin allowlist. |
 
 All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
-trailing slashes when Homarr or Docusaurus starts.
+trailing slashes when Homarr or Docusaurus starts. The Docusaurus-only `WORKSHOP_URL` name is accepted as a deprecated alias for
+`WORKSHOP_API_URL` for one release. `WORKSHOP_API_URL` takes precedence.

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

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

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

@@ -143,7 +143,7 @@ networks:
 ```
 
 :::important
-Homarr and Caddy must share the same Docker network:
+Homarr needs to be on the same network so you will need to add the following property to your homarr install:
 
 ```yaml
 homarr:

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

@@ -1,37 +1,102 @@
 # Styling
 
-Homarr uses Mantine and supports custom CSS at two scopes:
+:::tip
 
-- **Global:** **Management → Settings → Instance branding → Custom CSS**.
-- **Board:** **Board settings → Custom CSS**. Board CSS loads after the global stylesheet and can override it.
-
-Both editors accept direct CSS and Workshop imports.
-
-:::warning
-
-Custom CSS can break after updates and is not an authorization boundary. Hidden controls remain accessible to users who
-have permission to use them.
+This page is directed at more experienced users with knowledge about CSS and browsers.
+We recommend you to [look into the board customizations instead](/docs/management/boards#appearance),
+if you do not have experience with writing custom styles or CSS.
 
 :::
 
-## Target elements
+:::warning
 
-Use browser developer tools to inspect the element and test a selector. Prefer stable semantic or Mantine class names;
-avoid generated classes such as `mantine-Card-x2fske`, which change between builds.
+Our support specifically excludes custom CSS, and we will not help you to write CSS.
+However, we may help you by adding new CSS classes if required.
 
-To target one widget, add a custom class under **Edit item → Advanced options** and use that class in the board CSS.
+:::
 
-Use `!important` only when the existing cascade requires it.
+Homarr uses https://mantine.dev/ under the hood. You can change the look & feel of Homarr
+using custom CSS, that extends or overwrites the styles from Mantine.
 
-## Theme variables
+## Getting into CSS
 
-Mantine exposes [CSS variables](https://mantine.dev/styles/css-variables-list/) that can be overridden globally or per
-board:
+If you don't have any experience with CSS,
+we strongly recommend you to go through the courses here: https://www.w3schools.com/css/.
+Due to the infinite scenarios and setups possible with custom CSS,
+our support team will not provide any support with your own written CSS.
+
+## Limitations and dangers
+
+When using custom CSS, you can break the page or certain functionalities.
+Although CSS can improve the design & feel of the page, it **<ins>cannot do any of the following</ins>**:
+
+- Implement new features, widgets or integrations
+- Securely hide elements you don't want users to interact / have permission to
+- Completely revamp the design of the page, only smaller changes are possible
+
+Here are some dangers of using custom CSS:
+
+- Updates may contain breaking changes in the structure, built-in styling or how styling is processed. Therefore,
+  custom CSS may break unexpectedly without any warning
+- Custom CSS may make certain elements invisible or not possible to click / interact with
+- Custom CSS could make readability and accessibility worse for impaired people
+
+## How to inspect the page
+
+When styling the page, you can use the `Inspector` to inspect elements on the page and try out styles.
+This may vary depending on your browser and operating system, but the workflow usually goes like this:
+
+- Open the Homarr page
+- Press `Ctrl` + `Shift` + `I` at the same time.
+  Alternatively, right-click on the page and choose `Inspect` or `Inspect element`.
+- Open the tab `Elements` if it isn't open yet.
+- Search the element you want to change in the DOM tree or use the element picker (usually at the top left)
+  to select it by clicking on the page.
+- Experiment by changing the CSS code on the right side
+
+When writing custom CSS, it is important to also remember or create a selector, which tells the browser
+which element to apply the styles to. If you accidentally broke something or want to revert your changes in the inspector,
+simply reload the page.
+
+## Using Homarr's classes
+
+Homarr's elements will already have a lot of classes and styles pre-applied.
+You can reuse those classes to apply additional styles or overwrite them.
+When overwriting, remember to add the `!important` flag to your CSS property to tell the browser to use our instruction instead.
+
+Classes with random number suffixes, such as `mantine-Card-x2fske`, should be avoided, since those are dynamic
+CSS classes that will change with every build. This means, every time you update Homarr,
+your styles will no longer apply to them
+
+## Defining custom classes for widgets
+
+If you want to apply the styles only for one widget, you can define custom class names only for that widget.
+To do that, enter edit mode on your board, click the three dots of your widget, click `Edit item` and click `Advanced options`.
+Then, you can enter as many custom classes as you'd like:
+
+![](./img/widget-custom-classes.png)
+
+To save them, click `Save changes` on both modals and exit edit mode.
+
+## Where to enter custom CSS
+
+After you wrote your custom CSS, it is time to permanently save it, so you don't need to use the inspector anymore.
+To do this, enter the board settings:
+
+![](./img/enter-board-settings.png)
+
+Scroll down a bit and click on custom CSS.
+Here you can enter your CSS code, which will be applied on the respective board page.
+
+![](./img/custom-css-setting.png)
+
+## Using variables
+
+You can also change the values of the theme variables, which are located here: https://mantine.dev/styles/css-variables-list/.
+To do this, see the following example CSS:
 
 ```css
 :root {
   --mantine-primary-color-filled: #ffbb00;
 }
 ```
-
-CSS changes presentation only; use widgets, integrations, permissions, or application code for behavior.

apps/docs/docs/community/_category_.json

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

apps/docs/docs/community/donate.mdx

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

apps/docs/docs/community/faq.mdx

@@ -5,46 +5,106 @@ tags:
   - Help
 ---
 
-### Can Homarr run on a Raspberry Pi?
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
 
-Yes, when the device uses a supported `linux/arm64` operating system. `linux/arm/v7` is not supported. See
-[Prerequisites](/docs/getting-started).
+### Can I install Homarr on a Raspberry Pi?
 
-### Can I use custom app icons?
+Yes, Homarr is compatible with the architecture of the Raspberry Pi. Have a look in our <a href="/docs/category/installation-1">installation guide</a> on how to do so.
 
-Yes. Use a direct image URL, one of Homarr's icon sources, or upload an image. See [Icons](/docs/advanced/icons).
+### I have a suggestion / idea for improvement or want to report a bug
 
-### Can I create widgets?
+You can report issues, suggestions, or ideas for improvements <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
 
-Yes. [Custom Widgets](/docs/management/custom-widgets) use server-side API requests and safe JSX. They can be written in
-the workbench or created with an MCP-connected agent.
+### Can I use my own custom icons for apps?
 
-### Can Homarr be exposed to the internet?
+Yes, check out our guide on <a href="/docs/advanced/customizations/icons">how to add your custom icons</a>.
 
-Homarr supports authenticated and public deployments. Terminate HTTPS at a reverse proxy, keep Homarr updated, and grant
-public board access only when anonymous viewing is intended. See [Board access control](/docs/management/boards#access-control)
-and [Single sign-on](/docs/advanced/single-sign-on).
+### Some of my online icons are not working (anymore)
 
-### Where are the logs?
+It seems the `cdn.jsdelivr.net` database of icon sometimes appear in the lists for DNS-Holes (PiHole, AdGuard Home...). <br />
+So make sure to manually whitelist this address.
 
-Use **Management → Tools → Logs** for retained and live application logs. Container startup failures and older events are
-available through the deployment platform, for example `docker container logs homarr`.
+### Can I add my own widgets? Do I need programming skills?
 
-Use the browser developer console only for client-side failures. Review logs before sharing them because URLs and other
-deployment details may be present.
+Yes. A [Custom Widget](/docs/management/custom-widgets) can read a public or private HTTP API.
 
-### Why can Homarr not reach a service behind Gluetun?
+It can show responsive Mantine JSX. It can also use widget options and actions with board permission checks.
 
-Gluetun's firewall blocks traffic that is not explicitly allowed. Configure its
-[`FIREWALL_OUTBOUND_SUBNETS`](https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md) for the relevant
-LAN or Docker subnet, and use an address reachable from the Homarr container.
+Custom JSX v2 is the only Custom Widget format. Write the JSON and JSX in the workbench.
 
-### Where do I report a bug or request a feature?
+You can also use the AI copy prompt. An MCP agent can validate and preview a definition before it saves the definition.
 
-Use the [GitHub issue templates](https://github.com/homarr-labs/homarr/issues/new/choose). For community support, see
-[Get in touch](/docs/community/get-in-touch).
+The workbench reads a pasted AI response. It shows request capabilities and redacted diagnostics.
 
-### Can Homarr be used commercially?
+A template cannot import packages or run arbitrary JavaScript. It cannot call browser `fetch`.
 
-Yes. Homarr is licensed under the [Apache License 2.0](/docs/community/license). Commercial users can support development
-through [OpenCollective](/docs/community/donate).
+Named requests use the Homarr server. The server applies board permissions and the network policy.
+
+Before installation, examine the origins, methods, permissions, and actions. Use the same review before publication.
+
+### Is it secure to expose Homarr to the web?
+
+Yes, since v0.14.0, we are confident that Homarr is secure enough to be exposed to the web.
+Make sure to enable the "allow anonymous access" [option in the settings](/docs/management/boards#access-control), if you want to allow people without an account to be able to see your dashboard (not edit)
+
+### How do I open the console / log?
+
+There are two different sources of information:
+
+- console: This is your client (browser). It can tell us, if there is an issue on the client (crash, bug, ...).
+- log: This is your server. It will tell us, if there are issues with connections for the integrations, crashes and errors.
+
+Both variants _can_ contain personal data. It's recommended, that you don't post them publicly or remove personal data from it.
+
+<Tabs>
+  <TabItem value="apple" label="Read console" default>
+
+> Note: This will not work on most mobile browsers.
+
+Open your browser and ensure, that Homarr is your current tab.
+Press `CTRL` + `SHIFT` + `I` on your keyboard. If this shortcut doesn't work, please use one of the alternatives: https://developer.chrome.com/docs/devtools/open/.
+Click on `Console` in the new window, that opened. There, you should see white, orange and sometimes red messages. You can use the Windows Snip & Sketch tool (or your respective tool on Linux / MacOS) to screenshot those messages.
+
+> Please never execute any commands in the console. Scammers are using the console to let you execute harmful commands. If you want to resolve an issue in Homarr, **you'll never have to execute any commands here**
+
+  </TabItem>
+  <TabItem value="orange" label="Read log">
+
+This depends on your installation method. If you use Unraid, you can simply click on the App and on `Log`. If you have a bare Docker install, use `docker container logs homarr`. If you used a different name than `homarr` for your container, you need to replace said argument. Here is some additional information about the command: https://geekflare.com/check-docker-logs/.
+
+  </TabItem>
+</Tabs>
+
+### How do I post logs?
+
+Please check [the section above](#how-do-i-open-the-console--log), on how to obtain logs. Logs should always be posted to https://pastebin.com/ or https://rentry.co/.
+
+### Can I use Homarr at my company?
+
+Yes, you can! But please consider a donation, if our work has been useful to you.
+
+### I think I found a bug. What can I do?
+
+If you think, that you found a bug, please create an issue <a href="https://github.com/homarr-labs/homarr/issues/new/choose">here</a>.
+
+### Why can't I use my custom icons?
+
+You need to restart the Homarr Docker container after adding icons.
+
+### Why can't homarr see/ping containers running locally behind GluetunVPN?
+
+This is because GluetunVPN, and many other docker VPN services, secure their VPN connections with strict firewalls. These firewalls often block access to local containers, even on the same docker network. The workaround for <a href="https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md">GluetunVPN</a> is to add "- FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24" into the environmental variables of the docker compose file. If you are using a firewall on your system, you will need to add a rule that allows requests from ip's in the range of 192.168.xxx.xxx . If you are using UFW the command would be "sudo ufw allow from 192.168.0.0/16".
+Tip: If you are running your torrent client behind a VPN, and running Sonarr (or something similar) normally, make sure to open your torrent client's port in your firewall. If you don't, Sonarr will not be able to see it. Furthermore, use your machines IP (192.168.x.x) rather then 127.0.0.1 or localhost.
+
+### Can I get in touch with you?
+
+Yes, go <a href="/docs/community/get-in-touch">here</a> to get with us in touch.
+
+<hr />
+
+:::tip
+
+Haven't found the solution to your problem / question? We are eager to help you on [our Discord](/docs/community/get-in-touch#discord) or in a [GitHub Issue](https://github.com/homarr-labs/homarr/issues/new/choose).
+
+:::

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

@@ -1,23 +1,24 @@
 ---
-title: Get in touch
-description: Community, support, and private contact channels.
+title: Get In Touch
+description: Still have a question? Click here!
 tags:
   - Help
   - Community
 ---
 
-# Get in touch
+We're happy to talk with you! Shoot us a message at the following places:
 
-## GitHub
+## E-Mail
 
-Use the [issue templates](https://github.com/homarr-labs/homarr/issues/new/choose) for bugs and feature requests.
+We are open to discuss sponsorships, security vulnerabilities and other private requests through our email.
+Please do not report any bugs / feature requests here - they will be ignored and deleted.
+
+[homarr-labs@proton.me](mailto:homarr-labs@proton.me)
 
 ## Discord
 
-Use the [Homarr Discord server](https://discord.gg/aCsmEV5RgA) for community support, release discussion, and dashboard
-showcases.
+We have a Discord Server, where we announce new releases, discuss features and bugs and show off our dashboards.
+There are over 4'000 members and we're happy to answer your questions or concerns.
+You're also open to discuss new / upcoming features and any offtopic selfhosting content.
 
-## Email
-
-Use [homarr-labs@proton.me](mailto:homarr-labs@proton.me) for security reports, sponsorships, and other private matters.
-Bug reports and feature requests belong on GitHub.
+[_![](https://discordapp.com/api/guilds/972958686051962910/widget.png?style=banner2)_](https://discord.gg/aCsmEV5RgA)

apps/docs/docs/community/translations.mdx

@@ -5,24 +5,51 @@ tags:
   - Translations
 ---
 
-# Translations
+We want to make Homarr accessible for everyone.
+But to do that, we need your help.
+We are running a community program that enables everyone to translate Homarr into their language – no programming required.
+We are using [Crowdin](https://crowdin.com/) to manage our translations.
+You can find the translations [here](https://translate.homarr.dev/).
 
-Homarr translations are managed on [Crowdin](https://translate.homarr.dev/). Select a language, translate strings in
-context, and submit them for proofreading. Approved translations ship with a later Homarr release.
+## How to translate
 
-## Translate from Homarr
+### Using crowdin's online platform
 
-Select **Crowdin (live translations)** as the application language, connect a Crowdin account, and choose the target
-language. Select text in Homarr or use Crowdin's in-context panel to edit a string.
+Go to the [Crowdin translations](https://translate.homarr.dev/) and select a language you want to translate.
+You can then enter the translation mode and start translating.
+After you've submitted your translations, a Proofreader will review your changes.
+After a translation has been approved, it will be merged to the language development branch.
+We merge this one periodically to the development branch.
+After the next update of Homarr, all changes from the development branch will be merged, including the changes in the translations.
 
-Live translation submits changes to Crowdin; it does not update the installed Homarr image. Crowdin's preview option can
-show pending translations before the next Homarr release.
+### Using live translate
+
+You can also help translate homarr directly from the app!
+For this you can simply change your language to "Crowdin (live translations)"
+
+![](./img/crowdin-language-select.png)
+
+Then you'll be prompted to connect to your Crowdin account and choose the language in which you want to transalte.
+You can then start translating directly from the app by selecting some text on the app.
+If some text cannot be selected to be edited with the live translation tool, you can still translate it inside of the In-Context popup at the Home tab, it will be red if it's not translated yet.
+
+![](./img/crowdin-live-translate.png)
+
+:::caution
+Although you are translating directly from the app, your translations will not be directly be available inside of your language, they will be in the next update of Homarr, because we have to push the new translations to a new docker image.
+
+If you really want to use them you can enable the "preview transaltions" option in the live translate settings, but be aware that this is not recommended for performance reasons.
+:::
+
+:::tip
+
+Do you want to become a proofreader? [Let us know on our Discord](/docs/community/get-in-touch#discord)! We will add you to the proofreader team. You can then review the translations and approve them. **Note:** You must speak the language fluently, have it as your native language or lots of experience with it.
+
+:::
 
 ## Guidelines
 
-- Preserve the meaning and context of the English source.
-- Keep terminology consistent with existing translations.
-- Do not add punctuation, formatting, or explanatory text that is absent from the source.
-- Improve an existing translation only when the replacement is more accurate.
-
-Contact the [Discord community](/docs/community/get-in-touch#discord) to help proofread a language.
+1. Translate with context: Some translations can't be translated 1:1 - they need context. Ensure that your translations make sense in the context.
+2. Keep things simple and original - no additional characters are needed.
+3. Don't translate the same thing twice - if you see a translation that is already translated, don't translate it again unless you have a better translation.
+4. Keep your translations as close to the original as possible.

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

@@ -6,76 +6,384 @@ tags:
   - Configuration
 ---
 
-On first launch, onboarding creates the administrator, connects optional services, and builds the first board. A
-compatible SQLite backup can also be restored from the welcome screen.
+import imageStartFromScratchStepServerSettings from "./img/onboarding-from-scratch-step-server-settings.png";
+import imageStartFromScratchStepAdminUser from "./img/onboarding-from-scratch-step-admin-user.png";
+import imageStartFromScratchStepExternalAdminGroup from "./img/onboarding-from-scratch-step-external-admin-group.png";
+import imageStartFromScratchStepFinish from "./img/onboarding-from-scratch-step-finish.png";
+import manageBoardHeaderEditMode from "./img/manage-board-header-edit-mode.png";
+import manageBoardHeaderAddItem from "./img/manage-board-header-add-item-menu.png";
+import manageBoardHeaderChooseItem from "./img/manage-board-header-choose-item.png";
+import manageBoardNoApp from "./img/manage-board-no-app.png";
+import manageExportOldHomarr from "./img/old-homarr-export-data.png";
+import manageImportOldHomarrDropzone from "./img/old-homarr-import-dropzone.png";
+import manageImportOldHomarrChooseData from "./img/old-homarr-import-choose-imported-data.png";
+import manageImportDecryptionToken from "./img/old-homarr-import-decryption-token.png";
 
-If onboarding returns after a restart, check that `/appdata` is writable and persisted. See the
-[Docker installation guide](/docs/getting-started/installation/docker).
+:::tip
 
-## Core concepts
+Read our [glossary](/docs/getting-started/glossary) if you are new to Homarr.
 
-### Boards
+:::
 
-A **board** is a dashboard page containing apps, widgets, and Containers. Boards can be public or restricted to users
-and groups. Each user can choose a home board.
+Congratulations on installing Homarr. Now it's time to get yourself familiar with the concepts of Homarr and how to use it.
 
-![Board management with board previews](./img/after-installation-boards.png)
+## Onboarding
 
-See [Boards](/docs/management/boards) for responsive layouts, access control, appearance, and home-board settings.
+The onboard will show the first time you start Homarr.
+This process will help you with your first steps and adding some initial data, such as the administrator account.
 
-### Apps
+:::note
 
-An **app** is a saved shortcut: a name, URL, icon, and optional status check. Add an App tile or a Bookmarks widget to
-show apps on a board.
+If you see this screen repeatitly after you restarted the Homarr container, your Docker mounting paths may be missing,
+incorrect or read-only. Read [our installation instructions](/docs/getting-started/installation/docker) again to fix this issue.
 
-![App management with saved shortcuts](./img/after-installation-apps.png)
+:::
 
-See [Apps](/docs/management/apps) or [Icons](/docs/advanced/icons).
+You can either import a previous dashboard using the ZIP archive or start from scratch:
 
-### Integrations
+![Screenshot of Step 1 onboarding](./img/onboarding-step-1.png)
 
-An **integration** is a server-side connection from Homarr to a supported service such as Sonarr, Home Assistant, or
-Docker. Integrations provide data and actions to widgets. They can also be linked to apps.
+You may refresh anytime and continue from a different device - the onboarding is saved immediately on the server for your convenience.
 
-![Integration catalog with compatible widgets](./img/after-installation-integrations.png)
+### Starting from scratch
 
-See [Managing integrations](/docs/management/integrations) and the
-[integration catalog](/docs/category/integrations).
+Depending on your auth provider configuration you will either first see the admin user creation form or the external group creation form.
+If the credentials provider was selected, you'll be prompted to create an admin user for Homarr.
+This user cannot be deleted and has full control over Homarr and all of its boards.
+You must choose a username and password (both can later be changed).
+We enforce strict password requirements when you enter your password to protect your instance if you accidentally
+expose it to the internet.
 
-### Widgets
+<img src={imageStartFromScratchStepAdminUser} alt={"Screenshot form to create admin user"} width={300} />
 
-A **widget** is a board tile. Some widgets work on their own; others require one or more integrations. Configuration,
-supported integrations, and non-obvious limitations are documented on each widget page.
+If you selected external providers (such as LDAP or OIDC), you'll be prompted to create an admin group.
+This group will be used to synchronize users from your provider to Homarr.
+When a user logs in through the provider, any of their groups that match groups in Homarr will be assigned to the user.
+The name of the group must match exactly the name of the group in the provider.
 
-![Board in edit mode with the add-content menu](./img/after-installation-widgets.png)
+<img
+  src={imageStartFromScratchStepExternalAdminGroup}
+  alt={"Screenshot form to create external admin group"}
+  width={300}
+/>
 
-See the [widget catalog](/docs/category/widgets).
+Next, you can configure some basic settings for Homarr. We recommend to leave all settings at default for most users.
+Here you can also disable analytics. Please note that our analytics are completly anonymous and is fully compliant with GDPR and PECR.
 
-### Containers and rails
+<img
+  src={imageStartFromScratchStepServerSettings}
+  alt={"Screenshot of analytics and indexing settings in the onboarding"}
+  width={300}
+/>
 
-A **Container** groups board items and can be nested. A **rail** reserves a fixed area at the left or right of a
-responsive layout. Both are configured in board edit mode.
+### Setting up integrations
 
-![Board layout settings with fixed sidebars](./img/after-installation-containers-rails.png)
+After configuring server settings, the onboarding guides you through setting up your integrations.
 
-See [Boards](/docs/management/boards#containers-and-rails).
+#### Docker service discovery
 
-### Users, groups, and permissions
+If Docker is available (socket mounted), Homarr automatically detects running containers and matches them to known integration types.
+Matching integrations are pre-selected in the integration list, saving you from manually picking each one.
 
-Users inherit permissions and default boards from their groups. Resource-specific access can further restrict boards
-and integrations.
+#### URL templating
 
-![Group permission settings](./img/after-installation-users-permissions.png)
+You can define a base URL template to auto-fill integration URLs in bulk.
+Two modes are supported:
 
-See [Users and groups](/docs/management/users) and [single sign-on](/docs/advanced/single-sign-on).
+- **Subdomain mode** - e.g. `{app}.example.com` where `{app}` is replaced with the integration name
+- **Port mode** - e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port
 
-## Explore further
+#### API key helper links
 
-- [Server settings](/docs/management/settings)
-- [Assistant](/docs/management/assistant)
-- [Custom Widgets](/docs/management/custom-widgets)
-- [Community Workshop](/docs/workshop)
-- [API](/docs/management/api) and [MCP](/docs/management/mcp)
-- [Keyboard shortcuts](/docs/advanced/keyboard-shortcuts)
+For integrations that require API keys (such as Sonarr, Radarr, SABnzbd, or Seerr), a helper link opens the relevant settings page in the target application so you can quickly copy your key.
 
-See the [glossary](/docs/getting-started/glossary) for a compact list of Homarr terms.
+#### Creating apps from Docker containers
+
+You can optionally auto-create bookmark apps for all discovered Docker containers, making them immediately available on your board.
+
+:::note
+
+Release providers and Search.ch are configured directly in their widgets instead of the integrations page.
+
+:::
+
+After this step, you finished the onboarding.
+The onboarding can no longer be started again.
+From here you can click on one of the provided links to continue your journey.
+We recommend you to continue with the section [creating your first board on this page](#creating-your-first-board).
+
+<img src={imageStartFromScratchStepFinish} alt={"Screenshot of the finish onboarding process with links"} width={300} />
+
+### Importing a ZIP from version before 1.0.0
+
+This is recommended when you used Homarr before and want to re-import your data.
+It is important that you first migrate correctly using [the list of breaking changes for 1.0](/blog/2024/09/23/version-1.0).
+
+<img src={manageExportOldHomarr} alt="Export from old Homarr" style={{ maxWidth: 500 }} />
+
+**How to export and import data**
+
+1. Navigate to your old Homarr, open your management pages, open the tools submenu and open `Migrate to 1.0`.
+2. Check the contents that you want to export. We recommend you to export all data.
+3. Click on the export data button
+4. Save the ZIP file, that is being downloaded, on your device. If you selected "integrations" or "users", you also get an encryption / decryption key.
+   Copy it and do not loose it!
+5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose `Import from Homarr before 1.0`
+6. Drag and drop your previously downloaded ZIP archive into the file upload: <br/><img src={manageImportOldHomarrDropzone} style={{ maxWidth: 500 }} />
+7. Next, choose the data that you want to import and how to import it. Since screen sizes were removed in 1.0, we create a new board for every screen size by default. We recommend you to only keep the best layout and adjust it later in 1.0.0 - but you can also import all of them and pick later.<br/><img src={manageImportOldHomarrChooseData} style={{ maxWidth: 500 }} />
+8. If you previously exported integrations or users, you will be asked to decrypt the data safely using your obtained encryption token. Paste into the modal and confirm your action.<br/><img src={manageImportDecryptionToken} style={{ maxWidth: 500 }} />
+9. Next, you can [follow the same setup as when starting from scratch](#starting-from-scratch). After you completed the onboarding, all of your data will be migrated and available.
+
+## Creating your first board
+
+In Homarr, you organize your apps and widgets on boards.
+Boards can be organized using the interactive drag and drop.
+Let's create your first board by navigating here: `Manage` > `Boards` > `New board`:
+![](./img/manage-create-board-button.png)
+
+A board must always have a name and can either be public or private.
+Public boards are also accessible for users, that are not logged in ([see access control for boards](/docs/management/boards/#access-control)).
+
+![](./img/manage-create-board-modal.png)
+
+Congratulations - you've just created your first board. You can see boards, that you have access to, on this page:
+
+![](./img/manage-view-board.png)
+
+## Add your first app to Homarr
+
+To add links to your dashboard, you must first add them as an "app".
+Navigate to this page to add an app:
+
+![](./img/manage-navigate-apps.png)
+
+Next, click on the `New app` button. You'll need to provide a name and an icon to create an app.
+The name must be at least one character long but you can provide any image URL for the icon.
+Homarr ships with over 11K icons - so you can just search by entering a search text instead.
+
+![](./img/manage-add-app-form.png)
+
+After you created the app, you'll see in on the apps page:
+
+![](./img/manage-created-app.png)
+
+## Arrange and organize your board
+
+Let's add your freshly created app, from the previous step, to the board.
+To do this, edit your previously created board by clicking on the big `Open board` button:
+
+![](./img/manage-view-board.png)
+
+Here you have the following options in the header:
+
+![](./img/manage-board-header.png)
+
+- **Search**: Here you can search for data. You can search for integrations, boards, actions, sites and much more. Some actions may be context dependent (eg. will only show when certain widgets are on your page)
+- **Edit mode**: Clicking this button will toggle the edit mode. In this mode you can edit the contents of your board.
+- **Settings**: Clicking this button will redirect you to a settings page where you can adjust the board settings (page title, colors, ...).
+- **Profile**: This avatar will be visible on every page. Clicking it will show a menu with actions.
+
+When entering the edit mode, you'll get some additional buttons to work with:
+
+<img src={manageBoardHeaderEditMode} alt={"Screenshot of buttons in the edit mode"} width={200} />
+
+- **Add item**: Click this button to add new elements to your page.
+- **Exit edit mode**: Click this btuton to save your changes and exit edit mode.
+
+To continue, click the option "New Item":
+
+<img src={manageBoardHeaderAddItem} alt={"Screenshot of the add item menu"} width={200} />
+
+Next, you can choose what item you'd like to add.
+We will discuss the other options in the following sections - for now choose "App" to continue.
+
+<img src={manageBoardHeaderChooseItem} alt={"Screenshot of choosing the app item in the modal"} width={300} />
+
+As soon as you chose the app, the modal will close and you'll get the following item on your board:
+
+<img src={manageBoardNoApp} alt="Screenshot of the No app element on the board" />
+
+This is expected, because you haven't told Homarr what app it should show in this item.
+To configure this, click on the small 3 dots at the top of the item in the edit mode and choose "Edit item" in the menu.
+
+![](./img/manage-board-edit-app.gif)
+
+In the modal you can edit the app that you want to display:
+
+![](./img/manage-board-choose-app.png)
+
+As soon as you save your changes, the tile on the board will refresh and display your app.
+Using the small bidirectional arrow at the bottom right you can resize the element.
+Start pressing with your mouse button down, move your mouse to resize and release your finger as soon your you're happy with the size.
+
+![](./img/resize-item.gif)
+
+To move your item to a different position on the board, simply hold the mouse button anywhere on the item and move with the mouse to the desired position.
+As soon as you release your finger, the item will snap in place in the grid.
+
+![](./img/move-item.gif)
+
+:::note
+
+You cannot move items freely on the vertical axis.
+We always align all items to the top of the page to simply organization.
+To move items to the bottom, you must add more items or resize items.
+
+:::
+
+:::tip
+
+We recommend you to experiment for a few minutes, before you start building your actual dashboard.
+This helps you to explore the capabilities of Homarr before you build your board in a suboptimal way.
+
+:::
+
+Users on touch or mobile devices may not be able to drag and drop or move items.
+They can use the "Move / resize item" option in the edit menu of items instead:
+
+![](./img/manage-board-move-resize-item-menu.png)
+
+Be sure to save your changes by exiting edit mode!
+
+![](./img/exit-edit-mode.png)
+
+## Adding your first integration
+
+Now it's time to integrate some basic data into your board.
+To do this, we first need to create an integration.
+An integration is a connection between Homarr and a third party application - usually something that you run and deploy yourself.
+
+Navigate to `Manage` > `Integrations` (for example via your user menu).
+As an example, we are going to use the public demo instance of **Dash.** - a popular application to monitor CPU / hardware usage.
+Choose the **Dash.** integration from the list of available integrations:
+
+![](./img/choose-integration.gif)
+
+Next, choose a name (or leave it at default), enter `https://dash.mauz.dev/` as the URL in the form and click on `Test connection and create`.
+Pressing the save button will perform a test request to the integration, to confirm that the networking setup is working as expected.
+Sometimes invalid configurations, firewalls and other mistakes can lead to connectivity problems - [follow this guide here](/docs/management/integrations/#troubleshooting-connection) if you experience issues.
+
+If connection was successful, you will be redirect back to the list of integrations.
+Now let's embed it to your board (see next section).
+
+:::note
+
+Some integrations may require additional configuration, such as a username, password or API tokens.
+Depending on your networking setup and applications, the connection from Homarr might also get blocked by firewalls,
+the target application or your router.
+
+:::
+
+## Embed integration data using widgets
+
+Let's add your integration, that you have configured in the section above, as a widget to your board.
+First, navigate back to your board that you want to add it to.
+Next, enter edit mode again and add another item to your board:
+
+![](./img/manage-board-header-add-item-menu.png)
+
+Instead of choosing an app, let's choose `System Health Monitoring` this time.
+Click on "Add to board":
+
+![](./img/manage-board-header-choose-system-health.png)
+
+Resize the item slightly and then edit it using the three dots menu at the top:
+
+![](./img/edit-system-health-widget.gif)
+
+Next, choose your newly created Dash. integration in the integrations dropdown:
+
+![](./img/manage-board-edit-system-health.png)
+
+:::note
+
+Some widgets may support multiple integrations at the same time.
+If they do not support multiple integrations, you will be unable to select more than one.
+
+:::
+
+Confirm your changes by pressing save.
+Editing a widget will trigger a data update and data will soon appear:
+
+![](./img/widget-system-health.png)
+
+As with every change, don't forget to save your changes using the exit edit mode button:
+
+![](./img/exit-edit-mode.png)
+
+## Grouping your items
+
+As the last step, let's organize your freshly created items using two different options.
+You can choose either or both of them on your boards.
+
+### Using dynamic sections
+
+Dynamic sections are a simple, resizable visual group to group items.
+
+![](./img/create-dynamic-section.png)
+
+After adding a dynamic section, you can simply drag and drop items into the section:
+
+![](./img/dynamic-section.gif)
+
+### Using categories
+
+Categories are more advanced and complicated than dynamic sections.
+To create a category, open the add item modal and choose "new category":
+
+![](./img/add-category.png)
+
+Every category must have a name. After you click "Add category", you will get a new item on your board:
+
+![](./img/category.gif)
+
+You can drag and drop items in to this category in the edit mode.
+Categories will have a big space before and after them in the edit mode to
+enable you to drag and drop items outside the category.
+You can also collapse or open categories in edit mode to facilitate your editing process.
+
+:::note
+
+A current limitation of categories is, that they will always have a width of 100%.
+You cannot reduce their horizontal width.
+
+:::
+
+## Guided tours
+
+After completing the onboarding, Homarr provides interactive guided tours to help you discover key features.
+
+### Management tour
+
+When you first visit the management area (`/manage`), Homarr walks you through the main pages: boards, apps, integrations, and users (admin only).
+Each page highlights the list view and the create action so you know where to find and add things.
+
+### Board tour
+
+When you first open a board, a tour highlights the board header elements: search, edit mode, settings, board switcher, and user menu.
+
+### Tour controls
+
+- Press **Enter** (or click **Next**) to advance through tour steps
+- Tours auto-start on first visit and do not repeat once completed
+- Tours are skipped on mobile screens (below `sm` breakpoint)
+- You can **reset tours** from the user settings page under **Manage > Users > [Your user] > General**
+
+## Next steps
+
+You're done with the basic setup 🔥. Now it's time to organize and customize even more.
+We highly recommend you to experiment with different options, styles and configurations.
+See these curated pages for your next steps:
+
+- Create new apps using the [apps management](/docs/management/apps/)
+- Customize your board or add more boards using the [boards management](/docs/management/boards/)
+- Integrate software that you use using the [integrations management](/docs/management/integrations/)
+- Choose from our beautiful and interactive [widgets](/docs/category/widgets)
+- See [all supported integrations](/docs/category/integrations)
+- Integrate with Homarr with your own application using [the API](/docs/management/api/)
+
+:::danger
+
+The Homarr Team will never ask for your credentials. Do not send people your credentials, as they manage the access to your applications and can cause harm to your device if they are abused.
+
+:::

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

@@ -1,20 +1,13 @@
 # Glossary
 
-This glossary explains Homarr's main components and the terms used for them.
+In the glossary, you'll learn the different components and their names of Homarr.
 
-| Term            | Definition                                                                       |
-| --------------- | -------------------------------------------------------------------------------- |
-| App             | A saved shortcut with a name, destination, icon, and optional status check       |
-| Assistant       | A conversation interface that can use model responses and Homarr tools           |
-| Board           | A dashboard page where apps, widgets, and Containers are arranged                |
-| Container       | A resizable board area containing apps, widgets, or nested Containers            |
-| Custom Widget   | A validated definition for an API-backed board tile                              |
-| Edit mode       | The board state used to add, move, resize, configure, or remove content          |
-| Homarr provider | An Assistant provider routed through Workshop with a per-user allowance          |
-| Integration     | A server-side connection from Homarr to a supported service                      |
-| Layout          | An arrangement of board items selected for a viewport width                      |
-| Provider        | The model API selected for Assistant                                             |
-| Rail            | A fixed area at the left or right of a non-Mobile board layout                   |
-| Task            | A background workload that runs without an active browser session                |
-| Widget          | A board tile that displays information or provides actions                       |
-| Workshop        | A separate community service for sharing Custom Widget definitions and board CSS |
+| Term            | Definition                                                                                                     |
+| --------------- | -------------------------------------------------------------------------------------------------------------- |
+| Apps            | An piece of software that you or a third party hosts (eg. Google)                                              |
+| Integration     | A connection to a service outside of Homarr                                                                    |
+| Dynamic section | Resizeable area where items on your board can be placed and grouped                                            |
+| Widget          | A tile that uses your integrations to display data or enables you to interact with with them                   |
+| Edit mode       | Temporary state that you can enter where you can drag and drop, edit or customize your board                   |
+| Board           | Customizable page which can be edited using the edit mode. This is where apps, sections and widgets are placed |
+| Tasks           | Workloads that are performed in the background - even if there is no user present                              |

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

@@ -1,31 +1,45 @@
 ---
-title: Getting started
+title: Prerequisites
 sidebar_position: 1
 tags:
   - Getting Started
   - Installation
+  - Docker
+  - Unraid
 ---
 
-import {
-  GettingStartedOverview,
-  InstallationPaths,
-} from "@site/src/components/pages/getting-started/getting-started-overview";
+import Link from "@docusaurus/Link";
+import { IconArrowRight } from "@tabler/icons-react";
 
-<GettingStartedOverview />
+Before you try to install Homarr, please review if your device meets the requirements.
+Installing on an unsupported device may lead to unstable behaviour and no support will be provided.
 
-## Requirements
+## Hardware
 
-- `linux/amd64` or `linux/arm64`;
-- 500 MB RAM;
-- 600 MB free disk space for the container image;
-- a persistent writable `/appdata` directory.
+- At least 500MB RAM
+- At least 600MB of free disk space for the Docker image. SSD is preferred.
+- Single or dual core CPU
+- Stable network connection, Wi-Fi use is not recommended
 
-`linux/arm/v7` is not supported.
+## Architecture
 
-## Choose an installation method
+We build Homarr for a bunch of different architectures, including ARM. Please ensure that your device architecture is supported by Homarr. We won't be able to provide support for unusual or outdated architectures.
 
-<InstallationPaths />
+| Architecture | Supported        |
+| ------------ | ---------------- |
+| linux/amd64  | ✅ Supported     |
+| linux/arm64  | ✅ Supported     |
+| linux/arm/v7 | ❌ Not supported |
 
-After Homarr starts, open it in a browser and complete onboarding. Then continue with
-[After the installation](/docs/getting-started/after-the-installation) for the core concepts and the most useful next
-links.
+## Getting started with installation
+
+<Link
+  data-attr="Go to installation"
+  className={"button button--secondary button--lg rounded-3xl dark:border-zinc-600 dark:bg-zinc-800"}
+  to="/docs/category/installation-1"
+>
+  <div className={"flex items-center gap-3"}>
+    <span className={"dark:text-gray-200"}>Go to Installation</span>
+    <IconArrowRight className={"dark:text-gray-200"} size={20} />
+  </div>
+</Link>

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

@@ -2,52 +2,106 @@ import { DockerInstallSnippet } from "@site/src/components/pages/installation/do
 
 # Docker
 
-Docker Compose is the recommended installation method. Install
-[Docker Engine](https://docs.docker.com/engine/install/) and the
-[Compose plugin](https://docs.docker.com/compose/install/).
+Docker is our recommended installation method for beginners and professionals.
+It is easy to use, ships with all dependencies inside a single container and is easy to use and maintain.
+It requires at least some basic knowledge of [Docker](https://www.docker.com/).
+We recommend [NetworkChuck's Docker Containers 101](https://www.youtube.com/watch?v=eGz9DS-aIeY) as a good start for complete beginners.
 
-## Docker Compose
+## Docker compose
+
+### Prerequisites
+
+- A Linux or Windows based system that meets the [hardware prerequisites](/docs/getting-started/#hardware) and [architecture prerequisites](/docs/getting-started/#architecture).
+- [Docker](https://docs.docker.com/get-docker/)
+- [Docker Compose](https://docs.docker.com/compose/install/) - _preinstalled on many systems nowadays_
+
+### Installation
 
 <DockerInstallSnippet data-visual-test="blackout" />
+Finally, run ``docker compose up -d`` in the same directory. This will start the Homarr container in the background.
 
-Start Homarr from the directory containing `docker-compose.yaml`:
+:::caution
 
-```sh
-docker compose up -d
-```
+Docker compose creates a network by default. Some integrations may not work (specifically Dash.) when the network internal hostname is used since clients do not know this name. It is recommended that you either use a local network wide hostname or the IP directly. An alternative is to create a DNS record with the same internal compose stack hostname for all clients outside.
 
-Persist `/appdata`; it contains the database and configuration. Mount the Docker socket only when Homarr needs Docker
-discovery or management.
+:::
 
-Integration URLs must be reachable from the Homarr container. Browser-facing app URLs may use a different hostname;
-see [Managing integrations](/docs/management/integrations#configuration).
+### Updating
 
-### Update
+To update, navigate to the directory with the `docker-compose.yaml` located.
 
-```sh
-docker compose pull
-docker compose up -d
-```
+- Stop Homarr using `docker compose down`
+- Pull the newest image of Homarr using `docker compose pull`
+- Start Homarr again using `docker compose up -d` (`-d` for detached mode - start in background)
+- Delete the old image using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
 
-### Uninstall
+You can automate this process using [Watchtower](https://containrrr.dev/watchtower/).
 
-`docker compose down` removes the containers and Compose network. Delete the configured `/appdata` host directory or
-volume only when the Homarr data is no longer needed.
+### Uninstalling
 
-## Docker CLI
+To uninstall, navigate to the directory with the `docker-compose.yaml` located.
 
-The equivalent standalone container is:
+- Stop Homarr using `docker compose down`
+- Delete the created directories & files on your root file system (check `docker-compose.yaml` file for your specific locations)
+- Delete compose file using `rm docker-compose.yaml`
+- Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+- (Optional): Prune any network or volumes if you use any.
+- (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.
 
-```sh
-docker run \
+## Docker standalone
+
+:::caution
+
+[Docker Compose](#docker-compose) is easier and recommended for beginners. Consider using compose instead.
+
+:::
+
+### Prerequisites
+
+- A Linux or Windows based system that meets the [hardware prerequisites](/docs/getting-started/#hardware) and [architecture prerequisites](/docs/getting-started/#architecture).
+- [Docker](https://docs.docker.com/get-docker/)
+
+### Installation
+
+To install Homarr using Docker, simply run the following command.
+
+```bash
+docker run  \
   --name homarr \
   --restart unless-stopped \
   -p 7575:7575 \
   -v /var/run/docker.sock:/var/run/docker.sock \
-  -v /absolute/path/to/homarr/appdata:/appdata \
+  -v <your-path>/homarr/appdata:/appdata \
   -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' \
   -d ghcr.io/homarr-labs/homarr:latest
 ```
 
-Remove the Docker socket mount when it is not required. To update, pull the current image, recreate the container with
-the same arguments, and keep the `/appdata` mount and `SECRET_ENCRYPTION_KEY` unchanged.
+:::note
+
+Docker will mount the configuration files and icons to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
+
+:::
+
+### Updating
+
+To update Homarr, you must remove your container first. Make sure that you've mounted your data and that you have access to it, so your configuration doesn't get lost.
+
+1. Run `docker rm homarr` to remove the container.
+2. Pull the latest Homarr image `docker pull ghcr.io/homarr-labs/homarr:latest`.
+3. Re-run the command you used to install Homarr.
+
+This process can get tideous, if you update frequently. Thus, we recommend [using docker-compose](#docker-compose)
+
+:::tip
+
+Want to update all your containers automatically? Checkout [Watchtower](https://containrrr.dev/watchtower/) a service which will automatically update your containers on a set interval.
+
+:::
+
+### Uninstalling
+
+1. Obtain the container ID of your Homarr container using `docker ps | grep homarr`.
+2. Delete the container using `docker rm <your-container-id>`
+3. Prune unused Docker images using `docker image prune` (_Warning: this also removes you other unused images - not just Homarr_)
+4. (Optional): Prune any network or volumes if you use any.
+5. (Optional): Remove Homarr from your reverse proxy, VPNs or tunnels if you use any.

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

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

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

@@ -1,8 +1,14 @@
 # Portainer
 
-## Install with a stack
+## Portainer Stacks
 
-Create a Portainer stack with this Compose file:
+### Prerequisites
+
+- [Portainer Stacks](https://www.portainer.io/blog/stacks-docker-compose-the-portainer-way)
+
+### Installing
+
+To install Homarr using Portainer Stacks, simply create a new stack and paste the following code into it.
 
 ```yml title="docker-compose.yml"
 #---------------------------------------------------------------------#
@@ -22,12 +28,21 @@ services:
       - "7575:7575"
 ```
 
-Replace `<your-path>` with an absolute host path, generate `SECRET_ENCRYPTION_KEY`, then deploy the stack. See
-[Portainer's stack documentation](https://docs.portainer.io/user/docker/stacks/add) for Portainer-specific options.
+:::note
+Portainer will mount the files to your host machine. Please make sure to replace `<your-path>` from the docker run command with your desired storage location. The path must be absolute.
+:::
+
+Then, click on `Deploy the stack` and wait until the container has started.
+
+:::tip
+
+If you're unsure how to create a stack, checkout the [Portainer Documentation](https://docs.portainer.io/user/docker/stacks/add).
+
+:::
 
 ### Updating
 
-Pull the current image and redeploy the stack:
+To update Homarr using Docker Compose or Portainer Stacks, simply pull the latest image and restart the container.
 
 1. Run `docker pull ghcr.io/homarr-labs/homarr:latest` to pull the latest image.
 2. Re-run `docker-compose up -d` or re-deploy the stack in Portainer.

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

@@ -1,11 +1,9 @@
 # QNAP
 
 :::caution
-
-The available QNAP guides target Homarr 0.15.10 and have not been updated for 1.0.
-
+QNAP installation guide has not updated to 1.0 yet. There guide is still for 0.15.10.
 :::
 
-Run Homarr with [Container Station](https://www.qnap.com/en/software/container-station) or the
-[third-party QNAP package](https://www.myqnap.org/product/homarr/). A community
-[Container Station guide](https://post.smzdm.com/p/awzm7op2/) is available in Chinese.
+When installing on QNAP, we recommend you to install Homarr using [Container Station](https://www.qnap.com/en/software/container-station) or [this third-party image](https://www.myqnap.org/product/homarr/).
+
+There is also a guide available, but note that it is written in Chinese: https://post.smzdm.com/p/awzm7op2/

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

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

apps/docs/docs/integrations/beszel/index.ts

@@ -1,9 +1,9 @@
-import type { IntegrationDefinition } from "@site/src/types";
+import { IntegrationDefinition } from "@site/src/types";
 
-export const beszelIntegration = {
+export const beszelIntegration: IntegrationDefinition = {
   name: "Beszel",
   description:
     "Beszel is a lightweight server monitoring platform with Docker stats, historical data, and alert functions.",
   iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/beszel.svg",
   path: "../../integrations/beszel",
-} satisfies IntegrationDefinition;
+};

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

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

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

@@ -1,25 +1,115 @@
 ---
 title: "Docker"
-description: "Connect Homarr to Docker-compatible container engines."
+description: "Docker is a platform where you can run your applications in containers, allowing for easy deployment and management of applications."
 hide_title: true
 ---
 
 import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
+import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IconBrandDocker, IconTool } from "@tabler/icons-react";
 import { dockerIntegration } from ".";
 import { dockerContainersWidget } from "@site/docs/widgets/docker-containers";
 
 <IntegrationHeader integration={dockerIntegration} categories={["Containers"]} />
 
-### Widgets and capabilities
+### Widgets & Capabilities
 
-<IntegrationCapabilites items={[{ widget: dockerContainersWidget, note: "Requires administrator access" }]} />
+<IntegrationCapabilites
+  items={[
+    {
+      widget: dockerContainersWidget,
+      note: "This widget can only be used with administrator privileges",
+    },
+  ]}
+/>
 
-Docker endpoints are configured with environment variables rather than under **Management → Integrations**.
+## Enabling the Docker integration
 
-## Local socket
+This integration must first be enabled.
+If you directly run on the host system and you have docker installed, it will be enabled by default.
+Otherwise, you'll need to mount the [docker socket](https://docs.docker.com/engine/security/protect-access/) to the Homarr container,
+so Homarr can interact with the Docker service.
 
-Mount the Docker socket into the Homarr container:
+In Docker Compose, you can simply add this line:
+
+```yaml {10}
+#---------------------------------------------------------------------#
+#     Homarr - A simple, yet powerful dashboard for your server.      #
+#---------------------------------------------------------------------#
+services:
+  homarr:
+    container_name: homarr
+    image: ghcr.io/homarr-labs/homarr:latest
+    restart: unless-stopped
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock # <--- add this line here!
+      - ./homarr/appdata:/appdata
+    environment:
+      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
+    ports:
+      - "7575:7575"
+```
+
+With docker run, add this parameter: `-v /var/run/docker.sock:/var/run/docker.sock`.
+In Windows, you'll need to adjust the slashes: `-v //var/run/docker.sock:/var/run/docker.sock`
+
+### Using Podman
+
+On Linux, Homarr can connect to Podman's [Docker-compatible API](https://docs.podman.io/en/latest/markdown/podman-system-service.1.html).
+The Podman API socket must be running and mounted into the Homarr container.
+The socket grants full access to Podman, including arbitrary code execution as the user running the API, so only mount it into trusted containers.
+
+For rootless Podman, enable the socket for the user that runs Homarr:
+
+```bash
+systemctl --user enable --now podman.socket
+```
+
+The rootless socket is located at `$XDG_RUNTIME_DIR/podman/podman.sock` (usually `/run/user/<uid>/podman/podman.sock`).
+You can confirm the path with:
+
+```bash
+podman info --format '{{.Host.RemoteSocket.Path}}'
+```
+
+Mount that socket into the Homarr container and point `DOCKER_SOCKET_PATHS` to its path **inside** the container:
+
+```yaml
+services:
+  homarr:
+    container_name: homarr
+    image: ghcr.io/homarr-labs/homarr:latest
+    restart: unless-stopped
+    volumes:
+      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
+      - ./homarr/appdata:/appdata
+    environment:
+      SECRET_ENCRYPTION_KEY: your_64_character_hex_string
+      DOCKER_SOCKET_PATHS: /var/run/podman.sock
+    ports:
+      - "7575:7575"
+```
+
+Start Homarr with `podman compose up -d`.
+Run the compose project as the same user that owns the rootless Podman socket so `$XDG_RUNTIME_DIR` resolves to the correct path.
+To keep the user socket available after logout and across reboots, enable lingering with `loginctl enable-linger <user>`.
+
+For rootful Podman, enable the system socket with `sudo systemctl enable --now podman.socket`.
+Its default path is `/run/podman/podman.sock`; mount that path instead and start Homarr with `sudo podman compose up -d`.
+
+:::note SELinux
+On systems with SELinux enabled, Podman's documentation recommends disabling label separation for a container that accesses the API socket.
+Add the following to the Homarr service:
+
+```yaml
+security_opt:
+  - label=disable
+```
+
+:::
+
+You can connect Homarr to multiple Docker-compatible sockets by mounting each socket and listing their in-container paths, separated by commas:
 
 ```yaml
 services:
@@ -27,106 +117,120 @@ services:
     image: ghcr.io/homarr-labs/homarr:latest
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock
-      - ./homarr/appdata:/appdata
+      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
+    environment:
+      DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
 ```
 
-`/var/run/docker.sock` is the default. For other in-container paths, set a comma-separated list:
+### Managing your Docker containers within Homarr
+
+Homarr allows you to interact with Docker containers running on your system.
+Each container row has an action menu with the following options:
+
+- **View logs** - opens a dedicated logs page with a live terminal
+- **Start** - start a stopped container
+- **Stop** - stop a running container
+- **Restart** - restart a container
+- **Remove** - remove a container
+- **Add to Homarr** - create a bookmark app from the container
+
+You can also search and filter containers by **container** or **image** name:
+
+![Container and Image Search](img/container-and-image-search.png)
+
+#### Viewing container logs
+
+You can view the real-time logs of any container by selecting **View logs** from the row action menu.
+This opens a dedicated page with an xterm.js terminal that streams the container's log output.
+
+#### CPU and Memory columns
+
+The Docker management table supports optional **CPU usage** and **Memory usage** columns.
+These columns are hidden by default and can be toggled on from the table column visibility settings.
+
+#### Add apps from containers
+
+Homarr also lets you add apps from containers. You can simply select all containers you want to add an app for and then click the `Add to Homarr` button.
+This will open a dialog where you can specify the web addresses for all of them:
+
+![Dialog for addding apps to Homarr](img/add-to-homarr-dialog.png)
+
+Once you've changed the web addresses, click the `Add` button to add the apps to Homarr.
+They are then available in the app list and can be used as normally added apps.
+
+![Apps added from containers](img/add-to-homarr-apps.png)
+
+### Configuration
+
+Currently Homarr supports one label for configuration of the containers:
+
+- **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
+
+### Security
+
+Mounting docker sockets can be risky, as they permit full control over your docker service.
+As an example, a thread actor could abuse Homarr use the socket to start, stop or delete containers on your system.
+
+Therefore we recommend the usage of a socket proxy, which can prohibit certain actions.
+A few examples include:
+
+- https://github.com/linuxserver/docker-socket-proxy
+- https://github.com/Tecnativa/docker-socket-proxy
+
+See documentation of the respective proxies on how to configure them.
+Homarr may behave in unexpected ways when you use proxies.
+
+#### Permissions
+
+Homarr needs the following permissions from the Docker API:
+
+- Containers/Start
+- Containers/Stop
+- Containers/Restart
+- Containers/Remove
+
+For socket proxies, you will need these permissions:
+
+- `CONTAINERS=1`
+- `POST=1`
+
+**Caution:** `POST` access is security critical as it provides extensive capabilities to modify your docker environment. Please leave it disabled if you're concerned about this.
+
+As a workaround, you can use [LSIO's socket proxy](https://github.com/linuxserver/docker-socket-proxy) and set the following:
+
+- ALLOW_START=1
+- ALLOW_STOP=1
+- ALLOW_RESTARTS=1
+
+These will work even with `POST=0`.
+
+You lose the ability to remove containers, but start, stop and restarts should work just fine.
+
+#### Connecting to Docker via Socket Proxies
+
+To connect to Docker via a socket proxy, you'll need to add these two environment variables in the compose file:
+
+- `DOCKER_HOSTNAMES=<name of the socket proxy container>`
+- `DOCKER_PORTS=<socket proxy port, usually 2375>`
+
+Refer: https://homarr.dev/docs/advanced/environment-variables/
+
+You will also need to add Homarr to the network of your socket proxy. You can do it like this:
+
+1. Add the network to your compose file (with appropriate changes):
 
 ```yaml
-environment:
-  DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
+networks:
+  socket-proxy:
+    name: socket-proxy # <--- change this to the name of the network as set up by the socket proxy
+    external: true
 ```
 
-## Podman
-
-Homarr uses Podman's Docker-compatible API. Start the Podman socket, mount it, and include its in-container path in
-`DOCKER_SOCKET_PATHS`.
-
-For rootless Podman:
-
-```sh
-systemctl --user enable --now podman.socket
-podman info --format '{{.Host.RemoteSocket.Path}}'
-```
-
-Run Homarr as the user that owns the socket. On SELinux systems, Podman may require `security_opt: [label=disable]` for
-the Homarr container. Rootful Podman normally exposes `/run/podman/podman.sock`.
-
-## Remote endpoints
-
-For Docker socket proxies, list aligned hostnames and ports:
+2. Add the network to the homarr service in the compose file:
 
 ```yaml
-environment:
-  DOCKER_HOSTNAMES: docker-proxy-home,docker-proxy-lab
-  DOCKER_PORTS: 2375,2375
+networks:
+  - socket-proxy
 ```
 
-:::warning Plaintext Docker API
-
-Unauthenticated Docker TCP provides control of the Docker host. Keep a socket proxy on a private network or use TLS.
-
-:::
-
-Use `DOCKER_ENDPOINTS` for named endpoints, TLS, or restricted capabilities:
-
-```yaml
-environment:
-  DOCKER_ENDPOINTS: >-
-    [
-      {
-        "id": "local",
-        "name": "Local Docker",
-        "kind": "docker",
-        "transport": { "type": "socket", "path": "/var/run/docker.sock" },
-        "capabilities": ["inventory", "logs", "lifecycle", "remove"]
-      },
-      {
-        "id": "production",
-        "name": "Production inventory",
-        "kind": "docker",
-        "transport": {
-          "type": "tls",
-          "host": "docker.example.com",
-          "port": 2376,
-          "caPath": "/run/secrets/docker-ca.pem"
-        },
-        "capabilities": ["inventory", "logs"]
-      }
-    ]
-```
-
-Each endpoint requires a stable `id`, display `name`, `kind` (`docker` or `podman`), transport, and the `inventory`
-capability. Optional capabilities are `logs`, `lifecycle`, and `remove`.
-
-| Transport | Required values                                                                     |
-| --------- | ----------------------------------------------------------------------------------- |
-| `socket`  | Absolute in-container `path`                                                        |
-| `tls`     | `host`, `port`, absolute `caPath`; optional `certPath` and `keyPath` for mutual TLS |
-| `tcp`     | `host`, `port`, and `allowInsecure: true`                                           |
-
-`DOCKER_ENDPOINTS` takes precedence over the socket, hostname, and port lists.
-
-## Use in Homarr
-
-The Docker management page lists containers from every configured endpoint and can show logs, resource use, and
-permitted lifecycle actions. The Docker widget can include all endpoints or a selected subset.
-
-Assisted setup compares discovered containers with existing apps and integrations. Discovery is read-only; creating or
-updating a Homarr resource still requires confirmation. If one endpoint is unavailable, containers from healthy
-endpoints remain visible.
-
-The `homarr.hide` label excludes a container. Other `homarr.*` labels can provide apps, integrations, groups, and widgets
-during onboarding; see [Docker label discovery](../docker-labels).
-
-## Security
-
-A Docker or Podman socket grants extensive host control. Prefer a least-privilege socket proxy when lifecycle access is
-not required.
-
-Homarr needs `CONTAINERS=1` for inventory and `POST=1` for standard lifecycle actions with common proxies. LSIO's proxy
-can instead expose `ALLOW_START=1`, `ALLOW_STOP=1`, and `ALLOW_RESTARTS=1` while keeping `POST=0`; removal is then
-unavailable.
-
-Add Homarr to the proxy's Docker network and configure its service name and port with `DOCKER_HOSTNAMES` and
-`DOCKER_PORTS`.
+3. Finally, if it is present, remove the default docker socket connection under `volumes` in the homarr service.

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

@@ -8,6 +8,7 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IconZoomQuestion, IconChartBar, IconSearch } from "@tabler/icons-react";
 import { icalIntegration } from ".";
 import { calendarWidget } from "@site/docs/widgets/calendar";
 
@@ -38,5 +39,6 @@ import { calendarWidget } from "@site/docs/widgets/calendar";
   ]}
 />
 
-The integration accepts any public iCal URL, including calendars published by Google Calendar, Apple Calendar, and
-Outlook.
+## Using the iCal integration
+
+The iCal integration allows you to add external calendars to Homarr. Any calendar that provides a public iCal URL can be integrated, such as Google Calendar, Apple Calendar, or Outlook.

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

@@ -1,6 +1,6 @@
 ---
 title: "Immich"
-description: "Self-hosted photo and video management."
+description: "Self-hosted photo and video management solution"
 hide_title: true
 ---
 
@@ -14,7 +14,7 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
 
 <IntegrationHeader integration={immichIntegration} categories={["Photo server"]} />
 
-### Widgets and capabilities
+### Widgets & Capabilities
 
 <IntegrationCapabilites items={[{ widget: immichAlbumCarouselWidget }, { widget: immichServerStatsWidget }]} />
 
@@ -24,16 +24,34 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
 
 ### Secrets
 
-Create an API key under **Immich user settings → API Keys** with these permissions:
+<IntegrationSecrets secrets={[{
+  credentials: ['apiKey'],
+  steps: [
+    'Navigate to your Immich instance', 
+    'Open your account settings or navigate to https://YOUR_IMMICH/user-settings', 
+    'Scroll down to "API Keys"', 
+    'Click "New API Key"', 
+    'Enter a name, e.g. "Homarr"', 
+(
 
-`album.statistics`, `album.read`, `album.create`, `user.read`, `user.update`, `asset.read`, `asset.view`,
-`asset.download`, `asset.statistics`, `server.statistics`, and `server.about`.
+  <span>
 
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["apiKey"],
-      steps: ["Create the API key in Immich and copy its value into the Homarr integration."],
-    },
-  ]}
-/>
+    Select the following permissions:{" "}
+    <code>album.statistics</code>,{" "}
+    <code>album.read</code>,{" "}
+    <code>album.create</code>,{" "}
+    <code>user.read</code>,{" "}
+    <code>user.update</code>,{" "}
+    <code>asset.read</code>,{" "}
+    <code>asset.view</code>,{" "}
+    <code>asset.download</code>,{" "}
+    <code>asset.statistics</code>,{" "}
+    <code>server.statistics</code>,{" "}
+    <code>server.about</code>.
+
+  </span>
+
+),
+'Create the integration in Homarr and copy the API key to there'
+]
+}]} />

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

@@ -1,44 +1,58 @@
 ---
 title: "Kubernetes"
-description: "Read Kubernetes resources and cluster metrics in Homarr."
+description: "Kubernetes is a powerful container orchestration platform that automates the deployment, scaling, and management of containerized applications."
 hide_title: true
 ---
 
 import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
+import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IconBrandDocker, IconTool } from "@tabler/icons-react";
 import { kubernetesIntegration } from ".";
 
 <IntegrationHeader integration={kubernetesIntegration} categories={["Containers"]} />
 
-Homarr provides a read-only view of pods, services, ingresses, nodes, ConfigMaps, Secrets, namespaces, and volumes.
-Metrics Server is optional; without it, inventory and reserved capacity remain available but live CPU and memory do not.
+Homarr provides a user-friendly Kubernetes dashboard that offers an overview of your cluster’s resources in a clear and structured interface. It allows users to view key Kubernetes objects, including `Pods`, `Services`, `Ingresses`, `Nodes`, `ConfigMaps`, `Secrets`, `Namespaces`, and `Volumes`, as well as basic metrics when the Kubernetes Metrics Server is enabled.
 
-## In-cluster access
+:::warning[Read only]
+This integration is read-only, meaning Homarr does not modify or manage cluster resources but serves as an informational tool to enhance visibility into your Kubernetes environment.
+:::
 
-Enable RBAC in the Homarr Helm values:
+![Dashboard](img/dashboard.jpeg)
+
+### Prerequisites
+
+Before deploying Homarr in Kubernetes, ensure the following prerequisites are met:
+
+- Kubernetes (Version >= 1.24.0)
+- Metrics Server ([Install from here](https://github.com/kubernetes-sigs/metrics-server))
+- RBAC Enabled (Required for Homarr Helm chart)
+
+### Configuring RBAC in Helm Chart
+
+To enable RBAC for Homarr, configure the Helm chart values file as follows:
 
 ```yaml
 rbac:
   enabled: true
 ```
 
-The chart creates the service account and read-only Role/ClusterRole bindings used by Homarr. Kubernetes 1.24 or newer is
-required.
+:::tip[What Does rbac.enabled Do?]
+Enabling RBAC in the Helm chart creates the necessary Kubernetes Role-Based Access Control (RBAC) resources to allow Homarr to view various Kubernetes objects. These include:
 
-## Kubeconfig contexts
+- Service Account: A dedicated service account for Homarr.
+- Role & RoleBinding: Grants permissions within a specific namespace to list, watch, and get pods, services, secrets, configmaps, and more.
+- ClusterRole & ClusterRoleBinding: Extends the same permissions cluster-wide for additional flexibility.
+  :::
 
-When Homarr runs outside the cluster, mount a kubeconfig read-only and set `KUBECONFIG` to its in-container path:
+### Homarr Dashboard Overview
 
-```yaml
-services:
-  homarr:
-    volumes:
-      - ./kubeconfig:/app/config/kubeconfig:ro
-    environment:
-      KUBECONFIG: /app/config/kubeconfig
-```
+Once deployed, Homarr provides a dashboard displaying Kubernetes metrics and resource information. The main page includes:
 
-The management page exposes every configured context. An unavailable context does not hide healthy contexts; a context
-without Metrics Server is marked **Metrics unavailable**.
-
-Kubernetes resources are not converted into Homarr apps or integrations during Docker discovery.
+- Pods: Lists running and pending pods.
+- Services: Shows available services and their configurations.
+- Ingresses: Displays ingress rules and associated routes.
+- Nodes: Provides an overview of cluster nodes and their status.
+- ConfigMaps & Secrets: Lists configuration data and secrets used within the cluster.
+- Namespaces: Displays all available namespaces in the cluster.
+- Volumes: Shows persistent and ephemeral storage resources.

apps/docs/docs/integrations/opnsense/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "OPNsense"
-description: "Open-source firewall and routing platform."
+description: "OPNsense is an open-source, easy-to-use, and easy-to-build firewall and routing platform."
 hide_title: true
 ---
 
@@ -8,14 +8,22 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IconHeartRateMonitor } from "@tabler/icons-react";
 import { opnsenseIntegration } from ".";
+import Alert from "@theme/Admonition";
 import { firewallWidget } from "../../widgets/firewall";
 
 <IntegrationHeader integration={opnsenseIntegration} categories={["Firewall"]} />
 
-### Widgets and capabilities
+### Widgets & Capabilities
 
-<IntegrationCapabilites items={[{ widget: firewallWidget }]} />
+<IntegrationCapabilites
+  items={[
+    {
+      widget: firewallWidget,
+    },
+  ]}
+/>
 
 ### Adding the integration
 
@@ -23,18 +31,44 @@ import { firewallWidget } from "../../widgets/firewall";
 
 ### Secrets
 
-Use a dedicated API-only user with **Lobby: Dashboard** and **Reporting: Traffic** privileges.
-
 <IntegrationSecrets
   secrets={[
     {
-      tabLabel: "API key and secret",
+      tabLabel: "ApiKey (Key & Secret)",
       credentials: ["opnsenseApiKey", "opnsenseApiSecret"],
+      header: (
+        <Alert type="info">
+          This integration does not require full API access to the firewall. The following guide outlines the process
+          for creating a restricted OPNsense user with a scrambled password, designed exclusively for API access. This
+          ensures minimal permissions and prevents local login capability.
+        </Alert>
+      ),
       steps: [
-        "Under System → Access → Users, create a user with Scrambled Password enabled.",
-        "Grant Lobby: Dashboard and Reporting: Traffic privileges, then save the user.",
-        "Use the ticket action for that user and confirm the API key download.",
-        "Copy the downloaded key and secret into Homarr.",
+        "Log in to the OPNsense web interface as an administrator",
+        "Navigate to System → Access → Users",
+        "Click the + (Add) button to create a new user",
+        <>
+          Fill in the user details:
+          <ul>
+            <li>Username: Enter a unique name</li>
+            <li>Password: Leave empty</li>
+            <li>Scrambled Password: Enable this option</li>
+            <li>Full name: (Optional) Add a descriptive name</li>
+          </ul>
+        </>,
+        <>
+          In Privileges section → Select the option below:
+          <ul>
+            <li>Lobby: Dashboard</li>
+            <li>Reporting: Traffic</li>
+          </ul>
+        </>,
+        "Click Save",
+        "Return to the Users list",
+        "Find the user and click the ticket icon in the Commands column",
+        "Click Yes in the popup to confirm",
+        "A txt file will download automatically, containing: Key and Secret",
+        "Save this file securely—this information will only be shown once",
       ],
     },
   ]}

apps/docs/docs/integrations/pi-hole/index.mdx

@@ -8,6 +8,7 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IconAd, IconDeviceGamepad } from "@tabler/icons-react";
 import Alert from "@theme/Admonition";
 import { dnsHoleSummaryWidget } from "@site/docs/widgets/dns-hole-summary";
 import { dnsHoleControlsWidget } from "@site/docs/widgets/dns-hole-controls";
@@ -43,7 +44,7 @@ import { piHoleIntegration } from ".";
     {
       credentials: ["apiKey"],
       steps: [],
-      body: "Pi-hole v6 uses a password or application password instead of an API key. Prefer an application password.",
+      body: "Please note, that in v6 of Pi-hole you no longer specify an API key, but instead either a password or application password. We suggest to use the application password when possible.",
     },
     {
       credentials: [],

apps/docs/docs/integrations/proxmox/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Proxmox"
-description: "Virtual machines and containers managed by Proxmox VE."
+description: "Proxmox is a powerful open-source virtualization platform that allows you to run virtual machines and containers."
 hide_title: true
 ---
 
@@ -8,12 +8,15 @@ import { IntegrationHeader } from "@site/src/components/integrations/header";
 import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
 import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
+import { IconHeartRateMonitor } from "@tabler/icons-react";
 import { proxmoxIntegration } from ".";
+import Alert from "@theme/Admonition";
 import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
+import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
 
 <IntegrationHeader integration={proxmoxIntegration} categories={["System monitoring"]} />
 
-### Widgets and capabilities
+### Widgets & Capabilities
 
 <IntegrationCapabilites items={[{ widget: healthMonitoringWidget }]} />
 
@@ -23,23 +26,81 @@ import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
 
 ### Secrets
 
-Use a Proxmox VE (`pve`) user and API token with the `PVEAuditor` role at `/` and **Propagate** enabled. PAM
-authentication may not work with the API.
-
 <IntegrationSecrets
   secrets={[
     {
+      header: (
+        <Alert type="caution">
+          The Proxmox API may not work with Linux PAM standard authentication. It is strongly recommended to use the
+          Proxmox VE authentication server realm when creating your API user.
+        </Alert>
+      ),
       credentials: ["username", "tokenId", "realm", "apiKey"],
       steps: [
-        "Create a Proxmox VE user or group and grant PVEAuditor at / with Propagate enabled.",
-        "Create an API token for that user. Disable privilege separation to inherit the user permission, or grant the token the same PVEAuditor permission.",
-        "Copy the token secret when Proxmox displays it and enter the user, realm, token ID, and secret in Homarr.",
+        "Navigate to the Proxmox portal, click on Datacenter",
+        "Expand Permissions, click on Groups",
+        "Click the Create button",
+        "Name the group something informative, like api-users",
+        "Click on the Permissions 'folder'",
+        <>
+          Click Add {"->"} Group Permission
+          <ul>
+            <li>Path: /</li>
+            <li>Group: group from Step 4 above</li>
+            <li>Role: PVEAuditor</li>
+            <li>Propagate: Checked</li>
+          </ul>
+        </>,
+        "Expand Permissions, click on Users",
+        <>
+          Click the Add button
+          <ul>
+            <li>User name: something informative like api</li>
+            <li>Realm: Proxmox VE authentication server</li>
+            <li>Password: create a secure password for the user</li>
+            <li>Confirm Password: re-enter the password</li>
+            <li>Group: group from Step 4 above</li>
+          </ul>
+        </>,
+        "Expand Permissions, click on API Tokens",
+        <>
+          Click the Add button
+          <ul>
+            <li>User: user from Step 8 above</li>
+            <li>Token ID: something informative like the application or purpose like homarr</li>
+            <li>Privilege Separation: unchecked</li>
+          </ul>
+        </>,
+        "Copy the Secret that is shown in Step 10 because it is only shown once",
+        "Go back to the 'Permissions' menu",
+        <>
+          Click Add {"->"} API Token Permission
+          <ul>
+            <li>Path: /</li>
+            <li>API Token: select the API token created in Step 10</li>
+            <li>Role: PVE Auditor</li>
+            <li>Propagate: Checked</li>
+          </ul>
+        </>,
       ],
       body: (
-        <p>
-          For <code>api@pve!homarr</code>, use username <code>api</code>, realm <code>pve</code>, and token ID{" "}
-          <code>homarr</code>.
-        </p>
+        <>
+          <span>
+            Sometimes you'll also find the <code>api@pve!homarr</code> format, within Homarr you'll have to split it up
+            into:
+          </span>
+          <ul>
+            <li>
+              <b>Username:</b> api
+            </li>
+            <li>
+              <b>Realm:</b> pve
+            </li>
+            <li>
+              <b>Token ID:</b> homarr
+            </li>
+          </ul>
+        </>
       ),
     },
   ]}

apps/docs/docs/integrations/truenas/index.mdx

@@ -19,6 +19,8 @@ import Alert from "@theme/Admonition";
 
 <IntegrationCapabilites items={[{ widget: healthMonitoringWidget }, { widget: systemResourcesWidget }]} />
 
+The storage values shown by these widgets come from each pool's root ZFS dataset, so they already account for RAIDZ parity overhead and dataset limits and match what `zfs list` and the TrueNAS web interface report. When a pool cannot report its dataset space, Homarr falls back to the pool's physical values, which read higher on RAIDZ.
+
 ### Adding the integration
 
 <AddingIntegration />

apps/docs/docs/management/api/index.mdx

@@ -6,74 +6,93 @@ tags:
   - Interface
 ---
 
-Homarr exposes OpenAPI and tRPC endpoints for automation. Open the generated specification under
-**Management → Tools → API** or use the [interactive API reference](/api-reference).
+Using the Homarr API, you can interface with the application with your own code and business logic.
+It enables you to trigger almost all actions that you can perform from the Homarr UI.
+With the API, you can build resilient systems that automatically update Homarr with data - for example syncing it with
+your deployments in a cluster or dynamically adding integrations depending on how many replicas you run.
 
-![Homarr's API documentation page](../img/api.png)
+This page is language-neutral, and you must implement the API on your own in your desired language.
+It requires you to know your programming language well and have a basic understanding of HTTP, JSON and networking.
+You can test out API endpoints using any OpenAPI client - for example [Yaak](https://yaak.app/).
+
+## Opening the API specification
+
+The specification is implemented according to the OpenAPI standard.
+To access the documentation, you'll need to spin up an instance of Homarr.
+Navigate to `Management` > `Tools` > `API`.
+You can copy the JSON url into your OpenAPI client or try out the endpoints directly from your browser.
+
+Alternatively, you can [open the full interactive API reference](/api-reference) directly in your browser.
 
 ## Authentication
 
-Create an API key from the **Authentication** tab. Its value has the form `<id>.<token>` and is shown once.
+Many endpoints will require you to authenticate. At the top of the API reference, you'll find a button to authenticate yourself with an API key.
+You can obtain API keys from the "Authentication" tab at the top of the page.
+API keys will not expire and can be used indefinitely.
 
-Send it in the `ApiKey` header:
+### API Key Format
 
-```sh
-curl -H 'ApiKey: <id>.<token>' https://homarr.example.com/api/health/live
+API keys are provided in the format `<id>.<token>`. When making requests, include the key in the `ApiKey` header:
+
+```
+ApiKey: abc123def456.xyz789tokenvalue...
 ```
 
-The same header authenticates tRPC requests under `/api/trpc`. Without a key, browser requests can use the Homarr
-session cookie.
+### Supported Endpoints
 
-API keys do not expire automatically and act as the user that created them. Every request uses that user's group and
-resource permissions.
+API key authentication works with both endpoint types:
 
-## Permission behavior
+| Endpoint Type | Path Pattern    | API Key Support |
+| ------------- | --------------- | --------------- |
+| OpenAPI       | `/api/...`      | ✅ Supported    |
+| tRPC          | `/api/trpc/...` | ✅ Supported    |
 
-Unauthorized operations return `FORBIDDEN`. List endpoints filter records on the server when resource-specific access
-applies.
+If no API key is provided, Homarr falls back to session cookie authentication (for browser-based access).
 
-App catalog endpoints such as `app.all`, `app.getPaginated`, and `app.search` require **Modify all apps** because they
-include internal URLs. Use `app.selectable` for the reduced board-picker fields.
+### Usage Examples
 
-Integration list and search endpoints return only integrations the key owner can access. Check each integration's
-`hasUseAccess` and `hasInteractAccess` fields before reading data or invoking actions.
+**OpenAPI endpoint:**
 
-## Board automation
-
-The API can create, duplicate, rename, delete, and configure boards; manage board content; and set desktop or mobile home
-boards.
-
-Each board has exactly one Mobile and one Base layout. Mobile uses breakpoint `0`; all breakpoints are unique. Custom
-layouts can use any other breakpoint, and Homarr selects the highest breakpoint that fits the viewport. Preserve layout
-roles and use the canonical layouts returned by save operations, including generated IDs.
-
-Creating or changing an integration-backed widget requires use access to each newly selected integration.
-
-## Docker targets
-
-Docker actions identify both the configured endpoint and the container:
-
-```json
-{
-  "targets": [{ "endpointId": "local", "id": "container-id" }]
-}
+```bash
+curl -H 'ApiKey: <id>.<token>' http://localhost:7575/api/health/live
 ```
 
-Read both values from `docker.getContainers` immediately before calling `docker.startAll`, `stopAll`, `restartAll`, or
-`removeAll`. The endpoint ID prevents collisions between Docker or Podman hosts.
+**tRPC endpoint:**
 
-`docker.getContainers` accepts optional `endpointIds`. Omit it or pass an empty array for every configured endpoint.
+```bash
+curl -H 'ApiKey: <id>.<token>' http://localhost:7575/api/trpc/app.all
+```
 
-## Partial upstream failures
+### Use Cases
 
-Queries that combine several integrations can return healthy data alongside failure metadata. The exact response shape
-depends on the endpoint; inspect the generated schema instead of assuming a common `error` field. When every selected
-integration fails, the query returns an error.
+API key authentication enables programmatic access for:
 
-## Custom Widget resources
+- Automation scripts and CI/CD pipelines
+- Third-party integrations
+- Custom dashboards and monitoring tools
+- Container orchestration systems that need to sync app definitions
 
-Authenticated administrators can retrieve the current Custom Widget authoring prompt, schema, component catalog, skill,
-and focused references under `/api/custom-widgets/`.
+## Board Automation
 
-Use [Custom Widget agent authoring](../custom-widgets/agent-authoring) for the lifecycle and
-[MCP](../mcp) when the client supports Model Context Protocol.
+The OpenAPI and MCP APIs include board management endpoints for common automation workflows:
+
+- Create, duplicate, rename and delete boards
+- Change board visibility
+- Update board visual and behavior settings
+- Set desktop and mobile home boards for the current user
+- Configure global board defaults such as public home boards and status behavior
+
+Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
+
+## Get Custom Widget authoring resources
+
+Custom JSX v2 provides four HTTP discovery endpoints:
+
+- `GET /api/custom-widgets/authoring-prompt` returns the current prompt plus MCP and HTTP resource identifiers.
+- `GET /api/custom-widgets/schema` returns the canonical widget JSON Schema.
+- `GET /api/custom-widgets/components` returns the release-matched static component catalog.
+- `GET /api/custom-widgets/skill` returns the concise live `SKILL.md` plus skills.sh, source, and install metadata. Retrieve the schema, component catalog, and examples through their dedicated resources only when needed.
+
+Call `customWidget_configurationRequestUser` to create a temporary API source setup URL where the user can confirm their server URL and enter credentials. Do not construct or save this URL.
+
+Authenticated tRPC and MCP procedures support definition management, validation, previews, template patches, and credential writes. An exported definition does not contain credentials.

apps/docs/docs/management/apps/index.mdx

@@ -7,39 +7,50 @@ tags:
   - Ping
 ---
 
-import { AppFlowDiagram } from "@site/src/components/pages/core-concepts/technical-diagrams";
+Apps are the building blocks of your Homarr board.
+Most of the time they are a simple link to a website, but used on your board they also support a simple ping to check if your service is up.
+Apps are used in the bookmark and app widget.
 
-An **app** is a saved shortcut used by the App and Bookmarks widgets. It contains a name, destination, icon, and
-optional status-check address.
+## Create an app
 
-![The Apps management page](../img/apps.png)
+To create an app you can click on the button on the top right of the apps management page:
 
-## How an app is used
+![New app button](./img/new-app-button.png)
 
-<AppFlowDiagram />
+Next, you'll need to fill out the required fields to configure the app:
 
-## Configuration
+![New app form](./img/new-app-form.png)
 
-Create and manage apps under **Management → Apps**.
+### Name
 
-| Field       | Purpose                                                                                  |
-| ----------- | ---------------------------------------------------------------------------------------- |
-| Name        | Label shown on the board                                                                 |
-| Icon URL    | Direct image URL, icon-library result, or uploaded image                                 |
-| Description | Optional tooltip                                                                         |
-| URL         | Destination opened from the board; custom URI schemes are supported except `javascript:` |
-| Ping URL    | Optional HTTP(S) address used for status checks when it differs from the destination     |
+The name must be at least one character long and can be chosen freely.
 
-An app can be linked to an [integration](../integrations). Integration widgets then use the app as their destination
-when they provide a link to the service.
+### Icon URL
 
-See [Icons](/docs/advanced/icons) for icon sources and uploads.
+This is the URL to the icon that will be displayed on the app widget.
+You can paste a direct HTTP(S) URL to an image, search the included icon repositories by name, or upload a local file through the upload button. The app name is pre-filled as the initial library search when no image is selected. Local images appear first, followed by SVG icons and other formats. Direct image URLs are previewed, used as entered, and are not searched in the icon repositories.
 
-## Permissions
+![Icon URL](./img/app-icon-url.png)
 
-- `app-create` creates apps.
-- `app-modify-all` lists and edits every app.
-- `app-full-all` also deletes and uses every app.
-- `app-use-all` allows using every app on boards without granting management access.
+### Description
 
-Users with only `app-create` can open the page and create an app, but do not receive the existing app list.
+An optional description that can be shown as tooltip on the app widget.
+
+### URL
+
+The URL to the website you want to link to. Clicking on the app widget or bookmark will open this URL.
+
+You can also use custom URI schemes such as `vscode://file/path`, `microsoft-edge:https://example.com`, or `myapp://open` to link to local applications or third-party programs. We trust that you know what you are doing — only `javascript:` URIs are blocked for security reasons.
+
+### Ping URL
+
+When you want to use another url for the simple status check you can set it here.
+This will allow you to set a different URL for the ping than the URL that is opened when clicking on the app widget.
+It's useful when you want to ping the service internally for example with a custom ip but open the website externally.
+Note that the ping URL only accepts `http://` and `https://` URLs — custom URI schemes are not supported for pings.
+
+## List of apps
+
+On the apps management page you find all apps that exist in your Homarr instance. You can edit and delete them.
+
+![Apps list](./img/app-list.png)

apps/docs/docs/management/assistant.mdx

@@ -1,58 +0,0 @@
----
-description: Configure and use Assistant.
-tags:
-  - Assistant
-  - AI
-  - Administration
----
-
-import { AssistantFlowDiagram } from "@site/src/components/pages/core-concepts/technical-diagrams";
-
-# Assistant
-
-Assistant answers questions and operates Homarr through the signed-in user's permissions. Read-only tools can run
-automatically; changes require approval by default.
-
-![The Assistant management page](./img/assistant.png)
-
-## Request flow
-
-<AssistantFlowDiagram />
-
-## Configuration
-
-Under **Management → Assistant**, select a provider, configure its API URL and key when required, select the default
-model, and enable Assistant. Users can choose another available model for a conversation.
-
-Provider presets cover common APIs. **Custom endpoint** accepts an OpenAI-compatible Chat Completions API. For a model
-server outside the Homarr container, use a hostname that the container can resolve instead of `localhost`.
-
-The [Homarr provider](../workshop/homarr-provider) is available through the Community Workshop without an administrator
-API key and has a daily request allowance.
-
-## Access
-
-Open Assistant from the user menu, with `Shift+A`, from search with `Cmd/Ctrl+/`, or through the
-[Assistant widget](../widgets/assistant).
-
-Assistant can work with boards, apps, integrations, widgets, Custom Widgets, and supported connected services. Mention
-Homarr resources with `@`; the model loads additional live context only when needed.
-
-Conversations are stored per user and can be searched, renamed, exported, or deleted.
-
-## Permissions and data
-
-- Every tool call uses the current user's Homarr permissions.
-- Automatic approvals apply only to the current conversation and reset when switching conversations.
-- Provider keys and custom headers are encrypted and are not returned to the browser.
-- Prompts, attachments, tool definitions, and tool results are sent to the selected model provider.
-
-See [MCP](./mcp) to connect an external AI client and
-[Custom Widget agent authoring](./custom-widgets/agent-authoring) for widget generation.
-
-## Troubleshooting
-
-- **No models found:** check the API URL, discovery path, and API key, or enter a model ID manually.
-- **Assistant is unavailable:** enable it and save the configuration.
-- **Tool calls stop:** use a model that supports streaming and tool calls.
-- **Local endpoint is unreachable:** check container DNS, routing, and the model server's listen address.

apps/docs/docs/management/backup.mdx

@@ -6,34 +6,71 @@ tags:
   - Data
 ---
 
-# Backup and restore
+# Backup & Restore
 
-Administrators using SQLite can export and restore the complete Homarr database under
-**Management → Tools → Backup**. MySQL and PostgreSQL installations must use their database-native backup tools.
+Homarr provides a built-in backup and restore system for **SQLite** instances. You can export your entire database - including apps, integrations, boards, users, and encryption keys - as a ZIP archive, and restore it on the same or a different Homarr instance.
 
-![The Backup and restore management page](./img/backup.png)
+:::warning
 
-## Export
+Backup and restore is only available when using the **SQLite** database driver. MySQL and PostgreSQL instances do not show this page.
 
-The ZIP contains:
+:::
 
-| File            | Contents                                                    |
-| --------------- | ----------------------------------------------------------- |
-| `db.sqlite`     | Apps, integrations, boards, users, settings, and other data |
-| `metadata.json` | Homarr version, backup timestamp, and encryption metadata   |
+## Accessing the Backup Page
 
-Export requires typing `I understand`. Store the ZIP as sensitive data: it contains the database and the material
-needed to restore encrypted integration credentials.
+Navigate to `Management` → `Tools` → `Backup`. You must have **admin** permissions to access this page.
 
-## Restore
+## Exporting a Backup
 
-Select a Homarr backup ZIP. The browser previews entity counts, board names, and required database migrations before
-the archive is uploaded.
+Click the **Export** button in the export card. You'll be prompted to type `I understand` to confirm. Once confirmed, a ZIP file downloads containing:
 
-Restoring replaces the current SQLite database and cannot be undone. After a successful restore, the Next.js process
-restarts and the page reloads when Homarr is ready.
+| File            | Description                                                         |
+| --------------- | ------------------------------------------------------------------- |
+| `db.sqlite`     | Full SQLite database with all entities                              |
+| `metadata.json` | Backup metadata: Homarr version, creation timestamp, encryption key |
 
-A backup can be restored on another Homarr instance. When its `SECRET_ENCRYPTION_KEY` differs, Homarr re-encrypts stored
-integration secrets for the target instance. Version metadata is used to apply compatible migrations.
+The backup contains the complete database. It includes Custom Widgets and all other Homarr configuration.
 
-The same restore flow is available during first-run onboarding, before the target database contains user data.
+## Restoring a Backup
+
+### 1. Upload
+
+Drag and drop or select a `.zip` backup file. The import card validates that the file contains a valid `db.sqlite` and metadata.
+
+### 2. Preview
+
+Before restoring, Homarr uses **sql.js WASM** to analyze the backup directly in your browser. You'll see:
+
+- **Entity counts** - how many apps, integrations, boards, users, etc. are in the backup
+- **Board names** - which boards will be restored
+- **Migration status** - Drizzle migrations are applied in-browser with a visual timeline showing each migration step
+
+### 3. Confirm
+
+Type `I understand` to acknowledge that restoring will replace your current database. This cannot be undone.
+
+### 4. Restore
+
+The backup ZIP is sent to the server, validated, and applied. After a successful restore:
+
+- **The Next.js server restarts automatically** to reload the new database state
+- Nginx and Redis (if running in Docker) stay up - only the Next.js process restarts
+- The page reloads once the server is ready
+
+## Cross-Instance Restore
+
+You can restore a backup from one Homarr instance onto another. Homarr handles:
+
+- **Encryption key re-encryption** - If the target instance has a different `SECRET_ENCRYPTION_KEY`, integration secrets are decrypted with the old key and re-encrypted with the new one during import
+- **Version compatibility** - Backups include the Homarr version they were created with. Backward compatibility is maintained for older backup formats
+
+## Backup During Onboarding
+
+When setting up a new SQLite Homarr instance, the onboarding flow includes a **Restore from SQLite backup** step. You can upload a backup ZIP directly during onboarding to skip manual setup.
+
+## Security
+
+- Export requires admin permissions
+- The `I understand` confirmation dialog prevents accidental exports and overwrites
+- Backups contain encrypted integration secrets - they cannot be read without the `SECRET_ENCRYPTION_KEY`
+- Import only works on SQLite instances - the API routes refuse requests from MySQL/PostgreSQL instances

apps/docs/docs/management/boards/index.mdx

@@ -9,86 +9,287 @@ tags:
   - Layout
 ---
 
-import { BoardLayoutsDiagram } from "@site/src/components/pages/core-concepts/technical-diagrams";
+import iconColorImage from "./img/icon-color.png";
+import itemRadiusImage from "./img/item-radius.png";
+import layoutLargeImage from "./img/layout-large.png";
+import layoutMediumImage from "./img/layout-medium.png";
+import layoutSmallImage from "./img/layout-small.png";
 
-A **board** is a dashboard page containing apps, widgets, and Containers. Its name is unique and forms the board URL.
-Boards can be public or restricted to users and groups.
+Each dashboard is called a "board".
+You can create as many boards as you want.
+Boards can be restricted to user groups.
+A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/board).
+Other boards can be viewed by direct links (e.g. my-homarr.com/board/smart-home) or via the management pages.
 
-![The Boards management page](../img/boards.png)
+Names of boards must be unique because this will be used in the URL to load the desired board.
 
-Create, duplicate, open, and delete boards under **Management → Boards**. Press `Shift+C` from a board to open the
-board switcher.
+## Create a new board
 
-## Responsive layouts
+When creating a board, the availability of the board name will be checked for you.
 
-<BoardLayoutsDiagram />
+![](./img/create-board-modal.png)
 
-Mobile and Base are protected layouts. New boards use three Mobile columns; Base uses the column count selected at
-creation. Additional layouts use unique breakpoints. Homarr selects the layout with the highest breakpoint that fits
-the current viewport.
+### Name
 
-Tiles use fixed `200 × 200` logical-pixel cells with a `24px` gap. Homarr scales the complete layout to the available
-width instead of changing each widget's proportions. **Reset from Base** regenerates a Mobile or custom layout from the
-current Base layout.
+The name must not include any special characters and must be at least one character long.
+Underscores and hyphen-minus are allowed.
 
-### Containers and rails
+### Column count
 
-A **Container** groups apps, widgets, and nested Containers. It can have a label, collapse control, app-opening action,
-border color, and CSS classes.
+Homarr has a complex drag-and-drop system that can be used from the browser.
+The column count defines how many horizontal columns are available to drag and drop elements to.
 
-A **rail** reserves one to three columns at the left or right of a non-Mobile layout. Rails stay fixed while the page
-scrolls and store their contents separately for each layout.
+### Public
 
-## Edit a board
-
-Enter edit mode from the board header to add, move, resize, configure, or remove content. Save the board to persist the
-layout.
-
-- Drag from an item's inactive content area; Containers use their grip.
-- Hold `Ctrl` on Windows/Linux or `Cmd` on macOS to select several items.
-- Use **Move / resize item** for another canvas, rail, Container, or exact coordinates.
-- Keyboard users can focus a tile, press Enter or Space, then move with arrow keys or resize with Shift + arrow keys.
-- Press Escape during a pointer or touch interaction to restore the item to its previous position.
-
-The add-content menu can create an app, integration, widget, or Container without leaving the board.
+This will enable public access for everyone - regardless of whether they are logged in or not.
+This can be really useful if you want to have public boards in your company or for family and friends.
+Modifications for public boards must be allowed explicitly using user groups and their permissions.
 
 ## Board settings
 
-Board settings cover:
+You navigate to the board settings by clicking on these three dots:
 
-- **General:** page title, browser title, logo, and favicon.
-- **Layout:** responsive layouts, breakpoints, columns, and rails.
-- **Background:** image, attachment, size, and repeat behavior.
-- **Appearance:** colors, opacity, icon color, and item radius.
-- **Custom CSS:** styles applied only to the current board.
-- **Behaviour:** app status and widget context-menu behavior.
+![](./img/navigate-to-settings.png)
 
-See [Styling](/docs/advanced/styling) for board and global CSS.
+Alternatively, you can also navigate from the board page itself using the cog icon at the top right:
 
-Outside edit mode, widgets may expose an advanced view and a context menu for status, refresh, quick options, settings,
-and actions. Available controls depend on the widget and the user's board and integration permissions.
+![](./img/navigate-to-settings-2.png)
 
-## Access control
+All board settings are edited on a single page. Click the **Save changes** button in the save bar at the bottom to apply them, or **Discard** to restore the last saved values. The save bar only appears when you have unsaved changes. Access control and the Danger zone are independent sections and are applied immediately.
 
-Public boards are readable without signing in. Private boards require user, group, or global access.
+### General
 
-| Board access | View | Edit content and settings | Access control, rename, delete |
-| ------------ | ---- | ------------------------- | ------------------------------ |
-| View         | Yes  | No                        | No                             |
-| Modify       | Yes  | Yes                       | No                             |
-| Full         | Yes  | Yes                       | Yes                            |
+#### Page title
 
-Inherited access comes from group permissions. Resource-specific access can be granted from the board's access-control
-section.
+This is the title that will be visible at the top left in the navigation bar:
 
-Renaming a board changes its URL without a redirect. Deleting a board is permanent.
+![](./img/page-title.png)
 
-## Home boards
+This field is optional and Homarr will fall back to "Homarr" if nothing is set.
 
-A **home board** opens at `/` and `/boards`. Desktop and mobile home boards are separate from the responsive layouts
-inside a board.
+#### Meta title
 
-Defaults can be set for a user, group, or the whole server. User settings take priority, followed by matching groups,
-the `Everyone` group, and server defaults. Server-wide fallback boards must be public.
+This is the secondary title of the page that is not directly visible in the page itself.
+Browser will use it to set the title of tabs:
 
-See [Users and groups](../users) and [Server settings](../settings#boards).
+![](./img/meta-title.png)
+
+Homarr will fall back to the board name and a suffix if nothing is set.
+
+#### Logo image URL
+
+This is the URL that is used for the image at the top left.
+Homarr will fall back to the Homarr logo if nothing is set.
+
+#### Favicon image URL
+
+This is the URL that is used for the favicon in the tab title.
+Homarr will fall back to the Homarr logo if nothing is set.
+
+### Layout
+
+In this section you can configure the different responsive layouts. Depending on your screens width the layout will change.
+
+![](./img/layout-settings.png)
+
+On each element the position and size of items can be changed seperately.
+When adding a new layout the position and sizes will automatically be generated depending on the column count.
+When adding a new item / dynamic section that will always be 1x1 on each layout and placed on the first available position.
+
+#### Name
+
+The name of the layout can be choosen freely. It is only used for the management and will not be visible on the board.
+
+#### Column count
+
+Amount of columns for this layout. Defines how many items can be placed in a row. When changed it will automatically adjust the position and size of the items.
+
+#### Breakpoint
+
+Minimum width of the screen where the layout will be used.
+Once the minimum of the next layout is reached the layout will change.
+
+#### Preview
+
+<img src={layoutSmallImage} height={256} />
+<img src={layoutMediumImage} height={256} />
+<img src={layoutLargeImage} height={256} />
+
+### Background
+
+#### Background image URL
+
+Homarr can display a background image behind apps and widgets.
+This URL can be used to define what image should be shown.
+
+#### Background image attachment
+
+This defines whether the background should move when the user scrolls.
+
+#### Background image size
+
+This defines whether the background should cover the entire page (and possibly be cropped) or never be cropped but may not cover the entire page.
+
+#### Background image repeat
+
+This defines whether the background should be repeated if it cannot cover the entire page.
+This option can be useful if you have patterns that can be repeated easily (e.g. patterns):
+
+![](./img/background-repeat.png)
+
+### Appearance
+
+#### Primary color
+
+Color that can be chosen freely to give accents to active elements.
+
+#### Secondary color
+
+Color that can be chosen freely to give accents.
+
+#### Opacity
+
+Opacity of the colors.
+
+#### Icon color
+
+Change the color of your bookmark / app icons.
+
+<img src={iconColorImage} height={100} />
+
+#### Item radius
+
+Change the radius of your items / categories.
+
+<img src={itemRadiusImage} height={100} />
+
+### Custom CSS
+
+This is the field where you can enter custom CSS.
+The styling will only be applied on the respective board page.
+
+[See this guide on how to work with custom CSS](/docs/advanced/styling/).
+
+### Behaviour
+
+#### Disable app status
+
+This will disable the status check for apps.
+
+### Access control
+
+With the access control, you can permit a single user or a group to your board.
+The users and groups can have one of these three levels of access:
+
+| **Permission Level** | View board | Edit mode | Settings | Danger zone (eg. delete) |
+| -------------------- | ---------- | --------- | -------- | ------------------------ |
+| View board           | X          |           |          |                          |
+| Modify board         | X          | X         | X        |                          |
+| Full access          | X          | X         | X        | X                        |
+
+The permission level can only be changed after adding the user / group:
+
+![](./img/change-user-permission-level.png)
+
+If the board is private and the user is not added in any of the three tabs, they cannot access the board.
+They also do not see the board on the start page nor do they have access to any links for the board.
+
+Groups that have high permissions (e.g. administrator or all board permissions) will be shown as "inherited".
+They are permitted implicitly due to their permissions.
+
+After editing permissions, the save button below the table must be pressed.
+Otherwise, all changes will be discarded.
+
+### Danger zone
+
+#### Rename
+
+Renaming a board will break all existing links to it permanently with no redirect.
+
+#### Board visibility
+
+By default, boards will be private. This means only authenticated users that are authorized have access.
+Making a board public will expose it to everyone - including unauthenticated users.
+
+#### Delete
+
+This will permanently delete the board.
+This action is irreversible and cannot be undone.
+
+## Delete boards
+
+The deletion of boards is permanent and cannot be undone.
+There are two ways to delete a board:
+
+- Navigate to the settings of your board, open the "Danger zone" section and click on the "delete this board" button.
+- Navigate to the list of boards in the management pages, click the three dots and click on "delete permanently".
+
+Both actions will execute the same deletion process.
+
+## Duplicate boards
+
+:::note
+Duplicating a board will not copy the users and groups that have access to the board
+nor the integrations the user does not have access to.
+:::
+
+Duplicating a board will create a new board with the same settings and layout as the original board.
+You can duplicate a board by clicking on the three dots in the list of boards and selecting "Duplicate board".
+
+![](./img/duplicate-board-modal.png)
+
+## Setting boards as your home board
+
+The home board is the dashboard, that will be shown at the root path of Homarr or if no board name was passed in the URL.
+All the following paths will lead to the home board:
+
+- `my-homarr.com`
+- `my-homarr.com/boards`
+
+Your home board will have a special small badge at the top right in the list of boards:
+
+![](./img/home-board-flag.png)
+
+### For yourself
+
+To set the home board yourself, the easiest option is to set it directly in the list of boards:
+
+![](./img/set-as-home-board-menu.png)
+
+Alternatively, you can also define it via your user profile:
+
+1. Click on your user profile at the top right
+2. Click on `Your preferences`
+3. Change the home board in the `home board` dropdown and click on `Save`.
+
+### For other users
+
+1. Navigate to the users: `Management` > `Users` > `Manage`
+2. Click on the username of the user that you want to adjust
+3. Select the desired home board via the dropdown and click on `Save` \
+   ![](./img/set-home-board-other-user.png)
+
+### For user groups
+
+1. Navigate to the user groups: `Management` > `Users` > `Groups` > `Manage`
+2. Go to tab `Settings`
+3. Select the desired home board via the dropdown and click on `Save` \
+   ![](./img/set-home-board-user-group.png)
+
+### For whole server
+
+You can also set a global home board that will be used for all users that have not set a home board themselves.
+It will also be used for anonymous users.
+
+1. Navigate to the settings: `Management` > `Settings` > `Boards`
+2. Select the desired home board via the dropdown and click on `Save` \
+   ![](./img/set-home-board-global.png)
+
+:::note
+For the global home board you can only select boards that are public.
+:::
+
+### Mobile home board
+
+Same as the home board, you can also set a mobile home board.
+It will be used for devices that are detected as mobile devices. (Using User-Agent header)

apps/docs/docs/management/certificates/index.mdx

@@ -15,8 +15,6 @@ Below you can see a screenshot of the certificates page.
 The items show the subject, filename and when it expires.
 The color of the icon indicates how long it is valid.
 
-![The Trusted certificates management page](../img/certificates.png)
-
 ![](./img/screenshot.png)
 
 | Color     | Meaning                     |
@@ -32,12 +30,15 @@ Navigate to `Management` > `Tools` > `Certificates`.
 
 ## Add a certificate
 
-To add a certificate click on the "Add certificate" button. The upload form expands directly on the certificates page.
+To add a certificate click on the "Add certificate" button.
 
 ![](./img/add-button.png)
 
-Then select the certificate file you want to add and click the "Add" button. You can cancel to collapse the form without
-leaving the page.
+Then select the certificate file you want to add.
+
+![](./img/add-modal.png)
+
+And click the "Add" button.
 
 ## Delete a certificate
 
@@ -45,7 +46,7 @@ To delete a certificate you can click on the trash icon in the certificate card.
 
 ![](./img/card.png)
 
-The first click arms the action and the second click confirms the deletion in place; no confirmation dialog is opened.
+Then confirm the deletion.
 
 ## Managing it through file system
 
@@ -57,6 +58,11 @@ This means you can automate the update of the certificates by simply replacing o
 Every integration has its own way of obtaining certificates.
 Generally it is recommended to search for the documentation of the integration you are using.
 Most of the time you can find the certificate in the file system of the integration.
+The certificate file needs to be uploaded to Homarr. To first get the file on your computer you can either:
+
+- use `scp user@host:/path/to/file ./certificate.pem`
+- use `cat /path/to/file` to print the certificate. Then recreate the file on your machine.
+
 Below you can find instructions for some of the integrations.
 
 ### Pi-hole (v6)
@@ -64,3 +70,9 @@ Below you can find instructions for some of the integrations.
 Since version 6 of Pi-hole, the web interface can be accessed through HTTPS.
 The certificate can be found in the path `/etc/pihole/tls_ca.crt`. To add the certificate, this file needs to be copied and uploaded to Homarr.
 You can find more details regarding SSL / TLS for Pi-hole [here](https://docs.pi-hole.net/api/tls/).
+
+### Proxmox
+
+By default, Proxmox VE uses a node certificate signed by the cluster. You only need to configure Homarr with the certificate of a single node.
+The certificate can be found in any node on the path `/etc/pve/pve-root-ca.pem`.
+You can learn more about certificate management in Proxmox [here](https://pve.proxmox.com/wiki/Certificate_Management).

apps/docs/docs/management/custom-widgets/agent-authoring.mdx

@@ -1,45 +1,104 @@
-# Connect an agent
+# Use agents and skills.sh
 
-An MCP-connected agent can validate, preview, test, and save Custom Widgets. The API key owner must be a Homarr
-administrator.
+An external agent creates one widget at a time with the Homarr MCP server. The agent harness manages the list for multiple widgets.
 
-Install the official skill:
+Homarr does not create widget packs or drafts for multiple widgets.
+
+The MCP API key must belong to a Homarr administrator. Non-administrator keys do not list Custom Widget tools, prompts,
+or resources. The same administrator requirement applies to the matching HTTP authoring endpoints.
+
+<a className="button button--primary" href="https://www.skills.sh/homarr-labs/homarr/homarr-custom-widget">
+  View the Custom Widget Skill on skills.sh
+</a>
+
+Install the Agent Skill from the verified Homarr repository:
 
 ```sh
 npx skills add https://github.com/homarr-labs/homarr --skill homarr-custom-widget
 ```
 
-The skill routes the agent to the release-matched schema, runtime, security, examples, and component metadata. It keeps
-those references separate so the agent loads only what the current widget needs.
+The portable skill gives concise authoring guidance. The Homarr MCP prompt gives connected agents a retrieval workflow: read the live schema, then fetch only the component documentation needed for the widget.
 
-## MCP resources
+The workbench's **Copy AI prompt** action is separate. It creates a self-contained prompt below 12,000 characters for an ordinary ChatGPT or Claude conversation. It includes the lean contract, bindings, recommended components, and two polished examples. It never tells an offline model to call MCP tools.
+
+The source is in [`.agents/skills/homarr-custom-widget`](https://github.com/homarr-labs/homarr/tree/HEAD/.agents/skills/homarr-custom-widget). `HEAD` follows the repository default branch, so the link is not tied to an unreleased feature branch. Homarr does not provide a ZIP archive.
+
+After publication, run the installation command once. This action registers installation activity.
+
+Then, verify the skills.sh page. Request official maker attribution for `homarr-labs` from skills.sh.
+
+Repository code cannot give this attribution.
+
+## Get MCP resources
 
 - Prompt: `homarr-custom-widget-author`
-- Skill: `homarr://custom-widgets/skill`
-- References: `homarr://custom-widgets/references/{schema|runtime|security}`
-- Schema: `homarr://custom-widgets/schema`
-- Components: `homarr://custom-widgets/components` and `components/{name}`
-- Examples: `homarr://custom-widgets/examples/{name}`
+- Resources: `homarr://custom-widgets/schema`, `components`, `components/{name}`, `examples/{name}`, and `skill`
+- HTTP: `GET /api/custom-widgets/authoring-prompt`, `schema`, `components`, and `skill`
 
-Equivalent HTTP resources are available under `/api/custom-widgets/` for authenticated administrators.
+The authoring-prompt tool description contains one sentence. The prompt contains the workflow instructions and resource links.
 
-## Authoring lifecycle
+`GET /api/custom-widgets/skill` and the MCP tool return the concise skill discovery payload:
 
-1. Load the skill and only the references needed for the design.
-2. Read the external API documentation and build the definition.
-3. Validate the JSX, then create a preview from the complete definition.
-4. Run every returned query and simulate every relevant action against the current preview revision.
-5. Inspect the preview and redacted journal. Revise the existing preview for JSX-only changes.
-6. Save from the final tested preview.
-7. Configure deployment-specific source URLs and credentials, then preview the saved definition again.
+```ts
+{
+  name: "homarr-custom-widget";
+  version: string;
+  skillMd: string;
+  skillsShUrl: string;
+  sourceUrl: string;
+  installCommand: string;
+}
+```
 
-Use `templateLines` for multiline JSX tool input. A preview must have current evidence for every query and action before
-it can be saved. Simulation counts as action evidence without performing the mutation.
+The full installed component catalog stays available through `homarr://custom-widgets/components` and per-component resources. It is deliberately not embedded in the skill or clipboard prompt.
 
-If the agent does not have a source URL or credential, it can request a short-lived Homarr configuration URL. An
-authenticated administrator completes it in Homarr; the agent receives the status, never the plaintext credential.
+These interfaces do not return an archive URL or archive hash.
 
-Agents can also search, inspect, install, and configure existing Workshop widgets instead of regenerating them.
+## Create a Custom Widget with MCP
 
-See [MCP](/docs/management/mcp) for client configuration and [requests and security](./requests-and-security) for the
-runtime limits.
+1. Get the prompt, live schema, and component catalog.
+2. Read the external API documentation.
+3. Build one definition.
+4. Validate the definition without saving it.
+5. Create a preview session.
+6. Test the queries and actions.
+7. Open the preview URL with browser tools.
+8. Inspect the redacted journal and revise the local candidate until it is valid.
+9. Create the widget, including any source URLs and credentials the user already supplied.
+10. Otherwise, ask the user to configure the saved definition with the ten-minute Homarr source-setup URL.
+11. Create a final preview with the saved definition ID so Homarr loads its stored credentials, then test it again.
+12. Update the saved definition if the final verification finds a problem.
+13. Repeat the procedure for the next widget.
+
+Each source-configuration URL applies to one definition or preview and one source. It is short-lived, single-use, and
+can only be opened and completed by an authenticated Homarr administrator. The administrator confirms the server URL,
+network scope, and required credential fields directly in Homarr. The agent receives only request status and never
+receives plaintext credentials. Preview-scoped values expire with that preview; definition-scoped values persist.
+
+Agents can install existing widgets without regenerating them:
+
+1. Search with `customWidget_workshopSearch`.
+2. Inspect and validate a result with `customWidget_workshopGet`.
+3. Install it with `customWidget_workshopInstall`.
+4. Configure deployment-specific URLs and supplied credentials with `customWidget_sourceConfigure`.
+5. If the agent does not have those values, call `customWidget_configurationRequestUser` and wait for completion.
+6. Test the installed definition, then use `board_addItem` with kind `customApi` and the returned definition ID.
+
+Homarr encrypts the plaintext immediately. Homarr does not return the plaintext.
+
+## Evaluate the copied prompt
+
+Homarr maintainers can run the same self-contained prompt that the workbench copies through the live generation-quality suite:
+
+```sh
+OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:ai
+```
+
+The suite uses DeepSeek V4 Pro to author Pokédex, Portainer, football, Jellyfin, and Home Assistant widgets. Before DeepSeek V4 Flash judges a result, it must pass Homarr's real clipboard parser, canonical schema, and deterministic scenario checks for the documented API routes, authentication, bindings, actions, and essential runtime components. It saves every response, validated widget manifest, and detailed category scores under `packages/custom-widgets/.ai-evaluations/`.
+
+Each scenario stops as soon as it passes and has a hard limit of ten generation attempts. Override the models or
+per-scenario limit with `OPENROUTER_GENERATOR_MODEL`, `OPENROUTER_JUDGE_MODEL`, and
+`CUSTOM_WIDGET_AI_MAX_LOOPS`. Generated artifacts are local and ignored by Git; promote a reviewed, validated result
+into the bundled-widget source deliberately.
+
+The reference API check uses a real PokeAPI list/detail request and a read-only Portainer container query when `PORTAINER_BASE_URL` and `PORTAINER_API_KEY` are set. Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --pokeapi-only` for the public PokeAPI check alone. To exercise start, restart, and stop against a disposable container, also set `PORTAINER_TEST_CONTAINER_ID` and the explicit safeguard `PORTAINER_ALLOW_MUTATIONS=1`; the script restores the container's original running state.