style: auto-fix lint and format

feat(definitions): wire up doc slugs and sitemap for Beszel + Custom API
Set integration slug for beszel, widget slugs for all 4 Beszel widgets and customApi, add new paths to HomarrDocumentationPath type, and set documentationUrl for the Beszel integration.
2026-06-11 17:40:26 +00:00 · 2026-06-11 19:38:59 +02:00 · 2026-06-11 19:38:44 +02:00 · 2026-06-11 19:38:34 +02:00 · 2026-06-11 19:38:15 +02:00
880 changed files with 30550 additions and 139786 deletions
@@ -0,0 +1,197 @@
+---
+name: Revert Demo MCP
+overview: Revert the demo-specific MCP accommodations (API key bypass, read-only filtering, demo UI) since demo MCP is an edge case with poor ROI. Replace with a clear "MCP not available in demo mode" message. Keep the core MCP feature intact for real instances.
+todos:
+   - id: revert-backend
+     content: Revert demoSafe procedure, apiKeys demo bypass, isDemoMode export from mcp.ts
+     status: pending
+   - id: revert-mcp-route
+     content: Remove isDemoMode filtering and demo SERVER_INSTRUCTIONS from MCP route
+     status: pending
+   - id: revert-ui
+     content: Remove isDemoMode prop plumbing; add demo-not-supported Alert via info.isDemoMode
+     status: pending
+   - id: verify
+     content: Run lint + typecheck; smoke-test demo vs non-demo MCP tab
+     status: pending
+isProject: false
+---
+
+# Revert Demo MCP Accommodations
+
+## Why Docker works but integrations do not
+
+Demo mode has **two different mock mechanisms**:
+
+```mermaid
+flowchart TB
+  subgraph dockerPath [Docker - works in demo]
+    MCP1[MCP docker_getContainers]
+    Handler[docker.ts request handler]
+    MockContainers[Hardcoded mockContainers]
+    MCP1 --> Handler
+    Handler -->|"if DEMO_MODE"| MockContainers
+  end
+
+  subgraph integrationPath [Integrations - confusing in demo]
+    MCP2[MCP widget tools e.g. calendar_findAllEvents]
+    TRPC[tRPC procedure]
+    RH[cached-integration-request-handler]
+    Kind{integration.kind}
+    Mock[MockIntegration fake data]
+    Real[Sonarr/Radarr HTTP - fails]
+    MCP2 --> TRPC --> RH --> Kind
+    Kind -->|mock| Mock
+    Kind -->|sonarr/radarr| Real
+  end
+```
+
+- **Docker**:
+  [`packages/request-handler/src/docker.ts`](packages/request-handler/src/docker.ts)
+  checks `DEMO_MODE` directly and returns inline fake containers. No integration
+  record needed.
+- **Everything else**: Demo seed creates **one** integration with `kind: "mock"`
+  ([`packages/db/migrations/seed.ts`](packages/db/migrations/seed.ts)), not
+  Sonarr/Radarr/Overseerr.
+  [`MockIntegration`](packages/integrations/src/mock/mock-integration.ts) can
+  serve calendar, downloads, health, DNS, media server, etc. **if** callers pass
+  that integration ID.
+- **Why it felt broken**: MCP tool descriptions tell AI clients to look for
+  "Overseerr/Sonarr IDs". Demo has none. Tools like
+  `integration_searchMediaRequests` hard-filter to `mediaSearch` kinds
+  (`overseerr`, `jellyseerr`, `seerr`) — `mock` is excluded from that category
+  in
+  [`packages/definitions/src/integration.ts`](packages/definitions/src/integration.ts).
+
+Fixing this properly means extending the mock integration system (new
+`searchAsync`, category changes, middleware relaxations, instruction rewrites)
+for a feature almost nobody will use on the public demo.
+
+## Option comparison
+
+|                      | **Revert (chosen)**         | **Minimal fix**                                | **Full fix**                                        |
+| -------------------- | --------------------------- | ---------------------------------------------- | --------------------------------------------------- |
+| **Effort**           | ~1 hour, ~100 lines removed | ~2 hours                                       | 1-2 days                                            |
+| **Files touched**    | 8 MCP/demo-specific files   | 8 + route instructions                         | 15+ across integrations, definitions, seed, routers |
+| **Risk**             | Low                         | Low-medium                                     | Medium (mock/search semantics)                      |
+| **Demo MCP outcome** | Clearly unsupported         | Partial (widget reads only, no search/request) | Near-full read coverage                             |
+| **Maintenance**      | None ongoing                | Instructions drift with tool changes           | Mock parity with real integrations                  |
+
+**Recommendation: Revert.** The demo accommodation code added special-case
+plumbing (`demoSafePermissionRequiredProcedure`, dual mutation guards, hardcoded
+UI strings) for a workflow that still cannot deliver a convincing "homelab AI"
+experience without substantial integration-layer work.
+
+## What to revert (demo MCP accommodations only)
+
+These changes were added specifically for demo + MCP. **Do not revert** the core
+MCP server, OAuth, Scalar docs, tool descriptions, or `normalizeSchema`.
+
+### Backend (3 files)
+
+1. [`packages/api/src/trpc.ts`](packages/api/src/trpc.ts)
+   - Remove `demoSafePermissionRequiredProcedure` export (~12 lines)
+   - Keep existing `enforceDemoModeReadOnly` (pre-dates MCP; used by whole app)
+
+2. [`packages/api/src/router/apiKeys.ts`](packages/api/src/router/apiKeys.ts)
+   - Change `create` back to `permissionRequiredProcedure` (mutations blocked in
+     demo again)
+   - Remove `isDemoMode` guard on `delete` (global demo middleware already
+     blocks delete mutations)
+   - Remove `TRPCError` / `isDemoMode` imports if unused
+
+3. [`packages/api/src/mcp.ts`](packages/api/src/mcp.ts)
+   - Stop exporting `isDemoMode`; keep only `createTRPCContext` and `mcpRouter`
+
+### MCP route (1 file)
+
+4. [`apps/nextjs/src/app/api/mcp/[transport]/route.ts`](apps/nextjs/src/app/api/mcp/[transport]/route.ts)
+   - Remove `isDemoMode` import and all demo branches:
+     - `ListToolsRequestSchema` mutation filter
+     - `CallToolRequestSchema` mutation rejection
+     - `SERVER_INSTRUCTIONS` demo section
+   - Keep `getToolType` / `buildToolTypeMap` only if still needed elsewhere;
+     otherwise remove dead code from demo-only filtering
+
+### UI (4 files)
+
+5. [`apps/nextjs/src/app/[locale]/manage/tools/api/page.tsx`](apps/nextjs/src/app/[locale]/manage/tools/api/page.tsx)
+   - Remove `isDemoMode` import from `@homarr/api/mcp`
+   - Stop passing `isDemoMode` to child components
+
+6. [`apps/nextjs/src/app/[locale]/manage/tools/api/components/api-page-tabs.tsx`](apps/nextjs/src/app/[locale]/manage/tools/api/components/api-page-tabs.tsx)
+   - Remove `isDemoMode` prop from interface and `McpInstructions` call
+
+7. [`apps/nextjs/src/app/[locale]/manage/tools/api/components/mcp-instructions.tsx`](apps/nextjs/src/app/[locale]/manage/tools/api/components/mcp-instructions.tsx)
+   - Remove `isDemoMode` prop
+   - Replace current demo banner with a single **Alert**: MCP requires a
+     self-hosted instance; demo mode does not support MCP (API key creation and
+     write tools are disabled)
+   - Use `clientApi.info.isDemoMode.useQuery()` or pass `isDemoMode` from server
+     via existing `api.info.isDemoMode()` tRPC query (already exists in
+     [`packages/api/src/router/info.ts`](packages/api/src/router/info.ts)) —
+     avoids re-exporting from `@homarr/api/mcp`
+
+8. [`apps/nextjs/src/app/[locale]/manage/tools/api/components/api-keys.tsx`](apps/nextjs/src/app/[locale]/manage/tools/api/components/api-keys.tsx)
+   - Remove `isDemoMode` prop and conditional delete-column spread
+   - Delete button hidden automatically in demo because `apiKeys.delete`
+     mutation is blocked by global `enforceDemoModeReadOnly`
+
+## What to add instead
+
+- **MCP tab**: When `info.isDemoMode` is true, show a prominent notice at the
+  top of
+  [`mcp-instructions.tsx`](apps/nextjs/src/app/[locale]/manage/tools/api/components/mcp-instructions.tsx)
+  explaining MCP is for self-hosted instances only.
+- **Optional**: Disable/hide the "Create API Key" button on the MCP tab in demo
+  (mutations will fail anyway).
+- **No changes** to integrations, definitions, seed, or mock services.
+
+## Files NOT impacted by revert
+
+Core MCP feature stays as-is:
+
+- [`apps/nextjs/src/app/api/mcp/[transport]/route.ts`](apps/nextjs/src/app/api/mcp/[transport]/route.ts)
+  — auth, rate limiting, `normalizeSchema`, `SERVER_INSTRUCTIONS` (minus demo
+  section)
+- OAuth routes under `apps/nextjs/src/app/api/mcp/oauth/`
+- All MCP-enabled routers in `packages/api/src/router/`
+- [`packages/api/src/mcp.ts`](packages/api/src/mcp.ts) — eager router (minus
+  `isDemoMode` export)
+- Scalar UI, dynamic tools table,
+  [`.cursor/rules/mcp-integration.mdc`](.cursor/rules/mcp-integration.mdc)
+
+Pre-existing demo infrastructure (unchanged):
+
+- [`packages/request-handler/src/docker.ts`](packages/request-handler/src/docker.ts)
+  — Docker mock containers
+- [`packages/db/migrations/seed.ts`](packages/db/migrations/seed.ts) — mock
+  integration + demo board
+- [`packages/integrations/src/mock/`](packages/integrations/src/mock/) — mock
+  services for widgets on demo board UI
+
+## Verification
+
+1. `pnpm lint` and `pnpm typecheck` pass
+2. Demo mode (`DEMO_MODE=true`):
+   - MCP tab shows "not supported" notice
+   - API key create fails with existing "Mutations are disabled in demo mode"
+   - `docker_getContainers` still works on demo board UI (unchanged; separate
+     code path)
+3. Non-demo mode: MCP unchanged (all tools listed, mutations work with
+   permissions)
+
+## Commit strategy
+
+Single focused commit on `feat/add-mcp-server`:
+
+```
+revert(mcp): drop demo-mode accommodations for MCP
+
+MCP is intended for self-hosted instances. Remove demo-specific API key
+bypass, read-only tool filtering, and demo UI plumbing. Show a clear
+notice on the MCP tab when demo mode is active.
+```
+
+Then push to the existing PR (no force-push needed unless you want another
+squash).
@@ -1,622 +0,0 @@
-# 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"
-```
-
-### Old-import mappings
-
-Add to `packages/old-import/src/widgets/options.ts`:
-
-```typescript
-columnOrder: () => undefined,
-columnWidths: () => undefined,
-```
-
-### Dynamic storeKey
-
-Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
-
-```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 w = entry[key as keyof typeof entry];
-      if (typeof w === "number") widthMap[key] = w;
-      else if (typeof w === "string" && w.endsWith("px")) widthMap[key] = parseInt(w, 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 old-import mappings for new options
-8. Add translation keys (including hidden option labels)
-9. Add context menu if row actions exist
-10. Add row expansion if detail view exists
-11. Add error handling on all mutations
-12. Add accessibility attributes
-13. Test at multiple widget widths
-14. Update docs in `apps/docs/docs/widgets/` if applicable
-15. Run `pnpm turbo typecheck` — catches old-import mismatches
-16. Run translation spec — catches missing keys
@@ -6,14 +6,7 @@ npm-debug.log
 README.md
 .next
 .turbo
-.pnpm-store
-**/.pnpm-store
-coverage
-**/coverage
-**/.docusaurus
-**/build
 .git
-.github
 dev
 .build
 e2e
@@ -59,11 +59,4 @@ TURBO_TELEMETRY_DISABLED=1
 # ENABLE_KUBERNETES=true

 # Enable mock integration
-UNSAFE_ENABLE_MOCK_INTEGRATION=true
-
-# Enable demo mode (seeds a demo user "demo"/"demo", a sample board and a mock integration)
-# DEMO_MODE=true
-
-# Whether demo mode is read-only. Defaults to true (the public demo blocks all mutations).
-# Set to false for writable preview deployments so the demo user can modify the dashboard.
-# DEMO_READ_ONLY=false
+UNSAFE_ENABLE_MOCK_INTEGRATION=true
@@ -33,16 +33,6 @@ body:
      options:
        # The below comment is used to insert a new version with on-release.yml
        #NEXT_VERSION#
-        - 1.72.0
-        - 1.71.0
-        - 1.70.0
-        - 1.69.2
-        - 1.69.0
-        - 1.68.0
-        - 1.67.0
-        - 1.66.1
-        - 1.66.0
-        - 1.65.0
        - 1.64.0
        - 1.62.0
        - 1.61.0
@@ -1,2 +0,0 @@
-.secrets
-!.secrets.example
@@ -1,4 +0,0 @@
-TURBO_API=
-TURBO_TEAM=
-TURBO_TOKEN=
-TURBO_REMOTE_CACHE_SIGNATURE_KEY=
@@ -1,36 +0,0 @@
-# Running CI locally
-
-Install [Act](https://nektosact.com/installation/index.html) and ensure Docker is running, then use:
-
-```bash
-pnpm ci:act:fast
-pnpm ci:act:docker
-pnpm ci:act:all
-pnpm ci:act:cleanup
-```
-
-`fast` runs the quality gate. `docker` and `all` run the gate followed by the single container build, E2E suite, and memory regression test. `cleanup` validates the manual cleanup path without calling GitHub. The wrapper supports regular clones and Git worktrees, including non-default Docker contexts. Linux dependencies are kept in Docker volumes instead of overwriting host `node_modules`. The first run downloads the Act runner and Playwright browser dependencies.
-
-Remote caching is optional locally. Copy `.github/act/.secrets.example` to `.github/act/.secrets`, populate it with rotated credentials, and run with:
-
-```bash
-ACT_SECRET_FILE=.github/act/.secrets pnpm ci:act:all
-```
-
-Act never publishes or deletes GHCR images. The secret file is ignored by Git.
-
-## PR preview images
-
-Successful non-draft pull requests from this repository publish an amd64 image:
-
-```bash
-docker pull ghcr.io/homarr-labs/homarr-test:pr-<number>
-```
-
-The tag is replaced when the pull request is updated and deleted when it closes. Production Homarr images remain the supported multi-architecture releases. The `homarr-test` package must be configured as public in GHCR for unauthenticated testers.
-
-## Dokploy preview cache
-
-Keep `needs-demo` as the Dokploy preview label. Under the application's **Preview Build-time Secrets**, configure `TURBO_API`, `TURBO_TEAM`, `TURBO_TOKEN`, and `TURBO_REMOTE_CACHE_SIGNATURE_KEY`. Dokploy passes these to the Dockerfile as BuildKit secrets. Do not configure the token or signature key as Docker build arguments.
-
-Rotate any credentials that have appeared in chat, logs, or committed configuration before enabling the cache.
@@ -11,7 +11,7 @@ outputs:
 runs:
  using: "composite"
  steps:
-    - uses: actions/checkout@v7
+    - uses: actions/checkout@v6
      with:
        persist-credentials: false
    - name: Set up Docker Buildx
@@ -11,11 +11,3 @@
 - [ ] Commits follow the [conventional commits guideline](https://www.conventionalcommits.org/en/v1.0.0/)
 - [ ] No shorthand variable names are used (eg. `x`, `y`, `i` or any abbrevation)
 - [ ] Documentation is up to date. Create a pull request [here](https://github.com/homarr-labs/documentation/).
- [ ] When using AI; No temp files are checked in, the code style follows the rest of the project
-
-**When contributing a new integration or widget:**
-
- [ ] I confirmed manually that the integration or widget is working with a real system and performed basic smoke
-  tests (e.g. what happens if it is offline)
- [ ] Optional but recommended: I confirm that I am willing to be added to the `CODEOWNERS` of this feature and will
-  provide support and maintain the integration (e.g. in case of breaking or failure)
@@ -1,6 +1,6 @@
 {
  $schema: "https://docs.renovatebot.com/renovate-schema.json",
-  extends: ["config:recommended", ":dependencyDashboardApproval"],
+  extends: ["config:recommended"],
  packageRules: [
    {
      matchPackageNames: ["^@homarr/"],
@@ -22,7 +22,7 @@
      automerge: true,
    },
    {
-      // disallow automerge for allowBuilds dependencies (native builds need manual verification)
+      // disallow automerge for onlyBuiltDependencies
      matchPackageNames: [
        "@tree-sitter-grammars/tree-sitter-yaml",
        "bcrypt",
@@ -46,8 +46,8 @@
  updateInternalDeps: true,
  rangeStrategy: "bump",
  automerge: false,
-  baseBranchPatterns: ["dev"],
-  dependencyDashboard: true,
+  baseBranches: ["dev"],
+  dependencyDashboard: false,
  // prevent special characters in branch names (otherwise git errors occur on windows)
  branchNameStrict: true,
 }
@@ -1,47 +0,0 @@
-name: Auto-fix lint and format
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-    branches: ["*"]
-
-permissions:
-  contents: write
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-jobs:
-  autofix:
-    name: Auto-fix
-    if: github.event.pull_request.head.repo.id == github.repository_id
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    steps:
-      - uses: actions/checkout@v7
-        with:
-          fetch-depth: 0
-          ref: ${{ github.head_ref }}
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Get changed files
-        id: changed
-        env:
-          BASE_REF: ${{ github.base_ref }}
-        run: |
-          git diff --name-only --diff-filter=ACMR "origin/${BASE_REF}...HEAD" -- '*.ts' '*.tsx' '*.js' '*.jsx' > /tmp/changed-files
-          echo "count=$(wc -l < /tmp/changed-files | tr -d '[:space:]')" >> $GITHUB_OUTPUT
-
-      - name: Auto-fix lint + format
-        if: steps.changed.outputs.count != '0'
-        run: |
-          xargs -r -a /tmp/changed-files pnpm exec oxlint --fix || true
-          xargs -r -a /tmp/changed-files pnpm exec oxfmt --write
-
-      - name: Commit fixes
-        uses: stefanzweifel/git-auto-commit-action@v7
-        with:
-          commit_message: "style: auto-fix lint and format"
@@ -17,7 +17,7 @@ jobs:
    if: github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 || github.actor_id == 175486441
    steps:
      - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
      - name: Obtain token
        id: obtainToken
        uses: actions/create-github-app-token@v3
@@ -1,264 +0,0 @@
-name: CI
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["*"]
-  pull_request_target:
-    types: [closed]
-    branches: ["*"]
-  push:
-    branches: [main, dev, beta, next]
-  merge_group:
-  workflow_dispatch:
-    inputs:
-      operation:
-        description: Operation to run
-        required: true
-        default: validate
-        type: choice
-        options:
-          - validate
-          - publish
-          - cleanup
-      pr_number:
-        description: PR number for publish or cleanup
-        required: false
-        type: number
-      ref:
-        description: Git ref to validate or publish
-        required: false
-        type: string
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-env:
-  FORCE_COLOR: 3
-  SKIP_ENV_VALIDATION: true
-  TURBO_TELEMETRY_DISABLED: 1
-  REGISTRY: ghcr.io
-  PREVIEW_IMAGE: ghcr.io/homarr-labs/homarr-test
-
-jobs:
-  fast-gate:
-    name: Fast gate
-    if: github.event_name != 'pull_request_target' && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    env:
-      TURBO_API: ${{ secrets.TURBO_API }}
-      TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-      TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-      TURBO_SCM_BASE: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before || 'HEAD~1' }}
-      TURBO_SCM_HEAD: ${{ github.sha }}
-      TURBO_PLATFORM: linux/amd64
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Validate manual inputs
-        if: github.event_name == 'workflow_dispatch' && inputs.operation == 'publish'
-        env:
-          PR_NUMBER: ${{ inputs.pr_number }}
-          BUILD_REF: ${{ inputs.ref }}
-        run: |
-          test -n "$PR_NUMBER" || { echo "pr_number is required for publish"; exit 1; }
-          test -n "$BUILD_REF" || { echo "ref is required for publish"; exit 1; }
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Copy environment defaults
-        run: cp .env.example .env
-
-      - name: Lint, typecheck, and build affected workspaces
-        run: pnpm turbo run lint typecheck build --affected --continue=dependencies-successful
-
-      - name: Validate workspace configuration
-        run: pnpm lint:ws
-
-      - name: Run unit tests
-        run: pnpm test
-
-  container:
-    name: Container and E2E
-    needs: fast-gate
-    if: |
-      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: write
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build container once
-        if: "!env.ACT"
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/amd64
-          load: true
-          push: false
-          tags: |
-            homarr-ci
-            homarr-e2e
-          labels: |
-            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-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: Build container once with Act
-        if: env.ACT
-        env:
-          TURBO_API: ${{ secrets.TURBO_API }}
-          TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
-          TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-          TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-        run: |
-          secret_args=()
-          for secret in TURBO_API TURBO_TEAM TURBO_TOKEN TURBO_REMOTE_CACHE_SIGNATURE_KEY; do
-            if [ -n "${!secret:-}" ]; then
-              secret_args+=(--secret "id=${secret},env=${secret}")
-            fi
-          done
-          DOCKER_BUILDKIT=1 docker build --platform linux/amd64 \
-            --tag homarr-ci --tag homarr-e2e "${secret_args[@]}" .
-
-      - name: Cache Playwright browsers
-        if: "!env.ACT"
-        id: playwright-cache
-        uses: actions/cache@v6
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
-
-      - name: Install Playwright Chromium
-        if: steps.playwright-cache.outputs.cache-hit != 'true' || env.ACT
-        run: pnpm exec playwright install --with-deps chromium
-
-      - name: Install Playwright system deps
-        if: steps.playwright-cache.outputs.cache-hit == 'true'
-        run: pnpm exec playwright install-deps chromium
-
-      - name: Run E2E tests
-        run: pnpm test:e2e
-
-      - name: Upload E2E artifacts
-        if: failure() && !env.ACT
-        uses: actions/upload-artifact@v7
-        with:
-          name: playwright-report
-          path: e2e/test-results/
-          retention-days: 7
-
-      - name: Determine preview tag
-        id: preview
-        if: |
-          !env.ACT &&
-          (
-            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-          )
-        env:
-          PR_NUMBER: ${{ github.event.pull_request.number || inputs.pr_number }}
-        run: echo "tag=pr-${PR_NUMBER}" >> "$GITHUB_OUTPUT"
-
-      - name: Log in to GHCR
-        if: steps.preview.outputs.tag != ''
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Push preview image
-        if: steps.preview.outputs.tag != ''
-        env:
-          PREVIEW_TAG: ${{ steps.preview.outputs.tag }}
-        run: |
-          docker tag homarr-ci "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
-          docker push "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
-
-      - name: Show Act publication result
-        if: env.ACT
-        run: echo "Act validated the publication path; external GHCR writes are disabled locally."
-
-  cleanup:
-    name: Clean up preview image
-    if: github.event_name == 'pull_request_target' || (github.event_name == 'workflow_dispatch' && inputs.operation == 'cleanup')
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    permissions:
-      packages: write
-    env:
-      IMAGE_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
-    steps:
-      - name: Validate cleanup input
-        if: github.event_name == 'workflow_dispatch'
-        env:
-          PR_NUMBER: ${{ inputs.pr_number }}
-        run: test -n "$PR_NUMBER" || { echo "pr_number is required for cleanup"; exit 1; }
-
-      - name: Delete GHCR package version
-        if: "!env.ACT"
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const packageName = "homarr-test";
-            const org = context.repo.owner;
-            const tag = process.env.IMAGE_TAG;
-            const versions = await github.paginate(
-              github.rest.packages.getAllPackageVersionsForPackageOwnedByOrg,
-              { package_type: "container", package_name: packageName, org, per_page: 100 },
-            );
-            const target = versions.find((version) =>
-              version.metadata?.container?.tags?.includes(tag),
-            );
-            if (!target) {
-              core.info(`No package version found with tag "${tag}"`);
-              return;
-            }
-            await github.rest.packages.deletePackageVersionForOrg({
-              package_type: "container",
-              package_name: packageName,
-              org,
-              package_version_id: target.id,
-            });
-            core.info(`Deleted package version ${target.id} (${tag})`);
-
-      - name: Show Act cleanup result
-        if: env.ACT
-        run: echo "Act validated cleanup for ${IMAGE_TAG}; external GHCR writes are disabled locally."
@@ -0,0 +1,165 @@
+name: "[Quality] Code Analysis"
+permissions:
+  contents: read
+
+on:
+  pull_request:
+    branches: ["*"]
+  push:
+    branches: ["main"]
+  merge_group:
+
+concurrency:
+  group: "${{ github.workflow }}-${{ github.ref }}"
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+
+env:
+  FORCE_COLOR: 3
+  SKIP_ENV_VALIDATION: true
+  TURBO_API: ${{ secrets.TURBO_API }}
+  TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
+  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
+  TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
+  TURBO_SCM_BASE: ${{ github.event.pull_request.base.sha || github.event.before || 'HEAD~1' }}
+  TURBO_SCM_HEAD: ${{ github.sha }}
+
+jobs:
+  lint-format-autofix:
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+          ref: ${{ github.head_ref }}
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Get changed files
+        id: changed
+        run: |
+          git diff --name-only --diff-filter=ACMR origin/${{ github.base_ref }}...HEAD -- '*.ts' '*.tsx' '*.js' '*.jsx' > /tmp/changed-files
+          echo "count=$(wc -l < /tmp/changed-files | tr -d '[:space:]')" >> $GITHUB_OUTPUT
+
+      - name: Auto-fix lint + format
+        if: steps.changed.outputs.count != '0'
+        run: |
+          xargs -r -a /tmp/changed-files pnpm exec oxlint --fix || true
+          xargs -r -a /tmp/changed-files pnpm exec oxfmt --write
+
+      - name: Commit fixes
+        uses: stefanzweifel/git-auto-commit-action@v5
+        with:
+          commit_message: "style: auto-fix lint and format"
+
+  lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Copy env
+        shell: bash
+        run: cp .env.example .env
+
+      - name: Lint
+        run: pnpm turbo lint --affected && pnpm lint:ws
+
+  format:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Format
+        run: pnpm turbo format --affected --continue
+
+  typecheck:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Typecheck
+        run: pnpm turbo typecheck --affected
+
+  test:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Test
+        run: pnpm test
+
+      - name: "Report Coverage"
+        # Set if: always() to also generate the report if tests are failing
+        # Only works if you set `reportOnFailure: true` in your vite config as specified above
+        if: always()
+        uses: davelosert/vitest-coverage-report-action@v2
+
+  e2e:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v6
+      - name: Setup
+        uses: ./tooling/github/setup
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+      - name: Build docker image
+        id: build-docker-image
+        uses: docker/build-push-action@v7
+        with:
+          platforms: linux/amd64
+          context: .
+          push: false
+          load: true
+          tags: homarr-e2e
+          network: host
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+        env:
+          SKIP_ENV_VALIDATION: true
+      - name: Install playwright browsers
+        run: pnpm exec playwright install chromium
+      - name: Run E2E Tests
+        shell: bash
+        run: pnpm test:e2e
+
+  build:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - name: Setup
+        uses: ./tooling/github/setup
+      - name: Copy env
+        shell: bash
+        run: cp .env.example .env
+      - name: Build
+        run: pnpm turbo build --affected
@@ -15,7 +15,7 @@ jobs:

    steps:
      - name: Checkout
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6

      - name: Obtain token
        id: obtainToken
@@ -18,7 +18,7 @@ jobs:

    steps:
      - name: Checkout
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6

      - name: Upload Crowdin translations
        uses: crowdin/github-action@v2
@@ -26,7 +26,7 @@ jobs:
        with:
          args: "Beta release has been triggered: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        with:
          fetch-depth: 0
      - name: Get Next Version
@@ -57,7 +57,7 @@ jobs:
          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
          permission-contents: write # required to commit package.json & changelog changes, merge them to dev / next and publish the release

-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        if: env.SKIP_RELEASE == 'false'
        with:
          persist-credentials: false
@@ -66,7 +66,7 @@ jobs:
      - uses: actions/setup-node@v6
        if: env.SKIP_RELEASE == 'false'
        with:
-          node-version: 24.18.0
+          node-version: 24.16.0
          package-manager-cache: false
      - run: npm i -g pnpm
        if: env.SKIP_RELEASE == 'false'
@@ -119,7 +119,7 @@ jobs:
    outputs:
      digest: ${{ steps.build.outputs.digest }}
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: ${{ needs.release.outputs.git_ref }}

@@ -148,11 +148,6 @@ jobs:
          platforms: linux/amd64
          labels: ${{ steps.meta.outputs.labels }}
          outputs: type=image,"name=${{ env.GHCR_REPO }}",push-by-digest=true,name-canonical=true,push=true
-          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 }}
        env:
          SKIP_ENV_VALIDATION: true
  build-arm64:
@@ -163,7 +158,7 @@ jobs:
    outputs:
      digest: ${{ steps.build.outputs.digest }}
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: ${{ needs.release.outputs.git_ref }}

@@ -192,11 +187,6 @@ jobs:
          platforms: linux/arm64
          labels: ${{ steps.meta.outputs.labels }}
          outputs: type=image,"name=${{ env.GHCR_REPO }}",push-by-digest=true,name-canonical=true,push=true
-          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 }}
        env:
          SKIP_ENV_VALIDATION: true
  extract-asset-amd64:
@@ -30,7 +30,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - name: Setup
        uses: ./tooling/github/setup
      - name: Build docs
@@ -38,9 +38,9 @@ jobs:
        env:
          CI: "true"
      - name: Setup Pages
-        uses: actions/configure-pages@v6
+        uses: actions/configure-pages@v5
      - name: Upload pages artifact
-        uses: actions/upload-pages-artifact@v5
+        uses: actions/upload-pages-artifact@v4
        with:
          path: "apps/docs/build"

@@ -53,4 +53,4 @@ jobs:
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
-        uses: actions/deploy-pages@v5
+        uses: actions/deploy-pages@v4
@@ -3,7 +3,6 @@ name: "[Deployment] Automatic Weekly Release"
 on:
  schedule:
    - cron: "0 19 * * 5" # https://crontab.guru/#0_19_*_*_5
-      timezone: Europe/Zurich
  workflow_dispatch:
    inputs:
      send-notifications:
@@ -29,7 +28,7 @@ jobs:
        with:
          args: "Automatic release has been triggered: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        with:
          fetch-depth: 0
      - name: Get Next Version
@@ -20,7 +20,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6

      - name: Setup
        uses: ./tooling/github/setup
@@ -19,7 +19,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: dev

@@ -31,7 +31,7 @@ jobs:
        run: pnpm api-dump-contributors

      - name: Commit updated contributors
-        uses: EndBug/add-and-commit@v10
+        uses: EndBug/add-and-commit@v9
        with:
          add: "apps/docs/static"
          default_author: github_actor
@@ -16,7 +16,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
        with:
          ref: dev

@@ -58,7 +58,7 @@ jobs:
          echo "OpenAPI spec updated ($(jq '.paths | length' /tmp/openapi.json) paths)"

      - name: Commit updated spec
-        uses: EndBug/add-and-commit@v10
+        uses: EndBug/add-and-commit@v9
        with:
          add: "apps/docs/static/api/"
          default_author: github_actor
@@ -13,7 +13,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 5
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - name: Validate prebuilt dependencies for amd64
        id: validate-amd64
        uses: ./.github/actions/prebuilt-debian
@@ -30,7 +30,7 @@ jobs:
    runs-on: ubuntu-24.04-arm
    timeout-minutes: 5
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - name: Validate prebuilt dependencies for arm64
        id: validate-arm64
        uses: ./.github/actions/prebuilt-debian
@@ -13,7 +13,7 @@ jobs:
    runs-on: ubuntu-latest
    timeout-minutes: 2
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
      - run: |
          npx --yes --package renovate -- \
              renovate-config-validator --strict .github/renovate.json5
@@ -52,7 +52,7 @@ jobs:
          permission-contents: write # required to commit to branch
          permission-pull-requests: write # required to create pr & enable automerge
      - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        with:
          token: ${{ steps.obtainToken.outputs.token }}
          ref: dev
@@ -29,7 +29,7 @@ jobs:
          permission-pull-requests: write # required to create pr & enable automerge

      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        env:
          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}

@@ -28,7 +28,7 @@ jobs:
          permission-contents: write # required to commit to branch
          permission-pull-requests: write # required to create pr & enable automerge
      - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
        env:
          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
      - name: Setup
@@ -2,7 +2,6 @@

 # dependencies
 node_modules
-.pnpm-store/
 .pnp
 .pnp.js
 .idea/
@@ -71,10 +70,7 @@ apps/nextjs/public/images/background.png

 # personal agent config
 .opencode
-.agents/
-skills-lock.json

 # docusaurus
 apps/docs/.docusaurus
 apps/docs/build
-.pnpm-store
@@ -1,2 +1,3 @@
 [tools]
-node = "24.18.0"
+node = "24.16.0"
+pnpm = "10.34.1"
@@ -1,2 +1,6 @@
-# pnpm v11: non-auth settings moved to pnpm-workspace.yaml
-# Keep this file for any future registry/auth configuration
+# Expo doesn't play nice with pnpm by default. 
+# The symbolic links of pnpm break the rules of Expo monorepos.
+# @link https://docs.expo.dev/guides/monorepos/#common-issues
+node-linker=hoisted
+strict-peer-dependencies=false
+engine-strict=true
@@ -1 +1 @@
-24.18.0
+24.16.0
@@ -1,7 +1,7 @@
 {
  "recommendations": [
    "dbaeumer.vscode-eslint",
-    "oxc.oxc-vscode",
+    "esbenp.prettier-vscode",
    "yoavbls.pretty-ts-errors",
    "million.million-lint",
    "lokalise.i18n-ally"
@@ -1,5 +1,5 @@
 {
-  "js/ts.tsdk.path": "node_modules\\typescript\\lib",
+  "typescript.tsdk": "node_modules\\typescript\\lib",
  "js/ts.implicitProjectConfig.experimentalDecorators": true,
  "cSpell.words": [
    "ajnart",
@@ -1,130 +1,3 @@
-## [1.73.0](https://github.com/homarr-labs/homarr/compare/v1.72.0...v1.73.0) (2026-07-31)
-
-## [1.72.0](https://github.com/homarr-labs/homarr/compare/v1.71.0...v1.72.0) (2026-07-24)
-
-## [1.71.0](https://github.com/homarr-labs/homarr/compare/v1.70.0...v1.71.0) (2026-07-17)
-
-## [1.70.0](https://github.com/homarr-labs/homarr/compare/v1.69.2...v1.70.0) (2026-07-10)
-
-## [1.69.2](https://github.com/homarr-labs/homarr/compare/v1.69.1...v1.69.2) (2026-07-06)
-
-### Bug Fixes
-
-* **layout:** raise AppShellHeader z-index above Indicator dots ([687edb9](https://github.com/homarr-labs/homarr/commit/687edb9226307cb83986097abb24fe7f672e1778)), closes [#6194](https://github.com/homarr-labs/homarr/issues/6194)
-
-## [1.69.1](https://github.com/homarr-labs/homarr/compare/v1.69.0...v1.69.1) (2026-07-04)
-
-### Bug Fixes
-
-* unblock query cache mutations in demo mode and add cache buster ([#6176](https://github.com/homarr-labs/homarr/issues/6176)) ([a382c75](https://github.com/homarr-labs/homarr/commit/a382c75968e73bafff55b5890b1e95f0779b50d3))
-
-## [1.69.0](https://github.com/homarr-labs/homarr/compare/v1.68.1...v1.69.0) (2026-07-03)
-
-### Features
-
-* add per-widget secret storage for release provider authentication ([77884a3](https://github.com/homarr-labs/homarr/commit/77884a31794e12a6f7bc59d96c8f61aa429ca68d))
-* **config:** enable pnpm global virtual store for worktree support ([#6098](https://github.com/homarr-labs/homarr/issues/6098)) ([3864727](https://github.com/homarr-labs/homarr/commit/3864727502a64052c4e3838468094b30bf04a133))
-* **docker-widget:** add per-column visibility toggle ([#6093](https://github.com/homarr-labs/homarr/issues/6093)) ([0765262](https://github.com/homarr-labs/homarr/commit/076526293d13379004461633d7ba4c2e83bd5ffe))
-* **docs:** addd in documentation for archiveteam warrior ([f66469d](https://github.com/homarr-labs/homarr/commit/f66469d79797a2da214588f4e8253b03633c59a5))
-* simplify caching — TanStack Query as single source of truth ([#6075](https://github.com/homarr-labs/homarr/issues/6075)) ([f19033e](https://github.com/homarr-labs/homarr/commit/f19033e0d53d248aed678737f3d04d5d8c7815b5))
-* **widgets:** right-click context menu with auto-generated toggle actions ([#6126](https://github.com/homarr-labs/homarr/issues/6126)) ([7e58858](https://github.com/homarr-labs/homarr/commit/7e58858353ae866efd657270d4bb16d2c7d3e551))
-* **widgets:** show calendar events on hover with pin on click ([#2637](https://github.com/homarr-labs/homarr/issues/2637)) ([#6081](https://github.com/homarr-labs/homarr/issues/6081)) ([db3d588](https://github.com/homarr-labs/homarr/commit/db3d58821e4de8d46b110125d0fa36919765248f))
-
-### Bug Fixes
-
-* add id to repository schema and handle missing ids gracefully ([8747d5f](https://github.com/homarr-labs/homarr/commit/8747d5f93ee9a295aad3c7035e8c6c7080bf5ee6))
-* address PR review - atomic upsert, MCP metadata, stale tokens, save UX ([757d598](https://github.com/homarr-labs/homarr/commit/757d59854e5ec82d91c053b8bc3d7eaf2e70efc4))
-* address PR review findings for widget-only integration refactor ([c892731](https://github.com/homarr-labs/homarr/commit/c892731479b47fab6218bd1f52fa6eccbdaa371e))
-* address review - paginate GH releases, GitLab tag_name, docs, test ([e687bc8](https://github.com/homarr-labs/homarr/commit/e687bc8c9277797acaa164a09c74b3808a2cb346))
-* apply version filter to LinuxServer.io provider ([34d976e](https://github.com/homarr-labs/homarr/commit/34d976eeea09e396334ce8fce5c492c07e7dd32b))
-* catch individual repo fetch failures to prevent batch crashes ([d893515](https://github.com/homarr-labs/homarr/commit/d893515b932608ea08c9c6e90b83f340e40f6f8e))
-* compile versionRegex once and add fetch timeouts ([64c7512](https://github.com/homarr-labs/homarr/commit/64c75122833981a49e9c8bf1789d501faff6d62d))
-* **deps:** update dependency postcss to ^8.5.16 ([#6169](https://github.com/homarr-labs/homarr/issues/6169)) ([9252fdc](https://github.com/homarr-labs/homarr/commit/9252fdc13971bd982224a31d7be577112f99ec45))
-* dns-hole widgets showing stale disconnected state ([#6096](https://github.com/homarr-labs/homarr/issues/6096)) ([2443f1c](https://github.com/homarr-labs/homarr/commit/2443f1cd3ff6765a91783d60d42aa03d9ba63fcd))
-* gracefully degrade when widget_secret table is missing or access denied ([30107e4](https://github.com/homarr-labs/homarr/commit/30107e4e76a454ff7402de9a8bc2e0dd6f422aa8))
-* handle missing widgetSecrets table and add default releases repo ([af35a50](https://github.com/homarr-labs/homarr/commit/af35a50fa05fee2f0118e98727eb108b0200f762))
-* **immich:** v3 API compatibility — use searchAssets for album assets, drop deviceAssetId ([#5977](https://github.com/homarr-labs/homarr/issues/5977)) ([a5ec880](https://github.com/homarr-labs/homarr/commit/a5ec880eec276e0814d2ab3ed7f9bc0b804d0465))
-* quick wins — calendar, about, glances, admin UX, releases, iframe, notes ([#6116](https://github.com/homarr-labs/homarr/issues/6116)) ([f9da71a](https://github.com/homarr-labs/homarr/commit/f9da71a19bdfa589aafe26b164d0e0782208ac0a))
-* restore ArchiveTeam Warrior as a proper integration ([8a5ad58](https://github.com/homarr-labs/homarr/commit/8a5ad5861ba4c2d0978f1fa3f6115a1c5974f8a2))
-* **timetable:** restore station search by removing disabled query guard ([d670b69](https://github.com/homarr-labs/homarr/commit/d670b6939672932c1a3d17ab9913901491cb46e3))
-* update CHANGES.md for ArchiveTeam Warrior restoration, remove typo translation key ([62baaf7](https://github.com/homarr-labs/homarr/commit/62baaf78130c4b74e899a948cee17097d8c02593))
-* verbose error messages in all release providers ([2155f13](https://github.com/homarr-labs/homarr/commit/2155f13f245f601b99458e227b6e058fbfa44cd9))
-* **widgets:** make downloads widget table background transparent ([#6025](https://github.com/homarr-labs/homarr/issues/6025)) ([73bed51](https://github.com/homarr-labs/homarr/commit/73bed51df895250f415efd7a87e721e403b3fd99))
-
-## [1.68.1](https://github.com/homarr-labs/homarr/compare/v1.68.0...v1.68.1) (2026-06-30)
-
-### Bug Fixes
-
-* make source maps opt-in to restore v1.67.0 memory baseline ([57ef0af](https://github.com/homarr-labs/homarr/commit/57ef0af4a252ea39727caeba7e13587dabc6254e)), closes [#6123](https://github.com/homarr-labs/homarr/issues/6123)
-* revert production source maps to restore v1.67.0 memory baseline ([60a69e3](https://github.com/homarr-labs/homarr/commit/60a69e31efc7168b8f4309daf75954d7730d883b)), closes [#6123](https://github.com/homarr-labs/homarr/issues/6123)
-
-## [1.68.0](https://github.com/homarr-labs/homarr/compare/v1.67.0...v1.68.0) (2026-06-26)
-
-### Features
-
-* add VPN status widget ([#5812](https://github.com/homarr-labs/homarr/issues/5812)) ([a2bb53a](https://github.com/homarr-labs/homarr/commit/a2bb53a8b8fd17da3d2e23851b75d4e179f66225))
-* re-add Docker quick-access button in user menu ([#6054](https://github.com/homarr-labs/homarr/issues/6054)) ([abd1635](https://github.com/homarr-labs/homarr/commit/abd16354bc9ef3dddbb497fd16b03476535046ac)), closes [#2165](https://github.com/homarr-labs/homarr/issues/2165)
-* ship source maps for readable production stack traces ([#6031](https://github.com/homarr-labs/homarr/issues/6031)) ([89380f8](https://github.com/homarr-labs/homarr/commit/89380f81ddd132f5b1041a8f2c3b6c6b138923dd))
-
-### Bug Fixes
-
-* **beszel:** harden cache layer and prevent blank widgets ([#6052](https://github.com/homarr-labs/homarr/issues/6052)) ([49c2663](https://github.com/homarr-labs/homarr/commit/49c266374df12fea2404710232ced42e2de11dbf)), closes [#6030](https://github.com/homarr-labs/homarr/issues/6030)
-* **beszel:** improve stats date display, add click-to-stats modal, fix grid ordering ([#6026](https://github.com/homarr-labs/homarr/issues/6026)) ([55fb227](https://github.com/homarr-labs/homarr/commit/55fb227305fe51963e486ffb25c4ce6811a2f0e4))
-* **beszel:** leverage TanStack Query for stale-while-revalidate caching ([#6055](https://github.com/homarr-labs/homarr/issues/6055)) ([bbc4589](https://github.com/homarr-labs/homarr/commit/bbc4589c9e1608721fb58a6f9b03cca8d65c1c4a))
-* **beszel:** use 480m interval for 1w/30d stats views ([4383da3](https://github.com/homarr-labs/homarr/commit/4383da38ef634327c288626c58480cc1e5a2f805))
-* **beszel:** widget transparency, error handling, and cache invalidation ([#5993](https://github.com/homarr-labs/homarr/issues/5993)) ([39e4245](https://github.com/homarr-labs/homarr/commit/39e424563a3187dcf0dba5f654e2225be76aef51))
-* **icon-picker:** keep URL visible in edit mode, add SVG-first ordering ([#6051](https://github.com/homarr-labs/homarr/issues/6051)) ([e01571b](https://github.com/homarr-labs/homarr/commit/e01571b221812cd19a6d67ebe3cf44432104ec27))
-* **integrations:** prevent certificate trust button from submitting the form ([#6020](https://github.com/homarr-labs/homarr/issues/6020)) ([0f66bfd](https://github.com/homarr-labs/homarr/commit/0f66bfd6c128253ba644d80d7c908de5314cf997))
-* **manage/about:** bypass self-fetch + add manage error boundary (LLM exploration) ([#6009](https://github.com/homarr-labs/homarr/issues/6009)) ([19f9769](https://github.com/homarr-labs/homarr/commit/19f9769d9e669d56d793e9f6a0d265316113d743)), closes [#6008](https://github.com/homarr-labs/homarr/issues/6008) [#6008](https://github.com/homarr-labs/homarr/issues/6008) [#6008](https://github.com/homarr-labs/homarr/issues/6008)
-* **plex:** use series title for media releases instead of season label ([#6083](https://github.com/homarr-labs/homarr/issues/6083)) ([2443b89](https://github.com/homarr-labs/homarr/commit/2443b89b46f88fddbf41f0382a9f3bc5469c6fa8))
-* show app first in add item modal ([#6087](https://github.com/homarr-labs/homarr/issues/6087)) ([915c8a3](https://github.com/homarr-labs/homarr/commit/915c8a3501551fdccf786d0c34dc01107d873ce0))
-* **truenas:** report actual memory usage and pool free space ([#6017](https://github.com/homarr-labs/homarr/issues/6017)) ([f69e545](https://github.com/homarr-labs/homarr/commit/f69e545d6429aece0e55975c3b2426f20e91e545))
-* **unraid:** report disk free space instead of total size ([#6018](https://github.com/homarr-labs/homarr/issues/6018)) ([1fb97ee](https://github.com/homarr-labs/homarr/commit/1fb97ee9c6fbe656a7dd3a9d1e436125982533f4))
-* **widgets:** clean up health monitoring disk and size display ([#6019](https://github.com/homarr-labs/homarr/issues/6019)) ([e29c79a](https://github.com/homarr-labs/homarr/commit/e29c79a9028d9311dcb3d8323e0950a444589c7a))
-* **widgets:** hide health monitoring default tab option for non-proxmox integrations ([#6021](https://github.com/homarr-labs/homarr/issues/6021)) ([52df56b](https://github.com/homarr-labs/homarr/commit/52df56b19da8e0bcb6c2e5df47b7936ec63f3149))
-* **widgets:** hide system disk usage value when it overflows and show it in a tooltip ([#6022](https://github.com/homarr-labs/homarr/issues/6022)) ([a19c9d8](https://github.com/homarr-labs/homarr/commit/a19c9d88caacc86b42854c732818f0b5e5cc8dd5))
-
-## [1.67.0](https://github.com/homarr-labs/homarr/compare/v1.66.1...v1.67.0) (2026-06-19)
-
-### Features
-
-* **analytics:** migrate from Umami to PostHog server-side analytics ([#5983](https://github.com/homarr-labs/homarr/issues/5983)) ([d059023](https://github.com/homarr-labs/homarr/commit/d059023b51a323df027c1cf033454440bd0d7e57))
-* Calculate and display total CPU and memory usage ([#5911](https://github.com/homarr-labs/homarr/issues/5911)) ([d9cbd54](https://github.com/homarr-labs/homarr/commit/d9cbd5427d0e5be3e5dbecca8d6069dc8074d810))
-
-### Bug Fixes
-
-* **auth:** isolate session cookies from other Auth.js apps on same host ([#5996](https://github.com/homarr-labs/homarr/issues/5996)) ([e1a245f](https://github.com/homarr-labs/homarr/commit/e1a245ff2d8520d08957c4a7dbe01d039607a973))
-* **deps:** update tailwindcss monorepo to ^4.3.1 ([#5988](https://github.com/homarr-labs/homarr/issues/5988)) ([78b6e52](https://github.com/homarr-labs/homarr/commit/78b6e520ac095129398d3da8f2441df408e93e9f))
-* **downloads:** sort stalled torrents last when sorting by finish time ([#6011](https://github.com/homarr-labs/homarr/issues/6011)) ([c56d9d6](https://github.com/homarr-labs/homarr/commit/c56d9d6894c717b5c70ab75d6a100d4d1071c2d3)), closes [#5416](https://github.com/homarr-labs/homarr/issues/5416)
-
-## [1.65.0](https://github.com/homarr-labs/homarr/compare/v1.64.0...v1.65.0) (2026-06-12)
-
-### Features
-
-* add MCP server for AI assistant integration ([#5882](https://github.com/homarr-labs/homarr/issues/5882)) ([6baff7b](https://github.com/homarr-labs/homarr/commit/6baff7be3dc8f2473d93d17862b6d0b2df5c4d15))
-* add Technitium DNS integration, usable with DNS Hole widgets ([#5832](https://github.com/homarr-labs/homarr/issues/5832)) ([cd1a82a](https://github.com/homarr-labs/homarr/commit/cd1a82a640101cdca88d1e825edb11bd51f5ce66))
-* add Uptime Kuma, Audiobookshelf, Paperless-ngx, and Navidrome integrations ([#5910](https://github.com/homarr-labs/homarr/issues/5910)) ([d77c6f8](https://github.com/homarr-labs/homarr/commit/d77c6f8d4e50108f50831ee365e382a535acb254))
-* **beszel:** add Beszel integration with system monitoring widgets ([#5900](https://github.com/homarr-labs/homarr/issues/5900)) ([a4db9cf](https://github.com/homarr-labs/homarr/commit/a4db9cf0dcd8034015064f9d23f2d351b1d0c50a))
-* **board:** add widget hover overlay on dashboard ([#5888](https://github.com/homarr-labs/homarr/issues/5888)) ([29bd710](https://github.com/homarr-labs/homarr/commit/29bd7101b180acfb750c7d4414c30bd6450065e2))
-* custom widgets ([#5889](https://github.com/homarr-labs/homarr/issues/5889)) ([aecbca2](https://github.com/homarr-labs/homarr/commit/aecbca2b81ad1693c599e3168fd0c0723311b3b4))
-* **docs:** migrate documentation site into monorepo ([#5912](https://github.com/homarr-labs/homarr/issues/5912)) ([9e421c6](https://github.com/homarr-labs/homarr/commit/9e421c67bd87b5b7065118afedd08e7eb2140773))
-* **lang:** add Finnish language support ([#5892](https://github.com/homarr-labs/homarr/issues/5892)) ([2fb7bde](https://github.com/homarr-labs/homarr/commit/2fb7bde9002c2670aa49db804e352c3821fa8097))
-* search widgets by integration type when adding items ([#5909](https://github.com/homarr-labs/homarr/issues/5909)) ([48e1844](https://github.com/homarr-labs/homarr/commit/48e1844b5b9dc6d322bc22a972fdd29b6e03d3d2))
-* SQLite backup & restore with WASM preview ([#5887](https://github.com/homarr-labs/homarr/issues/5887)) ([5d1f268](https://github.com/homarr-labs/homarr/commit/5d1f268438b84bd19f5a79658a43931dd874cd41))
-* **ui:** add global query cache leveraging Redis ([#5811](https://github.com/homarr-labs/homarr/issues/5811)) ([74443a4](https://github.com/homarr-labs/homarr/commit/74443a49b2330b7d71c5ccdb873c61b270d1c72a))
-
-### Bug Fixes
-
-* **boards:** add permissions to board summary schema to fix manage page crash ([#5917](https://github.com/homarr-labs/homarr/issues/5917)) ([a42af0e](https://github.com/homarr-labs/homarr/commit/a42af0e678b58b6c63a8bac4978fb2951c6ddef8))
-* **ci:** rename baseBranches to baseBranchPatterns in renovate config ([15e061c](https://github.com/homarr-labs/homarr/commit/15e061cf03f2301996aaf11a25095194e5759fb5))
-* **db:** inline custom widget seed data to fix CJS migration crash ([f26007a](https://github.com/homarr-labs/homarr/commit/f26007a29a0b04765baba72122d38a9e5c639a0b))
-* **definitions:** gracefully handle sitemap fetch failure in codegen ([7f8b012](https://github.com/homarr-labs/homarr/commit/7f8b0121b303fa09a213c73e6a690463e9fc6b44))
-* **docs:** add trailingSlash for GitHub Pages compatibility ([28ceb37](https://github.com/homarr-labs/homarr/commit/28ceb37cbfe45f8ce45fd88e6a8c87ffe4c9b5c2))
-* **docs:** disable swcHtmlMinimizer and fix broken links ([905f795](https://github.com/homarr-labs/homarr/commit/905f795b5607744d0aeec4bb65d84aabd1505047))
-* gracefully skip widgets with unknown kind instead of crashing ([#5915](https://github.com/homarr-labs/homarr/issues/5915)) ([484b8cf](https://github.com/homarr-labs/homarr/commit/484b8cf9f18122a298dc7fae1027653cd287c09c))
-* **image-proxy:** use ArrayBuffer instead of Blob to prevent OOM on Node v24 ([#5926](https://github.com/homarr-labs/homarr/issues/5926)) ([3e464a7](https://github.com/homarr-labs/homarr/commit/3e464a76f2d1e5985f259270a4258f3db4f17c18))
-* **integrations:** support truenas json-rpc api, certificate trust, and api key auth ([#5861](https://github.com/homarr-labs/homarr/issues/5861)) ([f6d5f97](https://github.com/homarr-labs/homarr/commit/f6d5f97933cd257ee8851f2d6a27f56e2942076d))
-
 ## [1.64.0](https://github.com/homarr-labs/homarr/compare/v1.63.0...v1.64.0) (2026-06-05)

 ### Features
@@ -1,96 +0,0 @@
-# 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`.
@@ -1,220 +1,7 @@
 # ── CODEOWNERS ───────────────────────────────────────
 * @homarr-labs/maintainers

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

 FROM base AS builder
+RUN apk add --no-cache libc6-compat
+RUN apk update
+
+# Set working directory
 WORKDIR /app
-RUN apk add --no-cache libc6-compat curl bash && apk update
-
-RUN corepack enable pnpm
-COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
-COPY patches ./patches
-# Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
-# are configured with nodeLinker: hoisted. The applyPatchToDir function tries
-# to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
-# content-addressable store is populated). By temporarily switching to the
-# isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
-# which IS created by pnpm fetch. The original hoisted linker is restored
-# before the install step so the final node_modules layout stays flat.
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm config set store-dir /pnpm/store && \
-    sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
-    pnpm fetch && \
-    sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml
-
+RUN apk add --no-cache libc6-compat curl bash
+RUN apk update
 COPY . .
-# Follow the pnpm fetch pattern from https://pnpm.io/cli/fetch
-# --frozen-lockfile is omitted as recommended by the pnpm fetch docs
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm install --recursive

+RUN corepack enable pnpm && pnpm install --recursive --frozen-lockfile
+
+# Copy static data as it is not part of the build
+COPY static-data ./static-data
 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
 ARG DISABLE_REDIS_LOGS='true'
-ARG TARGETPLATFORM

-RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
-    --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \
-    --mount=type=secret,id=TURBO_TOKEN,env=TURBO_TOKEN \
-    --mount=type=secret,id=TURBO_REMOTE_CACHE_SIGNATURE_KEY,env=TURBO_REMOTE_CACHE_SIGNATURE_KEY \
-    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" pnpm build
+RUN corepack enable pnpm && pnpm build

 FROM base AS runner
 WORKDIR /app
@@ -61,7 +42,6 @@ RUN mkdir -p /var/cache/nginx && \

 COPY --from=builder /app/apps/nextjs/next.config.ts .
 COPY --from=builder /app/apps/nextjs/package.json .
-COPY --from=builder /app/pnpm-workspace.yaml ./pnpm-workspace.yaml

 COPY --from=builder /app/node_modules/better-sqlite3/build/Release/better_sqlite3.node /app/build/better_sqlite3.node

@@ -1,29 +0,0 @@
-# Product
-
-## Users
-
-Homarr serves people and teams who run self-hosted applications and want one dependable dashboard for launching apps, monitoring services, and viewing live operational data. They use it across wall displays, desktops, tablets, and smaller devices, often returning to the same board many times per day.
-
-## Product Purpose
-
-Homarr makes self-hosted services easy to find, understand, and operate without hand-editing configuration files. A successful board loads immediately, stays visually stable, keeps widgets legible across screen sizes, and makes editing feel direct and forgiving.
-
-## Brand Personality
-
-Fast, capable, and approachable. Homarr should feel like a mature productivity tool: dense when useful, calm in view mode, and explicit about state during editing.
-
-## Anti-references
-
-Avoid cramped tile spacing, undersized text, layout shifts, decorative motion, hidden drag targets, modal-heavy positioning controls, and dashboards that require users to understand grid internals. Editing must not make the read-only experience heavier or slower.
-
-## Design Principles
-
- Preserve the board: viewing is the primary workflow and must render before editor code is needed.
- Make spatial actions direct: moving, resizing, nesting, and using fixed sidebars should happen on the canvas with immediate feedback.
- Keep content predictable: fixed logical tile sizes preserve widget composition, typography, and controls at every viewport.
- Recover gracefully: collision handling, reflow, loading states, and persistence failures must never lose or obscure content.
- Use familiar controls: Mantine patterns, clear labels, keyboard support, and visible focus states take priority over novel decoration.
-
-## Accessibility & Inclusion
-
-Target WCAG 2.2 AA. Maintain keyboard equivalents for drag and resize operations, useful landmarks and announcements, sufficient contrast, readable control sizes, reduced-motion support, and horizontal scrolling before scaling content below an accessible minimum.
@@ -23,6 +23,9 @@
    "react-hooks/exhaustive-deps": "warn",
    "eslint/no-unused-expressions": "warn"
  },
+  "options": {
+    "reportUnusedDisableDirectives": "off"
+  },
  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", ".docusaurus/**", "build/**"],
  "settings": {
    "react": { "version": "19" }
@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve("@docusaurus/core/lib/babel/preset")],
+};
@@ -55,9 +55,9 @@ A random secret can be generated by using the following command: `openssl rand -

 | 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` | - |
+| ``DOCKER_HOSTNAMES``          | Comma seperated list of hostnames to connect to | For example `localhost,docker.example.com` | - |
+| ``DOCKER_PORTS``             | Comma seperated list of ports to connect to | For example `2375,2376` | - |
+| ``DOCKER_SOCKET_PATHS``             | Comma seperated list of paths to sockets | For example `/var/run/docker.sock,/run/user/1000/podman/podman.sock` | - |

 ## Database
 | Environment Variable     | Description | Possible values | Default |
@@ -23,7 +23,6 @@ Homarr supports multiple authentication options, from internal userbase (credent
 | AUTH_PROVIDERS             | Select Which provider to use between *credentials*, *ldap* and *oidc*. <br /> Multiple providers can be enabled with by separating them with `,`, (ex. `AUTH_PROVIDERS=credentials,oidc`, it is highly recommended to just enable one provider).  |  credentials  |
 | AUTH_LOGOUT_REDIRECT_URL  | URL to redirect to after clicking logging out.  | --- |
 | AUTH_SESSION_EXPIRY_TIME  | Time for the session to time out. Can be set as pure number, which will automatically be used in seconds, or followed by s, m, h or d for seconds, minutes, hours or days. (ex: "30m") | "30d"  |
-| AUTH_COOKIE_PREFIX  | Prefix used for all authentication cookies (session, csrf, callback, pkce, state, nonce). Change this if you run another Auth.js/NextAuth app on the same hostname as Homarr (browsers scope cookies by host, not by port) to avoid cookie name collisions. Only letters, numbers, hyphens and underscores are allowed. | `homarr`  |

 <Tabs>
  <TabItem value="credentials" label="Credentials Provider" default>
@@ -125,10 +124,6 @@ Homarr supports multiple authentication options, from internal userbase (credent

    Roles are fetched from group claims. This can also be changed to roles for example added to a azure app registration by using the `AUTH_OIDC_GROUPS_ATTRIBUTE`.

-    If you'd rather manage group memberships for OIDC users locally (instead of via the IdP), set `AUTH_OIDC_GROUPS_LOCAL_MANAGEMENT=true`. While enabled, Homarr stops syncing OIDC users' group memberships from the groups claim, and admins can add/remove OIDC users on a group's members page. If you turn this back to `false`, the next login of each user resumes the regular sync and reconciles their groups with the IdP's claim again, which may remove memberships that were added manually while local management was enabled.
-
-    To let an existing credentials user also sign in with OIDC, set `AUTH_OIDC_ENABLE_DANGEROUS_CREDENTIALS_LINKING=true`. On the first OIDC sign-in, Homarr links a credentials user with the same email address instead of creating a second user. The user keeps their password login, local username and profile, groups, permissions, boards, settings, and API keys. OIDC profile and group claims do not overwrite the credentials-owned data. Homarr requires the OIDC profile to contain `email_verified: true` while this option is enabled. Only enable this when your OIDC provider verifies email addresses, because a matching email could otherwise be used to take over an existing account.
-
    <details>
      <summary>
        Example Setup
@@ -202,11 +197,9 @@ Homarr supports multiple authentication options, from internal userbase (credent
    | ``AUTH_OIDC_AUTO_LOGIN``    | Automatically redirect to OIDC login                       | false         |
    | ``AUTH_OIDC_SCOPE_OVERWRITE`` | Overwrite default scopes (openid, profile, email)        | openid email profile groups           |
    | ``AUTH_OIDC_GROUPS_ATTRIBUTE`` | Attribute used for groups (roles) claim                  | groups        |
-    | ``AUTH_OIDC_GROUPS_LOCAL_MANAGEMENT`` | Stop syncing group memberships of OIDC users from the groups claim and manage them locally via the group members page instead | false |
    | ``AUTH_OIDC_NAME_ATTRIBUTE_OVERWRITE`` | Overwrite name attribute. By default it will use preferred_username if it does not contain a `@` and otherwise name. | ---          |
    | ``AUTH_OIDC_FORCE_USERINFO`` | Force userinfo endpoint to be used for user information.    | false         |
    | ``AUTH_OIDC_ENABLE_DANGEROUS_ACCOUNT_LINKING`` | Enable account linking for OIDC provider. This will link the OIDC accounts by email. Be sure that you have verified emails to prevent stealing accounts. | false |
-    | ``AUTH_OIDC_ENABLE_DANGEROUS_CREDENTIALS_LINKING`` | Link an OIDC identity to an existing credentials user with the same email. The credentials login and existing user data are preserved. Requires the OIDC profile to contain `email_verified: true`. | false |
    | ``AUTH_OIDC_TOKEN_ENDPOINT_AUTH_METHOD`` | Override method for the token endpoint authentication. Supported values are `client_secret_basic`, `client_secret_post`, `client_secret_jwt` and `none`. | client_secret_basic |

    ### Permission System
@@ -22,4 +22,4 @@ Homarr is completely free to use. We'd highly appreciate if you consider donatin
 ## Where to donate
 We accept donations on our official [OpenCollective](https://opencollective.com/homarr).
 You may also sponsor us directly by providing a useful service / product to us other means.
-You can get into contact with us [here](/docs/community/get-in-touch).
+You can get into contact with us [here](./get-in-touch).
@@ -21,14 +21,13 @@ import manageImportDecryptionToken from "./img/old-homarr-import-decryption-toke

 :::tip

-Read our [glossary](/docs/getting-started/glossary) if you are new to Homarr.
+Read our [glossary](./glossary) if you are new to Homarr.

 :::

 Congratulations on installing Homarr. Now it's time to get yourself familiar with the concepts of Homarr and how to use it.

 ## Onboarding
-
 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.

@@ -46,64 +45,50 @@ You can either import a previous dashboard using the ZIP archive or start from s
 You may refresh anytime and continue from a different device - the onboarding is saved immediately on the server for your convenience.

 ### Starting from scratch
-
 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.
+If 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 it's boards.
+You must choose an username and password (both can later be changed).
+We enforce strict password requirements, when you enter your password, to protect your instance if you accidentially
+expose it to the Internet.

 <img src={imageStartFromScratchStepAdminUser} alt={"Screenshot form to create admin user"} width={300} />

 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.
+This group will be used to synchronize users from your provider to Homarr. 
+When a user is logged in through the provider the groups of him that match groups with any in Homarr will be added to the user.
+The name of the group has to match exactly the name of the group in the provider.

-<img
-  src={imageStartFromScratchStepExternalAdminGroup}
-  alt={"Screenshot form to create external admin group"}
-  width={300}
-/>
+<img src={imageStartFromScratchStepExternalAdminGroup} alt={"Screenshot form to create external admin group"} width={300} />

 Next, you can configure some basic settings for Homarr. We recommend to leave all settings at default for most users.
 Here you can also disable analytics. Please note that our analytics are completly anonymous and is fully compliant with GDPR and PECR.

-<img
-  src={imageStartFromScratchStepServerSettings}
-  alt={"Screenshot of analytics and indexing settings in the onboarding"}
-  width={300}
-/>
+<img src={imageStartFromScratchStepServerSettings} alt={"Screenshot of analytics and indexing settings in the onboarding"} width={300} />

 ### Setting up integrations

 After configuring server settings, the onboarding guides you through setting up your integrations.

 #### Docker service discovery
-
 If Docker is available (socket mounted), Homarr automatically detects running containers and matches them to known integration types.
 Matching integrations are pre-selected in the integration list, saving you from manually picking each one.

 #### URL templating
-
 You can define a base URL template to auto-fill integration URLs in bulk.
 Two modes are supported:
-
- **Subdomain mode** - e.g. `{app}.example.com` where `{app}` is replaced with the integration name
- **Port mode** - e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port
+- **Subdomain mode** — e.g. `{app}.example.com` where `{app}` is replaced with the integration name
+- **Port mode** — e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port

 #### API key helper links
-
 For integrations that require API keys (such as Sonarr, Radarr, SABnzbd, or Seerr), a helper link opens the relevant settings page in the target application so you can quickly copy your key.

 #### Creating apps from Docker containers
-
 You can optionally auto-create bookmark apps for all discovered Docker containers, making them immediately available on your board.

 :::note

-Release providers and Search.ch are configured directly in their widgets instead of the integrations page.
+Some niche and registry integrations (GitHub, npm, Docker Hub, GitLab, Codeberg, LinuxServer.io, GHCR, Quay, Search.ch) are hidden from the onboarding selection grid but remain available on the manage integrations page.

 :::

@@ -115,31 +100,27 @@ We recommend you to continue with the section [creating your first board on this
 <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`.
+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`
+Copy it and do not loose it!
+5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose ``Import from Homarr before 1.0``
 6. Drag and drop your previously downloaded ZIP archive into the file upload: <br/><img src={manageImportOldHomarrDropzone} style={{ maxWidth: 500 }} />
 7. Next, choose the data that you want to import and how to import it. Since screen sizes were removed in 1.0, we create a new board for every screen size by default. We recommend you to only keep the best layout and adjust it later in 1.0.0 - but you can also import all of them and pick later.<br/><img src={manageImportOldHomarrChooseData} style={{ maxWidth: 500 }} />
 8. If you previously exported integrations or users, you will be asked to decrypt the data safely using your obtained encryption token. Paste into the modal and confirm your action.<br/><img src={manageImportDecryptionToken} style={{ maxWidth: 500 }} />
 9. Next, you can [follow the same setup as when starting from scratch](#starting-from-scratch). After you completed the onboarding, all of your data will be migrated and available.

 ## Creating your first board
-
 In Homarr, you organize your apps and widgets on boards.
-Boards use fixed-size tiles so the same widget keeps the same proportions on every screen.
-Drag, resize, and section controls are available in edit mode.
-Let's create your first board by navigating here: `Manage` > `Boards` > `New board`:
+Boards can be organized using the interactive drag and drop.
+Let's create your first board by navigating here: ``Manage`` > ``Boards`` > ``New board``:
 ![](./img/manage-create-board-button.png)

 A board must always have a name and can either be public or private.
@@ -152,13 +133,12 @@ Congratulations - you've just created your first board. You can see boards, that
 ![](./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.
+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.

@@ -169,9 +149,8 @@ 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:
+To do this, edit your previously created board by clicking on the big ``Open board`` button:

 ![](./img/manage-view-board.png)

@@ -189,7 +168,7 @@ 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 button to save your changes and exit edit mode.
+- **Exit edit mode**: Click this btuton to save your changes and exit edit mode.

 To continue, click the option "New Item":

@@ -214,28 +193,21 @@ 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.
-Use the resize handle at the bottom right to resize the tile.
-Press and hold the handle, move the pointer, and release it when the tile has the size you want.
+Using the small bidirectional arrow at the bottom right you can resize the element.
+Start pressing with your mouse button down, move your mouse to resize and release your finger as soon your you're happy with the size.

 ![](./img/resize-item.gif)

-To move a tile in edit mode, press and hold its content, move it to the desired position, and release it.
-Widget content is disabled while editing so its controls do not intercept the drag; use the tile's settings button for edit actions.
-The tile snaps to the grid. Equally-sized tiles swap when one is dropped into the other's slot, while other neighboring tiles move out of the way automatically.
+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)

-Every `1 × 1` tile has a logical content size of `200 × 200` pixels.
-Larger tiles use multiples of that fixed unit, with a consistent gap between cells.
-Homarr scales the complete board uniformly, like zooming a page.
-It stops shrinking at 75% and lets you scroll horizontally instead of making text and controls too small.
-It does not squeeze or reflow the content of individual widgets, so a widget keeps the same design and proportions across screen sizes.
-
 :::note

-Viewing a board initially uses the lightweight, non-interactive layout.
-For users with edit access, Homarr prepares drag-and-drop and resize controls in the background after the board becomes interactive.
-If you enter edit mode before that finishes, the existing board stays visible until the editor is ready.
+You cannot move items freely on the vertical axis.
+We always align all items to the top of the page to simply organization.
+To move items to the bottom, you must add more items or resize items.

 :::

@@ -246,10 +218,8 @@ This helps you to explore the capabilities of Homarr before you build your board

 :::

-Keyboard users can focus a tile, press Enter or Space, then use arrow keys to move and Shift plus arrow keys to resize.
-Press Escape to stop.
-For precise numeric controls or touch input, choose **Move / resize item** from the tile's edit menu.
-The dialog can also move the tile to another section or fixed sidebar:
+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)

@@ -258,18 +228,17 @@ 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).
+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`.
+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.

@@ -285,14 +254,13 @@ 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.
+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)
@@ -321,72 +289,68 @@ As with every change, don't forget to save your changes using the exit edit mode

 ![](./img/exit-edit-mode.png)

-## Organizing items with sections
+## 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.

-Sections are resizable containers for apps, widgets, and other sections.
-The same section works on the main canvas and inside a fixed sidebar.
-Each section can configure:
-
- Show or hide its label.
- Allow or disable collapsing.
- Show or hide **Open all in new tabs**.
- Change its border color and custom CSS classes.
+### Using dynamic sections
+Dynamic sections are a simple, resizable visual group to group items.

 ![](./img/create-dynamic-section.png)

-After adding a section, drag and resize it like any other tile, then drag items into it:
+After adding a dynamic section, you can simply drag and drop items into the section:

 ![](./img/dynamic-section.gif)

-### Labeled and collapsible sections
+### Using categories
+Categories are more advanced and complicated than dynamic sections.
+To create a category, open the add item modal and choose "new category":

-Open the add-content menu and choose **New section**.
-Use its settings menu to add a label and enable the behavior you want.
-In edit mode, move items into or out of the section directly.
-In view mode, each user can collapse eligible sections without changing the saved board layout.
-If **Open all in new tabs** is enabled, the section menu can open every app link it contains.
+![](./img/add-category.png)

-### Fixed sidebars
+Every category must have a name. After you click "Add category", you will get a new item on your board:

-Open the board's **Layout** settings to enable the left or right sidebar for each responsive layout.
-Choose one, two, or three columns with the slider and use the preview to check the remaining canvas width.
-The sidebar reserves those columns from the dashboard, so Homarr moves canvas items into the next available positions.
-Sidebar content stays visible while the page scrolls and remains editable.
+![](./img/category.gif)

-Existing categories become sections automatically, and category rails become fixed sidebars.
+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/)
+- Create new apps using the [apps management](../management/apps/)
+- Customize your board or add more boards using the [boards management](../management/boards/)
+- Integrate software that you use using the [integrations management](../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/)
+- Integrate with Homarr with your own application using [the API](../management/api/)

 :::danger

@@ -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.24.0](https://img.shields.io/badge/Version-8.24.0-informational?style=flat)
+![Version: 8.19.0](https://img.shields.io/badge/Version-8.19.0-informational?style=flat)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat)
-![AppVersion: v1.72.0](https://img.shields.io/badge/AppVersion-v1.72.0-informational?style=flat)
+![AppVersion: v1.60.0](https://img.shields.io/badge/AppVersion-v1.60.0-informational?style=flat)

 A Helm chart to deploy homarr for Kubernetes

@@ -259,7 +259,7 @@ httproute:
            value: /
      backendRefs:
        - name: homarr
-          port: 7575
+          port: 8080
 ````
 </details>

@@ -383,7 +383,6 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 | containerPorts | object | `{"http":{"port":7575,"protocol":"TCP"}}` | containerPorts defines the ports to open on the container. It is a map where each entry specifies:    - `port`     (int)    (required): The port number to expose inside the container.    - `protocol` (string) (required): The network protocol (TCP or UDP) used for the port.    - `disabled` (bool)              : Optional flag to disable this port (defaults to false). Can be overridden via Helm values.  By default, this configuration exposes TCP port 7575 with the name `http`. |
 | database.migrationEnabled | bool | `true` | Database migration configuration. DB_MIGRATIONS_DISABLED Set to `true` to disable database migrations. Migrations are enabled by default (`false`). |
 | database.type | string | `"sqlite"` | Database type: sqlite, mysql or postgresql |
-| env.AUTH_COOKIE_PREFIX | string | `"homarr"` | Prefix used for all authentication cookies. Change if you run another Auth.js/NextAuth app on the same hostname to avoid cookie name collisions. Only letters, numbers, hyphens and underscores. |
 | env.AUTH_LDAP_BASE | string | `nil` | Base dn of your LDAP server |
 | env.AUTH_LDAP_BIND_DN | string | `nil` | User used for finding users and groups |
 | env.AUTH_LDAP_GROUP_CLASS | string | `"groupOfUniqueNames"` | Class used for querying groups |
@@ -419,17 +418,17 @@ All available values are listed on the [artifacthub](https://artifacthub.io/pack
 | envSecrets.dbEncryption.key | string | `"db-encryption-key"` | Secret key for SECRET_ENCRYPTION_KEY can be generated with `openssl rand -hex 32` |
 | fullnameOverride | string | `""` | Overrides chart's fullname |
 | hostAliases | list | `[]` | Add static entries to /etc/hosts in the Pod. This is useful in the following cases: - You are running in a dual-stack cluster (IPv4 + IPv6) and want to force usage of IPv4 for specific hostnames - Your application is having DNS resolution issues or IPv6 preference issues - You need to override or simulate DNS entries without changing global DNS - You are running in an air-gapped or isolated environment without external DNS Example: hostAliases:   - ip: "192.168.1.10"     hostnames:       - "example.com"       - "example.internal" |
-| httproute | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration |
+| httproute | object | `{"enabled":false,"hostnames":["chart-example.local"],"parentRefs":[{"name":"my-gateway","namespace":"default"}],"rules":[{"backendRefs":[{"name":"homarr","port":8080}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]}` | Gateway API HTTPRoute configuration |
 | httproute.enabled | bool | `false` | Enable HTTPRoute |
 | httproute.hostnames | list | `["chart-example.local"]` | Hostnames this route matches (similar to ingress.hosts.host) |
 | httproute.parentRefs | list | `[{"name":"my-gateway","namespace":"default"}]` | References to the parent Gateway(s) this route attaches to. Each item must include at least a `name`, and optionally a `namespace`. |
-| httproute.rules | list | `[{"backendRefs":[{"name":"homarr","port":7575}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]` | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to |
+| httproute.rules | list | `[{"backendRefs":[{"name":"homarr","port":8080}],"filters":[],"matches":[{"path":{"type":"PathPrefix","value":"/"}}]}]` | List of routing rules. Each rule can include: - matches: path/header/query matching - filters: optional transformations (redirects, header modifications, etc.) - backendRefs: one or more Kubernetes Services to forward traffic to |
 | httproute.rules[0].filters | list | `[]` | Optional filters for this rule (default: empty) |
 | httproute.rules[0].matches[0].path.type | string | `"PathPrefix"` | Path match type. One of: Exact, PathPrefix, RegularExpression |
 | httproute.rules[0].matches[0].path.value | string | `"/"` | Path value to match |
 | image.pullPolicy | string | `"IfNotPresent"` | Image pull policy |
 | image.repository | string | `"ghcr.io/homarr-labs/homarr"` | Image repository |
-| image.tag | string | `"v1.72.0"` | Overrides the image tag whose default is the chart appVersion |
+| image.tag | string | `"v1.60.0"` | Overrides the image tag whose default is the chart appVersion |
 | imagePullSecrets | list | `[]` | Secrets for Docker registry |
 | ingress.annotations | object | `{}` | Ingress annotations |
 | ingress.enabled | bool | `false` | Enable ingress |
@@ -1,35 +0,0 @@
---
-title: "ArchiveTeam Warrior"
-description: "ArchiveTeam Warrior is an easy-to-run virtual machine that helps preserve websites by using some of your bandwidth and disk space to download and upload content to ArchiveTeam’s archive."
-hide_title: true
---
-
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { archiveTeamWarriorIntegration } from ".";
-
-<IntegrationHeader integration={archiveTeamWarriorIntegration} categories={["archiving"]} />
-
-The ArchiveTeam Warrior integration lets Homarr connect to your ArchiveTeam Warrior instance so you can manage and monitor your archiving tasks directly from your dashboard.
-
-### Adding the integration
-
-<AddingIntegration />
-
-### Secrets
-
-ArchiveTeam Warrior does not require authentication by default. If your instance is protected with basic authentication, you can provide a username and password.
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [],
-    },
-  ]}
-/>
@@ -1,9 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const archiveTeamWarriorIntegration: IntegrationDefinition = {
-  name: "ArchiveTeam Warrior",
-  description:
-    "ArchiveTeam Warrior is an easy-to-run virtual machine that helps preserve websites by using some of your bandwidth and disk space to download and upload content to ArchiveTeam’s archive.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/selfhst/icons/png/archiveteam-warrior.png",
-  path: "../../integrations/archiveteam-warrior",
-};
@@ -1,54 +0,0 @@
---
-title: 'Bazarr'
-description: "Bazarr is a companion application to Sonarr and Radarr that manages and downloads subtitles."
-hide_title: true
---
-
-import { IntegrationHeader } from '@site/src/components/integrations/header';
-import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
-import { AddingIntegration } from '@site/src/components/integrations/adding';
-import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
-import { bazarrIntegration } from '.';
-import { bazarrWidget } from '@site/docs/widgets/bazarr';
-
-<IntegrationHeader
-  integration={bazarrIntegration}
-  categories={['Subtitles', 'Media']}
-/>
-
-Bazarr complements Sonarr and Radarr by managing subtitle downloads. The Homarr integration uses your Bazarr API key to fetch missing subtitle counts and health badges.
-
-### Screenshots
-
-import apiKeySettings from './img/api-key-settings.png';
-import widgetOverview from '@site/docs/widgets/bazarr/img/widget-overview.png';
-
-<div className="flex flex-col gap-4">
-  <div>
-    <p>API key location in Bazarr (<strong>Settings → General → Security</strong>):</p>
-    <img src={apiKeySettings} alt="bazarr-api-key-settings" width={128 * 4} />
-  </div>
-  <div>
-    <p>Bazarr widget on a Homarr board:</p>
-    <img src={widgetOverview} alt="bazarr-widget-on-board" width={128 * 4} />
-  </div>
-</div>
-
-### Widgets & Capabilities
-<IntegrationCapabilites
-    items={[{ widget: bazarrWidget }]}
-/>
-
-### Adding the integration
-<AddingIntegration />
-
-### Secrets
-You can find your Bazarr API key under **Settings → General → Security**.
-
-<IntegrationSecrets secrets={[{
-    credentials: ['apiKey'],
-    steps: [
-      "Open Bazarr and go to Settings → General → Security.",
-      "Copy the API key and paste it into Homarr when creating the integration.",
-    ],
-}]} />
@@ -1,9 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const bazarrIntegration: IntegrationDefinition = {
-  name: "Bazarr",
-  description:
-    "Bazarr is a companion application to Sonarr and Radarr that manages and downloads subtitles for your media library.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/bazarr.svg",
-  path: "../../integrations/bazarr",
-};
@@ -0,0 +1,37 @@
+---
+title: 'Codeberg'
+description: "Codeberg is a non-profit, community-driven platform for hosting and collaborating on software projects."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { codebergIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={codebergIntegration}
+    categories={['Version Control', 'Software']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['personalAccessToken'],
+    steps: []
+}]} />
@@ -0,0 +1,9 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const codebergIntegration: IntegrationDefinition = {
+  name: "Codeberg",
+  description:
+    "Codeberg is a non-profit, community-driven platform for hosting and collaborating on software projects.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/codeberg.svg",
+  path: "../../integrations/codeberg",
+};
@@ -0,0 +1,37 @@
+---
+title: 'Docker Hub'
+description: "Docker Hub is a cloud-based registry service for sharing and managing Docker images."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { dockerHubIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={dockerHubIntegration}
+    categories={['Container Management', 'Software']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['username', 'personalAccessToken'],
+    steps: []
+}]} />
@@ -0,0 +1,8 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const dockerHubIntegration: IntegrationDefinition = {
+  name: "Docker Hub",
+  description: "Docker Hub is a cloud-based registry service for sharing and managing Docker images.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/docker.svg",
+  path: "../../integrations/docker-hub",
+};
@@ -55,83 +55,15 @@ services:
 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:
-  homarr:
-    image: ghcr.io/homarr-labs/homarr:latest
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
-    environment:
-      DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
-```
-
 ### 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
+- **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:

@@ -0,0 +1,42 @@
+---
+title: 'GitHub Container Registry'
+description: "GitHub Container Registry is a platform for hosting and managing packages."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { gitHubContainerRegistryIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={gitHubContainerRegistryIntegration}
+    categories={['Package Management', 'Software']}
+/>
+
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ["personalAccessToken"],
+    steps: []
+}, {
+    tabLabel: "GitHub App",
+    credentials: ['githubAppId', 'githubInstallationId', 'privateKey'],
+    steps: ['Create GitHub App', 'Create a private key for it', 'Install it to your organization / user']
+}]} />
@@ -0,0 +1,11 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const gitHubContainerRegistryIntegration: IntegrationDefinition = {
+  name: "GitHub Container Registry",
+  description: "GitHub Container Registry is a platform for hosting and managing packages.",
+  iconUrl: {
+    light: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github.svg",
+    dark: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github-light.svg",
+  },
+  path: "../../integrations/github-packages",
+};
@@ -0,0 +1,41 @@
+---
+title: 'GitHub'
+description: "GitHub is a web-based platform for version control and collaboration."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { githubIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={githubIntegration}
+    categories={['Version Control', 'Software']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['personalAccessToken'],
+    steps: []
+}, {
+    tabLabel: "GitHub App",
+    credentials: ['githubAppId', 'githubInstallationId', 'privateKey'],
+    steps: ['Create GitHub App', 'Create a private key for it', 'Install it to your organization / user']
+}]} />
@@ -0,0 +1,11 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const githubIntegration: IntegrationDefinition = {
+  name: "GitHub",
+  description: "GitHub is a web-based platform for version control and collaboration.",
+  iconUrl: {
+    light: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github.svg",
+    dark: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/github-light.svg",
+  },
+  path: "../../integrations/github",
+};
@@ -0,0 +1,37 @@
+---
+title: 'GitLab'
+description: "GitLab is a web-based DevOps lifecycle tool that provides a Git repository manager."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { gitlabIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={gitlabIntegration}
+    categories={['Version Control', 'Software']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ['personalAccessToken'],
+    steps: []
+}]} />
@@ -0,0 +1,8 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const gitlabIntegration: IntegrationDefinition = {
+  name: "GitLab",
+  description: "GitLab is a web-based DevOps lifecycle tool that provides a Git repository manager.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/gitlab.svg",
+  path: "../../integrations/gitlab",
+};
@@ -1,52 +0,0 @@
---
-title: 'Gluetun'
-description: 'Connect Gluetun to Homarr as a VPN integration.'
-hide_title: true
---
-
-import { IntegrationHeader } from '@site/src/components/integrations/header';
-import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
-import { AddingIntegration } from '@site/src/components/integrations/adding';
-import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
-import { gluetunIntegration } from '.';
-import { vpnWidget } from '@site/docs/widgets/vpn';
-
-<IntegrationHeader
-  integration={gluetunIntegration}
-  categories={['VPN', 'Network']}
-/>
-
-[Gluetun](https://github.com/qdm12/gluetun) exposes a control server that Homarr can query to report the VPN tunnel
-status, DNS status, public IP address, and active provider details in the VPN widget.
-
-### Widgets & Capabilities
-
-<IntegrationCapabilites
-  items={[{
-    widget: vpnWidget,
-  }]}
-/>
-
-### Setting up the Gluetun control server
-
-Refer to the [Gluetun control server documentation](https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md#authentication) to enable and configure authentication.
-
-### Adding the integration
-
-<AddingIntegration />
-
-### Secrets
-
-Gluetun's control server can be left unprotected or secured with either an API key or HTTP Basic authentication.
-Choose the option that matches how your Gluetun instance integration is set up.
-
-<IntegrationSecrets secrets={[{
-  credentials: [],
-  steps: [],
-},{
-  credentials: ['username', 'password'],
-  steps: [],
-},{
-  credentials: ['apiKey'],
-  steps: [],
-},,]} />
@@ -1,8 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const gluetunIntegration: IntegrationDefinition = {
-  name: "Gluetun",
-  description: "VPN control server integration for Homarr's VPN widget.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/gluetun.svg",
-  path: "../../integrations/gluetun",
-};
@@ -1,8 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const gotifyIntegration: IntegrationDefinition = {
-  name: "Gotify",
-  description: "Gotify is a simple, self-hosted server for sending and receiving messages in real time.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/gotify.svg",
-  path: "../../integrations/gotify",
-};
@@ -39,25 +39,13 @@ import { immichServerStatsWidget } from '../../widgets/immich-server-stats';
    'Scroll down to "API Keys"', 
    'Click "New API Key"', 
    'Enter a name, e.g. "Homarr"', 
-(
-
-  <span>
-
-    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>
-
-),
+    (<span>
+      Select the following permissions:{" "}
+      <code>album.read</code>,{" "}
+      <code>user.read</code>,{" "}
+      <code>server.statistics</code>,{" "}
+      <code>asset.download</code>
+    </span>), 
    'Create the integration in Homarr and copy the API key to there'
    ]
-}]} />
+}]} />
@@ -1,25 +1,26 @@
 ---
-title: 'Gotify'
-description: "Gotify is a simple, self-hosted server for sending and receiving messages in real time."
+title: 'LinuxServer.io'
+description: "LinuxServer.io is a platform for managing and deploying containerized applications."
 hide_title: true
 ---

-import { notificationsWidget } from '@site/docs/widgets/notifications';
-import { AddingIntegration } from '@site/src/components/integrations/adding';
 import { IntegrationHeader } from '@site/src/components/integrations/header';
-import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
-import { gotifyIntegration } from '.';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { linuxServerIoIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+

 <IntegrationHeader
-    integration={gotifyIntegration}
-    categories={['Notifications', 'Messaging']}
+    integration={linuxServerIoIntegration}
+    categories={['Container Management', 'Software']}
 />

 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[{
-        widget: notificationsWidget
+        widget: releasesWidget
    }]}
 />

@@ -28,6 +29,6 @@ import { gotifyIntegration } from '.';

 ### Secrets
 <IntegrationSecrets secrets={[{
-    credentials: ['username', 'password'],
+    credentials: [],
    steps: []
-}]} />
+}]} />
@@ -0,0 +1,8 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const linuxServerIoIntegration: IntegrationDefinition = {
+  name: "LinuxServer.io",
+  description: "LinuxServer.io is a platform for managing and deploying containerized applications.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/linuxserver-io.svg",
+  path: "../../integrations/linux-server-io",
+};
@@ -10,21 +10,19 @@ import { AddingIntegration } from '@site/src/components/integrations/adding';
 import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
 import { navidromeIntegration } from '.';
 import { audioStatsWidget } from '@site/docs/widgets/audio-stats';
-import { mediaServerWidget } from '@site/docs/widgets/media-server';


 <IntegrationHeader
    integration={navidromeIntegration}
-    categories={['Media', 'Media server']}
+    categories={['Media']}
 />

-Navidrome provides music library statistics including artist, album, and song counts, as well as now playing audio streams via the Subsonic API.
+Navidrome provides music library statistics including artist, album, and song counts, as well as now playing information via the Subsonic API.

 ### Widgets & Capabilities
 <IntegrationCapabilites
    items={[
        { widget: audioStatsWidget },
-        { widget: mediaServerWidget },
    ]}
 />

@@ -0,0 +1,34 @@
+---
+title: 'NPM'
+description: "NPM is a package manager for the JavaScript programming language, primarily used for managing Node.js packages."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { npmIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={npmIntegration}
+    categories={['Package Management', 'Software']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}]} />
@@ -0,0 +1,9 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const npmIntegration: IntegrationDefinition = {
+  name: "NPM",
+  description:
+    "NPM is a package manager for the JavaScript programming language, primarily used for managing Node.js packages.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/npm.svg",
+  path: "../../integrations/npm",
+};
@@ -1,43 +0,0 @@
---
-title: 'PatchMon'
-description: "PatchMon is a patch management and monitoring solution for Linux hosts."
-hide_title: true
---
-
-import { IntegrationHeader } from '@site/src/components/integrations/header';
-import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
-import { AddingIntegration } from '@site/src/components/integrations/adding';
-import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
-import { patchmonIntegration } from '.';
-import { patchmonWidget } from '@site/docs/widgets/patchmon';
-
-
-<IntegrationHeader
-    integration={patchmonIntegration}
-    categories={['Health Monitoring']}
-/>
-
-PatchMon provides host and package update statistics including total hosts, hosts needing updates, and security update counts.
-
-The PatchMon widget requires users to be **signed in to Homarr**; see the [PatchMon widget documentation](/docs/widgets/patchmon#authentication) for details on authentication and public boards.
-
-### Widgets & Capabilities
-<IntegrationCapabilites
-    items={[
-        { widget: patchmonWidget },
-    ]}
-/>
-
-### Adding the integration
-<AddingIntegration />
-
-### Secrets
-<IntegrationSecrets secrets={[{
-    credentials: ['patchmonApiKey', 'patchmonApiSecret'],
-    steps: [
-        'Open your PatchMon instance',
-        'Navigate to Settings and create a new GetHomepage API key',
-        'Copy the API key and secret from the success dialog',
-        'Paste them into Homarr — Basic authentication is handled automatically',
-    ]
-}]} />
@@ -1,9 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const patchmonIntegration: IntegrationDefinition = {
-  name: "PatchMon",
-  description:
-    "PatchMon is a patch management and monitoring solution for Linux hosts, tracking package updates and security patches across your infrastructure.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/patchmon.svg",
-  path: "../../integrations/patchmon",
-};
@@ -0,0 +1,37 @@
+---
+title: 'Quay'
+description: "Quay is a container registry for storing and managing container images."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { quayIntegration } from '.';
+import { releasesWidget } from '@site/docs/widgets/releases';
+
+
+<IntegrationHeader
+    integration={quayIntegration}
+    categories={['Container Registry', 'Software']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{
+        widget: releasesWidget
+    }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
+
+### Secrets
+<IntegrationSecrets secrets={[{
+    credentials: [],
+    steps: []
+}, {
+    credentials: ["personalAccessToken"],
+    steps: []
+}]} />
@@ -0,0 +1,8 @@
+import { IntegrationDefinition } from "@site/src/types";
+
+export const quayIntegration: IntegrationDefinition = {
+  name: "Quay",
+  description: "Quay is a container registry for storing and managing container images.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/png/quay.png",
+  path: "../../integrations/quay",
+};
@@ -0,0 +1,28 @@
+---
+title: 'Search.ch'
+description: "Search.ch supports searching for timetables in Switzerland."
+hide_title: true
+---
+
+import { IntegrationHeader } from '@site/src/components/integrations/header';
+import { IntegrationCapabilites } from '@site/src/components/integrations/widgets';
+import { AddingIntegration } from '@site/src/components/integrations/adding';
+import { IntegrationSecrets } from '@site/src/components/integrations/secrets';
+import { IconDownload } from "@tabler/icons-react";
+import { searchChIntegration } from '.';
+import Alert from '@theme/Admonition';
+import { timetableWidget } from '@site/docs/widgets/timetable';
+
+
+<IntegrationHeader
+  integration={searchChIntegration}
+  categories={['Timetable']}
+/>
+
+### Widgets & Capabilities
+<IntegrationCapabilites
+    items={[{ widget: timetableWidget }]}
+/>
+
+### Adding the integration
+<AddingIntegration />
@@ -0,0 +1,7 @@
+import { IntegrationDefinition } from "@site/src/types";
+export const searchChIntegration: IntegrationDefinition = {
+  name: "Search.ch",
+  description: "Search.ch supports searching for timetables in Switzerland.",
+  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/search-ch.png",
+  path: "../../integrations/search-ch",
+};
@@ -1,96 +0,0 @@
---
-title: "Synology DiskStation"
-description: "Monitor CPU, memory, storage volumes, and system health from Synology DSM."
-hide_title: true
---
-
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { synologyIntegration } from ".";
-import { systemResourcesWidget } from "@site/docs/widgets/system-resources";
-import { systemDisksWidget } from "@site/docs/widgets/system-disks";
-import { healthMonitoringWidget } from "@site/docs/widgets/health-monitoring";
-import Alert from "@theme/Admonition";
-
-<IntegrationHeader integration={synologyIntegration} categories={["NAS", "Hardware"]} />
-
-### Widgets & Capabilities
-
-<IntegrationCapabilites
-  items={[
-    { widget: healthMonitoringWidget },
-    { widget: systemResourcesWidget },
-    { widget: systemDisksWidget },
-  ]}
-/>
-
-### Supported metrics
-
-| Widget section               | DSM API source                                        | May be unavailable                                      |
-| ---------------------------- | ----------------------------------------------------- | ------------------------------------------------------- |
-| CPU ring / chart             | `SYNO.Core.System.Utilization`                        | —                                                       |
-| Memory ring / chart          | `SYNO.Core.System.Utilization`                        | —                                                       |
-| CPU temperature ring         | `SYNO.Core.System` system info                        | Models without a temperature sensor                     |
-| Network charts               | `SYNO.Core.System.Utilization` network totals         | Some DSM builds or permission configurations            |
-| Load average (info modal)    | `SYNO.Core.System.Utilization` CPU load fields        | —                                                       |
-| Storage volume usage         | `SYNO.Core.System` storage info / Storage Manager API | —                                                       |
-| SMART status and temperature | Storage Manager and SMART APIs                        | Disk-to-volume mapping may be incomplete on some setups |
-| Reboot / update indicator    | `SYNO.Core.System.Status` / upgrade APIs              | Permission-dependent                                    |
-| GPU                          | Not available                                         | Typical DiskStation models                              |
-
-### Adding the integration
-
-<AddingIntegration />
-
-<Alert type="info" title="Use the correct DSM URL">
-  Enter the HTTP or HTTPS URL of your Synology DSM web interface, for example <code>http://diskstation.local:5000</code>{" "}
-  or <code>https://diskstation.local:5001</code>. If DSM uses a self-signed certificate, add it under{" "}
-  <a href="/docs/management/certificates">Management &gt; Tools &gt; Certificates</a> so Homarr can connect securely.
-</Alert>
-
-### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Create a dedicated DSM user with a strong password for Homarr.",
-        "Add the user to the default Administrators group so Homarr can read `SYNO.Core.System` metrics.",
-        "Under User Groups and Permissions, deny access to shared folders and most applications.",
-        "Allow login to DSM only, optionally restricted by source IP address.",
-        "Log in once with the service account in DSM to accept terms and conditions.",
-      ],
-      body: (
-        <>
-          <Alert type="caution" title="Administrators group required">
-            Homarr reads system, storage, and utilization data from APIs that require membership in the default
-            Administrators group.
-          </Alert>
-          <Alert type="warning" title="Two-factor authentication is not supported">
-            Accounts with 2-step verification enabled cannot authenticate with this integration. Use a dedicated service
-            account without 2FA.
-          </Alert>
-          <Alert type="tip" title="First-time setup">
-            If login fails during testing, temporarily disable automatic blocking for invalid logins under Control Panel
-            &gt; Security &gt; Protection, then re-enable it after Homarr connects successfully.
-          </Alert>
-        </>
-      ),
-    },
-  ]}
-/>
-
-### Storage volume selection
-
-Health Monitoring and System Disks widgets can filter Synology storage volumes when **every** selected integration is a Synology DiskStation. Leave **Visible storage volumes** empty to show all volumes, or pick specific volumes from the list. When multiple Synology integrations are connected, volumes are labeled with the integration name.
-
-<Alert type="note" title="Synology-only option">
-  The volume filter is hidden when the widget also uses non-Synology integrations such as TrueNAS or Unraid.
-</Alert>
-
-<Alert type="note" title="Volume ordering">
-  When no volume filter is configured, the first volume returned by DSM is not guaranteed to be `volume_1`.
-</Alert>
@@ -1,8 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const synologyIntegration: IntegrationDefinition = {
-  name: "Synology DiskStation",
-  description: "Monitor CPU, memory, storage volumes, and system health from Synology DSM.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/synology.svg",
-  path: "../../integrations/synology",
-};
@@ -19,7 +19,7 @@ import { dnsHoleControlsWidget } from '@site/docs/widgets/dns-hole-controls';
 />

 <Alert type="note" className='my-2'>
-    Homarr supports Technitium DNS v11 and above. The correct API version is detected automatically - no manual configuration is required.
+    Homarr supports Technitium DNS v11 and above. The correct API version is detected automatically — no manual configuration is required.
 </Alert>

 ### Widgets & Capabilities
@@ -1,57 +0,0 @@
---
-title: "Traefik"
-description: "Cloud-native reverse proxy and load balancer"
-hide_title: true
---
-
-import { IntegrationHeader } from "@site/src/components/integrations/header";
-import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
-import { AddingIntegration } from "@site/src/components/integrations/adding";
-import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
-import { traefikIntegration } from ".";
-import { traefikWidget } from "../../widgets/traefik";
-
-<IntegrationHeader integration={traefikIntegration} categories={["Reverse proxy", "Monitoring"]} />
-
-### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: traefikWidget }]} />
-
-### Adding the integration
-
-<AddingIntegration />
-
-:::info URL configuration
-Use the URL where Traefik exposes its dashboard/API, for example `http://traefik:8080` or `https://traefik.example.com`. Homarr calls Traefik endpoints under `/api` automatically.
-:::
-
-:::warning API requirement
-Traefik must have the API enabled. For local or internal setups this is commonly exposed through `api.insecure=true`; for production setups, expose the `api@internal` service through an authenticated router.
-:::
-
-### Secrets
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [
-        "Choose this option when the Traefik API is only reachable from a trusted internal network and does not require authentication.",
-      ],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Use this option when your Traefik dashboard route is protected by Basic Auth.",
-        "Enter the same username and password required to open the Traefik dashboard.",
-      ],
-    },
-    {
-      credentials: ["apiKey"],
-      steps: [
-        "Use this option when your Traefik dashboard route accepts a bearer token.",
-        "Paste the token into the API Key field in Homarr.",
-      ],
-    },
-  ]}
-/>
@@ -1,8 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const traefikIntegration: IntegrationDefinition = {
-  name: "Traefik",
-  description: "Cloud-native reverse proxy and load balancer",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/traefik.svg",
-  path: "../../integrations/traefik",
-};
@@ -44,7 +44,7 @@ import Alert from '@theme/Admonition';
        steps: [
            "In the TrueNAS web interface, click your user avatar in the top-right corner and select \"API Keys\".",
            "Click \"Add\", give the key a name such as \"Homarr\", and confirm.",
-            "Copy the generated key immediately - TrueNAS only shows it once - and paste it as the API Key when creating the integration in Homarr.",
+            "Copy the generated key immediately — TrueNAS only shows it once — and paste it as the API Key when creating the integration in Homarr.",
        ],
    },
    {
@@ -47,7 +47,7 @@ import { umamiWidget } from '../../widgets/umami';
    credentials: ['username', 'password'],
    steps: [
      'Use the username and password of your Umami account',
-      'Note: username/password auth is for self-hosted instances only - Umami Cloud requires an API key',
+      'Note: username/password auth is for self-hosted instances only — Umami Cloud requires an API key',
    ]
  }
 ]} />
@@ -6,6 +6,8 @@ tags:
  - Interface
 ---

+import { ApiReferenceReact } from "@scalar/api-reference-react"
+
 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
@@ -13,25 +15,20 @@ your deployments in a cluster or dynamically adding integrations depending on ho

 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/).
+You can test out API endpoints using any OpenAPI client - for example [Postman](https://www.postman.com/), [Insomnia](https://insomnia.rest/) or [Hoppscotch](https://hoppscotch.io/).

 ## 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`.
+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
-
 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.

 ### API Key Format
-
 API keys are provided in the format `<id>.<token>`. When making requests, include the key in the `ApiKey` header:

 ```
@@ -39,54 +36,49 @@ ApiKey: abc123def456.xyz789tokenvalue...
 ```

 ### Supported Endpoints
-
 API key authentication works with both endpoint types:

-| Endpoint Type | Path Pattern    | API Key Support |
-| ------------- | --------------- | --------------- |
-| OpenAPI       | `/api/...`      | ✅ Supported    |
-| tRPC          | `/api/trpc/...` | ✅ Supported    |
+| Endpoint Type | Path Pattern | API Key Support |
+|--------------|--------------|-----------------|
+| OpenAPI | `/api/...` | ✅ Supported |
+| tRPC | `/api/trpc/...` | ✅ Supported |

 If no API key is provided, Homarr falls back to session cookie authentication (for browser-based access).

 ### Usage Examples

 **OpenAPI endpoint:**
-
 ```bash
 curl -H 'ApiKey: <id>.<token>' http://localhost:7575/api/health/live
 ```

 **tRPC endpoint:**
-
 ```bash
 curl -H 'ApiKey: <id>.<token>' http://localhost:7575/api/trpc/app.all
 ```

 ### Use Cases
-
 API key authentication enables programmatic access for:
-
 - Automation scripts and CI/CD pipelines
 - Third-party integrations
 - Custom dashboards and monitoring tools
 - Container orchestration systems that need to sync app definitions

-## Board Automation
+## Specification

-The OpenAPI and MCP APIs include board management endpoints for common automation workflows:
+:::info

- 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
+This section is automatically being updated hourly.
+Last update:
+``TEST`` <!-- OPEN_API_SPEC_LAST_UPDATED -->

-Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
+:::

-### Saving dashboard layouts
-
-The dashboard editor saves item positions and sections as one board update.
-Canvas height follows its content automatically and does not require a separate API setting.
-Responsive layouts store optional left and right gutter widths from zero to three columns.
-Gutter columns are reserved from the layout's total column count, and changing them reflows affected items.
+<ApiReferenceReact
+  configuration={{
+    url: "/api/open-api-schema.json",
+    theme: "kepler",
+    hideModels: false,
+    hideDownloadButton: false,
+  }}
+/>
@@ -1,76 +0,0 @@
---
-tags:
-  - Backup
-  - SQLite
-  - Management
-  - Data
---
-
-# Backup & Restore
-
-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.
-
-:::warning
-
-Backup and restore is only available when using the **SQLite** database driver. MySQL and PostgreSQL instances do not show this page.
-
-:::
-
-## Accessing the Backup Page
-
-Navigate to `Management` → `Tools` → `Backup`. You must have **admin** permissions to access this page.
-
-## Exporting a Backup
-
-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:
-
-| File                 | Description                                                         |
-| -------------------- | ------------------------------------------------------------------- |
-| `db.sqlite`          | Full SQLite database with all entities                              |
-| `metadata.json`      | Backup metadata: Homarr version, creation timestamp, encryption key |
-
-The backup includes everything: apps, integrations, secrets, boards, users, groups, permissions, search engines, custom widgets, and server settings. (It just backs-up the whole database)
-
-## 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
@@ -9,11 +9,11 @@ tags:
  - Layout
 ---

-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";
+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'

 Each dashboard is called a "board".
 You can create as many boards as you want.
@@ -24,30 +24,24 @@ Other boards can be viewed by direct links (e.g. my-homarr.com/board/smart-home)
 Names of boards must be unique because this will be used in the URL to load the desired board.

 ## Create a new board
-
 When creating a board, the availability of the board name will be checked for you.

 ![](./img/create-board-modal.png)

 ### Name
-
 The name must not include any special characters and must be at least one character long.
 Underscores and hyphen-minus are allowed.

 ### Column count
-
-The column count defines how many fixed-width cells are available in each row.
-One cell contains a `200 × 200` logical-pixel tile.
-Homarr scales the whole board uniformly instead of changing widget proportions, with horizontal scrolling when further shrinking would make controls too small.
+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.

 ### Public
-
 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.
+This can be really useful if you want to have public boards in your company or for family and fiends.
 Modifications for public boards must be allowed explicitly using user groups and their permissions.

 ## Board settings
-
 You navigate to the board settings by clicking on these three dots:

 ![](./img/navigate-to-settings.png)
@@ -57,9 +51,7 @@ Alternatively, you can also navigate from the board page itself using the cog ic
 ![](./img/navigate-to-settings-2.png)

 ### General
-
 #### Page title
-
 This is the title that will be visible at the top left in the navigation bar:

 ![](./img/page-title.png)
@@ -67,7 +59,6 @@ This is the title that will be visible at the top left in the navigation bar:
 This field is optional and Homarr will fall back to "Homarr" if nothing is set.

 #### Meta title
-
 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:

@@ -76,156 +67,78 @@ Browser will use it to set the title of tabs:
 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.
-Homarr selects a layout from the screen width, then scales its complete fixed-size canvas uniformly.
+In this section you can configure the different responsive layouts. Depending on your screens width the layout will change.

 ![](./img/layout-settings.png)

-Every `1 × 1` tile has a `200 × 200` logical-pixel content area.
-The `24` logical-pixel gap between tiles is separate from that size.
-A `2 × 1` tile therefore contains two fixed cell widths plus the gap between them.
-Widgets see their logical size, while the board's visual scale makes the complete layout larger or smaller.
-When fitting below 100%, Homarr keeps widget typography and control density at their normal readable size.
-On larger canvases, the complete board grows together like browser zoom.
-The scale never drops below 75%; on narrower screens the canvas scrolls horizontally instead of shrinking controls below an accessible size.
-
-The position and size of every item can be changed separately in each responsive layout.
+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.
-New items use their widget's default grid size, while a new inline section starts at a useful `4 × 3` size when the layout has enough columns.
-Both are placed in the first available position.
-
-Moving content downward in edit mode extends the canvas automatically, while view mode trims it back to the content.
-Nested sections keep their own resizable bounds.
+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 chosen freely. It is only used for management and will not be visible on the board.
+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

-Total number of columns for this layout.
-When changed, Homarr moves items into the next available positions without overlap.
-
-#### Fixed sidebars
-
-Each responsive layout can enable a fixed left sidebar, a fixed right sidebar, or both.
-Set a sidebar width to zero to disable it for that layout.
-Choose a width from one to three columns with the three-step slider.
-The preview shows how much space remains for the main canvas.
-
-Sidebar columns are reserved from the layout's total column count.
-For example, a 12-column layout with a two-column left sidebar leaves ten columns for the canvas.
-Enabling or widening a sidebar reflows canvas items into the remaining columns.
-Disabling a sidebar moves its contents back into the next available canvas positions.
-
-Sidebars remain visible while the page scrolls.
-Apps, widgets, and sections inside them still use the same fixed `200 × 200` cells and can be rearranged in edit mode.
+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.
-
-#### View and edit modes
-
-View mode renders a static board without executing the drag-and-drop editor.
-After the board is interactive, Homarr prepares the editor in the background for users who can modify it.
-Entering edit mode keeps the static board visible until that preparation finishes, then enables collision-aware movement and resizing without changing the board geometry.
-Widget content is inert in edit mode, so dragging anywhere on the content moves the tile instead of activating the widget; the visible grip and tile outline indicate the active move surface, while the tile's settings button remains available.
-Dropping a tile into another tile's exact slot swaps their positions when both resulting placements fit without overlapping other content.
-For other collisions, or when a tile grows into occupied space, nearby tiles are compacted out of the way.
-The visible corner controls provide a 44-pixel resize target, and edge controls appear on hover for horizontal or vertical resizing.
-Resize handles stop at the tile's minimum allowed size while the pointer is still moving.
-Exit edit mode to save the resulting positions.
-
-Keyboard users can focus a tile, press Enter or Space, then use arrow keys to move and Shift plus arrow keys to resize.
-Press Escape to stop.
-The **Move / resize item** action in the edit menu remains available for precise numeric or touch input.
+Minimum width of the screen where the layout will be used. 
+Once the minmum 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} />
-
-### Sections and sidebars
-
-Sections can contain apps, widgets, and nested sections.
-Every section uses the same model whether it is on the canvas or inside a sidebar.
-Sections can be moved and resized directly in edit mode.
-Expanding it creates space for its contents and pushes following items out of the way; collapsing it compacts the board.
-
-Each section can configure:
-
- Whether its label is visible.
- Whether users may collapse it.
- Whether its menu shows **Open all in new tabs**.
- Its label, border color, and custom CSS classes.
-
-Existing categories and dynamic sections are converted into this unified section model.
-Existing category rails become board sidebars automatically.
+<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} />
+<img src={iconColorImage}  height={100} />

 #### Item radius
-
 Change the radius of your items / categories.

-<img src={itemRadiusImage} height={100} />
+<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.

@@ -234,16 +147,14 @@ The styling will only be applied on the respective board page.
 ### 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                        |
@@ -262,23 +173,18 @@ 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:

@@ -290,7 +196,7 @@ 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
+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.
 :::

@@ -300,51 +206,47 @@ You can duplicate a board by clicking on the three dots in the list of boards an
 ![](./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`
+- ``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`.
+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`
+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)
+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)
+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)
+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.
@@ -353,4 +255,4 @@ 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)
+It will be used for devices that are detected as mobile devices. (Using User-Agent header)
@@ -1,208 +1,100 @@
 ---
+title: Custom Widgets
 tags:
-  - Custom Widgets
-  - API
+  - Management
  - Widgets
-  - JSX
+  - Custom
+  - API
 ---

-# Custom Widgets
-
-:::warning
-
-Custom widgets are a new feature. Share feedback, ask questions, and discuss ideas in our [GitHub Discussions](https://github.com/homarr-labs/homarr/discussions/categories/custom-widgets).
+Custom widgets let you create your own dashboard widgets that fetch data from any external API and render it with configurable displays. They are managed from the **Management → Custom Widgets** page (admin only).

+:::note Beta
+Custom widgets are currently in beta. Share feedback and report issues in the [GitHub discussion](https://github.com/homarr-labs/homarr/discussions/5916).
 :::

-Custom widgets allow you to fetch data from any HTTP API and display it on your Homarr dashboard. You define the API endpoint, authentication, and how the response should be rendered - no code compilation or server restart required.
+## Overview
+
+Custom widgets connect to any HTTP API endpoint and display the response data using one of several built-in display types. You can create multiple widget definitions, each with its own API configuration, display settings, and optional secrets for authentication.

 ## Creating a Custom Widget

-To create a custom widget, navigate to the **Custom Widgets** section in the management sidebar and click the **Add** button. Fill in the configuration:
+Navigate to **Management → Custom Widgets** and click **New Custom Widget**. You'll need to configure:

- **Name** - Display name shown in the widget picker and on the dashboard
- **Description** - Optional description shown in tooltips and management UI
- **Icon URL** - Optional URL to an icon image for the widget
- **URL** - The API endpoint to fetch data from (must include protocol, e.g. `https://api.example.com/stats`)
- **Authentication** - How the API request is authenticated:
-  - `none` - Public APIs with no authentication
-  - `bearer` - Bearer token authentication
-  - `basic` - HTTP Basic auth (username + password)
-  - `apiKeyHeader` - API key sent as a custom HTTP header
-  - `apiKeyQuery` - API key sent as a query parameter
- **Header Name** - Custom header or query parameter name for API key auth (e.g. `X-API-Key`)
- **HTTP Method** - `GET`, `POST`, `PUT`, `PATCH`, or `DELETE`
- **Request Body** - JSON string body for `POST`/`PUT`/`PATCH` requests
- **Display Type** - How the API response is rendered (see below)
+### API Configuration

-## Display Types
+- **URL** — The full URL of the API endpoint to fetch
+- **Method** — HTTP method (`GET`, `POST`, etc.)
+- **Headers** — Custom HTTP headers (e.g. `Authorization`, `Content-Type`)
+- **Body** — Request body for POST/PUT methods
+- **Auth type** — Authentication method (`none`, `bearer`, `basic`, `API key in header`, `API key in query`)

-| Display Type         | Description                                          | Best For                                 |
-| -------------------- | ---------------------------------------------------- | ---------------------------------------- |
-| **Single Value**     | Extracts a single value with a label and unit        | Metrics: temperature, uptime, user count |
-| **Key Value**        | Multiple labeled key-value pairs with optional units | System stats: CPU, memory, disk          |
-| **Table**            | API array data rendered as a sortable table          | Lists of items with columns              |
-| **Stat Grid**        | Labeled values in colored stat cards                 | Counts: movies, series, albums           |
-| **Progress Bars**    | Values as progress bars with percentages             | Usage: disk, quota, capacity             |
-| **Status Indicator** | Green/red status dots for health checks              | Service monitoring                       |
-| **Count Grid**       | Simple counts in a grid (no colors)                  | Library counts                           |
-| **Raw**              | Pretty-prints the raw JSON response                  | Debugging                                |
-| **Action Button**    | Clickable button executing the API request           | Triggers: restart, clear cache           |
-| **Custom JSX**       | Custom JSX template with Mantine v9 components       | Full layout control                      |
+### Secrets

-### AI-Powered JSX Generation
+Custom widgets support encrypted secret storage for API keys and passwords. Secrets are stored using AES-256-CBC encryption (same as integration secrets) and are **excluded from exports** for security.

-When editing or creating a custom widget with the **Custom JSX** display type, you'll find a **Copy Prompt** button. Clicking it copies a pre-formatted prompt describing your widget's name, API endpoint, and available Mantine components. Paste this into your preferred AI assistant (ChatGPT, Claude, Copilot, etc.) to generate a JSX template tailored to your data.
+### Display Configuration

-<details>
-<summary>Example: Pokédex widget using Custom JSX</summary>
+Choose from the following display types:

-```json
-{
-  "$schema": "homarr-custom-widget-v2",
-  "name": "Pokédex",
-  "description": "Browseable Pokémon list",
-  "iconUrl": "https://raw.githubusercontent.com/PokeAPI/sprites/master/sprites/items/poke-ball.png",
-  "url": "https://pokeapi.co/api/v2/pokemon?limit=75",
-  "authType": "none",
-  "method": "GET",
-  "displayType": "customJsx",
-  "displayConfig": {
-    "type": "customJsx",
-    "template": "<Stack gap=\"md\" p=\"xs\">\n  <Card withBorder radius=\"xl\" p=\"md\" shadow=\"md\">\n    <Group justify=\"space-between\">\n      <Title order={3}>Pokédex</Title>\n    </Group>\n  </Card>\n  <PaginatedList pageSize={12}>\n    <Grid gutter=\"sm\">\n      {data.results.map((pokemon, i) =>\n        <Grid.Col span={1.5}>\n          <Anchor href={pokemon.url} target=\"_blank\" underline=\"never\">\n            <Card withBorder radius=\"xl\" p=\"xs\" shadow=\"md\">\n              <Stack gap=\"sm\" align=\"center\">\n                <Group justify=\"space-between\" style={{ width: \"100%\" }}>\n                  <Badge size=\"sm\" color=\"red\">#{i + 1}</Badge>\n                  <Text fw={800} tt=\"capitalize\">{pokemon.name}</Text>\n                </Group>\n                <Avatar\n                  src={\"https://raw.githubusercontent.com/PokeAPI/sprites/master/sprites/pokemon/\" + (i + 1) + \".png\"}\n                  size={92}\n                  radius=\"xl\"\n                />\n              </Stack>\n            </Card>\n          </Anchor>\n        </Grid.Col>\n      )}\n    </Grid>\n  </PaginatedList>\n</Stack>"
-  }
-}
-```
+| Display Type | Description |
+|---|---|
+| **Single Value** | Shows a single extracted value prominently |
+| **Key-Value** | Displays data as labeled key-value pairs |
+| **Table** | Renders data in a table layout |
+| **Stat Grid** | Shows multiple statistics in a grid |
+| **Progress Bars** | Visualizes values as progress bars |
+| **Status Indicator** | Shows status with colored indicators |
+| **Count Grid** | Displays count values in a grid layout |
+| **Raw** | Shows the raw API response |
+| **Action Button** | A button that triggers an API call when clicked |
+| **Custom JSX** | Write custom JSX templates using whitelisted Mantine components |

-</details>
+:::tip Refresh interval
+When adding a Custom API widget to a board, you can configure its **refresh interval** (1–3600 seconds, default 30s) in the widget's board options.
+:::

-## Importing and Exporting
+## Custom JSX Display

-Custom widgets can be exported and imported as JSON files. To export, select the widget in the list and click the export button. To import, click the import button and paste the JSON. Secrets (API keys, passwords) are never included in exports and must be configured after import.
+The Custom JSX display type lets you write JSX templates to create rich, interactive displays. For security, only whitelisted components are allowed:

-The import format uses `"$schema": "homarr-custom-widget-v2"` to identify the widget version.
+- **Mantine components** — `Text`, `Badge`, `Group`, `Stack`, `Paper`, `Progress`, `RingProgress`, `ThemeIcon`, `Anchor`, `Image`, `Divider`, `Code`, `Table`, and more
+- **Interactive components** — `PaginatedList`, `TabsContainer`, `Collapsible`, `StatBar`, `TypeBadge`

-## Available Mantine Components for Custom JSX
+Templates have access to the API response data and can use JSONPath expressions to extract values.

-When using the `customJsx` display type, your template has access to a whitelist of [Mantine v9](https://mantine.dev) components. Unrecognized components, event handlers, and dangerous tags are stripped for security.
+:::warning Security
+The JSX sandbox blocks dangerous patterns like `eval`, `Function`, `__proto__`, and `javascript:` URLs. However, only admins can create custom widgets.
+:::

-### Layout
+## Live Preview

-| Component           | Doc                                           |
-| ------------------- | --------------------------------------------- |
-| `Stack`             | [docs](https://mantine.dev/core/stack)        |
-| `Group`             | [docs](https://mantine.dev/core/group)        |
-| `Flex`              | [docs](https://mantine.dev/core/flex)         |
-| `Grid` / `Grid.Col` | [docs](https://mantine.dev/core/grid)         |
-| `SimpleGrid`        | [docs](https://mantine.dev/core/simple-grid)  |
-| `Center`            | [docs](https://mantine.dev/core/center)       |
-| `Container`         | [docs](https://mantine.dev/core/container)    |
-| `Space`             | [docs](https://mantine.dev/core/space)        |
-| `AspectRatio`       | [docs](https://mantine.dev/core/aspect-ratio) |
+The widget editor includes a live preview panel that shows how the widget will look with real API data. Use the **Debug** panel to inspect the raw API response and test JSONPath expressions.

-### Typography & Content
+## Copy AI Prompt

-| Component         | Doc                                               |
-| ----------------- | ------------------------------------------------- |
-| `Text`            | [docs](https://mantine.dev/core/text)             |
-| `Title`           | [docs](https://mantine.dev/core/title)            |
-| `Code`            | [docs](https://mantine.dev/core/code)             |
-| `Highlight`       | [docs](https://mantine.dev/core/highlight)        |
-| `Mark`            | [docs](https://mantine.dev/core/mark)             |
-| `Kbd`             | [docs](https://mantine.dev/core/kbd)              |
-| `Blockquote`      | [docs](https://mantine.dev/core/blockquote)       |
-| `Anchor`          | [docs](https://mantine.dev/core/anchor)           |
-| `NumberFormatter` | [docs](https://mantine.dev/core/number-formatter) |
+Click the **Copy AI Prompt** button to copy a prompt containing the API's JSON Schema and sample response. Paste this into an LLM to get help writing JSONPath expressions or Custom JSX templates.

-### Data Display
+## Import & Export

-| Component                 | Doc                                               |
-| ------------------------- | ------------------------------------------------- |
-| `Badge`                   | [docs](https://mantine.dev/core/badge)            |
-| `Card` / `Card.Section`   | [docs](https://mantine.dev/core/card)             |
-| `Paper`                   | [docs](https://mantine.dev/core/paper)            |
-| `Alert`                   | [docs](https://mantine.dev/core/alert)            |
-| `ThemeIcon`               | [docs](https://mantine.dev/core/theme-icon)       |
-| `ColorSwatch`             | [docs](https://mantine.dev/core/color-swatch)     |
-| `Avatar` / `Avatar.Group` | [docs](https://mantine.dev/core/avatar)           |
-| `Image`                   | [docs](https://mantine.dev/core/image)            |
-| `BackgroundImage`         | [docs](https://mantine.dev/core/background-image) |
-| `Indicator`               | [docs](https://mantine.dev/core/indicator)        |
-| `Pill`                    | [docs](https://mantine.dev/core/pill)             |
-| `Spoiler`                 | [docs](https://mantine.dev/core/spoiler)          |
+Custom widget definitions can be exported as JSON files and imported on other Homarr instances:

-### Tables
+- **Export** — Downloads a JSON file with the widget definition (secrets are excluded)
+- **Import** — Upload a previously exported JSON file to create a new widget definition
+- The export format uses `$schema: "homarr-custom-widget-v2"`

-| Component                               | Doc                                    |
-| --------------------------------------- | -------------------------------------- |
-| `Table` / `Table.Thead` / `Table.Tbody` | [docs](https://mantine.dev/core/table) |
-| `Table.Tr` / `Table.Th` / `Table.Td`    | [docs](https://mantine.dev/core/table) |
+## Using Custom Widgets on a Board

-### Lists
+Once created, custom widgets appear in the widget picker when editing a board. Each custom widget definition can be added to any board like a built-in widget.

-| Component                    | Doc                                       |
-| ---------------------------- | ----------------------------------------- |
-| `List` / `List.Item`         | [docs](https://mantine.dev/core/list)     |
-| `Timeline` / `Timeline.Item` | [docs](https://mantine.dev/core/timeline) |
+## Seed Fixtures

-### Feedback & Loading
+Homarr ships with example custom widget definitions (disabled by default) to help you get started:

-| Component                       | Doc                                            |
-| ------------------------------- | ---------------------------------------------- |
-| `Progress` / `Progress.Section` | [docs](https://mantine.dev/core/progress)      |
-| `RingProgress`                  | [docs](https://mantine.dev/core/ring-progress) |
-| `Skeleton`                      | [docs](https://mantine.dev/core/skeleton)      |
-| `Loader`                        | [docs](https://mantine.dev/core/loader)        |
+- **Currency Exchange (JPY)** — Live exchange rates
+- **Random Dog Fact** — Random dog facts
+- **Jellyfin library** — Jellyfin server statistics

-### Navigation & Overlay
+Enable them from the custom widgets management page or use them as templates for your own widgets.

-| Component                                                                | Doc                                          |
-| ------------------------------------------------------------------------ | -------------------------------------------- |
-| `TabsContainer` / `TabPanel`                                             | Custom interactive component                 |
-| `Accordion` / `Accordion.Item` / `Accordion.Control` / `Accordion.Panel` | [docs](https://mantine.dev/core/accordion)   |
-| `ScrollArea`                                                             | [docs](https://mantine.dev/core/scroll-area) |
-| `Tooltip`                                                                | [docs](https://mantine.dev/core/tooltip)     |
-
-### Charts
-
-| Component        | Doc                                                 |
-| ---------------- | --------------------------------------------------- |
-| `AreaChart`      | [docs](https://mantine.dev/charts/area-chart)       |
-| `BarChart`       | [docs](https://mantine.dev/charts/bar-chart)        |
-| `LineChart`      | [docs](https://mantine.dev/charts/line-chart)       |
-| `DonutChart`     | [docs](https://mantine.dev/charts/donut-chart)      |
-| `PieChart`       | [docs](https://mantine.dev/charts/pie-chart)        |
-| `RadarChart`     | [docs](https://mantine.dev/charts/radar-chart)      |
-| `RadialBarChart` | [docs](https://mantine.dev/charts/radial-bar-chart) |
-| `Sparkline`      | [docs](https://mantine.dev/charts/sparkline)        |
-
-### Interactive Components
-
-| Component       | Description                              |
-| --------------- | ---------------------------------------- |
-| `PaginatedList` | Client-side pagination wrapper           |
-| `Collapsible`   | Expandable/collapsible section           |
-| `StatBar`       | Horizontal stat bar                      |
-| `TypeBadge`     | Type-styled badge                        |
-| `Divider`       | [docs](https://mantine.dev/core/divider) |
-
-## Template Bindings
-
-Your template receives:
-
- `data` - The sanitized API response object. Access fields via `data.fieldName` or `data.results[0].name`.
- `String(v)` - Type-safe string conversion
- `Number(v)` - Type-safe number conversion
- `Boolean(v)` - Type-safe boolean conversion
- `Math` - Safe subset: `round`, `floor`, `ceil`, `abs`, `min`, `max`, `pow`, `sqrt`, `PI`
- `JSON.stringify(v)` - JSON serialization
- `Array.isArray(v)` - Array type check
- `Object.keys(v)`, `Object.values(v)`, `Object.entries(v)` - Object utilities
-
-## Security Constraints
-
- Event handlers (`onClick`, `onChange`, etc.) are stripped
- Dangerous HTML attributes (`dangerouslySetInnerHTML`) are stripped
- `script`, `iframe`, `object`, `embed`, `form`, `style`, `link`, `meta`, `base` tags are forbidden
- Template strings containing `eval`, `Function`, `import`, `require`, `globalThis`, `window`, `document`, `fetch` are rejected
- Anchor `href` attributes are validated to only allow `https://`, relative (`/`), and hash (`#`) URLs
+Additional examples like the Pokédex are available as importable JSON files in the repository under `packages/db/seed/custom-widgets/`.
@@ -1,167 +0,0 @@
---
-tags:
-  - MCP
-  - API
-  - AI
-  - Automation
---
-
-# Model Context Protocol (MCP)
-
-Homarr exposes a [Model Context Protocol](https://modelcontextprotocol.io) server at `/api/mcp/mcp`, enabling AI assistants like Claude, Cursor, VS Code Copilot, and Claude Code to interact with your Homarr instance using natural language.
-
-With MCP, you can ask your AI assistant to manage apps, integrations, users, boards, Docker containers, media servers, DNS settings, and more - all through Homarr's existing tRPC API, now exposed as 50+ AI-callable tools.
-
-## Getting Started
-
-The MCP endpoint lives under the **API** page at `Management` → `Tools` → `API` → **MCP** tab.
-
-![MCP Instructions Page](./api/img/mcp-instructions.png)
-
-### 1. Create an API Key
-
-Navigate to the **Authentication** tab in the API page and create an API key. API keys follow the format `<id>.<token>`.
-You can also create one directly from the MCP tab if you don't have any keys yet.
-
-### 2. Choose a Transport
-
-| Transport           | Best For                                                     | Requirements                   |
-| ------------------- | ------------------------------------------------------------ | ------------------------------ |
-| **Streamable HTTP** | Cursor, Claude Desktop, VS Code Copilot, Claude Code         | Direct HTTP access to Homarr   |
-| **STDIO**           | Firewall-restricted environments, offline-compatible clients | `npx` and `mcp-remote` package |
-
-**Streamable HTTP** is recommended for most setups. It works with all major AI clients.
-
-### 3. Configure Your Client
-
-Add the following to your client's MCP configuration file:
-
-**Streamable HTTP** (recommended):
-
-```json
-{
-  "mcpServers": {
-    "homarr": {
-      "url": "https://your-homarr-instance.com/api/mcp/mcp",
-      "headers": {
-        "ApiKey": "<your-api-key>"
-      }
-    }
-  }
-}
-```
-
-Where to place this config:
-
-| Client          | Config File                                     |
-| --------------- | ----------------------------------------------- |
-| Cursor          | `.cursor/mcp.json`                              |
-| Claude Desktop  | `claude_desktop_config.json`                    |
-| Claude Code     | `.claude/mcp.json` (or `claude mcp add homarr`) |
-| VS Code Copilot | `.vscode/mcp.json`                              |
-
-:::warning
-
-Replace `<your-api-key>` with your actual API key. Never commit API keys to version control.
-
-:::
-
-**STDIO** (alternative):
-
-```json
-{
-  "mcpServers": {
-    "homarr": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "mcp-remote",
-        "https://your-homarr-instance.com/api/mcp/mcp",
-        "--header",
-        "ApiKey:<your-api-key>"
-      ]
-    }
-  }
-}
-```
-
-This option tunnels MCP communication through STDIO using the `mcp-remote` package. Useful when the AI client cannot make HTTP requests directly.
-
-## Authentication
-
-MCP supports two authentication methods:
-
-| Method               | Description                                           | Best For                                                         |
-| -------------------- | ----------------------------------------------------- | ---------------------------------------------------------------- |
-| **API Key**          | Include `ApiKey: <id>.<token>` header in all requests | Scripts, CI/CD, direct client configs                            |
-| **OAuth 2.1 + PKCE** | Full OAuth flow with dynamic client registration      | MCP clients with OAuth support (e.g. `opencode mcp auth homarr`) |
-
-API key authentication is simpler and recommended for most setups. The API key inherits the permissions of the user who created it. Tools that require higher privileges will return permission errors if the key lacks access.
-
-## Testing the Connection
-
-Verify your MCP endpoint is working:
-
-```bash
-curl -s -X POST \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -H "ApiKey: <your-api-key>" \
-  -d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}},"id":1}' \
-  https://your-homarr-instance.com/api/mcp/mcp
-```
-
-A successful response includes the server capabilities and available tools. Use `tools/list` to see all available tools:
-
-```bash
-curl -s -X POST \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -H "ApiKey: <your-api-key>" \
-  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}' \
-  https://your-homarr-instance.com/api/mcp/mcp
-```
-
-## Available Tools
-
-Homarr exposes 50+ tools organized by namespace. Each tool is either a **query** (GET, read-only) or **mutation** (POST, write action).
-
-| Namespace          | Example Tools                                            | Type       |
-| ------------------ | -------------------------------------------------------- | ---------- |
-| `app`              | List all apps, get app by ID, create/update/delete app   | GET + POST |
-| `apiKeys`          | List API keys                                            | GET        |
-| `beszel`           | Systems status, alerts, historical system metrics        | GET        |
-| `board`            | List boards, get board by ID, create/update/delete board | GET + POST |
-| `docker`           | List containers, inspect container, start/stop/restart   | GET + POST |
-| `icon`             | Search icons                                             | GET        |
-| `info`             | Server health, version info                              | GET        |
-| `integration`      | List integrations, test connection, delete integration   | GET + POST |
-| `invite`           | List invitations, delete invite                          | GET + POST |
-| `calendar`         | Calendar events from media servers                       | GET        |
-| `dnsHole`          | DNS hole summary, toggle blocking                        | GET + POST |
-| `downloads`        | Active downloads, pause/resume/delete                    | GET + POST |
-| `healthMonitoring` | Resource usage stats                                     | GET        |
-| `patchmon`         | Host patch and security update statistics                | GET        |
-| `mediaRequests`    | Approve/decline media requests                           | GET + POST |
-| `mediaServer`      | Media server sessions and stats                          | GET        |
-| `smartHome`        | Execute automations, device states                       | GET + POST |
-
-The tools table on the MCP tab is dynamically generated - it always reflects the latest available procedures from your Homarr instance.
-
-## Security
-
- API keys are required for authentication - unauthenticated requests are rejected
- Tools inherit the permissions of the API key's owner
- OAuth endpoints are rate-limited to prevent abuse
- Tool execution errors are contained - a failing tool call does not crash the MCP server
- All communication uses HTTPS (configure HTTP → HTTPS redirects on your reverse proxy)
-
-## Use Cases
-
- **"Show me all apps on my Homarr dashboard"** - AI lists all apps with their names and URLs
- **"Restart the Plex Docker container"** - AI finds and restarts the container via Docker integration
- **"What's downloading right now?"** - AI fetches active download status across all download integrations
- **"Create a new app pointing to my Grafana instance"** - AI creates an app with the correct icon and URL
- **"How many users are on my Homarr instance?"** - AI lists all users (admin only)
- **"Toggle Pi-hole blocking for 5 minutes"** - AI interacts with DNS controls
- **"How are my servers doing?"** - AI fetches Beszel system stats including CPU, memory, disk, and alerts
@@ -42,7 +42,7 @@ Homarr will replace the ``%s`` with the term that the user entered.
 ## Media request search

 Jellyseerr, Overseerr, and Seerr integrations have a dedicated **Spotlight mode** for searching and requesting media.
-This mode does not require creating a search engine entry - it is available automatically when you have a compatible integration configured.
+This mode does not require creating a search engine entry — it is available automatically when you have a compatible integration configured.

 You can access it from:
 - The **Modes list** in Spotlight (opened with `CTRL + K`)
@@ -51,10 +51,10 @@ You can access it from:
 ### Availability indicators

 Search results display colored status badges showing the media's current state in your integration:
- **Available** - fully available in your media library
- **Partial** - some content (e.g. seasons) is available
- **Processing** - currently being downloaded or processed
- **Requested** - requested but not yet available
+- **Available** — fully available in your media library
+- **Partial** — some content (e.g. seasons) is available
+- **Processing** — currently being downloaded or processed
+- **Requested** — requested but not yet available

 ### Requesting TV show seasons

@@ -0,0 +1,5 @@
+{
+  "label": "Tools",
+  "collapsed": true,
+  "position": 10
+}
@@ -0,0 +1,66 @@
+---
+title: SQLite Backup & Restore
+tags:
+  - Management
+  - Backup
+  - Restore
+  - SQLite
+---
+
+The SQLite Backup & Restore feature allows you to export and import your entire Homarr database as a portable ZIP file. This is useful for creating backups, migrating between instances, or recovering from failures.
+
+:::info SQLite only
+This feature is only available when using the SQLite database driver (`DB_DRIVER=better-sqlite3`). MySQL and PostgreSQL users should use their respective database backup tools.
+:::
+
+## Accessing Backup & Restore
+
+Navigate to **Management → Tools → Backup** from the sidebar. This page is only visible when running with SQLite.
+
+## Exporting a Backup
+
+Click the **Export** button to download a ZIP archive containing:
+
+- **`db.sqlite`** — A consistent snapshot of your database (created via `VACUUM INTO`)
+- **`metadata.json`** — Contains:
+  - `homarrVersion` — The version of Homarr that created the backup
+  - `exportedAt` — Timestamp of the export
+  - `dbDialect` — The database dialect (`sqlite`)
+  - `encryptionKey` — Your `SECRET_ENCRYPTION_KEY` (needed to decrypt integration secrets)
+
+:::caution
+The exported ZIP contains your encryption key and database. Store it securely and do not share it publicly.
+:::
+
+A confirmation dialog will ask you to type **"I understand"** before the export proceeds.
+
+## Importing a Backup
+
+1. Click the **Import** button and upload a previously exported ZIP file
+2. Homarr analyzes the backup **entirely in your browser** using WebAssembly (sql.js) — no data is sent to the server during preview
+3. The preview shows:
+   - **Entity counts** — How many boards, apps, users, integrations, etc. are in the backup
+   - **Board names** — A list of all boards contained in the backup
+   - **Migration status** — If the backup is from an older version, Homarr shows each pending database migration as animated timeline steps
+4. Review the preview and type **"I understand"** to confirm
+5. Homarr applies any pending migrations, re-encrypts integration secrets if the `SECRET_ENCRYPTION_KEY` differs between instances, and replaces the live database
+6. The server automatically restarts to pick up the new database
+
+:::tip
+The import process is **backward-compatible** with older backups that used a separate `encryption-key.txt` file instead of embedding the key in `metadata.json`.
+:::
+
+## Onboarding Integration
+
+When setting up a fresh Homarr instance with SQLite, the onboarding wizard includes a **"Restore from SQLite backup"** option. This lets you upload a backup ZIP to bootstrap your new instance with data from a previous installation.
+
+## Docker Restart Behavior
+
+After a successful import, only the Next.js process restarts — nginx and Redis remain running. The `run.sh` script automatically restarts Next.js in a loop, so the application comes back online within seconds. Running `docker stop` still works gracefully.
+
+## Best Practices
+
+- **Back up regularly** — Create exports before major updates or configuration changes
+- **Test restores** — Periodically verify your backups by importing them on a test instance
+- **Secure storage** — Keep backups in an encrypted or access-controlled location since they contain your encryption key
+- **Check versions** — Backups from newer versions cannot be imported into older Homarr instances; always import into the same or newer version
@@ -1,45 +1,43 @@
 ---
-title: "Audio Stats"
-description: "Displays media and listening statistics from Navidrome or Audiobookshelf, adapting its display based on the linked integration."
+title: 'Audio Stats'
+description: 'Displays library statistics from Navidrome or Audiobookshelf, adapting its display based on the linked integration.'
 hide_title: true
 ---

-import { WidgetHeader } from "@site/src/components/widgets/header";
-import { AddingWidget } from "@site/src/components/widgets/adding";
-import { WidgetConfig } from "@site/src/components/widgets/configuration";
-import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
-import { audioStatsWidget } from ".";
-import { navidromeIntegration } from "@site/docs/integrations/navidrome";
-import { audiobookshelfIntegration } from "@site/docs/integrations/audiobookshelf";
+import { WidgetHeader } from '@site/src/components/widgets/header';
+import { AddingWidget } from '@site/src/components/widgets/adding';
+import { WidgetConfig } from '@site/src/components/widgets/configuration';
+import { WidgetIntegrations } from '@site/src/components/widgets/integrations';
+import { audioStatsWidget } from '.';
+import { navidromeIntegration } from '@site/docs/integrations/navidrome';
+import { audiobookshelfIntegration } from '@site/docs/integrations/audiobookshelf';

-<WidgetHeader widget={audioStatsWidget} categories={["Media"]} />
+
+<WidgetHeader
+  widget={audioStatsWidget}
+  categories={['Media']}
+/>

 This widget adapts its display based on the linked integration:

- **Navidrome**: Shows artist, album, and song counts
+- **Navidrome**: Shows artist, album, and song counts, plus a now playing section with active streams
 - **Audiobookshelf**: Shows library count, audiobook/podcast totals, listening time, and active sessions

 Only options relevant to your linked integration are shown in the configuration panel.

 ### Supported Integrations

-<WidgetIntegrations
-  items={[
-    {
-      integration: navidromeIntegration,
-      note: "Displays music library statistics",
-    },
-    {
-      integration: audiobookshelfIntegration,
-      note: "Displays audiobook/podcast library stats and listening time",
-    },
-  ]}
-/>
+<WidgetIntegrations items={[{
+  integration: navidromeIntegration,
+  note: "Displays music library stats and now playing"
+}, {
+  integration: audiobookshelfIntegration,
+  note: "Displays audiobook/podcast library stats and listening time"
+}]} />

 ### Adding the widget

 <AddingWidget />

 ### Configuration
-
 <WidgetConfig configuration={audioStatsWidget.configuration} />
@@ -27,6 +27,24 @@ export const audioStatsWidget: WidgetDefinition = {
        values: { type: "boolean" },
        defaultValue: "yes",
      },
+      {
+        name: "Show now playing",
+        description: "Displays currently playing tracks (Navidrome only)",
+        values: { type: "boolean" },
+        defaultValue: "yes",
+      },
+      {
+        name: "Show now playing list",
+        description: "Displays a detailed list of now playing tracks (Navidrome only)",
+        values: { type: "boolean" },
+        defaultValue: "yes",
+      },
+      {
+        name: "Max now playing items",
+        description: "Maximum number of now playing tracks to display (Navidrome only)",
+        values: "Number (1-5)",
+        defaultValue: "3",
+      },
      {
        name: "Show library count",
        description: "Displays the number of libraries (Audiobookshelf only)",
@@ -1,41 +0,0 @@
---
-title: 'Bazarr'
-description: 'Displays missing subtitle counts and health indicators from your Bazarr instance.'
-hide_title: true
---
-
-import { WidgetHeader } from '@site/src/components/widgets/header';
-import { AddingWidget } from '@site/src/components/widgets/adding';
-import { WidgetConfig } from '@site/src/components/widgets/configuration';
-import { WidgetIntegrations } from '@site/src/components/widgets/integrations';
-import { bazarrWidget } from '.';
-import { bazarrIntegration } from '@site/docs/integrations/bazarr';
-
-<WidgetHeader
-  widget={bazarrWidget}
-  categories={['Subtitles', 'Media']}
-/>
-
-This widget shows subtitle status from your Bazarr instance, including missing episode and movie subtitles, provider issues, and health warnings.
-
-### Screenshots
-
-import widgetOverview from './img/widget-overview.png';
-
-<div className="flex flex-col gap-2">
-  <img src={widgetOverview} alt="bazarr-widget-overview" width={128 * 4} />
-</div>
-
-### Supported Integrations
-
-<WidgetIntegrations items={[{
-  integration: bazarrIntegration,
-  note: "Displays missing subtitle counts and health indicators"
-}]} />
-
-### Adding the widget
-
-<AddingWidget />
-
-### Configuration
-<WidgetConfig configuration={bazarrWidget.configuration} />
@@ -1,37 +0,0 @@
-import { WidgetDefinition } from "@site/src/types";
-import { IconBadgeCc } from "@tabler/icons-react";
-
-export const bazarrWidget: WidgetDefinition = {
-  icon: IconBadgeCc,
-  name: "Bazarr",
-  description: "Displays missing subtitle counts and health indicators from your Bazarr instance.",
-  path: "../../widgets/bazarr",
-  configuration: {
-    items: [
-      {
-        name: "Show missing episodes",
-        description: "Displays the number of episodes with missing subtitles",
-        values: { type: "boolean" },
-        defaultValue: "yes",
-      },
-      {
-        name: "Show missing movies",
-        description: "Displays the number of movies with missing subtitles",
-        values: { type: "boolean" },
-        defaultValue: "yes",
-      },
-      {
-        name: "Show provider issues",
-        description: "Displays the number of subtitle providers with issues",
-        values: { type: "boolean" },
-        defaultValue: "yes",
-      },
-      {
-        name: "Show health issues",
-        description: "Displays the number of Bazarr health issues",
-        values: { type: "boolean" },
-        defaultValue: "yes",
-      },
-    ],
-  },
-};
Author	SHA1	Message	Date
ajnart	7f96085e65	style: auto-fix lint and format	2026-06-11 17:40:26 +00:00
Thomas Camlong	35542176cc	feat(definitions): wire up doc slugs and sitemap for Beszel + Custom API Set integration slug for beszel, widget slugs for all 4 Beszel widgets and customApi, add new paths to HomarrDocumentationPath type, and set documentationUrl for the Beszel integration.	2026-06-11 19:38:59 +02:00
Thomas Camlong	cf75eddc1b	docs(custom-widgets): add Custom Widgets and Custom API documentation Add management page documenting custom widget creation with API configuration, 10 display types (including Custom JSX sandbox), live preview, AI prompt copy, import/export, and seed fixtures. Add Custom API widget doc page linking to the management docs (PR #5889).	2026-06-11 19:38:44 +02:00
Thomas Camlong	e771e774c6	docs(backup): add SQLite backup & restore documentation Document the new Tools > Backup page covering ZIP export with VACUUM INTO, client-side WASM preview via sql.js, import with migration timeline, onboarding integration, Docker restart behavior, and backward compatibility. SQLite-only feature (PR #5887).	2026-06-11 19:38:34 +02:00
Thomas Camlong	6095ce09d7	docs(beszel): add Beszel integration and widget documentation Add integration page with screenshots and secrets configuration, plus 4 widget doc pages: System Stats (time-series charts), System Grid (card overview), System Table (sortable data table), and Alerts (triggered/ok/history). Includes 4 PNG screenshots downloaded from PR #5900.	2026-06-11 19:38:15 +02:00
@@ -1 +1 @@
 .18.0
 .16.0