Skip to content

Changelog

What changed, and why.

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

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

0.8.0

Latest111

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.