Docs

One install equals one artist. The site shows every series and work with the on-chain record behind it, and keeps the CV, exhibitions, press and the rest of the practice around the work.

Catalogue data is files under src/fixtures, not a required database. Wallet sign-in, collectors, insights and a shop are optional modules — off until you configure them. When something is missing, pages name the variable. They do not invent a number or fail quietly.

Needs Node 20+ and pnpm. Production-shaped: pnpm build && pnpm start. Checks: pnpm exec tsc --noEmit and pnpm lint.

A full walkthrough of standing up your own Raisonne. Each chapter is its own clip so you can skip to the step you need. Draft voice for now; the picture is the real screens and terminal frames.

Groups: Catalogue (works, installations, physical works, exhibitions, collaborations, awards, writings), Artist (about, CV, press), and More (commissions, insights, shop) when those modules have something to show.

The same links sit in the footer. On long index pages the footer hides behind a bottom bar so a grid is not interrupted. The CV has no site footer — it is a document meant to print cleanly.

Landing blocks are optional in the data: hero, showreel, stats, featured work, catalogue strip, partners, news, newsletter. Empty blocks are simply omitted — a fresh install is not forced to fill every slot.

Three kinds in the type system: series (a contract the artist deployed), one-of-one (a single-work contract), and shared-platform (the artist’s tokens on a marketplace contract many people use). Filters on /works use chain and kind from that data.

A series can be hidden: it stays out of the public index, sitemap and catalogue API while remaining in the fixture for the artist. Sub-series nest under a parent via parentSlug when the record says so — the parent page lists children first.

Identity is chain:contract:tokenId in the catalogue API; the human URL is series slug plus a token segment. Media can be still, video, or interactive HTML — live HTML is off by default in settings and sandboxed when on.

Traits, categories, file facts and marketplace links come from the fixture. Holder names on the work page stay off unless settings.showOwners is on — collectors’ privacy is the default. A work can be featured, one-of-one, or hidden the same way a series can.

Raisonne does not ask visitors to trust a spreadsheet. Series pages and import review show the signals that tied a contract to the artist:

During import, contracts that look unrelated are labelled clearly (including “probably not yours”) so the artist can leave them out of the catalogue with the reason still in view.

In development the workbench tools are on. In production set RAISONNE_TOOLS=1 for both build and start to serve /import (and the design system). Routes that are off answer 404. Setting this on a public host publishes the workbench URLs to anyone who types them — switch it off when the work is done. The public docs at /docs do not need this flag.

Only an owner session can open the importer. Configure RAISONNE_OWNER_ADDRESSES and RAISONNE_SESSION_SECRET, then sign in from the account menu. Everyone else sees a lock screen that says so. Docs and design-system share the tools flag but do not require an owner session.

Series review is the decision surface. Evidence badges (deployer, ownership log, owner, token-creator, storefront decode, minted-to) explain each attribution. Contracts that are not yours stay visible so you can reject them with context, not hide them.

Today the page replays a recorded run (demo demo-import.ndjson or your local/import-events.ndjson) at original timing through /import/replay, so the UI matches a live stream. The reducer and components do not change when a live source is wired in — only the event feed does.

src/fixtures/index.ts is the only reader. Pages call getSiteData(). Components take domain types from src/lib/types.ts, never raw CMS shapes. Edit a file and the next request reloads it when the mtime changes.

next/image only loads hosts discovered from the fixtures at startup, plus optional RAISONNE_IMAGE_HOSTS. Restart after changing hosts. Public IPFS gateways and marketplace CDNs make this install an open image proxy for those hosts — fine on a private install; pin and self-host if that matters on yours.

SIWE (EIP-4361) with viem. No email, no password, no third-party auth service. The server issues a nonce, verifies the message, and sets an httpOnly signed cookie. Smart-contract wallets need ALCHEMY_API_KEY for ERC-1271 / ERC-6492; without it only key-pair wallets work, and the page says so.

A collector is an address. Nothing about a person is stored: no name, no email, no profile database. Holdings are read from the chain (cached a few minutes) with a re-sync control. Leaderboard and insights come from local/chain.json, never by replaying every transfer on page load.

Module insights. Pages under /insights summarise what the chain snapshot says about the work: activity, collections, sales stats when prices are known, and gaps when history was truncated or a sale price could not be read. Missing Alchemy or snapshot → designed panel with the command to run, not a blank chart.

Module store. Cart in local storage holds slugs, variant ids and quantities only. Every price a visitor sees and every amount Stripe charges is computed on the server from fixtures. Orders default to JSON files under .data/orders (persist across deploys). Print-on-demand provider dispatch is a stub in this release — flow and pages exist; the provider call does not.

Commissions module exposes /commissions and a request form when configured. Drops announce releases with phases, countdown, notify dialog and calendar — data-driven from the fixture, linked from series when seriesSlug is set.

In settings.modules inside the site data. Off modules drop out of nav, sitemap and the catalogue API. Known ids:

Related settings (not modules): liveHtml, showOwners, publicCollectorProfiles, analytics, maintenance, allowAiCrawlers, redirects, legal.

Full list lives in .env.example. Nothing is required for the bare catalogue. Copy to .env.local (gitignored). Never put secrets in fixtures.

GET and HEAD only. Domain shapes the pages already render. Anything that sounds like personal data (collector, customer, order, commission, credential) answers 404 whether or not this install has the type. Off modules contribute no records. Also published: /sitemap.xml, /robots.txt, /manifest.webmanifest, Open Graph image routes.

Data refresh is pnpm snapshot / pnpm snapshot:chain. Code refresh is /update or:

Apply needs a clean git checkout of the upstream repo (or RAISONNE_UPDATE_REPO), owner session on the web path, and RAISONNE_UPDATE=1 in production. Never touches src/fixtures/local/, .data/, or .env*. Restart after apply — the running Node process does not hot-reload.

Agents installing or extending the app: read CLAUDE.md and AGENTS.md in the repo root. Security reports: SECURITY.md.