The Archive
A curated, searchable corpus of live website references—not downloadable templates.
- 304 public records
- Industry/category browsing
- Full-page captures and source links
A searchable design archive, a source-aware intelligence layer, and a browser-native color workshop—mapped from homepage to record provenance, from HEX lookup to production CSS.
The public experience is designed as a loop: discover strong work, understand the decisions underneath it, then use those same concepts to make something of your own.
A curated, searchable corpus of live website references—not downloadable templates.
A private extraction and governance engine turns each site into a structured comparison record.
Free, no-signup tools translate the archive’s color language into practical design work.
Filter by intent or search this section. Every route below was opened and inspected directly.
The orientation layer: a global archive search, headline public counts, live-tool shortcuts, popular categories, recently studied sites, and the contribution doorway.
The core discovery surface. Search queries match names and embedded record attributes—including technology terms such as “Webflow”—while category pills narrow the 304-card collection.
Each reference becomes a study page with source link, screenshot, summary, style, palette, typography, inferred stack, classification confidence, captured pages, contact signals and provenance.
Industry-led browsing with counts, percentages, descriptions and trending lanes. Individual category pages gather matching records and state that automated labels may need review.
A transparent catalogue snapshot: category composition across 304 cleaned, deduplicated records plus methodology, caveats, and direct routes back into the evidence.
Three editorial directions are previewed—display typography, near-black/off-white dominance, and what framework choice says about a team. The page currently says the first pieces are landing soon.
A six-job sequence—find, transform, build, preview, interpolate and test. Five are live; Palette Checker is announced as an upcoming role-and-contrast tester.
Users can nominate sites, report bad data, ask questions, or open press/partnership conversations. Both forms compose an email to hello@allwebsites.design rather than posting to an account system.
About, Manifesto and Editorial Guidelines explain selection, governed taxonomy, source authority, honest unknowns and correction priority. Privacy and cookie pages expose collection and consent choices.
The public page is not a scraped row. It is an assembled comparison object whose claims are separated from inference and whose provenance remains visible.
Select a tool to see its job, controls, outputs and honest limitations. The illustrations below are explanatory, not embedded versions of the tools.
A source-aware color dictionary and perceptual matcher.
Nearby matching converts colors to Oklab and ranks them with ΔEOK rather than raw RGB distance.
A deterministic, exact-angle HSL transformer for the moment after a base color is chosen.
A role-based website color-system completer that protects the colors you already chose.
A controlled interface test: the layout stays fixed while the four-color system changes.
An OKLCH gradient builder and side-by-side interpolation laboratory.
in oklch CSS.The announced sixth job: role and contrast testing.
The tools index labels this instrument “Soon” and “In progress.” No public control surface is available yet.
It closes the workflow after interpolation by validating whether a color system survives semantic roles and contrast constraints.
Choose a scenario. Each route combines archive intelligence and practical tools into a repeatable workflow.
Use a sector, aesthetic and stack as comparison lenses, then take only the underlying decisions into your own work.
/archive · /c/archive/[slug]MockupalettesPreserve the identity; generate only the missing semantic roles; then judge the result at interface scale.
ChromaryColorhymeWebPaletteMockupalettesKeep the endpoints fixed, compare color-space journeys, choose the hue route, then export for modern and fallback browsers.
TrueGradientCompare mode4 routesCSS exportUse the catalogue as a bounded research sample—not as a claim about the entire web.
2026 Index/c/[slug]Record profilesThe public correction loop is part of the product, not a buried support channel.
/submit/contact/editorial-guidelinesThis section separates observed strengths from seams worth resolving. “Verify” items are questions raised by public behavior—not accusations about internal implementation.
The archive and tools share concepts—palette roles, typography, technology, evidence—so the suite feels like one system rather than a widget directory.
“Detected,” “likely,” “not detected” and “unknown” are treated as real product states. The official source remains authoritative.
Record ID, status, completeness and extractor version make the archive inspectable and correctable.
Sampled core pages had one H1, a main landmark, named controls and complete image alt text. The archive had 305 images with no missing alt attributes.
Next.js rendering, canonical URLs, Open Graph images and JSON-LD (Organization, WebSite, CollectionPage, ItemList, WebApplication and FAQPage) support discovery.
The archive exposes all 304 cards but uses Next image delivery; 303 of 305 images were marked lazy and all 305 used async decoding.
Homepage, footer and research index say 25 categories; the category atlas says 44 and includes several zero-count legacy/expansion lanes. Label “25 populated / 44 in taxonomy” or consolidate.
The archive page says the loaded set is 304 while a full 5,896-record production dataset connects behind it. Explain whether this is private corpus, future catalogue or environment-specific copy.
Chromary currently links to /tools/palette-fixer, /tools/website-palette-checker and /tools/true-gradient. The live destinations use newer names/slugs.
mailto:not foundAt least one sampled record turns an absent email value into an active mail link. Render plain “Not detected” when no valid address exists.
Core archive pages expose a skip link and primary navigation; sampled standalone tool shells generally do not. Carry the same accessibility affordances across the suite.
The cookie page says ad tracking is not run today, yet the homepage DOM includes Google AdSense scripts before a choice was made. Script presence does not prove tracking; confirm gating and update wording if needed.
Lazy images soften network cost, but the full archive still renders a large card tree. Pagination, incremental rendering or virtualisation may matter as the public corpus grows.
The editorial topics are strong acquisition and authority material. Publishing them would complete the archive → research → education loop.
Use this as a compact operator’s map. “Local” means the tool says processing happens in the browser without signup.
| Surface | Primary job | User input | Output | State |
|---|---|---|---|---|
/archive | Discover references | Text query + category | Matching website cards | Live |
/archive/[slug] | Study a website | Record selection | Design, stack and provenance profile | Live |
/c | Compare industries | Category choice | Counts, share and records | Live |
/research/… | Understand the corpus | Reading / link navigation | Composition + methodology | Live |
/tools/chromary | Find color | Name or HEX | Values, source and nearby names | Live · local |
/tools/colorhyme | Transform color | HEX + hue/sat/light settings | 4 colors + reproducible recipe | Live · local |
/tools/webpalette | Build a color system | 1+ protected colors | 5 roles, readiness, preview, CSS | Live · local |
/tools/mockupalettes | Preview a palette | 4 colors / 38 presets | Responsive fixed-layout preview | Live · local |
/tools/truegradient | Interpolate a gradient | Stops, angle, hue route | Native OKLCH + HEX fallback CSS | Live · local |
| Palette Checker | Test roles and contrast | Not public yet | Not public yet | Announced |
/submit | Nominate a site | URL, email, rationale | Composed email to editorial | Live |
/contact | Correct or enquire | Name, email, reason, message | Composed email to editorial | Live |
The website is a living product. Counts, routes and capabilities reflect the public site inspected on 31 August 2026.
This is a product and user-experience teardown based on public interfaces and client-visible behavior. It does not claim access to the private extraction engine, private datasets, server logs, analytics results or internal roadmap.
Observed inconsistencies are framed as verification or repair opportunities. They may reflect ongoing migration, unpublished data, or deployment differences.