next-site development
yarn dc:up # Postgres + Mailpit (emails at http://localhost:8025)yarn dev # http://localhost:3000, admin at /adminThe first visit to /admin creates the owner’s account. Seed on the
dashboard fills a development database with demo content (and deletes what is
there); it is disabled in production.
Changing the content model
Section titled “Changing the content model”After changing a collection, global, field or block:
yarn generate:types # src/payload-types.tsyarn generate:importmap # after adding an admin componentBefore deploying a schema change, create a migration against a database with the previous schema and commit it:
yarn payload migrate:create add-eventsThe project’s skills cover the common changes: add-block, add-collection
and, with the shop, add-payment-provider.
Building with Claude Code
Section titled “Building with Claude Code”The project ships its own guidance, stripped to the features it has:
CLAUDE.mdat the root: commands, layout and rules (Payload owns the schema, migrations before deploy, access enforced in collections, pages rendered per request,NEXT_PUBLIC_*inlined at build time; with the shop, one currency andpaymentStatusas the record of money received).- Task skills in
.claude/skills/:add-block(a page-builder section),add-collection(a new kind of content in the admin) and, with the shop,add-payment-provider. Ask for the task in plain words.
See Building with Claude Code for the whole workflow.
Checks and tests
Section titled “Checks and tests”yarn typecheck && yarn lint && yarn format:check && yarn buildyarn test:int # integration tests against the Postgres in DATABASE_URL