Mockups for the proposed system. Primary actions go neutral and theme-inverting (the portal login direction), red stays as glow, logo, and links, and destruction gets its own crimson. Values come from the cross-repo audit; the neutrals carry a faint red cast so the UI stays Herd even without red fills.
Same card, one change. White on #F61500 is 4.2:1 and fails WCAG AA; the inverting CTA is ~16:1 in both modes. The red survives as the "Forgot?" link, the footer link, and the logo.
4.2:1 — fails AA. Reads as a warning.
16:1. Visible oxblood #3E100C, red only as accent.
Saturated red vibrates on dark surfaces.
16:1. Blush white #F6EEEB on #161314; hover ignites to pure white.
Three roles, three shapes. Destructive actions rest as an outline and only turn solid crimson (#E5484D) on the confirm step — never the brand red, so "Remove site" and "Upgrade to Pro" can't be confused again.
Red illuminates instead of filling: the logo glows, links and small accents stay red, and focus is a warm glow — not a red border, which reads as a validation error. Upsell moments (the macOS onboarding/Pro flows) keep the brand via the glow while the CTA goes neutral.
Dumps, mail testing, log viewer, and the dump server — built in.
Dumps, mail testing, log viewer, and the dump server — built in.
Today the widget spends three different reds (#F61500, #DC2626, #EF4444) on four jobs: Send, active tab, focus ring, and the error state. Proposed: Send goes neutral, the active tab uses ink, the logo keeps the red — and Stop/delete standardize on the crimson the widget already uses for destruction.
Red tab, red Send, red focus, red errors — one hue, four meanings.
Brand lives in the glowing logo; Stop-while-generating becomes #E5484D.
Today the primary CTA (#F8332B) and the delete button (#DC2626) render side by side as two nearly identical reds. The Pro badge stays red in the proposal — small, branding, no action attached.
Spot the destructive one.
Action and destruction can't be confused; the crimson goes solid only on confirm.
Day-to-day chrome already follows the user's system accent — deliberately — so red-as-CTA only shows up in onboarding, What's New, and the Pro/license flows. The proposal keeps the system-accent behavior untouched: the glow carries the brand, the button goes neutral, and toggles stay whatever the user picked.
PHP and nginx are ready. Let's set up your first site.
Red glow + red button + system-blue toggle: two accent systems in one window.
PHP and nginx are ready. Let's set up your first site.
Glow = brand, button = action, toggle = the user's accent. Each color has one job.
One red fill per marketing page. Promotional context, no delete buttons nearby — red reads as energy here, not danger. Inside the apps and portal: zero red fills.
PHP, nginx, dnsmasq and Node — installed and kept up to date for you. Native on macOS and Windows.
The decisions to make once, centrally. Five brand reds currently ship across the four repos — exactly one should win.