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/datatable-migration/SKILL.md

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

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

@@ -1,44 +0,0 @@
----
-name: documentation-sync
-description: Keep Homarr documentation in sync with code changes. Use when modifying code that affects user-facing behavior, or when adding/modifying widgets, integrations, cron jobs, API routes, env vars, permissions, auth providers, or UI in apps/docs. Covers the docs/ mapping table, integration doc pattern, and widget doc pattern.
----
-
-# Documentation Sync
-
-When modifying code that affects user-facing behavior, you MUST also update the documentation in `apps/docs/`.
-
-## What triggers a doc update
-
-| Code change            | Doc location                                                |
-| ---------------------- | ----------------------------------------------------------- |
-| New integration        | `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts` |
-| New widget             | `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`      |
-| Changed API surface    | `apps/docs/docs/management/api.mdx`                         |
-| New/changed env vars   | `apps/docs/docs/advanced/`                                  |
-| New CLI commands       | `apps/docs/docs/advanced/command-line/`                     |
-| Changed auth providers | `apps/docs/docs/advanced/` SSO pages                        |
-| UI/UX changes          | Relevant getting-started or management pages                |
-| New cron job           | `apps/docs/docs/management/tasks.mdx`                       |
-| Changed permissions    | `apps/docs/docs/management/users.mdx`                       |
-
-## Integration doc pattern
-
-Each integration has a folder under `apps/docs/docs/integrations/<slug>/`:
-
-- `index.ts` — exports a typed `IntegrationDefinition` with name, description, iconUrl, path
-- `index.mdx` — uses shared components: `IntegrationHeader`, `IntegrationCapabilites`, `IntegrationSecrets`
-- Import metadata from `@homarr/definitions` where possible
-
-## Widget doc pattern
-
-Each widget has a folder under `apps/docs/docs/widgets/<slug>/`:
-
-- `index.ts` — exports a typed `WidgetDefinition` with icon, name, description, path, configuration
-- `index.mdx` — uses shared components: `WidgetHeader`, `WidgetConfig`, `WidgetAdding`
-
-## Development
-
-- Run docs locally: `pnpm dev:docs` from root
-- Build docs: `pnpm turbo build --filter=@homarr/docs`
-- The docs app can import from `@homarr/definitions` for type-safe integration/widget metadata
-- Docusaurus strict mode throws on broken links — fix any broken references before committing

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

@@ -1,28 +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.
-
-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.
-
-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.
-
-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.

.claude/skills

@@ -1 +0,0 @@
-../.agents/skills

.cursor/rules/codebase-context.mdc

@@ -1,6 +1,6 @@
 ---
-name: codebase-context
-description: Comprehensive Homarr codebase architecture and conventions reference. Use when orienting in the monorepo, understanding package dependency layers, the three runtime services and ports, tRPC router structure, multi-database support, widget/integration/cron system architecture, routing, auth providers, env vars, or key patterns before writing code.
+description: Comprehensive Homarr codebase architecture and conventions reference
+alwaysApply: true
 ---
 
 # Homarr Codebase Context
@@ -27,7 +27,7 @@ Homarr is an open-source, self-hosted dashboard for managing homelab services. I
 
 ## Repository Structure
 
-```text
+```
 homarr/
 ├── apps/
 │   ├── nextjs/          # Main Next.js application (port 3000)
@@ -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
@@ -77,11 +79,11 @@ homarr/
 
 ## Three Runtime Services
 
-| Service   | Port | Role                                         |
-| --------- | ---- | -------------------------------------------- |
-| Next.js   | 3000 | Main web app (SSR + API routes)              |
-| WebSocket | 3001 | tRPC subscriptions via `ws`                  |
-| Tasks     | 3002 | Cron job runner + management API via Fastify |
+| Service | Port | Role |
+|---------|------|------|
+| Next.js | 3000 | Main web app (SSR + API routes) |
+| WebSocket | 3001 | tRPC subscriptions via `ws` |
+| Tasks | 3002 | Cron job runner + management API via Fastify |
 
 In Docker, nginx listens on **7575** and proxies to all three. The tasks service authenticates via `CRON_JOB_API_KEY` header.
 
@@ -110,7 +112,6 @@ In Docker, nginx listens on **7575** and proxies to all three. The tasks service
 ### Multi-Database Support
 
 Drizzle schemas exist in three parallel implementations:
-
 - `packages/db/schema/sqlite.ts`
 - `packages/db/schema/mysql.ts`
 - `packages/db/schema/postgresql.ts`
@@ -120,7 +121,6 @@ Selected at runtime via `DB_DRIVER` env (`better-sqlite3` | `mysql2` | `node-pos
 ### Widget System
 
 Widgets are registered in `packages/widgets/src/index.tsx` as `widgetImports` (must satisfy `Record<WidgetKind, ...>`). Each widget:
-
 - Has a `definition` created via `createWidgetDefinition(kind, { icon, createOptions, supportedIntegrations? })`
 - Uses `optionsBuilder.from(factory => ({ ... }))` for typed options
 - Loads dynamically via `next/dynamic`
@@ -133,7 +133,6 @@ Integrations are defined in `packages/definitions/src/integration.ts` (`integrat
 ### Cron Job System
 
 Jobs defined in `packages/cron-jobs/src/jobs/`. Each job:
-
 - Uses `createCronJob` with a cron expression
 - Publishes results to Redis channels
 - Widget subscriptions consume those channels via tRPC subscriptions
@@ -161,7 +160,6 @@ Configured via `AUTH_PROVIDERS` env. Supports: `credentials` (local), `ldap`, `o
 ## Environment Variables
 
 Key env vars (from `.env.example`):
-
 - `DB_DRIVER`: `better-sqlite3` | `mysql2` | `node-postgres`
 - `DB_URL`: Database connection string
 - `AUTH_SECRET`: NextAuth secret
@@ -193,3 +191,16 @@ Key env vars (from `.env.example`):
 - Drag-and-drop via `@dnd-kit/*`
 - `typescript.ignoreBuildErrors: true` in next.config (types checked separately via `typecheck`)
 - `serverExternalPackages`: `dockerode`, `isomorphic-dompurify`, `jsdom`
+
+## Documentation (`apps/docs`)
+
+Docusaurus 3 site at `apps/docs/`, package name `@homarr/docs`.
+
+- Run with `pnpm dev:docs` from root
+- Build with `pnpm turbo build --filter=@homarr/docs`
+- Uses Tailwind CSS 3 for custom pages (not Mantine)
+- Imports `@homarr/definitions` for type-safe integration/widget metadata
+- When adding or modifying widgets, integrations, cron jobs, API routes, env vars, or user-facing features, you MUST also update corresponding docs in `apps/docs/docs/`
+- Integration docs: `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts`
+- Widget docs: `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`
+- Strict link checking: broken links/anchors cause build failure

.cursor/rules/documentation-sync.mdc

@@ -0,0 +1,50 @@
+---
+description: Keep documentation in sync with code changes
+globs:
+  - packages/definitions/src/**
+  - packages/widgets/src/**
+  - packages/integrations/src/**
+  - packages/api/src/**
+  - apps/nextjs/src/**
+  - apps/docs/**
+---
+
+# Documentation Sync Rule
+
+When modifying code that affects user-facing behavior, you MUST also update the documentation in `apps/docs/`.
+
+## What triggers a doc update
+
+| Code change | Doc location |
+|---|---|
+| New integration | `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts` |
+| New widget | `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts` |
+| Changed API surface | `apps/docs/docs/management/api.mdx` |
+| New/changed env vars | `apps/docs/docs/advanced/` |
+| New CLI commands | `apps/docs/docs/advanced/command-line/` |
+| Changed auth providers | `apps/docs/docs/advanced/` SSO pages |
+| UI/UX changes | Relevant getting-started or management pages |
+| New cron job | `apps/docs/docs/management/tasks.mdx` |
+| Changed permissions | `apps/docs/docs/management/users.mdx` |
+
+## Integration doc pattern
+
+Each integration has a folder under `apps/docs/docs/integrations/<slug>/`:
+
+- `index.ts` — exports a typed `IntegrationDefinition` with name, description, iconUrl, path
+- `index.mdx` — uses shared components: `IntegrationHeader`, `IntegrationCapabilites`, `IntegrationSecrets`
+- Import metadata from `@homarr/definitions` where possible
+
+## Widget doc pattern
+
+Each widget has a folder under `apps/docs/docs/widgets/<slug>/`:
+
+- `index.ts` — exports a typed `WidgetDefinition` with icon, name, description, path, configuration
+- `index.mdx` — uses shared components: `WidgetHeader`, `WidgetConfig`, `WidgetAdding`
+
+## Development
+
+- Run docs locally: `pnpm dev:docs` from root
+- Build docs: `pnpm turbo build --filter=@homarr/docs`
+- The docs app can import from `@homarr/definitions` for type-safe integration/widget metadata
+- Docusaurus strict mode throws on broken links — fix any broken references before committing

.cursor/rules/mcp-integration.mdc

@@ -1,14 +1,13 @@
 ---
-name: mcp-integration
-description: Expose tRPC procedures as MCP tools for AI clients. Use when modifying procedures in packages/api/src/router, adding a new tRPC procedure or router, or deciding what to expose via Homarr's MCP interface. Covers .meta({ mcp }), router registration in packages/api/src/mcp.ts, input schema rules, and what to expose vs skip.
+description: How to expose tRPC procedures as MCP tools for AI clients
+globs: packages/api/src/router/**/*.ts
+alwaysApply: false
 ---
 
-# MCP Integration
+# MCP Integration Guide
 
 Every new tRPC procedure that provides useful functionality should be exposed as an MCP tool so AI assistants (Claude, Cursor, etc.) can use it. This is a first-class feature of Homarr.
 
-Exposing a procedure makes it callable by any AI client with an API key. Before adding `.meta({ mcp })`, review what the tool exposes: authorization requirements, sensitive data, tenant isolation, auditability, and whether the action is destructive. Prefer exposing read-only queries over mutations unless the mutation is safe and permission-scoped. When in doubt, ask for a security review before shipping a new MCP tool.
-
 ## Adding MCP to a procedure
 
 Add `.meta({ mcp: { enabled: true, description: "..." } })` to the procedure chain:
@@ -17,7 +16,7 @@ Add `.meta({ mcp: { enabled: true, description: "..." } })` to the procedure cha
 // Read-only tool (query)
 myProcedure: protectedProcedure
   .meta({ mcp: { enabled: true, description: "Get all items with their status and metadata" } })
-  .input(z.object({ limit: z.number().default(10) }))
+  .input(z.object({ limit: z.number().default(50) }))
   .query(async ({ ctx, input }) => { ... })
 
 // Write tool (mutation)
@@ -39,27 +38,23 @@ The `.meta()` call must come **before** `.input()` and `.query()`/`.mutation()`
 The description is the **only thing** an AI sees to decide when and how to use the tool. Write it like you're explaining to a colleague who has never used Homarr.
 
 **Must include:**
-
 - What the tool returns or does
 - Which integrations/services it works with (if applicable)
 - How to get required IDs (e.g., "Use integration_all to get the integrationId")
 - Permission requirements (if non-obvious)
 
 **Good:**
-
-```text
+```
 "Get calendar events for upcoming and recent media releases. Fetches from all connected Sonarr (TV), Radarr (movies), Lidarr (music), and Readarr (books) integrations. Requires integrationIds from integration_all"
 ```
 
 **Bad:**
-
-```text
+```
 "Get calendar events"
 ```
 
 **For tools that return permission fields**, explain what they mean:
-
-```text
+```
 "List all integrations. Returns permissions.hasUseAccess (read) and permissions.hasInteractAccess (actions) — false means the API key lacks that permission, not an error"
 ```
 
@@ -82,13 +77,11 @@ export const mcpRouter = createTRPCRouter({
 ## What to expose vs. what to skip
 
 **Expose:**
-
 - Data queries (list, search, get by ID)
 - Actions users would ask an AI to do (toggle, create, delete, approve)
 - Status checks (health, stats, summaries)
 
 **Skip:**
-
 - Subscriptions (WebSocket-only, not supported by MCP)
 - Internal procedures (session management, onboarding steps)
 - File upload/download procedures

.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,30 +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 page opened from Homarr. 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,15 +33,6 @@ body:
       options:
         # The below comment is used to insert a new version with on-release.yml
         #NEXT_VERSION#
-        - 1.77.0
-        - 1.76.2
-        - 1.76.1
-        - 1.76.0
-        - 1.75.0
-        - 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

@@ -8,7 +8,7 @@ on:
     types: [closed]
     branches: ["*"]
   push:
-    branches: [main, dev, beta, next, 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,22 +82,11 @@ 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
 
@@ -242,7 +229,7 @@ jobs:
     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 == '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
@@ -299,9 +286,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     permissions:
-      contents: read
       packages: write
-      pull-requests: read
     env:
       PREVIEW_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
     steps:
@@ -317,26 +302,6 @@ 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:
@@ -347,18 +312,6 @@ jobs:
             "${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/deployment-docker-image.yml

@@ -68,6 +68,8 @@ jobs:
         with:
           node-version: 24.18.0
           package-manager-cache: false
+      - run: npm i -g pnpm
+        if: env.SKIP_RELEASE == 'false'
       - name: Install dependencies
         if: env.SKIP_RELEASE == 'false'
         run: |

.github/workflows/workshop.yml

@@ -1,63 +0,0 @@
-name: Workshop
-
-on:
-  pull_request:
-  push:
-    branches: [dev, 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 == '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' }}
-            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,12 +71,10 @@ apps/nextjs/public/images/background.png
 
 # personal agent config
 .opencode
-.agents/*
-!.agents/skills/
+.agents/
 skills-lock.json
 
 # docusaurus
 apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
-benchmark-results

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

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

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

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

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

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

.mcp.json

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

.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

@@ -46,8 +46,6 @@ homarr/
 ├── 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
@@ -70,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,19 +79,5 @@ When modifying user-facing code, you MUST also update the corresponding document
 - Lint: oxlint (not ESLint)
 - Format: oxfmt (not Prettier)
 - UI: Mantine (not Tailwind) — Tailwind is only used in docs app
-- Mantine: use the `mantine` MCP server (configured in `.mcp.json`; tools `get_item_doc` / `get_item_props` / `search_docs`) for current v9 APIs before writing component code. Prefer built-in primitives (`Combobox`/`useCombobox` for selects, the polymorphic `component` prop, `@mantine/hooks`) over hand-rolled equivalents. Check `packages/ui/` for existing conventions first.
-
-## MCP servers
-
-`.mcp.json` at the repo root declares project-scoped MCP servers (the standard Claude Code layout; other tools can import the same `mcpServers` block). See the `mantine` entry there for the Mantine v9 server, and the upstream docs at https://mantine.dev/guides/llms/ for per-tool setup (OpenCode: `.opencode/opencode.json`, Codex: `.codex/config.toml`). Only keyless server definitions belong in `.mcp.json`; anything needing secrets stays in local dotfiles.
-
-## Agent Skills
-
-Portable agent skills live in `.agents/skills/` (the Agent Skills open standard). Cursor, Codex, and OpenCode read `.agents/skills/` natively. Claude Code does not scan it, so `.claude/skills/` is a symlink back to `.agents/skills/`. Install skills at `.agents/skills/<name>/SKILL.md` — that single copy is used everywhere. See `.agents/skills/` for available skills (documentation-sync, mcp-integration, codebase-context, datatable-migration).
-
 - Icons: @tabler/icons-react
 - Docs app can import from `@homarr/definitions` for shared types
-- Run `pnpm dev:cli -- dev` to browse local `homarr:*` images and remote PR images.
-- Run `pnpm dev:cli -- build <name>` from a Homarr checkout to build `homarr:<name>` with rebuild provenance.
-- Run `pnpm dev:cli -- build --pr <number>` to build a PR locally from a temporary checkout.
-- Run Go checks from `tools/homarr-dev` with `go test ./...` and `go vet ./...`.

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,21 +1,3 @@
-## [1.77.0](https://github.com/homarr-labs/homarr/compare/v1.76.2...v1.77.0) (2026-09-06)
-
-## [1.76.2](https://github.com/homarr-labs/homarr/compare/v1.76.1...v1.76.2) (2026-08-27)
-
-## [1.76.1](https://github.com/homarr-labs/homarr/compare/v1.76.0...v1.76.1) (2026-08-26)
-
-## [1.76.0](https://github.com/homarr-labs/homarr/compare/v1.75.0...v1.76.0) (2026-08-21)
-
-## [1.75.0](https://github.com/homarr-labs/homarr/compare/v1.74.0...v1.75.0) (2026-08-14)
-
-## [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)

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"]

PRODUCT.md

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

apps/docs/README.md

@@ -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/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/command-line/development/index.mdx

@@ -1,41 +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 run <name>
-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,121 +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`.
 
-### Run PocketBase and documentation
+8. Start the development server with `pnpm dev` and wait for a message that says `✓ Ready in 10.7s`
 
-Start PocketBase in another terminal:
+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)
 
-```sh
-cp apps/workshop/.env.example apps/workshop/.env
-docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
-```
+### Useful npm scripts
 
-Then start Docusaurus in a third terminal:
+#### During development
 
-```sh
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
-```
+- `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.
 
-PocketBase runs on port 8090 and Docusaurus on port 3003. Stopping the services preserves the PocketBase volume.
+#### Checking code quality
 
-Open `http://127.0.0.1:8090/_/` and create the first PocketBase superuser. The Workshop UI is available at
-`http://127.0.0.1:3003/workshop`.
+- `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.
 
-Point Homarr at the local services with:
+#### Building the project
 
-```dotenv
-HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-WORKSHOP_API_URL=http://127.0.0.1:8090
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-```
-
-Restart `pnpm dev` after changing `.env`. GitHub OAuth is optional locally. See
-[`apps/workshop/README.md`](https://github.com/homarr-labs/homarr/blob/HEAD/apps/workshop/README.md) for OAuth,
-Workshop moderator promotion, logs, tests, backup, restore, stopping, and intentional volume reset.
-
-### URL testing
-
-Docusaurus reads `HOMARR_WEBSITE_URL` and `WORKSHOP_API_URL` when it starts or builds. Homarr also reads
-`WORKSHOP_WEB_URL` when its server starts, so these values do not rely on `NEXT_PUBLIC_*` build variables. Test a
-separate API origin before release:
-
-```sh
-HOMARR_WEBSITE_URL=http://127.0.0.1:3003 \
-WORKSHOP_API_URL=http://127.0.0.1:8090 \
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop \
-pnpm dev:docs
-```
-
-### Useful commands
-
-- `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:workshop` — local PocketBase through Docker Compose.
-- `pnpm docker:dev:up` — Redis development service in the background.
-- `pnpm cli` — Homarr operations CLI.
-- `pnpm db:migration:sqlite:run` — create or update a SQLite database.
-- `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 test:workshop` — disposable Workshop integration suite.
-- `pnpm build` — production monorepo build.
-- `docker build -t homarr .` — build a production Docker image.
-- `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>` — run it.
+- `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,17 +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 page opened from Homarr.                                                                                                                                                                                               | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
+| 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
 
@@ -55,11 +51,11 @@ A random secret can be generated by using the following command: `openssl rand -
 
 ## Docker
 
-| Environment Variable  | Description                                                                                                                              | Possible values                                         | Default |
-| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------- |
-| `DOCKER_HOSTNAMES`    | Comma-separated list of hostnames to connect to                                                                                          | For example `localhost,docker.example.com`              | -       |
-| `DOCKER_PORTS`        | Comma-separated list of ports to connect to                                                                                              | For example `2375,2376`                                 | -       |
-| `DOCKER_SOCKET_PATHS` | Comma-separated list of mounted Docker-compatible socket paths. See the [Docker and Podman integration guide](/docs/integrations/docker) | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
+| 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
 
@@ -109,12 +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.                                                                                                                                                               |
-| `WORKSHOP_PUBLIC_ORIGIN` | Origin used in PocketBase-generated links and email. It must be set explicitly in production and must match the externally reachable Workshop origin.                                                             |
-| `PB_ALLOWED_ORIGINS`     | Browser origins accepted by PocketBase. Use `*` for the central public community so arbitrary self-hosted Homarr instances can use the API and OAuth; private staging may use a comma-separated origin allowlist. |
-
-All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
-trailing slashes when Homarr or Docusaurus starts. The Docusaurus-only `WORKSHOP_URL` name is accepted as a deprecated alias for
-`WORKSHOP_API_URL` for one release. `WORKSHOP_API_URL` takes precedence.
+| 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/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/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/installation/helm.md

@@ -2,9 +2,9 @@
 
 <img src="https://raw.githubusercontent.com/homarr-labs/charts/refs/heads/main/charts/homarr/icon.svg" align="right" width="92" alt="homarr logo">
 
-![Version: 8.28.1](https://img.shields.io/badge/Version-8.28.1-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.76.1](https://img.shields.io/badge/AppVersion-v1.76.1-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.76.1"`                                                                                                                                                                                                                                      | 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/index.mdx

@@ -54,74 +54,6 @@ services:
 With docker run, add this parameter: `-v /var/run/docker.sock:/var/run/docker.sock`.
 In Windows, you'll need to adjust the slashes: `-v //var/run/docker.sock:/var/run/docker.sock`
 
-### Using Podman
-
-On Linux, Homarr can connect to Podman's [Docker-compatible API](https://docs.podman.io/en/latest/markdown/podman-system-service.1.html).
-The Podman API socket must be running and mounted into the Homarr container.
-The socket grants full access to Podman, including arbitrary code execution as the user running the API, so only mount it into trusted containers.
-
-For rootless Podman, enable the socket for the user that runs Homarr:
-
-```bash
-systemctl --user enable --now podman.socket
-```
-
-The rootless socket is located at `$XDG_RUNTIME_DIR/podman/podman.sock` (usually `/run/user/<uid>/podman/podman.sock`).
-You can confirm the path with:
-
-```bash
-podman info --format '{{.Host.RemoteSocket.Path}}'
-```
-
-Mount that socket into the Homarr container and point `DOCKER_SOCKET_PATHS` to its path **inside** the container:
-
-```yaml
-services:
-  homarr:
-    container_name: homarr
-    image: ghcr.io/homarr-labs/homarr:latest
-    restart: unless-stopped
-    volumes:
-      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
-      - ./homarr/appdata:/appdata
-    environment:
-      SECRET_ENCRYPTION_KEY: your_64_character_hex_string
-      DOCKER_SOCKET_PATHS: /var/run/podman.sock
-    ports:
-      - "7575:7575"
-```
-
-Start Homarr with `podman compose up -d`.
-Run the compose project as the same user that owns the rootless Podman socket so `$XDG_RUNTIME_DIR` resolves to the correct path.
-To keep the user socket available after logout and across reboots, enable lingering with `loginctl enable-linger <user>`.
-
-For rootful Podman, enable the system socket with `sudo systemctl enable --now podman.socket`.
-Its default path is `/run/podman/podman.sock`; mount that path instead and start Homarr with `sudo podman compose up -d`.
-
-:::note SELinux
-On systems with SELinux enabled, Podman's documentation recommends disabling label separation for a container that accesses the API socket.
-Add the following to the Homarr service:
-
-```yaml
-security_opt:
-  - label=disable
-```
-
-:::
-
-You can connect Homarr to multiple Docker-compatible sockets by mounting each socket and listing their in-container paths, separated by commas:
-
-```yaml
-services:
-  homarr:
-    image: ghcr.io/homarr-labs/homarr:latest
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
-      - ${XDG_RUNTIME_DIR}/podman/podman.sock:/var/run/podman.sock
-    environment:
-      DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
-```
-
 ### Managing your Docker containers within Homarr
 
 Homarr allows you to interact with Docker containers running on your system.

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/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/truenas/index.mdx

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

apps/docs/docs/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

@@ -83,16 +83,3 @@ The OpenAPI and MCP APIs include board management endpoints for common automatio
 - Configure global board defaults such as public home boards and status behavior
 
 Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
-
-## Get Custom Widget authoring resources
-
-Custom JSX v2 provides four HTTP discovery endpoints:
-
-- `GET /api/custom-widgets/authoring-prompt` returns the current prompt plus MCP and HTTP resource identifiers.
-- `GET /api/custom-widgets/schema` returns the canonical widget JSON Schema.
-- `GET /api/custom-widgets/components` returns the release-matched static component catalog.
-- `GET /api/custom-widgets/skill` returns the concise live `SKILL.md` plus skills.sh, source, and install metadata. Retrieve the schema, component catalog, and examples through their dedicated resources only when needed.
-
-Call `customWidget_configurationRequestUser` to create a temporary API source setup URL where the user can confirm their server URL and enter credentials. Do not construct or save this URL.
-
-Authenticated tRPC and MCP procedures support definition management, validation, previews, template patches, and credential writes. An exported definition does not contain credentials.

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

@@ -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,14 +40,11 @@ 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
 

apps/docs/docs/management/backup.mdx

@@ -29,7 +29,7 @@ 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
 

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

@@ -36,13 +36,13 @@ Underscores and hyphen-minus are allowed.
 
 ### Column count
 
-Homarr has a complex drag-and-drop system that can be used from the browser.
+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
@@ -55,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
@@ -107,7 +105,7 @@ Amount of columns for this layout. Defines how many items can be placed in a row
 #### Breakpoint
 
 Minimum width of the screen where the layout will be used.
-Once the minimum of the next layout is reached the layout will change.
+Once the minmum of the next layout is reached the layout will change.
 
 #### Preview
 
@@ -221,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.

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

@@ -58,11 +58,6 @@ This means you can automate the update of the certificates by simply replacing o
 Every integration has its own way of obtaining certificates.
 Generally it is recommended to search for the documentation of the integration you are using.
 Most of the time you can find the certificate in the file system of the integration.
-The certificate file needs to be uploaded to Homarr. To first get the file on your computer you can either:
-
-- use `scp user@host:/path/to/file ./certificate.pem`
-- use `cat /path/to/file` to print the certificate. Then recreate the file on your machine.
-
 Below you can find instructions for some of the integrations.
 
 ### Pi-hole (v6)
@@ -70,9 +65,3 @@ Below you can find instructions for some of the integrations.
 Since version 6 of Pi-hole, the web interface can be accessed through HTTPS.
 The certificate can be found in the path `/etc/pihole/tls_ca.crt`. To add the certificate, this file needs to be copied and uploaded to Homarr.
 You can find more details regarding SSL / TLS for Pi-hole [here](https://docs.pi-hole.net/api/tls/).
-
-### Proxmox
-
-By default, Proxmox VE uses a node certificate signed by the cluster. You only need to configure Homarr with the certificate of a single node.
-The certificate can be found in any node on the path `/etc/pve/pve-root-ca.pem`.
-You can learn more about certificate management in Proxmox [here](https://pve.proxmox.com/wiki/Certificate_Management).

apps/docs/docs/management/custom-widgets/_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,104 +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. The Homarr MCP prompt gives connected agents a retrieval workflow: read the live schema, then 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 the MCP tool return the concise skill discovery payload:
-
-```ts
-{
-  name: "homarr-custom-widget";
-  version: string;
-  skillMd: string;
-  skillsShUrl: string;
-  sourceUrl: string;
-  installCommand: string;
-}
-```
-
-The full installed component catalog stays available through `homarr://custom-widgets/components` and per-component resources. It is deliberately not embedded in the skill or clipboard prompt.
-
-These interfaces do not return an archive URL or archive hash.
-
-## Create a Custom Widget with MCP
-
-1. Get the prompt, live schema, and component catalog.
-2. Read the external API documentation.
-3. Build one definition.
-4. Validate the definition without saving it.
-5. Create a preview session.
-6. Test the queries and actions.
-7. Open the preview URL with browser tools.
-8. Inspect the redacted journal and revise the local candidate until it is valid.
-9. Create the widget, including any source URLs and credentials the user already supplied.
-10. Otherwise, ask the user to configure the saved definition with the ten-minute Homarr source-setup URL.
-11. Create a final preview with the saved definition ID so Homarr loads its stored credentials, then test it again.
-12. Update the saved definition if the final verification finds a problem.
-13. Repeat the procedure for the next widget.
-
-Each source-configuration URL applies to one definition or preview and one source. It is short-lived, single-use, and
-can only be opened and completed by an authenticated Homarr administrator. The administrator confirms the server URL,
-network scope, and required credential fields directly in Homarr. The agent receives only request status and never
-receives plaintext credentials. Preview-scoped values expire with that preview; definition-scoped values persist.
-
-Agents can install existing widgets without regenerating them:
-
-1. Search with `customWidget_workshopSearch`.
-2. Inspect and validate a result with `customWidget_workshopGet`.
-3. Install it with `customWidget_workshopInstall`.
-4. Configure deployment-specific URLs and supplied credentials with `customWidget_sourceConfigure`.
-5. If the agent does not have those values, call `customWidget_configurationRequestUser` and wait for completion.
-6. Test the installed definition, then use `board_addItem` with kind `customApi` and the returned definition ID.
-
-Homarr encrypts the plaintext immediately. Homarr does not return the plaintext.
-
-## Evaluate the copied prompt
-
-Homarr maintainers can run the same self-contained prompt that the workbench copies through the live generation-quality suite:
-
-```sh
-OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:ai
-```
-
-The suite uses DeepSeek V4 Pro to author Pokédex, Portainer, football, Jellyfin, and Home Assistant widgets. Before DeepSeek V4 Flash judges a result, it must pass Homarr's real clipboard parser, canonical schema, and deterministic scenario checks for the documented API routes, authentication, bindings, actions, and essential runtime components. It saves every response, validated widget manifest, and detailed category scores under `packages/custom-widgets/.ai-evaluations/`.
-
-Each scenario stops as soon as it passes and has a hard limit of ten generation attempts. Override the models or
-per-scenario limit with `OPENROUTER_GENERATOR_MODEL`, `OPENROUTER_JUDGE_MODEL`, and
-`CUSTOM_WIDGET_AI_MAX_LOOPS`. Generated artifacts are local and ignored by Git; promote a reviewed, validated result
-into the bundled-widget source deliberately.
-
-The reference API check uses a real PokeAPI list/detail request and a read-only Portainer container query when `PORTAINER_BASE_URL` and `PORTAINER_API_KEY` are set. Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --pokeapi-only` for the public PokeAPI check alone. To exercise start, restart, and stop against a disposable container, also set `PORTAINER_TEST_CONTAINER_ID` and the explicit safeguard `PORTAINER_ALLOW_MUTATIONS=1`; the script restores the container's original running state.
+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,38 +1,36 @@
-# Create a Custom Widget
+---
+sidebar_label: Authoring workbench
+---
 
-import { CanonicalCustomWidgetExample } from "@site/src/components/custom-widget-code";
+# Authoring workbench
 
-The workbench is visual-first: configure the default API connection, add request cards, add option rows, then write JSX. Additional sources and raw manifest JSON remain under Advanced. Code and preview sit side by side on desktop and use tabs on mobile.
+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.
 
-## Manual workflow
+## Choose a display
 
-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.
+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.
 
-<CanonicalCustomWidgetExample
-  id="named-widget-requests"
-  label="Named queries and actions"
-  example="requests"
-  height="420px"
-/>
+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.
 
-<CanonicalCustomWidgetExample id="widget-options" label="Widget options" example="options" height="360px" />
+## Test and preview
 
-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` with a query ID and value/label paths.
+The preview has four tabs:
 
-## ChatGPT or Claude
+- **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.
 
-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.
+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.
 
-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.
+## Keyboard and clipboard
 
-Homarr shows all actionable schema or JSX errors inline. Enter credentials separately. The prompt deliberately
-recommends a focused Mantine component set, visual hierarchy, responsive layout, theme compatibility, and loading,
-empty, failure, and success states.
+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.
 
-Connected agents should use the skills.sh skill and retrieve the live schema and individual component metadata only as needed.
+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.
+
+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.
+
+## Save behavior
+
+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,45 +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`.
 
-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.
+## Data and rendering
 
-## 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) => (
-      <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. Patterns with lookbehind, backreferences, nested quantifiers, excessive length, or unsupported flags 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 manual query with its `params`. Set `triggerContent` to a card or image to make that content the accessible click and keyboard trigger instead of showing the default load button.
-- `ActionButton` and `ToggleSwitch` run actions.
-- `RefreshButton` renders a compact, accessible icon control that refreshes load queries for authenticated viewers. It
-  is disabled for anonymous public-board viewers because refreshing invalidates shared server cache state.
-- `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,130 +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
+    }
+  ]
 }
 ```
 
-<CustomWidgetCodeExample
-  id="complete-widget-manifest"
-  label="Complete manifest"
-  code={completeManifest}
-  height="360px"
-/>
+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 browser renders JSX. Homarr's server executes named requests, applies board permissions and network protections, and injects credentials. The browser never receives source credentials.
+`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:
 
-## Permissions
+```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>
+```
 
-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.
+| 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                             |
 
-Adding or configuring a Custom Widget placement requires both administrator access and permission to modify that
-board. 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. Duplicating
-a board that contains Custom Widgets also requires an administrator.
+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.
 
-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.
+### Network scopes
 
-## Authoring paths
+| Scope      | Allowed destinations                                         |
+| ---------- | ------------------------------------------------------------ |
+| `public`   | Public IP addresses only                                     |
+| `private`  | Public addresses plus RFC1918 and IPv6 ULA private addresses |
+| `loopback` | Public, private, and loopback addresses                      |
 
-- [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).
+Link-local, cloud-metadata, unspecified, multicast, documentation, carrier-grade NAT, and IPv4-mapped bypass addresses remain blocked in every scope.
 
-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.
+### Example with a named query
 
-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.
+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:
 
-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.
+```json
+{
+  "id": "pokemon-detail",
+  "kind": "query",
+  "method": "GET",
+  "pathTemplate": "/api/v2/pokemon/{name}",
+  "parameters": { "name": "string" },
+  "auth": "none",
+  "minimumBoardPermission": "view",
+  "cacheTtlSeconds": 300
+}
+```
 
-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. The steps keep the same dimensions and the previous step remains available when
-you go back. After import, the new definition appears in the picker. Its tile
-waits for the board to be saved before server requests run and loads automatically after a successful save; no page
-reload is required.
+## Agent authoring through MCP
 
-## Import and Workshop
+Administrators can use Homarr's MCP server to iterate on custom widgets without bypassing validation or network controls. A typical agent workflow is:
 
-The install flow always links to the corresponding public Workshop entry using `WORKSHOP_WEB_URL`. 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.
+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 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.
+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.
 
-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.
+## Component reference
 
-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.
+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.
 
-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.
+<CustomJsxComponentReference />
 
-## Reliability and rollback
+This table and the searchable component list in the editor are generated from Homarr's runtime registry.
 
-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.
+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.
 
-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.
+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.
 
-## Bundled examples
+## HTTP protections and limits
 
-Homarr seeds five disabled examples without credentials and never overwrites an edited seed. They use the same public contract. The Tautulli example is the highest-scoring widget preserved from Homarr's AI authoring evaluation:
+All base, preview, query, and action requests use the same server executor:
 
-<BundledCustomWidgetGallery />
+- 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.
+
+## Import and export
+
+New exports use `"$schema": "homarr-custom-widget-v3"`. Version 2 imports remain accepted. Secrets are never exported and must be entered again after import.
+
+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,53 +1,32 @@
-# Configure requests and security
+---
+sidebar_label: Requests and security
+---
 
-Most widgets use a single source named `default`. Extra keyed sources are available under Advanced for widgets that combine APIs. 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.
+# 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.
 
-Paths and query-string values must resolve to text, numbers, or booleans. 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.
 
-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 for anonymous viewers, while ordinary scheduled query rendering remains
-available.
-
-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,83 +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 the current schema errors.
-
-## 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/mcp.mdx

@@ -92,10 +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.
-
 ## Testing the Connection
 
 Verify your MCP endpoint is working:
@@ -166,75 +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.
+:::
 
-Then, read the live schema and component resources. These resources describe the installed Mantine components.
+### 1. Get the schema
 
-1. Call `customWidget_getAuthoringPrompt` and `customWidget_schema`.
-2. Build one Custom Widget definition.
-3. Call `customWidget_validate` without saving the definition.
-4. Call `customWidget_previewCreate`.
-5. Test named requests with `customWidget_previewQuery` and `customWidget_previewAction`.
-6. Open the returned preview URL.
-7. Examine `customWidget_previewJournal`.
-8. Revise the local candidate and create another preview session until it is ready.
-9. Call `customWidget_create`, supplying any credentials and deployment-specific source URLs the user already provided.
-10. If the user must enter the source URL or credentials, call `customWidget_configurationRequestUser` with the new definition ID and wait for completion.
-11. Create a final preview with that definition ID so Homarr loads its stored credentials, then test it again.
-12. Use `customWidget_update` or `customWidget_templatePatch` for any final saved-definition corrections.
-13. 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.
 
-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.
+### 2. Draft and validate
 
-Discovery resources:
+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.
 
-- `homarr://custom-widgets/schema`
-- `homarr://custom-widgets/components`
-- `homarr://custom-widgets/components/{name}`
-- `homarr://custom-widgets/examples/{name}`
-- `homarr://custom-widgets/skill`
+### 3. Create the widget
 
-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.
+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.
 
-The Custom Widget tools are:
+### 4. Test with real data
 
-- `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_getSkill`
+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.
 
-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.
+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.
 
-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.
+### 5. Iterate on the template
 
-Homarr applies its request security controls during request execution. These controls include SSRF, DNS, redirect, size, timeout, rate, and permission controls.
+Use `customWidget_readTemplate` to get the current JSX template as plain text, then `customWidget_writeTemplate` to push updates. The write tool accepts either:
 
-Read [Use agents and skills.sh](./custom-widgets/agent-authoring) for the complete procedure and the portable Agent Skill.
+- `template` — a single string (newlines as `\n`)
+- `templateLines` — an array of strings (joined with newlines server-side, avoids `\n` escaping)
+
+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/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)

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

@@ -1,169 +0,0 @@
----
-tags:
-  - Workshop
-  - Custom Widgets
-  - Custom CSS
----
-
-# Community Workshop
-
-:::warning Experimental feature
-
-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!
-
-:::
-
-The [Community Workshop](pathname:///workshop) is where Homarr users share and discover
-**custom CSS themes** and **custom widgets**. You can browse submissions, upvote the ones
-you like, report abuse, and install entries directly into your own Homarr instance.
-
-The central `homarr.dev` Workshop is a public community. Browsing it on the website is public. Browsing, installing,
-publishing, or importing Workshop content **inside a Homarr instance is restricted to Homarr administrators**.
-
-:::warning
-
-The Workshop contains community-made content. Moderation is not a security boundary, and PocketBase does not interpret
-or validate submission content. Always review widget capabilities, network origins, actions, and CSS before installing.
-Homarr's installation-time validator is definitive and can reject content that the public service accepted earlier.
-Back up your instance before installing untrusted content.
-
-:::
-
-## Browsing and voting
-
-- Filter by **Widgets** or **CSS**, show or hide outdated entries, and sort by popularity, creation date, recent updates, or discussion activity.
-- Sign in with **GitHub** to upvote/downvote, submit your own creations, or report a submission.
-- Each submission shows its title, description, linked GitHub author, revision, optional screenshots, comments, and full content. Widget pages also summarize API sources, actions, options, network access, and required credentials before installation.
-- A new submission receives one real upvote owned by its author. Votes remain unique per user and submission.
-- Open report counts are public on submission cards so visitors can make an informed installation decision. The submission author and Workshop moderators can read each report category and explanation; reporter identities remain moderator-only.
-- Signed-in moderators see a **Moderation** button in the Workshop header. The moderation queue is sorted by open report count and lets moderators inspect every report, dismiss it, or delete the submission. Reports do not automatically remove a submission.
-- The manual **Outdated** badge warns visitors that a submission may need an update.
-
-## Comments
-
-Comments are publicly readable and appear in chronological conversation bubbles with the author's avatar and GitHub profile. Signed-in users can post; authors can edit or delete their own comments, and Workshop moderators can delete any comment. Failed posts keep the text you typed. When SMTP and `WORKSHOP_PUBLIC_ORIGIN` are configured, the submission author receives one email for a comment from another user. Self-comments, edits, and deletions do not send mail.
-
-## Submitting
-
-1. Sign in with GitHub.
-2. Click **Share yours** and choose the type:
-   - **Custom widget** — paste the JSON exported from **Manage → Custom Widgets → Export**.
-     It must match the `homarr-custom-widget-v2` schema (validated before submission).
-   - **Custom CSS** — paste your stylesheet (max 16384 characters).
-3. Review the widget JSON or CSS in the syntax-aware editor, then add a title, description, optional screenshots, and changelog.
-4. Submit the entry.
-
-Custom widget JSON is normalized to readable multi-line formatting when it is published, and the Workshop detail page
-also formats older compact submissions before displaying them.
-
-Community members can report submissions as outdated or no longer working, malicious, spam, copyright-infringing,
-inappropriate, or another concern. An outdated report does not automatically mark or remove the submission.
-
-Submissions are published immediately. Reported entries are reviewed and may be removed.
-Authors can edit a submission later to publish a new revision. The edit form can keep or remove existing screenshots and add new PNG, JPG, or WebP images without changing the Workshop URL.
-
-When SMTP and `WORKSHOP_PUBLIC_ORIGIN` are configured, every current Workshop moderator receives an email when a report is submitted. If a moderator deletes the reported submission, its author receives a separate removal email. Author self-deletion does not send a moderation email.
-
-:::info Separate roles
-
-A Workshop moderator is a user with PocketBase's internal `isAdmin` field. This role moderates the central community
-and is unrelated to a Homarr instance administrator.
-
-:::
-
-## Submission guidelines
-
-Submissions must be useful to Homarr users and safe to install. Do not submit content that is
-malicious, deceptive, illegal, hateful, sexually explicit, gore, gambling-focused, spam, or content
-that primarily promotes unrelated products or services.
-
-## Installing into Homarr
-
-You can install workshop entries without leaving Homarr:
-
-- **Custom widgets (Homarr administrators only)** — go to **Manage → Custom Widgets**, or use **Import from Workshop** in the
-  board widget picker. Choose **Install widget**, review the complete source and capabilities, then confirm API sources and any local secrets in the second modal step.
-- **Custom CSS from Workshop (Homarr administrators only)** — open a board's **Settings → Custom CSS**, click **Import from Workshop**, choose a theme, review its full CSS in the second same-size modal step, and click **Import CSS** once. The board setting is still saved separately.
-
-Alternatively, open a submission in the Workshop and use **Download widget JSON** or **Copy CSS**. The submission page shows the matching manual installation steps before the source code.
-
-Custom Widget imports detect required bearer, basic, header, or query credentials. You can enter them during import or explicitly defer them; secret values are never stored in Workshop content. Missing credentials remain visible on the local Custom Widget afterward.
-
-## Workshop deployment
-
-Workshop is powered by [PocketBase](https://pocketbase.io). The production image compiles the current Docusaurus site and serves it together with the API from one origin. The deployment lives in `apps/workshop/` with a Dockerfile, Compose configuration, version-controlled migrations, hooks, a smoke test, and ACT-local workflow instructions.
-
-Submission links include Open Graph and X/Twitter metadata for the submission title, description, and type. The first uploaded screenshot is used as the social preview image; submissions without screenshots use the Homarr logo.
-
-Run `pnpm docker:workshop` for PocketBase on port 8090, then run
-`WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs` for Docusaurus on port 3003. `pnpm docker:docs` builds the
-combined production layout. Normal start and stop commands retain data; `down --volumes` is an intentional,
-irreversible development reset.
-
-GitHub needs only the central callback `https://<workshop-host>/api/oauth2-redirect`. Keep PocketBase origins unrestricted
-unless every self-hosted Homarr caller is explicitly listed. Configure both `GITHUB_CLIENT_ID` and
-`GITHUB_CLIENT_SECRET`; supplying only one is a startup error. Set `WORKSHOP_PUBLIC_ORIGIN` in production so generated
-links and email use the public host. Workshop stores only the OAuth provider username in `users.name`, and
-users cannot rename it. Map **OAuth2 username** to `name`; leave OAuth2 id, full name, and avatar mappings
-empty. Profile and avatar URLs are derived from `https://github.com/<username>` and
-`https://github.com/<username>.png`, so PocketBase does not store duplicate profile metadata or avatar files. Configure
-SMTP for comment, report, and removal notices.
-
-The public URL contract is:
-
-| Variable                 | Purpose                                           | Default                       |
-| ------------------------ | ------------------------------------------------- | ----------------------------- |
-| `HOMARR_WEBSITE_URL`     | Documentation/site base used by Homarr links      | `https://homarr.dev`          |
-| `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone docs | `HOMARR_WEBSITE_URL`          |
-| `WORKSHOP_WEB_URL`       | Public Workshop page linked from Homarr           | `HOMARR_WEBSITE_URL/workshop` |
-| `WORKSHOP_PUBLIC_ORIGIN` | PocketBase-generated links and email              | Required in production        |
-| `PB_ALLOWED_ORIGINS`     | PocketBase browser origins                        | `*` for the central community |
-
-The deprecated docs-only `WORKSHOP_URL` alias remains for one release; `WORKSHOP_API_URL` takes precedence. The
-combined Workshop image writes these public URLs into its browser runtime configuration whenever the container starts;
-the Docker build arguments remain fallbacks. Restart the container after changing these values, without rebuilding it.
-
-### Staging and demo deployment
-
-Use `apps/workshop/docker-compose.staging.yml` with the published `ghcr.io/homarr-labs/workshop:v2` image for a v2
-preview. Copy `apps/workshop/.env.staging.example` to `.env.staging`; its default public contract is:
-
-```dotenv
-HOMARR_WEBSITE_URL=https://v2.preview.homarr.dev
-WORKSHOP_API_URL=https://v2.preview.homarr.dev
-WORKSHOP_WEB_URL=https://v2.preview.homarr.dev/workshop
-WORKSHOP_PUBLIC_ORIGIN=https://v2.preview.homarr.dev
-PB_ALLOWED_ORIGINS=*
-```
-
-Start or update it from the repository root:
-
-```sh
-docker compose --env-file apps/workshop/.env.staging \
-  -f apps/workshop/docker-compose.staging.yml pull
-docker compose --env-file apps/workshop/.env.staging \
-  -f apps/workshop/docker-compose.staging.yml up --detach
-curl --fail http://127.0.0.1:8090/api/health
-```
-
-The service binds to `127.0.0.1:8090`. Terminate TLS at a reverse proxy and forward the **entire hostname**, including
-`/api`, `/_/`, and `/workshop-runtime-config.js`; forwarding only `/workshop` breaks PocketBase and runtime URL loading.
-This combined image serves both the documentation site and PocketBase, so use a dedicated Workshop hostname if the
-chosen hostname already serves Homarr itself. In that case, replace the hostname in all four URL values and keep
-`/workshop` only on `WORKSHOP_WEB_URL`.
-
-The Compose volume preserves PocketBase data across pulls and container recreation. The mutable `v2` tag is suitable
-for previews; use the `sha-<commit>` tag for promotion. For the public central Workshop, `PB_ALLOWED_ORIGINS=*` allows
-self-hosted Homarr origins to use the API and OAuth. A private demo may use a comma-separated origin allowlist instead.
-GitHub OAuth requires both credentials and the callback
-`https://v2.preview.homarr.dev/api/oauth2-redirect`. Restart after changing environment values, then verify the health
-endpoint, `/workshop`, a public listing request, GitHub sign-in, and an installation from the Homarr preview.
-
-Back up application and PocketBase data before deployment. Publish the combined image by immutable digest, test the
-exact digest in staging, rehearse application rollback and PocketBase restore, then promote that same digest.
-
-## Client architecture
-
-Workshop access is centralized in `@homarr/workshop/backend`. It exports the typed `WorkshopBackend`, its typed PocketBase instance, stable TanStack Query option factories, and the `useWorkshop…` query and mutation hooks used by Homarr. The documentation site uses the same backend rather than maintaining a second API contract.
-
-Listing fields derived by the `workshop_listings` view—such as submission type, score, and counts—are normalized by the shared client. Healthy deployments keep filtering, sorting, and pagination in PocketBase. If a persistent development volume still has an older view that rejects those fields, the client retries without them and applies the same operations locally; it can also fall back to the base submissions collection. Production deployments should nevertheless apply the current migration so the view exposes the complete metadata.

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

@@ -13,7 +13,6 @@ import { appWidget } from ".";
 
 The app widget allows you to add a link to an application or a website that you want to access quickly from your Homarr board.
 It also supports a status check to indicate whether Homarr can reach the application or website.
-In view mode, right-clicking uses the browser's link menu. Homarr's widget menu remains available in edit mode.
 
 ### Screenshots
 

apps/docs/docs/widgets/audio-stats/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Audio Stats"
-description: "Displays media and listening statistics from Navidrome or Audiobookshelf, adapting its display based on the linked integration."
+description: "Displays library statistics from Navidrome or Audiobookshelf, adapting its display based on the linked integration."
 hide_title: true
 ---
 
@@ -16,7 +16,7 @@ import { audiobookshelfIntegration } from "@site/docs/integrations/audiobookshel
 
 This widget adapts its display based on the linked integration:
 
-- **Navidrome**: Shows artist, album, and song counts
+- **Navidrome**: Shows artist, album, and song counts, plus a now playing section with active streams
 - **Audiobookshelf**: Shows library count, audiobook/podcast totals, listening time, and active sessions
 
 Only options relevant to your linked integration are shown in the configuration panel.
@@ -27,7 +27,7 @@ Only options relevant to your linked integration are shown in the configuration
   items={[
     {
       integration: navidromeIntegration,
-      note: "Displays music library statistics",
+      note: "Displays music library stats and now playing",
     },
     {
       integration: audiobookshelfIntegration,

apps/docs/docs/widgets/audio-stats/index.ts

@@ -27,6 +27,24 @@ export const audioStatsWidget: WidgetDefinition = {
         values: { type: "boolean" },
         defaultValue: "yes",
       },
+      {
+        name: "Show now playing",
+        description: "Displays currently playing tracks (Navidrome only)",
+        values: { type: "boolean" },
+        defaultValue: "yes",
+      },
+      {
+        name: "Show now playing list",
+        description: "Displays a detailed list of now playing tracks (Navidrome only)",
+        values: { type: "boolean" },
+        defaultValue: "yes",
+      },
+      {
+        name: "Max now playing items",
+        description: "Maximum number of now playing tracks to display (Navidrome only)",
+        values: "Number (1-5)",
+        defaultValue: "3",
+      },
       {
         name: "Show library count",
         description: "Displays the number of libraries (Audiobookshelf only)",

apps/docs/docs/widgets/beszel-system-stats/index.mdx

@@ -15,7 +15,7 @@ import beszelSystemStats from "./img/beszel-system-stats.png";
 
 <WidgetHeader widget={beszelSystemStatsWidget} categories={["System Monitoring", "Charts"]} />
 
-This widget displays time-series charts for a selected Beszel system, including CPU, memory, disk, network, and Docker container metrics. The Disk Usage chart combines the root disk and every extra filesystem reported by Beszel. You can use the realtime Live view or select a historical period ranging from 1 hour to 30 days. Live view keeps a one-minute window and pauses while the browser tab is hidden. If the live stream drops, the widget now shows the connection failure state immediately and can switch back to historical data.
+This widget displays time-series charts for a selected Beszel system, including CPU, memory, disk, network, and Docker container metrics. The Disk Usage chart combines the root disk and every extra filesystem reported by Beszel. You can use the realtime Live view or select a historical period ranging from 1 hour to 30 days. If the live stream drops, the widget now shows the connection failure state immediately and can switch back to historical data.
 
 ### Screenshots
 

apps/docs/docs/widgets/beszel-system-table/index.mdx

@@ -13,17 +13,10 @@ import { beszelIntegration } from "@site/docs/integrations/beszel";
 
 <WidgetHeader widget={beszelSystemTableWidget} categories={["System Monitoring"]} />
 
-This widget displays all your Beszel-monitored systems in a sortable data table. Each row shows system metrics like CPU, memory, disk, network, temperature, and more. Columns can be toggled on or off, dragged into a different order, and resized from their headers. Column order and widths are saved automatically for each widget. When Beszel reports extra filesystems, the disk column adds a hover breakdown for each mount alongside the root disk.
+This widget displays all your Beszel-monitored systems in a sortable data table. Each row shows system metrics like CPU, memory, disk, network, temperature, and more. Columns can be toggled on or off, and the table supports sorting by any column. When Beszel reports extra filesystems, the disk column adds a hover breakdown for each mount alongside the root disk.
 
 Select a system row to open the complete statistics view, including system, filesystem, Docker, historical, and realtime charts.
 
-### Interactions
-
-- **Reorder columns** by hovering a header to reveal its grab handle, then dragging it
-- **Resize columns** by dragging a header's right edge
-- **Sort systems** by selecting a sortable column header
-- **Open system statistics** by selecting a row
-
 ### Supported Integrations
 
 <WidgetIntegrations

apps/docs/docs/widgets/bookmarks/index.mdx

@@ -13,7 +13,6 @@ import { bookmarksWidget } from ".";
 
 The bookmarks widget allows you to display multiple app links in a single widget.
 You can add links to your favorite applications, websites, or any other resources you want quick access to.
-In view mode, right-clicking uses the browser's link menu. Homarr's widget menu remains available in edit mode.
 
 ### Screenshots
 

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

@@ -1,6 +1,6 @@
 ---
 title: "Custom API"
-description: "The Custom API widget shows a Custom JSX v2 definition with server-side API requests, widget options, and actions."
+description: "Displays data from an administrator-defined HTTP API using built-in renderers or safe Custom JSX."
 hide_title: true
 ---
 
@@ -10,52 +10,30 @@ import { customApiWidget } from ".";
 
 <WidgetHeader widget={customApiWidget} categories={["Custom", "API"]} />
 
-The Custom API widget shows a Custom JSX v2 definition. Create the definition in [Management → Custom Widgets](/docs/management/custom-widgets).
-
-A definition contains API sources, named requests, a widget options schema, and one safe JSX template.
-
-Temporary inputs exist only while the tile is mounted. Homarr encrypts source credentials separately.
-
-Homarr does not send these credentials to the browser. Homarr does not include them in an export.
+The Custom API widget displays an API definition created by an administrator in [Management → Custom Widgets](/docs/management/custom-widgets). A definition owns the endpoint, credentials, display configuration, and any named network capabilities used by Custom JSX.
 
 ### Add the widget
 
 <AddingWidget />
 
-Select a definition from the searchable picker. Configure its generated widget options.
-
-Select a refresh interval. The board item stores the definition ID and the validated widget option values.
-
-Credentials remain on the server.
+Choose a custom-widget definition and a refresh interval. The board item stores only the selected definition and display options; credentials remain server-side.
 
 :::note
 
-Enable the definition before you use it. The definition must also be available to the board.
+A definition must be enabled and available to the board before it appears in the widget picker.
 
 :::
 
 ### Permissions and actions
 
-Each named request declares its minimum board permission. This permission does not depend on the HTTP method.
+The base response and named query requests require permission to view the board. Named POST, PUT, and PATCH actions require permission to modify the board by default. DELETE requires full board permission and a confirmation. Anonymous viewers cannot execute actions.
 
-Anonymous visitors can load queries from a Custom API widget on a public board. Definitions placed only on private
-boards remain unavailable to them.
-
-Queries and actions can use GET, POST, PUT, or PATCH. DELETE is valid only for actions so it can never run
-automatically while a board loads. The `kind` value controls the remaining runtime behavior.
-
-A DELETE request requires full board permission and confirmation. An anonymous viewer cannot run an action.
-
-Homarr disables interactive controls in board edit mode. An action runs only after a user action.
-
-Mounting, refresh polling, and automatic retries do not run actions. An authoring preview simulates actions by default.
-
-An administrator can enable live actions for the short preview session.
+Interactive controls are disabled while the board is in edit mode. Actions run only after an explicit user gesture and are never triggered by mounting, refresh polling, or automatic retries. Authoring previews simulate actions unless an administrator explicitly enables live actions for the short-lived preview session.
 
 ### Refresh behavior
 
-The refresh interval runs load queries again. `SubFetch` runs manual queries.
+The refresh interval applies to the base GET response. A Custom JSX query can declare its own cache duration and can be refreshed manually. Named actions can invalidate the parent response or related named queries after they succeed.
 
-Each query can declare a cache duration. A successful action can invalidate only its declared queries.
+If the definition needs a non-GET base request, migrate it to a GET base response plus a named action. Existing non-GET Custom JSX definitions require review before network access is enabled.
 
-Read [Custom Widgets management](/docs/management/custom-widgets) for authoring, widget options, named requests, Mantine, network scopes, and security limits.
+See [Custom Widgets management](/docs/management/custom-widgets) for the editor, display types, named-request manifest, network scopes, security limits, and migration guidance.

apps/docs/docs/widgets/custom-api/index.ts

@@ -4,7 +4,6 @@ import { IconApi } from "@tabler/icons-react";
 export const customApiWidget: WidgetDefinition = {
   icon: IconApi,
   name: "Custom API",
-  description:
-    "Renders an administrator-defined Custom JSX v2 widget with server-side API requests, options, and actions.",
+  description: "Displays data from a custom API endpoint using configurable display types and optional JSX templates.",
   path: "../../widgets/custom-api",
 };

apps/docs/docs/widgets/docker-containers/index.mdx

@@ -40,19 +40,13 @@ import dockerTable from "./img/table.png";
 
 ### Interactions
 
-Hover a column header to reveal its grab handle, then drag it to reorder the table or drag the header's edge to resize it. The layout is saved automatically for each widget instance and restored after a reload. These controls are disabled while the board is in edit mode.
-
-Each container row has an action menu, accessible via the three-dot icon or by right-clicking the row, with the following options:
+Each container row has an action menu (accessible via the three-dot icon) with the following options:
 
 - **View logs** - opens a dedicated terminal page streaming the container's logs
 - **Start** / **Stop** / **Restart** - manage the container's state
-- **Remove** - permanently remove the container after a second confirmation click
+- **Remove** - remove the container
 - **Add to Homarr** - create a bookmark app from the container
 
 ### Adding the widget
 
 <AddingWidget />
-
-### Configuration
-
-<WidgetConfig configuration={dockerContainersWidget.configuration} />

apps/docs/docs/widgets/docker-containers/index.ts

@@ -8,12 +8,6 @@ export const dockerContainersWidget: WidgetDefinition = {
   path: "../../widgets/docker-containers",
   configuration: {
     items: [
-      {
-        name: "Columns to show",
-        description: "Select which columns are visible in the table",
-        values: "Name, State, Host, CPU usage, Memory usage, and Actions",
-        defaultValue: "All columns",
-      },
       {
         name: "Enable items sorting",
         description: "Allows to sort containers by clicking on the column headers",

apps/docs/docs/widgets/downloads/index.mdx

@@ -4,7 +4,6 @@ description: "Allows you to view and manage your Downloads from both Torrent and
 hide_title: true
 ---
 
-import { aria2Integration } from "@site/docs/integrations/aria2";
 import { delugeIntegration } from "@site/docs/integrations/deluge";
 import { nzbgetIntegration } from "@site/docs/integrations/nzbget";
 import { qBittorentIntegration } from "@site/docs/integrations/q-bittorent";
@@ -15,41 +14,23 @@ import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
+import { IconAd } from "@tabler/icons-react";
+import TabItem from "@theme/TabItem";
+import Tabs from "@theme/Tabs";
 import { downloadsWidget } from ".";
 
 <WidgetHeader widget={downloadsWidget} categories={["Torrent client", "Usenet client", "Downloads"]} />
 
-This widget displays a list of torrents or usenet-articles that are currently being downloaded, along with their progress and other relevant information. It supports 7 download client integrations and provides a rich, responsive table interface.
+This widget displays a list of torrents or usenet-articles that are currently being downloaded, along with their progress and other relevant information.
 
 ### Screenshots
 
 import downloadsCard from "./img/screenshot.png";
-import contextMenuImg from "./img/context-menu.png";
 
 <div>
-  <img src={downloadsCard} alt="Downloads widget showing torrent and usenet items" width={128 * 4} />
+  <img src={downloadsCard} alt="downloads" width={128 * 4} />
 </div>
 
-#### Right-click context menu
-
-<div>
-  <img src={contextMenuImg} alt="Downloads widget context menu with pause, delete, and copy actions" width={128 * 4} />
-</div>
-
-### Features
-
-- **Responsive table** — columns automatically adapt to widget width, hiding less important columns at smaller sizes
-- **Sortable columns** — click any column header to sort ascending/descending
-- **Column customization** — choose which columns to display, then hover a header to reveal its grab handle for reordering or drag its edge to resize it; layouts save automatically per widget
-- **Right-click context menu** — pause, resume, delete downloads, or copy download names directly from the context menu
-- **Row expansion** — click any row to see full details inline without opening a separate modal
-- **Hover tooltips** — hover a download name to see size, speeds, ETA, ratio, and category
-- **Global stats bar** — toggle a summary bar showing queue progress, total size, speeds, ratio, and per-state counts
-- **Client filtering** — filter downloads by integration or status using the footer filter panel
-- **Global controls** — pause/resume all downloads across all clients from the footer bar
-- **Status indicators** — color-coded badges show download state at a glance
-- **Speed overview** — total download and upload speeds displayed in the footer
-
 ### Supported Integrations
 
 <WidgetIntegrations
@@ -74,26 +55,18 @@ import contextMenuImg from "./img/context-menu.png";
       integration: qBittorentIntegration,
       note: "Torrent client",
     },
-    {
-      integration: aria2Integration,
-      note: "Multi-protocol download client",
-    },
     {
       integration: slskdIntegration,
-      note: "Soulseek client (read-only)",
+      note: "Soulseek client",
     },
   ]}
 />
 
 ### Interactions
 
-- **Right-click** any download to open a context menu with pause/resume, delete, and copy actions
-- **Click** any row to expand it and see full download details inline
-- **Hover** a download name for a quick stats tooltip
-- **Stats toggle** — show or hide the global stats bar from the footer
-- **Pause / Resume** all downloads using the footer controls
-- **Filter** by integration or status using the filter button in the footer
-- **Sort** by clicking column headers (with persistent sort direction)
+- Pause / Resume one download by clicking on the according icon.
+- Delete one download by clicking on the trash icon. (Can also delete the files)
+- Pause / Resume all downloads by using the bottom button.
 
 ### Adding the widget
 

apps/docs/docs/widgets/downloads/index.ts

@@ -2,23 +2,26 @@ import { WidgetDefinition } from "@site/src/types";
 import { IconDownload } from "@tabler/icons-react";
 
 const columnsList = [
+  "id",
+  "actions",
+  "added",
+  "category",
+  "downSpeed",
+  "index",
+  "integration",
   "name",
   "progress",
-  "size",
-  "downSpeed",
-  "upSpeed",
-  "time",
-  "state",
-  "added",
   "ratio",
   "received",
   "sent",
-  "category",
-  "integration",
-  "index",
+  "size",
+  "state",
+  "time",
   "type",
+  "upSpeed",
 ];
-const sortColumns = columnsList.filter((c) => !["state", "category", "integration"].includes(c));
+const sortingExclusion = ["actions", "id", "state"];
+const columnsSort = columnsList.filter((column) => !sortingExclusion.some((exclusion) => exclusion === column));
 
 export const downloadsWidget: WidgetDefinition = {
   icon: IconDownload,
@@ -29,20 +32,25 @@ export const downloadsWidget: WidgetDefinition = {
     items: [
       {
         name: "Columns to show",
-        description:
-          "Select the columns you want to display in the widget. Columns automatically hide/show based on widget width.",
+        description: "Select the columns you want to display in the widget.",
         values: `List of columns: ${columnsList.join(", ")}`,
-        defaultValue: ["name", "progress", "downSpeed", "time", "state"].join(", "),
+        defaultValue: ["integration", "name", "progress", "time", "actions"].join(", "),
       },
       {
-        name: "Default sort column",
-        description: "The column used for initial sorting when the widget loads.",
-        defaultValue: "progress",
-        values: `List of columns: ${sortColumns.join(", ")}`,
+        name: "Enable items sorting",
+        description: "Enables the sorting in the table.",
+        values: { type: "boolean" },
+        defaultValue: "no",
+      },
+      {
+        name: "Column used for sorting by default",
+        description: "By default it will sort by this column.",
+        defaultValue: "type",
+        values: `List of columns: ${columnsSort.join(", ")}`,
       },
       {
         name: "Invert sorting",
-        description: "This will invert the default sorting order.",
+        description: "This will invert the sorting order of the table.",
         values: { type: "boolean" },
         defaultValue: "no",
       },
@@ -68,13 +76,13 @@ export const downloadsWidget: WidgetDefinition = {
         name: "Hide completed torrent under this threshold (in kiB/s)",
         description:
           "This will hide completed torrent entries that have a download speed below the specified threshold.",
-        values: "Any number above 0, 0 to disable",
+        values: "Any number above 1, 0 to disable",
         defaultValue: "0",
       },
       {
-        name: "Categories/labels to filter",
-        description: "You can filter the items by categories or labels. Use a comma to separate multiple values.",
-        values: "Comma-separated list of categories or labels",
+        name: "Categories/names to filter",
+        description: "You can filter the items by categories or names. Use a comma to separate multiple values.",
+        values: "Comma-separated list of categories or names",
         defaultValue: "-",
       },
       {
@@ -86,13 +94,13 @@ export const downloadsWidget: WidgetDefinition = {
       },
       {
         name: "Use filter to calculate Ratio",
-        description: "This will use the category filter when calculating the global torrent ratio.",
+        description: "This will use the filter to calculate the ratio of items shown in the widget.",
         values: { type: "boolean" },
         defaultValue: "yes",
       },
       {
         name: "Limit items per integration",
-        description: "This will limit the number of items shown per integration, not globally.",
+        description: "This will limit the number of items shown per integration, not globally",
         values: "Any number above 1",
         defaultValue: "50",
       },

apps/docs/docs/widgets/immich-album-carousel/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Immich Album Carousel"
-description: "Shows a slideshow of pictures from an Immich album or your full library"
+description: "Shows a slideshow of your album pictures from Immich"
 hide_title: true
 ---
 

apps/docs/docs/widgets/immich-album-carousel/index.ts

@@ -4,16 +4,15 @@ import { IconPhoto } from "@tabler/icons-react";
 export const immichAlbumCarouselWidget: WidgetDefinition = {
   icon: IconPhoto,
   name: "Immich Album",
-  description: "Shows a slideshow of pictures from an Immich album or your full library",
+  description: "Shows a slideshow of your album pictures from Immich",
   path: "../../widgets/immich-album-carousel",
   configuration: {
     items: [
       {
         name: "Album",
-        description:
-          "Select an Immich album or All photos. An empty selection also shows random photos from your full library.",
+        description: "Select the Immich album to show in the slideshow.",
         values: { type: "string" },
-        defaultValue: "All photos",
+        defaultValue: "",
       },
       {
         name: "Interval in seconds",

apps/docs/docs/widgets/media-server/index.mdx

@@ -14,7 +14,6 @@ import TabItem from "@theme/TabItem";
 import { mediaServerWidget } from ".";
 import { embyIntegration } from "@site/docs/integrations/emby";
 import { jellyfinIntegration } from "@site/docs/integrations/jellyfin";
-import { navidromeIntegration } from "@site/docs/integrations/navidrome";
 import { plexIntegration } from "@site/docs/integrations/plex";
 
 <WidgetHeader widget={mediaServerWidget} categories={["Media server"]} />
@@ -38,10 +37,6 @@ import mediaTable from "./img/table.png";
     {
       integration: jellyfinIntegration,
     },
-    {
-      integration: navidromeIntegration,
-      note: "Will always show only currently playing audio streams, not all active sessions.",
-    },
     {
       integration: plexIntegration,
       note: "Will always show only currently playing streams, not all active sessions.",

apps/docs/docs/widgets/media-server/index.ts

@@ -10,7 +10,7 @@ export const mediaServerWidget: WidgetDefinition = {
     items: [
       {
         name: "Show only currently playing",
-        description: "Plex and Navidrome always show only currently playing streams.",
+        description: "Disabling this will not work for plex.",
         values: { type: "boolean" },
         defaultValue: "yes",
       },

apps/docs/docs/widgets/smart-home-entity-state/index.mdx

@@ -43,7 +43,6 @@ import temperature from "./img/temperature.png";
 ### Interactions
 
 - Toggle entity state by clicking on the entity (only when clickable enabled).
-- After a successful toggle, the displayed state refreshes immediately.
 
 ### Adding the widget
 

apps/docs/docs/widgets/smart-home-execute-automation/index.mdx

@@ -53,6 +53,4 @@ import withDisplayname from "./img/with-displayname.png";
 
 ### Configuration
 
-Use the Home Assistant entity ID (for example, `automation.turn_on_lights`) in the **Automation ID** field, not the automation's internal ID.
-
 <WidgetConfig configuration={smartHomeExecuteAutomationWidget.configuration} />

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

@@ -1,35 +0,0 @@
----
-title: "What's Up Docker"
-description: "Displays how many watched containers have image updates available."
-hide_title: true
----
-
-import { WidgetHeader } from "@site/src/components/widgets/header";
-import { AddingWidget } from "@site/src/components/widgets/adding";
-import { WidgetConfig } from "@site/src/components/widgets/configuration";
-import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
-import { wudWidget } from ".";
-import { wudIntegration } from "@site/docs/integrations/whats-up-docker";
-
-<WidgetHeader widget={wudWidget} categories={["Health Monitoring"]} />
-
-This widget shows two stats from your WUD instance: the total number of monitored containers, and how many of them currently have an image update available. Optionally, it can also list each outdated container with its current and new version, linking to the release notes when WUD provides one.
-
-### Supported Integrations
-
-<WidgetIntegrations
-  items={[
-    {
-      integration: wudIntegration,
-      note: "Displays monitored container and available-update counts",
-    },
-  ]}
-/>
-
-### Adding the widget
-
-<AddingWidget />
-
-### Configuration
-
-<WidgetConfig configuration={wudWidget.configuration} />

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

@@ -1,38 +0,0 @@
-import { WidgetDefinition } from "@site/src/types";
-import { IconBrandDocker } from "@tabler/icons-react";
-
-export const wudWidget: WidgetDefinition = {
-  icon: IconBrandDocker,
-  name: "What's Up Docker",
-  description: "Displays how many watched containers have image updates available.",
-  path: "../../widgets/whats-up-docker",
-  configuration: {
-    items: [
-      {
-        name: "Show title",
-        description: 'Displays the icon and "What\'s Up Docker" label above the stats',
-        values: { type: "boolean" },
-        defaultValue: "yes",
-      },
-      {
-        name: "Show update ring",
-        description: "Displays a ring showing the percentage of monitored containers with a pending update",
-        values: { type: "boolean" },
-        defaultValue: "yes",
-      },
-      {
-        name: "Layout",
-        description: "Arrange the two stats side by side (Horizontal) or stacked (Vertical)",
-        values: { type: "select", options: ["Horizontal", "Vertical"] },
-        defaultValue: "Horizontal",
-      },
-      {
-        name: "Show container update list",
-        description:
-          "Lists each monitored container that has an image update available, linking to its release notes when known",
-        values: { type: "boolean" },
-        defaultValue: "no",
-      },
-    ],
-  },
-};

apps/docs/docusaurus.config.ts

@@ -1,33 +1,17 @@
 import type * as Preset from "@docusaurus/preset-classic";
 import type { Config } from "@docusaurus/types";
 import { themes as prismThemes } from "prism-react-renderer";
-import { resolveHomarrUrlConfig } from "@homarr/workshop/schema";
 const a11yEmoji = require("@fec/remark-a11y-emoji");
 
-const deprecatedWorkshopUrl = process.env.WORKSHOP_URL;
-if (deprecatedWorkshopUrl && !process.env.WORKSHOP_API_URL) {
-  console.warn("WORKSHOP_URL is deprecated; use WORKSHOP_API_URL instead.");
-}
-
-const publicUrls = resolveHomarrUrlConfig({
-  homarrWebsiteUrl: process.env.HOMARR_WEBSITE_URL,
-  workshopApiUrl: process.env.WORKSHOP_API_URL ?? deprecatedWorkshopUrl,
-  workshopWebUrl: process.env.WORKSHOP_WEB_URL,
-});
 const config: Config = {
   title: "Homarr documentation",
   tagline: "A simple yet powerful dashboard for your server.",
-  url: publicUrls.homarrWebsiteUrl,
+  url: "https://homarr.dev",
   baseUrl: "/",
   trailingSlash: undefined,
   favicon: "img/logo.png",
   organizationName: "homarr-labs",
   projectName: "homarr",
-  customFields: {
-    workshopUrl: publicUrls.workshopApiUrl,
-    workshopWebUrl: publicUrls.workshopWebUrl,
-  },
-  scripts: [{ src: "/workshop-runtime-config.js" }],
   i18n: {
     defaultLocale: "en",
     locales: ["en"],
@@ -59,6 +43,17 @@ const config: Config = {
 
   themes: ["@docusaurus/theme-mermaid"],
 
+  scripts: [
+    {
+      src: "https://widget.kapa.ai/kapa-widget.bundle.js",
+      "data-website-id": "1e4656f4-abeb-4343-bbae-1d8626f52378",
+      "data-project-name": "Homarr",
+      "data-project-color": "#2B2B2B",
+      "data-project-logo": "https://homarr.dev/img/favicon.png",
+      async: true,
+    },
+  ],
+
   presets: [
     [
       "classic",
@@ -128,30 +123,21 @@ const config: Config = {
           label: "Blog",
           position: "left",
           to: "/blog",
-          className: "navbar-item--secondary",
-        },
-        {
-          label: "Workshop",
-          position: "left",
-          to: "/workshop",
         },
         {
           label: "About us",
           position: "left",
           to: "/about-us",
-          className: "navbar-item--collapse-first",
         },
         {
           to: "https://demo.homarr.dev/",
           label: "Demo",
           position: "right",
-          className: "navbar-item--secondary",
         },
         {
           to: "https://opencollective.com/homarr",
           label: "💴 Donate",
           position: "right",
-          className: "navbar-item--collapse-first",
         },
         {
           type: "dropdown",
@@ -250,19 +236,11 @@ const config: Config = {
         },
       ],
       logo: {
-        alt: "Homarr home",
-        src: "img/logo.svg",
-        href: "/",
-        width: 86,
-        height: 58,
+        alt: "Homarr Logo",
+        src: "img/logo.png",
+        height: 100,
       },
-      copyright: `
-        <div class="footer__brand-copy">
-          <strong class="footer__brand-name">Homarr</strong>
-          <span class="footer__brand-tagline">Your dashboard for the services you run.</span>
-          <span class="copyright_text">© ${new Date().getFullYear()} Homarr · <a href="/docs/community/license">License</a></span>
-        </div>
-      `,
+      copyright: `<span class="copyright_text">Copyright © ${new Date().getFullYear()} Homarr<span> — <a href="/docs/community/license">License</a>`,
     },
     prism: {
       theme: prismThemes.github,
@@ -299,22 +277,8 @@ const config: Config = {
     function homarrPackagesPlugin() {
       return {
         name: "resolve-homarr-packages",
-        configureWebpack(_config, isServer, { getJSLoader }) {
-          return {
-            resolve: {
-              symlinks: false,
-              alias: { "@": require("path").resolve(__dirname, "src") },
-            },
-            module: {
-              rules: [
-                {
-                  test: /\.[jt]sx?$/iu,
-                  include: /node_modules[\\/]@homarr/u,
-                  use: [getJSLoader({ isServer })],
-                },
-              ],
-            },
-          };
+        configureWebpack() {
+          return { resolve: { symlinks: false } };
         },
       };
     },
@@ -345,68 +309,7 @@ const config: Config = {
         },
       };
     },
-    function workshopRoutesPlugin() {
-      return {
-        name: "workshop-routes",
-        injectHtmlTags() {
-          return {
-            headTags: [
-              {
-                tagName: "style",
-                innerHTML: `
-#workshop-detail-route-fallback { display: none; }
-html[data-workshop-detail-loading] #__docusaurus { display: none; }
-html[data-workshop-detail-loading] #workshop-detail-route-fallback {
-  align-items: center;
-  background: #fff;
-  box-sizing: border-box;
-  color: #4b5563;
-  display: flex;
-  font: 500 0.875rem/1.5 Inter, system-ui, sans-serif;
-  justify-content: center;
-  min-height: 100vh;
-  padding: 2rem;
-}
-@media (prefers-color-scheme: dark) {
-  html[data-workshop-detail-loading] #workshop-detail-route-fallback {
-    background: #18191a;
-    color: #d1d5db;
-  }
-}`,
-              },
-              {
-                tagName: "script",
-                innerHTML: `(function () {
-  var match = window.location.pathname.match(/^\\/workshop\\/([^/]+)\\/?$/);
-  if (match && match[1] !== "admin") {
-    document.documentElement.setAttribute("data-workshop-detail-loading", "");
-  }
-})();`,
-              },
-            ],
-            preBodyTags: [
-              {
-                tagName: "div",
-                attributes: {
-                  id: "workshop-detail-route-fallback",
-                  role: "status",
-                  "aria-live": "polite",
-                },
-                innerHTML: "Loading Workshop…",
-              },
-            ],
-          };
-        },
-        async contentLoaded({ actions }) {
-          actions.addRoute({
-            path: "/workshop/:id",
-            component: "@site/src/components/workshop/WorkshopDetailRoutePage",
-            exact: true,
-            priority: -1,
-          });
-        },
-      };
-    },
+    "@signalwire/docusaurus-plugin-llms-txt",
     async function tailwindCssPlugin() {
       return {
         name: "docusaurus-tailwindcss",

apps/docs/package.json

@@ -21,45 +21,29 @@
     "verify:search": "node ./scripts/verify-algolia-search.mjs"
   },
   "dependencies": {
-    "@base-ui/react": "^1.5.0",
     "@docusaurus/core": "^3.10.1",
     "@docusaurus/faster": "^3.10.1",
     "@docusaurus/plugin-content-docs": "^3.10.1",
     "@docusaurus/plugin-sitemap": "^3.10.1",
     "@docusaurus/preset-classic": "^3.10.1",
-    "@homarr/custom-widgets": "workspace:^",
     "@homarr/definitions": "workspace:^",
-    "@homarr/workshop": "workspace:^",
-    "@mantine/core": "catalog:",
     "@mdx-js/react": "^3.1.1",
     "@nivo/line": "^0.99.0",
     "@scalar/api-reference-react": "catalog:",
-    "@shadcn/react": "catalog:",
+    "@signalwire/docusaurus-plugin-llms-txt": "^1.2.2",
     "@tabler/icons-react": "catalog:",
     "@tailwindcss/postcss": "^4.3.2",
-    "class-variance-authority": "^0.7.1",
     "clsx": "catalog:",
-    "cmdk": "catalog:",
-    "date-fns": "catalog:",
     "dayjs": "catalog:",
     "docusaurus-plugin-image-zoom": "^3.0.1",
-    "embla-carousel-react": "catalog:",
-    "input-otp": "catalog:",
     "leader-line-new": "^1.1.9",
-    "next-themes": "catalog:",
-    "pocketbase": "catalog:",
     "postcss": "^8.5.16",
     "posthog-docusaurus": "^2.0.5",
     "prism-react-renderer": "^2.4.1",
     "random-word-slugs": "^0.1.7",
     "react": "catalog:",
-    "react-day-picker": "catalog:",
     "react-dom": "catalog:",
-    "react-resizable-panels": "catalog:",
-    "recharts": "3.8.0",
-    "sonner": "catalog:",
     "swiper": "^14.0.5",
-    "tailwind-merge": "^3.6.0",
     "tailwindcss": "^4.3.2"
   },
   "devDependencies": {

apps/docs/src/components/custom-jsx-component-reference.module.css

@@ -1,451 +0,0 @@
-.explorer {
-  --catalog-border: color-mix(in srgb, var(--ifm-color-emphasis-500) 42%, transparent);
-  --catalog-surface: color-mix(in srgb, var(--ifm-background-surface-color) 90%, var(--ifm-color-primary) 10%);
-  border: 1px solid var(--catalog-border);
-  border-radius: 18px;
-  margin: 1.5rem 0 2rem;
-  overflow: hidden;
-}
-
-.header {
-  align-items: flex-start;
-  background: linear-gradient(135deg, color-mix(in srgb, var(--ifm-color-primary) 13%, transparent), transparent 65%);
-  display: flex;
-  gap: 1.5rem;
-  justify-content: space-between;
-  padding: 1.4rem;
-}
-
-.eyebrow {
-  color: var(--ifm-color-primary);
-  font-size: 0.72rem;
-  font-weight: 750;
-  letter-spacing: 0.09em;
-  margin: 0 0 0.35rem;
-  text-transform: uppercase;
-}
-
-.title {
-  font-size: clamp(1.25rem, 3vw, 1.65rem);
-  margin: 0;
-}
-
-.summary {
-  color: var(--ifm-color-emphasis-700);
-  margin: 0.45rem 0 0;
-  max-width: 68ch;
-}
-
-.rawLink,
-.expandButton,
-.showMoreButton,
-.resetButton {
-  align-items: center;
-  border-radius: 9px;
-  cursor: pointer;
-  display: inline-flex;
-  font: inherit;
-  font-weight: 650;
-  justify-content: center;
-}
-
-.rawLink,
-.expandButton,
-.showMoreButton {
-  background: var(--ifm-color-primary);
-  border: 1px solid var(--ifm-color-primary);
-  color: var(--ifm-color-white);
-  padding: 0.58rem 0.85rem;
-  text-decoration: none;
-}
-
-.rawLink {
-  flex: 0 0 auto;
-  white-space: nowrap;
-}
-
-.rawLink:hover,
-.expandButton:hover,
-.showMoreButton:hover {
-  background: var(--ifm-color-primary-dark);
-  color: var(--ifm-color-white);
-  text-decoration: none;
-}
-
-.versions {
-  border-bottom: 1px solid var(--catalog-border);
-  border-top: 1px solid var(--catalog-border);
-  display: grid;
-  grid-template-columns: repeat(4, minmax(0, 1fr));
-  margin: 0;
-}
-
-.globalProps {
-  align-items: center;
-  border-bottom: 1px solid var(--catalog-border);
-  display: grid;
-  gap: 1rem;
-  grid-template-columns: minmax(0, 1fr) auto;
-  padding: 1rem 1.4rem;
-  scroll-margin-top: calc(var(--ifm-navbar-height) + 1rem);
-}
-
-.globalProps h4,
-.globalProps p {
-  margin: 0;
-}
-
-.globalProps p {
-  color: var(--ifm-color-emphasis-700);
-  font-size: 0.86rem;
-  margin-top: 0.2rem;
-}
-
-.globalPropsTable {
-  grid-column: 1 / -1;
-}
-
-.versions div {
-  padding: 0.75rem 1.4rem;
-}
-
-.versions div + div {
-  border-left: 1px solid var(--catalog-border);
-}
-
-.versions dt {
-  color: var(--ifm-color-emphasis-700);
-  font-size: 0.72rem;
-  font-weight: 650;
-  text-transform: uppercase;
-}
-
-.versions dd {
-  font-family: var(--ifm-font-family-monospace);
-  font-size: 0.86rem;
-  margin: 0.12rem 0 0;
-}
-
-.filters {
-  align-items: end;
-  background: var(--catalog-surface);
-  display: grid;
-  gap: 0.8rem;
-  grid-template-columns: minmax(220px, 2fr) repeat(3, minmax(130px, 1fr));
-  padding: 1.15rem 1.4rem;
-}
-
-.filters label:not(.checkboxField) {
-  display: grid;
-  gap: 0.3rem;
-}
-
-.filters label > span {
-  color: var(--ifm-color-emphasis-700);
-  font-size: 0.76rem;
-  font-weight: 700;
-}
-
-.filters input[type="search"],
-.filters select {
-  background: var(--ifm-background-color);
-  border: 1px solid var(--catalog-border);
-  border-radius: 9px;
-  color: var(--ifm-font-color-base);
-  font: inherit;
-  min-height: 42px;
-  padding: 0.55rem 0.68rem;
-  width: 100%;
-}
-
-.filters input:focus-visible,
-.filters select:focus-visible,
-.expandButton:focus-visible,
-.showMoreButton:focus-visible,
-.resetButton:focus-visible,
-.anchorLink:focus-visible {
-  outline: 3px solid color-mix(in srgb, var(--ifm-color-primary) 45%, transparent);
-  outline-offset: 2px;
-}
-
-.checkboxField {
-  align-items: center;
-  display: flex;
-  gap: 0.5rem;
-  grid-column: 1 / -1;
-}
-
-.checkboxField input {
-  height: 1rem;
-  margin: 0;
-  width: 1rem;
-}
-
-.resultSummary {
-  align-items: center;
-  border-bottom: 1px solid var(--catalog-border);
-  display: flex;
-  gap: 0.6rem;
-  min-height: 48px;
-  padding: 0.7rem 1.4rem;
-}
-
-.resetButton {
-  background: transparent;
-  border: 0;
-  color: var(--ifm-color-primary);
-  margin-left: auto;
-  padding: 0.35rem;
-}
-
-.componentList {
-  display: grid;
-}
-
-.componentCard {
-  scroll-margin-top: calc(var(--ifm-navbar-height) + 1rem);
-}
-
-.componentCard + .componentCard {
-  border-top: 1px solid var(--catalog-border);
-}
-
-.componentHeading {
-  align-items: center;
-  display: flex;
-  gap: 1rem;
-  justify-content: space-between;
-  padding: 1rem 1.4rem;
-}
-
-.componentNameRow {
-  align-items: baseline;
-  display: flex;
-  gap: 0.45rem;
-}
-
-.componentNameRow h4 {
-  font-family: var(--ifm-font-family-monospace);
-  font-size: 1.05rem;
-  margin: 0;
-}
-
-.anchorLink {
-  font-weight: 700;
-  opacity: 0;
-  text-decoration: none;
-}
-
-.componentCard:hover .anchorLink,
-.anchorLink:focus-visible {
-  opacity: 1;
-}
-
-.badges {
-  display: flex;
-  flex-wrap: wrap;
-  gap: 0.38rem;
-  margin-top: 0.45rem;
-}
-
-.badges span {
-  background: var(--ifm-color-emphasis-200);
-  border-radius: 999px;
-  color: var(--ifm-color-emphasis-800);
-  font-size: 0.7rem;
-  padding: 0.2rem 0.48rem;
-}
-
-.badges span[data-safety="allowed"] {
-  background: color-mix(in srgb, #2f9e44 18%, transparent);
-  color: color-mix(in srgb, #2f9e44 78%, var(--ifm-font-color-base));
-}
-
-.badges span[data-safety="wrapped"] {
-  background: color-mix(in srgb, var(--ifm-color-primary) 18%, transparent);
-  color: var(--ifm-color-primary-darkest);
-}
-
-.badges span[data-safety="denied"] {
-  background: color-mix(in srgb, #e03131 18%, transparent);
-  color: color-mix(in srgb, #e03131 78%, var(--ifm-font-color-base));
-}
-
-.expandButton {
-  background: transparent;
-  color: var(--ifm-color-primary);
-  flex: 0 0 auto;
-  padding: 0.42rem 0.7rem;
-}
-
-.expandButton:hover {
-  background: color-mix(in srgb, var(--ifm-color-primary) 12%, transparent);
-  color: var(--ifm-color-primary-dark);
-}
-
-.description,
-.deniedReason {
-  color: var(--ifm-color-emphasis-700);
-  margin: -0.45rem 1.4rem 1rem;
-}
-
-.deniedReason {
-  color: #c92a2a;
-}
-
-.details {
-  background: var(--catalog-surface);
-  border-top: 1px solid var(--catalog-border);
-  padding: 1.25rem 1.4rem;
-}
-
-.details h5 {
-  font-size: 0.9rem;
-  margin: 0 0 0.6rem;
-}
-
-.detailsGrid {
-  display: grid;
-  gap: 1rem;
-  grid-template-columns: minmax(0, 1.15fr) minmax(0, 0.85fr);
-  margin-bottom: 1.2rem;
-}
-
-.detailsGrid > section {
-  background: var(--ifm-background-color);
-  border: 1px solid var(--catalog-border);
-  border-radius: 12px;
-  min-width: 0;
-  padding: 0.9rem;
-}
-
-.detailsGrid p:last-of-type {
-  margin-bottom: 0.6rem;
-}
-
-.a11yList {
-  font-size: 0.86rem;
-  margin: 0 0 0.7rem;
-  padding-left: 1.1rem;
-}
-
-.tableScroll {
-  border: 1px solid var(--catalog-border);
-  border-radius: 10px;
-  max-height: 480px;
-  overflow: auto;
-}
-
-.propsTable {
-  display: table;
-  font-size: 0.78rem;
-  margin: 0;
-  width: 100%;
-}
-
-.propsTable th {
-  background: var(--ifm-background-color);
-  position: sticky;
-  top: 0;
-  z-index: 1;
-}
-
-.propsTable th,
-.propsTable td {
-  min-width: 96px;
-  padding: 0.58rem;
-  vertical-align: top;
-}
-
-.propsTable td:nth-child(2) {
-  max-width: 340px;
-  min-width: 190px;
-}
-
-.type {
-  overflow-wrap: anywhere;
-  white-space: normal;
-}
-
-.muted {
-  color: var(--ifm-color-emphasis-600);
-}
-
-.rawComponent {
-  margin-top: 1rem;
-}
-
-.rawComponent summary {
-  color: var(--ifm-color-primary);
-  cursor: pointer;
-  font-weight: 650;
-}
-
-.rawComponent > div {
-  margin-top: 0.6rem;
-}
-
-.showMoreButton {
-  display: flex;
-  margin: 1.1rem auto;
-}
-
-.loading,
-.error,
-.empty {
-  background: var(--ifm-background-surface-color);
-  border: 1px solid var(--ifm-color-emphasis-300);
-  border-radius: 12px;
-  margin: 1rem 0;
-  padding: 1rem;
-}
-
-.empty {
-  border: 0;
-  margin: 0;
-  text-align: center;
-}
-
-.error {
-  border-color: color-mix(in srgb, #e03131 58%, transparent);
-}
-
-@media (max-width: 996px) {
-  .filters {
-    grid-template-columns: repeat(2, minmax(0, 1fr));
-  }
-
-  .searchField {
-    grid-column: 1 / -1;
-  }
-}
-
-@media (max-width: 650px) {
-  .header,
-  .componentHeading {
-    align-items: stretch;
-    flex-direction: column;
-  }
-
-  .rawLink,
-  .expandButton {
-    align-self: flex-start;
-  }
-
-  .versions,
-  .filters,
-  .detailsGrid,
-  .globalProps {
-    grid-template-columns: 1fr;
-  }
-
-  .versions div + div {
-    border-left: 0;
-    border-top: 1px solid var(--catalog-border);
-  }
-
-  .searchField,
-  .checkboxField {
-    grid-column: auto;
-  }
-}

apps/docs/src/components/custom-jsx-component-reference.tsx

@@ -1,497 +1,66 @@
-import BrowserOnly from "@docusaurus/BrowserOnly";
-import useBaseUrl from "@docusaurus/useBaseUrl";
-import { useEffect, useMemo, useState } from "react";
+import React from "react";
 
-import { buildCustomJsxComponentUsageExample } from "@homarr/custom-widgets/catalog-example";
-import type {
-  CustomJsxAuthoringCatalog,
-  CustomJsxComponentApi,
-  CustomJsxPropDescriptor,
-} from "@homarr/custom-widgets/catalog";
+import customJsxComponentRegistry from "../generated/custom-jsx-components.json";
 
-import { CustomWidgetCodeExample } from "./custom-widget-code";
-import styles from "./custom-jsx-component-reference.module.css";
-
-type ComponentCatalog = CustomJsxAuthoringCatalog;
-type CatalogComponent = CustomJsxComponentApi;
-type CatalogProp = CustomJsxPropDescriptor;
-
-const PAGE_SIZE = 40;
+const enabledComponents = customJsxComponentRegistry.filter((component) => component.safety !== "denied");
+const deniedComponents = customJsxComponentRegistry.filter((component) => component.safety === "denied");
+const categories = [...new Set(enabledComponents.map((component) => component.category))];
 
 export function CustomJsxComponentReference() {
   return (
-    <BrowserOnly fallback={<ComponentReferenceFallback />}>{() => <CustomJsxComponentReferenceClient />}</BrowserOnly>
-  );
-}
-
-function ComponentReferenceFallback() {
-  return (
-    <div className={styles.loading} aria-busy="true">
-      Loading the Custom JSX component catalog…
-    </div>
-  );
-}
-
-function CustomJsxComponentReferenceClient() {
-  const catalogUrl = useBaseUrl("/custom-widgets/component-catalog-v1.json");
-  const [catalog, setCatalog] = useState<ComponentCatalog | null>(null);
-  const [loadError, setLoadError] = useState<string | null>(null);
-  const [query, setQuery] = useState("");
-  const [packageFilter, setPackageFilter] = useState("all");
-  const [categoryFilter, setCategoryFilter] = useState("all");
-  const [safetyFilter, setSafetyFilter] = useState("available");
-  const [bindableOnly, setBindableOnly] = useState(false);
-  const [visibleCount, setVisibleCount] = useState(PAGE_SIZE);
-  const [expanded, setExpanded] = useState<ReadonlySet<string>>(() => new Set());
-  const [showGlobalProps, setShowGlobalProps] = useState(false);
-
-  useEffect(() => {
-    const controller = new AbortController();
-    setLoadError(null);
-
-    void fetch(catalogUrl, { signal: controller.signal })
-      .then(async (response) => {
-        if (!response.ok) throw new Error(`The catalog request returned HTTP ${response.status}.`);
-        return (await response.json()) as ComponentCatalog;
-      })
-      .then((value) => {
-        if (!Array.isArray(value.components) || !Array.isArray(value.types) || !Array.isArray(value.globalProps)) {
-          throw new Error("The catalog response has an unsupported shape.");
-        }
-        setCatalog(value);
-      })
-      .catch((error: unknown) => {
-        if (controller.signal.aborted) return;
-        setLoadError(error instanceof Error ? error.message : "The component catalog could not be loaded.");
-      });
-
-    return () => controller.abort();
-  }, [catalogUrl]);
-
-  const categories = useMemo(
-    () => [...new Set(catalog?.components.map((component) => component.category) ?? [])].sort(),
-    [catalog],
-  );
-  const packages = useMemo(
-    () => [...new Set(catalog?.components.map((component) => component.package) ?? [])].sort(),
-    [catalog],
-  );
-  const filteredComponents = useMemo(() => {
-    if (!catalog) return [];
-    const normalizedQuery = query.trim().toLocaleLowerCase();
-    return catalog.components.filter((component) => {
-      if (packageFilter !== "all" && component.package !== packageFilter) return false;
-      if (categoryFilter !== "all" && component.category !== categoryFilter) return false;
-      if (safetyFilter === "available" && component.safety === "denied") return false;
-      if (safetyFilter !== "all" && safetyFilter !== "available" && component.safety !== safetyFilter) return false;
-      if (bindableOnly && !component.bind) return false;
-      if (!normalizedQuery) return true;
-
-      return [
-        component.name,
-        component.package,
-        component.category,
-        component.description,
-        component.deniedReason,
-        ...component.subcomponents,
-        ...component.props.map((prop) => prop.name),
-      ].some((value) => value?.toLocaleLowerCase().includes(normalizedQuery));
-    });
-  }, [bindableOnly, catalog, categoryFilter, packageFilter, query, safetyFilter]);
-  const visibleComponents = filteredComponents.slice(0, visibleCount);
-
-  useEffect(() => {
-    setVisibleCount(PAGE_SIZE);
-  }, [bindableOnly, categoryFilter, packageFilter, query, safetyFilter]);
-
-  useEffect(() => {
-    if (!catalog) return;
-
-    const revealHashTarget = () => {
-      const hash = decodeLocationHash(window.location.hash);
-      const component = catalog.components.find((entry) => componentAnchor(entry.name) === hash);
-      if (!component) return;
-
-      if (!document.getElementById(hash)) {
-        setQuery(component.name);
-        setPackageFilter("all");
-        setCategoryFilter("all");
-        setSafetyFilter(component.safety === "denied" ? "all" : "available");
-        setBindableOnly(false);
-        setVisibleCount(PAGE_SIZE);
-      }
-      setExpanded((current) => new Set([...current, component.name]));
-      window.requestAnimationFrame(() => {
-        window.requestAnimationFrame(() => document.getElementById(hash)?.scrollIntoView({ block: "start" }));
-      });
-    };
-
-    revealHashTarget();
-    window.addEventListener("hashchange", revealHashTarget);
-    return () => window.removeEventListener("hashchange", revealHashTarget);
-  }, [catalog]);
-
-  if (loadError) {
-    return (
-      <div className={styles.error} role="alert">
-        <strong>Component catalog unavailable.</strong> {loadError} <a href={catalogUrl}>Open the raw catalog</a> to
-        inspect the generated data directly.
-      </div>
-    );
-  }
-
-  if (!catalog) return <ComponentReferenceFallback />;
-
-  return (
-    <section className={styles.explorer} aria-label="Custom JSX component catalog">
-      <header className={styles.header}>
-        <div>
-          <p className={styles.eyebrow}>Release-matched static catalog</p>
-          <h3 className={styles.title}>Explore {catalog.components.length} Custom JSX components</h3>
-          <p className={styles.summary}>
-            This browser reads the same versioned JSON artifact used by offline authoring. It never imports or executes
-            the listed component objects.
-          </p>
-        </div>
-        <a className={styles.rawLink} href={catalogUrl} target="_blank" rel="noreferrer">
-          Open raw JSON
-        </a>
-      </header>
-
-      <dl className={styles.versions}>
-        <div>
-          <dt>Catalog schema</dt>
-          <dd>v{catalog.schemaVersion}</dd>
-        </div>
-        <div>
-          <dt>Custom Widget</dt>
-          <dd>{catalog.customWidgetVersion}</dd>
-        </div>
-        <div>
-          <dt>Mantine</dt>
-          <dd>{catalog.mantineVersion}</dd>
-        </div>
-        <div>
-          <dt>Blocked capabilities</dt>
-          <dd>{catalog.blockedCapabilities.length}</dd>
-        </div>
-      </dl>
-
-      <section className={styles.globalProps} id="custom-jsx-global-props">
-        <div>
-          <h4>Shared serializable props</h4>
-          <p>
-            Every available component also receives these {catalog.globalProps.length} generated global, ARIA, data, and
-            safe style props. Component cards below list only their component-specific additions.
-          </p>
-        </div>
-        <button
-          type="button"
-          className={styles.expandButton}
-          aria-expanded={showGlobalProps}
-          aria-controls="custom-jsx-global-props-table"
-          onClick={() => setShowGlobalProps((current) => !current)}
-        >
-          {showGlobalProps ? "Hide global props" : "View global props"}
-        </button>
-        {showGlobalProps && (
-          <div className={styles.globalPropsTable} id="custom-jsx-global-props-table">
-            <PropTable props={catalog.globalProps} types={catalog.types} />
-          </div>
-        )}
-      </section>
-
-      <div className={styles.filters}>
-        <label className={styles.searchField}>
-          <span>Search names, props, and subcomponents</span>
-          <input
-            type="search"
-            value={query}
-            onChange={(event) => setQuery(event.currentTarget.value)}
-            placeholder="For example: TextInput, bind, chart…"
-          />
-        </label>
-        <label>
-          <span>Package</span>
-          <select value={packageFilter} onChange={(event) => setPackageFilter(event.currentTarget.value)}>
-            <option value="all">All packages</option>
-            {packages.map((packageName) => (
-              <option key={packageName} value={packageName}>
-                {packageName}
-              </option>
-            ))}
-          </select>
-        </label>
-        <label>
-          <span>Category</span>
-          <select value={categoryFilter} onChange={(event) => setCategoryFilter(event.currentTarget.value)}>
-            <option value="all">All categories</option>
-            {categories.map((category) => (
-              <option key={category} value={category}>
-                {humanize(category)}
-              </option>
-            ))}
-          </select>
-        </label>
-        <label>
-          <span>Availability</span>
-          <select value={safetyFilter} onChange={(event) => setSafetyFilter(event.currentTarget.value)}>
-            <option value="available">Available only</option>
-            <option value="all">Available and denied</option>
-            <option value="allowed">Allowed only</option>
-            <option value="wrapped">Wrapped only</option>
-            <option value="denied">Denied only</option>
-          </select>
-        </label>
-        <label className={styles.checkboxField}>
-          <input
-            type="checkbox"
-            checked={bindableOnly}
-            onChange={(event) => setBindableOnly(event.currentTarget.checked)}
-          />
-          Supports temporary <code>bind</code>
-        </label>
-      </div>
-
-      <div className={styles.resultSummary} aria-live="polite">
-        <strong>{filteredComponents.length}</strong> matching component{filteredComponents.length === 1 ? "" : "s"}
-        {(query ||
-          packageFilter !== "all" ||
-          categoryFilter !== "all" ||
-          safetyFilter !== "available" ||
-          bindableOnly) && (
-          <button
-            type="button"
-            className={styles.resetButton}
-            onClick={() => {
-              setQuery("");
-              setPackageFilter("all");
-              setCategoryFilter("all");
-              setSafetyFilter("available");
-              setBindableOnly(false);
-            }}
-          >
-            Reset filters
-          </button>
-        )}
-      </div>
-
-      {filteredComponents.length === 0 ? (
-        <div className={styles.empty}>No component matches these filters.</div>
-      ) : (
-        <div className={styles.componentList}>
-          {visibleComponents.map((component) => {
-            const isExpanded = expanded.has(component.name);
-            return (
-              <article className={styles.componentCard} id={componentAnchor(component.name)} key={component.name}>
-                <div className={styles.componentHeading}>
-                  <div>
-                    <div className={styles.componentNameRow}>
-                      <h4>{component.name}</h4>
-                      <a
-                        className={styles.anchorLink}
-                        href={`#${componentAnchor(component.name)}`}
-                        aria-label={`Link to ${component.name}`}
-                      >
-                        #
-                      </a>
-                    </div>
-                    <div className={styles.badges}>
-                      <span>{component.package}</span>
-                      <span>{humanize(component.category)}</span>
-                      <span data-safety={component.safety}>{component.safety}</span>
-                      {component.bind && <span>bind: {component.bind.type}</span>}
-                    </div>
-                  </div>
-                  <button
-                    type="button"
-                    className={styles.expandButton}
-                    aria-expanded={isExpanded}
-                    aria-controls={`${componentAnchor(component.name)}-details`}
-                    onClick={() => {
-                      setExpanded((current) => {
-                        const next = new Set(current);
-                        if (next.has(component.name)) next.delete(component.name);
-                        else next.add(component.name);
-                        return next;
-                      });
-                    }}
-                  >
-                    {isExpanded ? "Hide API" : "View API"}
-                  </button>
-                </div>
-                {(component.description || component.deniedReason) && (
-                  <p className={component.safety === "denied" ? styles.deniedReason : styles.description}>
-                    {component.deniedReason ?? component.description}
-                  </p>
-                )}
-
-                {isExpanded && (
-                  <ComponentDetails
-                    id={`${componentAnchor(component.name)}-details`}
-                    component={component}
-                    types={catalog.types}
-                  />
-                )}
-              </article>
-            );
-          })}
-        </div>
-      )}
-
-      {visibleCount < filteredComponents.length && (
-        <button
-          type="button"
-          className={styles.showMoreButton}
-          onClick={() => setVisibleCount((current) => current + PAGE_SIZE)}
-        >
-          Show {Math.min(PAGE_SIZE, filteredComponents.length - visibleCount)} more
-        </button>
-      )}
-    </section>
-  );
-}
-
-function decodeLocationHash(hash: string) {
-  const value = hash.slice(1);
-  try {
-    return decodeURIComponent(value);
-  } catch {
-    return value;
-  }
-}
-
-function ComponentDetails({ id, component, types }: { id: string; component: CatalogComponent; types: string[] }) {
-  return (
-    <div className={styles.details} id={id}>
-      <div className={styles.detailsGrid}>
-        <section>
-          <CustomWidgetCodeExample
-            id={`${componentAnchor(component.name)}-usage`}
-            label="Usage example"
-            language="jsx"
-            code={buildCustomJsxComponentUsageExample(component, { types })}
-            height="180px"
-          />
-        </section>
-
-        <section>
-          <h5>Component contract</h5>
-          {component.bind ? (
-            <p>
-              <code>bind</code> stores a temporary <code>{component.bind.type}</code> input. Initialize it with{" "}
-              <code>{component.bind.initialProp}</code>.
-            </p>
-          ) : (
-            <p>This component does not expose a temporary-input adapter.</p>
-          )}
-          {component.subcomponents.length > 0 && (
-            <p>
-              <strong>Subcomponents:</strong>{" "}
-              {component.subcomponents.map((name, index) => (
-                <span key={name}>
-                  {index > 0 && ", "}
-                  <code>{name}</code>
-                </span>
-              ))}
-            </p>
-          )}
-          {component.blockedProps.length > 0 && (
-            <ul className={styles.a11yList}>
-              {component.blockedProps.map((prop) => (
-                <li key={prop.name}>
-                  <code>{prop.name}</code> is blocked: {prop.reason}
-                </li>
-              ))}
-            </ul>
-          )}
-          {component.accessibilityRequirements.length > 0 && (
-            <ul className={styles.a11yList}>
-              {component.accessibilityRequirements.map((requirement) => (
-                <li key={requirement}>{requirement}</li>
-              ))}
-            </ul>
-          )}
-          <a href={component.documentationUrl} target="_blank" rel="noreferrer">
-            Open upstream documentation
-          </a>
-        </section>
-      </div>
-
-      <section>
-        <h5>
-          Component props <span className={styles.muted}>({component.props.length})</span>
-        </h5>
-        {component.props.length === 0 ? (
-          <p>No component-specific props are exposed.</p>
-        ) : (
-          <PropTable props={component.props} types={types} />
-        )}
-      </section>
-
-      <details className={styles.rawComponent}>
-        <summary>Raw component JSON</summary>
-        <CustomWidgetCodeExample
-          id={`${componentAnchor(component.name)}-json`}
-          label="Component JSON"
-          code={JSON.stringify(component, null, 2)}
-          height="320px"
-        />
-      </details>
-    </div>
-  );
-}
-
-function PropTable({ props, types }: { props: CatalogProp[]; types: string[] }) {
-  return (
-    <div className={styles.tableScroll}>
-      <table className={styles.propsTable}>
+    <>
+      <h3>Enabled and wrapped components</h3>
+      <table>
         <thead>
           <tr>
-            <th>Prop</th>
-            <th>Type</th>
-            <th>Required</th>
-            <th>Known values</th>
-            <th>Description</th>
+            <th>Category</th>
+            <th>Components</th>
           </tr>
         </thead>
         <tbody>
-          {props.map((prop) => (
-            <tr key={prop.name}>
+          {categories.map((category) => (
+            <tr key={category}>
               <td>
-                <code>{prop.name}</code>
+                <code>{category}</code>
               </td>
               <td>
-                <code className={styles.type}>{types[prop.typeRef] ?? "unknown"}</code>
+                {enabledComponents
+                  .filter((component) => component.category === category)
+                  .map((component) => (
+                    <span key={component.name} style={{ display: "inline-block", margin: "0 0.5rem 0.35rem 0" }}>
+                      <a href={component.documentationUrl}>
+                        <code>{component.name}</code>
+                      </a>
+                      {component.safety === "wrapped" && <small> (wrapped)</small>}
+                    </span>
+                  ))}
               </td>
-              <td>{prop.required ? <strong>Yes</strong> : "No"}</td>
-              <td>
-                {prop.literalValues?.length ? (
-                  <code>{prop.literalValues.map(formatLiteral).join(" | ")}</code>
-                ) : (
-                  <span className={styles.muted}>—</span>
-                )}
-              </td>
-              <td>{prop.description ?? <span className={styles.muted}>—</span>}</td>
             </tr>
           ))}
         </tbody>
       </table>
-    </div>
+
+      <h3>Denied components</h3>
+      <table>
+        <thead>
+          <tr>
+            <th>Component</th>
+            <th>Reason</th>
+          </tr>
+        </thead>
+        <tbody>
+          {deniedComponents.map((component) => (
+            <tr key={component.name}>
+              <td>
+                <a href={component.documentationUrl} aria-label={component.name}>
+                  <code>{component.name}</code>
+                </a>
+              </td>
+              <td>{component.reason}</td>
+            </tr>
+          ))}
+        </tbody>
+      </table>
+    </>
   );
 }
-
-function componentAnchor(name: string) {
-  return `custom-jsx-component-${name
-    .replaceAll(".", "-")
-    .replace(/([a-z0-9])([A-Z])/g, "$1-$2")
-    .toLowerCase()}`;
-}
-
-function humanize(value: string) {
-  return value.replaceAll("-", " ").replace(/\b\w/g, (character) => character.toUpperCase());
-}
-
-function formatLiteral(value: string | number | boolean | null) {
-  return typeof value === "string" ? JSON.stringify(value) : String(value);
-}

apps/docs/src/components/custom-widget-code-client.tsx

@@ -1,114 +0,0 @@
-import { useState } from "react";
-import { useColorMode } from "@docusaurus/theme-common";
-import { MantineProvider, Select, Stack, Text } from "@mantine/core";
-/* oxlint-disable import/no-unassigned-import -- Mantine component styles intentionally load for side effects. */
-import "@mantine/core/styles.layer.css";
-/* oxlint-enable import/no-unassigned-import */
-
-import {
-  BUNDLED_CUSTOM_WIDGETS,
-  CUSTOM_WIDGET_OPTIONS_EXAMPLES,
-  CUSTOM_WIDGET_REQUEST_EXAMPLES,
-} from "@homarr/custom-widgets/core";
-import type { CustomWidgetEditorMessages } from "@homarr/custom-widgets/workbench";
-import { CustomWidgetCodeEditor, ReadOnlyCustomWidgetCode } from "@homarr/custom-widgets/workbench";
-
-import type {
-  CanonicalCustomWidgetExampleProps,
-  CustomWidgetCodeExampleProps,
-  CustomWidgetCodeInputProps,
-} from "./custom-widget-code";
-
-const messages: CustomWidgetEditorMessages = {
-  languageJsx: "JSX",
-  languageJson: "JSON",
-  undo: "Undo",
-  redo: "Redo",
-  components: "Components",
-  componentSearch: "Search components",
-  componentEmpty: "No matching components",
-  componentCount: (count) => `${count} components`,
-  insertStarter: "Insert starter",
-  format: "Format",
-  copy: "Copy",
-  copied: "Copied",
-  schema: "Schema",
-  schemaTab: "JSON Schema",
-  minimalTab: "Minimal example",
-  fullTab: "Full example",
-  errors: (count) => `${count} errors`,
-  warnings: (count) => `${count} warnings`,
-  ready: "Read-only example",
-  position: ({ line, column }) => `Ln ${line}, Col ${column}`,
-  characters: (count, limit) => (limit ? `${count} / ${limit}` : `${count} characters`),
-  diagnosticsTitle: "Diagnostics",
-  diagnostic: (diagnostic) => diagnostic.value ?? diagnostic.code,
-};
-const editableMessages: CustomWidgetEditorMessages = { ...messages, ready: "Ready" };
-
-export function CanonicalCustomWidgetExampleClient({ id, label, example, height }: CanonicalCustomWidgetExampleProps) {
-  const value = example === "requests" ? CUSTOM_WIDGET_REQUEST_EXAMPLES.full : CUSTOM_WIDGET_OPTIONS_EXAMPLES.full;
-
-  return <CustomWidgetCodeExampleClient id={id} label={label} code={JSON.stringify(value, null, 2)} height={height} />;
-}
-
-export function CustomWidgetCodeExampleClient(props: CustomWidgetCodeExampleProps) {
-  const { colorMode } = useColorMode();
-
-  return (
-    <MantineProvider forceColorScheme={colorMode}>
-      <ReadOnlyCustomWidgetCode
-        id={props.id}
-        label={props.label}
-        language={props.language ?? "json"}
-        value={props.code}
-        messages={messages}
-        height={props.height}
-      />
-    </MantineProvider>
-  );
-}
-
-export function CustomWidgetCodeInputClient(props: CustomWidgetCodeInputProps) {
-  const { colorMode } = useColorMode();
-
-  return (
-    <MantineProvider forceColorScheme={colorMode}>
-      <CustomWidgetCodeEditor {...props} messages={editableMessages} />
-    </MantineProvider>
-  );
-}
-
-export function BundledCustomWidgetGalleryClient() {
-  const { colorMode } = useColorMode();
-  const [selectedId, setSelectedId] = useState(BUNDLED_CUSTOM_WIDGETS[0]?.id ?? null);
-  const selected = BUNDLED_CUSTOM_WIDGETS.find(({ id }) => id === selectedId) ?? BUNDLED_CUSTOM_WIDGETS[0];
-  if (!selected) return null;
-
-  return (
-    <MantineProvider forceColorScheme={colorMode}>
-      <Stack gap="md">
-        <Select
-          label="Bundled widget"
-          data={BUNDLED_CUSTOM_WIDGETS.map(({ id, widget }) => ({ value: id, label: widget.name }))}
-          value={selected.id}
-          onChange={(value) => {
-            if (value) setSelectedId(value);
-          }}
-          allowDeselect={false}
-        />
-        <Text size="sm" c="dimmed">
-          {selected.widget.description}
-        </Text>
-        <ReadOnlyCustomWidgetCode
-          id={`${selected.id}-manifest`}
-          label="Complete widget.json"
-          language="json"
-          value={JSON.stringify(selected.widget, null, 2)}
-          messages={messages}
-          height="680px"
-        />
-      </Stack>
-    </MantineProvider>
-  );
-}

apps/docs/src/components/custom-widget-code.tsx

@@ -1,82 +0,0 @@
-import BrowserOnly from "@docusaurus/BrowserOnly";
-
-import {
-  BundledCustomWidgetGalleryClient,
-  CanonicalCustomWidgetExampleClient,
-  CustomWidgetCodeInputClient,
-  CustomWidgetCodeExampleClient,
-} from "./custom-widget-code-client";
-
-export interface CustomWidgetCodeExampleProps {
-  id: string;
-  label: string;
-  code: string;
-  language?: "json" | "jsx";
-  height?: string;
-}
-
-export interface CustomWidgetCodeInputProps {
-  id: string;
-  label: string;
-  value: string;
-  onChange(value: string): void;
-  language: "json" | "css";
-  description?: string;
-  placeholder?: string;
-  height?: string;
-  required?: boolean;
-  maxLength?: number;
-}
-
-export interface CanonicalCustomWidgetExampleProps {
-  id: string;
-  label: string;
-  example: "requests" | "options";
-  height?: string;
-}
-
-export function CanonicalCustomWidgetExample(props: CanonicalCustomWidgetExampleProps) {
-  return (
-    <BrowserOnly fallback={<CodeExampleFallback height={props.height} />}>
-      {() => <CanonicalCustomWidgetExampleClient {...props} />}
-    </BrowserOnly>
-  );
-}
-
-export function CustomWidgetCodeExample(props: CustomWidgetCodeExampleProps) {
-  return (
-    <BrowserOnly fallback={<CodeExampleFallback height={props.height} />}>
-      {() => <CustomWidgetCodeExampleClient {...props} />}
-    </BrowserOnly>
-  );
-}
-
-export function CustomWidgetCodeInput(props: CustomWidgetCodeInputProps) {
-  return (
-    <BrowserOnly fallback={<CodeExampleFallback height={props.height} />}>
-      {() => <CustomWidgetCodeInputClient {...props} />}
-    </BrowserOnly>
-  );
-}
-
-export function BundledCustomWidgetGallery() {
-  return (
-    <BrowserOnly fallback={<CodeExampleFallback height="520px" />}>
-      {() => <BundledCustomWidgetGalleryClient />}
-    </BrowserOnly>
-  );
-}
-
-function CodeExampleFallback({ height }: { height?: string }) {
-  return (
-    <div
-      style={{
-        minHeight: height ?? "220px",
-        border: "1px solid var(--ifm-color-emphasis-300)",
-        borderRadius: "var(--ifm-global-radius)",
-        background: "var(--ifm-background-surface-color)",
-      }}
-      aria-busy="true"
-    />
-  );
-}

apps/docs/src/components/ui/accordion.tsx

@@ -1,60 +0,0 @@
-import { Accordion as AccordionPrimitive } from "@base-ui/react/accordion";
-
-import { cn } from "@/lib/utils";
-import { IconChevronDown, IconChevronUp } from "@tabler/icons-react";
-
-function Accordion({ className, ...props }: AccordionPrimitive.Root.Props) {
-  return <AccordionPrimitive.Root data-slot="accordion" className={cn("flex w-full flex-col", className)} {...props} />;
-}
-
-function AccordionItem({ className, ...props }: AccordionPrimitive.Item.Props) {
-  return (
-    <AccordionPrimitive.Item data-slot="accordion-item" className={cn("not-last:border-b", className)} {...props} />
-  );
-}
-
-function AccordionTrigger({ className, children, ...props }: AccordionPrimitive.Trigger.Props) {
-  return (
-    <AccordionPrimitive.Header className="flex">
-      <AccordionPrimitive.Trigger
-        data-slot="accordion-trigger"
-        className={cn(
-          "group/accordion-trigger relative flex flex-1 items-start justify-between rounded-lg border border-transparent py-2.5 text-left text-sm font-medium transition-all outline-none hover:underline focus-visible:border-ring focus-visible:ring-3 focus-visible:ring-ring/50 focus-visible:after:border-ring aria-disabled:pointer-events-none aria-disabled:opacity-50 **:data-[slot=accordion-trigger-icon]:ml-auto **:data-[slot=accordion-trigger-icon]:size-4 **:data-[slot=accordion-trigger-icon]:text-muted-foreground",
-          className,
-        )}
-        {...props}
-      >
-        {children}
-        <IconChevronDown
-          data-slot="accordion-trigger-icon"
-          className="pointer-events-none shrink-0 group-aria-expanded/accordion-trigger:hidden"
-        />
-        <IconChevronUp
-          data-slot="accordion-trigger-icon"
-          className="pointer-events-none hidden shrink-0 group-aria-expanded/accordion-trigger:inline"
-        />
-      </AccordionPrimitive.Trigger>
-    </AccordionPrimitive.Header>
-  );
-}
-
-function AccordionContent({ className, children, ...props }: AccordionPrimitive.Panel.Props) {
-  return (
-    <AccordionPrimitive.Panel
-      data-slot="accordion-content"
-      className="overflow-hidden text-sm data-open:animate-accordion-down data-closed:animate-accordion-up"
-      {...props}
-    >
-      <div
-        className={cn(
-          "h-(--accordion-panel-height) pt-0 pb-2.5 data-ending-style:h-0 data-starting-style:h-0 [&_a]:underline [&_a]:underline-offset-3 [&_a]:hover:text-foreground [&_p:not(:last-child)]:mb-4",
-          className,
-        )}
-      >
-        {children}
-      </div>
-    </AccordionPrimitive.Panel>
-  );
-}
-
-export { Accordion, AccordionItem, AccordionTrigger, AccordionContent };