test: align release v2 contracts

* Add Homarr provider proxy foundation

* Complete Homarr provider integration

* Harden Homarr provider integration

* Address Homarr provider review feedback

* Address CodeRabbit provider feedback

* Localize provider errors

* Handle provider activity load failures

* docs: improve workshop and homepage

* Harden Homarr provider limits

* fix: harden the Homarr provider

* fix: address provider review feedback

* fix: clarify provider request accounting

* feat: complete the Homarr provider endpoint

* fix: terminate invalid provider streams

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

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

.cursor/rules/codebase-context.mdc

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

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

@@ -263,15 +263,6 @@ Even hidden options need translation keys or the translation test fails:
 "widget.mywidget.option.columnWidths.label": "Column widths"
 ```
 
-### Old-import mappings
-
-Add to `packages/old-import/src/widgets/options.ts`:
-
-```typescript
-columnOrder: () => undefined,
-columnWidths: () => undefined,
-```
-
 ### Dynamic storeKey
 
 Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
@@ -610,13 +601,12 @@ if (isEditMode) rowContextMenuHandler = undefined;
 4. Add CSS file for transparent backgrounds (if widget context)
 5. Add responsive column visibility (if widget context)
 6. Add hidden options + hydration logic (if column persistence needed)
-7. Add old-import mappings for new options
-8. Add translation keys (including hidden option labels)
-9. Add context menu if row actions exist
-10. Add row expansion if detail view exists
-11. Add error handling on all mutations
-12. Add accessibility attributes
-13. Test at multiple widget widths
-14. Update docs in `apps/docs/docs/widgets/` if applicable
-15. Run `pnpm turbo typecheck` — catches old-import mismatches
-16. Run translation spec — catches missing keys
+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

.github/workflows/ci.yml

@@ -95,6 +95,12 @@ jobs:
       - name: Validate checked-in OpenAPI schema
         run: pnpm check:openapi
 
+      - name: Validate feature contracts
+        run: pnpm check:feature-contracts
+
+      - name: Test feature platform
+        run: pnpm test:feature-platform
+
       - name: Validate Custom Widget bundle budget
         run: |
           pnpm --filter nextjs build

.gitignore

@@ -84,3 +84,11 @@ apps/docs/.docusaurus
 apps/docs/build
 .pnpm-store
 benchmark-results
+
+# local performance investigation (never ship benchmark data or restored backups)
+.widget-performance/
+.bench/
+homarr-backup*.zip
+*.sqlite-wal
+*.sqlite-shm
+/scripts/benchmarks/

AGENTS.md

@@ -40,8 +40,6 @@ 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

MANTINE.md

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

PRODUCT.md

@@ -6,28 +6,34 @@ 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.
+Homarr is for self-hosters and administrators who assemble dashboards for services across home labs and private infrastructure. They need dense, reliable controls and status at a glance, while retaining 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.
+Homarr provides one place to organize, observe, and operate self-hosted services. Success means users can build useful dashboards quickly, understand their state, recover from configuration errors, act on services, and reshape their workspace without repeatedly leaving the board. Boards must load immediately, stay visually stable, and keep widgets legible across screen sizes.
 
 ## 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.
+Direct, capable, precise, and approachable. Homarr should feel calm under load, be truthful about system state, and reward users who refine details.
 
 ## 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.
+- Decorative dashboards, oversized metric cards, and motion without state meaning.
+- Wizard flows that fight ordinary scrolling or rigid layouts that force one workflow.
+- Hidden configuration magic and implementation complexity exposed before it is needed.
+- Clever custom controls where familiar platform or Mantine interactions already work.
 
 ## 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.
+1. Keep configuration, consequences, and system state visible.
+2. Make simple tasks short without limiting advanced workflows.
+3. Preserve expert depth while prioritizing urgent information at small sizes.
+4. Reveal dense workspaces progressively through a consistent advanced focus mode.
+5. Isolate failures and show loading, stale, partial, empty, and failed states truthfully.
+6. Use the existing Mantine design language consistently across management and board surfaces.
+7. Keep spatial actions direct: moving, resizing, nesting, and using fixed rails happen on the canvas with immediate feedback.
+8. Preserve predictable widget composition with fixed logical tile sizes and horizontal scrolling before controls become inaccessible.
 
 ## 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.
+Target WCAG 2.2 AA. Every pointer interaction needs a keyboard and coarse-pointer path. Support screen readers, visible and restored focus, sufficient contrast, reduced motion, non-color status cues, responsive layouts, actionable error messages, and keyboard equivalents for drag and resize operations.

REVIEW.md

@@ -0,0 +1,263 @@
+# PR #6502 widget-modernization ultra-review
+
+## Executive result
+
+**Merge recommendation: changes required.** No P0 was found, but the current branch still has five P1 issues: a pre-existing Custom API authorization/redirect weakness exposed by this subsystem review, an inaccessible manual advanced-focus interaction, a likely fixed-position/transform geometry defect, systemic false empty states for failed queries, and unvalidated integration-provided navigation URLs. Eight P2 issues cover raw error disclosure, unsafe runtime-ref interfaces, localization, responsive/theming drift, test coverage, and inaccurate PR copy.
+
+Audit health (Impeccable rubric): accessibility 1/4, performance 2/4, responsive design 2/4, theming 2/4, anti-patterns 3/4; **10/20 (Acceptable, significant work required)**. The UI does not look generically AI-generated; its problem is inconsistent technical behavior beneath an otherwise coherent Mantine vocabulary.
+
+## Reviewed revision and environment
+
+| Item                         | Value                                                                                          |
+| ---------------------------- | ---------------------------------------------------------------------------------------------- |
+| PR                           | #6502, `feat: modernize dashboard widgets`                                                     |
+| Reviewed head                | `96e92485a5fd45f3648cfac0453e614779c414ba`                                                     |
+| Base branch / fetched base   | `dev` / `d58a47b776a55d04dee2220f59d072b9af8bbed3`                                             |
+| Merge base                   | `d58a47b776a55d04dee2220f59d072b9af8bbed3`                                                     |
+| Diff                         | 359 files, +15,721/-4,478                                                                      |
+| PR state                     | open, non-draft, `BLOCKED`; no approval decision                                               |
+| Hosted checks at audit start | Fast gate, Container and E2E, CodeQL, JS/TS analysis, Actions analysis, title, auto-fix: green |
+| Inline threads               | 34 total, 7 unresolved; only 2 remain substantively valid                                      |
+| Mantine                      | repository lock: `@mantine/core`, hooks, charts and dates 9.4.1                                |
+| Local tools                  | Node 24.16.0 and pnpm 9.5.0; repository requires Node >=24.18.0 and pnpm >=11.15.1             |
+
+The former red baseline `7b7045202d289b7d83946befcee5d2845ea4a706` had a green Fast gate and a failed Container/E2E run (`30748255760`, job `91498308523`). The latest head has a green Container/E2E job (`30756067198`, job `91519039504`). This proves the current suite passed once; it does not satisfy the requested three-run flake characterization.
+
+## PR-description traceability
+
+| Claim                                                     | Result               | Evidence / correction                                                                                                                                                                                                                                      |
+| --------------------------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| “all 54 widget renderers with compact and advanced modes” | **Inaccurate**       | 54 `WidgetKind` values exist. `displayMode="advanced"` reaches 53; `app` is deliberately excluded in `item-content.tsx:51` and documented as compact-only. Change copy to “53 widget renderers; app tiles remain compact,” or implement app advanced mode. |
+| advanced focus: hover, keyboard, touch, geometry          | **Partial**          | Entry paths, Escape ownership, reduced motion, close focus, touch button and zero-dimension guards exist. WID-002/003 remain.                                                                                                                              |
+| richer widget context actions                             | **Partial**          | `Menu.ContextMenu` is a good Mantine choice and query scope is item-aware. Dispatch still crosses `any`; Custom API action authorization is not represented.                                                                                               |
+| standardized query identity/cache/status                  | **Partial**          | Query keys, matchers, runtime capture, recovery and tests exist. Thirty-nine of 53 renderer query calls do not read errors; runtime ref registration is render-time mutable state.                                                                         |
+| safe polling                                              | **Mostly confirmed** | defaults are limited to `widget` namespace; Custom API resume immediately refetches; per-widget intervals exist. State/ref typing still needs redesign.                                                                                                    |
+| partial-failure rendering                                 | **Partial**          | settlement helper and several routers are strong; many renderer-level total failures still appear empty/disconnected.                                                                                                                                      |
+| bounded integration responses                             | **Mostly confirmed** | common bounded reader, Custom API 2 MiB, timetable 512 KiB, Traefik bounds and Beszel queue bounds exist. Custom action execution remains outside the hardened fetch path.                                                                                 |
+| timetable hardening                                       | **Confirmed**        | board/item permission checks, saved-value comparison, public-address resolution, private ranges, per-request DNS re-resolution, pinned dispatcher, redirect rejection, timeouts, response bounds and schemas are present.                                  |
+| precise placement                                         | **Mostly confirmed** | mouse, touch tolerance, keyboard, occupied-cell validation, dynamic bounds, nearest fit and immediate persistence exist. Failure/race/live responsive coverage remains insufficient.                                                                       |
+| widget catalog documentation                              | **Partial**          | all kinds have pages and shared interactions; wording overclaims focus behavior and validation counts are stale.                                                                                                                                           |
+| validation: 40 files/162 tests, 6/6 E2E                   | **Stale**            | current diff contains 57 changed unit-spec files (including three E2E specs); repository has 42 widget spec files and six E2E specs. Update from the exact final run.                                                                                      |
+| independent reviews “pass”                                | **Not supported**    | unresolved valid findings, current P1s, and unavailable live QA contradict an unqualified pass.                                                                                                                                                            |
+
+## Mantine suitability ledger
+
+Legend: **U** already used appropriately; **C** consolidation/replacement candidate; **R** relevant but current implementation can stay; **N** not relevant to widget runtime; **D** dependency/version addition. Exact 9.4.1 package archives were inspected in `/tmp`; live docs/Context7 include 9.5.0.
+
+### Core catalog
+
+- **U:** ActionIcon, Alert, Anchor, Avatar, Badge, Box, Button, Card, Center, Code, Divider, Flex, Grid, Group, Image, Loader, Menu (`Menu.ContextMenu`), Overlay, Paper, Popover, Portal, Progress, RingProgress, ScrollArea, SimpleGrid, Skeleton, Stack, Table, Tabs, Text, ThemeIcon, Title, Tooltip, UnstyledButton.
+- **C:** Accordion (dense integration sections), DataList (semantic label/value stats), EmptyState (replace bespoke empty state), FocusTrap and Modal compound API (WID-002), LoadingOverlay (background refetch without deleting content), NumberFormatter, OverflowList/Scroller (responsive action and chip rows), Table.ScrollContainer, Timeline (activity/feed histories), VisuallyHidden and Kbd, CloseButton, Dialog/HoverCard/Notification where persistent errors/actions need semantics.
+- **R:** Affix, AppShell, AspectRatio, BackgroundImage, Breadcrumbs, Burger, Checkbox, Chip, Collapse, ColorInput/ColorPicker/ColorSwatch/AlphaSlider/AngleSlider/HueSlider, Combobox/ComboboxPopover, Container, CopyButton, Drawer, Fieldset, FileButton/FileInput, FloatingIndicator/FloatingWindow, Highlight, Indicator, Input/JsonInput, List, Mark, Marquee, MaskInput, Menubar, MultiSelect/NativeSelect/NumberInput/PasswordInput/PillsInput/PinInput/Radio/RangeSlider/Rating/SegmentedControl/Select/Slider/Switch/TagsInput/Textarea/TextInput, Pagination, Pill, SemiCircleProgress, Space, Splitter, Spoiler, Stepper, Transition, Tree/TreeSelect, Typography. Use only where an existing widget requirement matches; do not churn working layouts.
+- **N:** Alpha/color/angle primitives outside configuration forms, AppShell/navigation primitives, TableOfContents, CorePackage documentation.
+- **D (9.5, not 9.4.1):** Cascader. **RollingNumber and Splitter are present in 9.4.1.**
+
+### Hooks catalog
+
+- **C:** `useFocusReturn`, `useFocusTrap`, `useReducedMotion`, `useRovingIndex`, `useLongPress`, `useScroller`, `useElementSize`, `useViewportSize`, `useHotkeys`, `useMediaQuery`, `useResizeObserver`.
+- **U/R:** focus-within, hover, disclosure, click-outside, merged-ref, interval/timeout, local-storage, event/window listeners, throttled/debounced values and list/set/map/state helpers are available in 9.4.1 and should replace local mechanics only when behavior and tests improve.
+- **N:** document title/favicon/hash/headroom/page-leave/OS/eye-dropper/fullscreen/network/orientation and other page-level utilities have no direct widget-remediation need. Every hook listed under `## Hooks` in `MANTINE.md` is covered by this rule; no hook requires 9.5 for the recommendations above.
+
+### Form, dates, charts, schedule, extensions, theme and styles
+
+- **Form:** existing `@homarr/form` should remain the abstraction over all cataloged form APIs. No widget-runtime replacement; use current validation/status APIs for widget editors (**R**).
+- **Dates:** all catalog entries are in installed 9.4.1 dates. `Calendar`, `MiniCalendar`, and `TimeValue` are candidates; other picker/input entries are editor-only (**R**). Importing dates directly into `@homarr/widgets` requires adding that workspace dependency (**D**).
+- **Charts:** 9.4.1 exports Area, Bar, BarsList, Bubble, Composite, Donut, Funnel, Heatmap, Line, Pie, Radar, RadialBar, Sankey, Scatter, Sparkline and Treemap (**C/R**). Prefer Sparkline for tiny trends, BarsList for ranked values, Heatmap for calendar/activity density, Composite for mixed analytics. **BulletChart and SunburstChart are 9.5-only (D)**. Replacement requires accessibility and bundle comparison, not blanket Recharts removal.
+- **Schedule:** all `AgendaView`, day/week/month/year/resource views and Schedule pages require new `@mantine/schedule` dependency (**D**). AgendaView is the only plausible calendar-widget candidate; its weight and semantics must beat the existing grouped list before adoption.
+- **Guides/FAQ/Other:** server components, portal testing, scroll lock, accessibility, nested popovers, zoom, responsive styling and version changelogs are relevant references (**R**); framework/setup/contribution/old migration entries are **N**. The 9.5 changelog is informational only.
+- **Theming/styles:** Colors, ColorSchemes, DefaultProps, MantineProvider, ThemeObject, CSS variables, data attributes, CSS Modules, responsive/RTL/style props/Styles API/performance are **U/R**. WID-009 requires shared layer/color tokens. Emotion, Sass, Vanilla Extract and unrelated global setup are **N**.
+- **Extensions:** existing modals, notifications, spotlight and rich-text abstractions are **U**; Carousel could consolidate Immich only after behavior parity; Dropzone/CodeHighlight/NProgress are **N** for this audit.
+
+## Complete 54-widget coverage matrix
+
+“Test” means a focused widget-local spec exists, not that all required states are covered. Every row still requires the common contract suite in WID-013.
+
+| WidgetKind                  | Family                  | Advanced    | Focused test | Principal audit gap                                        |
+| --------------------------- | ----------------------- | ----------- | ------------ | ---------------------------------------------------------- |
+| clock                       | basic                   | yes         | no           | query error, locale-format options                         |
+| weather                     | basic/feed              | yes         | yes          | query error; dayjs locale/time patterns                    |
+| app                         | basic/link              | **no**      | no           | PR wording; URL contract                                   |
+| iframe                      | custom content          | yes         | yes          | manual focus/iframe trapping; URL privacy thread now fixed |
+| video                       | custom content          | yes         | no           | media/focus/live behavior                                  |
+| notebook                    | notes                   | yes (inner) | yes          | editor focus inside manual surface                         |
+| anchorNote                  | notes                   | yes         | no           | query error, save/error regression                         |
+| dnsHoleSummary              | network                 | yes         | no           | total query error, hard-coded chart colors                 |
+| dnsHoleControls             | network/security        | yes         | no           | total error and permission matrix                          |
+| smartHome-entityState       | smart home              | yes         | no           | raw state in aria; action permissions                      |
+| smartHome-executeAutomation | smart home              | yes         | no           | mutation/permission/edit-mode E2E                          |
+| stockPrice                  | analytics               | yes         | yes          | total error                                                |
+| mediaServer                 | media                   | yes         | no           | total error and table a11y                                 |
+| calendar                    | calendar                | yes         | yes          | total error; fixed HH:mm; schedule tradeoff                |
+| downloads                   | media                   | yes         | yes          | four-state/component coverage, arbitrary z-index           |
+| mediaRequests-requestList   | media                   | yes         | no           | total error; external URLs/actions                         |
+| mediaRequests-requestStats  | media                   | yes         | no           | total error; links/colors                                  |
+| mediaTranscoding            | media                   | yes         | yes          | total error and responsive table                           |
+| mediaMissing                | media                   | yes         | yes          | total error and external URL                               |
+| minecraftServerStatus       | infrastructure          | yes         | no           | total error/malformed payload                              |
+| networkControllerSummary    | networking              | yes         | no           | total error; WAN/unknown localization                      |
+| networkControllerStatus     | networking              | yes         | no           | responsive rule duplication                                |
+| rssFeed                     | feed                    | yes         | yes          | strong stale/partial state; locale relative time           |
+| bookmarks                   | basic/link              | yes         | yes          | recomputation; URL contract                                |
+| indexerManager              | media                   | yes         | no           | total error; runtime action ref                            |
+| healthMonitoring            | infrastructure          | yes         | yes          | integration query error                                    |
+| releases                    | infrastructure/feed     | yes         | yes          | secret/item authorization needs E2E                        |
+| mediaReleases               | media                   | yes         | no           | total error; external URLs                                 |
+| dockerContainers            | infrastructure          | yes         | yes          | total error; z-index/table semantics                       |
+| firewall                    | networking/security     | yes         | yes          | partial-query matrix; loose router generics                |
+| notifications               | infrastructure          | yes         | no           | total error; untrusted href                                |
+| systemResources             | infrastructure          | yes         | yes          | total error; previous network thread fixed                 |
+| coolify                     | infrastructure          | yes         | yes          | total error; URL validation                                |
+| systemDisks                 | infrastructure          | yes         | yes          | total error                                                |
+| timetable                   | calendar                | yes         | no           | backend strong; component locale/live tests absent         |
+| immich-serverStats          | media                   | yes         | yes          | two ignored query errors                                   |
+| immich-albumCarousel        | media                   | yes         | yes (query)  | query error and nested overlay/focus E2E                   |
+| paperlessNgx                | analytics               | yes         | no           | former error thread fixed, no regression spec              |
+| patchmon                    | infrastructure          | yes         | yes          | total error                                                |
+| bazarr                      | media                   | yes         | yes          | total error                                                |
+| tracearr                    | analytics               | yes         | yes          | total error                                                |
+| speedtestTracker            | analytics               | yes         | yes          | total error                                                |
+| uptimeKuma                  | infrastructure          | yes         | yes          | total error                                                |
+| audioStats                  | media                   | yes         | yes          | good dual-error handling; partial-state tests needed       |
+| umami                       | analytics               | yes         | no           | runtime query registration; chart a11y                     |
+| vpn                         | networking/security     | yes         | no           | total error; status/permission matrix                      |
+| archiveTeamWarrior          | infrastructure          | yes         | yes          | suspense path; docs present                                |
+| ups                         | infrastructure          | yes         | no           | total error                                                |
+| beszelSystemTable           | monitoring              | yes         | yes          | nested chart/focus and live subscription                   |
+| beszelSystemGrid            | monitoring              | yes         | no           | live/error UI; no focused renderer test                    |
+| beszelAlerts                | monitoring              | yes         | no           | partial error and status semantics                         |
+| beszelSystemStats           | monitoring              | yes         | yes          | runtime refs, locale tooltip                               |
+| traefik                     | networking              | yes         | no           | total error; bounded backend positive                      |
+| customApi                   | custom content/security | yes         | yes          | WID-001/007/008; polling resume fixed                      |
+
+## Severity-ranked findings
+
+### WID-001 — P1 confirmed, pre-existing: Custom API actions lack resource authorization and hardened fetch policy
+
+- **Location/claim:** `packages/api/src/router/custom-widget/custom-widget-router.ts:57-102,392-451`; “harden Custom API” and action-permission semantics.
+- **Evidence/reproduction:** any authenticated account can call `customWidget.all`, learn every definition ID and URL, then call `customWidget.execute({definitionId})`. The mutation verifies neither board nor item nor an action permission. It decrypts administrator-provided secrets, uses `new URL()` only, and `redirect: "follow"`. The PR hardened `widget.customApi.getData`, but not this sibling execution path.
+- **Impact/rule:** unauthorized side effects against internal services and authenticated redirect chains; broken object-level authorization. A view-only account can invoke administrator-created controls outside any board context.
+- **Correction:** require `{boardId,itemId,definitionId}`; load the item and verify it is `customApi`, belongs to the board, references the definition, and the caller has an explicit execute policy. Until that policy exists, restrict to admin. Share `validateCustomApiUrl`, timeout, redirect rejection, bounded disposal and redacted errors with getData. Compatibility: old direct callers must send item/board context.
+- **Tests:** procedure tests for anonymous, unrelated authenticated, view-only, modifier, admin, mismatched item/definition, disabled definition, redirects, credential URL, timeout and secret non-disclosure; E2E action button across roles.
+
+### WID-002 — P1 confirmed, PR-introduced: manual advanced focus is not an accessible modal
+
+- **Location:** `advanced-focus/context.tsx:194-209`, `items/item-content.tsx:113-189`.
+- **Evidence:** manual mode renders an Overlay plus a `role="region"` Card. There is no FocusTrap, `aria-modal`, background inertness, scroll lock or backdrop dismissal. Only the close button is initially focused; Tab can leave the surface and activate dimmed board controls.
+- **Impact/rule:** keyboard/screen-reader users lose the interaction boundary; WCAG 2.1.2, 2.4.3 and ARIA dialog pattern. Iframes/editors make escape especially likely.
+- **Correction/Mantine:** render manual mode through `Modal.Root` compound parts (or ModalBase), using its portal, FocusTrap, scroll lock, Escape/return-focus and semantic content. Preserve preview mode as non-modal. Configure nested overlays and `removeScrollProps`; keep a 44px `Modal.CloseButton` and explicit title via VisuallyHidden if needed.
+- **Tests:** RTL portal/focus-cycle/return tests; Playwright Tab/Shift+Tab, nested Menu/Select/Popover/editor/iframe, backdrop and every close path; reduced motion and 200% zoom.
+
+### WID-003 — P1 probable, PR-introduced: fixed advanced surface remains under transformed Gridstack ancestry
+
+- **Location:** `advanced-focus.module.css:35-42`; Card remains inside the Gridstack item while only the backdrop is portaled.
+- **Evidence:** CSS fixed descendants establish their containing block at a transformed ancestor. Gridstack uses transforms for positioned items, so viewport-derived `left/top` can be interpreted relative to the item on affected layouts. A Portal wrapper exists only for Overlay.
+- **Impact:** off-screen, clipped or incorrectly scaled focus surface across breakpoints/remounts.
+- **Correction:** portal the focused surface itself (naturally achieved by WID-002) and calculate geometry in the same viewport coordinate system. Do not compensate with transform-specific offsets.
+- **Tests:** real Gridstack at every layout/viewport, scrolled page, header, dynamic section and resize/remount; assert bounding rect within viewport and finite scale.
+
+### WID-004 — P1 confirmed, regression-exposed/systemic: query failures still become valid empty/disconnected UI
+
+- **Location:** 39 of 53 renderer query calls do not read `error`, including bookmarks, weather, calendar, media server, system resources, Coolify, DNS Hole, Tracearr, notifications, Immich, VPN and others listed in the matrix. Query defaults do not set `throwOnError` (`trpc.tsx:69-93`).
+- **Evidence:** TanStack Query returns `data=undefined` on total failure. Components default to `[]`, `null`, or empty branches, so the board ErrorBoundary is never reached. Network Controller and Paperless were fixed, proving the pattern; it was not completed.
+- **Impact:** operators are told “empty” or “disconnected” when monitoring failed, violating the product’s truthful-state requirement.
+- **Correction/Mantine:** introduce a shared `WidgetQueryState` contract distinguishing initial Skeleton, background LoadingOverlay, stale Alert, partial warning, true EmptyState and terminal error. Either explicitly throw only when no usable cached data or render a shared error Alert. Preserve stale data.
+- **Tests:** parameterized contract tests for every queried widget: initial, success-empty, total failure, stale+failure, partial failure, refetch, remount/persisted cache and sibling isolation.
+
+### WID-005 — P1 confirmed, PR-introduced/systemic: integration-provided links bypass a shared URL policy
+
+- **Location:** examples include `media-missing/component.tsx:291`, `notifications/component.tsx:77`, media requests list/stats, Coolify resource/server links, releases, bookmarks and iframe. Only RSS and custom JSX visibly use explicit protocol sanitizers.
+- **Evidence:** dynamic strings are assigned directly to `href`/new-tab controls. Integration APIs and remote feeds are trust boundaries; no renderer-wide `http/https` guard is enforced.
+- **Impact:** unsafe schemes, credential-bearing URLs, internal detail disclosure and inconsistent opener behavior.
+- **Correction:** add one typed application URL helper returning a sanitized URL/undefined, with allowed schemes per use case, credential stripping/rejection, consistent `noopener noreferrer`, and disabled non-link presentation. Validate again server-side for action endpoints.
+- **Tests:** `javascript:`, `data:`, malformed, credential, relative, http/https and missing URLs for each shared link primitive.
+
+### WID-006 — P2 confirmed, PR-introduced: runtime query/action state mutates untyped refs during render
+
+- **Location:** `definition.ts:121-162`; runtime registration calls in media missing/transcoding, audio, calendar, Umami, Beszel and Immich; `widget-context-menu.tsx:157-174`.
+- **Evidence:** `setWidgetRuntimeQueries` mutates a shared object during render; concurrent/aborted renders can publish uncommitted query identity. Action dispatch casts the definition to `Record<string,unknown>` and `any`, then casts its result back.
+- **Correction:** make definition generics preserve kind/options/action types end-to-end; replace stringly opaque ref slots with a typed per-item registration API updated in a committed effect (or use `useSyncExternalStore`). Separate query registration from imperative actions.
+- **Tests:** StrictMode, interrupted/remount, options change and cleanup; compile-time `tsd`/type assertions rejecting wrong action props.
+
+### WID-007 — P2 confirmed, regression-exposed: raw backend errors are exposed to users and assistive text
+
+- **Location:** Custom API UI `component.tsx:561-576`; API `custom-api.ts:79-85`; several partial fallbacks use `error.message`.
+- **Impact:** internal hostnames, request paths and implementation details can appear in tooltips/aria labels and logs.
+- **Correction/Mantine:** return stable error codes plus redacted public messages; keep detailed causes server-side with correlation IDs. Render localized Alert/Notification details, never raw throwable text.
+- **Tests:** errors containing credentials, query strings, private hosts and multiline backend bodies must not reach tRPC payload, DOM, accessibility tree or notifications.
+
+### WID-008 — P2 confirmed, PR-introduced/regression-exposed: locale handling remains incomplete
+
+- **Locations:** Beszel chart/tooltip dayjs formats, calendar event `HH:mm`, downloads `YYYY-MM-DD HH:mm`, timetable `HH:mm:ss`, weather day/month/time formats; `_inputs/widget-location-input.tsx:199` hardcodes `Intl.NumberFormat("en")`.
+- **Also:** `beszel/_shared/disk-usage.tsx:41`, stats loading aria label, Network Controller `WAN`/`unknown` are English/raw accessible strings.
+- **Correction:** centralize app-locale date/time/number/duration/status helpers; load canonical dayjs locale only at the boundary; use localized translation keys for aria/status. NumberFormatter is suitable for simple display but application helpers should own locale.
+- **Tests:** at least `en-US`, `fr-FR`, `de-DE`, RTL locale, 12/24-hour preference and long translations, including accessibility names.
+
+### WID-009 — P2 confirmed: layer and color tokens are inconsistent
+
+- **Locations:** downloads z-index 1000 and rgba row colors; item title z-index 4; item menu/dynamic menu 10; media server white rgba; Indexer Manager hex colors; DNS Hole rgba palette; Umami hex tick colors.
+- **Correction:** define shared semantic layer tokens relative to Mantine CSS z-index variables and semantic status/chart tokens respecting light/dark/forced colors. Do not replace intentional service branding.
+- **Tests:** light/dark/forced-colors with nested overlays and tooltip ordering.
+
+### WID-010 — P2 confirmed: responsive decisions are duplicated and under-tested
+
+- **Location:** Network Controller Status `component.tsx:44,59-78` (open valid thread); Bookmark `component.tsx:94` recomputation (valid but low-impact thread); similar width/height literals across renderers.
+- **Correction:** small typed breakpoint lookup helpers per family, memoized only for genuinely expensive layout. Prefer container-query Grid/SimpleGrid where structural. Do not cargo-cult `useMemo` for a cheap pure calculation; benchmark Bookmark before accepting the review suggestion.
+- **Tests:** boundary tables for minimum/typical/wide/short/advanced sizes and 200% zoom.
+
+### WID-011 — P2 confirmed: PR/docs overstate behavior and validation
+
+- **Location:** PR body, board/getting-started copy “advanced preview in place,” validation numbers, and unqualified review pass.
+- **Correction:** state 53 advanced renderers plus compact-only app; call manual focus an overlay only after WID-002/003; publish exact final-SHA check/test counts and disclose unsupported/live-untested states.
+
+### WID-012 — P2 confirmed: focused automated coverage is far below the 54-widget/data-state claim
+
+- **Evidence:** 42 widget-local spec files are helper-heavy; 20+ renderers have no focused spec. Six E2E files exist, but only board interactions and Custom JSX directly exercise this modernization. The earlier Custom JSX login wait failed once and current exact-route wait remains.
+- **Correction:** add shared renderer contract harness plus family E2Es. Replace Custom JSX’s exact post-submit URL race with a shared login helper that waits for authenticated session/stable destination, then run it three times in CI.
+
+### WID-013 — P2 confirmed: open review-thread state no longer matches code
+
+| Thread                                      | Classification                                                      |
+| ------------------------------------------- | ------------------------------------------------------------------- |
+| iframe complete URL                         | already fixed/false positive at current line: only host is rendered |
+| system resources network gate               | already fixed, outdated                                             |
+| RSS total error                             | already fixed: no-data error throws; stale data retained            |
+| bookmarks memoization                       | valid P3/P2-low; benchmark first                                    |
+| network-controller total error              | already fixed, outdated                                             |
+| network-controller breakpoint consolidation | valid P2 maintainability                                            |
+| Paperless total error                       | already fixed, outdated                                             |
+
+Resolve the five stale threads with evidence; address or explicitly disposition the two live suggestions. Re-run review because CodeRabbit was paused during active development.
+
+## Systemic remediation roadmap
+
+1. **Security/authorization:** WID-001 and WID-005; add negative-role/protocol tests before merge.
+2. **Interaction accessibility:** replace manual focus with portaled Mantine modal semantics (WID-002/003), then test nested widget content.
+3. **Truthful data state:** build the shared query-state contract and migrate all 39 ambiguous sites; keep valid stale data and partial results.
+4. **Typed interfaces:** replace `widgetStateRef` slot mutation and `any` context dispatch with committed typed registrations.
+5. **Widget families:** media/downloads, infrastructure, networking/security, smart-home, analytics/calendar/feed, then Beszel; apply URL, state, locale, responsive and a11y contracts in that order.
+6. **Design-system cleanup:** semantic layers/colors and restrained Mantine consolidation. Do not add Schedule or upgrade to 9.5 without a separate dependency/bundle decision.
+7. **Docs/PR:** correct renderer count, behavior and exact validation evidence.
+8. **Final proof:** frozen install on supported Node/pnpm; format, lint, full typecheck, affected and full unit tests, production and docs builds; Custom JSX three times; complete production-container E2E; desktop/tablet/mobile keyboard/touch/light/dark/reduced-motion/zoom/a11y-tree QA. Push nothing until all refer to one unchanged SHA; close every review thread and obtain required approval.
+
+## Positive findings
+
+- Timetable is the strongest security work in the PR: saved resource authorization, private-range rejection, DNS rebinding resistance through pinned lookup, redirect rejection, bounds and schemas are coherently tested.
+- Bounded response helpers, Beszel bounded queue/cancellation, and partial-integration settlement materially reduce failure blast radius.
+- RSS preserves stale data and distinguishes partial feed failure; Network Controller and Paperless now correctly escalate total failures.
+- Item-scoped query matchers and tests address sibling-widget refresh isolation; global polling defaults are restricted to the widget namespace.
+- Touch long-press has movement tolerance; focus scale guards prevent Infinity/NaN; reduced-motion and remount cleanup are present.
+- Existing Homarr theme, Mantine components and shared UI vocabulary are generally preserved. Most proposed Mantine work is consolidation, not redesign.
+
+## Validation evidence and uncertainty
+
+- `MANTINE.md` was fetched from `https://mantine.dev/llms.txt` and passed byte-for-byte `cmp`; `llms-full.txt` stayed in `/tmp`.
+- Context7 current Mantine docs were queried for overlay/focus, responsive/data-state/accessibility, charts and Schedule. Static 9.4.1 archives verified exact exports; Cascader, BulletChart and SunburstChart are 9.5-only.
+- Local frozen install could not start because host Node/pnpm are below repository engine requirements. No dependencies, source files or machine toolchain were changed.
+- Docker API access is denied, so production-container E2E could not be rerun locally. Hosted exact-head Fast gate and Container/E2E are green.
+- `agent-browser` is not installed. Temporary `npx` execution was rejected by the environment’s security reviewer, so live exploratory QA/a11y-tree inspection was not performed.
+- External integrations were not available; malformed/partial/permission combinations are static-analysis conclusions unless a focused test already exists.
+- This review intentionally changes no production code and makes no commit, push, thread resolution or PR edit.
+
+Finalization must re-query the PR head/checks/threads. If the head differs from the reviewed SHA, this report is a snapshot and the delta requires review before merge.
+
+**Final refresh (2026-08-03):** head remained `96e92485a5fd45f3648cfac0453e614779c414ba`; all reported hosted checks remained successful; merge state remained `BLOCKED` with no approval decision; unresolved threads remained 7 of 34. The branch did not change during the audit.

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

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

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

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

apps/docs/docs/advanced/_category_.json

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

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

@@ -57,51 +57,73 @@ 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.
 
-### Run PocketBase and documentation
+Workshop contributors can set up PocketBase and Docusaurus with the dedicated
+[Workshop development guide](../../workshop/development).
 
-Start PocketBase in another terminal:
+### Scaffold a native feature
+
+Run `pnpm generate:feature` and choose `native-integration`, `widget`, or `integration-widget`. The generator creates
+implementation, focused test, documentation, and English translation skeletons and updates the current explicit
+registries. It stops before writing if a target exists, a registry anchor is ambiguous, or a supported integration is
+unknown.
+
+The generated code is a starting contract, not a finished feature. Replace the placeholder request, UI, tests, secrets,
+categories, configuration, error states, and documentation with behavior specific to the service. Then run:
 
 ```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
+pnpm check:feature-contracts
+pnpm test:feature-platform
 ```
 
-Then start Docusaurus in a third terminal:
+The contract check reports the exact registry, docs path, translation, support mapping, or package export that needs
+repair. It intentionally follows today's explicit registries; a future canonical feature descriptor can replace those
+patches without changing the contributor-facing generator names.
+
+Integration-capable widgets declare their server-safe relationship in `nativeFeatureCapabilities`. Homarr derives the
+widget-to-integration map, reverse integration-to-widget map, optional-connection set, and server selection limits from
+that descriptor. Widget definitions still mirror the supported list for client-side type inference; the focused widget
+manifest test and `check:feature-contracts` prevent drift until those definition types can consume the descriptor
+directly.
+
+New integration skeletons also include response fixtures using `simulateResponseContractAsync`. Replace the generated
+minimal schema and fixtures with representative upstream payloads: at least one successful response, important optional
+or version-specific shapes, and a malformed response that must be rejected. The simulator uses the real parser without
+network access and reports every fixture mismatch, so parser contracts can be reviewed before credentials are available.
+
+### Review native feature states
+
+In a development server, administrators can open `/manage/tools/feature-workbench` to inspect the shared `CatalogItem`
+and integration response-contract fixtures. The workbench uses the application Mantine theme and the same segmented
+fixture controls as the custom-widget preview. It covers ready, setup-required, standalone, connection-error, selected,
+loading, disabled, parser-success, and parser-failure states without requiring a live service.
+
+Use the workbench after changing shared catalog presentation or generated parser contracts, then run the focused test:
 
 ```sh
-WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
+pnpm exec vitest run "apps/nextjs/src/app/[locale]/manage/tools/feature-workbench/_feature-state-workbench.spec.tsx"
 ```
 
-PocketBase runs on port 8090 and Docusaurus on port 3003. Stopping the services preserves the PocketBase volume.
+The workbench is deliberately development-only and is not linked from management navigation. It does not yet exercise
+real integration branding, long translated labels, right-to-left text, high-contrast screenshots, touch interaction,
+small viewport clipping, live network latency, retry transitions, or service-specific response schemas. Those remain
+manual review items until screenshot and browser-automation coverage is added.
 
-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`.
+### Check one native feature
 
-Point Homarr at the local services with:
-
-```dotenv
-HOMARR_WEBSITE_URL=http://127.0.0.1:3003
-WORKSHOP_API_URL=http://127.0.0.1:8090
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
-```
-
-Restart `pnpm dev` after changing `.env`. GitHub OAuth is optional locally. See
-[`apps/workshop/README.md`](https://github.com/homarr-labs/homarr/blob/HEAD/apps/workshop/README.md) for OAuth,
-Workshop moderator promotion, logs, tests, backup, restore, stopping, and intentional volume reset.
-
-### URL testing
-
-Docusaurus reads `HOMARR_WEBSITE_URL` and `WORKSHOP_API_URL` when it starts or builds. Homarr also reads
-`WORKSHOP_WEB_URL` when its server starts, so these values do not rely on `NEXT_PUBLIC_*` build variables. Test a
-separate API origin before release:
+Run `pnpm check:feature <kind>` before submitting an integration or widget change. The command resolves the kind through
+`integrationDefs`, `widgetKinds`, the widget manifest, creator registry, documentation slug maps, and capability
+descriptor. When an integration and widget share a kind, such as `wud`, both sides are checked together.
 
 ```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
+pnpm check:feature wud --plan
+pnpm check:feature wud
 ```
 
+`--plan` (or `--dry-run`) prints the deterministic affected files and commands without executing them. The normal mode
+runs feature contracts, nearby fixture and unit tests, affected package typechecks, and lint and formatting for only the
+resolved files. Unknown kinds fail before any command runs. Live-service, container, and visual checks are printed as
+optional and are never executed implicitly because they may require credentials, images, or a running development app.
+
 ### Useful commands
 
 - `pnpm dev` — Next.js on port 3000.
@@ -112,17 +134,17 @@ pnpm dev:docs
 - `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 generate:feature` — scaffold a native integration, widget, or paired feature.
+- `pnpm check:feature-contracts` — validate native feature registries, docs, translations, support maps, and exports.
 - `pnpm lint` / `pnpm lint:fix` — check or apply oxlint.
 - `pnpm typecheck` — typecheck all workspaces.
 - `pnpm test` — unit and contract suites.
-- `pnpm test:workshop` — disposable Workshop integration suite.
 - `pnpm build` — production monorepo build.
 - `docker build -t homarr .` — build a production Docker image.
 - `docker run -p 7575:7575 -e SECRET_ENCRYPTION_KEY='your_64_character_hex_string' homarr:<name>` — run it.

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

@@ -37,6 +37,9 @@ Using the `PUID` and `PGID` will require you to set the correct permissions on t
 | `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` |
 
+Workshop service operators can find its server-only configuration in the
+[Workshop operator guide](../../workshop/operator#environment-variables).
+
 ## Authentication
 
 See [Single Sign-On](/docs/advanced/single-sign-on) for more informations.
@@ -55,11 +58,12 @@ 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_ENDPOINTS`    | JSON array of named, capability-scoped Docker or Podman endpoints. Supports socket, explicitly insecure TCP, and TLS transports. See the [Docker and Podman integration guide](/docs/integrations/docker) | A JSON array of endpoint descriptors                    | -       |
+| `DOCKER_HOSTNAMES`    | Legacy comma-separated list of plaintext TCP hostnames. Ignored when `DOCKER_ENDPOINTS` is set                                                                                                            | For example `localhost,docker.example.com`              | -       |
+| `DOCKER_PORTS`        | Legacy comma-separated list of plaintext TCP ports. Ignored when `DOCKER_ENDPOINTS` is set                                                                                                                | For example `2375,2376`                                 | -       |
+| `DOCKER_SOCKET_PATHS` | Legacy comma-separated list of mounted Docker-compatible socket paths. Ignored when `DOCKER_ENDPOINTS` is set                                                                                             | For example `/var/run/docker.sock,/var/run/podman.sock` | -       |
 
 ## Database
 
@@ -109,12 +113,9 @@ 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. |
+| Environment Variable     | Description                                         |
+| ------------------------ | --------------------------------------------------- |
+| `DB_MIGRATIONS_DISABLED` | Disable db migrations. For example for helm charts. |
 
 All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
-trailing slashes when Homarr or Docusaurus starts. The Docusaurus-only `WORKSHOP_URL` name is accepted as a deprecated alias for
-`WORKSHOP_API_URL` for one release. `WORKSHOP_API_URL` takes precedence.
+trailing slashes when Homarr or Docusaurus starts.

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

@@ -6,16 +6,22 @@ tags:
 
 Homarr has the following keyboard shortcuts:
 
-| Shortcut    | Description          |
-| ----------- | -------------------- |
-| `MOD` + `K` | Opens the search bar |
-| `MOD` + `J` | Toggles Dark Mode    |
-| `MOD` + `E` | Toggles Edit Mode    |
+| Shortcut                                        | Description                                |
+| ----------------------------------------------- | ------------------------------------------ |
+| `MOD` + `K`                                     | Opens the search bar                       |
+| `MOD` + `J`                                     | Toggles Dark Mode                          |
+| `MOD` + `E`                                     | Toggles Edit Mode                          |
+| Hold `Shift` for 500 ms over a supported widget | Opens its temporary advanced view          |
+| `Shift` + `Enter` on a supported widget         | Opens its advanced view until it is closed |
+| `Esc`                                           | Closes an open advanced view or board menu |
 
 :::tip
 
 Here `MOD` refers to the modifier key, which is `Ctrl` on Windows and `Cmd` on macOS.
 
+Advanced view is available outside edit mode. Widgets without a distinct advanced experience adapt to their normal
+dimensions instead. A progress ring follows the pointer while the temporary advanced view is preparing to open.
+
 :::
 
 :::note

apps/docs/docs/community/_category_.json

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

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

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

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

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

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

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

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

@@ -122,9 +122,77 @@ services:
       DOCKER_SOCKET_PATHS: /var/run/docker.sock,/var/run/podman.sock
 ```
 
+For named endpoints, transport security, or least-privilege actions, prefer `DOCKER_ENDPOINTS`. It is a JSON array where every endpoint declares its identity, transport, and capabilities:
+
+```yaml
+services:
+  homarr:
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock
+      - ./docker-ca.pem:/run/secrets/docker-ca.pem:ro
+    environment:
+      DOCKER_ENDPOINTS: >-
+        [
+          {
+            "id": "local",
+            "name": "Local Docker",
+            "kind": "docker",
+            "transport": { "type": "socket", "path": "/var/run/docker.sock" },
+            "capabilities": ["inventory", "logs", "lifecycle", "remove"]
+          },
+          {
+            "id": "remote-read-only",
+            "name": "Production inventory",
+            "kind": "docker",
+            "transport": {
+              "type": "tls",
+              "host": "docker.example.com",
+              "port": 2376,
+              "caPath": "/run/secrets/docker-ca.pem"
+            },
+            "capabilities": ["inventory", "logs"]
+          }
+        ]
+```
+
+The stable `id` keeps containers from different endpoints distinct. `name` is shown in the interface, and `kind` can be `docker` or `podman`. Every endpoint must include the `inventory` capability; optionally add `logs`, `lifecycle`, and `remove`. Homarr hides or disables actions the endpoint does not allow and also enforces the same capabilities on the server.
+
+Supported transports are:
+
+- `socket`: an absolute in-container `path`
+- `tls`: `host`, `port`, and an absolute `caPath`; add both `certPath` and `keyPath` for mutual TLS
+- `tcp`: `host`, `port`, and the explicit acknowledgement `allowInsecure: true`
+
+:::warning[Plaintext TCP]
+Plaintext Docker TCP can grant unauthenticated control of the Docker host. Prefer a local socket, a least-privilege socket proxy, or TLS. The structured configuration refuses TCP unless `allowInsecure` is explicitly set to `true`.
+:::
+
+When `DOCKER_ENDPOINTS` is set, it takes precedence over the legacy `DOCKER_SOCKET_PATHS`, `DOCKER_HOSTNAMES`, and `DOCKER_PORTS` variables.
+
 ### Managing your Docker containers within Homarr
 
 Homarr allows you to interact with Docker containers running on your system.
+The **Service setup** section compares the visible containers with your existing Homarr apps and integrations. It keeps every service distinct by Docker endpoint and container ID, including multiple containers that use the same integration type.
+
+Homarr can show a service as:
+
+- **Ready to connect** when its image or name matches a supported integration
+- **New service** when it can be added as an app but no integration is recognized
+- **Already represented** or **Linked** when an app or integration already matches
+- **Address changed** when a service appears to match an integration but its reachable address has changed
+
+Suggested addresses are ranked and explain where they came from. A published address or Docker endpoint host is normally usable from a browser; a container-name address is server-only and requires Homarr to share the container network. Wildcard addresses such as `0.0.0.0` are never offered as browser destinations. You can edit every suggestion before continuing.
+
+:::info[Review before changing]
+Service discovery is read-only. Homarr never creates or changes an app or integration automatically; use the action on an individual suggestion to review and confirm its setup.
+:::
+
+Use the inbox filters to focus on services that need attention or those already represented in Homarr. Refresh runs discovery again. Dismissed suggestions are stored in the current browser using their endpoint-qualified service identity and can be restored from the same panel. If multiple existing items could match, Homarr marks the result as ambiguous and does not choose one automatically.
+
+The health badges are an evidence-based projection across Docker, integration configuration, app representation, and persisted widget links. Authentication, API request success, and widget query execution are labeled **Not observed** because Homarr does not currently retain trustworthy last-run results for these layers. Use the suggested integration test or board action to diagnose them live; **Not observed** is never presented as healthy.
+
+If one Docker endpoint is unavailable, Homarr reports that endpoint while continuing to show services from healthy endpoints. An unavailable endpoint is not treated as an empty Docker installation.
+
 Each container row has an action menu with the following options:
 
 - **View logs** - opens a dedicated logs page with a live terminal
@@ -160,11 +228,13 @@ They are then available in the app list and can be used as normally added apps.
 
 ![Apps added from containers](img/add-to-homarr-apps.png)
 
-### Configuration
+### Container labels
 
-Currently Homarr supports one label for configuration of the containers:
+`homarr.hide` excludes a container from the Docker Containers widget, tools page, and onboarding discovery whenever the
+label is present.
 
-- **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
+During first-run onboarding, Homarr can also discover apps, integrations, groups, and compatible widgets from
+`homarr.*` labels, with Homepage labels as a fallback. See the complete [Docker label reference](/docs/integrations/docker-labels).
 
 ### Security
 

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

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

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

@@ -82,8 +82,48 @@ The OpenAPI and MCP APIs include board management endpoints for common automatio
 - Set desktop and mobile home boards for the current user
 - Configure global board defaults such as public home boards and status behavior
 
+Board layout responses identify each layout with a `mobile`, `base`, or `custom` role. Mobile and Base are protected. Layout-saving clients must preserve existing roles, keep Mobile at breakpoint `0`, keep Base as the highest breakpoint, and use unique custom breakpoints between them. The layout save operation returns the canonical saved layouts, including server-generated IDs for new custom layouts. A non-Base layout can be regenerated from Base with the protected reset operation.
+
 Use the interactive API reference to inspect the exact request body for each endpoint under the `boards` and `settings` tags.
 
+## Docker action payload migration
+
+Docker lifecycle and removal actions now identify each container with both its Docker endpoint and container ID. This is a
+breaking change for tRPC and MCP clients that previously sent an `ids` array to the start, stop, restart, or remove action.
+
+Replace the old payload:
+
+```json
+{ "ids": ["container-id"] }
+```
+
+with endpoint-qualified targets:
+
+```json
+{
+  "targets": [{ "endpointId": "local", "id": "container-id" }]
+}
+```
+
+Read `endpointId` and `id` from `docker.getContainers` (MCP tool `docker_getContainers`) immediately before the action.
+Pass those pairs unchanged to `docker.startAll`, `docker.stopAll`, `docker.restartAll`, or `docker.removeAll`; their MCP tool
+names use underscores, such as `docker_restartAll`. Endpoint qualification prevents identical container IDs on different
+Docker or Podman endpoints from targeting the wrong service.
+
+## Partial integration failures
+
+Multi-integration widget queries keep data from integrations that remain available. Calendar and media-server results include
+an optional `error` on a failed integration; media-request responses expose a `failedIntegrations` array, and the latest
+requests endpoint returns its items in `requests`. When every selected integration fails, the query returns an error instead
+of a partial response.
+
+### Saving dashboard layouts
+
+The dashboard editor saves item positions and sections as one board update.
+Canvas height follows its content automatically and does not require a separate API setting.
+Responsive layouts store optional left and right gutter widths from zero to three columns.
+Gutter columns are reserved from the layout's total column count, and changing them reflows affected items.
+
 ## Get Custom Widget authoring resources
 
 Custom JSX v2 provides four HTTP discovery endpoints:

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

@@ -51,6 +51,6 @@ Note that the ping URL only accepts `http://` and `https://` URLs — custom URI
 
 ## List of apps
 
-On the apps management page you find all apps that exist in your Homarr instance. You can edit and delete them.
+On the apps management page you find all apps that exist in your Homarr instance. Search by name or URL, open an app directly, or use its row actions to edit and delete it. A filtered search can be cleared without leaving the page.
 
-![Apps list](./img/app-list.png)
+Any signed-in user can view this list. Creating, editing, and deleting apps requires the corresponding app permission; board permissions are not required.

apps/docs/docs/management/assistant.mdx

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

apps/docs/docs/management/backup.mdx

@@ -22,6 +22,8 @@ Navigate to `Management` → `Tools` → `Backup`. You must have **admin** permi
 
 ## Exporting a Backup
 
+![Export database card with the Download Backup action](/img/backup/export-database.png)
+
 Click the **Export** button in the export card. You'll be prompted to type `I understand` to confirm. Once confirmed, a ZIP file downloads containing:
 
 | File            | Description                                                         |
@@ -33,6 +35,8 @@ The backup contains the complete database. It includes Custom Widgets and all ot
 
 ## Restoring a Backup
 
+![Restore database card with the backup ZIP drop zone](/img/backup/restore-database.png)
+
 ### 1. Upload
 
 Drag and drop or select a `.zip` backup file. The import card validates that the file contains a valid `db.sqlite` and metadata.
@@ -49,6 +53,9 @@ Before restoring, Homarr uses **sql.js WASM** to analyze the backup directly in
 
 Type `I understand` to acknowledge that restoring will replace your current database. This cannot be undone.
 
+During first-run onboarding, the database is still empty, so the restore preview goes directly to **Restore Database**
+without the extra typed confirmation. After Homarr restarts, onboarding opens the restored default home board.
+
 ### 4. Restore
 
 The backup ZIP is sent to the server, validated, and applied. After a successful restore:

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

@@ -20,6 +20,8 @@ You can create as many boards as you want.
 Boards can be restricted to user groups.
 A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/board).
 Other boards can be viewed by direct links (e.g. my-homarr.com/board/smart-home) or via the management pages.
+The management page includes a compact structural preview of each board's Base layout so you can recognize it before
+opening it. Containers include their visible widgets and app icons instead of appearing empty.
 
 Names of boards must be unique because this will be used in the URL to load the desired board.
 
@@ -36,8 +38,10 @@ Underscores and hyphen-minus are allowed.
 
 ### Column count
 
-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.
+The column count defines how many fixed-width cells are available in each row.
+One cell contains a `200 × 200` logical-pixel tile.
+Homarr scales the whole board uniformly instead of changing widget proportions, and always fits it to the available width without horizontal scrolling.
+The main canvas and enabled rails stay at least one viewport tall, and the canvas grows automatically while you drag or resize items near its lower edge.
 
 ### Public
 
@@ -88,33 +92,119 @@ Homarr will fall back to the Homarr logo if nothing is set.
 
 ### Layout
 
-In this section you can configure the different responsive layouts. Depending on your screens width the layout will change.
+In this section you can configure the different responsive layouts. Homarr selects the layout with the highest breakpoint that is not wider than the current screen, then scales its complete fixed-size canvas uniformly.
 
 ![](./img/layout-settings.png)
 
-On each element the position and size of items can be changed seperately.
-When adding a new layout the position and sizes will automatically be generated depending on the column count.
-When adding a new item / dynamic section that will always be 1x1 on each layout and placed on the first available position.
+Every board has two protected layouts:
+
+Every `1 × 1` tile has a `200 × 200` logical-pixel content area.
+The `24` logical-pixel gap between tiles is separate from that size.
+A `2 × 1` tile therefore contains two fixed cell widths plus the gap between them.
+Widgets see their logical size, while the board's visual scale makes the complete layout larger or smaller.
+When fitting below 100%, Homarr keeps widget typography and control density at their normal readable size.
+On larger canvases, the complete board grows together like browser zoom.
+The complete canvas always fits the available width and never adds horizontal board scrolling.
+
+- **Mobile** starts at `0px` and uses three columns on new boards.
+- **Base** is the widest layout and starts at `768px` on new boards.
+
+Mobile and Base can be renamed and their column counts can be changed, but they cannot be removed. Mobile has no fixed rails; rail configuration is available only on Base and custom layouts. You can add removable custom layouts between their breakpoints.
+
+Each layout stores independent positions and sizes. Moving or resizing a widget while editing Mobile does not move it in Base or any custom layout. New custom layouts are generated from Base and scaled to their selected column count.
+
+Use **Reset from Base** on Mobile or a custom layout to replace all of its positions and sizes with a newly generated version of Base. The layout's name, breakpoint, and column count are kept.
+
+The canvas is at least one window tall, even when it is empty.
+Its left and right edges are hard drag boundaries, while its bottom edge extends automatically as a tile is dragged or resized downward.
+Nested Containers keep their own resizable bounds.
+New items use their widget's default size and new Containers use a useful `4 × 3` size when space allows.
 
 #### Name
 
-The name of the layout can be choosen freely. It is only used for the management and will not be visible on the board.
+The name of the layout can be chosen freely. It is only used for management and is not displayed on the board.
 
 #### Column count
 
-Amount of columns for this layout. Defines how many items can be placed in a row. When changed it will automatically adjust the position and size of the items.
+The total number of columns in the layout. Changing it projects the saved positions and sizes into the new grid width without overlap.
+
+#### Fixed rails
+
+Base and custom responsive layouts can enable a fixed left rail, a fixed right rail, or both. Mobile has no fixed rails.
+Set a rail width to zero to disable it for that layout.
+Choose a width from one to three columns with the three-step slider.
+The preview shows how much space remains for the main canvas.
+
+Rail columns are reserved from the layout's total column count.
+For example, a 12-column layout with a two-column left rail leaves ten columns for the canvas.
+Enabling or widening a rail reflows canvas items into the remaining columns.
+Disabling a rail moves its contents back into the next available canvas positions.
+
+Rails fill the available window height and remain fixed while the page scrolls. They do not grow or scroll independently.
+Apps, widgets, and Containers inside them still use the same fixed `200 × 200` cells and can be rearranged in edit mode, where each rail shows its name and boundary.
 
 #### 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.
+The minimum screen width where the layout is used. Mobile is fixed at `0px`. Custom breakpoints must be unique and sit between Mobile and Base. Base must remain the highest breakpoint.
+
+#### View and edit modes
+
+View mode renders a static board without executing the drag-and-drop editor.
+After the board is interactive, Homarr prepares the editor in the background for users who can modify it.
+Entering edit mode keeps the static board visible until that preparation finishes, then enables collision-aware movement and resizing without changing the board geometry.
+Widget content is inert in edit mode, so dragging anywhere on the content moves the tile instead of activating the widget; its settings button remains visible in the compact header above the tile.
+Dropping a tile into another tile's exact slot swaps their positions when both resulting placements fit without overlapping other content.
+For other collisions, or when a tile grows into occupied space, nearby tiles are compacted out of the way.
+The visible corner controls provide a 44-pixel resize target, and edge controls appear on hover for horizontal or vertical resizing.
+Resize handles stop at the tile's minimum allowed size while the pointer is still moving.
+Exit edit mode to save the resulting positions.
+
+While edit mode is active, **Add board content** opens the same Universal Create surface as the global header action and
+Spotlight. It can add a widget, app, integration, Container, board, Workshop item, or Custom Widget when the
+current user and context allow it. Widget setup offers the main canvas, enabled rails, and existing Containers as
+destinations before the widget is created, so the common flow does not require a second move step.
+
+The widget editor also lists its selected integrations. Users with full access can choose **Edit connection** to test,
+diagnose, and repair an integration without leaving the board. A successful repair refreshes the affected widget; the
+saved integration changes apply everywhere that connection is used.
+
+Pointer users can drag anywhere on a widget tile. Containers use the grab button at their top-left corner.
+Resize tiles from any edge or corner handle.
+On a touch screen, press and hold the tile before moving it; resize handles support direct touch input.
+Keyboard users can focus a tile, press Enter or Space to start editing, use the arrow keys to move it, and use Shift plus the arrow keys to resize it.
+Press Enter, Space, or Escape to stop keyboard editing.
+Keyboard moves and resizes apply immediately; Escape stops keyboard editing without undoing those changes.
+During a pointer or touch interaction, Escape cancels the move or resize and restores the layout from before that interaction.
+The **Move / resize item** action in the edit menu remains available for precise numeric input.
 
 #### Preview
 
+Layout Settings shows a lightweight structural preview for every layout, including saved spans, Containers, widget labels, and app icons. The canvas width represents the screen range where that layout is active.
+
+Choose **Edit layout** to open the real board editor at that representative width on desktop. Save returns to Layout Settings. Cancel discards the local changes. On phones and tablets, the normal board editor continues to use the layout selected by the device width.
+
 <img src={layoutSmallImage} height={256} />
 <img src={layoutMediumImage} height={256} />
 <img src={layoutLargeImage} height={256} />
 
+### Containers and rails
+
+Containers can hold apps, widgets, and nested Containers.
+The same Container model works on the main canvas, inside a fixed rail, or inside another Container.
+Move and resize Containers directly in edit mode; nested content stays within the Container's local bounds.
+Resize outlines follow the pointer continuously while a dashed preview marks the grid size that will be applied on release.
+Each responsive layout stores its own Container position and size.
+
+Each Container can configure:
+
+- Its label and whether that label is visible.
+- Whether users can collapse and expand it like an accordion.
+- Whether its menu shows **Open all in new tabs** for the app links it contains.
+- Its border color and custom CSS classes.
+
+Collapsing a Container reduces its full-width header to a half-row expansion bar and compacts the surrounding layout without losing its expanded size.
+Expanding it smoothly restores those bounds and moves following items out of the way without reloading the widgets inside it.
+
 ### Background
 
 #### Background image URL
@@ -159,7 +249,7 @@ Change the color of your bookmark / app icons.
 
 #### Item radius
 
-Change the radius of your items / categories.
+Change the radius of your items and Containers.
 
 <img src={itemRadiusImage} height={100} />
 
@@ -168,6 +258,10 @@ Change the radius of your items / categories.
 This is the field where you can enter custom CSS.
 The styling will only be applied on the respective board page.
 
+When Homarr Assistant is enabled, users with modify permission can also ask it to edit the board's Custom
+CSS and other visual or behavior settings. The assistant reads the current stylesheet first and presents an
+editable review form before requesting approval to save the change.
+
 [See this guide on how to work with custom CSS](/docs/advanced/styling/).
 
 ### Behaviour
@@ -176,6 +270,20 @@ The styling will only be applied on the respective board page.
 
 This will disable the status check for apps.
 
+#### Work directly from the board
+
+Widgets expose their routine controls without requiring edit mode:
+
+- Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the other widgets
+  remain visible but dimmed. Release `Shift` to close it. Focus that widget and press `Shift` + `Enter` to keep the view
+  open until you close it. On touch devices, open it from the widget menu. Other widgets adapt in place instead.
+- Right-click a widget to inspect its live query status, refresh its data, change quick options, open settings, or run
+  supported actions. Available controls follow your board and integration permissions.
+- If you can modify the board, right-click or touch and hold an empty grid cell to add an item there. Focus a board
+  section and press `Shift` + `F10` for the keyboard equivalent.
+
+Widget and empty-space context menus follow the **Enable right click on widgets** preference in your user settings.
+
 ### Access control
 
 With the access control, you can permit a single user or a group to your board.

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

@@ -17,7 +17,9 @@ Install the Agent Skill from the verified Homarr repository:
 npx skills add https://github.com/homarr-labs/homarr --skill homarr-custom-widget
 ```
 
-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.
+The portable skill gives concise authoring guidance. For connected agents, Homarr returns the complete `SKILL.md` and
+all bundled skill references once in one lazy tool response. The Homarr MCP prompt then gives the agent a
+retrieval workflow: read the live schema and fetch only the component documentation needed for the widget.
 
 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.
 
@@ -37,38 +39,55 @@ Repository code cannot give this attribution.
 
 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:
+`GET /api/custom-widgets/skill` and `customWidget_getSkill` return a self-contained structured skill payload:
 
 ```ts
 {
   name: "homarr-custom-widget";
   version: string;
-  skillMd: string;
+  skillMd: string; // Complete SKILL.md
+  references: Record<string, 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.
+The `homarr://custom-widgets/skill` MCP resource returns the same `SKILL.md` and references once as bundled Markdown.
+
+The component catalog is a compact index of names, categories, safety levels, shared prop names, policies, and example
+IDs. Per-component results contain only component-specific props and a reference to shared prop documentation. Use
+`customWidget_getSharedProps` once with only the shared prop names needed across the selected components. This avoids
+repeating hundreds of global props in every tool result. The catalog is deliberately not embedded in the skill or
+clipboard prompt; the skill response still contains the complete authoring, schema, runtime, and security references.
 
 These interfaces do not return an archive URL or archive hash.
 
 ## Create a Custom Widget with MCP
 
-1. 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.
+1. Load `customWidget_getSkill`, then get the prompt and live schema.
+2. Call `customWidget_getComponentCatalog`, followed by `customWidget_getComponent` for only the relevant installed
+   components and `customWidget_getExample` when one catalog example matches the interaction pattern. If shared props
+   are needed, collect their catalog names and call `customWidget_getSharedProps` once for that set.
+3. Read the external API documentation.
+4. Build one definition, using `templateLines` for multiline JSX tool input.
+5. Validate the definition without saving it and repair every reported issue.
+6. Create a preview session.
+7. Run `customWidget_previewQuery` for every query returned by the preview and inspect its actual status and data shape.
+8. Test relevant actions in simulation mode.
+9. Open the returned preview path with browser tools.
+10. Inspect the redacted journal and revise the local candidate until validation, data, and rendering all work.
+11. Create the widget, including any source URLs and credentials the user already supplied.
+12. Open its returned management path, and use a structured question when the user must choose whether to place it on a board.
+13. Otherwise, ask the user to configure the saved definition with the ten-minute Homarr source-setup URL.
+14. Create a final preview with the saved definition ID so Homarr loads its stored credentials, then test it again.
+15. Update the saved definition if the final verification finds a problem. `customWidget_update` also accepts
+    `templateLines` for multiline JSX without resetting omitted options.
+16. Repeat the procedure for the next widget.
+
+Successful validation returns a compact summary instead of echoing the full widget and template. Preview creation
+returns its session, links, and query checklist without repeating the submitted definition. Keep the candidate locally
+and reuse it for the next lifecycle step.
 
 Each source-configuration URL applies to one definition or preview and one source. It is short-lived, single-use, and
 can only be opened and completed by an authenticated Homarr administrator. The administrator confirms the server URL,
@@ -94,11 +113,51 @@ Homarr maintainers can run the same self-contained prompt that the workbench cop
 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/`.
+The manifest suite covers nine complex and public-API prompts. Its deterministic fixture-backed cases include a fake
+homelab health API, CoinMarketCap's keyless public API, Bored, Agify, and a multi-request Pokédex. Before the configured
+model judges a result, the candidate must pass Homarr's real clipboard parser, canonical schema, and deterministic
+checks for documented endpoints, authentication, request triggers, query bindings, response fields, and essential
+runtime components.
 
-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
+To exercise the real Homarr Assistant lifecycle instead of accepting a returned JSON block, run:
+
+```sh
+OPENROUTER_API_KEY=... pnpm --filter @homarr/custom-widgets test:assistant-ai
+```
+
+The same suites can target the Homarr provider with a Workshop PocketBase token instead of an OpenRouter key:
+
+```sh
+AI_PROVIDER_BASE_URL=https://homarr.dev/api/ai/v1 \
+AI_PROVIDER_API_KEY=<workshop-token> \
+AI_PROVIDER_MODEL=homarr/model \
+pnpm --filter @homarr/custom-widgets test:assistant-ai
+```
+
+`AI_PROVIDER_JUDGE_MODEL` can select a separate judge when the configured endpoint offers one. The Homarr provider
+offers exactly one model, so generation and review both use `homarr/model`.
+
+The assistant test exposes the same lazy skill, live schema, component catalog, targeted component references,
+validation, preview-query, and create-from-preview tools as the product. It refuses to save a definition that was not
+validated exactly or whose preview queries were not all tested. Multi-request fixtures return a different payload for
+each documented path and require manual-query parameters. Use `--case=pokedex`, `--case=coinmarketcap-keyless`,
+`--case=bored-activity`, or `--case=agify-name` for a focused run.
+
+Both suites use the configured provider models for generation and harsh review. They save tool traces, validated
+manifests, raw reviews, and detailed category scores under
+`packages/custom-widgets/.ai-evaluations/`. These live tests are maintainer-invoked rather than CI-required because
+they consume a configured provider account and exercise a nondeterministic model. The repository's ordinary tests
+cover the lifecycle enforcement, fixture routing, score calculation, and failure behavior without network access.
+
+Each scenario stops as soon as it passes and has a hard limit of ten generation attempts. Override the endpoint,
+models, or per-scenario limit with `AI_PROVIDER_BASE_URL`, `AI_PROVIDER_API_KEY`, `AI_PROVIDER_MODEL`,
+`AI_PROVIDER_JUDGE_MODEL`, and
 `CUSTOM_WIDGET_AI_MAX_LOOPS`. Generated artifacts are local and ignored by Git; promote a reviewed, validated result
 into the bundled-widget source deliberately.
 
 The reference API check uses a real PokeAPI list/detail request and a read-only Portainer container query when `PORTAINER_BASE_URL` and `PORTAINER_API_KEY` are set. Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --pokeapi-only` for the public PokeAPI check alone. To exercise start, restart, and stop against a disposable container, also set `PORTAINER_TEST_CONTAINER_ID` and the explicit safeguard `PORTAINER_ALLOW_MUTATIONS=1`; the script restores the container's original running state.
+
+Use `pnpm --filter @homarr/custom-widgets test:reference-apis -- --public-ai-apis-only` to verify the live Bored and
+CoinMarketCap response shapes used by the assistant fixtures. The same command also verifies Agify when
+`AGIFY_API_KEY` is configured; otherwise it reports the authenticated check as skipped without weakening the
+deterministic Agify fixture tests.

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

@@ -40,6 +40,12 @@ interface HomarrCustomWidgetV2 {
 }
 ```
 
+### Design with AI
+
+The **Design with AI** action is available while creating or editing a custom widget. Describe what the widget should show and, when [Homarr Assistant](../assistant) is enabled, send the request directly from the form. The assistant receives the widget schema, current non-secret configuration, and latest test response, then proposes the matching create or update tool for your approval.
+
+Run **Test** first when possible so the prompt includes the endpoint's real response shape. Saved secrets are never added to the prompt. **Copy to clipboard** remains available when the Assistant is disabled or when you prefer another AI service.
+
 <CustomWidgetCodeExample
   id="complete-widget-manifest"
   label="Complete manifest"

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

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

apps/docs/docs/management/mcp.mdx

@@ -8,10 +8,19 @@ tags:
 
 # Model Context Protocol (MCP)
 
-Homarr exposes a [Model Context Protocol](https://modelcontextprotocol.io) server at `/api/mcp/mcp`, enabling AI assistants like Claude, Cursor, VS Code Copilot, and Claude Code to interact with your Homarr instance using natural language.
+Homarr exposes a [Model Context Protocol](https://modelcontextprotocol.io) server at `/api/mcp`, enabling AI assistants like Claude, Cursor, VS Code Copilot, and Claude Code to interact with your Homarr instance using natural language.
+
+The endpoint implements the stateless MCP 2026-07-28 protocol and accepts 2025 Streamable HTTP clients through a
+stateless compatibility path. It does not create protocol sessions or require sticky sessions. Homarr creates the
+server and extracts its tools only after an authenticated request reaches the route. The previous `/api/mcp/mcp` URL
+remains available as a compatibility alias, but new clients should always use `/api/mcp`.
 
 With MCP, you can ask your AI assistant to manage apps, integrations, users, boards, Docker containers, media servers, DNS settings, and more - all through Homarr's existing tRPC API, now exposed as 50+ AI-callable tools.
 
+The optional [Homarr Assistant](./assistant) uses these same tool definitions internally.
+Unlike external MCP clients, it uses the current Homarr session directly and asks for in-conversation
+approval before running mutating procedures.
+
 ## Getting Started
 
 The MCP endpoint lives under the **API** page at `Management` → `Tools` → `API` → **MCP** tab.
@@ -42,7 +51,7 @@ Add the following to your client's MCP configuration file:
 {
   "mcpServers": {
     "homarr": {
-      "url": "https://your-homarr-instance.com/api/mcp/mcp",
+      "url": "https://your-homarr-instance.com/api/mcp",
       "headers": {
         "ApiKey": "<your-api-key>"
       }
@@ -73,7 +82,7 @@ Replace `<your-api-key>` with your actual API key. Never commit API keys to vers
   "mcpServers": {
     "homarr": {
       "command": "npx",
-      "args": ["-y", "mcp-remote", "https://your-homarr-instance.com/api/mcp/mcp", "--header", "ApiKey:<your-api-key>"]
+      "args": ["-y", "mcp-remote", "https://your-homarr-instance.com/api/mcp", "--header", "ApiKey:<your-api-key>"]
     }
   }
 }
@@ -96,6 +105,10 @@ Custom Widget and Workshop authoring are different: their tools, prompts, and re
 key owner is a Homarr administrator. Non-administrator keys cannot discover or invoke those capabilities. Creating an
 API key never elevates the owner.
 
+OAuth authorization and token requests bind issued credentials to the canonical `/api/mcp` resource. Dynamic client
+registration remains available for compatibility with current MCP clients while the ecosystem transitions toward
+pre-registered clients and Client ID Metadata Documents.
+
 ## Testing the Connection
 
 Verify your MCP endpoint is working:
@@ -103,13 +116,17 @@ Verify your MCP endpoint is working:
 ```bash
 curl -s -X POST \
   -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
+  -H "Accept: application/json" \
   -H "ApiKey: <your-api-key>" \
-  -d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}},"id":1}' \
-  https://your-homarr-instance.com/api/mcp/mcp
+  -H "Mcp-Method: server/discover" \
+  -H "Mcp-Name: homarr" \
+  -d '{"jsonrpc":"2.0","method":"server/discover","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"test","version":"1.0"},"io.modelcontextprotocol/clientCapabilities":{}}},"id":1}' \
+  https://your-homarr-instance.com/api/mcp
 ```
 
-A successful response includes the server capabilities and available tools. Use `tools/list` to see all available tools:
+A successful response includes the supported protocol versions and server capabilities. Use `tools/list` to see all
+available tools. MCP v2 clients add the per-request metadata and `Mcp-Method` / `Mcp-Name` headers automatically; the
+abbreviated request below uses the stateless 2025 compatibility path for readability:
 
 ```bash
 curl -s -X POST \
@@ -117,33 +134,36 @@ curl -s -X POST \
   -H "Accept: application/json, text/event-stream" \
   -H "ApiKey: <your-api-key>" \
   -d '{"jsonrpc":"2.0","method":"tools/list","id":1}' \
-  https://your-homarr-instance.com/api/mcp/mcp
+  https://your-homarr-instance.com/api/mcp
 ```
 
+Tool catalogs are returned in deterministic order and may be cached privately by the client for five minutes. The
+removed HTTP+SSE `/sse` and `/message` transports return `410 Gone`; use the single Streamable HTTP endpoint instead.
+
 ## Available Tools
 
 Homarr exposes 50+ tools organized by namespace. Each tool is either a **query** (GET, read-only) or **mutation** (POST, write action).
 
-| Namespace          | Example Tools                                             | Type       |
-| ------------------ | --------------------------------------------------------- | ---------- |
-| `app`              | List all apps, get app by ID, create/update/delete app    | GET + POST |
-| `apiKeys`          | List API keys                                             | GET        |
-| `beszel`           | Systems status, alerts, historical system metrics         | GET        |
-| `board`            | List boards, get board by ID, create/update/delete board  | GET + POST |
-| `docker`           | List containers, inspect container, start/stop/restart    | GET + POST |
-| `icon`             | Search icons                                              | GET        |
-| `info`             | Server health, version info                               | GET        |
-| `integration`      | List integrations, test connection, delete integration    | GET + POST |
-| `invite`           | List invitations, delete invite                           | GET + POST |
-| `calendar`         | Calendar events from media servers                        | GET        |
-| `customWidget`     | Validate, preview, create, and iteratively update widgets | GET + POST |
-| `dnsHole`          | DNS hole summary, toggle blocking                         | GET + POST |
-| `downloads`        | Active downloads, pause/resume/delete                     | GET + POST |
-| `healthMonitoring` | Resource usage stats                                      | GET        |
-| `patchmon`         | Host patch and security update statistics                 | GET        |
-| `mediaRequests`    | Approve/decline media requests                            | GET + POST |
-| `mediaServer`      | Media server sessions and stats                           | GET        |
-| `smartHome`        | Execute automations, device states                        | GET + POST |
+| Namespace          | Example Tools                                              | Type       |
+| ------------------ | ---------------------------------------------------------- | ---------- |
+| `app`              | List all apps, get app by ID, create/update/delete app     | GET + POST |
+| `apiKeys`          | List API keys                                              | GET        |
+| `beszel`           | Systems status, alerts, historical system metrics          | GET        |
+| `board`            | List boards, read settings/CSS, create/update/delete board | GET + POST |
+| `docker`           | List containers, inspect container, start/stop/restart     | GET + POST |
+| `icon`             | Search icons                                               | GET        |
+| `info`             | Server health, version info                                | GET        |
+| `integration`      | List integrations, test connection, delete integration     | GET + POST |
+| `invite`           | List invitations, delete invite                            | GET + POST |
+| `calendar`         | Calendar events from media servers                         | GET        |
+| `customWidget`     | Validate, preview, create, and iteratively update widgets  | GET + POST |
+| `dnsHole`          | DNS hole summary, toggle blocking                          | GET + POST |
+| `downloads`        | Active downloads, pause/resume/delete                      | GET + POST |
+| `healthMonitoring` | Resource usage stats                                       | GET        |
+| `patchmon`         | Host patch and security update statistics                  | GET        |
+| `mediaRequests`    | Approve/decline media requests                             | GET + POST |
+| `mediaServer`      | Media server sessions and stats                            | GET        |
+| `smartHome`        | Execute automations, device states                         | GET + POST |
 
 The tools table on the MCP tab is dynamically generated - it always reflects the latest available procedures from your Homarr instance.
 
@@ -175,21 +195,36 @@ An agent creates one `homarr-custom-widget-v2` definition at a time. Start with
 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.
 
-Then, read the live schema and component resources. These resources describe the installed Mantine components.
+Load the installed skill before authoring. `customWidget_getSkill` returns the complete `SKILL.md` entrypoint and every
+bundled reference in one response, so an MCP client does not need filesystem access or a second documentation fetch.
+Then read the live schema and only the component resources required by the design. These resources describe the
+installed Mantine components.
 
-1. 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.
+1. Call `customWidget_getSkill`, `customWidget_getAuthoringPrompt`, `customWidget_schema`, and
+   `customWidget_getComponentCatalog`.
+2. Fetch only the relevant installed component documentation with `customWidget_getComponent` and, when useful,
+   one interaction example with `customWidget_getExample`. Component results contain component-specific props; collect
+   any needed shared prop names from the compact catalog and fetch them together once with `customWidget_getSharedProps`.
+3. Build one Custom Widget definition. Use `templateLines` for generated multiline JSX to avoid a fragile JSON-escaped
+   template string.
+4. Call `customWidget_validate` without saving the definition and repair every returned issue path.
+5. Call `customWidget_previewCreate`.
+6. Call `customWidget_previewQuery` for every entry in the returned `queries` list. Supply the listed invocation
+   parameters for manual queries and inspect the real HTTP status and response shape before binding template fields.
+7. Test relevant actions with `customWidget_previewAction` in simulation mode.
+8. Open the returned `previewPath` or `previewUrl`.
+9. Examine `customWidget_previewJournal`.
+10. Revise the local candidate and create another preview session until validation, query data, actions, and rendering
+    are ready.
+11. Call `customWidget_create`, supplying any credentials and deployment-specific source URLs the user already provided.
+12. Open the returned `managementPath` to review the exact saved definition.
+13. If the user must enter the source URL or credentials, call `customWidget_configurationRequestUser` with the new definition ID and wait for completion.
+14. Create a final preview with that definition ID so Homarr loads its stored credentials, then test it again.
+15. Use `customWidget_update` or `customWidget_templatePatch` for any final saved-definition corrections.
+16. Repeat this procedure for the next Custom Widget.
+
+Validation and preview creation return compact lifecycle metadata. They do not echo the submitted widget or duplicate
+its template as both a string and line array; the agent should retain and reuse its local candidate.
 
 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.
 
@@ -225,6 +260,10 @@ The Custom Widget tools are:
 - `customWidget_workshopGet`
 - `customWidget_workshopInstall`
 - `customWidget_getAuthoringPrompt`
+- `customWidget_getComponentCatalog`
+- `customWidget_getComponent`
+- `customWidget_getSharedProps`
+- `customWidget_getExample`
 - `customWidget_getSkill`
 
 Custom Widget permissions are not assignable group capabilities. Administrator status is required for the complete

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

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

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

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

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

@@ -25,6 +25,11 @@ import piHoleApp from "./img/pi-hole-ping-icon.png";
   <img src={piHoleApp} alt="app pi-hole with-status-check status-check-icon" width={128 * 1.5} height={128 * 1.5} />
   <img src={jellyseerrApp} alt="app jellyseerr with-description-tooltip" height={128 * 1.5} />
 </div>
+
+### Interactions
+
+App tiles stay compact and open their configured destination directly. Right-click a tile to inspect its status or change its settings when the board and your preferences allow it.
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/archive-team-warrior/index.mdx

@@ -0,0 +1,38 @@
+---
+title: "ArchiveTeam Warrior"
+description: "Monitor ArchiveTeam Warrior status, projects, bandwidth, and active archival jobs."
+hide_title: true
+---
+
+import { archiveTeamWarriorIntegration } from "@site/docs/integrations/archiveteam-warrior";
+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 { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+import { archiveTeamWarriorWidget } from ".";
+
+<WidgetHeader widget={archiveTeamWarriorWidget} categories={["Archiving", "Monitoring"]} />
+
+Use this widget to see what your ArchiveTeam Warrior is preserving without leaving Homarr. The compact view keeps the current project, runner state, job counts, bandwidth, and optional broadcast message visible. Advanced view adds the complete active-job list, job start times, project and bandwidth-session identifiers, session transfer totals, exact update time, and the full broadcast message whenever one is available. A failed refresh keeps the last snapshot visible with a stale-data warning.
+
+### Supported integration
+
+<WidgetIntegrations
+  items={[
+    {
+      integration: archiveTeamWarriorIntegration,
+      note: "Shows status and active archival work from one Warrior instance",
+    },
+  ]}
+/>
+
+<WidgetInteractionGuide />
+
+### Adding the widget
+
+<AddingWidget />
+
+### Configuration
+
+<WidgetConfig configuration={archiveTeamWarriorWidget.configuration} />

apps/docs/docs/widgets/archive-team-warrior/index.ts

@@ -0,0 +1,19 @@
+import type { WidgetDefinition } from "@site/src/types";
+import { IconArchive } from "@tabler/icons-react";
+
+export const archiveTeamWarriorWidget: WidgetDefinition = {
+  icon: IconArchive,
+  name: "ArchiveTeam Warrior",
+  description: "Monitor ArchiveTeam Warrior status, projects, bandwidth, and active archival jobs.",
+  path: "../../widgets/archive-team-warrior",
+  configuration: {
+    items: [
+      {
+        name: "Show broadcast message",
+        description: "Show the message broadcast by the selected Warrior project when space allows.",
+        values: { type: "boolean" },
+        defaultValue: "yes",
+      },
+    ],
+  },
+};

apps/docs/docs/widgets/assistant/index.mdx

@@ -0,0 +1,59 @@
+---
+title: "Assistant"
+description: "Have a complete assistant conversation directly on a board."
+hide_title: true
+---
+
+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 { assistantWidget } from ".";
+
+<WidgetHeader widget={assistantWidget} categories={["Productivity"]} />
+
+The Assistant widget brings the same conversation available from the user menu and command menu onto a
+board. Messages, conversations, tool calls, approvals, files, mentions, model controls, reasoning controls,
+usage details, and response actions remain synchronized with the app-wide assistant.
+
+The assistant must be enabled by an administrator in **Management → Assistant**. Signed-out users and users
+on an instance without an enabled model see an unavailable state instead of a broken composer.
+
+### Adding the widget
+
+<AddingWidget />
+
+The default widget size is ten columns by four rows and automatically fits boards with fewer columns. Controls
+and labels condense as the widget becomes narrower, while the conversation remains scrollable and usable on
+touch devices. When a board layout does not provide enough height for conversation controls, the widget shows
+a compact **Open assistant** action instead of squeezing an unusable composer into the card. Increase its height
+in that layout to keep the complete conversation inline.
+
+### Configuration
+
+<WidgetConfig configuration={assistantWidget.configuration} />
+
+**Current conversation** follows whichever conversation is active in the user-menu panel, `Shift + A`, or
+the command menu. This is the default and keeps every assistant entry point synchronized.
+
+**Pinned conversation** reveals a searchable conversation selector. A pinned widget never changes the
+active conversation silently: select **Open conversation** inside the widget before continuing that thread.
+
+### Conversation features
+
+- Create, switch, rename, and delete conversations.
+- Send text and supported file or image attachments by picker, drag and drop, or image paste.
+- Mention permitted apps, integrations, boards, widgets, and tools with `@`.
+- Use `/` shortcuts for common dashboard tasks.
+- Review tool calls, approve mutations, and answer structured assistant questions inline.
+- Answer pending structured questions from the dock above the composer without scrolling through the conversation.
+- Enable conversation-scoped automatic approvals from the shield control to approve protected mutations, use presented form details, and choose answers categorized as affirmative without individual clicks.
+- Edit user messages and copy, regenerate, branch, quote, export, or rate responses.
+- Inspect syntax-highlighted Markdown, sources, generated files, tool results, streaming chain-of-thought,
+  cumulative conversation usage, per-turn token and context use, timing, speed, provider routing, and cost.
+- Change the model and reasoning effort for the active conversation.
+- Refresh the current board from the conversation header. Approved mutations also refresh visible board data automatically.
+
+The expanded assistant and board widget use the same persisted thread runtime. A response continues in the
+background when the widget leaves the viewport or the expanded panel is minimized. Each visible surface keeps an
+independent draft, attachments, selection, and focus, so typing in a board widget cannot move or overwrite the
+floating panel composer.

apps/docs/docs/widgets/assistant/index.ts

@@ -0,0 +1,25 @@
+import type { WidgetDefinition } from "@site/src/types";
+import { IconRobot } from "@tabler/icons-react";
+
+export const assistantWidget: WidgetDefinition = {
+  icon: IconRobot,
+  name: "Assistant",
+  description: "Have a complete assistant conversation directly on a board.",
+  path: "../../widgets/assistant",
+  configuration: {
+    items: [
+      {
+        name: "Conversation",
+        description: "Follow the active conversation or attach the widget to one persisted conversation.",
+        values: { type: "select", options: ["Current conversation", "Pinned conversation"] },
+        defaultValue: "Current conversation",
+      },
+      {
+        name: "Pinned conversation",
+        description: "Search for a conversation. This field is hidden when Current conversation is selected.",
+        values: { type: "string" },
+        defaultValue: "",
+      },
+    ],
+  },
+};

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

@@ -4,6 +4,8 @@ description: "Displays media and listening statistics from Navidrome or Audioboo
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -36,6 +38,8 @@ Only options relevant to your linked integration are shown in the configuration
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/bazarr/index.mdx

@@ -4,6 +4,8 @@ description: "Displays missing subtitle counts and health indicators from your B
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -34,6 +36,10 @@ import widgetOverview from "./img/widget-overview.png";
   ]}
 />
 
+Advanced view shows every missing-subtitle and health summary regardless of compact visibility options, together with the already-fetched Sonarr and Radarr SignalR states and announcement count.
+
+<WidgetInteractionGuide advancedView />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/beszel-alerts/index.mdx

@@ -4,6 +4,8 @@ description: "View Beszel alert configurations and history with triggered/ok sta
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -32,6 +34,8 @@ This widget displays your Beszel alert configurations separated by status (trigg
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -4,6 +4,8 @@ description: "Card grid view of all Beszel-monitored systems with real-time metr
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -34,6 +36,8 @@ Select a system card to open the complete statistics view, including system, fil
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -4,6 +4,8 @@ description: "Time-series charts for CPU, memory, disk, network, and Docker cont
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -15,7 +17,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. Hover over or focus the widget controls to switch between the realtime Live view and historical periods 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.
 
 ### Screenshots
 
@@ -32,6 +34,8 @@ This widget displays time-series charts for a selected Beszel system, including
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -4,6 +4,8 @@ description: "Table view of all Beszel-monitored systems with sortable columns a
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -13,9 +15,9 @@ 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. System and load-average status dots are displayed inline with their values. 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.
 
-Select a system row to open the complete statistics view, including system, filesystem, Docker, historical, and realtime charts.
+Select a system row to open the complete statistics view.
 
 ### Interactions
 
@@ -35,6 +37,8 @@ Select a system row to open the complete statistics view, including system, file
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -4,6 +4,8 @@ description: "Displays multiple app links"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -13,18 +15,20 @@ 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.
+Its normal view adapts each configured layout to the available width and height: lower-priority hostnames are hidden before names or icons, and larger collections scroll instead of crushing cards.
+Advanced view shows every bookmark as a roomy card with its full title, hostname, icon, and complete description regardless of the compact layout and visibility choices.
 
 ### Screenshots
 
 import gridIconsOnly from "./img/grid-icons-only.png";
 import gridWithTitle from "./img/grid-with-title.png";
 import verticalListAll from "./img/vertical-list-all.png";
-import vericalListSimple from "./img/vertical-list-simple.png";
+import verticalListSimple from "./img/vertical-list-simple.png";
 
 <div className='flex gap-1'>
     <div className='flex flex-col gap-1'>
         <img src={gridIconsOnly} alt="bookmarks grid icons-only" width={128} height={128} />
-        <img src={vericalListSimple} alt="bookmarks vertical-list no-domain" width={128} height={128} />
+        <img src={verticalListSimple} alt="bookmarks vertical-list no-domain" width={128} height={128} />
     </div>
 
     <img src={gridWithTitle} alt="bookmarks grid with-title" width={256 + 4} height={256 + 4} />
@@ -32,6 +36,8 @@ import vericalListSimple from "./img/vertical-list-simple.png";
 
 </div>
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/calendar/index.mdx

@@ -4,6 +4,8 @@ description: "Display events from your integrations in a calendar view within a
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -24,6 +26,8 @@ import { icalIntegration } from "@site/docs/integrations/ical";
 
 The calendar widget shows a month view of events from different integrations.
 It allows you to view calendar events or upcoming releases from your media managers.
+Calendar requests use normal human month numbers (`1` for January through `12` for December), including when
+the same data is requested through Homarr's MCP or Assistant tools.
 
 ### Screenshots
 
@@ -70,8 +74,10 @@ import withoutIntegrations from "./img/without-integrations.png";
 ### Interactions
 
 - Hover over a marked date to preview its events in a popover.
-- Click on a marked date to pin the popover open (it will stay visible even after moving the mouse away).
-- Click the date again or click outside to close the pinned popover.
+- The advanced view replaces the month grid with a grouped event list, keeps every event attributed to its source integration, and expands titles, locations, and descriptions. Use its previous and next controls to change months.
+- If one selected integration is unavailable, its warning indicator remains visible while events from healthy integrations continue to load.
+
+<WidgetInteractionGuide />
 
 ### Adding the widget
 

apps/docs/docs/widgets/clock/index.mdx

@@ -4,6 +4,8 @@ description: "Displays the current date and time."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -25,6 +27,8 @@ import tokyoClock from "./img/tokyo-12-hour.png";
   <img src={tokyoClock} alt="clock format-12-hours timezone-tokyo" width={256} height={128} />
 </div>
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/coolify/index.mdx

@@ -4,6 +4,8 @@ description: "Overview of your Coolify instance with servers, applications, and
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -25,6 +27,12 @@ The Coolify widget displays a compact overview of your Coolify instance. It can
   ]}
 />
 
+Advanced view opens the Servers, Applications, and Services sections regardless of their compact visibility switches. It identifies each Coolify integration, shows server `is_reachable` and `is_usable` values, and lists applications nested in services when the API provides them. Healthy integrations remain visible if another source fails, with the failed source identified by a warning.
+
+IP addresses remain masked in advanced view until you explicitly use the eye control. Public resource, Coolify dashboard, and log links retain the widget's safe new-tab handling.
+
+<WidgetInteractionGuide advancedView />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -1,24 +1,26 @@
 ---
 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 a custom API endpoint using configurable display types and optional JSX templates."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { 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.
 
-### Add the widget
+<WidgetInteractionGuide advancedView={false} />
+
+### Adding the widget
 
 <AddingWidget />
 
@@ -29,9 +31,8 @@ Select a refresh interval. The board item stores the definition ID and the valid
 Credentials remain on the server.
 
 :::note
-
-Enable the definition before you use it. The definition must also be available to the board.
-
+Custom API widgets must first be created in **Management → Custom Widgets** before they appear in the widget picker.
+Action buttons can only be executed by administrators.
 :::
 
 ### Permissions and actions

apps/docs/docs/widgets/dns-hole-controls/index.mdx

@@ -1,9 +1,11 @@
 ---
 title: "DNS Hole Controls"
-description: "Control PiHole or AdGuard from your dashboard."
+description: "Control Pi-hole, AdGuard Home, or Technitium DNS from your dashboard."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -18,7 +20,9 @@ import { technitiumDnsIntegration } from "@site/docs/integrations/technitium-dns
 
 <WidgetHeader widget={dnsHoleControlsWidget} categories={["DNS Hole"]} />
 
-This widget allows you to enable or disable your DNS Hole.
+When several DNS integrations are selected, Homarr keeps healthy controls available if one source fails and shows a warning identifying the unavailable integration.
+
+This widget lets permitted users enable, disable, or temporarily pause one or more DNS services. It shares the summary query and cache with DNS Hole Summary. Every selected source stays available in the normal scrollable view, while cards and controls adapt to the widget&apos;s width and height.
 
 ### Screenshots
 
@@ -46,9 +50,12 @@ import smallSize from "./img/small.png";
 
 ### Interactions
 
-- Enable / Disable one dns-hole by clicking on the badge.
-- Disable one dns-hole in x seconds by clicking on the clock icon.
-- Do all of the above for all dns-holes by using the top button row.
+- Enable or disable one DNS service by clicking its status badge.
+- Temporarily disable one service with the clock action.
+- Apply an action to all available services from the top action row. Homarr keeps successful results visible and reports how many sources failed.
+- Interaction controls only appear when the current user has permission for that integration.
+
+<WidgetInteractionGuide advancedView={false} />
 
 ### Adding the widget
 

apps/docs/docs/widgets/dns-hole-summary/index.mdx

@@ -4,6 +4,8 @@ description: "Displays the summary of your DNS Hole."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -15,7 +17,9 @@ import { dnsHoleSummaryWidget } from ".";
 
 <WidgetHeader widget={dnsHoleSummaryWidget} categories={["DNS Hole"]} />
 
-This widget allows you to display statistics about your DNS Hole like total queries, blocked queries, and more.
+When several DNS integrations are selected, Homarr keeps healthy sources visible if one source fails and shows a warning identifying the unavailable integration.
+
+This widget combines statistics from every selected DNS service, including total queries, blocked queries, and blocklist size. Its data is cached under the same DNS query family as DNS Hole Controls, so placing both widgets on a board does not create a second integration request. When the widget has enough room, it adds a scrollable status row naming each selected source.
 
 ### Screenshots
 
@@ -50,6 +54,8 @@ import { technitiumDnsIntegration } from "@site/docs/integrations/technitium-dns
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -4,6 +4,8 @@ description: "Allows you to view and manage your Downloads from both Torrent and
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { aria2Integration } from "@site/docs/integrations/aria2";
 import { delugeIntegration } from "@site/docs/integrations/deluge";
 import { nzbgetIntegration } from "@site/docs/integrations/nzbget";
@@ -43,7 +45,7 @@ import contextMenuImg from "./img/context-menu.png";
 - **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
+- **Hover tooltips** — hover a download name to see size, speeds, ETA, ratio, and category; open tooltips close when switching between compact and advanced mode
 - **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
@@ -95,6 +97,8 @@ import contextMenuImg from "./img/context-menu.png";
 - **Filter** by integration or status using the filter button in the footer
 - **Sort** by clicking column headers (with persistent sort direction)
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/firewall/index.mdx

@@ -4,6 +4,8 @@ description: "Displays a summary of firewalls."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
@@ -28,6 +30,8 @@ import { opnsenseIntegration } from "../../integrations/opnsense";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/health-monitoring/index.mdx

@@ -4,6 +4,8 @@ description: "Displays information showing the health and status of your system(
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -21,6 +23,8 @@ import { glancesIntegration } from "@site/docs/integrations/glances";
 
 This widget displays information about the health and status of your system(s), including CPU, memory, disk usage, and more.
 
+Advanced view is a complete health workspace: it shows every available CPU, temperature, memory, GPU, filesystem, update, reboot, and system-information section even when compact visibility switches hide some of them on the board. Proxmox clusters likewise show uptime, CPU, memory, and every node, VM, container, and storage section. Storage-volume filters, units, and permissions remain in effect.
+
 ### Screenshots
 
 import systemView from "./img/system-view.png";
@@ -62,6 +66,8 @@ import { synologyIntegration } from "@site/docs/integrations/synology";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/iframe/index.mdx

@@ -4,6 +4,8 @@ description: "Embed any content from the internet. Some websites may restrict ac
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -26,6 +28,8 @@ import youtubeStream from "./img/nasa-iss-stream.png";
   <img src={youtubeStream} alt="iframe youtube-iss-stream" width={128 * 3} />
 </div>
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />
@@ -35,13 +39,14 @@ import youtubeStream from "./img/nasa-iss-stream.png";
 Although you can integrate many websites, some may not work.
 This is because the administrators of those sites disallow iframes
 for security reasons, as users could easily be tricked
-by embeding the original site on a malicious page.
+by embedding the original site on a malicious page.
 
 Some proxies disallow iframes by default for this reason.
-You can use https://iframetest.com to check, if the site is allowing iframes.
+You can use https://iframetest.com to check whether the site allows iframes.
 
 If you manage all of your own applications, you can usually change that by configuring
-the appropriate headers (such as `X-Frame-Options` or `Content-Security-Policy`) to allow iframes.
+the `Content-Security-Policy` header and its `frame-ancestors` directive. The obsolete
+`X-Frame-Options: ALLOW-FROM` directive is not supported by modern browsers.
 
 For example, to allow your site to be embedded in iframes from specific domains:
 
@@ -49,14 +54,12 @@ For example, to allow your site to be embedded in iframes from specific domains:
 
 ```apache
 Header set Content-Security-Policy "frame-ancestors 'self' https://trusted-domain.com"
-Header set X-Frame-Options "ALLOW-FROM https://trusted-domain.com"
 ```
 
 **Nginx:**
 
 ```nginx
 add_header Content-Security-Policy "frame-ancestors 'self' https://trusted-domain.com";
-add_header X-Frame-Options "ALLOW-FROM https://trusted-domain.com";
 ```
 
 ### Example URLs
@@ -82,11 +85,11 @@ To create a transparent iframe like below you can use the following html code an
 
 ![transparent iframe](./img/transparent-iframe.png)
 
-### Third party content
+### Third-party content
 
 :::warning
 
-The content below is an overview of third party projects. All support requests/problems must be redirected to the appropriate repository.
+The content below is an overview of third-party projects. All support requests/problems must be redirected to the appropriate repository.
 We cannot guarantee the functionality nor security of these tools.
 
 :::

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

@@ -4,6 +4,8 @@ description: "Shows a slideshow of pictures from an Immich album or your full li
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { immichIntegration } from "../../integrations/immich";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -29,6 +31,10 @@ import screen from "./img/screen.png";
   ]}
 />
 
+<WidgetInteractionGuide />
+
+Hover or focus the widget to pause its slideshow; touch devices keep the control available. A paused slideshow keeps its resume control visible. The advanced view displays the complete photo without cropping, groups previous, pause or resume, and next together, and includes every loaded photo in its thumbnail strip. If an Immich refresh fails, the last loaded album stays visible with a stale-data warning.
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/immich-server-stats/index.mdx

@@ -4,6 +4,8 @@ description: "Information about your Immich instance"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { immichIntegration } from "../../integrations/immich";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -29,6 +31,10 @@ import screen from "./img/screen.png";
   ]}
 />
 
+In advanced mode, the widget also ranks the largest albums by asset count. To keep the dashboard response lightweight, it shows up to 50 albums.
+
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/indexer-manager/index.mdx

@@ -4,6 +4,8 @@ description: "View the status of your indexers."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
@@ -37,6 +39,8 @@ import { prowlarrIntegration } from "@site/docs/integrations/prowlarr";
 
 - Test all indexers by clicking on the test button.
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -4,6 +4,8 @@ description: "Track missing media and active downloads from Radarr and Sonarr"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -16,6 +18,8 @@ import { sonarrIntegration } from "@site/docs/integrations/sonarr";
 
 Monitor which movies and episodes are missing from your library, and track what is currently being downloaded. The widget pulls data from Radarr and Sonarr and groups results by type in two tabs.
 
+Advanced view always shows both Missing and Queued panels side by side when space allows, requests at least 50 items per source, exposes queue status and time remaining, and keeps partial-integration warnings visible. Compact tab visibility and page-size choices continue to shape the board tile.
+
 ### Screenshots
 
 import widgetMissing from "./img/missing.png";
@@ -58,6 +62,8 @@ The widget adapts to its container size, so it looks good at any grid size:
 
 Each item shows its poster art (with the artwork bleeding softly behind the card), a type badge, and — on the queue — an animated progress bar with the estimated time remaining.
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -1,9 +1,11 @@
 ---
 title: "Media releases"
-description: "Display newly added medias or upcoming releases from different integrations"
+description: "Display newly added media or upcoming releases from different integrations"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -17,6 +19,10 @@ import { plexIntegration } from "@site/docs/integrations/plex";
 
 Provides a list of newly added media or upcoming releases from your media server.
 
+Releases retain the name and icon of the integration that supplied them. If one integration is unavailable, releases from healthy integrations remain visible and a warning identifies the failed source without exposing connection details. The widget reports an error only when every selected integration fails.
+
+Advanced view displays every release in a roomy poster layout with its complete available metadata, description, tags, and visible source name, regardless of the compact layout and visibility options.
+
 ### Screenshots
 
 import backdrop from "./img/backdrop.png";
@@ -43,6 +49,8 @@ import poster from "./img/poster.png";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/media-request-list/index.mdx

@@ -4,6 +4,8 @@ description: "See a list of all media requests from your integration"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -44,6 +46,9 @@ import mediaRequestList from "./img/list.png";
 
 - Approve / decline a request by clicking on the thumbs up or down icon.
 - Hover over the widget to reveal a **search button** that opens Spotlight in media request search mode, scoped to the widget's integrations.
+- A warning indicator identifies unavailable integrations without hiding requests returned by healthy integrations.
+
+<WidgetInteractionGuide advancedView={false} />
 
 ### Adding the widget
 

apps/docs/docs/widgets/media-request-stats/index.mdx

@@ -4,6 +4,8 @@ description: "Statistics about your media requests"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -17,7 +19,7 @@ import { overseerrIntegration } from "@site/docs/integrations/overseerr";
 
 <WidgetHeader widget={mediaRequestStatsWidget} categories={["Media requests"]} />
 
-Provide a statistics overview of your media requests, such as mount of requests, open requests, approvement and rejections.
+Provides an overview of media requests, including totals, availability, approvals, and rejections. Resize the widget to reveal denser stat tiles; the user ranking remains scrollable instead of being truncated.
 
 ### Supported Integrations
 
@@ -41,6 +43,9 @@ import mediaRequestStats from "./img/stats.png";
 ### Interactions
 
 - Hover over the widget to reveal a **search button** that opens Spotlight in media request search mode, scoped to the widget's integrations.
+- A warning indicator identifies unavailable integrations while totals from healthy integrations remain visible.
+
+<WidgetInteractionGuide advancedView={false} />
 
 ### Adding the widget
 

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

@@ -4,6 +4,8 @@ description: "Show the current streams on your media servers"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -19,8 +21,12 @@ import { plexIntegration } from "@site/docs/integrations/plex";
 
 <WidgetHeader widget={mediaServerWidget} categories={["Media server"]} />
 
-The media server widget enables you to watch and view current active sessions over all your media servers.
-It also displays useful information, that you can use when providing support to users or debugging a problem.
+The media server widget shows active sessions across your media servers.
+It shows playback progress, pause state, time remaining, and whether each session is direct play, direct stream, or transcoding audio or video. Location and bitrate can be toggled independently.
+
+Select a session to inspect its media metadata in an anchored popover. Advanced mode adds search, sorting, location, bitrate, and a summary of playing and transcoding sessions while keeping separate integration instances identifiable. Compact visibility switches do not hide location or bitrate from the complete advanced session view.
+If one selected server is unavailable, a warning indicator identifies the degraded result while sessions from healthy servers remain usable.
+Sessions without user metadata remain visible and are labeled as an unknown user.
 
 ### Screenshots
 
@@ -48,6 +54,7 @@ import mediaTable from "./img/table.png";
     },
   ]}
 />
+<WidgetInteractionGuide />
 
 ### Adding the widget
 

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

@@ -4,6 +4,8 @@ description: "Statistics, current queue and worker status of your media transcod
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -18,6 +20,7 @@ import { tdarrIntegration } from "@site/docs/integrations/tdarr";
 
 The media transcoding widget provides you with an overview of your media transcoding status.
 It shows you the current queue, worker status, and statistics about your transcoding jobs.
+Advanced view presents all three panels together. If refreshes fail after data has loaded, Homarr keeps the last useful result visible and marks it as stale.
 
 ### Screenshots
 
@@ -41,6 +44,8 @@ import statisticsCard from "./img/statistics.png";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/minecraft-server-status/index.mdx

@@ -4,6 +4,8 @@ description: "Displays the status of a Minecraft server."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -24,9 +26,11 @@ import bedrockItem from "./img/bedrock.png";
 
 <div className="flex gap-1">
   <img src={javaItem} alt="minecraft-server-status java-edition" width={128 * 1.5} height={128 * 1.5} />
-  <img src={bedrockItem} alt="minecraft-server-status bedrock-editon" width={128 * 1.5} height={128 * 1.5} />
+  <img src={bedrockItem} alt="minecraft-server-status bedrock-edition" width={128 * 1.5} height={128 * 1.5} />
 </div>
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />
@@ -38,4 +42,4 @@ import bedrockItem from "./img/bedrock.png";
 ### Data source
 
 We use the Minecraft Server Status API to fetch the server status.
-If you need to whitelist the api, please use the following URL: `hhttps://api.mcsrvstat.us`
+If you need to whitelist the API, use the following URL: `https://api.mcsrvstat.us`.

apps/docs/docs/widgets/network-controller-status/index.mdx

@@ -4,6 +4,8 @@ description: "Display connected devices on a network"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { unifiControllerIntegration } from "@site/docs/integrations/unifi-controller";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -18,6 +20,8 @@ import { networkControllerStatusWidget } from ".";
 
 Shows connected users and connected guest devices on wired or wireless networks.
 
+Compact view aggregates the configured controllers into the selected Wi-Fi or wired total. Advanced view shows both totals separately for every controller, preserving each integration's name, type, and exact update time while keeping partial-source and stale-data warnings visible.
+
 ### Screenshots
 
 import wifiCard from "./img/wifi.png";
@@ -36,6 +40,8 @@ import wiredCard from "./img/wired.png";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/network-controller-summary/index.mdx

@@ -4,6 +4,8 @@ description: "Displays the summary of a Network Controller"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { unifiControllerIntegration } from "@site/docs/integrations/unifi-controller";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -16,7 +18,7 @@ import { networkControllerSummaryWidget } from ".";
 
 <WidgetHeader widget={networkControllerSummaryWidget} categories={["Network controller"]} />
 
-Shows information whether your WAN is connected, Wi-Fi is active and several other information.
+Shows whether your WAN, internet, Wi-Fi, LAN, and VPN are available. Wider or taller layouts progressively reveal latency, ping, and connected-client counts without a separate view.
 
 ### Screenshots
 
@@ -34,6 +36,10 @@ import summaryCard from "./img/summary.png";
   ]}
 />
 
+In advanced view, each controller gets its own information matrix showing source, last update, WAN and web status, latency, ping, web uptime, separate Wi-Fi and LAN user and guest counts, and connected VPN users. The compact board view keeps its progressive aggregate layout.
+
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/notebook/index.mdx

@@ -4,6 +4,8 @@ description: "A simple notebook widget that supports markdown."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -24,6 +26,8 @@ import editOn from "./img/edit.png";
   <img src={editOn} alt="notebook edit-on" width={128 * 3} />
 </div>
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />
@@ -34,7 +38,7 @@ import editOn from "./img/edit.png";
 
 ### Editing
 
-When the permissions of the user allows it, you can enter the editing of the text by clicking the following button in the top right.
+When your permissions allow it, hover the widget, focus within it, or use a touch device to reveal the edit button in the top right. You can also double-click the document to edit it directly.
 
 ![](./img/notebook-enter-editing.webp)
 

apps/docs/docs/widgets/notifications/index.mdx

@@ -4,6 +4,8 @@ description: "Display notification history from an integration"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -32,6 +34,10 @@ import notificationsScreenshot from "./img/notifications.png";
   items={[{ integration: ntfyIntegration }, { integration: nextcloudIntegration }, { integration: gotifyIntegration }]}
 />
 
+Advanced view always shows available notification logos and sources and removes the compact body line limit. External notification links retain the same safe new-tab behavior.
+
+<WidgetInteractionGuide advancedView />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/paperless-ngx/index.mdx

@@ -4,6 +4,8 @@ description: "Displays document management statistics including inbox ratio, doc
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -26,6 +28,8 @@ This widget displays statistics from your Paperless-ngx instance, including an i
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/patchmon/index.mdx

@@ -4,6 +4,8 @@ description: "Displays host patch statistics from PatchMon including update and
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -70,6 +72,10 @@ The widget adapts its layout based on the available space:
 
 When the widget has enough space, a "last updated" timestamp appears at the bottom showing how recently PatchMon refreshed its data. Narrow layouts use a shortened timestamp such as `5m ago`; wider short layouts can show the full translated text.
 
+### Advanced view
+
+Advanced view is a complete PatchMon posture view. It always shows the compliance hero, all eight host and package statistics, the full OS distribution with versions, and the last-updated time. Compact visibility switches and OS limits still shape the board tile, but do not hide already-fetched security information in advanced view. Threshold and chart-style choices remain in effect.
+
 ### Supported Integrations
 
 <WidgetIntegrations
@@ -81,6 +87,8 @@ When the widget has enough space, a "last updated" timestamp appears at the bott
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/releases/index.mdx

@@ -4,6 +4,8 @@ description: "Displays a list of the current version of the given repositories w
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -33,6 +35,10 @@ GitHub, Docker Hub, GitLab, NPM, Codeberg, GitHub Container Registry, Quay, and
 For GitHub Container Registry, use `owner/package` identifiers such as `homarr-labs/homarr`.
 Full image references such as `ghcr.io/homarr-labs/homarr:latest` are also accepted.
 
+Advanced view shows every configured repository even when compact view is limited to highlighted or top releases. Repository names and details remain visible, and selecting a repository still expands its description and links.
+
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/rss-feed/index.mdx

@@ -4,6 +4,8 @@ description: "Monitor and display one or more generic RSS, ATOM or JSON feeds."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -19,6 +21,10 @@ import screenshot from "./img/screenshot.png";
 
 <img src={screenshot} alt="rss-feed noted-lol" width={128 * 4} />
 
+Advanced view keeps the configured feeds and post limit unchanged while showing each fetched post's full description, image, source, relative time, and exact publication timestamp. Right-to-left text and safe external links continue to follow the widget configuration.
+
+<WidgetInteractionGuide advancedView />
+
 ### Adding the widget
 
 <AddingWidget />
@@ -27,6 +33,8 @@ import screenshot from "./img/screenshot.png";
 
 <WidgetConfig configuration={rssFeedWidget.configuration} />
 
+If one configured feed fails, the widget keeps entries from healthy feeds visible and shows a warning. If a refresh fails after entries have loaded, the previous entries stay visible with a stale-data warning.
+
 ### Examples
 
 Here's a small collection of examples, that you can use for testing or actual use (in no particular order):

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

@@ -4,6 +4,8 @@ description: "Display the state of an entity and toggle it optionally"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -20,6 +22,8 @@ The entity state enables you to display the current state of an entity.
 This works with most entities and enables you display almost any data.
 It is recommended that you transform data on the integration as much as possible since Homarr's capabilities in transformation are very limited.
 
+Advanced view shows the safe Home Assistant metadata owned by Homarr: the friendly name, entity ID, unit, device class, icon, last-changed time, and last-updated time. Arbitrary attributes remain intentionally excluded.
+
 ### Screenshots
 
 import sun from "./img/sun.png";
@@ -43,6 +47,9 @@ import temperature from "./img/temperature.png";
 ### Interactions
 
 - Toggle entity state by clicking on the entity (only when clickable enabled).
+- If Homarr cannot refresh an entity, the last known state stays visible but toggling is disabled until the connection recovers.
+
+<WidgetInteractionGuide />
 
 ### Adding the widget
 

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

@@ -4,6 +4,8 @@ description: "Trigger an automation with one click"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -18,6 +20,8 @@ import { homeAssistantIntegration } from "@site/docs/integrations/home-assistant
 
 The execute automation widget allows you to trigger an automation with one click.
 
+Advanced view shows the automation ID, interaction permission, last successful run in the current browser session, and the latest action error together. Session-only history is not presented as Home Assistant history.
+
 ### Screenshots
 
 import empty from "./img/empty.png";
@@ -47,6 +51,8 @@ import withDisplayname from "./img/with-displayname.png";
 
 - Trigger the automation by clicking on the widget.
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/speedtest-tracker/index.mdx

@@ -4,6 +4,8 @@ description: "Displays speed test results from your Speedtest Tracker instance."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -16,6 +18,10 @@ import { speedtestTrackerIntegration } from "@site/docs/integrations/speedtest-t
 This widget displays internet speed test results from your [Speedtest Tracker](https://docs.speedtest-tracker.dev/) instance,
 including the latest result, historical averages, and a live chart of the last 12 hours.
 
+Advanced view renders a source-labeled panel for every healthy integration. Each panel exposes that source's latest test, statistics, speed and ping charts, plus 12-hour, 24-hour, and truthful **Last 30** result ranges regardless of compact visibility switches. Compact mode keeps the responsive aggregate overview and names its healthy sources when multiple integrations are selected.
+
+When multiple Speedtest Tracker integrations are selected, results from healthy sources remain visible if another source fails. A warning indicator identifies each unavailable integration without exposing private request details. If every selected integration fails, the widget reports an error; if cached data remains visible after a later total failure, a stale-data warning is shown.
+
 ### Screenshots
 
 import screenshot from "./img/screenshot.png";
@@ -32,6 +38,8 @@ import screenshot from "./img/screenshot.png";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/stock-price/index.mdx

@@ -4,6 +4,8 @@ description: "Displays the current stock price of a company."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -12,6 +14,9 @@ import { stockPriceWidget } from ".";
 <WidgetHeader widget={stockPriceWidget} categories={["Finance", "Market"]} />
 
 Using the Stocks widget, you can show the current stock prices of your favorite companies on your dashboard.
+The widget prioritizes the symbol, current price, and trend. Company name, change, time range, and a taller chart appear progressively when both widget dimensions can support them.
+
+In advanced view, the widget always shows the returned symbol and company name, configured range and interval, current and previous close, absolute and percentage change, range minimum and maximum, and the full price-history chart. These values use the same configured Yahoo Finance query as the compact widget; advanced view does not change the symbol, range, or interval.
 
 ### Screenshots
 
@@ -31,6 +36,8 @@ import nvidia from "./img/nvidia.png";
   <img src={nvidia} alt="stock-price nvidia" width={128 * 2 + 2} height={128 * 2 + 4} />
 </div>
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/system-disks/index.mdx

@@ -4,6 +4,8 @@ description: "Disk usage of your system"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -42,6 +44,10 @@ This widget displays filesystem and SMART disk usage for supported server and NA
   ]}
 />
 
+Advanced view keeps your configured volume filters while showing each integration name, usage percentage, used and total space, free-space percentage, SMART status, available temperature, and the usage background bar regardless of compact display options.
+
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/system-resources/index.mdx

@@ -4,6 +4,8 @@ description: "Displays CPU, RAM and network of your host in real time"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -65,6 +67,8 @@ import { synologyIntegration } from "@site/docs/integrations/synology";
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/timetable/index.mdx

@@ -4,6 +4,8 @@ description: "Displays departure times for a station."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -23,6 +25,8 @@ import streetDepartures from "./img/street-departures.png";
   <img src={streetDepartures} alt="timetable-widget-bus-and-tram-departures" width={128 * 2} />
 </div>
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />
@@ -30,3 +34,7 @@ import streetDepartures from "./img/street-departures.png";
 ### Configuration
 
 <WidgetConfig configuration={timetableWidget.configuration} />
+
+For security, all custom base URLs must resolve to a public IP address whenever Homarr uses them. Private and local hosts are rejected.
+
+If a timetable refresh fails after departures have loaded, the widget keeps the previous departures visible and marks them as stale. The advanced view also shows their last update time.

apps/docs/docs/widgets/timetable/index.ts

@@ -11,7 +11,7 @@ export const timetableWidget: WidgetDefinition = {
       {
         name: "Search.ch URL",
         description: "Base URL for the Search.ch timetable API.",
-        values: "Any valid URL.",
+        values: "An HTTP(S) URL that resolves to a public IP address.",
         defaultValue: "https://search.ch",
       },
       {

apps/docs/docs/widgets/tracearr/index.mdx

@@ -4,6 +4,8 @@ description: "Monitor media server streams, user activity, and policy violations
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -15,6 +17,8 @@ import { tracearrIntegration } from "@site/docs/integrations/tracearr";
 
 The Tracearr widget provides a real-time monitoring dashboard for your media server activity. It displays active streams, user statistics, recent watching history, and policy violations.
 
+When multiple Tracearr integrations are selected, every stream, violation, and activity row keeps its source identity and an integration-scoped key. Data from healthy sources remains visible if another source fails, and a warning identifies each unavailable integration without exposing private request details. If every selected integration fails, the widget reports an error; if cached data remains visible after a later total failure, a stale-data warning is shown.
+
 ### Sections
 
 | Section             | Description                                                                                                                            |
@@ -34,6 +38,8 @@ import streamsAndStats from "./img/streams-and-stats.png";
   <img src={streamsAndStats} alt="tracearr-streams-and-stats" width={128 * 4} />
 </div>
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/traefik/index.mdx

@@ -4,6 +4,8 @@ description: "Displays Traefik router, service, middleware, and entry point coun
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -15,6 +17,10 @@ import { traefikIntegration } from "@site/docs/integrations/traefik";
 
 This widget displays a compact overview of your Traefik instance, including total routers, entry points, protocol-specific router/service/middleware counts, and warning or error totals when Traefik reports them.
 
+Advanced view shows every protocol and entry point, identifies every healthy Traefik source and version, and labels each resource or failed endpoint with its owning integration. Compact mode keeps the responsive aggregate overview and names each healthy source when multiple integrations are selected.
+
+When multiple Traefik integrations are selected, data from healthy sources remains visible if another source fails. A warning indicator identifies each unavailable integration without exposing private request details. If every selected integration fails, the widget reports an error; if cached data remains visible after a later total failure, a stale-data warning is shown.
+
 ### Supported Integrations
 
 <WidgetIntegrations
@@ -26,6 +32,8 @@ This widget displays a compact overview of your Traefik instance, including tota
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/umami/index.mdx

@@ -4,6 +4,8 @@ description: "Display visitor stats from your Umami analytics instance"
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -25,6 +27,8 @@ The Umami Analytics widget displays key visitor metrics from a website tracked b
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/ups/index.mdx

@@ -4,6 +4,8 @@ description: "Monitor the status of your UPS devices through a NUT server."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -17,6 +19,10 @@ This widget displays the status of the UPS devices reported by a Network UPS Too
 status (online, on battery, charging or low battery), battery charge and estimated runtime, output load, and input and
 output voltage.
 
+Every device keeps an integration-scoped identity. Advanced view always labels each device with its owning integration, while compact layouts add the source label only when multiple healthy integrations are present.
+
+When multiple UPS integrations are selected, devices from healthy sources remain visible if another source fails. A warning indicator identifies each unavailable integration without exposing private request details. If every selected integration fails, the widget reports an error; if cached data remains visible after a later total failure, a stale-data warning is shown.
+
 ### Layouts
 
 import screenshotFull from "./img/screenshot.png";
@@ -41,6 +47,8 @@ The widget adapts to the size of the tile, so it stays readable from a full dash
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/uptime-kuma/index.mdx

@@ -4,6 +4,8 @@ description: "Displays monitor uptime statistics, average uptime percentage, and
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
@@ -15,6 +17,10 @@ import { uptimeKumaIntegration } from "@site/docs/integrations/uptime-kuma";
 
 This widget displays uptime statistics from your Uptime Kuma status page, including a visual uptime ring, average uptime percentage, and per-status monitor counts.
 
+Advanced view always shows the uptime ring, all status totals, and the complete monitor list with source identity, regardless of compact visibility switches.
+
+When multiple Uptime Kuma integrations are selected, monitors from healthy sources remain visible if another source fails. A warning indicator identifies each unavailable integration without exposing private request details. If every selected integration fails, the widget reports an error; if cached data remains visible after a later total failure, a stale-data warning is shown.
+
 ### Supported Integrations
 
 <WidgetIntegrations
@@ -26,6 +32,8 @@ This widget displays uptime statistics from your Uptime Kuma status page, includ
   ]}
 />
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/video/index.mdx

@@ -4,6 +4,8 @@ description: "Embed a video stream or video from a camera or a website."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -25,6 +27,8 @@ http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp
 
 ![video big-buck-bunny](./img/bunny.png)
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/video/index.tsx

@@ -5,7 +5,7 @@ export const videoWidget: WidgetDefinition = {
   icon: IconDeviceCctv,
   name: "Video Stream",
   description: "Embed a video stream or video from a camera or a website.",
-  path: "../../widgets/stock-price",
+  path: "../../widgets/video",
   configuration: {
     items: [
       {

apps/docs/docs/widgets/vpn/index.mdx

@@ -4,6 +4,8 @@ description: "Monitor the status of your VPN integrations."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
@@ -36,6 +38,8 @@ import singleIntegrationImage from "./img/single.png";
   ]}
 />
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/weather/index.mdx

@@ -4,6 +4,8 @@ description: "Displays the current weather information of a set location."
 hide_title: true
 ---
 
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
+
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetHeader } from "@site/src/components/widgets/header";
@@ -12,6 +14,9 @@ import { weatherWidget } from ".";
 <WidgetHeader widget={weatherWidget} categories={["Weather"]} />
 
 The Weather Widget uses your location to display the current, highest and lowest temperature.
+In the compact view, select a condition icon or forecast day to open details with a mouse, keyboard or touch.
+The advanced view always combines current conditions with the full seven-day forecast, including humidity, wind,
+gusts, sunrise and sunset. Both views reuse the same cached Open Meteo response.
 
 ### Screenshots
 
@@ -23,6 +28,8 @@ import currentWeather from "./img/current.png";
   <img src={currentWeather} alt="weather current" width={128 * 3} />
 </div>
 
+<WidgetInteractionGuide />
+
 ### Adding the widget
 
 <AddingWidget />

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

@@ -8,6 +8,7 @@ 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 { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
 import { wudWidget } from ".";
 import { wudIntegration } from "@site/docs/integrations/whats-up-docker";
 
@@ -26,6 +27,10 @@ This widget shows two stats from your WUD instance: the total number of monitore
   ]}
 />
 
+<WidgetInteractionGuide />
+
+In advanced view, the widget always shows its title, update ring, monitored-container summary, and the full list of available container updates. The configured horizontal or vertical layout still applies. Visibility options only affect the compact board view. A failed refresh keeps the last WUD snapshot visible with a stale-data warning.
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/workshop/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Workshop",
+  "collapsed": true,
+  "position": 4,
+  "link": {
+    "type": "doc",
+    "id": "workshop/index"
+  }
+}

apps/docs/docs/workshop/development.mdx

@@ -0,0 +1,62 @@
+---
+title: Workshop development
+sidebar_position: 4
+tags:
+  - Workshop
+  - Developer
+  - Docusaurus
+  - PocketBase
+---
+
+# Workshop development
+
+Install the repository dependencies and make sure Docker is available before starting the Workshop services. See the
+[main development guide](../advanced/development/getting-started) for the repository prerequisites.
+
+## Run PocketBase and documentation
+
+Start PocketBase in one terminal:
+
+```sh
+cp apps/workshop/.env.example apps/workshop/.env
+docker compose --env-file apps/workshop/.env -f apps/workshop/docker-compose.yml up --build workshop
+```
+
+Then start Docusaurus in another terminal:
+
+```sh
+WORKSHOP_API_URL=http://127.0.0.1:8090 pnpm dev:docs
+```
+
+PocketBase runs on port 8090 and Docusaurus on port 3003. Stopping the services preserves the PocketBase volume.
+
+Open `http://127.0.0.1:8090/_/` and create the first PocketBase superuser. The Workshop UI is available at
+`http://127.0.0.1:3003/workshop`.
+
+Point Homarr at the local services with:
+
+```dotenv
+HOMARR_WEBSITE_URL=http://127.0.0.1:3003
+WORKSHOP_API_URL=http://127.0.0.1:8090
+WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
+```
+
+Restart `pnpm dev:docs` after changing the Docusaurus URL variables. If Homarr is also running, restart its `pnpm dev`
+process after changing the Workshop URLs. 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
+```
+
+The [Workshop operator guide](./operator) covers production environment variables, staging, and service validation.

apps/docs/docs/workshop/homarr-provider.mdx

@@ -0,0 +1,51 @@
+---
+title: Homarr provider
+sidebar_position: 2
+tags:
+  - Assistant
+  - AI
+  - Privacy
+  - Community
+---
+
+import { OpenCollectiveLink } from "@site/src/components/assistant-provider/open-collective-link";
+
+# Homarr provider
+
+The Homarr provider gives Community Workshop users access to the **Homarr model** without an administrator API key.
+The Homarr team chooses the upstream model based on quality, reliability, and cost.
+
+## Set it up
+
+1. Open **Management → Assistant**.
+2. Select **Homarr** as the provider.
+3. Save the provider connection.
+4. Select the available model, enable the assistant, and save.
+5. Open the assistant and sign in to the Workshop when asked.
+
+## Daily allowance
+
+- Each user gets **50 request units per UTC day**.
+- Each model request uses one unit. A tool loop can use several units.
+- Forwarded requests count even if the model later fails.
+- Allowances reset at 00:00 UTC. A shared daily limit also applies.
+
+The battery beside the model selector shows the remaining allowance and reset time. Workshop enforces all limits on
+its server; changing the browser clock cannot bypass them.
+
+## Privacy
+
+Workshop keeps the OpenRouter API key on its server. Homarr and the browser never receive it.
+
+Prompts, attachments, tools, and tool results pass through Workshop and OpenRouter. Workshop does not retain this
+content or the responses. It stores only the user, UTC day, and counters needed to enforce allowances. OpenRouter is
+configured for zero data retention with data collection disabled. Homarr does not use this content to train models.
+
+We would rather become millionaires in a more ethical manner.
+
+The community pays for these requests. Donations help cover the cost.
+
+<OpenCollectiveLink />
+
+Workshop operators can change the upstream model, per-user allowance, global allowance, and security limits in the
+[Workshop operator guide](./operator#homarr-provider-proxy).

apps/docs/docs/workshop/index.mdx

@@ -0,0 +1,53 @@
+---
+title: Community Workshop
+sidebar_label: Overview
+tags:
+  - Workshop
+  - Custom Widgets
+  - Custom CSS
+---
+
+# Community Workshop
+
+The [Community Workshop](pathname:///workshop) is where Homarr users share Custom Widgets and dashboard CSS.
+
+:::warning Experimental
+
+Workshop content is made by the community. Review it before installation and back up your Homarr instance.
+
+:::
+
+## Find and install content
+
+Browse the Workshop by type, date, popularity, or recent activity. Each submission includes its source, screenshots,
+author, revision, comments, and reports.
+
+Administrators can install content without leaving Homarr:
+
+- **Custom Widgets:** open **Management → Custom Widgets**, then select **Import from Workshop**.
+- **Custom CSS:** open a board's **Settings → Custom CSS**, then select **Import from Workshop**.
+
+Homarr shows the complete source and required permissions before installation. Widget credentials are entered in your
+Homarr instance and are never included in a Workshop submission.
+
+## Share your work
+
+1. Sign in to the Workshop with GitHub.
+2. Select **Share yours**.
+3. Choose **Custom Widget** or **Custom CSS**.
+4. Add the source, a short description, screenshots, and a changelog.
+5. Review and publish the submission.
+
+Export Custom Widget JSON from **Management → Custom Widgets → Export**. You can edit a submission later without
+changing its Workshop URL.
+
+## Voting, comments, and reports
+
+Signed-in users can vote, comment, and report submissions. Authors can edit their own comments and submissions.
+Workshop moderators can review reports, remove comments, and delete unsafe content. Reports do not remove a submission
+automatically.
+
+A Workshop moderator manages the public community. This is separate from the administrator role on a Homarr instance.
+
+Deployment and server configuration are in the [Workshop operator guide](./operator). Local setup is in
+[Workshop development](./development).

apps/docs/docs/workshop/operator.mdx

@@ -0,0 +1,144 @@
+---
+title: Workshop operator guide
+sidebar_label: Operator guide
+sidebar_position: 3
+tags:
+  - Workshop
+  - Deployment
+  - Environment variables
+  - PocketBase
+---
+
+# Workshop operator guide
+
+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. See [Workshop development](./development) for the complete local setup.
+
+## Authentication and notifications
+
+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.
+
+## Environment variables
+
+The public URL contract and Workshop-only server configuration are:
+
+| 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  |
+| `OPENROUTER_API_KEY`                   | Server-only key for the Homarr provider proxy     | Provider disabled when empty   |
+| `HOMARR_AI_DAILY_REQUEST_LIMIT`        | Per-user daily provider allowance                 | `50`                           |
+| `HOMARR_AI_GLOBAL_DAILY_REQUEST_LIMIT` | Shared daily ceiling across all users             | `10000`                        |
+| `HOMARR_AI_OPENROUTER_BASE_URL`        | OpenRouter-compatible proxy upstream              | `https://openrouter.ai/api/v1` |
+| `HOMARR_AI_OPENROUTER_MODEL`           | Server-selected upstream model                    | Selected by the Homarr team    |
+
+All public URL variables reject non-HTTP protocols, embedded credentials, query strings, and fragments, and normalize
+trailing slashes when Homarr or Docusaurus starts. The deprecated docs-only `WORKSHOP_URL` alias remains for one
+release; `WORKSHOP_API_URL` takes precedence. The combined Workshop image writes the 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.
+
+### Homarr provider proxy
+
+The [Homarr provider](./homarr-provider) proxy is part of the Workshop image. `OPENROUTER_API_KEY` enables the proxy,
+`HOMARR_AI_OPENROUTER_BASE_URL` selects its OpenRouter-compatible upstream, `HOMARR_AI_OPENROUTER_MODEL` selects the
+private upstream model behind the stable `homarr/model` alias, and the two allowance variables provide per-user and
+shared request ceilings. Lowering either allowance takes effect for existing users. The upstream URL cannot contain
+embedded credentials, a query, or a fragment and must use HTTPS. Tests can explicitly opt into an insecure local mock
+with `HOMARR_AI_ALLOW_INSECURE_UPSTREAM=true`; do not use that setting with a real API key.
+
+The proxy overwrites client routing and generation limits. It requires OpenRouter zero-data-retention routing, denies
+data-collecting providers, limits responses to 32,768 completion tokens, and does not retain prompts, responses, or
+per-request telemetry. It accepts only uploaded image data, conservatively bounds text to the advertised context, and
+allows at most two concurrent requests per user and 100 across the service. Keep an OpenRouter account-level credit
+limit as the final monetary backstop because request quotas are not dollar accounting.
+
+Run `pnpm test:workshop` to test authentication, streaming, UTC reset, atomic per-user and global quota enforcement,
+failed-request accounting, identity attribution, server-selected model routing, function tools, input and output
+controls, privacy routing, spoofing resistance, absence of request logs, and migration rollback.
+
+An operator can explicitly smoke-test a deployed Workshop against its real configured upstream with a dedicated,
+low-quota test user:
+
+```sh
+HOMARR_AI_LIVE_SMOKE=1 \
+WORKSHOP_LIVE_TEST_URL=https://workshop.example.com \
+WORKSHOP_LIVE_TEST_TOKEN=<temporary-pocketbase-user-token> \
+pnpm test:workshop-live-provider
+```
+
+This optional check consumes one provider request. The test client needs neither the OpenRouter key nor the private
+upstream model ID. Do not run it in CI or with a normal user's Workshop token.
+
+The Custom Widget AI tests can use this proxy. Set `AI_PROVIDER_BASE_URL` to the `/api/ai/v1` endpoint and
+`AI_PROVIDER_API_KEY` to a temporary Workshop user token. See
+[Agent authoring](../management/custom-widgets/agent-authoring#evaluate-the-copied-prompt) for the command.
+
+## 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/docusaurus.config.ts

@@ -362,7 +362,7 @@ html[data-workshop-detail-loading] #workshop-detail-route-fallback {
   box-sizing: border-box;
   color: #4b5563;
   display: flex;
-  font: 500 0.875rem/1.5 Inter, system-ui, sans-serif;
+  font: 500 0.875rem/1.5 "Work Sans", system-ui, sans-serif;
   justify-content: center;
   min-height: 100vh;
   padding: 2rem;

apps/docs/package.json

@@ -51,7 +51,6 @@
     "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:",

apps/docs/src/components/assistant-provider/open-collective-link.module.css

@@ -0,0 +1,41 @@
+.link {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.5rem;
+  padding: 0.45rem 0.7rem;
+  border: 1px solid var(--ifm-color-emphasis-300);
+  border-radius: 0.5rem;
+  background: var(--ifm-background-surface-color);
+  color: var(--ifm-font-color-base);
+  font-size: 0.875rem;
+  font-weight: 600;
+  line-height: 1.25;
+  text-decoration: none;
+  transition:
+    background-color 150ms ease,
+    border-color 150ms ease;
+}
+
+.link:hover {
+  border-color: var(--ifm-color-emphasis-500);
+  background: var(--ifm-color-emphasis-100);
+  color: var(--ifm-font-color-base);
+  text-decoration: none;
+}
+
+.link:focus-visible {
+  outline: 2px solid var(--ifm-color-primary);
+  outline-offset: 2px;
+}
+
+.logo {
+  width: 1.1rem;
+  height: 1.1rem;
+  flex: 0 0 auto;
+}
+
+@media (prefers-reduced-motion: reduce) {
+  .link {
+    transition: none;
+  }
+}

apps/docs/src/components/assistant-provider/open-collective-link.tsx

@@ -0,0 +1,10 @@
+import Translate from "@docusaurus/Translate";
+
+import styles from "./open-collective-link.module.css";
+
+export const OpenCollectiveLink = () => (
+  <a className={styles.link} href="https://opencollective.com/homarr">
+    <img className={styles.logo} src="/img/opencollective.svg" alt="" aria-hidden />
+    <Translate id="workshop.provider.donate">Donate to Homarr on OpenCollective</Translate>
+  </a>
+);