plugin onboarding · palette case studies · 2026-08-24

Six palettes, one screen

Two things were wrong with the last round. #FBF1DF was still cream — caught, and it was a plugin's amber tint rather than ours, which is worse because it is indistinguishable at a glance. And the reason everything looked creamy: the artifact page itself was on #FDFAF8. Neutral white panels read warm against a warm ground, so none of those four options was actually assessable. This page is on #F4F4F5 for that reason.

One screen — the consent step, the most copy-heavy and brand-sensitive in the flow — drawn six times. Same markup, same structure, same words. Only the token block changes, so colour is the only variable. Candidate A is your suggestion: the literal midpoint of our indigo and core's blue.

no cream anywhere, including the page core button + controls untouched in all six constant: mono label · 1.5px ink rule · hairlines · 4px
the six

Judged against core's own grey

Each carries the letterhead band from the previous round, since that is the recommended device and holding it constant is what makes the palettes comparable.

a · bridge — your idea, computed
#6359D6 → #4265C4 ← #2271b1 · tint #EEF1FA

SearchSync

SearchSync setupstep 2 / 4
02

Two optional things

Two questions, and no is a complete answer to both.

Send us diagnostics?

The whole payload, as it stands on this site:

siteoakhill-learning.com
php8.2.14
wordpress6.8.1
answer both to continue

A blue-violet that is adjacent to core rather than fighting it. The band tint sits a hair cooler than the admin grey, which reads as intentional. Genuinely the safest of the six. The honest risk: at 20% opacity in a band, a colour 30° from core's blue may just read as core's blue — you get nativeness by becoming slightly invisible.

b · graphite — no hue at all
accent = ink · #18181B / #2A2A2E · tint #F1F1F2

SearchSync

SearchSync setupstep 2 / 4
02

Two optional things

Two questions, and no is a complete answer to both.

Send us diagnostics?

The whole payload, as it stands on this site:

siteoakhill-learning.com
php8.2.14
wordpress6.8.1
answer both to continue

Every accent role played by the ink. The only colour on screen is core's own blue button — which makes the button unmissable, and is arguably the correct hierarchy for a screen whose job is answer these and move on. Reads as a well-made tool rather than a branded one. Whether that is discipline or surrender is the actual question, and I do not think it is obvious.

c · slate & salmon — the unspent colour
logo salmon #FD9597 · text-safe #C4494C · slate #525A66

SearchSync

SearchSync setupstep 2 / 4
02

Two optional things

Two questions, and no is a complete answer to both.

Send us diagnostics?

The whole payload, as it stands on this site:

siteoakhill-learning.com
php8.2.14
wordpress6.8.1
answer both to continue

The most distinctive of the six, and the only one nobody would mistake for another plugin. Salmon is our most recognisable colour and it has never carried a surface — the mark keeps the true #FD9597, text drops to #C4494C for contrast. The problem is unavoidable: red-family in wp-admin means error. A rose band above a form may read as a warning for the first half-second, every time.

d · olive & bone — earthy, cool neutral
olive #507F06 · bone #F7F7F5 (cool, not cream)

SearchSync

SearchSync setupstep 2 / 4
02

Two optional things

Two questions, and no is a complete answer to both.

Send us diagnostics?

The whole payload, as it stands on this site:

siteoakhill-learning.com
php8.2.14
wordpress6.8.1
answer both to continue

Warm feeling without a warm ground — the bone neutral is cooler than cream and does not fight #f0f0f1. Olive is in the brand set and has never carried a surface. Same learned-meaning problem as salmon but milder: green in wp-admin says success or update available, so the band may read as a status strip rather than a letterhead.

e · one hue — indigo all the way down
every neutral derived from #5B51C9 · ink #1C1A24

SearchSync

SearchSync setupstep 2 / 4
02

Two optional things

Two questions, and no is a complete answer to both.

Send us diagnostics?

The whole payload, as it stands on this site:

siteoakhill-learning.com
php8.2.14
wordpress6.8.1
answer both to continue

Keeps our actual brand colour and gets rid of cream by making every neutral a desaturated indigo — the lines, the strip, even the ink. The screen becomes one hue family, which is cohesive in a way none of the others are. Two costs: indigo is the colour already spent on the DDD viewer, and violet-tinted greys next to core's pure greys can look faintly off rather than deliberate on a cheap panel.

f · ink band — echo the admin bar
band = WP's own #1D2327 · one small accent #4265C4

SearchSync

SearchSync setupstep 2 / 4
02

Two optional things

Two questions, and no is a complete answer to both.

Send us diagnostics?

The whole payload, as it stands on this site:

siteoakhill-learning.com
php8.2.14
wordpress6.8.1
answer both to continue

The band goes to WP's own #1D2327 — the admin bar and menu colour — so it borrows the one dark surface the environment already has instead of introducing a new colour. Ties the panel to the chrome vertically, and the accent mark is the only colour anywhere. Cost: a dark band inside a light panel is heavy, and it competes with the menu for the eye's first stop.

reading the six

What the comparison actually shows

The learned-meaning problem is the real finding, and it eliminates two. wp-admin has trained every admin for a decade: green is success, red is error, amber is warning, blue is a link. That leaves the brand palette almost nowhere to stand — olive reads status and salmon reads error, both for the first half-second, every time, on a screen that is neither. Those are not aesthetic objections and they do not go away with better craft. Blue-violet and achromatic are the only two families wp-admin has no prior meaning for — which is exactly why A, B, E and F are the four that survive, and it is not a coincidence that they are the four with the least colour.

Ranked, with the reasoning rather than the taste:

1 · F, ink band. Best answer to "Tangible-ish but at home", because it solves the problem by borrowing: the dark band already exists in the environment, so it cannot look foreign, and one small accent mark is enough to be ours. It also happens to be the strongest per-plugin theming host of all six — the plugin's colour is the mark, on a constant dark ground, so no plugin colour can wreck the band.

2 · A, bridge. Your idea, and the safest. I rank it second only because its safety is bought by being nearly indistinguishable from core at band opacity — which is a real cost if the goal includes identifiable.

3 · B, graphite. Underrated. It gives the blue button the only colour on screen, which is the correct hierarchy for a step whose job is answer-and-move-on. The best fallback if any band at all proves to be one gesture too many.

4 · E, one hue — cohesive, but indigo is spent on DDDash and violet-greys read as slightly-wrong rather than deliberate on a bad panel. 5 · D and 6 · C — killed by learned meaning, not by looks.

A combination worth drawing next, if you want one: F's ink band as the constant frame, with A's #4265C4 as the Tangible accent on core steps and the plugin's own colour as the mark on its steps. That keeps the band's "whose step is this" idea from the previous round while removing the risk that a plugin's brand colour has to work as a full-width tint.

Still open, and it is the question underneath all six: does Tangible-in-wp-admin get to be warm at all? D is the only candidate that even tries, and it tries by swapping the ground for a cool bone and buying warmth back through the accent. If the answer is no, then the brand's presence here is entirely typographic — the mono label, the ink rule, the copy voice — and the palette question is smaller than it looks.

Painted 4:46 PM EST all artifacts