Skip to content

Changelog

What changed, and why.

Written by hand, not generated from commits — a claim about what changed for you.

Latest
0.10.0
Shipped
Releases
7
AddedSomething new you can go and use.
ImprovedSomething that already existed, made better.
FixedSomething that was wrong, and no longer is.

0.10.0

Latest422

A palette that follows you from tool to tool, exports that can be written in OKLCH, and Pro billed by the year

In plain wordsThe colours you're working on now travel with you between the tools instead of being pasted in again — and the image tools open on a real photo, with a stock search built in.

  • Added

    Your palette travels with you between tools

    Every hand-off between tools — the links at the foot of a tool page, the generator's tools menu, the Palette Doctor's fixes — now carries the colours you're holding, and only to the tools that can read them, so a link never appends something the next page quietly ignores. The colours are read at the moment you click rather than when the page loaded, so a swatch you changed a second earlier is the one that arrives.

  • Improved

    The contrast checker opens on the pair that failed

    Sent there by a finding in the Palette Doctor, it now lands on the two colours that finding is about. It used to open on the darkest-over-lightest pair of whatever palette it was handed, which is the pairing least likely to be the one that just failed — so the first thing you saw was a pass, for a pair nobody had asked about.

  • Added

    Exports can be written in OKLCH

    CSS, SCSS, Tailwind v4 and design tokens can now come out as lightness, chroma and hue instead of a hex code, so a hover state or a dark-mode step reads as the same token with the lightness moved rather than another opaque number nobody can relate to the first. The CSS export ships a hex line above each one for older browsers, and the switch only appears on the formats it actually changes. There's a new guide under Resources on when it's worth it and when hex is still the right answer.

  • Added

    Pro can be billed yearly

    $3 a month, billed as $36 once a year, beside the $5 monthly plan — the annual figure always stated in the same breath as the monthly one, because a monthly number that quietly bills a year is a dark pattern. Your account page says which one you're on and reads the amount back off your own subscription, so anyone who subscribed at an older price still sees what they actually pay rather than today's list price.

  • Added

    Stock photos in every tool that takes an image

    The photo picker, the image editor and the collage tool now share one way in: upload a file, paste a URL, or search a stock library without leaving the page. The photographer is credited on anything you pick.

  • Improved

    The image tools open on a photograph, not an empty box

    The photo picker and the editor now start on a real sample image, clearly marked as a sample, with 'use your own image' as the main button. The picker's one interaction — dragging a sample point onto the colour you want — is invisible until there is an image to drag it across.

  • Fixed

    Stock search returned the same photo for every term

    On the live site only, and for an unpleasant reason: the layer in front of the site was caching image searches without looking at what had been searched for, so whichever request arrived first was served to everyone after it. Every term returned one result, the URL tab returned somebody else's picture, and all of it worked perfectly on a developer's machine, where nothing sits in front of it. Paging through results no longer repeats images either.

  • Fixed

    Links to the site show the right preview image

    Sharing a page into a chat or a social post produced a broken or missing preview card. It now renders one for the page being shared.

0.9.0

43

Every use case now shows the tool actually running, the blog folded into the guides, and the site has real privacy, cookie and contact pages

In plain wordsThe page that explains what each tool is for now plays a small animation of it working — and you can now switch analytics and ads off, and get in touch.

  • Added

    Every use case plays a miniature of the tool

    Beside each card, a scripted run-through of the job it describes: the palette being diagnosed, the stylesheet being scanned, the scale being built. The written steps and the animation are tied together — the rail lights the step being played and ticks off the ones behind it, so you can tell which sentence you're watching. Every number, colour and line of code in them is produced by the same code the real tool runs, so a miniature can't claim something the tool doesn't do.

  • Improved

    The finder is organised by stage, not by who you are

    It used to ask whether you were a developer, a designer or neither, and filter on the answer. It now follows the same four stages as everything else — generate, understand, validate, ship — because the honest answer to 'is this page talking to me' is 'which of these are you trying to do', and every tool works for everyone regardless.

  • Added

    Cookie controls that switch things off

    'Manage cookies' in the footer is a real preference, not a description of one: turning analytics or ads off stops the scripts loading, on the page you're standing on, in the same moment you flip the switch. The sign-in cookie isn't offered as a choice, because a switch that signs you out isn't a preference.

  • Added

    Privacy policy, terms, licence and a contact page

    Including what you may do with a palette you exported, which is the question a designer on a client project actually has and the one most colour tools leave to guesswork.

  • Added

    Password reset by email

    Forgotten-password links that expire and work once. The page deliberately gives the same answer whether or not an account exists at that address — a reset form that says 'no such account' is an account-checker for anyone who wants one.

  • Improved

    The blog is now part of the guides

    Two places to read the same kind of writing was one too many. The colour-debt post moved in alongside the methodology pages, so there is one shelf rather than two half-empty ones.

  • Improved

    A pass over type sizes, spacing and tap targets

    Buttons across the site come from one component instead of a dozen near-identical ones, touch targets are large enough to hit on a phone, line heights and heading sizes follow one scale, and the shadows are gone from the places that were using them to compensate. A colour tool that fails the checks it hands out is not in a strong position.

0.8.0

111

The footer signs the page off with the brand mark's own shear, and every guide, post and release now carries a breadcrumb trail

In plain wordsThe big name at the bottom of the home page is new, and it now says where it takes you. The guides, blog and this page will also tell you where you are.

  • Improved

    The footer wordmark is the logo, at page scale

    The mark is one circle cut in half with the halves slid apart, and the name at the foot of the home page is now built the same way: two copies of it, the light one leading, the brand one slid down and to the right across the full width of the page, widening as you move onto it. It's the same idea the logo states in 20 pixels, said once at the size of the page — rather than a gradient banner, which every other product's marketing page already ends on.

  • Fixed

    The footer wordmark says that it's a link

    It goes home, and it always did, but at that size it reads as a graphic rather than a control — so nobody found out unless they happened to hover it, and on a phone there is no hovering. There's now a standing 'Back to home' label above it that lights up along with the word, instead of a cue you had to already be touching to see.

  • Added

    Breadcrumbs on the guides, the blog, this page and the use-case finder

    These four are the pages most likely to be the first one you land on from a search, and they were the ones with no trail back into the site. Each now shows where it sits and publishes the same trail to search engines, so results can show the path rather than a bare address. The visible trail and the machine-readable one are generated from a single list, because two copies kept by hand disagree eventually — and a mismatched one gets ignored outright.

0.7.0

23

A home page that deals its proof one card at a time, a changelog you can read without being a developer, and a use-case finder

In plain wordsThe front page now walks you through what the tools do instead of asking you to scroll past five blocks of it — and this page you're reading is new.

  • Added

    This changelog

    Every release written twice — once in product terms and once with no product vocabulary in it — and each entry labelled as something new to try, something that got better, or something that was wrong and no longer is. The labels carry an icon and a rail rather than only a colour, because a colour-accessibility product that codes meaning in hue alone has no argument left.

  • Added

    A use-case finder

    Every tool as a job to be done: the situation you're in, what you walk away holding, and the three steps in between — filtered by whether you arrived as a developer, a designer, or someone who just wants better colours. Each card runs the full width of the page, so the steps read as steps.

  • Improved

    The home page reads as one argument, not five bands

    Colour systems, colour debt, the inspector, contrast and export now stack as a deck — each one sticks while the next scrolls up over it, so the sequence reads as a sequence. A section taller than your screen scrolls all the way through before it pins, so nothing is ever parked out of reach, and below tablet width the effect turns off entirely rather than becoming a very long scroll.

  • Improved

    The tool directory is called what it is

    It's 'The toolkit' now — it used to share a heading with the section directly beneath it, which read as a bug. It also promises 'free to start' rather than free outright: every tool opens and does its job without paying, but the repair tools, semantic tokens, the audit report and PDF export are Pro, and a page that says otherwise costs more trust than the word buys.

  • Improved

    The image tools moved after export

    Everything above them takes a colour as input and they take a file, so they now get their own beat once the main argument has landed instead of interrupting it.

0.6.0

24

Theme Predictor, a home page rebuilt around the four pillars, and a navigation you can find things in

In plain wordsYou can now check that a set of colours works in dark mode as well as light — and the site itself got easier to move around.

  • Added

    Theme Predictor

    Point it at a palette and it tells you which theme the palette is actually built for — light or dark — then builds both so you can compare them side by side. It reuses the Palette Doctor's role logic, so the light and dark builds agree with the diagnosis rather than being a second opinion.

  • Added

    Use cases for every tool

    One page that says, for each of the seventeen tools, what job it does, what you end up holding, and the three steps to get there — filterable by whether you arrived as a developer, a designer, or someone who just wants better colours.

  • Improved

    The navigation names four pillars, not six categories

    Generate, Understand, Validate, Ship. The menu, the landing page, the pricing page and the guides now use the same four words in the same order, so the nav no longer teaches one story and the page it opens teaches another. Resources opens as a small panel under its own trigger instead of a full-width sheet.

  • Improved

    A home page that shows the tools instead of describing them

    The hero leads with a live palette rather than a claim, and the tool directory below it is grouped by pillar with a working preview in each card. Image tools sit in their own strip — their input is a file, not a colour, and pretending otherwise made them hard to find.

  • Improved

    The Palette Doctor reads as a report, not a form

    Findings lead with the consequence — 'tiring for older readers' — and keep the ratio one click away for anyone who wants it. The repair panels are laid out in the order you'd act on them.

  • Improved

    Pricing leads with what Pro is actually for

    Semantic tokens and the audit report, rather than a saved-palette limit. A cap on saved palettes describes a restriction; tokens and an audit describe the work you get done.

0.5.0

321

Resources, a colour-debt engine, and the navigation rebuilt around the five pillars

In plain wordsWe published how the scoring works, and added a tool that finds colours you're keeping twice by accident.

  • Added

    Resources — five guides, including the full methodology

    The Proof Score methodology is published with its weights and thresholds read live out of the rule engine, so the page cannot quietly drift away from the code it describes. If the number is wrong, you can now check it by hand.

  • Added

    A colour-debt engine

    Reports duplicate and near-identical colours across a set of stylesheets, with file and line numbers, and is ready to run in CI. Every colour in a stylesheet is a value somebody has to keep in sync forever; this tells you which ones are earning that cost.

  • Added

    This changelog, and a blog

    Written by hand rather than generated from commits, so each line is a claim about what changed for you.

  • Improved

    The Improve tools are reachable from the menu

    Auto Fix, merge duplicates, compression and semantic tokens were buried inside the Palette Doctor. A visitor could use the site for a month without discovering the features they'd have paid for.

  • Improved

    Pricing leads with tokens and the audit report

    Rather than saved-palette limits, which describe a restriction instead of a result.

  • Fixed

    Pro subscribers no longer see ads

    The plan check was missing entirely, so "no ads" was a promise nothing enforced.

0.4.0

3

Dark palettes are read correctly, and the colour ramps stop reversing at the extremes

In plain wordsThree maths bugs that made dark palettes and near-black or near-white colours come out wrong.

  • Fixed

    A dark theme is no longer read as a light one

    Any near-white in a palette was treated as "that's obviously the page" — but a dark theme ships a near-white as its body text, so the single most common dark palette was misread, and misread confidently. Everything downstream took its roles from that call, so tokens, compression and the audit were all wrong on dark palettes.

  • Fixed

    Shades of black came out lighter than black

    And tints of white came out darker than white — the ramp reversed direction at both extremes.

  • Fixed

    The sRGB primaries stopped coming back duller

    The six primaries were being gamut-mapped when they did not need to be. Pure green lost 49 of its 255.