Skip to Content
Design

Component Integration

Public integration contract for Qokit shared components, Patterns, Skins, and style Tokens.

Component Integration

Qokit uses a "shared skeleton + Skin recipe" model. External integrators rely on the semantic and interaction contracts of components, completing visual adaptation through Skins and Tokens.

2026-10-22 · Active navigation tabs on narrow screens

PillTabs accepts optional scrollActiveTabIntoView (default false). With horizontal tabs, it reveals the active direct PillTabLink or PillTabButton on selection and resize. Only the tab strip scrolls; page position and keyboard focus stay unchanged. It supports LTR and RTL and uses an immediate correction, including with reduced motion. Vertical tabs and callers that omit the option retain their behavior.

2026-10-20 · Visual choice card actions

EditorVisualChoiceGroup options accept an optional accessory for independent card menus or name editors. The shared RadioGroup renders this content beside the native label, so managing a card does not activate its radio. Optional afterOptions places a separate catalog action, such as a create card, after the choices. Hosts retain ownership of persistence, permissions, validation and focus after a card is replaced or removed. Existing options without accessories keep their markup and behavior.

2026-10-17 · Shared workbench panel motion

EditorWorkbenchChrome renders injected start/end lanes through BuilderWorkbenchFrame, the same panel skeleton used by Creator and content editing. Hosts provide content, visibility and width preferences. Desktop tracks and panel opacity/translation share --qk-sidebar-motion-duration and --qk-sidebar-motion-easing; dragging disables transitions and reduced motion switches immediately.

Collapsed panels stay mounted to retain drafts. The shared frame immediately applies inert and aria-hidden, while the platform skin completes the exit before hiding visibility. Compact panels retain their overlay geometry throughout exit; hosts must not add hidden or display: none to the panel shell. Explicit peek panels retain their existing interactive reveal behavior. Header choices remain available across open/closed states; use EditorPanelChoiceShortcuts.mobileMenu when phone destinations should share a menu.

2026-10-17 · Measured editor defaults

useWorkspaceResponsiveProfile accepts optional onWidthChange(width), reporting the same available work-area width used for responsive profiles after inline padding is deducted. Use a stable callback to derive proportional defaults without adding another observer. useEditorLayout applies sharedWidths.limits to host preferences as well as shared width storage; readEditorLayout accepts the same limits as its optional fourth argument. Existing callers retain their default bounds and behavior.

2026-10-15 · Shared inspector choices

EditorStyleChoice uses the shared EditorChoiceControl for finite settings. In auto mode, two or three illustrated options use a segmented group; larger illustrated sets use a portalled ControlMenu showing the current icon and name. Text-only choices retain a native Select. Existing custom values remain selectable.

For select and menu options, optional annotation adds a theme-colored dot after the label and includes its localized meaning in the accessible name. ControlMenu also displays the active option's dot beside its trigger label; triggerAnnotation: null keeps that annotation inside the menu only. Menu presentations forward optional onReselect when an enabled, already selected item is chosen. Native select options show the localized annotation alongside the label; optional hidden keeps a placeholder out of the picker. Hosts decide which value carries the annotation and what selecting it does; the shared control does not infer inheritance or write data.

Use presentation="visual" for labeled diagram choices and presentation="toolbar" for familiar tools such as four-way text alignment. The toolbar has separate targets without a shared capsule. Native radios, shared menu keyboard handling, visible focus, disabled states and theme Tokens are retained. Hosts own labels, allowed values, persistence and undo. id identifies the control; ControlMenu also accepts triggerId and disabled.

Inspector menus, inputs, collapsed summaries and reset actions share a 32px mouse field height, restored to 40px on narrow screens and coarse pointers. Field icons use 16px and diagram choices keep an 8px gap. EditorComponentSettings reuses these choices for columns, density, image fit and aspect ratio, while composition layouts retain detailed previews. If saving briefly disables native radios, the shared skeleton restores focus to the selected option for continuous arrow-key editing.

Inspector labels and diagram captions use the 12px caption scale; values, actions and section titles use the 13px field scale. Visual choices have no decorative outer border: a soft selected surface and centered caption identify the current option, while keyboard focus retains its ring. Font specimens in the inspector use a compact, bounded scale.

2026-10-15 · Responsive workspace tables

WorkspaceDataTable reflows mobileLayout="records" into two columns of labeled facts, with the primary identity and sticky end actions spanning the record. Names and identifiers can use two lines. Column labels and selection remain accessible. Comparison tables using mobileLayout="scroll" retain their columns.

When a host toolbar already provides sorting or other header actions, set mobileHeader="labels" to remove duplicate header controls from the mobile layout and tab order. Column names remain available to assistive technology; desktop headers are unchanged. The default "controls" preserves custom header controls on mobile.

2026-10-14 · Independent editor panels

resolveWorkspaceResponsiveProfile and useWorkspaceResponsiveProfile from WorkspacePanels, and EditorWorkbenchChrome, accept the optional panelPolicy="independent". With BuilderWorkbenchFrame and the platform editor skin, both panels remain docked above the mobile threshold. Shared styles temporarily compress displayed widths while retaining remembered sizes, and the canvas fits the remaining space. Effective work areas at or below 720px retain mobile task switching.

Hosts own panel visibility. When supplying a measured profile, use the same policy for the measurement hook and Chrome. Omitting panelPolicy retains the default "adaptive" policy with its existing desktop, two-column and overlay layouts.

2026-10-10 · Pagination dot display

Pagination from @qokit/components/ui accepts pageDisplay="dots" for compact visual choosers. Combine it with layout="centered" for centered arrows and 6px indicators with 32px-wide click targets. Dot colors, hover and keyboard focus use shared theme Tokens; PaginationSkin.dot adapts the indicator slot. Hosts supply currentPage, totalPages, onPageChange and localized navigation labels. pageLabel names each dot; its fallback combines ariaLabel with the page and total. Browsing pages only invokes the host callback. The default "numbers" display retains numeric pagination and formatPageNumber. In containers up to 440px wide, numeric page items become a current/total indicator while previous, next and the optional jump input remain available. Dot pagination keeps its visual chooser behavior.

2026-10-10 · ActionMenu search header

ActionMenu.dropdownHeader accepts host-owned content before the actions in both dropdown and mobile sheet presentations. onOpenChange reports opening and dismissal so hosts can reset transient search state. Search hosts supply localized copy, filtering and initial input focus; ArrowDown from the input should focus the first enabled result, then the shared menu handles result navigation, selection and Escape.

2026-10-09 · Inline ColorPicker

ColorPicker from @qokit/components/ui/ColorPicker accepts presentation="inline" to expand its editor beneath the field trigger. It renders a named group in the document flow, keeps the surrounding workspace available, and retains palette, HEX, opacity, gradient and reset capabilities. Hosts should reserve a full row for the field. Changes to the controlled value, including undo and reset, update the open inline editor; leaving the field finishes the current edit. The default "popover" presentation retains its portal, outside-click dismissal and Escape behavior.

2026-10-07 · WorkspacePanelGrid

WorkspacePanelGrid from @qokit/components/patterns/WorkspaceLayout places independent detail panels below the shortest available column. It responds to content and container size changes without moving or remounting child nodes; DOM and keyboard order remain unchanged. Narrow containers use one column. Keep continuous panels in one grid rather than separate rows. Metrics, tables, paired fields and ordered workflows retain their own layouts.

Each direct child is a panel. Use data-workspace-panel-span="full" or a numeric column span on that child's root for wider panels. The optional skin has a root slot and variables; --qk-workspace-panel-grid-gap controls shared spacing, and --qk-workspace-panel-grid-max-columns defaults to 2. Without JavaScript or ResizeObserver, panels retain the responsive ordinary grid.

2026-09-30 · SelectionToolbar accessibility

SelectionToolbar.ariaLabel optionally names the toolbar as a region. Its count remains a live status message. Hosts supply localized labels and may use actionContent for a shared EditorToolGroup and ActionMenu; permission checks and action handlers remain with the host.

2026-09-10 · Workspace identity badges

ProjectSwitcherProject.badge accepts optional, non-interactive React content. The switcher displays it beside each item name, in the fallback current-context row, and beside the current name in a text trigger. Icon-only triggers retain their compact form; platform text triggers hide the badge at phone widths to preserve the workspace name. The opened menu includes the badge. Hosts provide scoped data, localized labels and presentation styles. Omit the field to retain the existing appearance.

2026-09-08 · Editor context and inactive canvas

EditorHeader.contextMode="title" displays the editor's own titleControl instead of the host workspace picker. The default "host" behavior is unchanged; navigation, brand, account controls and leave guards retain their existing ownership. Hosts supply responsive placement for their title control.

EditorViewControls.focusInMenu shows a labelled preview action and moves focus mode into the shared menu. Its default remains false; view shortcuts and returning from preview keep the existing behavior.

EditorViewControls.toolsControl replaces the fallback menu with a host-owned tools control. Hosts retain its accessible trigger, menu state and actions; view buttons and keyboard shortcuts keep their existing behavior. Creator uses this slot for its complete editor tools menu beside Add, Layers and Preview.

EditorViewControls.responsiveLabels displays text beside focus and preview icons above 720px, reserving space for both focus labels. At phone widths the labels are hidden while accessible names and tooltips remain. EditorSaveButton.showStatusLabel displays saved/saving status or a retry action when state is provided; it reserves label space across states. Both options default to false.

ResizablePanels.middlePanelProps forwards section attributes such as inert to the middle panel, matching the existing side-panel attribute slots. An editor can keep its canvas mounted while preventing keyboard and pointer interaction when a compact conversation view covers it. Hosts still control panel visibility and restore focus when switching views; the prop does not unmount content.

2026-09-08 · ProjectSwitcher context and actions

ProjectSwitcher.currentWorkspaceId optionally marks the parent workspace independently of currentProjectId; only the current location receives the selected surface. IDs must match the supplied projects items. onActionSelect(action, event) lets the host guard shortcut navigation after the menu closes; omitted callbacks retain normal link behavior. Creation shortcuts use ordinary menu surfaces. Optional SiteHeaderCopy.projectSwitcherCreate and projectSwitcherWebsites label creation and the current workspace's website group without renaming the Creator product.

2026-09-08 · EmptyState

EmptyState centers its optional decorative icon, title, optional description and action on a transparent surface. layout="section" is the compact default; layout="workspace" reserves more space for an empty business area. Actions belong directly in the action slot (use a fragment for multiple buttons); the shared wrapper handles spacing and long labels. The title is an h2; target the title skin slot instead of a strong selector. Existing root classes remain. skin.vars and style are supported. Hosts retain localized copy, permission checks, navigation and create handlers; search results and errors keep their own messages and actions.

2026-09-08 · SidebarNavigation

SidebarNavigation prefetches same-origin routes after a 180 ms mouse hover or keyboard focus, sharing a limit of 8 destinations per 30 seconds across docked and popup navigation. Prefetching pauses offline, in hidden tabs, with Save-Data or on 2G; downloads, disabled links, new-window targets and same-page anchors are excluded. Navigation and unsaved-change guards are unchanged.

2026-09-07 - AccountDropdown / SidebarProfile

AccountDropdown.usageSummary is an optional slot below the account identity for host-supplied credit balances, plan usage and links to details. It also accepts ({ environmentInfo }) => ReactNode to place the shared ID disclosure and copy controls in the summary without duplicating them below. Links use role="menuitem" and retain menu keyboard behavior and navigation guards. The platform header shows credits and plan usage in two columns, with ID details expanding below; the sidebar account retains appearance and language. Failed reads never appear as zero, and reopening the menu refreshes the data.

AccountDropdown accepts optional compact and preferences: compact mode hides identifiers and creation history; the default retains existing content. Appearance and Language accept triggerRole="menuitem" inside account menus. Menu keyboard navigation restores focus and lets nested language dialogs handle Escape. SidebarNavigation.searchEnabled defaults to true; set it to false for short, fixed navigation. A SidebarProfile with href and no menu links to the same destination in expanded and icon modes.

2026-09-07 - FormField / AdminEntityDialog / EditorWorkspace

Shared form typography wraps long labels and metadata while keeping pill shapes and brand colors. FormField names composite groups; pair controlId with the nested input id for label focus. SearchField restores focus after clearing. Segmented and ControlMenu support disabled options; disabled ActionMenu items have no link. Busy buttons keep their size and visible indicator. AdminEntityDialog validates required fields, email and JSON, focuses errors, prevents duplicate saves and retains failed input. EditorWorkspace exposes ref.focusControl(element) to reveal hidden panels before focusing. Reduced motion disables control transitions. WorkspaceDialog scrolls long content while keeping its header and actions visible; short mobile dialogs fit their content.

2026-09-07 · WorkspaceLocationSync / ProjectSwitcher

After a route commits, WorkspaceLocationSync closes the transient space chooser so the destination immediately shows its tools. Search and section preferences remain. Sidebar scope labels and context badges occupy separate lines; long header switcher names truncate within the button.

2026-09-07 · Unified workbench navigation and rounded Qokit surfaces

WorkspaceNavigationDock reuses the host sidebar and its permissions on desktop; items, fallback, className and onClickCapture adapt its contents without loading another session. Expanded, icon and hidden states share the existing preference. Hosts can set hoverReveal={false} to disable navigation previews from the trigger and window edge while retaining explicit controls and drag resizing; the default remains true. At 860px and below, navigation uses the shared drawer. PlatformHeader.leadingContext also appears in EditorHeader, preserving workspace and project switching. Pill buttons and rounded content surfaces remain; repeated outlines are removed.

On desktop, clicking the menu hides the sidebar or restores its last visible mode. Dragging the menu or sidebar edge snaps between hidden, icons and expanded states. Left/right keys follow the reading direction. Cancelled drags keep the saved preference; mobile keeps the navigation drawer.

Mount WorkspaceLocationSync once under Suspense in a Next layout. useWorkspaceQueryState(key, defaultValue, validate) returns [value, setValue, ready]; useWorkspaceQueryRecord(key, defaults, validators) restores only declared flat filters. Keep credentials and drafts out of URLs. WorkspacePage restores bounded session scroll positions; nested scrollers use data-workspace-scroll-region with WorkspaceScrollRestoration. Native cancellable Back/Forward transitions reuse leave protection without adding history entries; other browsers retain their existing fallback. AdminEntityDialog retains input after failed saves and parent rerenders; hosts still own versions and save results.

Management typography uses stable roles: page title 20px/650, section title 16px/600, body and navigation 14px, labels 13px, captions 12px. --qk-workspace-body-ink and --qk-workspace-active-ink derive from existing platform colors.

Primary pill buttons retain the Logo-blue fill #4695D8 and use white text, icons and loading indicators in both themes. Hover keeps the existing slight brightening. Secondary and danger buttons retain their own semantic colors.

Dropdowns and workspace switchers share --menu-option-font-size (14px) and --menu-option-font-weight (500), with a 1.45 line height; selected options use weight 600 and metadata uses 12px/400. WorkspaceNavigationDock prefetches same-origin destinations on mouse hover or keyboard focus, with bounded deduplication. Navigation still uses the existing leave guards and host routes.

2026-09-07 - ColumnLayout

Desktop management hosts using ColumnLayout fill the viewport with docked navigation, independent content scrolling and a sticky page toolbar. WorkspacePage uses flat sections and shared control-radius Tokens. Navigation remains a drawer at 860px and below; closed drawers are inert. Props and business behavior are unchanged. Remove duplicate outer gutters and limit reading width within forms.

Import Entry Points

import { Button, Card, Dialog, IconButton } from '@qokit/components/ui';
import { PlatformHeader, SiteFooter } from '@qokit/components/patterns';
import { platformButtonSkin } from '@qokit/components/skins/platform';
import { siteCardSkin } from '@qokit/components/skins/site';
Entry PointPurpose
@qokit/components/uiBasic components like Button, Card, Dialog, Menu, Pill, etc.
@qokit/components/patternsCompositions like Header, Footer, Workspace, Table, Resources, and AI Assistant
@qokit/components/skins/platformPlatform and Workspace visual recipes
@qokit/components/skins/adminAdmin visual recipe
@qokit/components/skins/siteGenerated site visual recipe

Public Responsibility Boundaries

PromptPanel accepts optional referenceReader and localized referenceCopy props. The reader provides asynchronous file(File, AbortSignal) and website(url, AbortSignal) operations returning extracted contentExcerpt and a truncated flag; authentication and API access belong to the host. With a reader, the component manages reading, preview, retry and removal. Valid website input enables submission even without prompt text; referenceCopy.websitePrompt supplies the localized request in that case. Format errors use referenceCopy.errors.url and prevent fetching. Clicking Submit while the website is unread or reading waits for fresh content, then dispatches the form submission once. Changed input or a read failure cancels that pending submission; retrying a failed read does not revive it. Files must be ready before submission. Website references are read automatically when a complete address is pasted, the input loses focus, or Enter is pressed. Initial URLs without a reading result are also read automatically; pending and completed results are reused, and failures expose an explicit retry action. Editing or removing the URL cancels the previous read and clears its result. Reader-free integrations keep native form submission without asynchronous reference processing.

Reference ingestion was added as an optional, backward-compatible component capability in September 2026.

Skeleton components guarantee:

  • DOM and semantic tags;
  • ARIA, keyboard, focus, and disabled behaviors;
  • State and basic interactions;
  • Stable default classes;
  • Named Skin slots.

Skins can:

  • Add classes to slots like root, header, body, item, action;
  • Pass CSS variables via vars;
  • Use component-published tone, layer, or visual adaptation switches.

Skins must not request data, modify DOM, hold business rules, or bypass accessibility behaviors.

Generated Element Content

Generated custom sections continue to use registered html-* elements in Schema v2, not executable HTML or a new block type. Since September 2026, @qokit/site-schema provides bindSiteModuleContent, updateSiteModuleBoundContent, and forkSiteModuleContentBindings for locale-backed element content. Persist content paths in module content, store visitor copy in the locale content map, and use the existing undo/save transaction around updates. Copying or moving an element to another block must fork its bindings to avoid changing the source.

Optional extensionRequirements records unresolved runtime needs; it is not an installation manifest or permission grant. createSiteExtensionHandoff exports an inert version-1 development request. Such requirements must be resolved or explicitly excluded through review before publishing a runnable site.

Form Controls

Shared forms use FormField for label, description, required metadata, error association, and control IDs. Text-like controls use Input; multiline content uses Textarea; choice controls use Checkbox, RadioGroup, and Switch. Existing Select and SearchField use the same size and state contract.

import { FormField, Input } from '@qokit/components/ui';

<FormField label="Site name" description="Up to 60 characters" error={errors.name} required>
  <Input name="name" value={name} onChange={handleChange} />
</FormField>;

FormField connects its label, description, and error to its single child control through id, aria-describedby, aria-invalid, and required. Integrators should not manually wrap shared controls in an additional <label>.

Input, Textarea, Select, and SearchField support sm, md, and lg control sizes, mapped to 40px, 44px, and 48px. Single-line controls default to the pill shape; Textarea always uses the shared rounded multiline shape. Error, disabled, readonly, hover, active, focus, and focus-visible appearances come from shared Tokens.

The legacy .qk-field contract remains available during migration, but new integrations should use the shared components and named Skin slots rather than route-owned selectors.

List Selection

Since September 2026, list integrations can use useWorkspaceSelectionMode({ enabled, resetKey, onClear }) with WorkspaceFilterToolbar.selection. The hook starts inactive, resets when list scope or permission changes, and separates clearing selected IDs from exiting bulk mode. Scope keys should include the collection, language, pagination and active filters; refreshes within the same scope need not exit the mode.

Only pass WorkspaceDataTable.selection while the mode is active. Grid or mobile checkbox controls must use the same mode. The toolbar owns Select, Done, select-visible and Clear; consumers supply localized copy, eligible visible IDs and permission-checked domain actions. Optional actionContent supports domain controls with additional ARIA semantics, such as a scheduling disclosure. It does not replace common selection controls or confirmation requirements. Read-only lists do not expose bulk mode; file pickers and proposal-review checkboxes retain their task-specific selection semantics.

These additions are optional and backward-compatible; table selection is still explicitly controlled by its consumer.

Data Cards

DataCard provides a title and optional headerAction, body content with an optional emphasized value, and optional footerText and footerAction. Pass other body content as children. density="default" has a 144px minimum height and 20px padding; density="compact" has a 112px minimum height and 16px padding. Cards grow when content needs more room. variant selects the shared Card surface: surface, muted, or state. Choose these shared sizes instead of overriding height, padding, or value typography in route CSS.

Use shared UI controls in action slots. Keep the card root non-interactive when it has actions; a whole-card action cannot contain nested buttons or links. MetricCard composes the same skeleton and retains label, detail, semantic tone, and optional visuals.

import { DataCard, MetricCard } from '@qokit/components/patterns';
import { Button } from '@qokit/components/ui';

<DataCard
  title="Published"
  value={24}
  headerAction={<Button size="sm" variant="ghost">View</Button>}
  footerText="Up 3 from last week"
  footerAction={<Button size="sm" variant="secondary">Details</Button>}
  density="compact"
/>;

<MetricCard density="compact" label="Published" value={24} tone="success" />;

Logo defaults to a static image. With motion="breathe", it reserves its initial dimensions and starts drawing when at least half visible. While the page loads, it approaches roughly 80% over 4.8 seconds and holds. The browser load event triggers a 900 ms finish from the current drawing; an already loaded page uses a direct 1.8-second entrance without waiting. This is a visual phase, not a measured resource percentage; load does not cover asynchronous business requests. The controller uses one load listener, visibility observation and CSS animations, with no polling or per-frame React updates. motionVisibilityDelayMs defaults to zero. motionOnceKey shares a playback record across remounts in the same document, with independent platform header and footer keys. Navigation, theme changes and scrolling back do not replay a consumed key; a full reload resets it. Reduced motion, disabled JavaScript and unavailable visibility observation show the static logo. motion="reveal" remains an alias.

PlatformHeader is a Header skeleton without business state. PublicPlatformHeader composes brand entry, public navigation, language, theme, login, "Try Now", and mobile menu on top of it; the platform's anonymous state and documentation site directly reuse this composition.

PlatformHeader.autoHideOnScroll defaults to false; PublicPlatformHeader enables it. The header hides when the page scrolls down and returns when scrolling up or near the top. Open header menus and focus within the header keep it visible. Workspace and editor headers remain stationary.

PublicPlatformHeader.workspaceAction optionally supplies { href, label } for an authenticated visitor's return link. It replaces the desktop login icon and stays visible beside the mobile menu; the mobile menu then omits anonymous account actions. Session detection belongs to the host. The platform home uses a lightweight local session check, updates after focus/storage changes, and keeps ?view=public on its brand link so explicit website visits survive refresh.

Public navigation is uniformly generated via buildPublicHeaderNavItems(copy, links) as "Resources / Pricing / News". Integrators should only parse intra-site, documentation site, and platform URLs for the current application, and should not redefine menu order or copy. The logged-in platform Header also uses the same generation function.

<PublicPlatformHeader
  copy={headerCopy}
  links={{
    brandHref: '/',
    resourceCenterHref: '/resources',
    userManualHref: 'https://docs.qokit.com/manual',
    developerDocsHref: 'https://docs.qokit.com/developers',
    changelogHref: 'https://docs.qokit.com/changelog',
    pricingHref: '/pricing',
    newsHref: '/news',
    loginHref: '/login',
    studioHref: '/studio'
  }}
/>

The underlying navItems still supports link, scroll, and menu. menu supports click, keyboard, Escape, and outside-click-to-close on desktop, while mobile expands into link groups via MobileHeaderMenu.

SiteFooter is the Footer skeleton; the platform and documentation site use PublicPlatformFooter to uniformly compose the outer Shell, brand entry, links, theme, and language controls. Cross-domain integration converts relative platform links to absolute addresses via resolveCompanyHref.

<PublicPlatformFooter
  brandHref="https://qokit.com"
  copy={footerCopy}
  resolveCompanyHref={(href) => `https://qokit.com${href}`}
/>

Business applications must not duplicate Header, Footer DOM, or public navigation arrays; for different visual presentations, use PlatformHeaderSkin, SiteFooterSkin, or the corresponding platform Skin.

Compatibility Strategy

  • Adding optional properties and Skin slots is a backward-compatible change;
  • Deleting properties, modifying default semantics, or changing DOM/keyboard behavior is a breaking change;
  • Breaking changes must be recorded in the Changelog with migration examples;
  • Do not rely on unpublished internal classes, directories, or routing structures;
  • When two or more integration points require the same overrides, promote them to public Skins or Tokens.

Full-screen editing

EditorWorkspace combines a full-screen dialog, focus management and responsive panels. Use dirty to confirm discarding changes, busy to block closing during saves, and onSave for Ctrl/Cmd+S. Hosts own permissions, data, saving and publishing.

workspaceNavigation connects the host's shared business navigation through EditorWorkbenchChrome: desktop navigation reserves space beside the content, while mobile uses the shared drawer. It is separate from the document structure panel navigation and retains the host's permissions and unsaved-change protection.

view / onViewChange select edit, focus, or preview without replacing the document editor. preview supplies a preview; previewPanel reuses an existing panel. layout supports writing, structure, and canvas. storageKey remembers panel widths and collapse preferences, never document data.

onSaveAndClose returns true only after a confirmed save, false on failure, handled when the host navigated, or pending when domain validation needs a decision. Failures keep the editor open. Use closeBehavior="collapse" only when the host retains the draft. EditorSaveStatus displays host-confirmed state; EditorViewControls, EditorLeaveDialog, and useEditorLayout can also be composed in existing workspaces.

Keyboard migration: Segmented has one Tab stop and uses arrows / Home / End to switch choices. Dialog respects a child overlay consuming Escape; the editor then exits focus or preview before closing. LivePreviewToolbar.exitControl accepts the shared view controls. Save shortcuts call the host; publishing and permissions remain host-owned.

import { EditorWorkspace } from '@qokit/components/patterns';

<EditorWorkspace
  open={open}
  title={title}
  dirty={dirty}
  busy={saving}
  onClose={closeEditor}
  onSave={saveDraft}
  onSaveAndClose={saveDraft}
  saveState={saveState}
  layout="writing"
  storageKey="article"
  preview={preview}
  navigation={structure}
  inspector={properties}
  actions={saveActions}
>
  {editor}
</EditorWorkspace>

SidebarToggleSlot

SidebarToggleSlot places the existing sidebar toggle in a workspace header. Render one slot alongside one left sidebar. SidebarNavigation keeps ownership of collapse state, shortcuts and the mobile drawer; without a slot it keeps its original controls. The header button also closes the mobile drawer; closing restores focus to that same button.

EditorSaveButton.showIcon keeps the save glyph beside its label. iconOnly reduces the control to an icon while retaining an accessible action and status name and tooltip. Editor hosts can use useCompactWorkspaceHeader() to show icons and labels in roomy layouts and icons alone in compact layouts. EditorStatusAction.iconOnly follows the same rule while retaining its issue count.

EditorHeader

EditorHeader keeps the host logo, account and global menu inside the active editor. startControl and endControl toggle the corresponding side panels; center holds view commands and actions holds save commands. PlatformHeader.editorActions reuses the responsive navigation, language and appearance controls. onNavigate must resolve unsaved changes before running its callback. On narrow screens the header uses two rows, and nested menus consume Escape before the editor does.

contextAfter places editor-specific scope controls after the host project picker, preserving their DOM and keyboard order. The host retains project navigation and leave guards; the editor owns page and content-language selection. Hosts may adapt the responsive layout to put this context on its own row.

WorkspaceHeaderPortal.startControl and endControl place managed-page panel toggles in the host's matching slots. Hosts expose optional startTarget and endTarget alongside title, status and actions. The Files library and single-asset workspace use workAreaControls; asset preview keeps the full header so its identity, return action and panel destinations stay available. ProjectWorkspace owns the shared left navigation/conversation choices for Content and Files. Files registers its remembered resource-panel dimensions through useProjectResourcePanel, portals navigation through ProjectContentTools, and supplies only its right inspector control through ProjectToolbar.endControl. Conversation uses the same left lane and embedded composer across project areas; compact resource, conversation and inspector tasks are mutually exclusive.

EditorNavigationMenu

EditorNavigationMenu reuses the host’s full SidebarNavigation in an overlay, preserving permissions and project context without resizing the canvas. Language and theme stay at the bottom; nested menus handle Escape first. Focus and native browser fullscreen are independent; navigation waits for pending saves and protects drafts.

WorkspaceNavigationMenu / WorkspacePageHeader

Global navigation uses Command+\ on Mac or Control+\ on Windows/Linux, including inside Creator. Trigger hints and aria-keyshortcuts expose the combination. The shortcut ignores editable targets, composition, repeated and already-handled events. Creator retains T and Shift+T for its editor layout; global navigation no longer consumes bare T.

Signed-in workspaces use PlatformHeader.workspaceActions for one account and navigation area at every width. WorkspacePageHeader shares titles and actions. WorkspaceNavigationMenu displays the current sidebar, preserving permissions and context; EditorNavigationMenu remains a compatible alias. Studio keeps its task toolbar. Public headers retain their existing presentation.

WorkspaceNavigationMenu.footerLinks supplies direct icon links alongside the sidebar display control. footerMenus accepts ordered WorkspaceNavigationFooterMenu entries, each with a label, icon and link items (with optional separatorBefore). The platform uses one menu for Website Home, Pricing, Templates and News, and a book-icon Help & Support menu for the user manual and contact support. The single footerMenu prop remains supported when footerMenus is omitted. Desktop menus open upward with ActionMenu placement="top" portal; mobile uses bottom sheets. The controls form one row when expanded and a column in icon mode; on mobile the sidebar control closes the navigation drawer. Each icon retains an accessible name and tooltip. profile adds the user name, plan and account menu without duplicating an existing sidebar account. Omitting footer links and menus retains the existing preferences and fullscreen actions.

Set a footer menu item's newTab to open a reference destination with target="_blank" and rel="noopener noreferrer". The skeleton adds a trailing arrow and localized screen-reader notice; other items keep current-page navigation. Website Home, Pricing, Templates, News, the manual and contact support use new tabs so the workspace stays open. An explicit public-home visit preserves ?view=public to bypass the signed-in landing redirect, including after refresh.

WorkspaceNavigationGuard protects global navigation with dirty, busy, error and optional onSave. Saving must resolve to true before leaving; failure retains the draft. Language.onBeforeChange(apply) lets the host defer a language change through the same guard. Keep form fields disabled while saving.

Desktop navigation retains expanded and icon modes and adds auto-hide. The docked sidebar and drawer share search and section state. When hover previews are enabled, fine-pointer edge hover opens a temporary preview after 300ms and closes it 320ms after leaving; clicking keeps it open. Touch and keyboard retain explicit controls. Dialog defaults to modal={true} and autoFocus={true}; a hover preview sets both to false to preserve input focus and scrolling.

Editor tool palettes can use Dialog with keepMounted to preserve search and form state while closed. Closed dialogs immediately become inert, hidden from assistive technology, and leave the focus stack, including during a visual exit transition; the default still unmounts their content. Pair nonmodal palettes with DialogPanel to reuse the global overlay surface. Toolbar accepts a DOM ref for bounded positioning while retaining its shared arrow-key navigation.

useFloatingSurface from @qokit/components/patterns/FloatingTools supports defaultHeight: 'auto' for content-sized palettes. Keep the host body shrinkable with internal scrolling; the hook caps the surface to its workspace bounds and observes size changes. Moving an automatic palette stores its position without freezing the measured height. Resizing explicitly stores a fixed height, including across reloads; reset() or Home on a movement/resize handle restores automatic sizing. Numeric defaultHeight retains the existing fixed-height behavior.

FloatingToolPanel composes the shared DialogPanel, TreeToggle, pin button, tooltip and close button. Place it inside a nonmodal Dialog; the host controls pinned, collapsed, their callbacks and document operations. Pinning keeps the palette open after an operation; it does not lock its position. The title and header whitespace accept useFloatingSurface().dragHandle, while buttons, menus and inputs never initiate dragging or folding. Double-click the title or whitespace to fold; the explicit fold button supports keyboard and touch. Folding hides the body without unmounting it, preserving searches and tree state. Pass the same collapsed value to useFloatingSurface to retain the expanded height while moving the folded header. Optional actions and skin slots reuse the same structure; styles stay in the shared stylesheet.

Optional FloatingToolPanel.viewKey adds a short opacity transition when the active tool changes, without replacing its body instance. Ordinary parameter updates do not animate. Opening, closing, unfolding and pin feedback share the existing motion Tokens and respect reduced motion. Dragging stays direct; useFloatingSurface coalesces pointer movement to one geometry update per animation frame and saves the final position on release. Browsers without discrete display transitions close immediately.

EditorViewControls

Unified editors pass focus={false} to omit the separate Focus control. primaryActions accepts shared tool buttons before Preview; onTogglePanels handles T, and onToggleAllPanels handles Shift+T. Creator uses T to cycle from visible panels to floating launchers to fully hidden and back to the last visible layout; ordinary launcher clicks still open their panel. Shift+T directly hides everything and restores the exact preceding state. Both sidebar shortcuts are inactive in Preview and respect editable targets and active overlays. Existing hosts keep Edit/Focus behavior by default.

useWorkspacePanelVisibility().togglePanels hides the visible editor panels or restores their preceding layout. Desktop and compact layouts are remembered independently, and forceCollapsed (for example during Preview) does not overwrite that memory. The host owns global navigation visibility and any edge launchers.

One button switches both ways: Edit shows Focus, and Focus shows Edit. Click it or press T; E still returns directly to Edit. On narrow headers, the switch stays visible and Preview, Fullscreen and extra actions appear in More.

EditorViewControls separates Edit/Focus from native screen fullscreen. Preview is an independent toggle and returns to the previous editing mode; useEditorWorkMode preserves that mode for custom exit actions. The existing edit/focus/preview values remain supported. Preview now uses a button with aria-pressed instead of a radio in the mode group. Fullscreen requires an explicit click, keeps navigation and dialogs inside the application root, and is hidden when unavailable.

Language / Appearance

Language and Appearance variant="menu" accept optional layout="row" to display a label, current value and chevron. The default compact layout and language-change guard remain unchanged. SiteHeaderCopy.helpResources and contactSupport optionally label workspace help links.

requestWorkspaceNavigation

Pages with a sidebar toggle omit the extra header menu button, including collapsed and mobile layouts. Editors and pages without a sidebar keep it. Import requestWorkspaceNavigation(returnFocusTarget?) and useWorkspaceNavigationState() from @qokit/components/patterns/WorkspaceNavigation: the request toggles the registered drawer and returns false when none is available; the optional element receives focus on close. Check .available before showing another entry. Use the existing toggle or this API instead of depending on the removed button’s DOM position.

WorkspacePanelReveal

Global navigation uses a menu icon; editor tools use directional panel icons. useWorkspacePanelReveal({ temporary: true }) allows click and keyboard access to temporary tools in Focus. toggle(trigger?) and close(true) preserve the saved layout and work mode and restore focus when closing. Hosts that use persistent sidebars can enable this hook only during Focus and disable navigation hover previews through WorkspaceNavigationDock. Preview hides editing panel toggles and offers Return to editing, restoring the previous editing mode.

For floating editor panels, pass skin: platformWorkspacePanelRevealSkin from @qokit/components/skins/platform and spread the returned panelProps onto the existing panel. The skin applies only while revealed; the docked panel and its mounted content remain intact. ResizablePanels merges startPanelProps, middlePanelProps, and endPanelProps class names with its own skin slots. Pair focus controls with Toolbar and platformFloatingToolbarSkin for shared keyboard navigation and compact spacing. Both skins share the global DialogPanel surface (background, shadow and blur); panel corners use the card radius and toolbar corners use the control radius. Hosts own positioning and available space, not a separate overlay palette.

useWorkspacePanelEdgeDrag is an opt-in hook for an existing workspace root ref. Mark its focusable borders with data-workspace-panel-edge="start" or "end"; ResizablePanels supplies these attributes on its own separators. The host provides each side's mode (expanded, icons, hidden), saved width and bounds through getState, applies onChange, and returns a rollback callback from onBegin. onResizing should suspend layout transitions; onFinish restores focus to the resulting control, and onReset restores the host's default width. One captured mouse or touch gesture crosses all three states, with RTL direction handling and cancellation on Escape, pointer cancellation or window changes. Arrow keys resize or step states, Shift increases the step, Home/double-click resets, and End expands to the allowed maximum. This hook adds no visual controls or stored content. Hosts can pair hidden borders with useWorkspacePanelReveal for temporary shortcut access while retaining their normal click actions; hosts without the hook keep existing resizer behavior.

EditorViewControls / Display mode

EDITOR_VIEW_SHORTCUTS → Tooltip + aria-keyshortcuts

EditorHeader also owns EDITOR_TOOLBAR_SHORTCUTS: Command/Control+S invokes its visible EditorSaveButton, Shift+P opens an EditorStatusAction shortcut="publish", and Shift+M opens its editor tools menu. These commands use the same enabled controls as pointer actions. Publication remains a separate explicit action inside its panel. Only the active visible header responds; child menus/dialogs, composing/repeated events, and editable targets (except Save) are excluded. Hints and aria-keyshortcuts share the command definitions. A custom toolsControl supplies aria-keyshortcuts={EDITOR_TOOLBAR_SHORTCUTS.tools.aria} on its trigger. ActionMenu.triggerKeyShortcuts adds that attribute and a shared tooltip hint without registering a global command.

Panel commands use Shift+A (Add), Shift+L (Pages/Layers), Shift+K (Conversation), Shift+C (Content), Shift+D (Design), and Shift+G (Global style). CMS adds Shift+S (Settings), Shift+E (SEO), and Shift+H (History) when available. Pass shortcut metadata to EditorChoiceControl/EditorViewTabs options and ActionMenu items for shared hints. EditorPanelChoiceShortcuts retains the same host actions when choices fold into a menu; EditorViewControls.compactActions does the same for phone tools. Custom EditorPanelShortcuts.commands can register their existing actions in the active header without rendering duplicate controls. Hidden/inert, disabled, preview and overlay restrictions still apply. Non-modal phone sidebars in the same workspace allow switching panels; menus and modal dialogs continue to block shortcuts. Unmodified editor keys retain their existing behavior.

Display mode
EEdit
TEdit ↔ Focus
VPreview / Return to editing
FEnter full screen / Exit full screen

Only the active editor handles these keys. Typing, IME composition, held keys and open child dialogs or menus do not switch modes.

PlatformHeader.workspaceNavigation

PlatformHeader.workspaceNavigation places global navigation before the logo; workspaceActions and editorActions retain account actions. Workspaces reuse the existing sidebar toggle, and editors place the right panel toggle before the avatar. Narrow screens put navigation, branding, title and avatar above editing tools and Save. DOM order follows the layout; borderless frosted chrome is preserved.

2026-09-06 - EditorHeader.preview / EditorViewControls.returnView

EditorHeader.preview keeps only center as a compact borderless preview toolbar; logo, account, save and panel controls remain mounted but hidden. Hosts with a separate LivePreviewToolbar may hide the editor header and pass EditorViewControls.returnView (edit or focus) to restore the preceding mode. Keep accessible return and independent fullscreen controls; the website's own header remains in the preview.

2026-09-06 · Builder / CMS

Builder and CMS content editing share BuilderWorkspace, EditorCatalog and EditorComponentSettings for panels, insertion graphics and presentation controls. Preset changes apply their linked settings together and preserve authored content; each host owns persistence and undo. Workspace controls follow the platform theme, while rendered content follows the site theme.

2026-09-07 · WorkspaceAssembly

WorkspaceAssembly marks outgoing cards and incoming workspace sections without adding a layout box. For hosts with direct-child layout contracts, place workspaceAssemblyAttributes(part, index, phase) on the existing DOM element. EditorHeader.assemble and BuilderWorkspacePanels.assemble provide these markers for editor chrome.

Call await startWorkspaceAssembly(navigate, destinationPathname) only after creation succeeds. It snapshots visible pieces, navigates once, and assembles the destination workspace or its matching loading skeleton in up to 720 ms. The destination must expose an incoming canvas marker. Use useWorkspaceAssemblyPending() to keep that loading surface mounted until its snapshots settle; preload editor data and code during the handoff. Reduced motion and unsupported browsers navigate directly; slow or interrupted transitions release their snapshots and continue navigation. Markers alone never animate edits, reloads, or history navigation. The helper owns temporary styles and their cleanup; hosts retain creation errors, idempotency and loading state.

SiteFooterLayout accepts an explicit locale and a single-language copy. Server Components render the shared footer structure; theme and language controls and the QR dialog remain client components. The existing SiteFooter and PublicPlatformFooter interfaces remain supported.

import { SiteFooterLayout } from '@qokit/components/patterns/SiteFooter';

<div className="qk-platform-footer-shell">
  <SiteFooterLayout locale={locale} copy={footerCopy} />
</div>

Resolve cross-domain links in copy.companyLinks on the server. Supply controls to customize the interactive control slot.

EditorHeader.titleControl / FloatingAssistant.presentation

EditorHeader.titleControl and EditorWorkspace.titleControl optionally replace the plain title with shared project navigation. Keep a descriptive title for the workspace identity and route navigation through the existing unsaved-change guard. FloatingAssistant.presentation="embedded" renders a labelled region inside a host panel without a floating launcher or backdrop; the default remains floating. The host owns placement and visibility, while conversation state and permissions stay in the assistant.

FloatingAssistant.headerActionsTarget optionally accepts an HTMLElement in the host heading. The assistant portals its existing conversation history and new-conversation controls into that element and omits its internal header. Without a target, the original header remains. The host owns the heading and placement; the assistant retains action handlers, accessibility labels and conversation state. The Web adapter forwards this slot.

FeatureHint · 2026-09

FeatureHint is exported from @qokit/components/patterns/FeatureHint. Use it for contextual first-use guidance attached to a real control. Provide a versioned id, a stable user scopeKey, an anchor: HTMLElement, an active eligibility signal, localized title, description, dismissLabel, and action: { label, onClick }. Set completed when the user discovers the capability independently. A null scope or unavailable anchor suppresses the hint.

The shared component allows one hint at a time, waits briefly for a visible target, follows scrolling and resizing, supports RTL, and keeps content inside the viewport. It does not add a backdrop, steal focus, or perform the action automatically. Escape, the close button, or clicking elsewhere dismisses it; Tab from the target reaches the action. The target receives a temporary highlight and accessible description. Seen hints are remembered in the current browser per scope and version, with an in-memory fallback if storage is unavailable; this is not cross-device progress. Hosts own permissions, review-state suppression and the actual action. skin, className and style adapt presentation.

AssistantContextCard

AssistantContextCard is exported from @qokit/components/patterns/FloatingAssistant. Place it in composerContext to summarize the current editing target. Its typed contract includes title, description, scope, preview, parameters: { id, label, value }[], optional controls, status and notice, plus actions, onLocate and clearAction. Pass localized labels and formatted values, including units, from the host.

The card renders a read-only definition list, an optional controls slot for a few common adjustments, and a live status region. Reuse the host’s existing editing controls and commands in this slot; keep complete settings behind an explicit action that opens the existing inspector. Hosts retain ownership of selection, permissions, save, undo and AI requests. Conversation, canvas editing and inspector editing can operate together, with independent panel visibility. Selecting an object updates the card and an already open inspector without opening a closed panel or moving focus. Removing a conversation reference preserves canvas selection and direct editing; keep the conversation entry independent of this card and of floating-tool visibility. Changing the target or a parameter updates this live card without appending chat messages. Both draft and project conversations can use the same component. className, style and AssistantContextCardSkin support visual adaptation; styles are loaded with the component.

2026-09 · Management workspaces

WorkspacePage and WorkspaceLayout accept variant: overview, list, detail, settings or editor. WorkspaceFormFooter places host-provided actions, message, tone and busy feedback beside the save action; it does not save data.

Narrow WorkspaceDataTable and AdminDataTable layouts now default to labeled records, preserving selection, custom headers and actions. Set mobileLayout="scroll" for comparison matrices that must retain aligned columns. Sidebar titles use h2; the page owns h1.

2026-09-08 · Task focus

useSidebarTaskFocus(active) temporarily hides navigation during a focused task. It restores the prior display on exit unless the user explicitly changes the navigation mode; automatic hiding does not overwrite the saved preference.

FloatingAssistantPanel.composerContext 接收输入框上方的实时上下文区域。提供此插槽时,顶部旧的 activeContext 摘要隐藏,activeContext.promptPlaceholder 仍供输入框使用。实时参数属于当前编辑状态,不应追加到历史消息列表;Web 适配器透传此插槽。

The Web adapter also forwards FloatingAssistantPanel.composerAttachments. This slot renders host-owned attachments inside the message form, before the textarea. The host owns grid placement and the submission lifecycle: dropping stages an attachment; successful completion clears only the submitted attachment; failures preserve it for retry.

Conversation · Creator shared surface

@qokit/components/patterns/Conversation exports ConversationPanel, ConversationMessages, ConversationMessage, ConversationSuggestions and ConversationComposer. Creator generation, draft refinement and the embedded project assistant use these structures and the same token-based stylesheet. Hosts own requests, history, permissions, selected objects and review/apply actions.

ConversationFeedback composes InlineNotice for compact task status, failure, fallback and save receipts within conversations. Supply a localized title, optional description, tone and action. It uses the caption size for both lines, a compact gap and a transparent surface; tone emphasizes the status while supporting text stays muted. The default role="status" and aria-atomic="true" announce the whole update together; use role="alert" for actionable failures. Assistant-authored prose remains in ConversationText.

Place the scrollable ConversationMessages and the fixed ConversationComposer directly inside the panel. Supply a localized label for the messages region and inputProps for the controlled textarea. The composer accepts attachments, notice and actions slots, plus formProps and formRef; it creates the form, so do not nest it in another form. Enter inserts a newline; Cmd/Ctrl+Enter requests submission with composition and disabled/busy guards. Preserve user input while a request is running when the host supports it.

PromptPanel.presentation="conversation" reuses the composer while retaining reference reading, upload/menu controls and serialized form fields. The default "prompt" preserves the landing-page prompt behavior. FloatingAssistant.presentation="embedded" uses the shared panel, messages, suggestions and composer; floating assistants retain their compact presentation.

2026-10-08 · Shared list toolbar groups

WorkspaceFilterToolbar now has one container-responsive contract across Projects, CMS and Admin:

  • query: search, status filters, sort, domain controls, advanced options, conditional reset, resource result and auxiliary summary.
  • presentation: view, display controls and options such as visible columns and page size. Page widget customization belongs in the page header actions.
  • actions: persistent operations, followed by the optional selection control at the logical end. Use ToolbarButtons with icon and localized compactLabel for refresh and other familiar actions.

The shared component measures its own available width. Controls show icons with labels above 960px and accessible icon buttons at or below 960px. At or below 640px, search occupies the first row and tool groups wrap in query → presentation → actions order. Routes must not override group widths or hide individual labels. ControlMenu and ViewMenu inherit this presentation without a route-specific responsive flag.

Use query.result={{ label, count, total?, locale? }} for a resource name and result count. The shared WorkspaceResultSummary renders “Name · count”, adds “/ total” only when a reliable unfiltered total differs, formats numbers for the UI locale, and isolates bidirectional numbers. Omit result until a count is known; zero is a valid result. Do not add a separate title/count row above the same list. AdminFilterBar.result accepts the same object. Keep page headings, meaningful section headings, pagination and selected-object counts in their respective roles; use query.summary for different units, query context or freshness information.

Give overflow a localized label to move advanced and display options into More when compact. query.compactItems and presentation.compactItems supply complete menu choices replacing their corresponding controls; controlled values and callbacks remain in the host. Permanent menu actions use overflow.items. Selection and refresh stay outside More. Select and Done share the end slot, hit target and reserved idle toolbar height, including wrapped mobile rows.

This replaces the old flat toolbar API: migrate search, filters, sort, reset and secondaryControls into query; migrate view and display controls into presentation; move persistent endActions to actions. The former adaptive / inline-wrap CSS modes and WorkspaceFilterControlGroup capsule are removed; use these three semantic groups rather than compatibility aliases.

CustomizableWidgetLayoutControls / CustomizableWidgetLibrary

Place CustomizableWidgetLayoutControls in the page header actions after contextual help and before the primary action, including on mobile. Use localized copy.customize to name the action explicitly (for example, “Customise widgets”). The same icon-only entry exposes aria-pressed and aria-expanded, and becomes copy.done while editing. customizeButtonRef optionally exposes the trigger for host focus restoration; disabledCustomize disables the entry without changing its geometry. Supply onCollapseToggle and areWidgetsCollapsed only for hosts that support collapsing widgets; omitting them renders the customization entry alone.

CustomizableWidgetLibrary owns the common library heading, reset/close actions, responsive scrolling layout, initial close-button focus and Escape handling. Closing returns focus to the invoking control when focus is still inside the library; outside clicks keep their destination focus. Hosts keep widget definitions, add/remove/order/resize commands, persistence and reset semantics. CMS and Admin class slots remain available for domain hooks, but must not define separate library surfaces or mobile layouts.

2026-10-15 · EditorControlGroup title actions

The headerActions slot on EditorControlGroup remains visible in both expanded and collapsed groups, for actions such as content visibility beside a group title. Pointer and keyboard interactions with these actions do not toggle the group. summaryActions still appears only when collapsed. Hosts own action names, state and persistence; icon actions must use the shared IconButton with a localized accessible name.

2026-10-10 · EditorItemDisclosure

EditorItemDisclosure from @qokit/components/patterns/EditorItemCollection accepts title, summary, open, onOpenChange, leading, actions and children for editing within a list. Sibling items remain visible. Escape collapses the item and restores trigger focus; opening does not scroll or autofocus. useEditorItemDisclosure scopes single-item expansion with scopeKey and restores adjacent focus after deletion. EditorItemCollection uses the same interaction; hosts still own content, ordering, persistence and undo. The existing EditorFocusedItem export remains available for flows that require a separate detail view.

2026-10-14 · Management groups and summaries

WorkspaceSectionGroup, WorkspaceSection, WorkspaceFieldGrid and WorkspaceFacts are exported from @qokit/components/patterns/WorkspaceLayout. Headings and descriptions sit above their content panels on both desktop and mobile, sharing the starting edge. Use the default stacked layout; legacy layout="split" callers also render stacked. Apply qk-workspace-section-group__form to forms within a group to share spacing and save-area alignment. WorkspaceSection accepts optional icon, actions and description slots, keeping headings outside the content panel.

WorkspaceFieldGrid arranges independent short fields in at most two columns according to available width. WorkspaceFacts renders a semantic definition list with stable id, label, value, and optional unit, description, emphasis and tone. columns supports 2, 3 or 4 columns and adapts to narrow containers. Set mobileColumns={2} for short numeric summaries that should retain two columns on phones; the default is one. It is unboxed so summaries can share an existing content panel. Each component supports its named Skin, className and style. Hosts retain form state, permissions, submission, conflicts and recovery; these components do not make requests.

2026-10-14 · Management content panels and disclosures

WorkspaceContentPanel and WorkspaceSection.kind support summary, form, records, and actions. Section toolbar stays outside the content surface; supporting and footer provide compact metadata and end operations. titleId preserves existing heading anchors. The default panel container does not override a host's named container.

Use WorkspacePanelBlock, WorkspacePanelMeta, and WorkspaceRecordRow for subordinate groups, metadata, and repeated records. A record accepts title, description, meta, status, actions, and full-width detail children. Facts always align at the top. Hosts retain business fields, permissions, table columns, and submission boundaries.

WorkspaceActionRow accepts an optional action label or quiet empty/loading status, alongside description and actions. Action identity uses 14px semibold text, status uses 14px regular text, and descriptions use 12px. Copy and controls share a center line on desktop and stack at narrow widths. Card surfaces do not override descendant strong typography or spacing.

WorkspaceDisclosure accepts title, optional status, and children; WorkspaceDisclosureGroup accepts Accordion items and controlled expansion props. They start closed unless the host specifies an initial item, and open at most one sibling. Enter/Space toggles; Escape closes and returns focus to its trigger, handling inner disclosures before their parent. Hidden panels retain their DOM and input state. Optional headingLevel supplies section heading semantics; Skin and class slots only adapt appearance. Import these components from @qokit/components/patterns/WorkspaceLayout.

2026-10-17 · Rich ActionMenu triggers

ActionMenu.renderTrigger can reuse a rich control such as SelectableTile. It receives aria-expanded, aria-haspopup, disabled, and onClick; spread these onto the actual trigger. The host retains the control’s selection semantics and appearance. Portal positioning, menu keyboard navigation, dismissal, focus return, and optional mobile sheets remain owned by ActionMenu. The default button and icon triggers are unchanged.

Radius and range controls

RangeNumber from @qokit/components/ui/RangeNumber pairs a native range slider with an exact numeric Input. Supply label, value, min, max, optional step and unit, and onChange. An undefined value shows a mixed-value dash; changing either input sets one bounded number. onCommit lets the host group continuous changes into its existing undo history. disabled, keyboard navigation, compact density, RTL and focus styles are shared; persistence belongs to the host. RangeNumberSkin exposes root, range, input and unit slots.

EditorRadiusControl from @qokit/components/patterns/EditorRadiusControl combines a live shape preview, four physical corner inputs, RangeNumber and optional shape presets. Its value and onChange use CSS border-radius shorthand; cornerLabels and preset labels are localized by the host. Corners remain top-left, top-right, bottom-right, bottom-left in RTL. Supplying max restricts editing to bounded pixel values, while omitting it preserves CSS units and elliptical corner syntax. A mixed radius shows no single numeric value until the user sets all four together. The optional EditorRadiusControlSkin adapts root, diagram, preview and preset slots without changing state or persistence.

On this page

Component Integration2026-10-22 · Active navigation tabs on narrow screens2026-10-20 · Visual choice card actions2026-10-17 · Shared workbench panel motion2026-10-17 · Measured editor defaults2026-10-15 · Shared inspector choices2026-10-15 · Responsive workspace tables2026-10-14 · Independent editor panels2026-10-10 · Pagination dot display2026-10-10 · ActionMenu search header2026-10-09 · Inline ColorPicker2026-10-07 · WorkspacePanelGrid2026-09-30 · SelectionToolbar accessibility2026-09-10 · Workspace identity badges2026-09-08 · Editor context and inactive canvas2026-09-08 · ProjectSwitcher context and actions2026-09-08 · EmptyState2026-09-08 · SidebarNavigation2026-09-07 - AccountDropdown / SidebarProfile2026-09-07 - FormField / AdminEntityDialog / EditorWorkspace2026-09-07 · WorkspaceLocationSync / ProjectSwitcher2026-09-07 · Unified workbench navigation and rounded Qokit surfaces2026-09-07 - ColumnLayoutImport Entry PointsPublic Responsibility BoundariesGenerated Element ContentForm ControlsList SelectionData CardsPlatform Header and FooterCompatibility StrategyFull-screen editingSidebarToggleSlotEditorHeaderEditorNavigationMenuWorkspaceNavigationMenu / WorkspacePageHeaderEditorViewControlsLanguage / AppearancerequestWorkspaceNavigationWorkspacePanelRevealEditorViewControls / Display modePlatformHeader.workspaceNavigation2026-09-06 - EditorHeader.preview / EditorViewControls.returnView2026-09-06 · Builder / CMS2026-09-07 · WorkspaceAssemblyServer-rendered footer · 2026-09-07EditorHeader.titleControl / FloatingAssistant.presentationFeatureHint · 2026-09AssistantContextCard2026-09 · Management workspaces2026-09-08 · Task focusConversation · Creator shared surface2026-10-08 · Shared list toolbar groupsCustomizableWidgetLayoutControls / CustomizableWidgetLibrary2026-10-15 · EditorControlGroup title actions2026-10-10 · EditorItemDisclosure2026-10-14 · Management groups and summaries2026-10-14 · Management content panels and disclosures2026-10-17 · Rich ActionMenu triggersRadius and range controls