We did a quiet but visible cleanup across FapIndex: every coloured badge, pill, hero gradient, and capability tag now belongs to one and only one meaning. The header on /best-ai-sites/ is purple, the header on /best-virtual-reality-sites/ is indigo, the header on /best-live-cams-sites/ is rose, and those colours are now used only for those sections. Before this week, the same purple was also a 4K capability tag, a payment biller accent, and a heading icon on VR scoring docs. It made the rest of the UI quietly confusing.
Why colours were drifting
FapIndex is built with a fairly large Tailwind palette. We had grown into using colour as a signal without writing the system down anywhere. The result was honest accident: AI sites live on a purple section, and someone reaching for “a nice highlight colour” for a 4K tag also picked purple. Three different reasons to use purple, no single meaning.
On a busy listing this added noise. Imagine a card on /best-ai-sites/ with a purple section header above it, a purple 4K pill, a violet member pill, and a violet payment icon. Four different things, four uses of the same wedge of the colour wheel, no hierarchy. The brain treats them as related when they are not.
One colour, one job: the seven layers
We sat down and gave every colour family exactly one job. Seven jobs, one palette per job:
- Section / domain (nav, hero, breadcrumb): purple for AI, rose for cams, indigo for VR, orange for the general top.
- Site type (the small label that says network, member, standalone): blue, teal, gray, plus red for warnings.
- Capability tags (4K, downloads, mobile): neutral gray. They describe; they do not categorise.
- Catalog state (fresh, stale, archive on the Scene Catalog Freshness plate): emerald, slate, amber.
- Brand actions (the score, the “Visit” button, Best Value): orange and only orange.
- Payment billers: their own isolated palette inside the PaymentIcons component.
- Score tiers on /how-we-score/: a dedicated traffic-light scheme (green Excellent, blue Good, yellow Average, red Poor, amber Outstanding).
Then we wrote a small audit script that reads every TSX file in the project, finds every Tailwind class with a colour family in it, and flags any usage that does not belong to the layer that owns that colour. The first run found 261 user-facing violations. After the cleanup, zero.
Eight places that actually changed
Most of the 261 hits were false positives once we expanded the registry to match real usage. Eight clusters were actual wrong-colour bugs:
- The “AI Platform” pill at the top of every AI review was violet. It is now purple, matching the AI section.
- The fallback hero gradient on AI reviews (visible when a site has no preview image) was violet to indigo. It is now a clean purple gradient.
- The same fallback gradient on cam reviews was also violet to indigo. It is now rose.
- The “Part of {network}” pill that appears on category-page hover was violet, which on an AI category page bled into the section colour. It is now teal, distinct from purple.
- The big “AI” heading icon on /how-we-score/ai/ was violet. Now purple.
- The “+5 VR Bonus” icon on /how-we-score/vr/ was purple. Purple is for AI. It is now indigo.
- The “VR NETWORK” overlay on hub cards in the VR shelf was purple. Same reason as above. Now indigo.
- The 4K tag in sortable lists was purple and the DL tag was blue. Both now sit in neutral gray with a soft border, because capability tags describe a site, they do not classify it.




What you will notice
Walk through the site and the sections feel cleaner. The nav pill at the top is the same colour you see on the corresponding shelf, scoring doc, and review hero. Capability tags fall to the back. The score, the visit button, and the Best Value pill keep their job as the only orange things on a card, which is what we wanted them to do all along.
Nothing else changed: no scores moved, no rankings shifted, no site got reclassified. This was purely about the colour signalling. The audit script now lives in the repo so the next time someone adds a new badge, a wrong-colour leak fails the build instead of quietly joining 200 other accidents.