5 solution docs
Payload blog solution docs
A full CMS in your own repo and database. No second service, no content API bill.
Pick Payload blog and all 5 land in docs/solutions/blog-payload/, next to the rules and skills that reference them.
Every Payload blog doc in the registry
Tags: access-control · app-router · architecture · auth · cms · deployment · drizzle · migrations · nextjs · payload · postgres · prisma · roles · s3 · schema · security · serverless · storage · uploads · vercel
Payload access control when your app already has auth
Two user tables is the right answer. Map your app's roles onto Payload's rules instead of merging the tables, and never leave an access block undeclared.
payload · access-control · auth · roles
Payload uploads vanish after a deploy: move media to an object store
staticDir writes to a filesystem that disappears on serverless. Add a storage adapter, keep the database rows, and migrate the files you already have.
payload · uploads · storage · s3
Payload migrations on Vercel without a broken deploy
Vercel runs your build, not your migrations. Run them in the build command, forward-only, and split the schema deploy from the code that needs it.
payload · vercel · migrations · deployment
Running Payload inside the same Next.js app
The admin panel is a route group, not a second service. Route groups, withPayload, the import map and why your blog pages must not fetch their own API.
payload · nextjs · app-router · cms
Letting Payload share your Postgres without wrecking your migrations
Two migration tools in one database will fight over table names and drop each other's tables. A separate schema keeps them apart for one config line.
payload · postgres · migrations · drizzle