style(e2e): format custom-widgets e2e test

When a custom widget is added to a board in edit mode, the item only
exists in local TanStack cache (persisted on saveBoard at edit-mode
exit). The getData query fired immediately, hit the DB before the item
existed, threw NOT_FOUND, and retry was disabled so the widget stayed
on 'definition not found' until reload.

- Gate getData with !isEditMode so it only fires for persisted items
- Show an edit-mode placeholder instead of an empty box
- Add e2e regression test verifying no 'not found' before reload

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

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

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

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

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

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

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

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

.cursor/rules/codebase-context.mdc

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

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

@@ -1,612 +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"
-```
-
-### 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 translation keys (including hidden option labels)
-8. Add context menu if row actions exist
-9. Add row expansion if detail view exists
-10. Add error handling on all mutations
-11. Add accessibility attributes
-12. Test at multiple widget widths
-13. Update docs in `apps/docs/docs/widgets/` if applicable
-14. Run `pnpm turbo typecheck`
-15. Run translation spec — catches missing keys

.deepsource.toml

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

.dockerignore

@@ -17,8 +17,7 @@ coverage
 dev
 .build
 e2e
-apps/docs/*
-!apps/docs/package.json
+apps/docs
 apps/nextjs/.next
 .env
 .env.*

.env.example

@@ -61,31 +61,9 @@ TURBO_TELEMETRY_DISABLED=1
 # Enable mock integration
 UNSAFE_ENABLE_MOCK_INTEGRATION=true
 
-# Public URL contract. Values must be absolute HTTP(S) URLs without credentials,
-# query strings, or fragments. Trailing slashes are normalized at startup.
-HOMARR_WEBSITE_URL=https://homarr.dev
-# PocketBase API used by Homarr and by the standalone documentation site.
-# Defaults to HOMARR_WEBSITE_URL.
-# WORKSHOP_API_URL=https://homarr.dev
-# Public Workshop website used by links in Homarr, Custom Widgets, onboarding,
-# and assistant context. Defaults to HOMARR_WEBSITE_URL/workshop.
-# WORKSHOP_WEB_URL=https://homarr.dev/workshop
-
-# Documentation and PocketBase deployment settings.
-# WORKSHOP_PUBLIC_ORIGIN=https://homarr.dev
-# PB_ALLOWED_ORIGINS=*
-
-# Local Workshop stack:
-# HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-# WORKSHOP_API_URL=http://127.0.0.1:8090
-# WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-# WORKSHOP_PUBLIC_ORIGIN=http://127.0.0.1:3003
-# Optional: GITHUB_CLIENT_ID=
-# Optional: GITHUB_CLIENT_SECRET=
-
 # Enable demo mode (seeds a demo user "demo"/"demo", a sample board and a mock integration)
 # DEMO_MODE=true
 
 # Whether demo mode is read-only. Defaults to true (the public demo blocks all mutations).
 # Set to false for writable preview deployments so the demo user can modify the dashboard.
-# DEMO_READ_ONLY=false
+# DEMO_READ_ONLY=false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -33,10 +33,6 @@ body:
       options:
         # The below comment is used to insert a new version with on-release.yml
         #NEXT_VERSION#
-        - 1.74.0
-        - 1.73.0
-        - 1.72.0
-        - 1.71.0
         - 1.70.0
         - 1.69.2
         - 1.69.0

.github/pull_request_template.md

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

.github/renovate.json5

@@ -1,6 +1,6 @@
 {
   $schema: "https://docs.renovatebot.com/renovate-schema.json",
-  extends: ["config:recommended", ":dependencyDashboardApproval"],
+  extends: ["config:recommended"],
   packageRules: [
     {
       matchPackageNames: ["^@homarr/"],
@@ -47,7 +47,7 @@
   rangeStrategy: "bump",
   automerge: false,
   baseBranchPatterns: ["dev"],
-  dependencyDashboard: true,
+  dependencyDashboard: false,
   // prevent special characters in branch names (otherwise git errors occur on windows)
   branchNameStrict: true,
 }

.github/workflows/autofix.yml

@@ -32,4 +32,4 @@ jobs:
         run: |
           git diff --name-only --diff-filter=ACMR -z "origin/${BASE_REF}...HEAD" -- \
             '*.css' '*.js' '*.json' '*.jsonc' '*.jsx' '*.md' '*.mdx' '*.scss' '*.ts' '*.tsx' '*.yaml' '*.yml' \
-            | xargs -0 -r pnpm exec oxfmt --check --
+            | xargs -0 -r pnpm exec oxfmt --check

.github/workflows/automatic-approval.yml

@@ -0,0 +1,35 @@
+name: "[Dependency Updates] Auto Approve"
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+permissions: {}
+
+jobs:
+  approve-automatic-prs:
+    runs-on: ubuntu-latest
+    timeout-minutes: 2
+    # 158783068: homarr-renovate[bot]
+    # 190541745: homarr-crowdin[bot]
+    # 210161987: homarr-update-contributors[bot]
+    # 175486441: homarr-releases[bot]
+    # Extracted from https://api.github.com/users/<username>
+    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
+      - name: Obtain token
+        id: obtainToken
+        uses: actions/create-github-app-token@v3
+        with:
+          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
+          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
+          permission-pull-requests: write # required to approve pull request
+
+      - name: Install GitHub CLI
+        run: sudo apt-get install -y gh
+      - name: Approve automatic PRs
+        env:
+          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
+        run: |
+          gh pr review ${{github.event.pull_request.number}} --approve --body "Automatically approved by GitHub Action"

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

@@ -1,43 +0,0 @@
-name: "[Bots] Reconcile Auto-merge"
-
-on:
-  schedule:
-    - cron: "*/30 * * * *"
-  workflow_dispatch:
-
-permissions: {}
-
-jobs:
-  reconcile:
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v7
-
-      - name: Obtain token
-        id: obtainToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
-          permission-pull-requests: write # required to enable auto-merge
-
-      - name: Install GitHub CLI
-        run: sudo apt-get install -y gh
-
-      - name: Re-enable auto-merge for prepared bot PRs
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-        run: |
-          # 158783068: homarr-renovate[bot]
-          # 190541745: homarr-crowdin[bot]
-          # 210161987: homarr-update-contributors[bot]
-          # 175441: homarr-releases[bot]
-          gh pr list --repo "${{ github.repository }}" --base dev --state open --limit 100 \
-            --json number,author,reviewDecision,mergeStateStatus,autoMergeRequest \
-            --jq '.[] | select(.author.login as $login | ["app/homarr-renovate", "app/homarr-crowdin", "app/homarr-update-contributors", "app/homarr-releases"] | index($login)) | select(.reviewDecision == "APPROVED") | select(.mergeStateStatus == "CLEAN") | select(.autoMergeRequest == null) | .number' \
-          | while read -r pr; do
-              echo "Re-enabling auto-merge on PR #$pr"
-              gh pr merge "$pr" --auto --squash
-            done

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

@@ -1,47 +0,0 @@
-name: "[Bots] Approve and Auto-merge"
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened, ready_for_review]
-
-permissions: {}
-
-jobs:
-  approve-and-automerge:
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    # 158783068: homarr-renovate[bot]
-    # 190541745: homarr-crowdin[bot]
-    # 210161987: homarr-update-contributors[bot]
-    # 175441: homarr-releases[bot]
-    # Extracted from https://api.github.com/users/<username>
-    if: |
-      (github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 || github.actor_id == 175441) &&
-      github.event.pull_request.head.repo.full_name == github.repository &&
-      github.event.pull_request.base.ref == 'dev'
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v7
-
-      - name: Obtain token
-        id: obtainToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
-          permission-pull-requests: write # required to approve a pull request and enable auto-merge
-
-      - name: Install GitHub CLI
-        run: sudo apt-get install -y gh
-
-      - name: Approve and enable auto-merge
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-        run: |
-          PR_NUMBER="${{ github.event.pull_request.number }}"
-          if [ "$(gh pr view "$PR_NUMBER" --json reviewDecision --jq .reviewDecision)" != "APPROVED" ]; then
-            gh pr review "$PR_NUMBER" --approve --body "Automatically approved by Homarr bot policy"
-          fi
-          if [ "$(gh pr view "$PR_NUMBER" --json autoMergeRequest --jq '.autoMergeRequest != null')" != "true" ]; then
-            gh pr merge "$PR_NUMBER" --auto --squash
-          fi

.github/workflows/ci.yml

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

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

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

.github/workflows/workshop.yml

@@ -1,63 +0,0 @@
-name: Workshop
-
-on:
-  pull_request:
-  push:
-    branches: [dev, v2, release/v2, main]
-
-permissions:
-  contents: read
-
-jobs:
-  validate:
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    steps:
-      - uses: actions/checkout@v7
-      - uses: actions/setup-node@v6
-        with:
-          node-version: 24.18.0
-      - uses: pnpm/action-setup@v6
-        with:
-          run_install: false
-      - run: pnpm install --frozen-lockfile
-      - run: pnpm --filter @homarr/workshop typecheck
-      - run: pnpm --filter @homarr/docs typecheck
-      - run: docker compose --env-file apps/workshop/.env.staging.example -f apps/workshop/docker-compose.staging.yml config --quiet
-      - run: pnpm test:workshop
-      - run: pnpm test:workshop-image
-
-  publish:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
-    needs: validate
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - uses: actions/checkout@v7
-      - uses: docker/setup-qemu-action@v4
-      - uses: docker/setup-buildx-action@v4
-      - uses: docker/login-action@v4
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      - uses: docker/metadata-action@v6
-        id: metadata
-        with:
-          images: ghcr.io/homarr-labs/workshop
-          tags: |
-            type=sha,prefix=sha-,format=long
-            type=raw,value=v2,enable=${{ github.ref_name == 'v2' || github.ref_name == 'release/v2' }}
-            type=raw,value=latest,enable=${{ github.ref_name == 'main' }}
-      - uses: docker/build-push-action@v7
-        with:
-          context: .
-          file: apps/workshop/Dockerfile
-          target: production
-          platforms: linux/amd64,linux/arm64
-          push: true
-          tags: ${{ steps.metadata.outputs.tags }}
-          labels: ${{ steps.metadata.outputs.labels }}

.gitignore

@@ -16,7 +16,6 @@ out/
 next-env.d.ts
 
 # artifacts
-.ai-evaluations/
 packages/db/migrations/*/migrate.cjs
 
 # nitro
@@ -72,23 +71,10 @@ apps/nextjs/public/images/background.png
 
 # personal agent config
 .opencode
-.agents/*
-!.agents/skills/
-.agents/skills/*
-!.agents/skills/homarr-custom-widget/
-!.agents/skills/homarr-custom-widget/**
+.agents/
 skills-lock.json
 
 # docusaurus
 apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
-benchmark-results
-
-# local performance investigation (never ship benchmark data or restored backups)
-.widget-performance/
-.bench/
-homarr-backup*.zip
-*.sqlite-wal
-*.sqlite-shm
-/scripts/benchmarks/

.oxfmtrc.json

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

.oxlintrc.json

@@ -30,15 +30,7 @@
   "options": {
     "reportUnusedDisableDirectives": "off"
   },
-  "ignorePatterns": [
-    "**/*.config.js",
-    "**/*.config.mjs",
-    "**/*.cjs",
-    "**/lang/*.d.json.ts",
-    ".next/**",
-    "apps/docs/.docusaurus/**",
-    "apps/docs/build/**"
-  ],
+  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", "**/lang/*.d.json.ts", ".next/**", "apps/docs/.docusaurus/**", "apps/docs/build/**"],
   "settings": {
     "react": { "version": "19" }
   }

AGENTS.md

@@ -40,12 +40,12 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
+│   ├── old-import/      # Legacy Homarr import
+│   ├── old-schema/      # Legacy Homarr zod schemas
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig
 │   └── github/          # CI setup action
-├── tools/
-│   └── homarr-dev/      # Go CLI for local and PR Docker images
 ├── development/         # Dev docker-compose (Redis, MySQL, PostgreSQL)
 ├── e2e/                 # E2E test specs
 └── Dockerfile           # Multi-stage production build
@@ -68,9 +68,6 @@ When modifying user-facing code, you MUST also update the corresponding document
 ## Monorepo Commands
 
 - `pnpm dev` — Next.js app only
-- `pnpm dev:cli -- dev` — run the developer CLI without installing a global binary
-- `pnpm db:seed` — seed default database data explicitly
-- `pnpm docker:dev:up` — start the Redis development service in the background
 - `pnpm dev:docs` — Docusaurus docs site only
 - `pnpm turbo build` — build all packages
 - `pnpm turbo build --filter=@homarr/docs` — build docs only
@@ -84,7 +81,3 @@ When modifying user-facing code, you MUST also update the corresponding document
 - UI: Mantine (not Tailwind) — Tailwind is only used in docs app
 - Icons: @tabler/icons-react
 - Docs app can import from `@homarr/definitions` for shared types
-- Run `pnpm dev:cli -- dev` to browse local `homarr:*` images and remote PR images.
-- Run `pnpm dev:cli -- build <name>` from a Homarr checkout to build `homarr:<name>` with rebuild provenance.
-- Run `pnpm dev:cli -- build --pr <number>` to build a PR locally from a temporary checkout.
-- Run Go checks from `tools/homarr-dev` with `go test ./...` and `go vet ./...`.

AUDIT.md

@@ -0,0 +1,535 @@
+# Custom Widgets Architecture Audit and North Star
+
+> Status: implemented in the current working tree; baseline retained below for traceability
+> Evidence snapshot: `c5703e7e5` on PR #6304
+> Scope: built-in custom-widget displays, Custom JSX, network execution, authoring, preview, import/export, AI prompts, and MCP tools
+
+## Implementation outcome
+
+The migration described by this audit is implemented. `@homarr/custom-widgets` now owns the domain through explicit `core`, `jsx`, `runtime`, `server`, and `workbench` exports. API, Widgets, and Next.js retain only authorization, persistence, transport, board registration, navigation, and localized adapter concerns.
+
+Key outcomes:
+
+- One typed configuration and display-descriptor model drives schemas, defaults, form hydration, serialization, import/export, preview, examples, diagnostics, generated references, and AI prompts.
+- Display-data extraction moved out of API and Widgets into the domain package; the former API-to-Widgets re-export chain no longer exists.
+- The interpreter, shared security policy, registry, wrappers, named-request runtime, hardened executor, preview sessions, rate limits, and workbench UI have focused package-owned modules and tests.
+- Runtime and workbench network behavior is injected through typed ports. The domain package has no dependency on API, Widgets, Next.js routes, notification infrastructure, or modal infrastructure.
+- Public tRPC and MCP procedures are characterized, v2 and v3 import envelopes remain accepted, display-only v1 remains covered, and MCP offers iterative schema, validation, template read/write/patch, create/import/update, preview query, simulation, and journal tools.
+- The AI prompt uses a multiline two-block authoring bundle, documents the `SubFetch` render-child contract, and is generated from the canonical registry and tested examples.
+- Architecture enforcement currently scans 110 production modules for dependency direction, cycles, file budgets, dynamic loading, and untranslated JSX literals. Generated-reference drift and every Mantine export classification are test-enforced.
+- The latest production build measured the largest Custom JSX route payload at 99,852 gzip bytes across two chunks, below the 768 KiB budget.
+
+Focused verification is green: 278 package tests, 35 API/MCP tests, 52 Widgets renderer tests, 7 E2E tests, affected typecheck, affected lint, docs build, production Next.js build, architecture checks, generated drift, and the bundle budget. The root `pnpm test` command is presently blocked on this workstation by unrelated Docker-backed integration suites timing out while the shared Docker daemon is under external load; no Custom Widget test failed in those runs.
+
+## Executive summary
+
+The feature has a strong security direction and a capable authoring experience, but its implementation has outgrown its current ownership model. PR #6304 changes 56 files with 13,206 additions. The primary feature directories contain 10,437 lines, spread across `@homarr/widgets`, `@homarr/api`, `@homarr/definitions`, `@homarr/validation`, and the Next.js management route.
+
+The main problem is not the absolute line count. It is that domain policy, transport, persistence, rendering, form state, compatibility, and documentation generation are interleaved across package boundaries. A change to one display type can require synchronized edits in schemas, form defaults, import conversion, preview extraction, runtime rendering, documentation, and AI instructions. Several of those paths use untyped records, duplicated conversion logic, or direct API dependencies.
+
+The north star is a single `@homarr/custom-widgets` domain package with explicit `core`, `jsx`, `runtime`, `server`, and `workbench` entry points. Existing applications and packages become thin adapters. The extraction must preserve public APIs, import formats, permission behavior, and the current UI while improving internal cohesion.
+
+This audit does not authorize a big-bang rewrite. The migration should be a sequence of behavior-preserving PRs, beginning with characterization tests and ending with enforced dependency and complexity budgets.
+
+## Measured baseline
+
+### Change footprint
+
+| Measure                         | Current value |
+| ------------------------------- | ------------: |
+| PR files changed                |            56 |
+| PR additions                    |        13,206 |
+| PR deletions                    |         1,385 |
+| Primary feature-directory lines |        10,437 |
+
+Generated component-reference JSON accounts for 2,491 added lines and is not treated as source complexity.
+
+### Largest production files
+
+| File                                                                            | Lines | Responsibilities currently combined                                                                                                                                                   |
+| ------------------------------------------------------------------------------- | ----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `apps/nextjs/src/app/[locale]/manage/custom-widgets/_custom-widget-form.tsx`    | 1,911 | Schema refinement, defaults, server-error mapping, form conversion, submission, preview state, focus management, display picker, connection fields, and every display-specific editor |
+| `packages/api/src/router/custom-widget/custom-widget-router.ts`                 |   978 | CRUD, import/export, template patching, MCP descriptions, preview sessions, preview execution, journals, and action simulation/execution                                              |
+| `packages/widgets/src/custom-api/safe-jsx-interpreter.tsx`                      |   944 | AST model, parsing, environments, budgets, sanitization, expression evaluation, safe methods, callbacks, and React rendering                                                          |
+| `apps/nextjs/src/app/[locale]/manage/custom-widgets/_custom-widget-preview.tsx` |   834 | Preview orchestration, error boundary, tabs, response tree, diagnostics, request journal, sample data, and renderer selection                                                         |
+| `packages/widgets/src/custom-api/jsx-whitelist.ts`                              |   775 | Mantine imports, wrappers, icon mapping, runtime component map, registry filtering, data sanitization, and safe bindings                                                              |
+| `packages/widgets/src/custom-api/jsx-sub-fetch.tsx`                             |   599 | Query rendering, render props, path display, action execution, buttons, toggles, refresh, notifications, and confirmations                                                            |
+
+These files exceed the proposed 300-line production-module target. The interpreter is a reasonable candidate for a documented 400-line exception after its independent policies, evaluators, and renderer are extracted.
+
+### Current ownership
+
+```mermaid
+flowchart LR
+  D["@homarr/definitions<br/>registry and examples"]
+  V["@homarr/validation<br/>schemas and AST diagnostics"]
+  W["@homarr/widgets<br/>renderers and interpreter"]
+  A["@homarr/api<br/>CRUD, permissions, execution and MCP"]
+  N["Next.js route<br/>workbench, preview and prompt"]
+  X["Docs<br/>generated reference and guides"]
+
+  N --> A
+  N --> V
+  N --> D
+  N --> W
+  W --> A
+  W --> D
+  A --> V
+  X --> D
+```
+
+The `@homarr/widgets → @homarr/api` edge is particularly costly. Runtime request components call the generated tRPC client directly, so moving the domain into a package that is also consumed by the API would create a dependency cycle unless request execution is inverted behind a typed port.
+
+## What is working well
+
+- Custom JSX v2 replaces raw runtime URLs and methods with named, typed requests.
+- Board permissions, network scope, DNS validation, redirect policy, response limits, caching, concurrency, and action rules are server-enforced.
+- The safe interpreter no longer treats an upstream JSX parser as a sandbox.
+- Component metadata drives runtime classification, editor completion, docs generation, and part of the AI prompt.
+- The workbench supports multiline JSX, diagnostics, real preview sizes, response inspection, request journals, import review, undo/redo, and paste-to-import.
+- MCP exposes schema, validation, preview, journal, template read/write/patch, import, and update workflows without exposing stored secrets.
+- Shared examples cover simple metrics, nested queries, charts, actions, and richer interactive layouts.
+
+The migration must preserve these capabilities. Package extraction is not a reason to weaken the security boundary or remove authoring features.
+
+## Findings
+
+### P1 — Domain ownership is fragmented
+
+Custom-widget behavior is implemented in five packages/applications. None of them is the clear source of truth for the complete lifecycle. `@homarr/definitions` owns component metadata and examples, `@homarr/validation` owns schemas and template diagnostics, `@homarr/widgets` owns runtime evaluation, `@homarr/api` owns network and persistence flows, and Next.js owns authoring transformations.
+
+Impact:
+
+- Maintainers must search unrelated packages to understand one behavior.
+- Changes have a large synchronization surface and can drift silently.
+- The domain cannot be tested or reused as a coherent unit.
+- Package names describe infrastructure location rather than feature ownership.
+
+### P1 — Giant modules mix unrelated reasons to change
+
+The largest files are not merely long; they combine policy, orchestration, state, and presentation. The form contains all display editors. The router contains every management and preview procedure. The interpreter contains parsing through React emission. The request component file contains both query and mutation interaction models.
+
+Impact:
+
+- Reviews are broad and regression-prone.
+- Unit-test seams are difficult to identify.
+- Merge conflicts concentrate in a small number of files.
+- Small feature changes require understanding thousands of lines of adjacent behavior.
+
+### P1 — Runtime code depends directly on the API client
+
+`packages/widgets/src/custom-api/component.tsx` and `jsx-sub-fetch.tsx` import `@homarr/api/client`. They also directly invoke notifications and confirmation modals.
+
+Impact:
+
+- The renderer cannot be used or tested without application infrastructure.
+- A future `@homarr/custom-widgets` package would cycle with `@homarr/api` if both retained these imports.
+- Preview and board runtime cannot share the same renderer through different request implementations without branching inside the components.
+
+Required direction: a runtime provider must receive typed query, action, confirmation, notification, and invalidation ports. The board and preview layers supply adapters.
+
+### P1 — Configuration transformations are duplicated
+
+Create defaults and builders live in the form, edit hydration lives in the edit page, and import hydration lives in `_custom-widget-import-utils.ts`. These paths independently translate between stored display configs and form values. They rely on display-type switches, record casts, and JSON text fields such as the request manifest.
+
+Impact:
+
+- Create, edit, paste replacement, import, export, and MCP can disagree.
+- Adding a field requires updating multiple transforms.
+- Round trips are difficult to prove lossless.
+
+Required direction: each display type supplies one typed descriptor containing schema, defaults, `toForm`, `fromForm`, preview projection, and migration behavior.
+
+### P1 — Type safety degrades at domain boundaries
+
+`Record<string, unknown>`, `as never`, and `as unknown as` are frequent in form conversion, display extraction, preview state, imports, registry wrappers, and API parsing. Some casts are necessary at the interpreter/React boundary, but most domain-level casts indicate missing discriminated unions or validated adapters.
+
+Impact:
+
+- Invalid combinations survive until runtime.
+- Refactors do not receive complete compiler guidance.
+- Server and client transformations can diverge while continuing to compile.
+
+Required direction: parse unknown values once at ingress and use typed domain objects afterward. Unsafe casts must be isolated to named boundary modules and justified by tests.
+
+### P1 — Security policy is represented more than once
+
+The template validator and interpreter both parse JSX and maintain concepts such as blocked properties, blocked props, AST depth, and operation limits. Runtime component filtering adds another policy layer.
+
+The analyzer and interpreter have different jobs, so they should not be collapsed into one evaluator. They must, however, consume one immutable policy definition and shared AST normalization utilities.
+
+Impact:
+
+- A property can be rejected by one layer and missed by another.
+- Security changes require parallel edits and duplicate tests.
+- Diagnostics can describe behavior that differs from runtime enforcement.
+
+### P1 — The API router combines transport and application behavior
+
+The router owns tRPC metadata, Zod inputs, database writes, encryption, import/export, template revisions, preview execution, rate-limit acquisition, journal recording, and MCP documentation.
+
+Impact:
+
+- Domain logic is only testable through tRPC context setup.
+- MCP and browser endpoints can accidentally implement different workflows.
+- Framework-specific `TRPCError` values leak into lower-level executor and manifest code.
+
+Required direction: tRPC procedures authorize, load persistence models, call a domain service, and map domain errors. They do not implement request rendering, template patching, preview execution, or import conversion inline.
+
+### P2 — Metadata generation is only partially centralized
+
+The component registry and examples are shared, but runtime maps, wrappers, safe bindings, display-type metadata, AI prompt prose, form choices, and some docs remain separately assembled. The AI prompt is built inside a client button component.
+
+Impact:
+
+- Agent instructions can drift from validation and runtime behavior.
+- Prompt generation requires UI and network context.
+- Display types lack the same single-registry guarantee as JSX components.
+
+Required direction: prompt generation is a pure function in `core`, using the schema, display descriptors, component registry, and tested fixtures. The UI only fetches context and copies the result.
+
+### P2 — Compatibility behavior is mixed into primary flows
+
+V1 detection, migration warnings, legacy network diagnostics, v2 imports, v3 exports, and fallback display parsing are embedded beside current authoring/runtime logic.
+
+Impact:
+
+- Happy paths are harder to read.
+- Legacy behavior can accidentally influence v2 code.
+- Compatibility retirement has no obvious deletion boundary.
+
+Required direction: version detection and migrations live under `core/migrations`. Runtime and workbench receive a normalized current model plus explicit review state.
+
+### P2 — Test topology does not mirror the architecture
+
+Interpreter coverage is substantial, and request-executor/router tests exist, but tests are colocated under their current infrastructure owners instead of a feature package. A focused renderer run passed 52 tests during review, while the selected API suites failed before collecting tests because the root Vitest client environment rejected server-only environment access.
+
+Impact:
+
+- The complete feature cannot be verified with one package command.
+- Server test failures can be configuration failures rather than behavioral failures.
+- Form conversion and workbench orchestration have limited direct characterization coverage relative to their size.
+
+Required direction: the package owns focused test projects or environment-specific configs for core, DOM runtime/workbench, and Node server tests. API adapter tests remain in `@homarr/api`.
+
+### P2 — A small amount of user-facing copy bypasses translation
+
+Examples found during the snapshot include the raw-response tooltip and a default empty template message. Dynamic translation keys also require repeated `as never` casts, reducing translation-key safety.
+
+Impact:
+
+- Locale completeness gates are unreliable.
+- Refactoring copy is harder than changing typed translation keys.
+
+Required direction: all package UI receives a typed message catalog or uses typed scoped translations. No visible fallback literals are allowed in production components.
+
+## North-star package
+
+```text
+packages/custom-widgets/
+├── src/core/
+│   ├── config/          # discriminated display configurations and form models
+│   ├── displays/        # typed display descriptors and built-in display metadata
+│   ├── import/          # v2/v3 parsing, export, review, and authoring bundles
+│   ├── migrations/      # v1 detection, normalization, and review requirements
+│   ├── prompts/         # pure AI prompt generation
+│   └── examples/        # typed fixtures shared by tests, docs, editor, and prompts
+├── src/jsx/
+│   ├── ast/             # parser adapter, AST types, traversal, and normalization
+│   ├── policy/          # blocked properties, props, URLs, and budgets
+│   ├── analyzer/        # authoring diagnostics
+│   ├── interpreter/     # expression and collection evaluation
+│   ├── registry/        # component descriptors, wrappers, and export classification
+│   └── bindings/        # branded safe helpers and sanitized data
+├── src/runtime/
+│   ├── displays/        # built-in renderers
+│   ├── jsx/             # Custom JSX renderer and error containment
+│   ├── requests/        # SubFetch, actions, toggles, refresh, and state handling
+│   └── provider/        # injected runtime capabilities
+├── src/server/
+│   ├── network/         # hardened executor and destination policy
+│   ├── requests/        # manifest resolution and parameter substitution
+│   ├── limits/          # rate and concurrency limits
+│   └── preview/         # sessions, simulation, and journals
+└── src/workbench/
+    ├── form/            # shared state and connection/display sections
+    ├── editor/          # CodeMirror and registry-driven diagnostics
+    ├── preview/         # widget, response, journal, and diagnostic views
+    └── import/          # clipboard parsing and review UI
+```
+
+Public exports are explicit:
+
+```json
+{
+  "exports": {
+    "./core": "./src/core/index.ts",
+    "./jsx": "./src/jsx/index.ts",
+    "./runtime": "./src/runtime/index.ts",
+    "./server": "./src/server/index.ts",
+    "./workbench": "./src/workbench/index.ts"
+  }
+}
+```
+
+There is no broad root barrel. Internal folders cannot be imported by consumers.
+
+### Dependency rules
+
+```mermaid
+flowchart LR
+  C["custom-widgets/core"]
+  J["custom-widgets/jsx"]
+  R["custom-widgets/runtime"]
+  S["custom-widgets/server"]
+  B["custom-widgets/workbench"]
+  API["@homarr/api adapter"]
+  W["@homarr/widgets adapter"]
+  N["Next.js route adapter"]
+  DOC["Docs generator"]
+
+  J --> C
+  R --> C
+  R --> J
+  S --> C
+  B --> C
+  B --> R
+  API --> C
+  API --> S
+  W --> C
+  W --> R
+  N --> C
+  N --> B
+  DOC --> C
+  DOC --> J
+```
+
+Hard rules:
+
+1. `@homarr/custom-widgets` never imports `@homarr/api`, `@homarr/widgets`, or Next.js route modules.
+2. `core` has no React, Mantine, tRPC, database, Redis, or browser dependency.
+3. `jsx` has no API, persistence, Redis, notification, or modal dependency.
+4. `runtime` performs no direct tRPC calls. It consumes `CustomWidgetRuntimePort`.
+5. `workbench` performs no direct tRPC calls. It consumes `CustomWidgetWorkbenchPort` callbacks.
+6. `server` has no tRPC or database-query dependency. API adapters load authorized records and map errors.
+7. Cross-entry imports follow the arrows above; reverse imports fail CI.
+
+### Runtime ports
+
+The exact transport remains owned by adapters. The domain contract should cover behavior rather than tRPC details:
+
+```ts
+interface CustomWidgetRuntimePort {
+  getData(input: { itemId: string; signal?: AbortSignal }): Promise<CustomWidgetRequestResult>;
+  query(input: NamedRequestInvocation & { signal?: AbortSignal }): Promise<CustomWidgetRequestResult>;
+  action(input: NamedRequestInvocation & { confirmed?: boolean }): Promise<CustomWidgetRequestResult>;
+  confirm(input: ActionConfirmation): Promise<boolean>;
+  notify(input: RuntimeNotification): void;
+  invalidate(input: RuntimeInvalidation): Promise<void>;
+}
+```
+
+Board runtime and preview runtime implement the same port. Preview simulation is an adapter capability, not a conditional tRPC import inside `ActionButton`.
+
+### Display descriptors
+
+Every display type is represented once:
+
+```ts
+interface CustomWidgetDisplayDescriptor<TConfig, TForm> {
+  type: CustomWidgetDisplayType;
+  configSchema: ZodType<TConfig>;
+  formSchema: ZodType<TForm>;
+  createDefault(): TConfig;
+  toForm(config: TConfig): TForm;
+  fromForm(form: TForm): TConfig;
+  migrate(input: unknown): DisplayMigrationResult<TConfig>;
+  extract(response: unknown, config: TConfig): DisplayModel;
+  capabilities(config: TConfig): CustomWidgetCapability[];
+}
+```
+
+UI fields and renderer components may be registered in runtime/workbench companion maps keyed by the same typed display identifier. Domain descriptors remain serializable and framework-independent.
+
+## Developer-experience north star
+
+### Maintainers
+
+- Start at `packages/custom-widgets` for every feature behavior.
+- Find one module per concept and one descriptor per display type.
+- Add a display type without editing central switches in multiple packages.
+- Run one package command for core, DOM, and server tests.
+- Receive compile-time failures when a configuration field is not handled by forms, preview, migration, or export.
+- Review PRs that move one domain boundary at a time.
+
+### Administrators and template authors
+
+- Preserve the current continuous form and live workbench.
+- Keep preview usable before a live response exists through schema-valid defaults and editable sample data.
+- Keep diagnostics actionable, localized, clickable, and consistent with runtime policy.
+- Keep imports reviewable and secrets excluded.
+- Keep query and action capabilities visible without noisy permanent warnings.
+
+### AI agents
+
+- Obtain schema, registry, limits, examples, and prompt rules from the same typed sources.
+- Use readable multiline templates through authoring bundles and line-based template tools.
+- Validate, preview, inspect journals, patch, and revalidate without rewriting unrelated configuration.
+- Receive stable machine-actionable issue codes in addition to localized or human-readable messages.
+- Never need to infer runtime behavior from UI-only prompt strings.
+
+## Fragmentation rules
+
+- Production modules target at most 300 lines, excluding generated files, fixtures, and type-only declarations.
+- Algorithmic modules can reach 400 lines only with a file-level rationale and focused tests.
+- A module has one primary reason to change; moving lines without separating policy from orchestration does not satisfy the target.
+- React components do not contain schema definitions or persistence transforms.
+- Routers do not contain reusable domain algorithms.
+- Domain functions do not throw framework-specific errors.
+- Unknown input is validated once. Parsed values are not carried as `Record<string, unknown>` through internal layers.
+- Compatibility code lives in versioned migration modules and has explicit removal criteria.
+- Generated artifacts are reproducible and checked for drift, but excluded from line budgets.
+
+## Migration roadmap
+
+### PR 1 — Characterize contracts
+
+- Add round-trip tests for every display descriptor: default → form → config, stored config → form → config, and import → export.
+- Add fixtures for v1 display-only, v1 network-review-required, v2 import, and v3 export.
+- Add prompt snapshots sourced from the component registry and examples.
+- Split Node and DOM Vitest projects so server suites collect and run reliably.
+- Record bundle and render baselines before moving modules.
+
+Gate: all existing behavior is represented by tests, with no production moves yet.
+
+### PR 2 — Establish `core`
+
+- Create `@homarr/custom-widgets` and explicit exports.
+- Move custom-widget schemas, typed configs, display descriptors, examples, import/export, migration, capability analysis, and prompt generation into `core`.
+- Replace form/edit/import conversion duplication with descriptor calls.
+- Temporarily re-export legacy imports from definitions and validation to keep consumers stable.
+
+Gate: create, edit, import, export, MCP validation, and AI prompt generation use the same domain contracts.
+
+### PR 3 — Extract JSX policy and interpreter
+
+- Move AST types, parser adapter, shared security policy, analyzer, evaluator, budgets, bindings, and registry into `jsx`.
+- Separate evaluator modules by expression family and React emission.
+- Generate diagnostics and runtime enforcement from the same policy constants.
+- Keep the Mantine export-classification CI check.
+
+Gate: the security suite passes unchanged, analyzer/runtime policy drift tests pass, and no consumer imports JSX internals.
+
+### PR 4 — Extract runtime
+
+- Move built-in renderers, Custom JSX display, SubFetch, actions, toggles, refresh, and error containment into `runtime`.
+- Introduce the runtime port and adapters for board and preview contexts.
+- Remove direct imports of the API client, modals, and notifications from domain components.
+- Split request components into query, action, toggle, refresh, feedback, and shared-state modules.
+
+Gate: board rendering and workbench preview use the same runtime components through different adapters; actions retain confirmation, rollback, invalidation, and permission behavior.
+
+### PR 5 — Extract server services
+
+- Move executor, manifests, network policy, limits, caching/single-flight, and preview-session logic into `server`.
+- Replace `TRPCError` below the adapter with typed domain errors.
+- Split API procedures into management, templates, preview, and runtime routers that delegate to package services.
+- Keep authorization, database lookup, encryption, and tRPC/MCP metadata in `@homarr/api`.
+
+Gate: browser and MCP flows call the same services; request security tests run as Node package tests; public procedure names and inputs remain compatible.
+
+### PR 6 — Extract and fragment workbench
+
+- Move reusable editor, preview, response tree, import review, connection section, display picker, and display-specific fields into `workbench`.
+- Introduce a workbench port for validate, preview, query, simulate action, journal, and save callbacks.
+- Keep Next.js pages responsible only for routing, loading initial data, and constructing adapters.
+- Replace the monolithic form with small sections and descriptor-driven display fields while preserving the continuous form, two-pane scrolling, autofocus, and mobile modes.
+
+Gate: no workbench source file exceeds the agreed budget, and create/edit/paste replacement share one state model.
+
+### PR 7 — Remove scaffolding and enforce boundaries
+
+- Remove compatibility re-exports and old implementations after all consumers move.
+- Add CI checks for forbidden imports, dependency cycles, source-size budgets, untranslated literals, generated-artifact drift, component classification, and custom-JSX chunk size.
+- Update contributor and architecture documentation with package entry points and extension recipes.
+
+Gate: old ownership paths contain only thin adapters or are deleted.
+
+## Verification strategy
+
+### Core
+
+- Every display descriptor accepts valid data and rejects mismatched configuration.
+- All create/edit/import/export transformations are lossless where expected.
+- V1/v2/v3 compatibility and review states are deterministic.
+- Prompt output, authoring bundles, fixtures, docs data, and completion data are generated from shared sources.
+
+### JSX
+
+- Computed and Unicode-obfuscated reflective access remains blocked.
+- Analyzer and interpreter share property, prop, URL, and budget policy.
+- Own-property resolution, branded calls, callback accounting, and node/operation limits remain enforced.
+- Every upstream Mantine export is classified and every enabled runtime component resolves.
+
+### Runtime and workbench
+
+- Query cancellation, stale results, retries, render children, action locks, DELETE confirmation, toggle rollback, and invalidation behave identically in preview and boards.
+- Error boundaries isolate template and display failures.
+- Empty, sample, stale, loading, failure, and success states are localized and accessible.
+- Keyboard, focus, responsive, reduced-motion, and narrow-widget behavior remain covered.
+
+### Server and adapters
+
+- Board IDOR, permission levels, anonymous actions, named-request kinds, substitutions, DNS classes, redirects, headers, response limits, caching, and rate limits remain covered.
+- Server tests run under an explicit Node environment rather than failing during client-environment initialization.
+- MCP schemas and descriptions remain discoverable, stable, and absent from unsafe runtime procedures.
+
+### Required commands
+
+At the end of the migration, the package and repository must pass:
+
+```sh
+pnpm --filter @homarr/custom-widgets test
+pnpm test
+pnpm test:e2e
+pnpm turbo typecheck --affected
+pnpm turbo lint --affected
+pnpm turbo build --filter=@homarr/docs
+pnpm check:custom-widget-bundle # after the Next.js production build
+```
+
+CI additionally checks dependency direction, cycles, file budgets, generated references, translations, and client bundle size.
+
+## Completion criteria
+
+- `@homarr/custom-widgets` owns every reusable custom-widget domain behavior.
+- No circular dependencies exist.
+- The package does not import `@homarr/api`, `@homarr/widgets`, or Next.js route modules.
+- Runtime and workbench networking uses injected typed ports.
+- One typed descriptor is the source of truth for each display type.
+- One shared JSX policy drives authoring diagnostics and runtime enforcement.
+- Create, edit, import, export, preview, MCP, and board runtime use the same typed transformations.
+- Public tRPC/MCP names, import formats, stored configuration, and permission behavior remain compatible.
+- V1 display-only migration and network-review states remain tested.
+- Production modules satisfy the 300/400-line budgets.
+- No untranslated user-facing strings remain.
+- Core, JSX, runtime, server, workbench, integration, E2E, accessibility, docs, and bundle checks pass.
+- A maintainer can locate a custom-widget behavior from the package structure without searching unrelated packages.
+
+## Explicit non-goals
+
+- Replacing Mantine or Homarr's visual language.
+- Allowing arbitrary cross-origin requests.
+- Replacing named requests with general JavaScript execution.
+- Changing stored secrets or exposing them through export or MCP.
+- Redesigning the current management UX during the package extraction.
+- Removing compatibility formats before migration and review flows are proven.
+
+## Decision record
+
+- The package owns all Custom Widget behavior, not only Custom JSX.
+- Security and correctness are hard constraints.
+- Maintainer simplicity is the primary tie-breaker after those constraints.
+- Current user and agent workflows are preserved during extraction.
+- Generated artifacts do not count toward source-size budgets.
+- Migration occurs through reviewable, behavior-preserving PRs rather than a single rewrite.

CHANGELOG.md

@@ -1,11 +1,3 @@
-## [1.74.0](https://github.com/homarr-labs/homarr/compare/v1.73.0...v1.74.0) (2026-08-07)
-
-## [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)

CHANGES.md

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

CODEOWNERS

@@ -206,14 +206,6 @@ packages/integrations/src/unraid @manuel-rw
 apps/docs/docs/integrations/uptime-kuma @ajnart
 packages/integrations/src/uptime-kuma @ajnart
 
-# What's Up Docker (WUD) - introduced in https://github.com/homarr-labs/homarr/pull/6523 by @tiimonn
-apps/docs/docs/integrations/whats-up-docker @tiimonn
-apps/docs/docs/widgets/whats-up-docker @tiimonn
-packages/api/src/router/widgets/wud.ts @tiimonn
-packages/integrations/src/wud @tiimonn
-packages/request-handler/src/wud.ts @tiimonn
-packages/widgets/src/wud @tiimonn
-
 # Traefik - by @Nerdy-Technician
 apps/docs/docs/integrations/traefik @Nerdy-Technician
 apps/docs/docs/widgets/traefik @Nerdy-Technician

Dockerfile

@@ -3,18 +3,12 @@
 FROM node:24.18.0-alpine AS base
 
 FROM base AS builder
-ARG TARGETPLATFORM
 WORKDIR /app
-# Native dependencies normally use prebuilds, but the build must remain
-# reproducible when a prebuild download times out and compilation is required.
-RUN apk add --no-cache libc6-compat curl bash python3 make g++
+RUN apk add --no-cache libc6-compat curl bash && apk update
 
 RUN corepack enable pnpm
-COPY .npmrc pnpm-lock.yaml pnpm-workspace.yaml package.json ./
+COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
 COPY patches ./patches
-COPY --parents ./apps/*/package.json ./packages/*/package.json ./tooling/*/package.json ./
-# @homarr/definitions generates documentation types during install.
-COPY --parents ./packages/definitions/src ./
 # Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
 # are configured with nodeLinker: hoisted. The applyPatchToDir function tries
 # to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
@@ -22,19 +16,17 @@ COPY --parents ./packages/definitions/src ./
 # isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
 # which IS created by pnpm fetch. The original hoisted linker is restored
 # before the install step so the final node_modules layout stays flat.
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
+RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
     pnpm config set store-dir /pnpm/store && \
     sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
-    pnpm fetch --ignore-scripts && \
+    pnpm fetch && \
     sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml
 
-# Install only from the fetched, committed lockfile so local and Docker builds
-# resolve the same dependency graph. Serial lifecycle builds avoid esbuild's
-# atomic binary replacement racing across the hoisted workspace (pnpm/pnpm#8200).
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store,sharing=locked \
-    npm_config_nodedir=/usr/local pnpm install --recursive --offline --frozen-lockfile --child-concurrency=1
-
 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
 
 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
@@ -45,9 +37,7 @@ RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
     --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \
     --mount=type=secret,id=TURBO_TOKEN,env=TURBO_TOKEN \
     --mount=type=secret,id=TURBO_REMOTE_CACHE_SIGNATURE_KEY,env=TURBO_REMOTE_CACHE_SIGNATURE_KEY \
-    --mount=type=cache,id=homarr-next-build-${TARGETPLATFORM},target=/app/apps/nextjs/.next/cache,sharing=locked \
-    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" \
-    pnpm turbo build --filter=@homarr/nextjs... --filter=@homarr/cli
+    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" pnpm build
 
 FROM base AS runner
 WORKDIR /app
@@ -95,6 +85,5 @@ ENV AUTH_PROVIDERS='credentials'
 ENV REDIS_IS_EXTERNAL='false'
 ENV NODE_ENV='production'
 
-EXPOSE 7575
 ENTRYPOINT [ "/app/entrypoint.sh" ]
 CMD ["sh", "run.sh"]

MANTINE.md

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

apps/docs/README.md

@@ -21,14 +21,8 @@ pnpm dev:docs
 
 # Or from within this directory
 pnpm dev
-
-# Point the docs at a local PocketBase instance
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
 ```
 
-The standalone docs use `WORKSHOP_API_URL` for PocketBase and `HOMARR_WEBSITE_URL` for the public site origin. The old
-`WORKSHOP_URL` name is a deprecated one-release alias.
-
 ## Build
 
 ```bash
@@ -46,7 +40,7 @@ Uses oxlint and oxfmt (same as the rest of the monorepo):
 ```bash
 pnpm lint        # oxlint
 pnpm format      # oxfmt (check)
-pnpm format:fix    # oxfmt (fix)
+pnpm format -- --write  # oxfmt (fix)
 ```
 
 ## Typecheck
@@ -61,8 +55,8 @@ pnpm typecheck
 docs/
 ├── getting-started/    # Installation guides, glossary, prerequisites
 ├── management/         # Boards, apps, users, integrations, settings, tasks, API
-├── integrations/       # 56 integration guides (one folder each)
-├── widgets/            # 43 widget guides (one folder each)
+├── integrations/       # 55 integration guides (one folder each)
+├── widgets/            # 42 widget guides (one folder each)
 ├── advanced/           # SSO, env vars, proxy, styling, CLI, development
 └── community/          # FAQ, donate, license, translations, get-in-touch
 ```
@@ -99,7 +93,7 @@ pnpm verify:search
 | Layer          | Technology                                  |
 | -------------- | ------------------------------------------- |
 | Site generator | Docusaurus 3 (`@docusaurus/preset-classic`) |
-| Styling        | Tailwind CSS 4 + Docusaurus Infima          |
+| Styling        | Tailwind CSS 3 + Docusaurus Infima          |
 | Icons          | `@tabler/icons-react`                       |
 | Diagrams       | Mermaid (`@docusaurus/theme-mermaid`)       |
 | Search         | Algolia DocSearch                           |

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

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

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

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

apps/docs/components.json

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

apps/docs/docs/advanced/_category_.json

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

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

@@ -1,43 +0,0 @@
-# Developer Docker CLI
-
-The host-side developer CLI builds and runs local Homarr images and pull-request previews. Run it directly from a checkout with `pnpm dev:cli -- ...`; no shell-specific setup script is required. It is separate from the recovery CLI included in production images.
-
-To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your Go bin directory available on `PATH`. GitHub CLI authentication is only needed for pull-request features.
-
-## Browse development images
-
-```bash
-pnpm dev:cli --
-```
-
-The main screen combines local `homarr:*` images with open pull requests and their GHCR preview status. Select an image to start or stop it, use `R` to build a remote pull request locally in the background or rebuild a local image, or use `p` to force a remote preview pull. Press `d` to switch to the instance dashboard and `d` again to return without losing the browser state. The explicit `dev` and `dash` subcommands start on either screen.
-
-A locally built PR image is folded into its remote PR row only when its recorded revision exactly matches the current GitHub head SHA. The row is marked `◆ local`, and starting it prefers that local image without a registry pull. Outdated local builds remain separate rows. Navigation and dashboard switching remain available during background builds.
-
-## Build images
-
-```bash
-pnpm dev:cli -- build <name>
-pnpm dev:cli -- build --pr <number> [name]
-```
-
-The first command builds the current checkout as `homarr:<name>`. The pull-request form uses a depth-one clone in a temporary directory and defaults to `homarr:pr-<number>` when `name` is omitted.
-
-## Rebuild images
-
-```bash
-pnpm dev:cli -- rebuild <name>
-```
-
-Images built by this CLI record their source checkout, revision, and optional pull-request number. Rebuild uses that provenance to select the original checkout or create a fresh temporary pull-request checkout.
-
-## Run images
-
-```bash
-homarr --pr <number> --env HOMARR_WEBSITE_URL=https://app-v2.preview.homarr.dev/
-homarr run <name>
-homarr run --pr <number>
-```
-
-The direct `homarr --pr <number>` form is shorthand for `homarr run --pr <number>`. Add `--detach` to run in the
-background, `--demo` to enable demo data, or repeat `--env KEY=VALUE` to provide additional environment variables.

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

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

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

@@ -25,20 +25,13 @@ This is especially useful for [docker secrets](https://docs.docker.com/engine/sw
 Using the `PUID` and `PGID` will require you to set the correct permissions on the mounted volumes and if used the docker socket. See more in the [Running as a different user](/docs/advanced/running-as-different-user) documentation.
 :::
 
-| Environment Variable     | Description                                                                                                                                                                                                                            | Possible values                     | Default                       |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ----------------------------- |
-| `PUID`                   | User ID to run the container as                                                                                                                                                                                                        | Any valid user ID                   | `0`                           |
-| `PGID`                   | Group ID to run the container as                                                                                                                                                                                                       | Any valid group ID                  | `0`                           |
-| `LOG_LEVEL`              | Log level to use                                                                                                                                                                                                                       | `debug` / `info` / `warn` / `error` | `info`                        |
-| `NO_EXTERNAL_CONNECTION` | Disables Homarr's internet-backed requests, including update checks, weather, and RSS feeds                                                                                                                                            | `true` or `false`                   | `false`                       |
-| `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag                                                     | `true` or `false`                   | `true`                        |
-| `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false`                       |
-| `HOMARR_WEBSITE_URL`     | Main Homarr documentation/site base used by runtime links. Must be an absolute HTTP(S) URL.                                                                                                                                            | HTTP(S) URL                         | `https://homarr.dev`          |
-| `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone documentation.                                                                                                                                                                            | HTTP(S) URL                         | `HOMARR_WEBSITE_URL`          |
-| `WORKSHOP_WEB_URL`       | Public Workshop website used by links in Homarr, Custom Widgets, onboarding, and assistant context.                                                                                                                                    | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
-
-Workshop service operators can find its server-only configuration in the
-[Workshop operator guide](../../workshop/operator#environment-variables).
+| Environment Variable     | Description                                                                                                                                                                        | Possible values                     | Default |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- | ------- |
+| `PUID`                   | User ID to run the container as                                                                                                                                                    | Any valid user ID                   | `0`     |
+| `PGID`                   | Group ID to run the container as                                                                                                                                                   | Any valid group ID                  | `0`     |
+| `LOG_LEVEL`              | Log level to use                                                                                                                                                                   | `debug` / `info` / `warn` / `error` | `info`  |
+| `NO_EXTERNAL_CONNECTION` | Disables some requests that need internet connection                                                                                                                               | `true` or `false`                   | `false` |
+| `ENABLE_DNS_CACHING`     | Enables dns caching. Enabled by default, but if you experience issues with IPv6 or static IPs, see [#4006](https://github.com/homarr-labs/homarr/issues/4006) or disable this flag | `true` or `false`                   | `true`  |
 
 ## Authentication
 
@@ -58,12 +51,11 @@ A random secret can be generated by using the following command: `openssl rand -
 
 ## Docker
 
-| Environment Variable  | Description                                                                                                                                                                                                          | Possible values                                         | Default |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
-| `DOCKER_SOCKET_PATHS` | Comma-separated mounted Docker-compatible socket paths. Homarr discovers each path as a selectable Docker environment                                                                                                | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
-| `DOCKER_HOSTNAMES`    | Comma-separated plaintext TCP hostnames. Pair each hostname with the port in the same position in `DOCKER_PORTS`                                                                                                     | For example `localhost,docker.example.com`              | -       |
-| `DOCKER_PORTS`        | Comma-separated plaintext TCP ports paired with `DOCKER_HOSTNAMES`                                                                                                                                                   | For example `2375,2376`                                 | -       |
-| `DOCKER_ENDPOINTS`    | Optional advanced JSON configuration for custom names, TLS, or restricted capabilities. It takes precedence over the simple variables above. See the [Docker and Podman connection guide](/docs/integrations/docker) | A JSON array of endpoint descriptors                    | -       |
+| Environment Variable  | Description                                     | Possible values                                                      | Default |
+| --------------------- | ----------------------------------------------- | -------------------------------------------------------------------- | ------- |
+| `DOCKER_HOSTNAMES`    | Comma 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
 
@@ -113,9 +105,6 @@ External redis is currently not supported with Proxmox Community Scripts
 The advanced deployments environment variables should only be used if you know what you are doing.
 :::
 
-| Environment Variable     | Description                                         |
-| ------------------------ | --------------------------------------------------- |
-| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts. |
-
-All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
-trailing slashes when Homarr or Docusaurus starts.
+| Environment Variable     | Description                                        |
+| ------------------------ | -------------------------------------------------- |
+| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts |

apps/docs/docs/advanced/icons/index.mdx

@@ -12,7 +12,7 @@ tags:
 
 Icons in Homarr are automatically requested from multiple sources:
 
-- [Dashboard Icons](https://dashboardicons.com/) - Our recommended source with more than 1,888 curated, high-quality icons
+- [Dashboard Icons](https://dashboardicons.com/) - Our recommended source with over 1888+ curated, high-quality icons
 - [selfh.st icons](https://github.com/selfhst/icons)
 - [Simple icons](https://github.com/simple-icons/simple-icons)
 - [Tabler icons](https://tabler-icons.io/)
@@ -21,7 +21,7 @@ Icons in Homarr are automatically requested from multiple sources:
 - **Local icons**: automatically fetched from the [medias feature](/docs/management/media/)
 
 Using these icon sources, Homarr provides a total collection of over 11,000 icons at your fingertips.
-The image picker searches this collection after a short typing delay. When a name is available, such as an app or search engine name, the picker uses it as the initial search. Results show your locally uploaded images first, followed by SVG icons and then other image formats.
+The icon picker is a fast searcher that helps you to find your desired icon simply by entering a search term.
 
 ### Finding Missing Icons
 
@@ -31,13 +31,7 @@ If you can't find the icon you're looking for in Homarr's built-in picker, we st
 
 Icons that are high quality and printable ([SVG](https://wikipedia.org/wiki/Scalable_Vector_Graphics)) are marked with a red badge "SVG" at the top right.
 
-You can clear the selected image with the clear button or the usual keyboard shortcut for deleting a line (Command+Backspace on macOS or Control+Backspace on other platforms). Clearing the field does not restore the previous image.
-
 ### Using external icons
 
 If you don't find the icon you're looking for on Dashboard Icons or wish to use a different source, you can simply enter a URL that points to an icon.
-Direct HTTP(S) image URLs are used as entered instead of being searched in the built-in repositories. The picker previews the image and shows whether it loaded successfully. It is important that the URL directly points to the file without any advertisements or elements around it.
-
-### Uploading a local image
-
-Users with media upload permission can select **Upload image** next to the field. After the upload finishes, the new local image is selected immediately and is available at the top of future searches.
+It is important that the URL directly points to the file without any advertisements or elements around it.

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

@@ -6,51 +6,11 @@ tags:
 
 Homarr has the following keyboard shortcuts:
 
-| Shortcut                                        | Description                                                                                                                |
-| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| `MOD` + `K`                                     | Opens the search bar                                                                                                       |
-| `MOD` + `J`                                     | Toggles Dark Mode                                                                                                          |
-| `MOD` + `E`                                     | Toggles Edit Mode                                                                                                          |
-| Hold `Shift` for 500 ms over a supported widget | Opens its temporary advanced view                                                                                          |
-| `Shift` + `Enter` on a supported widget         | Opens its advanced view until it is closed                                                                                 |
-| `Esc`                                           | Stops keyboard tile editing, cancels an active pointer or touch move/resize, or closes an open advanced view or board menu |
-
-## Widget advanced view
-
-Supported widgets open a temporary advanced view when you hold `Shift` over them for 500 ms. Focus a widget and press
-`Shift` + `Enter`, or use its menu, to keep the advanced view open.
-
-## Board editing
-
-`MOD` + `E` enters edit mode. Homarr keeps the current board visible while the editor prepares; movement and resizing become available when it is ready.
-
-When a tile is focused in edit mode:
-
-| Shortcut             | Description                                                                 |
-| -------------------- | --------------------------------------------------------------------------- |
-| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
-| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
-| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
-| `Esc`                | Stops keyboard editing without undoing its changes                          |
-
-Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
-Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
-
-On touch screens, press and hold a tile before moving it; a quick tap does not start a drag. Resize handles accept direct touch input. During a pointer or touch move or resize, `Esc` cancels the interaction and restores the layout from before it started.
-
-## Board editing
-
-When a tile is focused in edit mode:
-
-| Shortcut             | Description                                                                 |
-| -------------------- | --------------------------------------------------------------------------- |
-| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
-| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
-| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
-| `Esc`                | Stops keyboard editing without undoing its changes                          |
-
-Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
-Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
+| Shortcut    | Description          |
+| ----------- | -------------------- |
+| `MOD` + `K` | Opens the search bar |
+| `MOD` + `J` | Toggles Dark Mode    |
+| `MOD` + `E` | Toggles Edit Mode    |
 
 :::tip
 

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

@@ -49,6 +49,7 @@ services:
       traefik.http.routers.homarr.rule: Host(`your.internal.dns.address.here.com`)
       traefik.http.routers.homarr.entrypoints: websecure
       traefik.http.routers.homarr-secure.app: homarr
+      traefik.http.apps.homarr.loadbalancer.server.port: 7575
 
 networks:
   proxy:

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

@@ -128,8 +128,6 @@ Homarr supports multiple authentication options, from internal userbase (credent
 
     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
@@ -207,7 +205,6 @@ Homarr supports multiple authentication options, from internal userbase (credent
     | ``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

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

@@ -85,8 +85,8 @@ To do this, enter the board settings:
 
 ![](./img/enter-board-settings.png)
 
-Scroll to the **Custom CSS** section on the board settings page. It is part of the unified settings form; enter your CSS
-there and save the board settings to apply it to that board.
+Scroll down a bit and click on custom CSS.
+Here you can enter your CSS code, which will be applied on the respective board page.
 
 ![](./img/custom-css-setting.png)
 

apps/docs/docs/community/_category_.json

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

apps/docs/docs/community/faq.mdx

@@ -27,21 +27,11 @@ So make sure to manually whitelist this address.
 
 ### Can I add my own widgets? Do I need programming skills?
 
-Yes. A [Custom Widget](/docs/management/custom-widgets) can read a public or private HTTP API.
+Yes. Administrators can create [Custom Widgets](/docs/management/custom-widgets) that read an HTTP API and render the response with a built-in display type. These display types require no programming.
 
-It can show responsive Mantine JSX. It can also use widget options and actions with board permission checks.
+Custom JSX is available when you need a more specific layout or an interactive control. It uses a restricted declarative JSX interpreter with a classified Mantine component set. Network operations are declared as named, same-origin requests and are checked against board permissions on the server. It does not execute arbitrary JavaScript or expose browser `fetch`.
 
-Custom JSX v2 is the only Custom Widget format. Write the JSON and JSX in the workbench.
-
-You can also use the AI copy prompt. An MCP agent can validate and preview a definition before it saves the definition.
-
-The workbench reads a pasted AI response. It shows request capabilities and redacted diagnostics.
-
-A template cannot import packages or run arbitrary JavaScript. It cannot call browser `fetch`.
-
-Named requests use the Homarr server. The server applies board permissions and the network policy.
-
-Before installation, examine the origins, methods, permissions, and actions. Use the same review before publication.
+You should be comfortable reading JSON and JSX to author complex templates. The management workbench includes examples, diagnostics, a component reference, API response inspection, and a prompt you can copy into an AI assistant. Always review imported templates and request capabilities before saving them.
 
 ### Is it secure to expose Homarr to the web?
 

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

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

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

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

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

@@ -2,9 +2,9 @@
 
 <img src="https://raw.githubusercontent.com/homarr-labs/charts/refs/heads/main/charts/homarr/icon.svg" align="right" width="92" alt="homarr logo">
 
-![Version: 8.26.0](https://img.shields.io/badge/Version-8.26.0-informational?style=flat)
+![Version: 8.22.0](https://img.shields.io/badge/Version-8.22.0-informational?style=flat)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat)
-![AppVersion: v1.74.0](https://img.shields.io/badge/AppVersion-v1.74.0-informational?style=flat)
+![AppVersion: v1.70.0](https://img.shields.io/badge/AppVersion-v1.70.0-informational?style=flat)
 
 A Helm chart to deploy homarr for Kubernetes
 
@@ -263,7 +263,7 @@ httproute:
             value: /
       backendRefs:
         - name: homarr
-          port: 7575
+          port: 8080
 ```
 
 </details>
@@ -427,17 +427,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.74.0"`                                                                                                                                                                                                                                      | Overrides the image tag whose default is the chart appVersion                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| image.tag                                          | string | `"v1.70.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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

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

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

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

@@ -24,11 +24,12 @@ import { dockerContainersWidget } from "@site/docs/widgets/docker-containers";
   ]}
 />
 
-## Connecting Docker to Homarr
+## Enabling the Docker integration
 
-Docker connections come directly from Homarr's environment variables. They are automatically available in the Docker management table and Docker widget; you do not create a Docker integration under **Management → Integrations**.
-
-If Homarr runs directly on a host with Docker installed, it uses `/var/run/docker.sock` by default. When Homarr runs in a container, mount the [Docker socket](https://docs.docker.com/engine/security/protect-access/) into it so Homarr can interact with Docker.
+This integration must first be enabled.
+If you directly run on the host system and you have docker installed, it will be enabled by default.
+Otherwise, you'll need to mount the [docker socket](https://docs.docker.com/engine/security/protect-access/) to the Homarr container,
+so Homarr can interact with the Docker service.
 
 In Docker Compose, you can simply add this line:
 
@@ -53,157 +54,9 @@ 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
-```
-
-For remote socket proxies, list the hostnames and matching ports in the same order:
-
-```yaml
-environment:
-  DOCKER_HOSTNAMES: docker-proxy-home,docker-proxy-lab
-  DOCKER_PORTS: 2375,2375
-```
-
-Homarr automatically discovers each comma-separated entry as a separate Docker environment. All environments are selected by default; the Docker widget lets you select one or more without any additional setup.
-
-:::warning[Plaintext TCP]
-Plaintext Docker TCP can grant unauthenticated control of the Docker host. Prefer a local socket, a least-privilege socket proxy on a private Docker network, or TLS.
-:::
-
-### Advanced endpoint configuration
-
-Most users should use the comma-separated variables above. Use `DOCKER_ENDPOINTS` only when you need custom names, TLS, or restricted capabilities. It is a JSON array where every endpoint declares its identity, transport, and capabilities:
-
-```yaml
-services:
-  homarr:
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - ./docker-ca.pem:/run/secrets/docker-ca.pem:ro
-    environment:
-      DOCKER_ENDPOINTS: >-
-        [
-          {
-            "id": "local",
-            "name": "Local Docker",
-            "kind": "docker",
-            "transport": { "type": "socket", "path": "/var/run/docker.sock" },
-            "capabilities": ["inventory", "logs", "lifecycle", "remove"]
-          },
-          {
-            "id": "remote-read-only",
-            "name": "Production inventory",
-            "kind": "docker",
-            "transport": {
-              "type": "tls",
-              "host": "docker.example.com",
-              "port": 2376,
-              "caPath": "/run/secrets/docker-ca.pem"
-            },
-            "capabilities": ["inventory", "logs"]
-          }
-        ]
-```
-
-The stable `id` keeps containers from different endpoints distinct. `name` is shown in the interface, and `kind` can be `docker` or `podman`. Every endpoint must include the `inventory` capability; optionally add `logs`, `lifecycle`, and `remove`. Homarr hides or disables actions the endpoint does not allow and also enforces the same capabilities on the server.
-
-Supported transports are:
-
-- `socket`: an absolute in-container `path`
-- `tls`: `host`, `port`, and an absolute `caPath`; add both `certPath` and `keyPath` for mutual TLS
-- `tcp`: `host`, `port`, and the explicit acknowledgement `allowInsecure: true`
-
-The structured configuration refuses TCP unless `allowInsecure` is explicitly set to `true`. When `DOCKER_ENDPOINTS` is set, it takes precedence over `DOCKER_SOCKET_PATHS`, `DOCKER_HOSTNAMES`, and `DOCKER_PORTS`.
-
 ### Managing your Docker containers within Homarr
 
 Homarr allows you to interact with Docker containers running on your system.
-The collapsed **Assisted Docker setup** helper optionally compares visible containers with your existing Homarr apps and integrations. Open it only when you want setup suggestions; it never blocks normal container management. Every service stays distinct by Docker endpoint and container ID, including multiple containers that use the same integration type.
-
-Homarr can show a service as:
-
-- **Ready to connect** when its image or name matches a supported integration
-- **New service** when it can be added as an app but no integration is recognized
-- **Already represented** or **Linked** when an app or integration already matches
-- **Address changed** when a service appears to match an integration but its reachable address has changed
-
-Set the usual server address once, then choose whether services normally use different ports, subdomains, or paths. Homarr uses that pattern to prefill every detected service. Each suggestion has one editable URL field with the generated and Docker-reported addresses available as autocomplete options, so you can select a suggestion or type any address directly.
-
-:::info[Review before changing]
-Service discovery is read-only. Homarr never creates or changes an app or integration automatically. **Set up integration** opens the standard prefilled integration form, while **Create app** opens the existing Docker app form, so you can review and confirm the final setup.
-:::
-
-Suggestions appear as a compact task list. Expand an item only when you want to edit its URL or inspect relevant setup statuses. Use the filters to focus on services that need attention or those already represented in Homarr. Refresh runs discovery again. Dismissed suggestions are stored in the current browser using their endpoint-qualified service identity and can be restored from the same helper. If multiple existing items could match, Homarr marks the result as ambiguous and does not choose one automatically.
-
-Compact status icons summarize the setup information Homarr can act on. Unknown and non-applicable runtime layers are omitted to keep the helper focused; use the integration form's connection test or the relevant board action for live diagnostics.
-
-If one Docker endpoint is unavailable, Homarr reports that endpoint while continuing to show services from healthy endpoints. An unavailable endpoint is not treated as an empty Docker installation.
-
 Each container row has an action menu with the following options:
 
 - **View logs** - opens a dedicated logs page with a live terminal
@@ -227,10 +80,6 @@ This opens a dedicated page with an xterm.js terminal that streams the container
 The Docker management table supports optional **CPU usage** and **Memory usage** columns.
 These columns are hidden by default and can be toggled on from the table column visibility settings.
 
-#### Choosing Docker environments in the widget
-
-The Docker widget can show one or more configured Docker environments. Leave **Docker environments** empty to include every endpoint, which is also the default for existing widgets. Selecting one or more entries limits container and statistics requests to those endpoints.
-
 #### Add apps from containers
 
 Homarr also lets you add apps from containers. You can simply select all containers you want to add an app for and then click the `Add to Homarr` button.
@@ -243,13 +92,11 @@ They are then available in the app list and can be used as normally added apps.
 
 ![Apps added from containers](img/add-to-homarr-apps.png)
 
-### Container labels
+### Configuration
 
-`homarr.hide` excludes a container from the Docker Containers widget, tools page, and onboarding discovery whenever the
-label is present.
+Currently Homarr supports one label for configuration of the containers:
 
-During first-run onboarding, Homarr can also discover apps, integrations, groups, and compatible widgets from
-`homarr.*` labels, with Homepage labels as a fallback. See the complete [Docker label reference](/docs/integrations/docker-labels).
+- **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
 
 ### Security
 

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

@@ -43,11 +43,12 @@ import { immichServerStatsWidget } from "../../widgets/immich-server-stats";
     <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>.
+    <br />
+    Additional permissions may be required depending on your Immich version. If you encounter authorization errors, grant any missing permissions requested by the server.
 
   </span>
 

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

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

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

@@ -10,15 +10,14 @@ import { AddingIntegration } from "@site/src/components/integrations/adding";
 import { IntegrationSecrets } from "@site/src/components/integrations/secrets";
 import { navidromeIntegration } from ".";
 import { audioStatsWidget } from "@site/docs/widgets/audio-stats";
-import { mediaServerWidget } from "@site/docs/widgets/media-server";
 
-<IntegrationHeader integration={navidromeIntegration} categories={["Media", "Media server"]} />
+<IntegrationHeader integration={navidromeIntegration} categories={["Media"]} />
 
-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 }]} />
+<IntegrationCapabilites items={[{ widget: audioStatsWidget }]} />
 
 ### Adding the integration
 

apps/docs/docs/integrations/whats-up-docker/index.mdx

@@ -1,48 +0,0 @@
----
-title: "What's Up Docker"
-description: "What's Up Docker (WUD) watches your Docker containers and reports which ones have newer image versions available."
-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 { wudIntegration } from ".";
-import { wudWidget } from "@site/docs/widgets/whats-up-docker";
-
-<IntegrationHeader integration={wudIntegration} categories={["Health Monitoring"]} />
-
-The What's Up Docker integration lets Homarr connect to your [WUD](https://github.com/getwud/wud) instance so you can see how many of your watched containers have image updates available directly from your dashboard.
-
-### Widgets & Capabilities
-
-<IntegrationCapabilites items={[{ widget: wudWidget }]} />
-
-### Adding the integration
-
-<AddingIntegration />
-
-:::info URL configuration
-Use the root URL of your WUD instance, for example `https://wud.example.com`. Homarr calls the `/api/app` and `/api/containers` endpoints under that URL automatically.
-:::
-
-### Secrets
-
-WUD does not require authentication by default. If your instance is protected with [Basic Authentication](https://github.com/getwud/wud/blob/main/docs/configuration/authentications/basic/README.md), you can provide a username and password.
-
-<IntegrationSecrets
-  secrets={[
-    {
-      credentials: [],
-      steps: [],
-    },
-    {
-      credentials: ["username", "password"],
-      steps: [
-        "Open your WUD instance's configuration and configure a WUD_AUTH_BASIC_* user as described in the WUD documentation",
-        "Enter that username and password in Homarr — Basic authentication is handled automatically",
-      ],
-    },
-  ]}
-/>

apps/docs/docs/integrations/whats-up-docker/index.ts

@@ -1,9 +0,0 @@
-import { IntegrationDefinition } from "@site/src/types";
-
-export const wudIntegration: IntegrationDefinition = {
-  name: "What's Up Docker",
-  description:
-    "What's Up Docker (WUD) watches your Docker containers and reports which ones have newer image versions available.",
-  iconUrl: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@master/svg/whats-up-docker.svg",
-  path: "../../integrations/whats-up-docker",
-};

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

@@ -82,65 +82,4 @@ The OpenAPI and MCP APIs include board management endpoints for common automatio
 - Set desktop and mobile home boards for the current user
 - Configure global board defaults such as public home boards and status behavior
 
-Board layout responses identify each layout with a `mobile`, `base`, or `custom` role. Mobile and Base are protected. Layout-saving clients must preserve existing roles, keep Mobile at breakpoint `0`, keep Base as the highest breakpoint, and use unique custom breakpoints between them. The layout save operation returns the canonical saved layouts, including server-generated IDs for new custom layouts. A non-Base layout can be regenerated from Base with the protected reset operation.
-
 Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
-
-## Docker action payload migration
-
-Docker lifecycle and removal actions now identify each container with both its Docker endpoint and container ID. This is a
-breaking change for tRPC and MCP clients that previously sent an `ids` array to the start, stop, restart, or remove action.
-
-Replace the old payload:
-
-```json
-{ "ids": ["container-id"] }
-```
-
-with endpoint-qualified targets:
-
-```json
-{
-  "targets": [{ "endpointId": "local", "id": "container-id" }]
-}
-```
-
-Read `endpointId` and `id` from `docker.getContainers` (MCP tool `docker_getContainers`) immediately before the action.
-Pass those pairs unchanged to `docker.startAll`, `docker.stopAll`, `docker.restartAll`, or `docker.removeAll`; their MCP tool
-names use underscores, such as `docker_restartAll`. Endpoint qualification prevents identical container IDs on different
-Docker or Podman endpoints from targeting the wrong service.
-
-`docker.getContainers` also accepts an optional `endpointIds` array. Omit it or pass an empty array to query every configured
-Docker environment, or pass one or more IDs returned by `docker.getEndpoints` to query only those Dockerode clients. The
-Docker widget uses the same behavior for its environment selector.
-
-## Partial integration failures
-
-Multi-integration widget queries keep data from integrations that remain available. Calendar and media-server results include
-an optional `error` on a failed integration; media-request responses expose a `failedIntegrations` array, and the latest
-requests endpoint returns its items in `requests`. When every selected integration fails, the query returns an error instead
-of a partial response.
-
-Other widgets use the same settlement pattern with endpoint-specific shapes: a failed integration may appear as a named
-fallback row, in a failure array, or be omitted while healthy results remain. Widget pages should identify the shape they
-render rather than assuming every query exposes an `error` field.
-
-### 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.
-
-## Get Custom Widget authoring resources
-
-Custom JSX v2 provides four HTTP discovery endpoints:
-
-- `GET /api/custom-widgets/authoring-prompt` returns the current prompt plus MCP and HTTP resource identifiers.
-- `GET /api/custom-widgets/schema` returns the canonical widget JSON Schema.
-- `GET /api/custom-widgets/components` returns the release-matched static component catalog.
-- `GET /api/custom-widgets/skill` returns the concise live `SKILL.md` plus skills.sh, source, and install metadata. Retrieve the schema, component catalog, and examples through their dedicated resources only when needed.
-
-Call `customWidget_configurationRequestUser` to create a temporary API source setup URL where the user can confirm their server URL and enter credentials. Do not construct or save this URL.
-
-Authenticated tRPC and MCP procedures support definition management, validation, previews, template patches, and credential writes. An exported definition does not contain credentials.

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

@@ -28,7 +28,7 @@ The name must be at least one character long and can be chosen freely.
 ### Icon URL
 
 This is the URL to the icon that will be displayed on the app widget.
-You can paste a direct HTTP(S) URL to an image, search the included icon repositories by name, or upload a local file through the upload button. The app name is pre-filled as the initial library search when no image is selected. Local images appear first, followed by SVG icons and other formats. Direct image URLs are previewed, used as entered, and are not searched in the icon repositories.
+It can be a url to an image in the internet, one from the included icon repositories or a local file uploaded through the upload button.
 
 ![Icon URL](./img/app-icon-url.png)
 
@@ -40,17 +40,14 @@ An optional description that can be shown as tooltip on the app widget.
 
 The URL to the website you want to link to. Clicking on the app widget or bookmark will open this URL.
 
-You can also use custom URI schemes such as `vscode://file/path`, `microsoft-edge:https://example.com`, or `myapp://open` to link to local applications or third-party programs. We trust that you know what you are doing — only `javascript:` URIs are blocked for security reasons.
-
 ### Ping URL
 
 When you want to use another url for the simple status check you can set it here.
 This will allow you to set a different URL for the ping than the URL that is opened when clicking on the app widget.
 It's useful when you want to ping the service internally for example with a custom ip but open the website externally.
-Note that the ping URL only accepts `http://` and `https://` URLs — custom URI schemes are not supported for pings.
 
 ## List of apps
 
-On the apps management page you find all apps that exist in your Homarr instance. Search by name or URL, open an app directly, or use its row actions to edit and delete it. A filtered search can be cleared without leaving the page.
+On the apps management page you find all apps that exist in your Homarr instance. You can edit and delete them.
 
-Any signed-in user can view this list. Creating, editing, and deleting apps requires the corresponding app permission; board permissions are not required.
+![Apps list](./img/app-list.png)

apps/docs/docs/management/assistant.mdx

@@ -1,68 +0,0 @@
----
-description: Configure and use Homarr Assistant.
-tags:
-  - Assistant
-  - AI
-  - Administration
----
-
-# Assistant
-
-Homarr Assistant can answer questions and manage Homarr for you. It uses the signed-in user's permissions and asks for
-approval before making changes.
-
-![Homarr Assistant conversation with suggested prompts](/img/assistant/conversation.png)
-
-## Set it up
-
-Open **Management → Assistant**.
-
-![Assistant provider, credentials, and model configuration](/img/assistant/configuration.png)
-
-1. Select a provider and check its API URL.
-2. Enter an API key when required, then save the connection.
-3. Refresh the model list and select a model.
-4. Enable the assistant and save.
-
-Choose a provider preset or use **Custom endpoint** with an OpenAI-compatible Chat Completions API. The
-[Homarr provider](../workshop/homarr-provider) is the default and needs no administrator API key. The Homarr team pays
-for a limited number of Assistant uses for each user every day; users sign in to the Community Workshop to use them.
-
-:::info Local model servers
-
-Inside a container, `localhost` means the Homarr container. Use the model server's container name, local DNS name, or
-host gateway address.
-
-:::
-
-## Use it
-
-- Select **Assistant** in the user menu or press `Shift + A`.
-- Ask from `Cmd/Ctrl + K`.
-- Add the [Assistant widget](../widgets/assistant) to a board.
-
-The assistant can work with boards, apps, integrations, widgets, Custom Widgets, and connected services. Use `@` to
-add Homarr items as context, `/` for shortcuts, and the paperclip for supported files.
-
-Each request includes the user's name, current page and board, home board, server time, browser time zone, and a small
-summary of accessible Homarr resources. Live status is fetched only when needed.
-
-## Permissions and privacy
-
-- Read-only actions can run automatically. Changes require approval.
-- Homarr permissions apply to every tool call and mentioned item.
-- API keys and custom headers are encrypted and never returned to the browser.
-- Conversations are stored per user and can be exported or deleted.
-
-Prompts, attachments, tool definitions, and tool results are sent to the selected model provider. Review that
-provider's privacy policy before enabling the assistant.
-
-## Troubleshooting
-
-- **No models found:** check the base URL, model discovery path, and API key. You can enter a model ID manually.
-- **Assistant is unavailable:** enable it and save the configuration.
-- **Tool calls stop:** select a model that supports streaming and tool calls.
-- **Local endpoint is unreachable:** check container networking and the server's listen address.
-
-See [MCP](./mcp) for external AI clients and [Custom Widget agent authoring](./custom-widgets/agent-authoring) for the
-widget authoring workflow.

apps/docs/docs/management/backup.mdx

@@ -22,8 +22,6 @@ Navigate to `Management` → `Tools` → `Backup`. You must have **admin** permi
 
 ## Exporting a Backup
 
-![Export database card with the Download Backup action](/img/backup/export-database.png)
-
 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                                                         |
@@ -31,12 +29,10 @@ Click the **Export** button in the export card. You'll be prompted to type `I un
 | `db.sqlite`     | Full SQLite database with all entities                              |
 | `metadata.json` | Backup metadata: Homarr version, creation timestamp, encryption key |
 
-The backup contains the complete database. It includes Custom Widgets and all other Homarr configuration.
+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
 
-![Restore database card with the backup ZIP drop zone](/img/backup/restore-database.png)
-
 ### 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.
@@ -53,9 +49,6 @@ Before restoring, Homarr uses **sql.js WASM** to analyze the backup directly in
 
 Type `I understand` to acknowledge that restoring will replace your current database. This cannot be undone.
 
-During first-run onboarding, the database is still empty, so the restore preview goes directly to **Restore Database**
-without the extra typed confirmation. After Homarr restarts, onboarding opens the restored default home board.
-
 ### 4. Restore
 
 The backup ZIP is sent to the server, validated, and applied. After a successful restore:

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

@@ -11,19 +11,15 @@ tags:
 
 import iconColorImage from "./img/icon-color.png";
 import itemRadiusImage from "./img/item-radius.png";
-import layoutSettingsImage from "./img/layout-settings.png";
-import layoutSettingsCustomRailsImage from "./img/layout-settings-custom-rails.png";
-import boardViewModeImage from "./img/board-view-mode.png";
-import boardEditModeImage from "./img/board-edit-mode.png";
-import keyboardTileEditingImage from "./img/keyboard-tile-editing.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.
 Boards can be restricted to user groups.
-A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/boards).
-Other boards can be viewed by direct links (e.g. my-homarr.com/boards/smart-home) or via the management pages.
-The management page includes a compact structural preview of each board's Base layout so you can recognize it before
-opening it. Containers include their visible widgets and app icons instead of appearing empty.
+A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/board).
+Other boards can be viewed by direct links (e.g. my-homarr.com/board/smart-home) or via the management pages.
 
 Names of boards must be unique because this will be used in the URL to load the desired board.
 
@@ -40,15 +36,13 @@ 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, and always fits it to the available width without horizontal scrolling.
-The main canvas and enabled rails stay at least one viewport tall, and the canvas grows automatically while you drag or resize items near its lower edge.
+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
@@ -61,8 +55,6 @@ Alternatively, you can also navigate from the board page itself using the cog ic
 
 ![](./img/navigate-to-settings-2.png)
 
-All board settings are edited on a single page. Click the **Save changes** button in the save bar at the bottom to apply them, or **Discard** to restore the last saved values. The save bar only appears when you have unsaved changes. Access control and the Danger zone are independent sections and are applied immediately.
-
 ### General
 
 #### Page title
@@ -94,170 +86,32 @@ 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 the layout with the highest breakpoint that is not wider than the current screen, 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
-  src={layoutSettingsImage}
-  alt="Board settings showing protected Mobile and Base responsive layouts with rail controls"
-  style={{ maxWidth: "100%" }}
-/>
+![](./img/layout-settings.png)
 
-The layout cards show the representative geometry used for planning. This current example also shows a custom layout
-with both fixed rails enabled; the rails reserve columns and the remaining canvas reflows automatically.
-
-<img
-  src={layoutSettingsCustomRailsImage}
-  alt="Board layout settings with a custom layout and both fixed rails enabled"
-  style={{ maxWidth: "100%" }}
-/>
-
-Every board has two protected layouts. Creating a board adds **Mobile** at `0px` with three columns and **Base** at
-`768px` with the column count you choose. Both layouts can be edited, but neither can be removed.
-
-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 complete canvas always fits the available width and never adds horizontal board scrolling.
-
-- **Mobile** starts at `0px` and uses three columns on new boards.
-- **Base** is the widest layout and starts at `768px` on new boards.
-
-Mobile and Base can be renamed and their column counts can be changed, but they cannot be removed. Mobile has no fixed
-rails; rail configuration is available only on Base and custom layouts. You can add removable custom layouts between
-their breakpoints.
-
-Each layout stores independent positions and sizes. Moving or resizing a widget while editing Mobile does not move it in
-Base or any custom layout. New custom layouts start from Base's current column count and rail widths; Homarr chooses a
-free breakpoint between Mobile and Base, and you can then change the breakpoint, columns, and rails.
-
-Older or incomplete boards are repaired automatically. A board with no layouts receives Mobile at `0px` with three
-columns and Base at `768px` with ten columns. A board with one layout keeps it as Base and receives a generated Mobile
-layout. With multiple layouts, the narrowest becomes Mobile, the widest becomes Base, and intermediate layouts remain
-custom. Duplicate or out-of-order breakpoints are normalized without discarding saved positions.
-
-Use **Reset from Base** on Mobile or a custom layout to replace all of its positions and sizes with a newly generated version of Base. The layout's name, breakpoint, and column count are kept.
-
-The canvas is at least one window tall, even when it is empty.
-Its left and right edges are hard drag boundaries, while its bottom edge extends automatically as a tile is dragged or resized downward.
-Nested Containers keep their own resizable bounds.
-New items use their widget's default size and new Containers use a useful `4 × 3` size when space allows.
+On each element the position and size of items can be changed seperately.
+When adding a new layout the position and sizes will automatically be generated depending on the column count.
+When adding a new item / dynamic section that will always be 1x1 on each layout and placed on the first available position.
 
 #### Name
 
-The name of the layout can be chosen freely. It is only used for management and is not displayed 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
 
-The total number of columns in the layout. Changing it projects the saved positions and sizes into the new grid width without overlap.
-
-#### Fixed rails
-
-Each responsive layout can enable a fixed left rail, a fixed right rail, or both.
-Set a rail 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.
-
-Rail columns are reserved from the layout's total column count.
-For example, a 12-column layout with a two-column left rail leaves ten columns for the canvas.
-The combined rail widths cannot consume the final main-canvas column.
-Enabling or widening a rail reflows canvas items into the remaining columns.
-Disabling a rail moves its contents back into the next available canvas positions.
-
-Rails fill the available window height and remain fixed while the page scrolls. They do not grow or scroll independently.
-Apps, widgets, and Containers inside them still use the same fixed `200 × 200` cells and can be rearranged in edit mode, where each rail shows its name and boundary.
+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
 
-The minimum screen width where the layout is used; a layout is eligible at its breakpoint and above. Mobile is fixed at
-`0px`. Custom breakpoints must be unique and sit between Mobile and Base. Base must remain the highest breakpoint.
-When the initial viewport is not available, Homarr uses its remembered viewport information, client hints, or User-Agent
-fallback to select a layout.
-
-#### 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.
-Collapsed Containers are expanded while editing so their contents and controls are reachable.
-
-<img
-  src={boardViewModeImage}
-  alt="A Homarr board in view mode with the dashboard canvas and static widgets visible"
-  style={{ maxWidth: "100%" }}
-/>
-
-Widget content is inert in edit mode, so dragging from the inert widget area moves the tile instead of activating the widget;
-settings and other controls remain usable in the compact header above the tile.
-A single compatible collision can swap two items when both resulting placements fit, including different-sized or lateral moves.
-For other collisions, or when a tile grows into occupied space, nearby tiles are compacted out of the way and collision chains reflow.
-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.
-Use the pencil button in the board header to enter edit mode; click it again to save. If you leave the page with unsaved
-changes, Homarr asks whether to discard them. If the editor cannot load, the board remains in view mode.
-
-<img
-  src={boardEditModeImage}
-  alt="Board in edit mode with the board header controls and editable dashboard tiles visible"
-  style={{ maxWidth: "100%" }}
-/>
-
-While edit mode is active, **Add board content** opens the same Universal Create surface as the global header action and
-Spotlight. It can add a widget, app, integration, Container, board, Workshop item, or Custom Widget when the
-current user and context allow it. Widget setup offers the main canvas, enabled rails, and existing Containers as
-destinations before the widget is created, so the common flow does not require a second move step.
-
-The widget editor also lists its selected integrations. Users with full access can choose **Edit connection** to test,
-diagnose, and repair an integration without leaving the board. A successful repair refreshes the affected widget; the
-saved integration changes apply everywhere that connection is used.
-
-Pointer users can drag from the inert widget area; interactive controls are excluded. Containers use the grab button at their top-left corner.
-Widgets can be resized from any edge or corner handle. Activate a Container's chrome with its top-left grip before using
-its resize handles.
-On a touch screen, press and hold a tile for about `200 ms` before moving it; a quick tap does not start a drag. Resize
-handles support direct touch input.
-Keyboard users can focus a tile, press Enter or Space to start editing, use the arrow keys to move it, and use Shift plus the arrow keys to resize it.
-Press Enter, Space, or Escape to stop keyboard editing.
-Keyboard moves and resizes apply immediately within the current canvas, rail, or Container; they cannot move an item
-between grids. Use pointer drag or **Move / resize item** for that.
-Escape stops keyboard editing without undoing those changes.
-During a pointer or touch interaction, Escape cancels the move or resize and restores the layout from before that interaction.
-Invalid, outside, or otherwise forbidden drops are cancelled in the same way.
-The **Move / resize item** action in the edit menu remains available for precise numeric input.
-
-<img
-  src={keyboardTileEditingImage}
-  alt="A focused board tile in keyboard editing mode"
-  style={{ maxWidth: "100%" }}
-/>
+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
 
-Layout Settings shows a lightweight structural preview for every layout, including saved spans, Containers, widget labels, and app icons.
-It uses a representative viewport width to project the saved geometry; it does not execute widget queries or represent every
-pixel of the screen range where the layout is active.
-
-Choose **Edit layout** to open the real board editor at that representative width on desktop. Save returns to Layout Settings. Cancel discards the local changes. On phones and tablets, the normal board editor continues to use the layout selected by the device width.
-
-### Containers and rails
-
-Containers can hold apps, widgets, and nested Containers.
-The same Container model works on the main canvas, inside a fixed rail, or inside another Container.
-Move and resize Containers directly in edit mode; nested content stays within the Container's local bounds.
-Resize outlines follow the pointer continuously while a dashed preview marks the grid size that will be applied on release.
-Each responsive layout stores its own Container position and size.
-
-Each Container can configure:
-
-- Its label and whether that label is visible.
-- Whether users can collapse and expand it like an accordion.
-- Whether its menu shows **Open all in new tabs** for the app links it contains.
-- Its border color and custom CSS classes.
-
-Collapsing a Container reduces its full-width header to a half-row expansion bar and compacts the surrounding layout without losing its expanded size.
-Expanding it smoothly restores those bounds and moves following items out of the way without reloading the widgets inside it.
+<img src={layoutSmallImage} height={256} />
+<img src={layoutMediumImage} height={256} />
+<img src={layoutLargeImage} height={256} />
 
 ### Background
 
@@ -303,7 +157,7 @@ Change the color of your bookmark / app icons.
 
 #### Item radius
 
-Change the radius of your items and Containers.
+Change the radius of your items / categories.
 
 <img src={itemRadiusImage} height={100} />
 
@@ -312,11 +166,6 @@ Change the radius of your items and Containers.
 This is the field where you can enter custom CSS.
 The styling will only be applied on the respective board page.
 
-When Homarr Assistant is enabled, users with modify permission can also ask it to edit the board's General, Background,
-Appearance, Custom CSS, and app-status settings. The assistant reads the current stylesheet first and presents an
-editable review form before requesting approval to save the change. It does not edit responsive layouts, access control,
-or Danger zone actions.
-
 [See this guide on how to work with custom CSS](/docs/advanced/styling/).
 
 ### Behaviour
@@ -325,20 +174,6 @@ or Danger zone actions.
 
 This will disable the status check for apps.
 
-#### Work directly from the board
-
-Widgets expose their routine controls without requiring edit mode:
-
-- Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the other widgets
-  remain visible but dimmed. Release `Shift` to close it. Focus that widget and press `Shift` + `Enter` to keep the view
-  open until you close it. On touch devices, open it from the widget menu. Other widgets adapt in place instead.
-- When signed in, outside edit mode, and with **Enable right click on widgets** enabled, right-click a widget to inspect
-  its live query status, refresh its data, change quick options, open settings, or run supported actions. App tiles do
-  not use this widget menu, and available controls follow your board and integration permissions.
-
-The widget context menu follows the **Enable right click on widgets** preference in your user settings. On touch devices,
-use the widget menu where your browser exposes it.
-
 ### Access control
 
 With the access control, you can permit a single user or a group to your board.
@@ -384,7 +219,7 @@ This action is irreversible and cannot be undone.
 The deletion of boards is permanent and cannot be undone.
 There are two ways to delete a board:
 
-- Navigate to the settings of your board, open the "Danger zone" section and click on the "delete this board" button.
+- Navigate to the settings of your board, open the "Danger zone" dropdown and click on the "delete this board" button.
 - Navigate to the list of boards in the management pages, click the three dots and click on "delete permanently".
 
 Both actions will execute the same deletion process.
@@ -396,8 +231,7 @@ Duplicating a board will not copy the users and groups that have access to the b
 nor the integrations the user does not have access to.
 :::
 
-Duplicating a board will create a new board with the same settings, all responsive layouts, and independent positions as the original board.
-Duplicating a board that contains Custom Widgets also requires an administrator.
+Duplicating a board will create a new board with the same settings and layout as the original board.
 You can duplicate a board by clicking on the three dots in the list of boards and selecting "Duplicate board".
 
 ![](./img/duplicate-board-modal.png)
@@ -455,13 +289,5 @@ For the global home board you can only select boards that are public.
 
 ### Mobile home board
 
-The mobile home board controls which board opens for devices that Homarr detects as mobile from the User-Agent header.
-This is separate from a board's **Mobile layout**, which controls the layout selected inside that board.
-You can set a mobile home board for yourself in your user preferences, for a user or group through management, or for the
-whole server with **Global mobile board** under `Management` > `Settings` > `Boards`.
-
-For signed-in users, Homarr checks the user's mobile home board, then the user's desktop home board, then the mobile and
-desktop defaults for the lowest-position matching group, followed by the mobile and desktop defaults for the `Everyone`
-group, and finally the server-wide mobile and desktop defaults. Anonymous visitors use the server-wide mobile default and
-then the server-wide desktop default. Server-wide fallback boards must be public. See the
-[global board defaults](/docs/management/settings#boards) for the complete precedence and the required public-board rule.
+Same as the home board, you can also set a mobile home board.
+It will be used for devices that are detected as mobile devices. (Using User-Agent header)

apps/docs/docs/management/custom-widgets/_category_.json

@@ -1,9 +0,0 @@
-{
-  "label": "Custom Widgets",
-  "collapsed": true,
-  "position": 8,
-  "link": {
-    "type": "doc",
-    "id": "management/custom-widgets/index"
-  }
-}

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

@@ -1,169 +1,26 @@
-# Use agents and skills.sh
+---
+sidebar_label: AI and MCP authoring
+---
 
-An external agent creates one widget at a time with the Homarr MCP server. The agent harness manages the list for multiple widgets.
+# AI and MCP authoring
 
-Homarr does not create widget packs or drafts for multiple widgets.
+Homarr exposes an iterative, validation-first workflow to authenticated administrators. Agents should continue until validation, preview, and diagnostics are clean; they must not invent inline network access.
 
-The MCP API key must belong to a Homarr administrator. Non-administrator keys do not list Custom Widget tools, prompts,
-or resources. The same administrator requirement applies to the matching HTTP authoring endpoints.
+## Recommended loop
 
-<a className="button button--primary" href="https://www.skills.sh/homarr-labs/homarr/homarr-custom-widget">
-  View the Custom Widget Skill on skills.sh
-</a>
+1. Read `customWidget_schema` and the generated component/capability reference.
+2. Read an existing definition with `customWidget_byId`, or create a v3 draft.
+3. Call `customWidget_validate`; fix every issue using its exact path.
+4. Call `customWidget_preview` for the base GET and retain the preview session ID.
+5. Test each named query with `customWidget_previewQuery`.
+6. Dry-run every action with `customWidget_simulatePreviewAction`.
+7. Inspect `customWidget_previewJournal` for status, duration, and method coverage.
+8. Revalidate, then call import/create or a focused update/patch operation.
 
-Install the Agent Skill from the verified Homarr repository:
+Stored secret values are never readable. Omitting secrets during an update preserves them. MCP actions are simulation-only; enabling live preview actions remains a browser-only administrator decision.
 
-```sh
-npx skills add https://github.com/homarr-labs/homarr --skill homarr-custom-widget
-```
+## Template format
 
-The portable skill gives concise authoring guidance. For connected agents, Homarr returns the complete `SKILL.md` and
-all bundled skill references once in one lazy tool response. The Homarr MCP prompt then gives the agent a
-retrieval workflow: read the live schema and fetch only the component documentation needed for the widget.
+Use multiline JSX when reading or patching templates. Prefer focused template read/write/patch tools over rewriting an escaped one-line JSON string. When a complete portable artifact is needed, use the authoring bundle placeholder plus a separate fenced JSX block.
 
-The workbench's **Copy AI prompt** action is separate. It creates a self-contained prompt below 12,000 characters for an ordinary ChatGPT or Claude conversation. It includes the lean contract, bindings, recommended components, and two polished examples. It never tells an offline model to call MCP tools.
-
-The source is in [`.agents/skills/homarr-custom-widget`](https://github.com/homarr-labs/homarr/tree/HEAD/.agents/skills/homarr-custom-widget). `HEAD` follows the repository default branch, so the link is not tied to an unreleased feature branch. Homarr does not provide a ZIP archive.
-
-After publication, run the installation command once. This action registers installation activity.
-
-Then, verify the skills.sh page. Request official maker attribution for `homarr-labs` from skills.sh.
-
-Repository code cannot give this attribution.
-
-## Get MCP resources
-
-- Prompt: `homarr-custom-widget-author`
-- Resources: `homarr://custom-widgets/schema`, `components`, `components/{name}`, `examples/{name}`, and `skill`
-- HTTP: `GET /api/custom-widgets/authoring-prompt`, `schema`, `components`, and `skill`
-
-The authoring-prompt tool description contains one sentence. The prompt contains the workflow instructions and resource links.
-
-`GET /api/custom-widgets/skill` and `customWidget_getSkill` return a self-contained structured skill payload:
-
-```ts
-{
-  name: "homarr-custom-widget";
-  version: string;
-  skillMd: string; // Complete SKILL.md
-  references: Record<string, string>;
-  skillsShUrl: string;
-  sourceUrl: string;
-  installCommand: string;
-}
-```
-
-The `homarr://custom-widgets/skill` MCP resource returns the same `SKILL.md` and references once as bundled Markdown.
-
-The component catalog is a compact index of names, categories, safety levels, shared prop names, policies, and example
-IDs. Per-component results contain only component-specific props and a reference to shared prop documentation. Use
-`customWidget_getSharedProps` once with only the shared prop names needed across the selected components. This avoids
-repeating hundreds of global props in every tool result. The catalog is deliberately not embedded in the skill or
-clipboard prompt; the skill response still contains the complete authoring, schema, runtime, and security references.
-
-These interfaces do not return an archive URL or archive hash.
-
-## Create a Custom Widget with MCP
-
-1. Load `customWidget_getSkill`, then get the prompt and live schema.
-2. Call `customWidget_getComponentCatalog`, followed by `customWidget_getComponent` for only the relevant installed
-   components and `customWidget_getExample` when one catalog example matches the interaction pattern. Fetch at most
-   eight component documents before the first validation (or four after a complete example already matches). If shared
-   props are needed, collect their catalog names and call `customWidget_getSharedProps` once for that set.
-3. Read the external API documentation.
-4. Build one definition, using `templateLines` for multiline JSX tool input.
-5. Validate the definition without saving it and repair every reported issue.
-6. Create a preview session.
-7. Run `customWidget_previewQuery` for every query returned by the preview and inspect its actual status and data shape. Assistant conversations retain a bounded response preview so large APIs cannot exhaust the model context. Use
-   `{}` for load queries; manual queries require exactly the returned primitive `parameterNames`.
-8. Test relevant actions in simulation mode.
-9. Open the returned preview path with browser tools.
-10. Inspect the redacted journal and revise the local candidate until validation, data, and rendering all work. Keep the
-    exact tested preview candidate locally. Any definition, template, or source change requires a new validation and preview;
-    earlier query evidence belongs to the previous preview revision.
-11. Create the widget from that final tested preview with `customWidget_createFromPreview`. The preview session already carries
-    the source URLs and encrypted credentials supplied during preview; the create call accepts only its session ID plus an
-    optional target board and persists that tested preview.
-12. Open its returned management path, and use a structured question when the user must choose whether to place it on a board.
-13. Otherwise, ask the user to configure the saved definition with the ten-minute Homarr source-setup URL.
-14. Create a final preview with the saved definition ID so Homarr loads its stored credentials, then test it again.
-15. Update the saved definition if the final verification finds a problem. `customWidget_update` also accepts
-    `templateLines` for multiline JSX without resetting omitted options.
-16. Repeat the procedure for the next widget.
-
-Successful validation returns a compact summary instead of echoing the full widget and template. Preview creation
-returns its session, links, and query checklist without repeating the submitted definition. Keep the candidate locally
-and reuse it for the next lifecycle step.
-
-Each source-configuration URL applies to one definition or preview and one source. It is short-lived, single-use, and
-can only be opened and completed by an authenticated Homarr administrator. The administrator confirms the server URL,
-network scope, and required credential fields directly in Homarr. The agent receives only request status and never
-receives plaintext credentials. Preview-scoped values expire with that preview; definition-scoped values persist.
-
-Agents can install existing widgets without regenerating them:
-
-1. Search with `customWidget_workshopSearch`.
-2. Inspect and validate a result with `customWidget_workshopGet`.
-3. Install it with `customWidget_workshopInstall`.
-4. Configure deployment-specific URLs and supplied credentials with `customWidget_sourceConfigure`.
-5. If the agent does not have those values, call `customWidget_configurationRequestUser` and wait for completion.
-6. Test the installed definition, then use `board_addItem` with kind `customApi` and the returned definition ID.
-
-Homarr encrypts the plaintext immediately. Homarr does not return the plaintext.
-
-## Evaluate the copied prompt
-
-Homarr maintainers can run the same self-contained prompt that the workbench copies through the live generation-quality suite:
-
-```sh
-OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:ai
-```
-
-The manifest suite covers nine complex and public-API prompts. Its deterministic fixture-backed cases include a fake
-homelab health API, CoinMarketCap's keyless public API, Bored, Agify, and a multi-request Pokédex. Before the configured
-model judges a result, the candidate must pass Homarr's real clipboard parser, canonical schema, and deterministic
-checks for documented endpoints, authentication, request triggers, query bindings, response fields, and essential
-runtime components.
-
-To exercise the real Homarr Assistant lifecycle instead of accepting a returned JSON block, run:
-
-```sh
-OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:assistant-ai
-```
-
-The same suites can target the Homarr provider with a Workshop PocketBase token instead of an OpenRouter key:
-
-```sh
-AI_PROVIDER_BASE_URL=https://homarr.dev/api/ai/v1 \
-AI_PROVIDER_API_KEY=<workshop-token> \
-AI_PROVIDER_MODEL=homarr/model \
-pnpm --filter @homarr/custom-widgets test:assistant-ai
-```
-
-`AI_PROVIDER_JUDGE_MODEL` can select a separate judge when the configured endpoint offers one. The Homarr provider
-offers exactly one model, so generation and review both use `homarr/model`.
-
-The assistant test exposes the same lazy skill, live schema, component catalog, targeted component references,
-validation, preview-query, and create-from-preview tools as the product. It refuses to save a definition that was not
-validated exactly or whose preview queries were not all tested. Multi-request fixtures return a different payload for
-each documented path and require manual-query parameters. Use `--case=pokedex`, `--case=coinmarketcap-keyless`,
-`--case=bored-activity`, or `--case=agify-name` for a focused run.
-
-Both suites use the configured provider models for generation and harsh review. They save tool traces, validated
-manifests, raw reviews, and detailed category scores under
-`packages/custom-widgets/.ai-evaluations/`. These live tests are maintainer-invoked rather than CI-required because
-they consume a configured provider account and exercise a nondeterministic model. The repository's ordinary tests
-cover the lifecycle enforcement, fixture routing, score calculation, and failure behavior without network access.
-
-Each scenario stops as soon as it passes and has a hard limit of ten generation attempts. Override the endpoint,
-models, or per-scenario limit with `AI_PROVIDER_BASE_URL`, `AI_PROVIDER_API_KEY`, `AI_PROVIDER_MODEL`,
-`AI_PROVIDER_JUDGE_MODEL`, and
-`CUSTOM_WIDGET_AI_MAX_LOOPS`. Generated artifacts are local and ignored by Git; promote a reviewed, validated result
-into the bundled-widget source deliberately.
-
-The reference API check uses a real PokeAPI list/detail request and a read-only Portainer container query when `PORTAINER_BASE_URL` and `PORTAINER_API_KEY` are set. Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --pokeapi-only` for the public PokeAPI check alone. To exercise start, restart, and stop against a disposable container, also set `PORTAINER_TEST_CONTAINER_ID` and the explicit safeguard `PORTAINER_ALLOW_MUTATIONS=1`; the script restores the container's original running state.
-
-Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --public-ai-apis-only` to verify the live Bored and
-CoinMarketCap response shapes used by the assistant fixtures. The same command also verifies Agify when
-`AGIFY_API_KEY` is configured; otherwise it reports the authenticated check as skipped without weakening the
-deterministic Agify fixture tests.
+The AI prompt is generated from the same registry, examples, request rules, and limits as the validator. Agents should still trust validation output over prompt memory because the installed Homarr version is authoritative.

apps/docs/docs/management/custom-widgets/architecture.mdx

@@ -0,0 +1,29 @@
+---
+sidebar_label: Maintainer architecture
+---
+
+# Maintainer architecture
+
+Reusable Custom Widget behavior belongs to `@homarr/custom-widgets`:
+
+- `core` owns schemas, descriptors, migrations, import/export, examples, diagnostics metadata, and prompt generation.
+- `jsx` owns AST parsing, shared policy, interpreter, bindings, registry, wrappers, and analysis.
+- `runtime` owns renderers and named-request controls through injected ports.
+- `server` owns manifests, network execution, caching, limits, preview sessions, and typed domain errors.
+- `workbench` owns form contracts, editor analysis, preview UI, response tree, and import review through injected ports.
+
+The API package retains persistence and board authorization adapters. Widgets retain board registration and runtime transport wiring. Next.js routes retain navigation and shells. The domain package must never import API, widgets, or route modules.
+
+## Add a display type
+
+Extend the typed descriptor and discriminated schema, defaults/hydration/serialization, renderer, workbench section, preview, import round-trip fixtures, docs, and translations. Create, edit, import, export, MCP, and preview must all use the same transform.
+
+## Add a JSX component
+
+Classify the upstream export, document safety mode and supported props, add a wrapper if behavior needs constraining, and update registry tests. CI fails when a Mantine upgrade introduces an unclassified export.
+
+## Change networking
+
+Implement policy below the framework-neutral server boundary and expose infrastructure through a typed port. Add tests for permissions, typed substitution, DNS classes, redirects, headers, timeouts, limits, redaction, cache behavior, and action non-retry semantics before wiring the tRPC adapter.
+
+Production files target 300 lines. Algorithmic AST/network modules may use a documented 400-line ceiling. Dependency-boundary, cycle, file-size, translation, generated-artifact, component-classification, focused unit, integration, E2E, accessibility, and docs-build gates protect the architecture. After a Next.js production build, `pnpm check:custom-widget-bundle` also enforces a 768 KiB gzip ceiling across the client chunks referenced by Custom JSX.

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

@@ -1,70 +1,36 @@
-# Create a Custom Widget
+---
+sidebar_label: Authoring workbench
+---
 
-import { CanonicalCustomWidgetExample } from "@site/src/components/custom-widget-code";
-import workbenchImage from "./img/workbench.png";
-import workbenchMobileImage from "./img/workbench-mobile.png";
-import workbenchValidationImage from "./img/workbench-validation.png";
+# Authoring workbench
 
-The workbench exposes **General**, **API sources**, **Requests**, **Options**, **JSX**, and **Preview** sections. Advanced JSON is
-available in the manifest and request/option editors. Code and preview sit side by side on desktop; on smaller screens the
-**Configure**/**Preview** switch shows one pane at a time and the section navigation scrolls horizontally. Preview sizes display
-as **S/M/L** (Compact/Standard/Wide), and fixtures are **Live**, **Loading**, **Empty**, or **Error**.
-For multiline JSX, prefer `templateLines` in agent or MCP input and keep the final tested preview as the source of truth before saving.
+The Custom Widget form is a continuous workflow: choose a display, configure the HTTP connection, configure the display, then test it in the adjacent preview. Each section stays visible so you can revisit earlier choices without losing context.
 
-<img
-  src={workbenchImage}
-  alt="Custom Widget workbench with configuration sections and a live preview"
-  style={{ maxWidth: "100%" }}
-/>
+## Choose a display
 
-<img
-  src={workbenchMobileImage}
-  alt="Mobile Custom Widget workbench with Configure and Preview switch and horizontally scrollable section navigation"
-  style={{ maxWidth: "100%" }}
-/>
+The display grid is the first product decision. Built-in displays are best for common metrics, tables, statuses, and actions. Choose Custom JSX when the layout needs multiple Mantine components, conditional presentation, charts, dates, or named requests.
 
-The workbench keeps the configuration and preview together so you can inspect validation diagnostics, the redacted request
-journal, fixture data, and preview size before saving. Invalid fields stay marked in the form while the preview explains why it
-needs attention.
+Changing display type preserves shared connection fields and initializes safe display defaults. A Custom JSX template is never blank; new and migrated forms receive the tested starter fixture.
 
-<img
-  src={workbenchValidationImage}
-  alt="Custom Widget workbench showing a Base URL validation error with Test, preview, and Create actions disabled"
-  style={{ maxWidth: "100%" }}
-/>
+## Test and preview
 
-## Manual workflow
+The preview has four tabs:
 
-1. Configure the default API source, network scope, authentication, and credential.
-2. Add query/action cards. Values can be literals, widget options, or invocation parameters.
-3. Add widget options with their control and default value.
-4. Write responsive JSX using `data`, `status`, `options`, and temporary `inputs`.
-5. Test and preview, inspect Data and the redacted request journal, then save.
+- **Widget** renders at compact, standard, or wide board-like sizes.
+- **Response** uses a tree to inspect data, copy paths, and insert paths into JSX. The external-response action opens a temporary local blob and never publishes the response.
+- **Request** shows the redacted base request, named capabilities, status, duration, and preview journal.
+- **Diagnostics** shows template size, named requests, network scope, and blocking or advisory issues.
 
-<CanonicalCustomWidgetExample
-  id="named-widget-requests"
-  label="Named queries and actions"
-  example="requests"
-  height="420px"
-/>
+Only GET base requests run automatically. Preview actions are simulated until an administrator explicitly enables live actions for the five-minute preview session. DELETE still requires confirmation.
 
-<CanonicalCustomWidgetExample id="widget-options" label="Widget options" example="options" height="360px" />
+## Keyboard and clipboard
 
-Every option has a default. Supported controls include text, textarea, number, switch, select, multi-select, slider, date, time, color, icon, URL, duration, time zone, and JSON. Dynamic choices use `choicesFrom: { request, itemsPath?, valuePath, labelPath }`; the request must be a load query without invocation parameters, and you cannot provide both static `choices` and `choicesFrom`.
+The JSX and JSON editors support native Ctrl/Cmd+Z and redo, plus visible toolbar controls. Cursor position, character count, and the 50,000-character limit remain visible.
 
-Preview actions are simulated by default and recorded in the journal without contacting the service. Enable **Run actions against the configured API** only when you intend a real mutation; live actions still require configured confirmation.
+On the list page, paste a complete v3 export with Ctrl+V or Command+V to import it as new. On an edit page, pasting opens a replacement review. Nothing is applied before the origin, methods, credential inheritance, and permissions are shown.
 
-## ChatGPT or Claude
+For AI output, prefer the authoring bundle format: a JSON block containing `"template": "__HOMARR_TEMPLATE__"`, followed by a JSX block. This keeps multiline JSX readable and avoids JSON escape errors.
 
-Open **Create or fix with any AI**, enter the desired widget and optional API documentation URL, then select the copy action beside the accordion title. The single self-contained prompt is below 12,000 characters, starts with your request, includes the lean contract and two polished examples, and never claims that an offline chat has MCP tools.
+## Save behavior
 
-The model must return one fenced `json` block containing the complete widget, including the JSX in its `template`
-field. Copy that single block and select **Paste**. Homarr fills the visual builders and the JSX editor
-without any placeholder replacement or second paste.
-
-Homarr shows all actionable schema or JSX errors inline. Enter credentials separately. The copied prompt does not include the
-latest preview response; use **Preview** > **Data** to inspect it and mention important response fields in your request. The prompt deliberately
-recommends a focused Mantine component set, visual hierarchy, responsive layout, theme compatibility, and loading,
-empty, failure, and success states.
-
-Connected agents should use the skills.sh skill and retrieve the live schema and individual component metadata only as needed.
+Errors block save; warnings do not. Server validation runs again on every create or update. Leaving with dirty changes triggers protection. Secrets omitted during edit remain unchanged, and secrets are never exported.

apps/docs/docs/management/custom-widgets/component-reference.mdx

@@ -1,13 +0,0 @@
----
-title: Component reference
-sidebar_position: 3
-tags: [Custom Widgets, JSX, Mantine, Components]
----
-
-import { CustomJsxComponentReference } from "@site/src/components/custom-jsx-component-reference";
-
-# Custom JSX component reference
-
-Search the components and properties exposed by Homarr's safe Custom JSX runtime. The live schema and diagnostics remain authoritative: properties marked as blocked cannot be passed from widget code, and denied components are shown only for explanation.
-
-<CustomJsxComponentReference />

apps/docs/docs/management/custom-widgets/custom-jsx.mdx

@@ -1,68 +1,49 @@
-# Use the safe JSX runtime
+---
+sidebar_label: Custom JSX language
+---
 
-Templates are JSX expressions interpreted inside a widget-local safety and render budget. They can read:
+# Custom JSX language
 
-- `data.requestId` — the latest response
-- `status.requestId` — `{ loading, ok, status, statusText, error }`
-- `options.name` — saved widget configuration
-- `inputs.name` — temporary values from declarative `bind`
+Custom JSX is a declarative expression language, not browser JavaScript. Homarr parses an explicit AST subset and emits React elements from a classified component registry. Templates cannot access browser globals, native prototypes, constructors, refs, portals, raw event handlers, or direct `fetch`.
 
-The v2 manifest requires a `default` source and supports up to eight sources, 64 requests, and 64 options. Source IDs are
-case-insensitively unique. Each request allows up to 32 static headers and 32 invalidation targets; a widget can contain
-up to 24 secrets, each up to 8,192 characters, and templates are limited to 50,000 characters. Validation reports the
-exact field when a limit is exceeded.
+## Data and rendering
 
-Authoring input accepts either `template` or `templateLines`, not both. `templateLines` accepts 1–2,000 lines, each up to
-10,000 characters; after joining lines with newlines, the complete template must still fit the 50,000-character limit.
-
-The safe interpreter also bounds JSX evaluation: AST depth 64, 25,000 operations, 4,000 collection items, 10,000 rendered
-nodes, and 200,000 characters in one string or rendered value. API responses are bounded separately before they reach the
-template.
-
-Use normal Mantine layouts, typography, feedback, dates, and charts. Official compound names such as `Card.Section`, `Tabs.List`, and `Radio.Group` are supported. Ordinary safe props pass through; a dangerous capability produces an explicit error.
-Unsafe URLs, callback props, and unapproved style properties are stripped. Response data is deep-sanitized and budgeted
-before it reaches `data`, so treat it as untrusted input even when the source is private.
-
-## Temporary inputs
+The base GET response is available as `data`. Safe member access, conditionals, arrays, object literals, and interpreter-created collection callbacks can compose displays:
 
 ```jsx
-<Stack>
-  <TextInput bind="search" defaultValue="" label="Search" />
-  <SubFetch requestId="search" params={{ query: inputs.search }}>
-    {(results, meta) => (
-      <Stack>
-        {(results ?? []).map((item) => (
-          <Text key={item.id}>{item.name}</Text>
-        ))}
-      </Stack>
-    )}
-  </SubFetch>
+<Stack gap="xs">
+  {data.services
+    .filter((service) => service.visible)
+    .map((service) => (
+      <Group key={service.id} justify="space-between">
+        <Text>{service.name}</Text>
+        <Badge color={service.online ? "green" : "red"}>{service.status}</Badge>
+      </Group>
+    ))}
 </Stack>
 ```
 
-Bound values live only in React memory while the widget is mounted. They are not saved to the database, board options, exports, browser storage, or `localStorage`. Remounting resets them. Components can share a binding when their adapter types agree.
+Properties are resolved own-only. Reflective names such as `constructor`, `prototype`, `__proto__`, `caller`, `callee`, `arguments`, `bind`, `call`, and `apply` are rejected even when computed or Unicode escaped.
 
-## Expression language
+## Components and props
 
-Use expressions, conditionals, optional chaining, arrays, objects, template strings, safe standard helpers, and expression callbacks for `map`, `filter`, `sort`, and trusted runtime slots. Callback blocks, authored `const`, IIFEs, authored recursion, arbitrary functions, imports, hooks, refs, raw events, browser requests, `eval`, and bigint are blocked.
+Every Mantine export is classified as allowed, wrapped, or denied. The [generated component reference](./#component-reference) is authoritative. Props are allowlisted per component; unsupported props produce warnings and are ignored. Polymorphic roots, unsafe URLs, portals, positioning escapes, refs, and function props are stripped.
 
-Bounded regex literals are supported for string matching, splitting, search, and replacement. Regex literals are limited to
-128 characters and flags `gimsu`; lookarounds, backreferences, repeated alternatives/groups, unsupported flags, and more
-than one variable quantifier are rejected.
+`SubData` is a convenience for simple response paths. Prefer the render-child pattern for rich nested results:
 
-## Runtime components
+```jsx
+<SubFetch requestId="detail" params={{ id: data.selectedId }}>
+  {(detail, meta) => (
+    <Stack>
+      <Title>{detail.name}</Title>
+      <Text>HTTP {meta.status}</Text>
+    </Stack>
+  )}
+</SubFetch>
+```
 
-- `SubFetch` runs a named query. Automatic queries run when the widget loads; set `trigger="manual"` to defer one and pass
-  primitive `params` for its invocation references. With `triggerContent`, any content node (commonly a card or image) becomes
-  the accessible click and keyboard trigger instead of showing the default load button.
-- `SubFetch` with `trigger="manual"` keeps its result local to that instance; it does not populate the shared
-  `data.requestId` or `status.requestId` roots. The child callback receives `(result, meta)`, while loading, errors, and
-  retry are handled by `SubFetch`. Provide both `triggerContent` and `triggerAriaLabel` when custom content launches it.
-- `ActionButton` and `ToggleSwitch` run actions only when the widget is mounted outside edit mode. A toggle needs both
-  enabled and disabled request parameters and rolls back its visual state if the action fails.
-- `RefreshButton` renders a compact, accessible icon control that invalidates the client&apos;s load-query cache so active load
-  queries can refetch; it does not execute a request itself. It is disabled when the widget has no active item or preview
-  session, or while the board is in edit mode.
-- `Icon`/`TablerIcon` resolves installed safe icons.
+## Safe helpers and budgets
 
-Always include responsive loading, empty, error, and success states. Runtime failures remain inside the widget tile.
+Bindings include restricted conversion, string, array, object, JSON, math, URI, and pure date helpers. Native `Date` objects and native prototypes are not exposed.
+
+Templates are limited to 50,000 characters, 10,000 rendered nodes, and explicit AST-depth, operation, collection, and string budgets. Budget errors stop only the Custom JSX renderer and are contained by its error boundary.

apps/docs/docs/management/custom-widgets/extension-recipes.mdx

@@ -0,0 +1,66 @@
+---
+sidebar_label: Extension recipes
+---
+
+# Custom Widget extension recipes
+
+These recipes keep every authoring and runtime path on the same typed source of truth. Run `pnpm check:custom-widgets` after each structural change and add focused package tests before changing an adapter.
+
+## Add a built-in display type
+
+1. Add the discriminated configuration schema in `@homarr/custom-widgets/core`.
+2. Add one descriptor with its icon, category, localized metadata keys, defaults, hydration, serialization, and validation.
+3. Add the renderer to the runtime display map. It must consume normalized display data and injected actions only.
+4. Add a bounded workbench section that edits the descriptor-owned form fields.
+5. Add one fixture and assert create, edit, v2/v3 import, export, MCP, and preview round trips against it.
+6. Add translation keys and update the display table in the user guide.
+
+Do not add route-specific conversion code. `buildDisplayFormValues` and `buildDisplayConfigFromFormValues` are the only form conversion boundary.
+
+## Add or update a JSX component
+
+1. Classify the Mantine export as `allowed`, `wrapped`, or `denied` in the component registry. Denied entries require a reason.
+2. Declare supported props and subcomponents. Function props, refs, portals, polymorphic roots, and unsafe positioning stay denied unless a wrapper removes the unsafe behavior.
+3. Implement wrappers in the JSX package and register them through the package runtime-component factory.
+4. Add analyzer and renderer tests for accepted props, stripped props, reflective-property attacks, and the rendered-node budget.
+5. Regenerate the docs reference and verify the editor completion and AI prompt include the same entry.
+
+The component-classification test must pass against the locked Mantine version. Never expose an upstream namespace or native prototype as a shortcut.
+
+## Add a named-request capability
+
+1. Extend the request schema and manifest renderer in `core` and `server` without accepting a raw runtime URL, method, header, or body.
+2. Enforce permission, network scope, redirect, DNS, header, body, response, concurrency, and rate policies in the framework-neutral server service.
+3. Expose infrastructure through a typed server port. Translate domain errors only in the API adapter.
+4. Add the control to runtime through the injected request port. Queries use query semantics; actions require a gesture and use mutation semantics.
+5. Add preview simulation and redacted-journal coverage. Live actions remain an explicit administrator-only browser choice.
+6. Update MCP validation and simulation tools without exposing stored secrets or unrestricted action execution.
+
+Tests must prove actions are never mounted automatically, polled, retried, cached, or redirected. DELETE must retain full permission and confirmation.
+
+## Add a workbench feature
+
+1. Put reusable state, analysis, or presentation in `@homarr/custom-widgets/workbench`.
+2. Receive localized messages and typed callbacks as props. The package cannot import the tRPC client, Next.js navigation, notifications, or Homarr widget adapters.
+3. Keep the Next.js component as a transport and page-shell adapter.
+4. Cover keyboard operation, focus order, reduced motion, 320/768/desktop layouts, dirty-state behavior, and error-boundary recovery.
+5. Keep each production module below 300 lines and preserve the continuous two-pane form behavior.
+
+## Change examples or AI authoring
+
+Examples live as typed shared fixtures. Tests, snippets, documentation data, and the AI prompt consume those fixtures. AI output uses an authoring bundle: a JSON block with `__HOMARR_TEMPLATE__`, followed by a readable multiline JSX block. Do not require agents to escape an entire template into one JSON string.
+
+After changing a fixture, validate every example, render it, regenerate the component reference, and run the prompt snapshot tests. MCP agents must be able to read a widget, patch template lines with a revision, validate, preview named queries, simulate actions, inspect the journal, and update the definition without receiving secret values.
+
+## Required checks
+
+```bash
+pnpm check:custom-widgets
+pnpm test
+pnpm test:e2e
+pnpm turbo typecheck --affected
+pnpm turbo lint --affected
+pnpm turbo build --filter=@homarr/docs
+```
+
+Also run the component-classification, generated-reference drift, bundle-budget, accessibility, and focused package/API suites configured by the repository. A change is incomplete if any create, edit, import, export, MCP, preview, or board-runtime path uses a separate transform.

apps/docs/docs/management/custom-widgets/index.mdx

@@ -1,140 +1,204 @@
 ---
-title: Custom Widgets
-sidebar_label: Overview
-tags: [Custom Widgets, API, JSX, MCP]
+tags:
+  - Custom Widgets
+  - API
+  - Widgets
+  - JSX
 ---
 
-import { BundledCustomWidgetGallery, CustomWidgetCodeExample } from "@site/src/components/custom-widget-code";
-
-export const completeManifest = `{
-  "$schema": "homarr-custom-widget-v2",
-  "name": "Service status",
-  "sources": {
-    "default": { "name": "Service API", "baseUrl": "https://status.example.com", "networkScope": "public", "auth": "none" }
-  },
-  "requests": { "status": { "path": "/api/status" } },
-  "options": {},
-  "template": "<Badge color={data.status?.ok ? 'green' : 'red'}>{data.status?.label ?? 'Unknown'}</Badge>"
-}`;
+import { CustomJsxComponentReference } from "@site/src/components/custom-jsx-component-reference";
 
 # Custom Widgets
 
-:::warning Experimental feature
+Custom widgets connect a dashboard item to an HTTP API without compiling a new Homarr widget. Administrators choose the endpoint and authentication, then use a built-in display type or a Custom JSX template to render the response.
 
-This feature is experimental and will probably change. If you encounter bugs, need more capabilities, or find something confusing, tell us in the [official discussion thread](https://github.com/homarr-labs/homarr/discussions/categories/custom-widgets). Your feedback directly shapes what comes next. Happy hacking!
+## Guides
+
+- [Authoring workbench](./authoring): create, edit, preview, paste, undo, import, and export.
+- [Custom JSX language](./custom-jsx): supported syntax, components, bindings, diagnostics, and limits.
+- [Named requests and security](./requests-and-security): permissions, network scopes, request manifests, and server protections.
+- [AI and MCP authoring](./agent-authoring): an iterative agent workflow that validates and previews before saving.
+- [Compatibility and migration](./migration): v1/v2 JSX and v2/v3 import behavior.
+- [Troubleshooting](./troubleshooting): common editor, preview, permission, and networking failures.
+- [Maintainer architecture](./architecture): package boundaries, extension points, and required tests.
+- [Extension recipes](./extension-recipes): step-by-step changes for displays, JSX components, requests, and workbench features.
+
+:::caution
+
+A custom widget can expose data or perform actions with the credentials configured for it. Import definitions only from sources you trust and review every network capability before using the widget on a shared board.
 
 :::
 
-Custom JSX v2 is Homarr's only Custom Widget format. A definition contains keyed API sources, keyed requests, optional widget options, and one safe JSX template. Credentials are encrypted separately and never exported.
+## Create a widget
 
-```ts
-interface HomarrCustomWidgetV2 {
-  $schema: "homarr-custom-widget-v2";
-  name: string;
-  description?: string;
-  iconUrl?: string;
-  sources: Record<string, CustomWidgetSource>;
-  requests: Record<string, CustomWidgetRequest>;
-  options?: Record<string, CustomWidgetOption>;
-  template: string;
+Open **Management → Custom Widgets**, select **Add**, and configure:
+
+- **Name, description, and icon**: identify the widget in management and the widget picker.
+- **URL**: the full HTTP or HTTPS base endpoint.
+- **Authentication**: none, bearer token, basic authentication, API-key header, or API-key query parameter.
+- **Display type**: a built-in renderer or Custom JSX.
+
+Use **Test** to run the current GET request. The preview workbench separates the rendered widget, sanitized response tree, redacted request journal, and diagnostics. It marks sample data as stale whenever the connection or display configuration changes after a test.
+
+Testing creates a five-minute, administrator-bound preview session for unsaved named queries. Action controls are simulated by default. An administrator can explicitly enable live actions for that session; DELETE still requires confirmation.
+
+## Display types
+
+| Display type     | Use it for                                                |
+| ---------------- | --------------------------------------------------------- |
+| Single Value     | One metric with a label and unit                          |
+| Key Value        | Several labeled values                                    |
+| Table            | Arrays of records                                         |
+| Stat Grid        | Compact colored metrics                                   |
+| Progress Bars    | Capacity, quota, and completion                           |
+| Status Indicator | Health and availability                                   |
+| Count Grid       | Compact counters                                          |
+| Raw              | Sanitized JSON inspection                                 |
+| Action Button    | One explicit API action                                   |
+| Custom JSX       | A declarative Mantine layout with optional named requests |
+
+## Custom JSX workbench
+
+The JSX editor provides syntax highlighting, formatting, undo/redo buttons and Ctrl/Cmd+Z shortcuts, a searchable component reference, character and cursor status, and diagnostics. Errors block saving; warnings identify behavior that still receives server-side validation. Templates can contain up to 50,000 characters and render up to 10,000 nodes.
+
+The template reads the base GET response from `data`:
+
+```jsx
+<Stack gap="xs" p="sm">
+  <Text fw={600}>{data.name}</Text>
+  <Badge color={data.online ? "green" : "red"}>{data.status}</Badge>
+</Stack>
+```
+
+The **Copy AI prompt** action is available on desktop and mobile. Its prompt, component list, and examples are generated from the same metadata used by the renderer, so the reference stays aligned with the installed Homarr version.
+
+### JSX API versions
+
+- **Version 2** is the default. Network access is declared in a named-request manifest and enforced by the server.
+- **Version 1** remains available for display-only templates. Inline network components are disabled until the definition is reviewed and migrated.
+
+Definitions without `jsxApiVersion` are treated as version 1. Display-only templates can be migrated by selecting version 2 and saving an empty request list.
+
+## Named requests
+
+Version 2 templates never choose an arbitrary URL, method, header, or body at runtime. An administrator declares each allowed operation once, and the template references its `requestId` with typed parameters.
+
+```json
+{
+  "type": "customJsx",
+  "jsxApiVersion": 2,
+  "networkScope": "public",
+  "template": "<SubFetch requestId=\"service-detail\" params={{ id: data.id }}><SubData path=\"status\" as=\"Badge\" /></SubFetch>",
+  "requests": [
+    {
+      "id": "service-detail",
+      "kind": "query",
+      "method": "GET",
+      "pathTemplate": "/api/services/{id}",
+      "parameters": { "id": "string" },
+      "auth": "inherit",
+      "minimumBoardPermission": "view",
+      "cacheTtlSeconds": 30
+    }
+  ]
 }
 ```
 
-### Design with AI
+Path placeholders use `{parameter}` and are URL-encoded by the server. JSON body placeholders use `{ "$param": "parameter" }` and preserve the declared string, number, or boolean type.
 
-The **Design with AI** action is available while creating or editing a custom widget. Describe what the widget should show and,
-when [Homarr Assistant](../assistant) is enabled, send the request directly from the form. The generated prompt includes the
-widget schema and current non-secret configuration, but not the latest preview response. It proposes the matching create or
-update tool for your approval.
+`SubData` remains available for simple paths. For richer nested output, pass an interpreter-created render child; it receives the response data and safe status metadata:
 
-Use the preview's **Data** tab to inspect the endpoint's real response shape and mention important fields in your request; the
-copied prompt does not automatically include the latest preview response. Saved secrets are never added to the prompt. **Copy to
-clipboard** remains available when the Assistant is disabled or when you prefer another AI service.
+```jsx
+<SubFetch requestId="service-detail" params={{ id: data.id }}>
+  {(detail, meta) => (
+    <Stack gap="xs">
+      <Badge color={detail.online ? "green" : "red"}>{detail.status}</Badge>
+      <Text size="xs">HTTP {meta.status}</Text>
+    </Stack>
+  )}
+</SubFetch>
+```
 
-<CustomWidgetCodeExample
-  id="complete-widget-manifest"
-  label="Complete manifest"
-  code={completeManifest}
-  height="360px"
-/>
+| Component       | Request kind | Behavior                                                      |
+| --------------- | ------------ | ------------------------------------------------------------- |
+| `SubFetch`      | `query`      | Loads a named GET request automatically or manually           |
+| `ActionButton`  | `action`     | Runs a named POST, PUT, PATCH, or DELETE after a user gesture |
+| `ToggleSwitch`  | `action`     | Passes declared on/off parameters and rolls back on failure   |
+| `RefreshButton` | None         | Refreshes the parent GET response                             |
 
-The browser renders JSX. Homarr's server executes named requests, applies board permissions and network protections, and injects credentials. The browser never receives source credentials.
+Queries require board **view** permission. POST, PUT, and PATCH actions require **modify** by default. DELETE requires **full** permission and confirmation. Allowing viewers to execute a non-DELETE action requires explicit administrator approval. Anonymous viewers cannot execute actions.
 
-## Permissions
+### Network scopes
 
-Custom Widget management is an administrator-only surface. Only a Homarr administrator can create, import, migrate,
-preview, publish, install, configure, or write secrets, including through HTTP authoring resources or MCP. An API key
-only lists Custom Widget MCP tools, prompts, and resources when its owner is an administrator.
+| Scope      | Allowed destinations                                         |
+| ---------- | ------------------------------------------------------------ |
+| `public`   | Public IP addresses only                                     |
+| `private`  | Public addresses plus RFC1918 and IPv6 ULA private addresses |
+| `loopback` | Public, private, and loopback addresses                      |
 
-Adding or configuring a Custom Widget placement requires both administrator access and permission to modify that
-board. Duplicating a board that contains Custom Widgets also requires an administrator. A non-administrator with
-board-modify access can move, resize, change presentation settings, or remove an existing placement, but cannot add one,
-change its definition, refresh interval, or Custom Widget options.
+Link-local, cloud-metadata, unspecified, multicast, documentation, carrier-grade NAT, and IPv4-mapped bypass addresses remain blocked in every scope.
 
-Once an administrator has placed a widget, ordinary board permissions apply to rendering and requests. Authorized
-non-administrators can use it on private boards, and queries can render for anonymous viewers on public boards.
-Mutations remain authenticated and enforce each request's view, modify, or full permission.
+### Example with a named query
 
-## Authoring paths
+The editor and AI prompt include a shared Pokédex fixture that loads details only for the visible page. Its named request is equivalent to:
 
-- [Create a Custom Widget](./authoring) visually or with one copied AI prompt.
-- [Use the JSX runtime](./custom-jsx) for data, Mantine components, temporary inputs, and diagnostics.
-- [Browse the supported component reference](./component-reference).
-- [Configure requests and security](./requests-and-security).
-- [Use MCP and the skills.sh skill](./agent-authoring).
-- [Correct problems](./troubleshooting).
+```json
+{
+  "id": "pokemon-detail",
+  "kind": "query",
+  "method": "GET",
+  "pathTemplate": "/api/v2/pokemon/{name}",
+  "parameters": { "name": "string" },
+  "auth": "none",
+  "minimumBoardPermission": "view",
+  "cacheTtlSeconds": 300
+}
+```
 
-The workbench keeps one continuous layout with visual source, request, and option editors. Advanced raw JSON remains available for experts and AI paste. Invalid values stay inline and disable both preview and Save/Create until they are corrected.
+## Agent authoring through MCP
 
-Exports, imports, the official Workshop client, and MCP validate the same schema. PocketBase stores community
-submissions without interpreting their content, and Homarr validates them before installation. Widgets saved in the v1
-format remain visible to administrators with a **Migration required** badge after upgrading. Use **Copy migration
-prompt**, give the redacted prompt to an LLM, copy its single complete JSON block, then select **Paste migrated widget**
-from that widget's action menu. Homarr reads the `template` value into the JSX editor automatically. The prompt keeps safe
-request metadata but deliberately omits the v1 display configuration because legacy free-text and JSX can contain
-hard-coded credentials. Add a credential-free description of the widget's visible layout and behavior when sending the
-prompt.
+Administrators can use Homarr's MCP server to iterate on custom widgets without bypassing validation or network controls. A typical agent workflow is:
 
-Homarr keeps the original v1 definition and encrypted secret as a compatibility backup even after the validated v2
-replacement is created. The v2 record uses the same stable ID and takes precedence. The archived v1 copy stays hidden
-while the replacement exists; deleting the v2 record surfaces the v1 entry as migration-required again. Automatic
-legacy deletion is intentionally unavailable during v2 stabilization. Credentials are never included in prompts,
-logs, or exports.
+1. Call `customWidget_schema` to inspect the current import format.
+2. Generate a complete `homarr-custom-widget-v3` draft.
+3. Call `customWidget_validate` and correct every returned issue.
+4. Call `customWidget_preview` to test the base GET request through Homarr's hardened executor.
+5. Use `customWidget_previewQuery` for named queries and `customWidget_simulatePreviewAction` to verify action parameters without sending mutations.
+6. Inspect `customWidget_previewJournal`, then validate again.
+7. Call `customWidget_import`, or read an existing widget with `customWidget_byId` and apply a focused `customWidget_update`.
 
-For administrators adding widgets while editing a board, the Custom Widgets section includes **Import from
-Workshop**. Non-administrators do not see the Custom Widget picker or Workshop actions. Selecting **Install widget**
-opens a two-step modal flow: first review the Workshop entry and its complete source in the read-only editor, then
-confirm API sources and credentials. After import, the new definition appears in the picker. Its tile waits for the board
-to be saved before server requests run.
+MCP preview actions are simulation-only. Enabling live preview actions remains an explicit administrator choice in the browser workbench. Stored secret values are never returned by MCP; omit `secrets` when updating an existing widget to preserve them.
 
-## Import and Workshop
+## Component reference
 
-The install flow always links to the corresponding public Workshop entry under the configured Workshop origin. Import confirmation shows origins, authentication modes, network scopes, methods, actions, and permissions. Every source has a suggested URL, but private and loopback sources must be confirmed or replaced for the current Homarr installation. The same screen accepts API keys, tokens, usernames, and passwords; credentials remain optional at install time and missing values stay visible on the Custom Widgets page.
+Custom JSX exposes a classified subset of Mantine Core, Charts, Dates, and Homarr components. Allowed components render directly. Wrapped components receive safe props or read-only behavior. Denied components remain in the registry so dependency upgrades cannot silently expand the template surface.
 
-For example, installing **Tautulli Activity** asks for both the user's Tautulli URL and API key. A stable public source such as PokéAPI keeps its published URL without creating unnecessary setup work.
+<CustomJsxComponentReference />
 
-Workshop publishes technically valid widgets immediately; users can vote or report them, and Workshop moderators can
-delete submissions. Community moderation is separate from Homarr administration and is not a security boundary.
-Publishers should replace personal private-network hosts with a clear service placeholder before publishing. Homarr
-performs definitive validation again at install time.
+This table and the searchable component list in the editor are generated from Homarr's runtime registry.
 
-Connected agents can search, inspect, and install Workshop widgets with `customWidget_workshopSearch`, `customWidget_workshopGet`, and `customWidget_workshopInstall`. After installation they can set a source URL and credentials with `customWidget_sourceConfigure`, or create a secure user-facing setup URL with `customWidget_configurationRequestUser`. Secret values are never returned through MCP.
+Component props are filtered. Polymorphic roots, portals, refs, unsafe positioning, raw event handlers, and `dangerouslySetInnerHTML` are not exposed. Direct browser globals and direct `fetch` calls are unavailable, while ordinary text containing the word “fetch” is valid.
 
-These tools are only exposed to API keys owned by Homarr administrators. Opening and completing a source-configuration
-URL also requires the same authenticated administrator; the URL is short-lived, single-use, and redacted.
+Safe bindings include conversion helpers, a restricted `Math` and `JSON` surface, object and array helpers, URI encoding helpers, and pure date formatting helpers. Collection callbacks and rendered output are subject to interpreter budgets.
 
-## Reliability and rollback
+## HTTP protections and limits
 
-Custom Widget response caches and action invalidation use shared Redis state, so multiple Homarr replicas see the same
-versioned cache generation. Deployments must point every replica at the same Redis service.
+All base, preview, query, and action requests use the same server executor:
 
-Before upgrading, back up the database and `SECRET_ENCRYPTION_KEY`; a v1 binary can still read preserved v1 tables
-during application rollback. Widgets created only in v2 may be unavailable to the rolled-back binary, but do not
-replace the v1 backup.
+- Only HTTP and HTTPS are accepted. URL credentials and fragments are rejected.
+- Named paths must stay on the base endpoint origin.
+- DNS results are validated against the selected network scope and pinned for the request.
+- Queries can follow up to three revalidated same-origin redirects. Actions do not follow redirects.
+- Authorization, cookie, host, forwarding, proxy, content-length, and hop-by-hop headers cannot be supplied by a template.
+- Request bodies are limited to 10 KiB. Decompressed responses are limited to 1 MiB, 32 JSON levels, and 50,000 JSON nodes.
+- GET requests can be cached and deduplicated. Actions are never cached, polled, or retried automatically.
 
-## Bundled examples
+## Import and export
 
-Homarr seeds five disabled examples without credentials and never overwrites an edited seed. They use the same public
-contract. Tautulli Activity is one of the bundled examples preserved from Homarr's AI authoring evaluation:
+New exports use `"$schema": "homarr-custom-widget-v3"`. Version 2 imports remain accepted. Secrets are never exported and must be entered again after import.
 
-<BundledCustomWidgetGallery />
+Review the base origin, network scope, named request methods, inherited authentication, and required permissions before saving an imported widget. A version 1 template that contains inline network components stays disabled until it is converted to named requests.
+
+AI-generated Custom JSX can also be pasted as a Homarr authoring bundle: one fenced JSON block with `"template": "__HOMARR_TEMPLATE__"`, followed by one fenced JSX block containing the readable multiline template. Homarr combines the blocks before validation, avoiding JSON newline and quote escaping. Raw JSON imports remain supported.
+
+On the custom-widget list, paste a complete export with Ctrl+V or Command+V to open the import review and create it as a new definition. On an edit page, the same shortcut opens a replacement review and fills the existing form after confirmation. Pasted definitions never include secrets.

apps/docs/docs/management/custom-widgets/migration.mdx

@@ -0,0 +1,19 @@
+---
+sidebar_label: Compatibility and migration
+---
+
+# Compatibility and migration
+
+Homarr preserves existing display definitions while moving network-enabled Custom JSX to the named-request model.
+
+## JSX API versions
+
+Missing `jsxApiVersion` means v1. Display-only v1 templates can be opened and saved as v2 with an empty request manifest. Inline `url`, `method`, `headers`, and body props are inert in v2.
+
+Static v1 network components can be converted by creating a named request and replacing inline capability props with `requestId` and typed `params`. Dynamic target construction requires an administrator to design an explicit path template and parameter list. Existing non-GET base definitions stop polling and show a network-review state.
+
+## Import versions
+
+Exports use `homarr-custom-widget-v3`; v2 imports remain accepted. Import migration normalizes display configuration, preserves v1 semantics, and never imports secret values. The review screen must be accepted before persistence.
+
+Test migration with the same base response and compare rendered output, query results, action simulation, permissions, and journal entries before enabling the migrated definition on shared boards.

apps/docs/docs/management/custom-widgets/requests-and-security.mdx

@@ -1,67 +1,32 @@
-# Configure requests and security
+---
+sidebar_label: Requests and security
+---
 
-Most widgets use a single source named `default`; the manifest must contain it. Extra keyed sources are available for widgets
-that combine APIs. Source IDs are case-insensitively unique. Base URLs must use HTTP(S), contain no embedded credentials,
-query string, or fragment, and sources can be `public`, `private`, or `loopback`. Authentication is `none`, `bearer`,
-`basic`, an API-key header, or an API-key query parameter. Credentials belong to the widget but remain outside its manifest.
-Source origins are fixed by the definition and source-setup flow; widget options and invocation parameters cannot redirect a
-request to a different origin.
+# Named requests and security
 
-## Named requests
+Custom JSX v2 uses a saved request manifest. Runtime components pass only a `requestId` and declared primitive parameters; they cannot change the URL, method, headers, authentication, or body shape.
 
-Requests are keyed by ID. `source`, `kind`, `method`, `trigger`, `auth`, and `permission` have sensible defaults, so a load query can be as small as:
+## Capability kinds
 
-```json
-{ "status": { "path": "/api/status" } }
-```
+`SubFetch` references a GET `query`. `ActionButton` and `ToggleSwitch` reference a POST, PUT, PATCH, or DELETE `action`. Base data is GET-only. Actions require an explicit gesture and are never polled, cached, retried automatically, or run on mount.
 
-The request `path` is appended to the source `baseUrl`, including a base path such as `/api/v2`.
+Default board permissions are view for queries, modify for POST/PUT/PATCH, and full for DELETE. Viewer actions require explicit high-risk approval; anonymous users cannot execute actions. DELETE always requires confirmation.
 
-GET, POST, PUT, and PATCH work for queries and actions. DELETE is restricted to actions so it can never run while a
-board loads. Kind controls the remaining behavior: load queries run automatically, manual queries run through
-`SubFetch`, and actions run only from `ActionButton` or `ToggleSwitch`.
+## Parameter substitution
 
-Bind values directly where they are used:
+Path placeholders use `{name}` and are URL-encoded by the server. Runtime parameters must exactly match all declared names and types. JSON bodies substitute `{ "$param": "name" }` recursively and preserve string, number, or boolean types.
 
-```json
-{
-  "containers": {
-    "path": "/api/endpoints/{option:endpointId}/docker/containers/json",
-    "query": { "all": { "$option": "showAll" } }
-  },
-  "restart": {
-    "kind": "action",
-    "method": "POST",
-    "path": "/api/endpoints/{option:endpointId}/docker/containers/{param:id}/restart",
-    "invalidates": ["containers"]
-  }
-}
-```
+## Network boundary
 
-`{option:name}` and `$option` read saved widget options. `{param:name}` and `$param` read invocation-time `params`. Load queries cannot use invocation parameters. Homarr infers the exact parameter names and primitive values from these references, rejecting missing or extra invocation params at the request boundary.
+Named paths stay on the base URL origin. HTTP and HTTPS are accepted; URL credentials and fragments are rejected. DNS answers are classified and pinned. Public, private, and loopback scopes progressively allow destinations, but link-local, metadata, unspecified, multicast, documentation, carrier-grade NAT, and IPv4-mapped addresses are always blocked.
 
-Path placeholders and query values must resolve to text, numbers, or booleans. `$option` and `$param` references may appear
-recursively in JSON bodies; invocation parameters remain primitive, and load queries cannot use `$param`. JSON bodies can
-also use structured `json` and `multiSelect` option values, for example `{ "entity_ids": { "$option": "entities" } }`.
+Queries may follow three revalidated same-origin redirects. Actions do not follow redirects. Credentials never cross origins. Reserved authentication, cookie, host, forwarding, proxy, content-length, security, and hop-by-hop headers cannot be declared.
 
-## Protection
+## Limits
 
-Every request uses Homarr's existing server executor: same-origin source enforcement, network scope, DNS and redirect validation, SSRF protection, board permissions, rate and request limits, body and response limits, timeouts, and encrypted credential injection. Static headers cannot override credentials, cookies, routing, proxy, forwarding, or hop-by-hop headers.
+- Request body: 10 KiB UTF-8.
+- Decompressed response: 1 MiB, 32 JSON levels, 50,000 JSON nodes.
+- Per user/item: 60 queries, 10 actions, and 3 deletes per minute.
+- Concurrency: 4 per user/item and 8 per definition.
 
-The executor caps request bodies at 10 KiB and response bodies at 1 MiB. Parsed JSON is limited to depth 32 and 50,000 nodes;
-each network hop has a ten-second timeout, queries follow at most three same-origin redirects, actions do not follow redirects,
-and the total request deadline is 45 seconds.
-
-The limiter allows four concurrent requests per user/item and eight per definition. Per minute, a user/item can make up to 60
-queries, 10 actions, or 3 DELETE actions; a definition can receive up to 240, 40, or 12 of those request categories.
-
-Queries default to view permission and actions to modify. DELETE always requires full permission and confirmation. Actions are never cached, retried, or run on load.
-
-Management and runtime are intentionally separate. A Homarr administrator with board-modify permission places and
-configures the widget. After placement, query and action authorization follows the request's board permission. Public
-boards may execute queries for anonymous viewers, but mutations stay authenticated. This includes shared-cache
-invalidation: `RefreshButton` is disabled only without an active item or preview session, or in edit mode, while ordinary
-scheduled query rendering remains available to anonymous viewers.
-
-Responses use bounded, versioned shared-Redis cache keys. Action invalidation advances the shared version so every
-Homarr replica stops serving the previous response without scanning or deleting a key prefix.
+Successful GETs can use manifest cache TTLs and single-flight deduplication. Logs contain redacted origin/method/error metadata, never secrets, request bodies, or query values.

apps/docs/docs/management/custom-widgets/troubleshooting.mdx

@@ -1,84 +1,33 @@
-# Correct Custom Widget problems
+---
+sidebar_label: Troubleshooting
+---
 
-## Correct an unavailable widget
+# Troubleshooting
 
-The definition does not exist. If it was deleted, remove the unavailable tile from the board.
+## The preview says the template is required
 
-If the Custom Widgets page shows the definition with a **Migration required** badge, an administrator can open its
-action menu and select **Copy migration prompt**. Give that redacted prompt to an LLM, then import the resulting v2 JSON
-from the same menu. The LLM returns one complete JSON block; copy it once and select **Paste migrated widget**. Homarr
-places its `template` value into the JSX editor automatically. Because arbitrary v1 display text or JSX may contain
-credentials, the prompt omits that display configuration; describe the old widget's visible layout and behavior without
-including secrets. Other viewers see **Contact an administrator** instead of a migration link.
+New Custom JSX forms always include the starter fixture. If an imported definition has an empty template, reopen its import review; malformed imports must be corrected rather than previewed as JSX.
 
-Homarr keeps the v1 definition and encrypted secret after migration. The validated v2 replacement uses the same ID and
-takes precedence; the archived v1 record reappears if the v2 replacement is deleted. There is no v1 permanent-delete
-action during the v2 stabilization period.
+## A prop is ignored
 
-Otherwise, install or create a Custom JSX v2 definition.
+The diagnostics name the component and prop. Check the generated component reference. Unsupported props are intentionally removed; use a supported layout primitive or wrapper prop instead of polymorphic, portal, ref, positioning, or raw handler props.
 
-## Correct an invalid saved definition
+## A request does not run
 
-The Custom Widgets page isolates a definition that does not conform to the current schema. The other definitions remain available.
+Confirm that the component kind matches the manifest: `SubFetch` needs a query; action controls need an action. Parameter names and primitive types must match exactly. Base requests and queries require GET. Actions only run from a gesture, and edit mode disables controls.
 
-An invalid definition shows its validation errors. You can delete it.
+## Network scope errors
 
-You cannot edit, enable, export, duplicate, publish, or select an invalid v2 definition. Recreate the definition or import a valid definition. Preserved v1 definitions use the separate **Migration required** workflow described above.
+Resolve the hostname from the Homarr server environment. Select private or loopback scope only when required and understood. Link-local and metadata destinations cannot be enabled by any scope. Redirects must remain on the base origin.
 
-## Correct validation errors
+## Permission errors
 
-Read the first schema or JSX diagnostic. Use its path to find the invalid value.
+The placed board item is the authorization anchor. A definition ID alone cannot authorize credential use. Verify board view/modify/full access, explicit viewer-action approval, and that the caller is not anonymous.
 
-Make sure keyed API source and request names are valid and unique.
+## Stale or failed preview data
 
-Make sure that each named request references an API source. Use explicit `$option` and `$param` references.
+Connection, authentication, body, method, secret, or manifest changes mark samples stale. Run the GET test again. Background query failures keep prior content visible and offer retry; actions roll toggles back and show error feedback.
 
-Make sure every option default matches its control. Use the correct request kind for each runtime component.
+## Import paste is ignored
 
-An incomplete API source URL or icon URL causes a form validation error. The workbench keeps the draft open.
-
-The workbench marks the invalid field while you type. An invalid URL does not replace the form with the error boundary.
-
-An invalid definition disables widget preview and Save/Create. The Data, Options, Actions, and Diagnostics tabs remain available so you can correct it.
-
-The Diagnostics tab shows current schema and JSX errors, accessibility checks, and (after a preview) the redacted request
-journal. It does not expose credentials or raw secret values.
-
-## Workshop unavailable
-
-If Workshop is unavailable, check `WORKSHOP_API_URL` and PocketBase health. Widgets that are already installed continue
-to work.
-
-## Correct request errors
-
-Check the API source network scope. Check the base URL and credentials.
-
-Check the request method, path, body, direct value bindings, and board permission.
-
-For “invalid placeholder,” use `{option:name}` or `{param:name}`. Load queries can only reference options. The preview journal does not show credentials.
-
-The journal shows the method, request ID, path template, status, and duration.
-
-In a multi-instance deployment, all Homarr replicas must share Redis. Versioned cache invalidation is distributed
-through Redis; replicas connected to different Redis databases can serve stale query responses after an action.
-
-## Correct a Mantine prop warning
-
-`UNKNOWN_MANTINE_PROP` is a warning. Homarr passes the prop to Mantine.
-
-Check the prop in the documentation for the installed Mantine version. `BLOCKED_CAPABILITY` identifies an unsafe capability.
-
-Use safe widget options, temporary inputs, or named requests instead.
-
-## Repair an existing item
-
-The widget option definitions changed and the saved values are invalid. Open the item settings.
-
-Correct the marked configuration values. Homarr does not infer widget option migrations.
-
-## Roll back safely
-
-Before an application upgrade, back up the database and preserve the exact `SECRET_ENCRYPTION_KEY`. The v2 schema keeps
-the physical v1 definition and secret tables readable by a v1 binary. Roll back the application without running
-manual cleanup, verify legacy widgets, and restore the database backup if the migration itself must be reversed.
-PocketBase Workshop data is a separate backup and restore operation.
+Paste a complete v2/v3 JSON export or authoring bundle while the list or edit page is focused. Ordinary text and partial JSON are ignored so normal typing is not intercepted.

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

@@ -13,9 +13,9 @@ Check [the available integrations](/docs/category/integrations) for further info
 
 ## Create an integration
 
-To create an integration, choose **New integration** and select the supported application from the searchable grid. The grid groups related services visually and shows which widgets each integration supports.
+To create an integration, you can choose the supported application from the dropdown at the top right:
 
-The integrations management page uses a searchable list. Each row shows the integration type and URL, with the actions you have permission to use.
+![](./img/create-integration-dropdown.png)
 
 Next, you'll need to fill out the required fields to configure the integration:
 
@@ -59,22 +59,6 @@ It is not allowed to create an integration without passing the test.
 This is to ensure that you minimize the amount of broken applications on your Homarr instance.
 The test and create button will perform a network request to the application and authenticate if required.
 
-When you connect a service from a board, Homarr keeps you in the same setup flow. After the connection succeeds, it
-confirms whether an application shortcut was linked and offers the widgets that support the new integration. Selecting a
-widget returns to its settings with the new integration already selected.
-
-Users with full access can also test and update a selected integration directly in the **Edit widget → Edit integration**
-tab on a board. Failed tests keep the editor open and show the same connection diagnostics as the management page.
-Successful changes apply to every app and widget that uses the integration.
-
-When app creation is not permitted, the setup form offers linking an existing accessible app instead of attempting to
-create one.
-
-When the connection unlocks useful widgets that are not on the current board yet, the confirmation also shows up to
-three explainable recommendations. A recommendation is based only on the services you can use and the widget kinds
-already present on that board. You can open the existing widget picker prefiltered to the recommendation, or dismiss
-recommendations for that service on that board.
-
 ## Managing permissions
 
 On the edit page of an integration, you can manage which users / groups can

apps/docs/docs/management/mcp.mdx

@@ -8,24 +8,15 @@ tags:
 
 # Model Context Protocol (MCP)
 
-Homarr exposes a [Model Context Protocol](https://modelcontextprotocol.io) server at `/api/mcp`, enabling AI assistants like Claude, Cursor, VS Code Copilot, and Claude Code to interact with your Homarr instance using natural language.
-
-The endpoint implements the stateless MCP 2026-07-28 protocol and accepts 2025 Streamable HTTP clients through a
-stateless compatibility path. It does not create protocol sessions or require sticky sessions. Homarr creates the
-server and extracts its tools only after an authenticated request reaches the route. The previous `/api/mcp/mcp` URL
-remains available as a compatibility alias, but new clients should always use `/api/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.
 
-The optional [Homarr Assistant](./assistant) uses these same tool definitions internally.
-Unlike external MCP clients, it uses the current Homarr session directly and asks for in-conversation
-approval before running mutating procedures.
-
 ## Getting Started
 
-The MCP endpoint lives under the **API** page at `Management` → `Tools` → `API` → **AI / MCP** tab.
+The MCP endpoint lives under the **API** page at `Management` → `Tools` → `API` → **MCP** tab.
 
-![AI / MCP tab showing the endpoint, API-key warning, and client configuration](./api/img/mcp-instructions.png)
+![MCP Instructions Page](./api/img/mcp-instructions.png)
 
 ### 1. Create an API Key
 
@@ -51,7 +42,7 @@ Add the following to your client's MCP configuration file:
 {
   "mcpServers": {
     "homarr": {
-      "url": "https://your-homarr-instance.com/api/mcp",
+      "url": "https://your-homarr-instance.com/api/mcp/mcp",
       "headers": {
         "ApiKey": "<your-api-key>"
       }
@@ -82,7 +73,7 @@ Replace `<your-api-key>` with your actual API key. Never commit API keys to vers
   "mcpServers": {
     "homarr": {
       "command": "npx",
-      "args": ["-y", "mcp-remote", "https://your-homarr-instance.com/api/mcp", "--header", "ApiKey:<your-api-key>"]
+      "args": ["-y", "mcp-remote", "https://your-homarr-instance.com/api/mcp/mcp", "--header", "ApiKey:<your-api-key>"]
     }
   }
 }
@@ -101,14 +92,6 @@ MCP supports two authentication methods:
 
 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.
 
-Custom Widget and Workshop authoring are different: their tools, prompts, and resources are exposed only when the API
-key owner is a Homarr administrator. Non-administrator keys cannot discover or invoke those capabilities. Creating an
-API key never elevates the owner.
-
-OAuth authorization and token requests bind issued credentials to the canonical `/api/mcp` resource. Dynamic client
-registration remains available for compatibility with current MCP clients while the ecosystem transitions toward
-pre-registered clients and Client ID Metadata Documents.
-
 ## Testing the Connection
 
 Verify your MCP endpoint is working:
@@ -116,17 +99,13 @@ Verify your MCP endpoint is working:
 ```bash
 curl -s -X POST \
   -H "Content-Type: application/json" \
-  -H "Accept: application/json" \
+  -H "Accept: application/json, text/event-stream" \
   -H "ApiKey: <your-api-key>" \
-  -H "Mcp-Method: server/discover" \
-  -H "Mcp-Name: homarr" \
-  -d '{"jsonrpc":"2.0","method":"server/discover","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"test","version":"1.0"},"io.modelcontextprotocol/clientCapabilities":{}}},"id":1}' \
-  https://your-homarr-instance.com/api/mcp
+  -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 supported protocol versions and server capabilities. Use `tools/list` to see all
-available tools. MCP v2 clients add the per-request metadata and `Mcp-Method` / `Mcp-Name` headers automatically; the
-abbreviated request below uses the stateless 2025 compatibility path for readability:
+A successful response includes the server capabilities and available tools. Use `tools/list` to see all available tools:
 
 ```bash
 curl -s -X POST \
@@ -134,36 +113,33 @@ curl -s -X POST \
   -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
+  https://your-homarr-instance.com/api/mcp/mcp
 ```
 
-Tool catalogs are returned in deterministic order and may be cached privately by the client for five minutes. The
-removed HTTP+SSE `/sse` and `/message` transports return `410 Gone`; use the single Streamable HTTP endpoint instead.
-
 ## 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, read settings/CSS, 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        |
-| `customWidget`     | Validate, preview, create, and iteratively update widgets  | GET + POST |
-| `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 |
+| 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        |
+| `customWidget`     | Validate, preview, create, and iteratively update widgets | GET + POST |
+| `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.
 
@@ -186,94 +162,58 @@ The tools table on the MCP tab is dynamically generated - it always reflects the
 - **"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
-- **"Build a Custom Widget for this API"** - AI validates and previews one definition before it saves the definition
+- **"Build and refine a custom widget for this API"** - AI validates the draft, tests GET data and named queries, simulates actions, and creates or updates the widget
 
-## Create a Custom Widget with an AI agent
+## Custom Widget Workflow for AI Agents
 
-An agent creates one `homarr-custom-widget-v2` definition at a time. Start with the native prompt `homarr-custom-widget-author`.
+AI agents can create and iterate on custom widgets using these tools in sequence.
 
-The API key owner must be a Homarr administrator. The same rule applies to management, import, migration, preview,
-secrets, publication, Workshop installation, and the HTTP authoring resources.
+:::tip Editing an existing widget?
+Skip to step 5. Use `customWidget_byId` to fetch it and `customWidget_readTemplate` / `customWidget_writeTemplate` to edit its template directly.
+:::
 
-Load the installed skill before authoring. `customWidget_getSkill` returns the complete `SKILL.md` entrypoint and every
-bundled reference in one response, so an MCP client does not need filesystem access or a second documentation fetch.
-Then read the live schema and only the component resources required by the design. These resources describe the
-installed Mantine components.
+### 1. Get the schema
 
-1. Call `customWidget_getSkill`, `customWidget_getAuthoringPrompt`, `customWidget_schema`, and
-   `customWidget_getComponentCatalog`.
-2. Fetch only the relevant installed component documentation with `customWidget_getComponent` and, when useful,
-   one interaction example with `customWidget_getExample`. Component results contain component-specific props; collect
-   any needed shared prop names from the compact catalog and fetch them together once with `customWidget_getSharedProps`.
-3. Build one Custom Widget definition. Use `templateLines` for generated multiline JSX to avoid a fragile JSON-escaped
-   template string.
-4. Call `customWidget_validate` without saving the definition and repair every returned issue path.
-5. Call `customWidget_previewCreate`.
-6. Call `customWidget_previewQuery` for every entry in the returned `queries` list. Supply the listed invocation
-   parameters for manual queries and inspect the real HTTP status and response shape before binding template fields.
-7. Test relevant actions with `customWidget_previewAction` in simulation mode.
-8. Open the returned `previewPath` or `previewUrl`.
-9. Examine `customWidget_previewJournal`.
-10. Revise the local candidate and create another preview session until validation, query data, actions, and rendering
-    are ready.
-11. Call `customWidget_create`, supplying any credentials and deployment-specific source URLs the user already provided.
-12. Open the returned `managementPath` to review the exact saved definition.
-13. If the user must enter the source URL or credentials, call `customWidget_configurationRequestUser` with the new definition ID and wait for completion.
-14. Create a final preview with that definition ID so Homarr loads its stored credentials, then test it again.
-15. Use `customWidget_update` or `customWidget_templatePatch` for any final saved-definition corrections.
-16. Repeat this procedure for the next Custom Widget.
+Call `customWidget_schema` to receive the JSON Schema for the `homarr-custom-widget-v3` format. This tells the agent what fields are required and their types.
 
-Validation and preview creation return compact lifecycle metadata. They do not echo the submitted widget or duplicate
-its template as both a string and line array; the agent should retain and reuse its local candidate.
+### 2. Draft and validate
 
-The agent receives the configuration-request status. The agent does not receive plaintext credentials. A preview-scoped setup URL configures only that temporary preview; use a definition-scoped URL when the values must persist.
+Build a widget JSON object and call `customWidget_validate` with it. The tool returns structured issues (path + message) so the agent can fix and re-validate until the draft is clean.
 
-Discovery resources:
+### 3. Create the widget
 
-- `homarr://custom-widgets/schema`
-- `homarr://custom-widgets/components`
-- `homarr://custom-widgets/components/{name}`
-- `homarr://custom-widgets/examples/{name}`
-- `homarr://custom-widgets/skill`
+Call `customWidget_import` with the validated `homarr-custom-widget-v3` draft. This returns the new widget `id`. Use `customWidget_create` only when you intentionally need its lower-level creation input, including secret fields.
 
-An authenticated administrator can use the matching `/api/custom-widgets/authoring-prompt`, `/schema`, `/components`,
-and `/skill` endpoints instead of MCP resource URIs. These endpoints are not public schema downloads.
+### 4. Test with real data
 
-The Custom Widget tools are:
+Call `customWidget_preview` with the widget's connection info. This makes a real GET request through Homarr's hardened executor and returns the sanitized response plus a preview session ID.
 
-- `customWidget_schema`
-- `customWidget_validate`
-- `customWidget_list`
-- `customWidget_get`
-- `customWidget_create`
-- `customWidget_update`
-- `customWidget_delete`
-- `customWidget_templatePatch`
-- `customWidget_previewCreate`
-- `customWidget_previewQuery`
-- `customWidget_previewAction`
-- `customWidget_previewJournal`
-- `customWidget_secretSet`
-- `customWidget_sourceConfigure`
-- `customWidget_configurationRequestUser`
-- `customWidget_workshopSearch`
-- `customWidget_workshopGet`
-- `customWidget_workshopInstall`
-- `customWidget_getAuthoringPrompt`
-- `customWidget_getComponentCatalog`
-- `customWidget_getComponent`
-- `customWidget_getSharedProps`
-- `customWidget_getExample`
-- `customWidget_getSkill`
+For Custom JSX v2 widgets with named requests, use `customWidget_previewQuery` to test each named GET query, and `customWidget_simulatePreviewAction` to dry-run actions without network calls.
 
-Custom Widget permissions are not assignable group capabilities. Administrator status is required for the complete
-authoring surface. A source-configuration URL is short-lived and single-use, requires the same logged-in administrator
-to open and complete it, and never returns plaintext credentials to the agent.
+### 5. Iterate on the template
 
-Adding a `customApi` item through `board_addItem`, changing its definition or options, and duplicating a board that
-contains one also require an administrator with board-modify access. Existing placements continue to render and run
-authorized requests according to normal board permissions.
+Use `customWidget_readTemplate` to get the current JSX template as plain text, then `customWidget_writeTemplate` to push updates. The write tool accepts either:
 
-Homarr applies its request security controls during request execution. These controls include SSRF, DNS, redirect, size, timeout, rate, and permission controls.
+- `template` — a single string (newlines as `\n`)
+- `templateLines` — an array of strings (joined with newlines server-side, avoids `\n` escaping)
 
-Read [Use agents and skills.sh](./custom-widgets/agent-authoring) for the complete procedure and the portable Agent Skill.
+Both options validate the template AST before saving. This avoids re-sending the full widget JSON for template-only edits.
+
+For small changes, prefer `customWidget_patchTemplate`. Pass the `revision` returned by `customWidget_readTemplate` and one or more line edits. Homarr rejects stale revisions, applies all edits atomically, and validates the complete template against its named request manifest before saving.
+
+### 6. Update non-template fields
+
+Call `customWidget_byId` to get the full widget, modify fields, and call `customWidget_update` with only the changed fields.
+
+### Available components in templates
+
+Custom JSX templates support 100+ Mantine components plus:
+
+- `<TablerIcon name="server" size={20} color="blue" />` — 100+ curated Tabler icons by kebab-case name (e.g. `"player-play"`, `"alert-triangle"`)
+- `<SubFetch>` / `<ActionButton>` / `<ToggleSwitch>` — network-capable components for named requests
+- Array methods: `map`, `filter`, `find`, `findIndex`, `some`, `every`, `reduce`, `sort`, `slice`, `flat`, `reverse`, `at`, `pop`, `join`, `includes`, `indexOf` (note: `pop` returns last element without mutating)
+- String methods: `toUpperCase`, `toLowerCase`, `trim`, `trimStart`, `trimEnd`, `slice`, `substring`, `includes`, `startsWith`, `endsWith`, `split`, `replace`, `replaceAll`, `repeat`, `padStart`, `padEnd`, `charAt`, `indexOf`, `lastIndexOf`
+
+:::note
+All `customWidget_*` tools require admin-level API key permissions. The preview executor enforces rate limits (60 queries/min, 10 actions/min).
+:::

apps/docs/docs/management/search-engines/index.mdx

@@ -8,7 +8,8 @@ tags:
 # Search Engines
 
 Using the search engines, terms can be quickly searched simply by opening the search bar at the top or using the keyboard shortcut `CTRL + K`.
-The management page provides a searchable list with the shortcut, URL template, source, and available row actions for each engine.
+
+![](./img/search-engines.png)
 
 You can add any search engine that has a search URL that accepts a search term as a parameter.
 

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

@@ -10,126 +10,109 @@ tags:
 
 # Settings
 
-The settings page applies options to the whole Homarr application.
-Some changes need a full page reload before they take effect.
-
-All changes are collected in a single form. Click the **Save changes** button in the save bar at the bottom of the page to apply them. The save bar only appears when you have unsaved changes, and the **Discard** button reverts your changes.
+The settings page has a few options that will be applied to the entire Homarr application.
+They may require a full page reload for changes to apply.
 
 ## Analytics
 
-Homarr uses [PostHog](https://posthog.com/) to collect anonymous usage data.
-We collect this data to see what features people ACTUALLY use.
-We use this data to decide where we spend our development time.
+By default, Homarr is collecting anonymous analytics to identify issues and prioritize bugfixes and improvements.
+The data is never shared with any third-parties and is fully GDPR & CCPA compliant.
+The software being used is [Umami Analytics](https://umami.is/) which is fully open source.
+The main server software can be found [here](https://github.com/umami-software/umami) and [this node library](https://github.com/umami-software/node) to perform server side calls to the API.
 
-We do not sell the data. We do not share the data with third parties.
-The data does not contain personal information and does not identify you or your installation.
+A full list of the collected data by default can be found here: https://umami.is/docs/metric-definitions.
 
-Homarr sends the data to our own PostHog server at `https://hog.homarr.dev`.
-The server sends the data once a week and when the server starts.
+We understand that you might not want Homarr to communicate with our services.
+By unchecking the `Send anonymous analytics` checkbox and reloading the full page, all communication by Umami will be disabled and no data will be collected.
+If you are paranoid, you can permanently block `umami.homarr.dev` from your DNS / firewall.
 
-### What we collect
+Additionally, you opt in to more data collection to help us provide more useful data.
 
-Homarr collects technical data about your installation:
+### Integration data
 
-- Your Homarr version
-- Your database type (SQLite, MySQL, or PostgreSQL)
-- Whether Docker or Kubernetes is enabled
-- Your enabled authentication providers
-- Your operating system and CPU architecture
-- Your default language
-- The number of boards, apps, sections, layouts, users, groups, search engines, icon repositories, cron jobs, API keys, invites, sessions, and accounts
-- The integration types you use and how many you have of each (for example, Sonarr or SABnzbd)
-- The widget types you use and how many you have of each
+Enabling this optional data will send the types of integrations (e.g. SABnzbd, Sonarr, ...) and how many you have configured of them.
+This will not include any URLs, names, secrets, errors and others. This is disabled by default.
 
-Homarr does NOT collect:
+### Widget data
 
-- URLs
-- Names
-- Usernames, emails, or passwords
-- Integration secrets or API keys
-- Error messages or logs
-- Any data that can identify you
+Enabling this optional data will send the types of widgets (e.g. downloads, media streams, iframe, ...) and how many you have configured of them.
+This will not include any URLs, names, secrets, errors and others. This is disabled by default.
 
-Each installation gets a random ID. We use this ID only to count unique installations. We cannot use this ID to identify you.
+### Users data
 
-Homarr does not use cookies for analytics. Homarr does not track page views automatically. Homarr only sends the data listed above.
-
-### Disable analytics
-
-Analytics are enabled by default. To disable analytics:
-
-1. Open the Settings page.
-2. Uncheck the "Help us improve Homarr" checkbox.
-3. Reload the full page.
-
-When analytics are disabled, Homarr does not send any data to PostHog.
-
-You can also set the `NO_EXTERNAL_CONNECTION` environment variable to `true`. This stops all external requests, including analytics. See the [environment variables](/docs/advanced/environment-variables) page for more information.
-
-You can block `hog.homarr.dev` in your DNS or firewall. Homarr cannot send data when this address is blocked.
+Enabling this optional data will send the count of users and whether you activated SSO.
+This will not include any usernames, passwords, emails, URLs, authentication flows or client IDs.
+This is disabled by default.
 
 ## Search Engine Optimization (SEO)
 
-Search engines use web crawlers to index websites. This can cause unwanted traffic to your dashboard.
-Homarr asks crawlers to not index your instance by default. Use these settings to change this request.
-
-Homarr cannot control what the crawlers do. A crawler can ignore the request. Your website can still appear in an index.
+Big companies [like Google, Microsoft, Baidu and Yandex](https://de.wikipedia.org/wiki/Web-Index) will use [web crawlers](https://de.wikipedia.org/wiki/Webcrawler) to index the Internet for new websites & pages.
+This is desirable in many cases (for example when selling products in an online shop) but can lead to unwanted traffic and attention to your personal dashboard.
+Homarr is requesting the crawlers to not index Homarr instances by default for this reason.
+If you use Homarr as a public website and want it to be searchable on these search engines, you can disable these settings.
+Please note that Homarr doesn't have control over what the crawlers do; it is a mere request to them to not perform these actions but will not guarantee that your website doesn't land on some index.
 
 ### No index
 
-This setting asks crawlers to not index your instance.
-This setting is enabled by default. Disable this setting to allow indexing.
+This will ask crawlers to not index your Homarr instance on any indexes.
+It is up to the crawler to properly respect this request.
+By default, this setting is enabled. Disabling it will allow indexing.
 
 ### No follow
 
-Crawlers follow links to discover new pages.
-This setting asks crawlers to not follow links. This setting is enabled by default.
-Crawler behavior can differ between search engines.
+If indexing is allowed, crawlers will also attempt to follow any links on your page to further "discover" new parts of the Internet and on your website.
+By default, this setting is enabled and will ask crawlers to not follow any links.
+Crawler of different companies may behave differently when indexing is prohibited and following is allowed.
 
 ### No translate
 
-Some browsers offer to translate pages.
-This setting asks crawlers to not offer translation. Some browsers ignore this setting.
+Google and Chrome on Android will prompt users to translate pages that are not in their device language.
+This can lead to some shifting and can be undesired in some cases. By enabling this,
+you ask crawlers to never translate and never prompt users for translation.
+It should be noted that some browsers will ignore this and translate regardless.
 
 ### No site links search box
 
-This setting applies to Google only.
-Google can show a search box below your domain.
-This setting asks Google to not show this box. This setting is disabled by default.
+This setting is exclusive to Google.
+[Google will create a box below your domain](https://developers.google.com/search/docs/appearance/structured-data/sitelinks-searchbox) that lists the paths that were discovered by the "folowing".
+The user can search them directly in Google.
+You can ask the crawlers to not allow searches by enabling this setting.
+This setting is disabled by default.
 
 ## Boards
 
 ### Global home board
 
-You can set a global home board.
-This board is the fallback for users without their own home board. It is also the fallback for anonymous users.
-The board must be public.
+You can 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.
+Note that the board must be public to be used as a global home board.
 
 ### Global mobile board
 
-You can set a global mobile board.
-Homarr shows this board on mobile devices instead of the global home board.
-Homarr detects mobile devices with the User-Agent header.
-The board must be public.
+You can set a global mobile board. It will be shown instead of the global home board on mobile devices that can be detected by Homarr. (Using the User-Agent header).
+It will similar to the global home board be as fallback for normal users and for any anonymous users.
+It also has to be public.
 
 ### App status
 
 #### Enable status by default
 
-You can decide if app status is enabled when you add a new app.
+You can decide if the app status should be enabled by default when adding a new app to the board.
 
 #### Force disable status
 
-You can decide if app status is disabled on all boards.
+You can decide if the app status should be disabled for all boards.
+
+###
 
 ## Appearance
 
 ### Default color scheme
 
-You can set the default color scheme for users without their own color scheme.
+You can set the default color scheme for all users that have not set a color scheme themselves.
 
 ## Culture
 
 ### Default language
 
-You can set the default language for users without their own language.
+You can set the default language for all users that have not set a language themselves.

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

@@ -177,11 +177,6 @@ Currently, the following permissions are available:
   - **Full integration access**: Allow members to manage, use and interact with any integration
 - **Administrator**: Members with this permission have full access to all features and settings
 
-Custom Widget authoring, import, migration, preview, secrets, Workshop access, and placement configuration are reserved
-for administrators and are not separate assignable group permissions. Board modifiers can still move, resize, change
-presentation settings, or remove an existing Custom Widget placement, and board viewers can use placed widgets as
-allowed by each request.
-
 When you changed permissions, you must confirm your changes by clicking the banner at the bottom:
 
 ![](./img/changing-group-permissions.png)
@@ -220,8 +215,7 @@ Clicking the `Copy & close` button will copy the URL to your clipboard.
 
 ### Self-onboarding
 
-Clicking the invitation link opens a centered registration form that uses the same visual shell as Homarr's onboarding
-and sign-in pages, with fields for the username and password:
+Clicking the invitation link will bring up a form with fields for the username and password:
 
 ![](./img/invitation-self-onboarding.png)
 

apps/docs/docs/widgets/anchor-note/index.mdx

@@ -4,8 +4,6 @@ description: "Display and edit a selected note from Anchor"
 hide_title: true
 ---
 
-import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
-
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -17,8 +15,6 @@ import { anchorIntegration } from "@site/docs/integrations/anchor";
 
 The Anchor Note widget shows a selected note from your Anchor integration. If your note permissions allow it, you can also edit the note title and content directly in Homarr.
 
-Advanced view always shows the note title and update time alongside the complete formatted document, permission, creation date, and pinned or archived state. Compact title and update-time switches do not hide that information in advanced view.
-
 ### Screenshots
 
 import anchorNoteWidgetScreenshot from "./img/widget.png";
@@ -37,12 +33,10 @@ import anchorNoteWidgetScreenshot from "./img/widget.png";
 
 ### Interactions
 
-- Hover the widget, focus within it, or use a touch device to reveal **Edit**, then select it to start editing the note.
+- Click **Edit** to start editing the selected note.
 - Click **Save** to persist changes to Anchor.
 - Click **Cancel** to discard unsaved changes.
 
-<WidgetInteractionGuide />
-
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/app/index.mdx

@@ -25,12 +25,6 @@ import piHoleApp from "./img/pi-hole-ping-icon.png";
   <img src={piHoleApp} alt="app pi-hole with-status-check status-check-icon" width={128 * 1.5} height={128 * 1.5} />
   <img src={jellyseerrApp} alt="app jellyseerr with-description-tooltip" height={128 * 1.5} />
 </div>
-
-### Interactions
-
-App tiles stay compact and open their configured destination directly. They do not use the shared widget context menu;
-configure the app and its status check from the tile's edit actions.
-
 ### Adding the widget
 
 <AddingWidget />