@rio-cloud/uikit-mcp 1.1.4 → 1.1.6

package/dist/docs/start/guidelines/state-in-url.md

@@ -0,0 +1,263 @@
+# State in URL (deep links)
+
+*Category:* Getting started
+*Section:* Guidelines
+*Source:* https://uikit.developers.rio.cloud/#/start/guidelines/state-in-url
+*Captured:* 2026-02-23T13:48:34.867Z
+
+Every service frontend should support deep linking and reflect meaningful UI state in the URL. This enables restoring state when links are shared, when they are stored as bookmarks, when users navigate with browser history, or when a service is opened from another app.
+
+## State in URL (deep links)
+
+## Mental model
+
+Think of the URL as the external representation of app state. It should describe where the user is and what they are looking at (intent), not what they are currently doing (interaction).
+
+State that only lives in memory breaks a core web expectation. If users refresh or navigate back and lose filters, view settings, or selections, the app feels unreliable. URLs should preserve context so users can return to the same place without redoing their work.
+
+## Decision criteria
+
+Before putting something in the URL, ask:
+
+- Would the user expect this to persist after reload or sharing the link?
+- Would the link feel “broken” without it?
+- Does it describe intent rather than a transient UI interaction?
+
+## What belongs in the URL
+
+## Good candidates
+
+- Search queries and filters
+- Sorting and column visibility (when it changes what users see)
+- View modes (list/grid/table/map)
+- Date ranges and time periods
+- Selected items or active tabs (focus)
+- UI configuration that affects content (e.g. grouping, expanded views)
+- Feature variants (only if stable and safe to share)
+
+## Poor candidates
+
+- Sensitive information (passwords, tokens, PII) - NEVER!
+- Temporary UI states (e.g. dropdown expanded, tooltip open)
+- Form input in progress (unsaved changes)
+- Very large or complex nested data
+- Base64 encoded data
+- High-frequency transient state (mouse position, scroll)
+
+## Example deep links
+
+Prefer readable, self-describing URLs. Use consistent naming across services to make deep links easier to share and reason about.
+
+## Annotated example
+
+https://example.com/#/assets?q=truck&sort=-name&viewType=table&selectedAssetId=asset-123
+
+q                search query (user intent)
+sort             sort key with direction prefix ("-name" = descending by name)
+viewType         content representation mode
+selectedAssetId  focused entity that should be shareable/restorable
+
+## More examples
+
+https://example.com/#/overview?view=history&assetIds=5a88af1e-2fb2-494e-9240-6a833d5f1791&q=10&startDate=2019-06-17T00:00:00Z&endDate=2019-06-17T23:59:59Z&sort=timestamp#details
+https://example.com/#/drivers/74eb88e1-1a84-4abe-90bc-9e0079807d57?driverState=ACTIVE&q=my%20test
+https://example.com/#/users/0848-b02e-47be-bd77-d332f61a90d6?sort=-lastName
+https://example.com/#/issues?projectKey=FM&view=details&selectedIssue=FM-4346
+
+Treat the URL as user input. Invalid or unknown params should not break rendering. Fall back to defaults and keep the UI usable.
+
+## Common param names
+
+Use consistent, concise camelCase param names across services whenever possible. If URLs become verbose, prefer a well-known short form (e.g. q, lat / lng) and document it so other teams can align.
+
+## URLs as contracts
+
+Well-designed URLs are more than a storage place for state. They become a contract between your app and its consumers, setting expectations for humans, developers, and machines.
+
+A clear URL draws boundaries between public and private state, shareable and session-only data, and client versus server responsibility. Developers know what is safe to persist, users know what they can bookmark, and machines know what is worth indexing.
+
+Readable URLs communicate meaning. Compare:
+
+// bad: unclear intent, hard to reason about
+https://example.com/#/p?id=x7f2k&v=3
+
+// good: self-describing, stable, easier to maintain
+https://example.com/#/products/laptop?color=silver&sort=price
+
+The first hides intent; the second explains itself and is easier to evolve without breaking consumers.
+
+## How to
+
+Typical flow:
+
+- Define which parts of state belong in the URL and what the defaults are.
+- Parse URL to initial state on load.
+- Update URL when state changes (omit defaults to keep URLs compact).
+- Choose history behavior (push vs replace) based on user expectations.
+
+Use UIKIT utilities instead of hand-rolled parsers:
+
+```ts
+import { useLocation, useNavigate, useNavigationType } from 'react-router-dom';
+import useUrlState from '@rio-cloud/rio-uikit/useUrlState';
+import type { UrlConfigItem } from '@rio-cloud/rio-uikit/routeUtils';
+
+type ViewType = 'list' | 'grid';
+type AppState = { query: string; viewType: ViewType; tags: string[] };
+
+const actions = {
+setQuery: (value: string) => ({ type: 'setQuery' as const, payload: value }),
+setViewType: (value: ViewType) => ({ type: 'setViewType' as const, payload: value }),
+setTags: (value: string[]) => ({ type: 'setTags' as const, payload: value }),
+};
+
+const config: readonly UrlConfigItem<AppState, unknown>[] = [
+{ key: 'q', selector: s => s.query, action: actions.setQuery, defaultValue: '' },
+{ key: 'viewType', selector: s => s.viewType, action: actions.setViewType, defaultValue: 'list' },
+{ key: 'tags', selector: s => s.tags, action: actions.setTags, type: 'array', defaultValue: [] },
+];
+
+const location = useLocation();
+const navigate = useNavigate();
+const navigationType = useNavigationType();
+
+useUrlState({
+config,
+searchString: location.search,
+storeValues: { q: state.query, viewType: state.viewType, tags: state.tags },
+navigationType,
+onUpdateStore: action => dispatch(action),
+onNavigate: (search, mode) => navigate({ search }, { replace: mode === 'replace' }),
+});
+```
+
+> Implementation details: See useUrlState and route utils for details.
+
+## Best practices
+
+Keep URLs tidy, predictable, and easy to share. Compact URLs are easier to read, easier to compare, and less likely to break in older environments.
+
+Handle defaults by omitting them from the URL. Only include values that differ from the default state.
+
+// avoid: defaults add noise
+?viewType=table&lang=en&sort=date&filters=type
+
+// prefer: only non-default values
+?viewType=grid
+
+## pushState vs. replaceState
+
+Use pushState when a change is a meaningful navigation step and should be undoable via the Back button (switching view type, applying a filter set). Use replaceState for small refinements where history noise would harm usability (search-as-you-type, incremental tweaks).
+
+// use pushState for meaningful navigation steps (undoable via Back button)
+?viewType=grid
+?selectedAssetId=asset-123
+?filters=type:truck,status:active
+
+// use replaceState for refinements (avoid noisy history)
+?q=tr
+?q=tru
+?q=truck
+
+Respect the Back button: if a change should be undoable, use pushState. If it is just a refinement, prefer replaceState.
+
+## URL state and Redux
+
+Pick one source of truth and keep synchronization one-way to avoid loops.
+
+**URL as source of truth (simple cases)**
+
+- Read URL params directly (for example with React Router search params).
+- Derive rendered state from URL values.
+- Update URL directly from UI actions with push/replace based on intent.
+
+```ts
+import { useMemo } from 'react';
+import { useSearchParams } from 'react-router-dom';
+
+type ViewType = 'list' | 'grid';
+
+// URL as source of truth (simple screens, no centralized store sync)
+const [searchParams, setSearchParams] = useSearchParams();
+
+const urlState = useMemo(
+() => ({
+q: searchParams.get('q') ?? '',
+viewType: (searchParams.get('viewType') as ViewType) ?? 'list',
+}),
+[searchParams]
+);
+
+const setUrlState = (patch: Partial<typeof urlState>, historyMode: 'push' | 'replace' = 'push') => {
+const next = new URLSearchParams(searchParams);
+const merged = { ...urlState, ...patch };
+
+if (merged.q) next.set('q', merged.q);
+else next.delete('q');
+
+if (merged.viewType === 'list') next.delete('viewType');
+else next.set('viewType', merged.viewType);
+
+setSearchParams(next, { replace: historyMode === 'replace' });
+};
+
+// Typical usage:
+const onSearchChange = (q: string) => setUrlState({ q }, 'replace'); // typing/search refinement
+const onViewTypeChange = (viewType: ViewType) => setUrlState({ viewType }, 'push'); // meaningful step
+```
+
+**Redux as source of truth (more complex but recommend for more complex SPAs)**
+
+- Parse the URL once to seed initial Redux state.
+- Subscribe to Redux and update the URL (debounced).
+- Listen for URL changes and dispatch to Redux with guards to avoid loops and no-op updates.
+
+```ts
+import useUrlState from '@rio-cloud/rio-uikit/useUrlState';
+import { useDispatch, useSelector } from 'react-redux';
+import { useLocation, useNavigate, useNavigationType } from 'react-router-dom';
+import type { AppDispatch } from '../../../../setup/store';
+
+// Redux as source of truth (recommended for larger SPAs)
+// 1) Parse URL and dispatch updates on URL changes (including browser POP).
+// 2) Observe store values and write URL changes via push/replace rules.
+// 3) Keep this logic centralized in one component near the router.
+
+const dispatch = useDispatch<AppDispatch>();
+const location = useLocation();
+const navigate = useNavigate();
+const navigationType = useNavigationType();
+
+const storeValues = useSelector(state => ({
+q: getSearchValue(state),
+sort: { sortBy: getSortBy(state), sortDir: getSortDir(state) },
+filters: getActivityFilter(state),
+}));
+
+useUrlState({
+config: tableUrlConfig,
+searchString: location.search,
+storeValues,
+localStorageKey: 'service.ui.state',
+navigationType,
+onUpdateStore: action => dispatch(action),
+onNavigate: (search, mode) => navigate({ search }, { replace: mode === 'replace' }),
+});
+```
+
+useUrlState supports this second model: centralized store-url synchronization. If you still use template helpers like routeHelper with qs, replace them with a centralized config + useUrlState synchronizer and define per-field history behavior with history: 'push' | 'replace'.
+
+## Things to consider
+
+- Use comma-separated values for lists (keep them readable, avoid encoding commas in lists).
+- Keep param names explicit and avoid merging unrelated state into one param.
+- If a value equals the default, omit it from the URL to reduce clutter.
+- Encode user input (search strings) with encodeURIComponent.
+- Document formats for dates and timezones (recommend UTC) and coordinate precision.
+- Treat URL params as untrusted input: ignore unknown params, fall back to defaults for invalid values, and never break rendering due to a malformed URL.
+
+## Limitations
+
+URL length limits vary by browser, OS, and environment. Modern browsers typically handle very long URLs, but older/legacy browsers can fail around a few thousand characters.
+
+Keep URLs concise. If you need to support older environments, validate URL length limits in your target setup and consider alternative persistence (e.g. server-side saved views) for large state.

package/dist/docs/start/guidelines/supported-browsers.md

@@ -2,8 +2,8 @@
 
 *Category:* Getting started
 *Section:* Guidelines
-*Source:* https://uikit.developers.rio.cloud/#start/guidelines/supported-browsers
-*Captured:* 2026-01-14T09:06:50.006Z
+*Source:* https://uikit.developers.rio.cloud/#/start/guidelines/supported-browsers
+*Captured:* 2026-02-23T13:48:36.676Z
 
 We currently support the following browsers:
 

package/dist/docs/start/guidelines/writing.md

@@ -2,8 +2,8 @@
 
 *Category:* Getting started
 *Section:* Guidelines
-*Source:* https://uikit.developers.rio.cloud/#start/guidelines/writing
-*Captured:* 2026-01-14T09:06:50.570Z
+*Source:* https://uikit.developers.rio.cloud/#/start/guidelines/writing
+*Captured:* 2026-02-23T13:48:37.143Z
 
 UX writing doesn't receive as much attention as it should. In the past, digital experiences featured words written by different individuals - ranging from designers to engineers — at various times and in diverse styles, all without a centralized guide.
 

package/dist/docs/start/howto.md

@@ -2,8 +2,8 @@
 
 *Category:* Getting started
 *Section:* Welcome
-*Source:* https://uikit.developers.rio.cloud/#start/howto
-*Captured:* 2026-01-14T09:06:48.253Z
+*Source:* https://uikit.developers.rio.cloud/#/start/howto
+*Captured:* 2026-02-23T13:48:35.220Z
 
 Install the latest version of the UIKIT (that includes latest beta versions as well) via
 
@@ -33,7 +33,7 @@ npm install @rio-cloud/rio-uikit
 Or install a dedicated version via
 
 ```javascript
-npm install @rio-cloud/rio-uikit@2.1.0
+npm install @rio-cloud/rio-uikit@2.2.0
 ```
 
 ## TypeScript
@@ -85,7 +85,7 @@ ManualNot Recommended
 Use the CSS Stylesheet as follows (specify your required version number in the URL) if you need more control on what style you want to use.
 
 ```html
-<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.1.0/rio-uikit.css">
+<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.2.0/rio-uikit.css">
 ```
 
 > Note: Please make sure to use the same UIKIT style version as the npm package, otherwise this will lead to inconsistency and UI bugs.
@@ -99,15 +99,15 @@ These other themes may only be used for applications or services who don't run o
 In order to use such a brand theme, modify the URL in the <link> tag that loads the CSS
 
 ```html
-<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.1.0/vw-uikit.css">
+<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.2.0/vw-uikit.css">
 ```
 
 ```html
-<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.1.0/man-uikit.css">
+<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.2.0/man-uikit.css">
 ```
 
 ```html
-<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.1.0/scania-uikit.css">
+<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.2.0/scania-uikit.css">
 ```
 
 ManagedRecommended
@@ -131,7 +131,7 @@ You can simply omit the <link> tag in your index.html altogether. The UIKIT will
 The UIKIT supports simple print stylings in order to have printable content. See Print CSS
 
 ```html
-<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.1.0/rio-uikit-print-utilities.css">
+<link rel="stylesheet" type="text/css" href="https://uikit.developers.rio.cloud/2.2.0/rio-uikit-print-utilities.css">
 ```
 
 ## Additional styling information
@@ -139,7 +139,7 @@ The UIKIT supports simple print stylings in order to have printable content. See
 In some cases like using D3 you may need the color variables as .json from the UIKIT provided via CDN. You can fetch the provided file from CDN via the following URL:
 
 ```html
-https://uikit.developers.rio.cloud/2.1.0/rio-uikit-colors.json
+https://uikit.developers.rio.cloud/2.2.0/rio-uikit-colors.json
 ```
 
 ## Dark mode
@@ -168,7 +168,7 @@ The UIKIT is fully dark mode ready.
 In cases where the React ApplicationLayout component cannot be used, you can import the new darkmode.js from the UIKIT CDN and add it to your index.html. This script will take care of listening to the theme switch for you.
 
 ```html
-<script src="https://uikit.developers.rio.cloud/2.1.0/rio-darkmode.js"></script>
+<script src="https://uikit.developers.rio.cloud/2.2.0/rio-darkmode.js"></script>
 ```
 
 If you want to react on the dark mode for instance to exchange some images or apply some specific utility classes, you can use the custom hook useDarkMode to do so.

package/dist/docs/start/intro.md

@@ -2,8 +2,8 @@
 
 *Category:* Getting started
 *Section:* Welcome
-*Source:* https://uikit.developers.rio.cloud/#start/intro
-*Captured:* 2026-01-14T09:06:48.139Z
+*Source:* https://uikit.developers.rio.cloud/#/start/intro
+*Captured:* 2026-02-23T13:48:34.460Z
 
 Welcome! This UI library is designed to help you build beautiful, consistent, and maintainable user interfaces with minimal effort. Here’s how you can make the most of it:
 

package/dist/docs/start/responsiveness.md

@@ -2,8 +2,8 @@
 
 *Category:* Getting started
 *Section:* Guidelines
-*Source:* https://uikit.developers.rio.cloud/#start/responsiveness
-*Captured:* 2026-01-14T09:06:48.290Z
+*Source:* https://uikit.developers.rio.cloud/#/start/responsiveness
+*Captured:* 2026-02-23T13:48:35.159Z
 
 The UIKIT considers all platforms — both desktop and mobile. We recognize that people work across many different products and often need to support multiple platforms and the UIKIT is a foundation for that with its many responsive building blocks and responsive components.
 

package/dist/docs/templates/common-table.md

@@ -2,8 +2,8 @@
 
 *Category:* Templates
 *Section:* Tables
-*Source:* https://uikit.developers.rio.cloud/#templates/common-table
-*Captured:* 2026-01-14T09:08:38.319Z
+*Source:* https://uikit.developers.rio.cloud/#/templates/common-table
+*Captured:* 2026-02-23T13:48:44.299Z
 
 ## Common table
 
@@ -80,8 +80,8 @@ Load more
 ```tsx
 import { useEffect, useMemo, useState } from 'react';
 import { isEmpty, omit } from 'es-toolkit/compat';
-import classNames from 'classnames';
 
+import classNames from '@rio-cloud/rio-uikit/classNames';
 import TableToolbar from '@rio-cloud/rio-uikit/TableToolbar';
 import TableViewToggles, { type TableViewTogglesViewType } from '@rio-cloud/rio-uikit/TableViewToggles';
 import TableSearch from '@rio-cloud/rio-uikit/TableSearch';
@@ -307,7 +307,8 @@ const TableCommonDemo = (props: TableCommonDemoProps) => {
     };
 
     // Filter for hidden columns
-    const columns = columnOrder.filter(name => !hiddenColumns.includes(name));
+    const hiddenColumnsSet = new Set(hiddenColumns);
+    const columns = columnOrder.filter(name => !hiddenColumnsSet.has(name));
 
     // Filter data to omit hidden columns
     const filteredRows = sortedItems.map(vehicle => omit(vehicle, hiddenColumns)) as Vehicle[];
@@ -787,7 +788,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="ckl7ormzjp4" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="trd65487yqs" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -818,7 +819,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="t8chh0jvc7" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="wdz1utbw6l9" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -849,7 +850,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="1g2lmyza8th" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="1l0ty4wxe9n" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -880,7 +881,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="h8hoxt8xzfl" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="ivqs9z3cr6h" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -911,7 +912,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="5edzesgw846" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="w8r8fiunzde" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -938,7 +939,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="mxmpujcx1nb" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="lhbkn1zoxkg" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -969,7 +970,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="nofngogq7ob" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="as32daumgbi" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -1000,7 +1001,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="2qp5w1as7z5" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="d6k381docg9" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -1031,7 +1032,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="panh4sgqddl" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="olx3pb7wk5s" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>
@@ -1058,7 +1059,7 @@ export default TableCommonDemo;
                     <td class="table-action">
                         <span>
                             <div class="dropdown btn-group">
-                                <button type="button" id="fwx2tczay4" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                                <button type="button" id="s04bj3kzc6d" class="btn btn-default btn-link btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                     <span class="rioglyph rioglyph-option-vertical">
                                     </span>
                                 </button>

package/dist/docs/templates/detail-views.md

@@ -2,8 +2,8 @@
 
 *Category:* Templates
 *Section:* Content
-*Source:* https://uikit.developers.rio.cloud/#templates/detail-views
-*Captured:* 2026-01-14T09:08:27.349Z
+*Source:* https://uikit.developers.rio.cloud/#/templates/detail-views
+*Captured:* 2026-02-23T13:48:39.310Z
 
 ## Detail views
 
@@ -319,7 +319,7 @@ export default () => {
                     </div>
                     <div>
                         <div class="dropdown btn-group">
-                            <button type="button" id="disz4fc2bv5" class="btn btn-default btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
+                            <button type="button" id="t66oq22gd3" class="btn btn-default btn-md btn-icon-only btn-component dropdown-toggle" tabindex="0">
                                 <span class="rioglyph rioglyph-option-horizontal" aria-hidden="true">
                                 </span>
                             </button>

package/dist/docs/templates/expandable-details.md

@@ -2,8 +2,8 @@
 
 *Category:* Templates
 *Section:* Content
-*Source:* https://uikit.developers.rio.cloud/#templates/expandable-details
-*Captured:* 2026-01-14T09:08:36.729Z
+*Source:* https://uikit.developers.rio.cloud/#/templates/expandable-details
+*Captured:* 2026-02-23T13:48:38.521Z
 
 ## Expandable details