Skip to content

[local-explorer-ui] Revert to default Kumo theme#13029

Draft
MattieTK wants to merge 2 commits intomainfrom
local-explorer-ui/use-default-kumo-theme
Draft

[local-explorer-ui] Revert to default Kumo theme#13029
MattieTK wants to merge 2 commits intomainfrom
local-explorer-ui/use-default-kumo-theme

Conversation

@MattieTK
Copy link
Member

Per feedback from the Kumo team – the orange Workers brand theme overrides are not yet ready to ship. This reverts the local explorer UI to use Kumo's default theme.

Summary

  • Removed the :root block that overrode --color-kumo-* and --text-color-kumo-* tokens with orange Workers brand values. Kumo's own theme-kumo.css defaults (neutral greys, blue brand) now apply.
  • Removed dark mode Kumo token overrides (--color-kumo-tip-shadow, --color-kumo-tip-stroke, --color-kumo-overlay).
  • Replaced the orange-tinted app design tokens (--color-bg, --color-text, --color-primary, surfaces, borders, etc.) with a neutral palette that aligns with Kumo's default aesthetic.

  • Tests
    • Tests included/updated
    • Automated tests not possible - manual testing has been completed as follows:
    • Additional testing not necessary because: visual-only CSS change to a private package; verified via pnpm dev:ui
  • Public documentation
    • Documentation not necessary because: internal UI change, no public API affected

…kers brand overrides

The Kumo team is not yet ready for custom orange themes to ship.
This removes the Workers-branded orange colour overrides from the
local explorer UI and replaces them with a neutral palette that
aligns with Kumo's default theme (neutral greys, blue brand accent).

Changes:
- Remove :root block that overrode --color-kumo-* and
  --text-color-kumo-* tokens with orange Workers values
- Remove dark mode Kumo token overrides
- Replace orange-tinted app design tokens with neutral equivalents
  matching Kumo's default aesthetic
@changeset-bot
Copy link

changeset-bot bot commented Mar 23, 2026

⚠️ No Changeset found

Latest commit: 0603693

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ask-bonk
Copy link
Contributor

ask-bonk bot commented Mar 23, 2026

No remaining references to the removed --color-kumo-* / --text-color-kumo-* variables in the package. The CSS-only change looks clean.

LGTM

github run

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 23, 2026

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@13029

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@13029

miniflare

npm i https://pkg.pr.new/miniflare@13029

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@13029

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@13029

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@13029

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@13029

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@13029

wrangler

npm i https://pkg.pr.new/wrangler@13029

commit: 0603693

…oken overrides

The initial neutral palette used pure black surfaces with no visual
layering. This replaces them with a stepped grey scale that preserves
the depth hierarchy of the original design.

Also adds explicit Kumo dark mode token overrides. Kumo's theme uses
light-dark() which requires color-scheme: dark (activated via
data-mode="dark"), but this app uses prefers-color-scheme media
queries instead. Without these overrides, Kumo components (Table
headers, text) render with their light-mode values in dark mode.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

2 participants