How these are made
Every page in Dossier is generated from a single JSON record per artist. The record holds what the artist confirmed — bio, images, links, releases, dates, contact — and nothing else. There is no editorial voice layer, no auto-written biography, and no scraped copy.
One grammar, six profiles
Six design profiles carry the visual system. A profile fixes the grid, the type treatment, the density and the way rules are drawn; it does not fix the colour. Colour comes from the artist's own artwork.
Grid / Brutalist
Hard grid, oversized condensed type, no ornament. Built for pressure.
0 in useEditorial / Mono
Margins, hairline rules, mono captions holding a long-form bio.
0 in useIndustrial / Dither
Noise fields, cut type, high contrast. Signal in a dirty room.
0 in useLabel / Minimal
Sparse, numeric index, small caps. Catalogue as architecture.
0 in useAmbient / Airy
Wide leading, soft fields, slow motion. Room to breathe.
0 in useSignal / Hardcore
Loud accents, stacked slabs, a ticker that will not sit still.
0 in useWhat varies, and what does not
Within a profile, exactly four things change per artist: the palette roles, the grain seed, the hero crop, and the motion cadence. Everything else is locked. That constraint is the whole idea — 150 pages that each look like themselves while still reading as one archive.
The palette is extracted from the artwork at build time by clustering its colours, then scoring clusters on chroma and mid-tone weight. A near-black sleeve with one acid highlight yields an acid accent; a monochrome sleeve yields a neutral and the page says so. Colours are then clamped and checked: no page ships with body text below 7:1 contrast, or accent text below 4.5:1. If a pinned palette would break that, the build fails rather than publishing something unreadable.
Deterministic by construction
The same record and the same artwork always produce the same page. Nothing is randomised at render time, so a rebuild on a Tuesday cannot silently reshuffle an artist's design. Seed values are derived from the slug; extracted tokens are computed from image bytes. A determinism check runs in CI: build twice, diff the output, expect nothing.
Three clocks
Nightly — public metadata is refreshed into a review queue, and every outbound link is checked. Nothing lands on a live page without a human accepting it.Weekly — accepted changes build and deploy once, and the update feed gets a new entry. Quarterly — each record's edition increments, and the changelog on the page shows what moved.
The edition stamp matters more than it looks. A booker who saved a link in September can see that the page is at 2026.Q4.2 and what changed, instead of wondering whether anything is current.
Rights, and what we refuse to do
We do not scrape. Bandcamp's policy forbids it, Resident Advisor requires a written agreement for automated extraction, and SoundCloud's API terms prohibit building pages dedicated to specific artists — which is precisely what a roster is. Spotify's developer policy restricts apps whose sole subject is named artists, and its preview URLs are deprecated anyway.
So playback happens on the artist's own platform, through that platform's official player. Nothing is downloaded, rehosted or proxied. Every image carries a credit, a source and a permission basis in the record; the build refuses to publish an asset missing any of the three. “For press use” is not treated as a licence for a permanent public archive — the artist is asked to confirm the specific use.
Credit is not permission. Both are required here.
What happens when something is wrong
A record can be withdrawn with one flag. The page disappears at the next build and the URL redirects to the roster; the artist is not argued with. SeeRemoval & corrections.
What this is not
Not a booking agency, not a marketplace, not a paywall, and not a claim of representation. It is an archive that tries to make the artists in it easier to book, write about and pay.