Kumo

The site notes that CodeHighlighted provides server utilities for SSR frameworks such as Next.js RSC, Astro, and Remix so highlighting can happen at build time (https://kumo-ui.com/components/code-highlighted). The changelog also mentions that missing “use client” directives in a past build broke components in Next.js App Router (https://kumo-ui.com/changelog.md). However, no specific Kumo components are identified as accessing browser-only APIs like window or document, and the site does not mention using Next.js dynamic imports with SSR disabled.

Create a dedicated Next.js / SSR integration guide that explicitly lists which components access browser-only APIs (e.g., window, document) and provides copy-paste dynamic import examples with SSR disabled.

Where we looked: /components/code-highlighted, /changelog.md

Kumo describes its components as "tree-shakeable" and recommends granular imports (e.g., `import { Button } from "@cloudflare/kumo/components/button"`) for better tree-shaking and smaller bundle sizes. However, the site does not explicitly state whether importing only a few components from the main `@cloudflare/kumo` barrel automatically tree-shakes the rest of the registry, nor does it mention whether you need to configure `sideEffects` in your own `package.json`.

Add explicit guidance to the Installation docs on whether consumers need to configure `sideEffects` in their `package.json` to enable tree-shaking, and clarify if barrel imports from `@cloudflare/kumo` are automatically tree-shaken or if granular imports are required to avoid unused code.

Where we looked: /installation.md, /components-vs-blocks.md, /installation.md, /installation.md

The streaming documentation focuses on LLM token streaming and progressive rendering of flat UI trees. It does not mention React Suspense boundaries, individual component streaming, or full-page streaming patterns.

Consider adding a section to the streaming documentation that clarifies whether Kumo UI supports React Suspense boundaries for individual components, or if streaming is limited to full-page LLM response patterns.

Where we looked: /streaming.md, /streaming.md, /streaming.md

The CommandPalette supports a flat array of items as well as single-level grouped items, but the documentation does not specify a maximum nesting depth for sub-commands or describe support for hierarchical nesting beyond groups.

Document whether the CommandPalette supports nested sub-commands or hierarchical drill-down, and clarify the maximum nesting depth if applicable.

Where we looked: /components/command-palette, /components/command-palette, /components/command-palette.md

The documentation does not explicitly state whether non-Gregorian calendars like Jalali or Hijri are supported out of the box. It notes that the DatePicker is built on react-day-picker v9, supports localization via date-fns locales, and forwards all react-day-picker props, but every example shows standard Gregorian dates (e.g., July 2026) and no non-Gregorian calendar modes are mentioned.

Add an explicit statement or FAQ on the DatePicker page clarifying which calendar systems are supported out of the box (e.g., Gregorian/ISO only) and whether non-Gregorian calendars can be configured via react-day-picker props.

Where we looked: /changelog.md, /components/date-picker, /components/date-picker, /components/date-picker.md

Kumo's Dialog supports rendering inside a portal, Shadow DOM, or custom container via the `container` prop and `KumoPortalProvider`, and the dialog renders the content underneath inert. However, the site does not explicitly state whether the focus trap stays scoped to the portal DOM node or if tabbing can leak back to the main document.

Add explicit documentation on focus trap behavior when Dialog is rendered inside a portal or Shadow DOM, clarifying whether tabbing is scoped to the portal container or can leak to the main document.

Where we looked: /components/dialog.md, /components/dialog.md, /changelog.md

The site documents that you install blocks via `npx @cloudflare/kumo add <block-name>`, but it does not mention whether the CLI auto-detects your package manager or if you must pass a flag like `--pnpm`.

Add CLI documentation explaining whether `kumo add` auto-detects the project's package manager or if users must pass a flag (e.g., `--pnpm`, `--npm`, `--yarn`).

Where we looked: /installation.md, /cli.md

The Kumo UI Grid component documentation describes its responsive layout variants (e.g., 2up, 3up, 4up), gap sizes, and props, but it does not mention whether the component uses CSS subgrid under the hood or specify any fallback behavior for browsers that do not support subgrid.

Add an implementation details or browser support section to the Grid documentation that explicitly states whether CSS subgrid is used and describes the fallback strategy for unsupported browsers.

Where we looked: /components/grid, /components/grid, /components/grid.md, /components/grid

The Kumo site describes a Figma plugin that generates components directly from `component-registry.json` — the same source of truth used by React components — and states that regenerating everything fresh on each run ensures the Figma file always matches the current state of the codebase. However, the chunks do not mention Figma community files, version-locking to specific Kumo releases, or whether published files typically lag behind React components.

Add explicit guidance on whether published Figma community files (if offered) are tied to specific releases and how users should expect them to stay in sync with React components.

Where we looked: /figma, /figma, /figma.md