chore(release): db-postgres/0.1.3

fix: #3521

.editorconfig

@@ -4,7 +4,7 @@ charset = utf-8
 trim_trailing_whitespace = true
 insert_final_newline = true
 
-[*.js]
+[*.{js,ts,tsx}]
 indent_style = space
 indent_size = 2
 
@@ -15,3 +15,11 @@ indent_size = 2
 [*.scss]
 indent_style = space
 indent_size = 2
+
+[*.mdx]
+indent_style = space
+indent_size = 2
+
+[*.json]
+indent_style = space
+indent_size = 2

.eslintignore

@@ -0,0 +1,10 @@
+.tmp
+**/.git
+**/.hg
+**/.pnp.*
+**/.svn
+**/.yarn/**
+**/build
+**/dist/**
+**/node_modules
+**/temp

.eslintrc.cjs

@@ -0,0 +1,38 @@
+module.exports = {
+  extends: ['@payloadcms'],
+  overrides: [
+    {
+      extends: ['plugin:@typescript-eslint/disable-type-checked'],
+      files: ['*.js', '*.cjs', '*.json', '*.md', '*.yml', '*.yaml'],
+    },
+    {
+      files: ['packages/eslint-config-payload/**'],
+      rules: {
+        'perfectionist/sort-objects': 'off',
+      },
+    },
+    {
+      files: ['package.json', 'tsconfig.json'],
+      rules: {
+        'perfectionist/sort-array-includes': 'off',
+        'perfectionist/sort-astro-attributes': 'off',
+        'perfectionist/sort-classes': 'off',
+        'perfectionist/sort-enums': 'off',
+        'perfectionist/sort-exports': 'off',
+        'perfectionist/sort-imports': 'off',
+        'perfectionist/sort-interfaces': 'off',
+        'perfectionist/sort-jsx-props': 'off',
+        'perfectionist/sort-keys': 'off',
+        'perfectionist/sort-maps': 'off',
+        'perfectionist/sort-named-exports': 'off',
+        'perfectionist/sort-named-imports': 'off',
+        'perfectionist/sort-object-types': 'off',
+        'perfectionist/sort-objects': 'off',
+        'perfectionist/sort-svelte-attributes': 'off',
+        'perfectionist/sort-union-types': 'off',
+        'perfectionist/sort-vue-attributes': 'off',
+      },
+    },
+  ],
+  root: true,
+}

.eslintrc.js

@@ -1,15 +0,0 @@
-module.exports = {
-  parser: "babel-eslint",
-  extends: "@trbl",
-  rules: {
-    "import/no-unresolved": [
-      2,
-      {
-        ignore: [
-          'payload/config',
-          'payload/unsanitizedConfig',
-        ]
-      }
-    ],
-  },
-};

.git-blame-ignore-revs

@@ -0,0 +1,12 @@
+# lint and format
+ae7d6f97d205491390f15850e5104c7abded1550
+1fbda85cd04a774cb978778b0f813001664c53dd
+
+# prettier all templates
+75a428ddc4672903455998eaba7ae9f9d710bf85
+
+# re-run prettier and eslint everywhere again
+cdaa0acd61d3001407609915bd573b78565d5571
+
+# prettier write again
+dfac7395fed95fc5d8ebca21b786ce70821942bb

.github/ISSUE_TEMPLATE/1.bug_report.yml

@@ -0,0 +1,47 @@
+name: Bug Report
+description: Create a bug report for Payload
+labels: ['possible-bug']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        *Note:* Feature requests should be opened as [discussions](https://github.com/payloadcms/payload/discussions/new?category=feature-requests-ideas).
+  - type: input
+    id: reproduction-link
+    attributes:
+      label: Link to reproduction
+      description: Please add a link to a reproduction. See the fork [reproduction-guide](https://github.com/payloadcms/payload/blob/main/.github/reproduction-guide.md) for more information.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: To Reproduce
+      description: Steps to reproduce the behavior, please provide a clear description of how to reproduce the issue, based on the linked minimal reproduction. Screenshots can be provided in the issue body below. If using code blocks, make sure that [syntax highlighting is correct](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#syntax-highlighting) and double check that the rendered preview is not broken.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the Bug
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Payload Version
+      description: What version of Payload are you running?
+    validations:
+      required: true
+  - type: input
+    id: adapters-plugins
+    attributes:
+      label: Adapters and Plugins
+      description: What adapters and plugins are you using? ie. db-mongodb, db-postgres, bundler-webpack, etc.
+  - type: markdown
+    attributes:
+      value: Before submitting the issue, go through the steps you've written down to make sure the steps provided are detailed and clear.
+  - type: markdown
+    attributes:
+      value: Contributors should be able to follow the steps provided in order to reproduce the bug.
+  - type: markdown
+    attributes:
+      value: These steps are used to add integration tests to ensure the same issue does not happen again. Thanks in advance!

.github/ISSUE_TEMPLATE/DOCUMENTATION_ISSUE.md

@@ -0,0 +1,13 @@
+---
+name: Documentation Issue
+about: Suggest fix to Payload documentation
+labels: 'documentation'
+---
+
+# Documentation Issue
+
+<!--- Please provide a summary of the documentation issue -->
+
+## Additional Details
+
+<!--- Provide any other additional details -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Feature Request
+    url: https://github.com/payloadcms/payload/discussions
+    about: Suggest an idea to improve Payload in our GitHub Discussions
+  - name: Question about Payload
+    url: https://github.com/payloadcms/payload/discussions
+    about: Please ask Payload-related questions in our GitHub Discussions

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+## Description
+
+<!-- Please include a summary of the pull request and any related issues it fixes. Please also include relevant motivation and context. -->
+
+- [ ] I have read and understand the [CONTRIBUTING.md](../CONTRIBUTING.md) document in this repository.
+
+## Type of change
+
+<!-- Please delete options that are not relevant. -->
+
+- [ ] Chore (non-breaking change which does not add functionality)
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Change to the [templates](../templates/) directory (does not affect core functionality)
+- [ ] Change to the [examples](../examples/) directory (does not affect core functionality)
+- [ ] This change requires a documentation update
+
+## Checklist:
+
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] Existing test suite passes locally with my changes
+- [ ] I have made corresponding changes to the documentation

.github/reproduction-guide.md

@@ -0,0 +1,63 @@
+# Reproduction Guide
+
+1. [fork](https://github.com/payloadcms/payload/fork) this repo
+2. run `yarn` to install dependencies
+3. open up the `test/_community` directory
+4. add any necessary `collections/globals/fields` in this directory to recreate the issue you are experiencing
+5. run `yarn dev _community` to start the admin panel
+
+**NOTE:** The goal is to isolate the problem by reducing the number of `collections/globals/fields` you add to the `test/_community` folder. This folder is _not_ meant for you to copy your project into, but rather recreate the issue you are experiencing with minimal config.
+
+## Example test directory file tree
+
+```text
+.
+├── config.ts
+├── int.spec.ts
+├── e2e.spec.ts
+└── payload-types.ts
+```
+
+- `config.ts` - This is the _granular_ Payload config for testing. It should be as lightweight as possible. Reference existing configs for an example
+- `int.spec.ts` [Optional] - This is the test file run by jest. Any test file must have a `*int.spec.ts` suffix.
+- `e2e.spec.ts` [Optional] - This is the end-to-end test file that will load up the admin UI using the above config and run Playwright tests.
+- `payload-types.ts` - Generated types from `config.ts`. Generate this file by running `yarn dev:generate-types _community`.
+
+The directory split up in this way specifically to reduce friction when creating tests and to add the ability to boot up Payload with that specific config. You should modify the files in `test/_community` to get started.
+
+<br />
+
+## Testing is optional but encouraged
+
+An issue does not need to have failing tests — reproduction steps with your forked repo are enough at this point. Some people like to dive deeper and we want to give you the guidance/tools to do so. Read more below:
+
+### Running integration tests (Payload API tests)
+
+First install [Jest Runner for VSVode](https://marketplace.visualstudio.com/items?itemName=firsttris.vscode-jest-runner).
+
+There are a couple ways run integration tests:
+
+- **Granularly** - you can run individual tests in vscode by installing the Jest Runner plugin and using that to run individual tests. Clicking the `debug` button will run the test in debug mode allowing you to set break points.
+
+  <img src="https://raw.githubusercontent.com/payloadcms/payload/main/packages/payload/src/admin/assets/images/github/int-debug.png" />
+
+- **Manually** - you can run all int tests in the `/test/_community/int.spec.ts` file by running the following command:
+
+  ```bash
+  yarn test:int _community
+  ```
+
+### Running E2E tests (Admin Panel UI tests)
+
+The easiest way to run E2E tests is to install
+
+- [Playwright Test for VSCode](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright)
+- [Playwright Runner](https://marketplace.visualstudio.com/items?itemName=ortoni.ortoni)
+
+Once they are installed you can open the `testing` tab in vscode sidebar and drill down to the test you want to run, i.e. `/test/_community/e2e.spec.ts`
+
+<img src="https://raw.githubusercontent.com/payloadcms/payload/main/packages/payload/src/admin/assets/images/github/e2e-debug.png" />
+
+#### Notes
+
+- It is recommended to add the test credentials (located in `test/credentials.ts`) to your autofill for `localhost:3000/admin` as this will be required on every nodemon restart. The default credentials are `dev@payloadcms.com` as email and `test` as password.

.github/workflows/main.yml

@@ -0,0 +1,208 @@
+name: build
+
+on:
+  pull_request:
+    types: [opened, reopened, synchronize]
+  push:
+    branches: ['main']
+
+jobs:
+  core-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 25
+
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+          run_install: false
+
+      - name: Get pnpm store directory
+        shell: bash
+        run: |
+          echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
+
+      - uses: actions/cache@v3
+        name: Setup pnpm cache
+        with:
+          path: ${{ env.STORE_PATH }}
+          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: |
+            ${{ runner.os }}-pnpm-store-
+            ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+
+      - run: pnpm install
+      - run: pnpm run build
+
+      - name: Cache build
+        uses: actions/cache@v3
+        with:
+          path: ./*
+          key: ${{ github.sha }}-${{ github.run_number }}
+
+  tests:
+    runs-on: ubuntu-latest
+    needs: core-build
+    strategy:
+      fail-fast: false
+      matrix:
+        database: [mongoose, postgres]
+    env:
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: postgres
+      POSTGRES_DB: payloadtests
+
+    steps:
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+          run_install: false
+
+      - name: Restore build
+        uses: actions/cache@v3
+        with:
+          path: ./*
+          key: ${{ github.sha }}-${{ github.run_number }}
+
+      - name: Start PostgreSQL
+        uses: CasperWA/postgresql-action@v1.2
+        with:
+          postgresql version: '14'  # See https://hub.docker.com/_/postgres for available versions
+          postgresql db: ${{ env.POSTGRES_DB }}
+          postgresql user: ${{ env.POSTGRES_USER }}
+          postgresql password: ${{ env.POSTGRES_PASSWORD }}
+        if: matrix.database == 'postgres'
+
+      - run: sleep 30
+      - name: Configure PostgreSQL
+        run: |
+          psql "postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@localhost:5432/$POSTGRES_DB" -c "CREATE ROLE runner SUPERUSER LOGIN;"
+          psql "postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@localhost:5432/$POSTGRES_DB" -c "SELECT version();"
+          echo "POSTGRES_URL=postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@localhost:5432/$POSTGRES_DB" >> $GITHUB_ENV
+        if: matrix.database == 'postgres'
+
+      - name: Component Tests
+        run: pnpm test:components
+
+      - name: Integration Tests
+        run: pnpm test:int
+        env:
+          PAYLOAD_DATABASE: ${{ matrix.database }}
+          POSTGRES_URL: ${{ env.POSTGRES_URL }}
+
+  tests-e2e:
+    runs-on: ubuntu-latest
+    needs: core-build
+    strategy:
+      fail-fast: false
+      matrix:
+        part: [1/4, 2/4, 3/4, 4/4]
+
+    steps:
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+          run_install: false
+
+      - name: Restore build
+        uses: actions/cache@v3
+        with:
+          path: ./*
+          key: ${{ github.sha }}-${{ github.run_number }}
+
+      - name: E2E Tests
+        run: pnpm test:e2e --part ${{ matrix.part }} --bail
+
+      - uses: actions/upload-artifact@v3
+        if: always()
+        with:
+          name: test-results
+          path: test-results/
+          retention-days: 1
+
+  tests-type-generation:
+    runs-on: ubuntu-latest
+    needs: core-build
+
+    steps:
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+          run_install: false
+
+      - name: Restore build
+        uses: actions/cache@v3
+        with:
+          path: ./*
+          key: ${{ github.sha }}-${{ github.run_number }}
+
+      - name: Generate Payload Types
+        run: pnpm dev:generate-types fields
+
+      - name: Generate GraphQL schema file
+        run: pnpm dev:generate-graphql-schema graphql-schema-gen
+
+  build-packages:
+    name: Build Packages
+    runs-on: ubuntu-latest
+    needs: core-build
+    strategy:
+      fail-fast: false
+      matrix:
+        pkg:
+          - db-mongodb
+          - db-postgres
+          - bundler-webpack
+          - bundler-vite
+          - richtext-slate
+          - richtext-lexical
+          - live-preview
+          - live-preview-react
+
+    steps:
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+          run_install: false
+
+      - name: Restore build
+        uses: actions/cache@v3
+        with:
+          path: ./*
+          key: ${{ github.sha }}-${{ github.run_number }}
+
+      - name: Build ${{ matrix.pkg }}
+        run: pnpm turbo run build --filter=${{ matrix.pkg }}

.github/workflows/tests.yml

@@ -1,30 +0,0 @@
-name: Node.js CI
-
-on: [push]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        node-version: [10.x, 12.x]
-
-    steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - name: Cache node modules
-      uses: actions/cache@v1
-      with:
-        path: ~/.npm
-        key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
-    - run: yarn
-    - run: yarn test:int # In-memory db + api tests
-      env:
-        CI: true

.gitignore

@@ -2,11 +2,16 @@ coverage
 package-lock.json
 dist
 .idea
+test-results
+.devcontainer
+/migrations
 
-# Created by https://www.gitignore.io/api/node,macos,windows,webstorm,sublimetext,visualstudiocode
+# Created by https://www.toptal.com/developers/gitignore/api/node,macos,windows,webstorm,sublimetext,visualstudiocode
+# Edit at https://www.toptal.com/developers/gitignore?templates=node,macos,windows,webstorm,sublimetext,visualstudiocode
 
 ### macOS ###
-*.DS_Store
+# General
+.DS_Store
 .AppleDouble
 .LSOverride
 
@@ -29,6 +34,10 @@ Network Trash Folder
 Temporary Items
 .apdisk
 
+### macOS Patch ###
+# iCloud generated files
+*.icloud
+
 ### Node ###
 # Logs
 logs
@@ -36,6 +45,11 @@ logs
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+lerna-debug.log*
+.pnpm-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
 
 # Runtime data
 pids
@@ -48,11 +62,12 @@ lib-cov
 
 # Coverage directory used by tools like istanbul
 coverage
+*.lcov
 
 # nyc test coverage
 .nyc_output
 
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
 .grunt
 
 # Bower dependency directory (https://bower.io/)
@@ -61,15 +76,18 @@ bower_components
 # node-waf configuration
 .lock-wscript
 
-# Compiled binary addons (http://nodejs.org/api/addons.html)
+# Compiled binary addons (https://nodejs.org/api/addons.html)
 build/Release
 
 # Dependency directories
 node_modules/
 jspm_packages/
 
-# Typescript v1 declaration files
-typings/
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
 
 # Optional npm cache directory
 .npm
@@ -77,6 +95,15 @@ typings/
 # Optional eslint cache
 .eslintcache
 
+# Optional stylelint cache
+.stylelintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
 # Optional REPL history
 .node_repl_history
 
@@ -86,25 +113,87 @@ typings/
 # Yarn Integrity file
 .yarn-integrity
 
-# dotenv environment variables file
+# dotenv environment variable files
 .env
+.env.development.local
+.env.test.local
+.env.production.local
+.env.local
 
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# vuepress v2.x temp and cache directory
+.temp
+
+# Docusaurus cache and generated files
+.docusaurus
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v2
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.yarn/install-state.gz
+.pnp.*
+
+### Node Patch ###
+# Serverless Webpack directories
+.webpack/
+
+# Optional stylelint cache
+
+# SvelteKit build / generate output
+.svelte-kit
 
 ### SublimeText ###
-# cache files for sublime text
+# Cache files for Sublime Text
 *.tmlanguage.cache
 *.tmPreferences.cache
 *.stTheme.cache
 
-# workspace files are user-specific
+# Workspace files are user-specific
 *.sublime-workspace
 
-# project files should be checked into the repository, unless a significant
-# proportion of contributors will probably not be using SublimeText
+# Project files should be checked into the repository, unless a significant
+# proportion of contributors will probably not be using Sublime Text
 # *.sublime-project
 
-# sftp configuration file
+# SFTP configuration file
 sftp-config.json
+sftp-config-alt*.json
 
 # Package control specific files
 Package Control.last-run
@@ -124,46 +213,77 @@ GitHub.sublime-settings
 
 ### VisualStudioCode ###
 .vscode/*
+!.vscode/settings.json
 !.vscode/tasks.json
 !.vscode/launch.json
 !.vscode/extensions.json
+!.vscode/*.code-snippets
+
+# Local History for Visual Studio Code
+.history/
+
+# Built Visual Studio Code Extensions
+*.vsix
+
+### VisualStudioCode Patch ###
+# Ignore all local history of files
 .history
+.ionide
 
 ### WebStorm ###
-# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and Webstorm
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
 # Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
 
-# User-specific stuff:
+# User-specific stuff
 .idea/**/workspace.xml
 .idea/**/tasks.xml
-.idea/dictionaries
+.idea/**/usage.statistics.xml
+.idea/**/dictionaries
+.idea/**/shelf
 
-# Sensitive or high-churn files:
+# AWS User-specific
+.idea/**/aws.xml
+
+# Generated files
+.idea/**/contentModel.xml
+
+# Sensitive or high-churn files
 .idea/**/dataSources/
 .idea/**/dataSources.ids
-.idea/**/dataSources.xml
 .idea/**/dataSources.local.xml
 .idea/**/sqlDataSources.xml
 .idea/**/dynamic.xml
 .idea/**/uiDesigner.xml
+.idea/**/dbnavigator.xml
 
-# Gradle:
+# Gradle
 .idea/**/gradle.xml
 .idea/**/libraries
 
-# CMake
-cmake-build-debug/
+# Gradle and Maven with auto-import
+# When using Gradle or Maven with auto-import, you should exclude module files,
+# since they will be recreated, and may cause churn.  Uncomment if using
+# auto-import.
+# .idea/artifacts
+# .idea/compiler.xml
+# .idea/jarRepositories.xml
+# .idea/modules.xml
+# .idea/*.iml
+# .idea/modules
+# *.iml
+# *.ipr
 
-# Mongo Explorer plugin:
+# CMake
+cmake-build-*/
+
+# Mongo Explorer plugin
 .idea/**/mongoSettings.xml
 
-## File-based project format:
+# File-based project format
 *.iws
 
-## Plugin-specific files:
-
 # IntelliJ
-/out/
+out/
 
 # mpeltonen/sbt-idea plugin
 .idea_modules/
@@ -174,8 +294,8 @@ atlassian-ide-plugin.xml
 # Cursive Clojure plugin
 .idea/replstate.xml
 
-# Ruby plugin and RubyMine
-/.rakeTasks
+# SonarLint plugin
+.idea/sonarlint/
 
 # Crashlytics plugin (for Android Studio and IntelliJ)
 com_crashlytics_export_strings.xml
@@ -183,6 +303,12 @@ crashlytics.properties
 crashlytics-build.properties
 fabric.properties
 
+# Editor-based Rest Client
+.idea/httpRequests
+
+# Android studio 3.1+ serialized cache file
+.idea/caches/build_file_checksums.ser
+
 ### WebStorm Patch ###
 # Comment Reason: https://github.com/joeblau/gitignore.io/issues/186#issuecomment-215987721
 
@@ -192,16 +318,43 @@ fabric.properties
 # *.ipr
 
 # Sonarlint plugin
-.idea/sonarlint
+# https://plugins.jetbrains.com/plugin/7973-sonarlint
+.idea/**/sonarlint/
+
+# SonarQube Plugin
+# https://plugins.jetbrains.com/plugin/7238-sonarqube-community-plugin
+.idea/**/sonarIssues.xml
+
+# Markdown Navigator plugin
+# https://plugins.jetbrains.com/plugin/7896-markdown-navigator-enhanced
+.idea/**/markdown-navigator.xml
+.idea/**/markdown-navigator-enh.xml
+.idea/**/markdown-navigator/
+
+# Cache file creation bug
+# See https://youtrack.jetbrains.com/issue/JBR-2257
+.idea/$CACHE_FILE$
+
+# CodeStream plugin
+# https://plugins.jetbrains.com/plugin/12206-codestream
+.idea/codestream.xml
+
+# Azure Toolkit for IntelliJ plugin
+# https://plugins.jetbrains.com/plugin/8053-azure-toolkit-for-intellij
+.idea/**/azureSettings.xml
 
 ### Windows ###
 # Windows thumbnail cache files
 Thumbs.db
+Thumbs.db:encryptable
 ehthumbs.db
 ehthumbs_vista.db
 
+# Dump file
+*.stackdump
+
 # Folder config file
-Desktop.ini
+[Dd]esktop.ini
 
 # Recycle Bin used on file shares
 $RECYCLE.BIN/
@@ -209,21 +362,13 @@ $RECYCLE.BIN/
 # Windows Installer files
 *.cab
 *.msi
+*.msix
 *.msm
 *.msp
 
 # Windows shortcuts
 *.lnk
 
+# End of https://www.toptal.com/developers/gitignore/api/node,macos,windows,webstorm,sublimetext,visualstudiocode
 
-# End of https://www.gitignore.io/api/node,macos,windows,webstorm,sublimetext,visualstudiocode
-
-# Ignores compiled CSS
-src/**/*.css
-demo**/*.css
-dist
-
-# Ignore all uploads
-demo/upload
-demo/media
-demo/files
+/build

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+pnpm run lint-staged --quiet

.node-version

@@ -0,0 +1 @@
+v18.17.1

.npmrc

@@ -0,0 +1,2 @@
+symlink=true
+node-linker=isolated # due to a typescript bug, isolated mode requires @types/express-serve-static-core, terser and monaco-editor to be installed https://github.com/microsoft/TypeScript/issues/47663#issuecomment-1519138189 along with two other changes in the code which I've marked with (tsbugisolatedmode) in the code

.nvmrc

@@ -0,0 +1 @@
+v18.17.1

.prettierignore

@@ -0,0 +1,11 @@
+.tmp
+**/.git
+**/.hg
+**/.pnp.*
+**/.svn
+**/.yarn/**
+**/build
+**/dist/**
+**/node_modules
+**/temp
+**/docs/**

.prettierrc.json

@@ -0,0 +1,6 @@
+{
+  "singleQuote": true,
+  "trailingComma": "all",
+  "printWidth": 100,
+  "semi": false
+}

.release-it.json

@@ -0,0 +1,22 @@
+{
+  "verbose": true,
+  "git": {
+    "commitMessage": "chore(release): v${version}",
+    "requireCleanWorkingDir": true
+  },
+  "github": {
+    "release": true
+  },
+  "npm": {
+    "skipChecks": true
+  },
+  "hooks": {
+    "before:init": ["pnpm i", "pnpm clean", "pnpm test"]
+  },
+  "plugins": {
+    "@release-it/conventional-changelog": {
+      "preset": "angular",
+      "infile": "CHANGELOG.md"
+    }
+  }
+}

.release-it.pre.json

@@ -0,0 +1,25 @@
+{
+  "verbose": true,
+  "git": {
+    "requireCleanWorkingDir": false,
+    "commit": false,
+    "push": false,
+    "tag": false
+  },
+  "github": {
+    "release": true
+  },
+  "npm": {
+    "skipChecks": true,
+    "tag": "canary"
+  },
+  "hooks": {
+    "before:init": ["pnpm i", "pnpm clean", "pnpm test"]
+  },
+  "plugins": {
+    "@release-it/conventional-changelog": {
+      "preset": "angular",
+      "infile": "CHANGELOG.md"
+    }
+  }
+}

.vscode/extensions.json

@@ -0,0 +1,3 @@
+{
+  "recommendations": ["esbenp.prettier-vscode", "dbaeumer.vscode-eslint"]
+}

.vscode/launch.json

@@ -1,66 +1,146 @@
 {
   // Use IntelliSense to learn about possible attributes.
   // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
   "configurations": [
     {
-      "name": "Debug Jest Tests",
-      "type": "node",
+      "command": "pnpm run dev _community",
+      "cwd": "${workspaceFolder}",
+      "name": "Run Dev Community",
       "request": "launch",
-      "runtimeArgs": [
-        "--inspect-brk",
-        "${workspaceRoot}/node_modules/.bin/jest",
-        "--runInBand"
-      ],
-      "env": {
-        "PAYLOAD_CONFIG_PATH": "demo/payload.config.js"
-      },
-      "console": "integratedTerminal",
-      "internalConsoleOptions": "neverOpen",
-      "port": 9229,
-      "skipFiles": [
-        "<node_internals>/**"
-      ]
+      "type": "node-terminal"
     },
     {
-      "name": "Debug Jest Test - Current File",
-      "type": "node",
+      "command": "pnpm run dev fields",
+      "cwd": "${workspaceFolder}",
+      "name": "Run Dev Fields",
       "request": "launch",
-      "runtimeArgs": [
-        "--inspect-brk",
-        "${workspaceRoot}/node_modules/.bin/jest",
-        "${fileBasename}",
-        "--runInBand"
-      ],
-      "env": {
-        "PAYLOAD_CONFIG_PATH": "demo/payload.config.js"
-      },
-      "console": "integratedTerminal",
-      "internalConsoleOptions": "neverOpen",
-      "port": 9229,
-      "skipFiles": [
-        "<node_internals>/**"
-      ]
+      "type": "node-terminal"
     },
     {
-      "type": "node",
+      "command": "pnpm run dev:postgres fields",
+      "cwd": "${workspaceFolder}",
+      "name": "Run Dev Postgres",
       "request": "launch",
-      "name": "Launch Program",
-      "env": {
-        "PAYLOAD_CONFIG_PATH": "demo/payload.config.js"
-      },
-      "program": "${workspaceFolder}/demo/server.js",
-      "skipFiles": [
-        "<node_internals>/**"
-      ]
+      "type": "node-terminal"
     },
     {
-      "type": "chrome",
+      "command": "pnpm run dev versions",
+      "cwd": "${workspaceFolder}",
+      "name": "Run Dev Versions",
       "request": "launch",
-      "name": "Launch Chrome against Localhost",
-      "url": "http://localhost:3000/admin",
-      "webRoot": "${workspaceFolder}"
+      "type": "node-terminal"
+    },
+    {
+      "command": "PAYLOAD_BUNDLER=vite pnpm run dev fields",
+      "cwd": "${workspaceFolder}",
+      "name": "Run Dev Fields (Vite)",
+      "request": "launch",
+      "type": "node-terminal",
+      "env": {
+        "NODE_ENV": "production"
+      }
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts build",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/fields/config.ts",
+        "PAYLOAD_BUNDLER": "vite",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+      },
+      "name": "Build CLI - Vite",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts build",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/fields/config.ts",
+        "PAYLOAD_ANALYZE_BUNDLE": "true",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+      },
+      "name": "Build CLI - Webpack",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts generate:types",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/_community/config.ts",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+      },
+      "name": "Generate Types CLI",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts migrate:status",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/migrations-cli/config.ts",
+        "PAYLOAD_DATABASE": "postgres",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+        // "PAYLOAD_DROP_DATABASE": "true",
+      },
+      "name": "Migrate CLI - status",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts migrate:create yass",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/migrations-cli/config.ts",
+        "PAYLOAD_DATABASE": "postgres",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+        // "PAYLOAD_DROP_DATABASE": "true",
+      },
+      "name": "Migrate CLI - create",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts migrate:down",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/migrations-cli/config.ts",
+        "PAYLOAD_DATABASE": "mongoose",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+        // "PAYLOAD_DROP_DATABASE": "true",
+      },
+      "name": "Migrate CLI - down",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts migrate:reset",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/migrations-cli/config.ts",
+        "PAYLOAD_DATABASE": "mongoose",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+        // "PAYLOAD_DROP_DATABASE": "true",
+      },
+      "name": "Migrate CLI - reset",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "ts-node ./packages/payload/src/bin/index.ts migrate:refresh",
+      "env": {
+        "PAYLOAD_CONFIG_PATH": "test/migrations-cli/config.ts",
+        "PAYLOAD_DATABASE": "mongoose",
+        "DISABLE_SWC": "true" // SWC messes up debugging the bin scripts
+        // "PAYLOAD_DROP_DATABASE": "true",
+      },
+      "name": "Migrate CLI - refresh",
+      "outputCapture": "std",
+      "request": "launch",
+      "type": "node-terminal"
     }
-  ]
+  ],
+  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+  "version": "0.2.0"
 }

.vscode/settings.json

@@ -0,0 +1,39 @@
+{
+  "npm.packageManager": "pnpm",
+  "editor.defaultFormatter": "esbenp.prettier-vscode",
+  "[typescript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.eslint": true
+    }
+  },
+  "[typescriptreact]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.eslint": true
+    }
+  },
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.eslint": true
+    }
+  },
+  "[json]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true
+  },
+  "[jsonc]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true
+  },
+  "editor.formatOnSaveMode": "file",
+  // All ESLint rules to 'warn' to differentate from TypeScript's 'error' level
+  "eslint.rules.customizations": [{ "rule": "*", "severity": "warn" }],
+  "typescript.tsdk": "node_modules/typescript/lib",
+  // Load .git-blame-ignore-revs file
+  "gitlens.advanced.blame.customArguments": ["--ignore-revs-file", ".git-blame-ignore-revs"]
+}

CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contributing to Payload
+
+Below you'll find a set of guidelines for how to contribute to Payload.
+
+## Opening issues
+
+Before you submit an issue, please check all existing [open and closed issues](https://github.com/payloadcms/payload/issues) to see if your issue has previously been resolved or is already known. If there is already an issue logged, feel free to upvote it by adding a :thumbsup: [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). If you would like to submit a new issue, please fill out our Issue Template to the best of your ability so we can accurately understand your report.
+
+## Security issues & vulnerabilities
+
+If you come across an issue related to security, or a potential attack vector within Payload or one of its dependencies, please DO NOT create a publicly viewable issue. Instead, please contact us directly at [`dev@payloadcms.com`](mailto:dev@payloadcms.com). We will do everything we can to respond to the issue as soon as possible.
+
+If you find a vulnerability within the core Payload repository, and we determine that it is remediable and of significant nature, we will be happy to pay you a reward for your findings and diligence. [`Contact us`](mailto:dev@payloadcms.com) to find out more.
+
+## Documentation edits
+
+Payload documentation can be found directly within its codebase and you can feel free to make changes / improvements to any of it through opening a PR. We utilize these files directly in our website and will periodically deploy documentation updates as necessary.
+
+## Building additional features
+
+If you're an incredibly awesome person and want to help us make Payload even better through new features or additions, we would be thrilled to work with you.
+
+## Design Contributions
+
+When it comes to design-related changes or additions, it's crucial for us to ensure a cohesive user experience and alignment with our broader design vision. Before embarking on any implementation that would affect the design or UI/UX, we ask that you **first share your design proposal** with us for review and approval.
+
+Our design review ensures that proposed changes fit seamlessly with other components, both existing and planned. This step is meant to prevent unintentional design inconsistencies and to save you from investing time in implementing features that might need significant design alterations later.
+
+### Before Starting
+
+To help us work on new features, you can create a new feature request post in [GitHub Discussion](https://github.com/payloadcms/payload/discussions) or discuss it in our [Discord](https://discord.com/invite/payload). New functionality often has large implications across the entire Payload repo, so it is best to discuss the architecture and approach before starting work on a pull request.
+
+### Code
+
+Most new functionality should keep testing in mind. With 1.0, testability of new features has been vastly improved. All top-level directories within the `test/` directory are for testing a specific category: `fields`, `collections`, etc.
+
+If it makes sense to add your feature to an existing test directory, please do so.
+
+A typical directory with `test/` will be structured like this:
+
+```text
+.
+├── config.ts
+├── int.spec.ts
+├── e2e.spec.ts
+└── payload-types.ts
+```
+
+- `config.ts` - This is the _granular_ Payload config for testing. It should be as lightweight as possible. Reference existing configs for an example
+- `int.spec.ts` - This is the test file run by jest. Any test file must have a `*int.spec.ts` suffix.
+- `e2e.spec.ts` - This is the end-to-end test file that will load up the admin UI using the above config and run Playwright tests. These tests are typically only needed if a large change is being made to the Admin UI.
+- `payload-types.ts` - Generated types from `config.ts`. Generate this file by running `pnpm dev:generate-types my-test-dir`.
+
+The directory split up in this way specifically to reduce friction when creating tests and to add the ability to boot up Payload with that specific config.
+
+The following command will start Payload with your config: `pnpm dev my-test-dir`. This command will start up Payload using your config and refresh a test database on every restart.
+
+By default, it will automatically log you in with the default credentials. To disable that, you can either pass in the --no-auto-login flag (example: `pnpm dev my-test-dir --no-auto-login`) or set the `PAYLOAD_PUBLIC_DISABLE_AUTO_LOGIN` environment variable to `false`.
+
+If you wish to use to your own Mongo database for the `test` directory instead of using the in memory database, all you need to do is add the following env vars to the `test/dev.ts` file:
+
+- `process.env.NODE_ENV`
+- `process.env.PAYLOAD_TEST_MONGO_URL`
+- Simply set `process.env.NODE_ENV` to `test` and set `process.env.PAYLOAD_TEST_MONGO_URL` to your mongo url e.g. `mongodb://127.0.0.1/your-test-db`.
+
+NOTE: It is recommended to add the test credentials (located in `test/credentials.ts`) to your autofill for `localhost:3000/admin` as this will be required on every nodemon restart. The default credentials are `dev@payloadcms.com` as E-Mail and `test` as password.
+
+### Commits
+
+We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for our commit messages. Please follow this format when creating commits. Here are some examples:
+
+- `feat: adds new feature`
+- `fix: fixes bug`
+- `docs: adds documentation`
+- `chore: does chore`
+
+Here's a breakdown of the format. At the top-level, we use the following types to categorize our commits:
+
+- `feat`: new feature that adds functionality. These are automatically added to the changelog when creating new releases.
+- `fix`: a fix to an existing feature. These are automatically added to the changelog when creating new releases.
+- `docs`: changes to [docs](./docs) only. These do not appear in the changelog.
+- `chore`: changes to code that is neither a fix nor a feature (e.g. refactoring, adding tests, etc.). These do not appear in the changelog.
+
+If you are committing to [templates](./templates) or [examples](./examples), use the `chore` type with the proper scope, like this:
+
+- `chore(templates): adds feature to template`
+- `chore(examples): fixes bug in example`
+
+## Pull Requests
+
+For all Pull Requests, you should be extremely descriptive about both your problem and proposed solution. If there are any affected open or closed issues, please leave the issue number in your PR message.

ISSUE_GUIDE.md

@@ -0,0 +1,69 @@
+# Reporting an issue
+
+To report an issue, please follow the steps below:
+
+1. Fork this repository
+2. Add necessary collections/globals/fields to the `test/_community` directory to recreate the issue you are experiencing
+3. Create an issue and add a link to your forked repo
+
+**The goal is to isolate the problem by reducing the number of fields/collections you add to the test/\_community folder. This folder is not meant for you to copy your project into, but to recreate the issue you are experiencing with minimal config.**
+
+## Test directory file tree explanation
+
+```text
+.
+├── config.ts
+├── int.spec.ts
+├── e2e.spec.ts
+└── payload-types.ts
+```
+
+- `config.ts` - This is the _granular_ Payload config for testing. It should be as lightweight as possible. Reference existing configs for an example
+- `int.spec.ts` [Optional] - This is the test file run by jest. Any test file must have a `*int.spec.ts` suffix.
+- `e2e.spec.ts` [Optional] - This is the end-to-end test file that will load up the admin UI using the above config and run Playwright tests.
+- `payload-types.ts` - Generated types from `config.ts`. Generate this file by running `pnpm dev:generate-types _community`.
+
+The directory split up in this way specifically to reduce friction when creating tests and to add the ability to boot up Payload with that specific config. You should modify the files in `test/_community` to get started.
+
+## How to start test collection admin UI
+
+To start the admin panel so you can manually recreate your issue, you can run the following command:
+
+```bash
+# This command will start up Payload using your config
+# NOTE: it will wipe the test database on restart
+pnpm dev _community
+```
+
+## Testing is optional but encouraged
+
+An issue does not need to have failing tests — reproduction steps with your forked repo are enough at this point. Some people like to dive deeper and we want to give you the guidance/tools to do so. Read more below.
+
+### How to run integration tests (Payload API tests)
+
+There are a couple ways to do this:
+
+- **Granularly** - you can run individual tests in vscode by installing the Jest Runner plugin and using that to run individual tests. Clicking the `debug` button will run the test in debug mode allowing you to set break points.
+
+  <img src="https://raw.githubusercontent.com/payloadcms/payload/main/src/admin/assets/images/github/int-debug.png" />
+
+- **Manually** - you can run all int tests in the `/test/_community/int.spec.ts` file by running the following command:
+
+  ```bash
+  pnpm test:int _community
+  ```
+
+### How to run E2E tests (Admin Panel UI tests)
+
+The easiest way to run E2E tests is to install
+
+- [Playwright Test for VSCode](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright)
+- [Playwright Runner](https://marketplace.visualstudio.com/items?itemName=ortoni.ortoni)
+
+Once they are installed you can open the `testing` tab in vscode sidebar and drill down to the test you want to run, i.e. `/test/_community/e2e.spec.ts`
+
+<img src="https://raw.githubusercontent.com/payloadcms/payload/main/src/admin/assets/images/github/e2e-debug.png" />
+
+#### Notes
+
+- It is recommended to add the test credentials (located in `test/credentials.ts`) to your autofill for `localhost:3000/admin` as this will be required on every nodemon restart. The default credentials are `dev@payloadcms.com` as email and `test` as password.

README.md

@@ -1,21 +1,137 @@
-# Payload
+<a href="https://payloadcms.com">
+  <img width="100%" src="https://github.com/payloadcms/payload/blob/main/packages/payload/src/admin/assets/images/github-banner-alt.jpg?raw=true" alt="Payload headless CMS Admin panel built with React" />
+</a>
+<br />
+<br />
+<p align="left">
+  <a href="https://github.com/payloadcms/payload/actions">
+    <img alt="GitHub Workflow Status" src="https://img.shields.io/github/actions/workflow/status/payloadcms/payload/main.yml?style=flat-square">
+  </a>
+  &nbsp;
+  <a href="https://discord.gg/payload">
+    <img alt="Discord" src="https://img.shields.io/discord/967097582721572934?label=Discord&color=7289da&style=flat-square" />
+  </a>
+  &nbsp;
+  <a href="https://www.npmjs.com/package/payload">
+    <img alt="npm" src="https://img.shields.io/npm/v/payload?style=flat-square" />
+  </a>
+  &nbsp;
+  <a href="https://twitter.com/payloadcms">
+    <img src="https://img.shields.io/badge/follow-payloadcms-1DA1F2?logo=twitter&style=flat-square" alt="Payload Twitter" />
+  </a>
+</p>
+<hr/>
+<h4>
+<a target="_blank" href="https://payloadcms.com/docs/getting-started/what-is-payload" rel="dofollow"><strong>Explore the Docs</strong></a>&nbsp;·&nbsp;<a target="_blank" href="https://payloadcms.com/community-help" rel="dofollow"><strong>Community Help</strong></a>&nbsp;·&nbsp;<a target="_blank" href="https://demo.payloadcms.com/" rel="dofollow"><strong>Try Live Demo</strong></a>&nbsp;·&nbsp;<a target="_blank" href="https://github.com/payloadcms/payload/discussions/1539" rel="dofollow"><strong>Roadmap</strong></a>&nbsp;·&nbsp;<a target="_blank" href="https://www.g2.com/products/payload-cms/reviews#reviews" rel="dofollow"><strong>View G2 Reviews</strong></a>
+</h4>
+<hr/>
 
-Headless CMS and application framework
+### 🎉 Payload 2.0 is now available! Read more in the [announcement post](https://payloadcms.com/blog/payload-2-0).
 
-*TODO: More on why to use it and some features*
+<h3>Benefits over a regular CMS</h3>
+<ul>
+  <li>Don’t hit some third-party SaaS API, hit your own API</li>
+  <li>Use your own database and own your data</li>
+  <li>It's just Express - do what you want outside of Payload</li>
+  <li>No need to learn how Payload works - if you know JS, you know Payload</li>
+  <li>No vendor lock-in</li>
+  <li>Avoid microservices hell - get everything (even auth) in one place</li>
+  <li>Never touch ancient WP code again</li>
+  <li>Build faster, never hit a roadblock</li>
+  <li>Both admin and backend are 100% extensible</li>
+</ul>
 
-## Installation
+## ☁️ Deploy instantly with Payload Cloud.
 
-`yarn add @payloadcms/payload` or `npm install @payloadcms/payload`
+Create a cloud account, connect your GitHub, and [deploy in minutes](https://payloadcms.com/new).
 
-## Usage
+## 🚀 Get started by self-hosting completely free, forever.
 
-*TODO: Show basic usage and link to docs*
+Before beginning to work with Payload, make sure you have all of the [required software](https://payloadcms.com/docs/getting-started/installation).
 
-## Contributing
+```text
+npx create-payload-app
+```
 
-*TODO: Create Contributing.md*
+Alternatively, it only takes about five minutes to [create an app from scratch](https://payloadcms.com/docs/getting-started/installation#from-scratch).
 
-## License
+## 🖱️ One-click templates
 
-*TODO: Create License.md*
+Jumpstart your next project by starting with a pre-made template. These are production-ready, end-to-end solutions designed to get you to market as fast as possible.
+
+### [🛒 E-Commerce](https://github.com/payloadcms/payload/tree/main/templates/ecommerce)
+
+Eliminate the need to combine Shopify and a CMS, and instead do it all with Payload + Stripe. Comes with a beautiful, fully functional front-end complete with shopping cart, checkout, orders, and much more.
+
+### [🌐 Website](https://github.com/payloadcms/payload/tree/main/templates/website)
+
+Build any kind of website, blog, or portfolio from small to enterprise. Comes with a beautiful, fully functional front-end complete with posts, projects, comments, and much more.
+
+We're constantly adding more templates to our [Templates Directory](https://github.com/payloadcms/payload/tree/main/templates). If you maintain your own template, consider adding the `payload-template` topic to your GitHub repository for others to find.
+
+- [Official Templates](https://github.com/payloadcms/payload/tree/main/templates)
+- [Community Templates](https://github.com/topics/payload-template)
+
+## ✨ Features
+
+- Completely free and open-source
+- [GraphQL](https://payloadcms.com/docs/graphql/overview), [REST](https://payloadcms.com/docs/rest-api/overview), and [Local](https://payloadcms.com/docs/local-api/overview) APIs
+- [Easily customizable ReactJS Admin](https://payloadcms.com/docs/admin/overview)
+- [Fully self-hosted](https://payloadcms.com/docs/production/deployment)
+- [Extensible Authentication](https://payloadcms.com/docs/authentication/overview)
+- [Local file storage & upload](https://payloadcms.com/docs/upload/overview)
+- [Version History and Drafts](https://payloadcms.com/docs/versions/overview)
+- [Field-based Localization](https://payloadcms.com/docs/configuration/localization)
+- [Block-based Layout Builder](https://payloadcms.com/docs/fields/blocks)
+- [Extensible SlateJS rich text editor](https://payloadcms.com/docs/fields/rich-text)
+- [Array field type](https://payloadcms.com/docs/fields/array)
+- [Field conditional logic](https://payloadcms.com/docs/fields/overview#conditional-logic)
+- Extremely granular [Access Control](https://payloadcms.com/docs/access-control/overview)
+- [Document and field-level hooks](https://payloadcms.com/docs/hooks/overview) for every action Payload provides
+- Built with Typescript & very Typescript-friendly
+- Intensely fast API
+- Highly secure thanks to HTTP-only cookies, CSRF protection, and more
+
+<a target="_blank" href="https://github.com/payloadcms/payload/discussions"><strong>Request Feature</strong></a>
+
+## 🗒️ Documentation
+
+Check out the [Payload website](https://payloadcms.com/docs/getting-started/what-is-payload) to find in-depth documentation for everything that Payload offers.
+
+Migrating from v1 to v2? Check out the [2.0 Release Notes](https://github.com/payloadcms/payload/releases/tag/v2.0.0) on how to do it.
+
+## 🙋 Contributing
+
+If you want to add contributions to this repository, please follow the instructions in [contributing.md](./CONTRIBUTING.md).
+
+## 📚 Examples
+
+The [Examples Directory](./examples) is a great resource for learning how to setup Payload in a variety of different ways, but you can also find great examples in our blog and throughout our social media.
+
+- [Examples Directory](./examples)
+- [Payload Blog](https://payloadcms.com/blog)
+- [Payload YouTube](https://www.youtube.com/@payloadcms)
+
+## 🔌 Plugins
+
+Payload is highly extensible and allows you to install or distribute plugins that add or remove functionality. There are both officially-supported and community-supported plugins available. If you maintain your own plugin, consider adding the `payload-plugin` topic to your GitHub repository for others to find.
+
+- [Official Plugins](https://github.com/orgs/payloadcms/repositories?q=topic%3Apayload-plugin)
+- [Community Plugins](https://github.com/topics/payload-plugin)
+
+## 🚨 Need help?
+
+There are lots of good conversations and resources in our Github Discussions board and our Discord Server. If you're struggling with something, chances are, someone's already solved what you're up against. :point_down:
+
+- [GitHub Discussions](https://github.com/payloadcms/payload/discussions)
+- [GitHub Issues](https://github.com/payloadcms/payload/issues)
+- [Discord](https://t.co/30APlsQUPB)
+- [Community Help](https://payloadcms.com/community-help)
+
+## ⭐ Like what we're doing? Give us a star
+
+![payload-github-star](https://cms.payloadcms.com/media/payload-github-star.gif)
+
+## 👏 Thanks to all our contributors
+
+<img align="left" src="https://contributors-img.web.app/image?repo=payloadcms/payload"/>

SECURITY.md

@@ -0,0 +1,5 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+Please report any security issues or concerns to [info@payloadcms.com](mailto:info@payloadcms.com).

demo/access/checkRole.js

@@ -1,21 +0,0 @@
-/**
- * authorize a request by comparing the current user with one or more roles
- * @param allRoles
- * @param user
- * @returns {Function}
- */
-const checkRole = (allRoles, user) => {
-  if (user) {
-    if (allRoles.some((role) => {
-      return user.roles && user.roles.some((individualRole) => {
-        return individualRole === role;
-      });
-    })) {
-      return true;
-    }
-  }
-
-  return false;
-};
-
-module.exports = checkRole;

demo/access/roles.js

@@ -1,7 +0,0 @@
-module.exports = [
-  'admin',
-  'editor',
-  'moderator',
-  'user',
-  'viewer',
-];

demo/blocks/CallToAction.js

@@ -1,23 +0,0 @@
-module.exports = {
-  slug: 'cta',
-  labels: {
-    singular: 'Call to Action',
-    plural: 'Calls to Action',
-  },
-  fields: [
-    {
-      name: 'label',
-      label: 'Label',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-    },
-    {
-      name: 'url',
-      label: 'URL',
-      type: 'text',
-      height: 100,
-      required: true,
-    },
-  ],
-};

demo/blocks/Email.js

@@ -1,16 +0,0 @@
-module.exports = {
-  slug: 'email',
-  labels: {
-    singular: 'Email',
-    plural: 'Emails',
-  },
-  fields: [
-    {
-      name: 'testEmail',
-      label: 'Test Email Field',
-      type: 'email',
-      maxLength: 100,
-      required: true,
-    },
-  ],
-};

demo/blocks/Number.js

@@ -1,16 +0,0 @@
-module.exports = {
-  slug: 'number',
-  labels: {
-    singular: 'Number',
-    plural: 'Numbers',
-  },
-  fields: [
-    {
-      name: 'testNumber',
-      label: 'Test Number Field',
-      type: 'number',
-      maxLength: 100,
-      required: true,
-    },
-  ],
-};

demo/blocks/Quote.js

@@ -1,31 +0,0 @@
-module.exports = {
-  blockImage: '/static/assets/images/generic-block-image.svg',
-  slug: 'quote',
-  labels: {
-    singular: 'Quote',
-    plural: 'Quotes',
-  },
-  fields: [
-    {
-      name: 'author',
-      label: 'Author',
-      type: 'relationship',
-      relationTo: 'public-users',
-      required: true,
-    },
-    {
-      name: 'quote',
-      label: 'Quote',
-      type: 'textarea',
-      height: 100,
-      required: true,
-    },
-    {
-      name: 'color',
-      label: 'Color',
-      type: 'text',
-      maxLength: 7,
-      required: true,
-    },
-  ],
-};

demo/client/components.js

@@ -1,9 +0,0 @@
-import PageList from '../collections/Page/components/List';
-
-const components = {
-  pages: {
-    List: PageList,
-  },
-};
-
-export default components;

demo/client/components/layout/Sidebar/index.js

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const Sidebar = () => <div className="sidebar">fake sidebar</div>
-
-export default Sidebar;

demo/collections/Admin.js

@@ -1,61 +0,0 @@
-const roles = require('../access/roles');
-const checkRole = require('../access/checkRole');
-
-const access = ({ req: { user } }) => {
-  const result = checkRole(['admin'], user);
-  return result;
-};
-
-module.exports = {
-  slug: 'admins',
-  labels: {
-    singular: 'Admin',
-    plural: 'Admins',
-  },
-  access: {
-    create: access,
-    read: access,
-    update: access,
-    delete: access,
-    admin: () => true,
-  },
-  auth: {
-    tokenExpiration: 7200,
-    useAPIKey: true,
-    secureCookie: process.env.NODE_ENV === 'production',
-  },
-  fields: [
-    {
-      name: 'roles',
-      label: 'Role',
-      type: 'select',
-      options: roles,
-      defaultValue: 'user',
-      required: true,
-      saveToJWT: true,
-      hasMany: true,
-    },
-    {
-      name: 'apiKey',
-      access: {
-        read: ({ req: { user } }) => {
-          if (checkRole(['admin'], user)) {
-            return true;
-          }
-
-          if (user) {
-            return {
-              email: user.email,
-            };
-          }
-
-          return false;
-        },
-      },
-    },
-  ],
-  timestamps: true,
-  admin: {
-    useAsTitle: 'email',
-  },
-};

demo/collections/AllFields.js

@@ -1,233 +0,0 @@
-const checkRole = require('../access/checkRole');
-const Email = require('../blocks/Email');
-const Quote = require('../blocks/Quote');
-const NumberBlock = require('../blocks/Number');
-const CallToAction = require('../blocks/CallToAction');
-
-const AllFields = {
-  slug: 'all-fields',
-  labels: {
-    singular: 'All Fields',
-    plural: 'All Fields',
-  },
-  admin: {
-    useAsTitle: 'text',
-  },
-  preview: (doc, token) => {
-    if (doc && doc.text) {
-      return `http://localhost:3000/previewable-posts/${doc.text.value}?preview=true&token=${token}`;
-    }
-
-    return null;
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'text',
-      type: 'text',
-      label: 'Text',
-      required: true,
-      defaultValue: 'Default Value',
-      unique: true,
-      access: {
-        create: ({ req: { user } }) => checkRole(['admin'], user),
-        update: ({ req: { user } }) => checkRole(['admin'], user),
-        read: ({ req: { user } }) => Boolean(user),
-      },
-    },
-    {
-      name: 'image',
-      type: 'upload',
-      label: 'Image',
-      relationTo: 'media',
-    },
-    {
-      name: 'select',
-      label: 'Select',
-      type: 'select',
-      options: [{
-        value: 'option-1',
-        label: 'Option 1 Label',
-      }, {
-        value: 'option-2',
-        label: 'Option 2 Label',
-      }, {
-        value: 'option-3',
-        label: 'Option 3 Label',
-      }, {
-        value: 'option-4',
-        label: 'Option 4 Label',
-      }],
-      defaultValue: 'option-1',
-      required: true,
-    },
-    {
-      name: 'selectMany',
-      label: 'Select w/ hasMany',
-      type: 'select',
-      options: [{
-        value: 'option-1',
-        label: 'Option 1 Label',
-      }, {
-        value: 'option-2',
-        label: 'Option 2 Label',
-      }, {
-        value: 'option-3',
-        label: 'Option 3 Label',
-      }, {
-        value: 'option-4',
-        label: 'Option 4 Label',
-      }],
-      defaultValue: 'option-1',
-      required: true,
-      hasMany: true,
-    },
-    {
-      name: 'radioGroupExample',
-      label: 'Radio Group Example',
-      type: 'radio',
-      options: [{
-        value: 'option-1',
-        label: 'Options 1 Label',
-      }, {
-        value: 'option-2',
-        label: 'Option 2 Label',
-      }, {
-        value: 'option-3',
-        label: 'Option 3 Label',
-      }],
-      defaultValue: 'option-2',
-      required: true,
-    },
-    {
-      type: 'row',
-      fields: [
-        {
-          name: 'email',
-          label: 'Email',
-          type: 'email',
-        }, {
-          name: 'number',
-          label: 'Number',
-          type: 'number',
-        },
-      ],
-    },
-    {
-      type: 'group',
-      label: 'Group',
-      name: 'group',
-      fields: [
-        {
-          type: 'row',
-          fields: [
-            {
-              name: 'nestedText1',
-              label: 'Nested Text 1',
-              type: 'text',
-            }, {
-              name: 'nestedText2',
-              label: 'Nested Text 2',
-              type: 'text',
-            },
-          ],
-        },
-      ],
-    },
-    {
-      type: 'array',
-      label: 'Array',
-      name: 'array',
-      minRows: 2,
-      maxRows: 4,
-      fields: [
-        {
-          type: 'row',
-          fields: [
-            {
-              name: 'arrayText1',
-              label: 'Array Text 1',
-              type: 'text',
-              required: true,
-            }, {
-              name: 'arrayText2',
-              label: 'Array Text 2',
-              type: 'text',
-              required: true,
-              access: {
-                read: ({ req: { user } }) => Boolean(user),
-                update: ({ req: { user } }) => checkRole(['admin'], user),
-              },
-            },
-          ],
-        },
-        {
-          type: 'text',
-          name: 'arrayText3',
-          label: 'Array Text 3',
-          admin: {
-            readOnly: true,
-          },
-        },
-      ],
-    },
-    {
-      type: 'blocks',
-      label: 'Blocks Content',
-      name: 'blocks',
-      minRows: 2,
-      singularLabel: 'Block',
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      localized: true,
-      required: true,
-    },
-    {
-      type: 'relationship',
-      label: 'Relationship to One Collection',
-      name: 'relationship',
-      relationTo: 'conditions',
-    },
-    {
-      type: 'relationship',
-      label: 'Relationship hasMany',
-      name: 'relationshipHasMany',
-      relationTo: 'localized-posts',
-      hasMany: true,
-    },
-    {
-      type: 'relationship',
-      label: 'Relationship to Multiple Collections',
-      name: 'relationshipMultipleCollections',
-      relationTo: ['localized-posts', 'conditions'],
-    },
-    {
-      type: 'textarea',
-      label: 'Textarea',
-      name: 'textarea',
-    },
-    {
-      name: 'slug',
-      type: 'text',
-      label: 'Slug',
-      admin: {
-        position: 'sidebar',
-      },
-      localized: true,
-      unique: true,
-      required: true,
-    },
-    {
-      name: 'checkbox',
-      type: 'checkbox',
-      label: 'Checkbox',
-      admin: {
-        position: 'sidebar',
-      },
-    },
-  ],
-  timestamps: true,
-};
-
-module.exports = AllFields;

demo/collections/Blocks.js

@@ -1,26 +0,0 @@
-const Email = require('../blocks/Email');
-const Quote = require('../blocks/Quote');
-const NumberBlock = require('../blocks/Number');
-const CallToAction = require('../blocks/CallToAction');
-
-module.exports = {
-  slug: 'blocks',
-  labels: {
-    singular: 'Blocks',
-    plural: 'Blocks',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'layout',
-      label: 'Layout Blocks',
-      singularLabel: 'Block',
-      type: 'blocks',
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      localized: true,
-      required: true,
-    },
-  ],
-};

demo/collections/Code.js

@@ -1,17 +0,0 @@
-const Code = {
-  slug: 'code',
-  labels: {
-    singular: 'Code',
-    plural: 'Codes',
-  },
-  fields: [
-    {
-      name: 'code',
-      type: 'code',
-      label: 'Code',
-      required: true,
-    },
-  ],
-};
-
-module.exports = Code;

demo/collections/Conditions.js

@@ -1,53 +0,0 @@
-const Conditions = {
-  slug: 'conditions',
-  labels: {
-    singular: 'Conditions',
-    plural: 'Conditions',
-  },
-  fields: [
-    {
-      name: 'title',
-      type: 'text',
-      label: 'Title',
-      required: true,
-    },
-    {
-      name: 'enableTest',
-      type: 'checkbox',
-      label: 'Enable Test',
-    },
-    {
-      name: 'number',
-      type: 'number',
-      label: 'Number Field',
-    },
-    {
-      name: 'simpleCondition',
-      type: 'text',
-      label: 'Enable Test is checked',
-      required: true,
-      admin: {
-        condition: (_, siblings) => siblings.enableTest === true,
-      },
-    },
-    {
-      name: 'orCondition',
-      type: 'text',
-      label: 'Number is greater than 20 OR enableTest is checked',
-      required: true,
-      admin: {
-        condition: (_, siblings) => siblings.number > 20 || siblings.enableTest === true,
-      },
-    },
-    {
-      name: 'nestedConditions',
-      type: 'text',
-      label: 'Number is either greater than 20 AND enableTest is checked, OR number is less than 20 and enableTest is NOT checked',
-      admin: {
-        condition: (_, siblings) => (siblings.number > 20 && siblings.enableTest === true) || (siblings.number < 20 && siblings.enableTest === false),
-      },
-    },
-  ],
-};
-
-module.exports = Conditions;

demo/collections/CustomComponents/components/fields/Description/Cell/index.js

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const Cell = () => <div className="description">fake description cell</div>;
-
-export default Cell;

demo/collections/CustomComponents/components/fields/Description/Field/index.js

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const Description = () => <div className="description">fake description field</div>
-
-export default Description;

demo/collections/CustomComponents/components/fields/Description/Filter/index.js

@@ -1,26 +0,0 @@
-import React from 'react';
-import PropTypes from 'prop-types';
-
-import './index.scss';
-
-const Filter = ({ onChange, value }) => {
-  return (
-    <input
-      className="custom-description-filter"
-      type="text"
-      onChange={e => onChange(e.target.value)}
-      value={value}
-    />
-  );
-};
-
-Filter.defaultProps = {
-  value: '',
-};
-
-Filter.propTypes = {
-  onChange: PropTypes.func.isRequired,
-  value: PropTypes.string,
-};
-
-export default Filter;

demo/collections/CustomComponents/components/fields/Description/Filter/index.scss

@@ -1,3 +0,0 @@
-.custom-description-filter {
-  background: lightgray;
-}

demo/collections/CustomComponents/components/fields/Group/Field/index.js

@@ -1,21 +0,0 @@
-import React from 'react';
-import PropTypes from 'prop-types';
-import { Group } from '../../../../../../../field-types';
-
-const CustomGroup = (props) => {
-  return (
-    <div className="custom-group">
-      <Group {...props} />
-    </div>
-  );
-};
-
-CustomGroup.defaultProps = {
-  value: '',
-};
-
-CustomGroup.propTypes = {
-  value: PropTypes.string,
-};
-
-export default CustomGroup;

demo/collections/CustomComponents/components/fields/NestedArrayCustomField/Field/index.js

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const NestedArrayCustomField = () => <div className="nested-array-custom-field">Nested array custom field</div>;
-
-export default NestedArrayCustomField;

demo/collections/CustomComponents/components/fields/NestedGroupCustomField/Field/index.js

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const NestedGroupCustomField = () => <div className="nested-group-custom-field">Nested group custom field</div>;
-
-export default NestedGroupCustomField;

demo/collections/CustomComponents/components/fields/NestedText1/Field/index.js

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const NestedText1 = () => <div className="nested-text-1">Nested Text 1</div>;
-
-export default NestedText1;

demo/collections/CustomComponents/components/views/List/index.js

@@ -1,25 +0,0 @@
-import React from 'react';
-import PropTypes from 'prop-types';
-import DefaultList from '../../../../../../src/client/components/views/collections/List/Default';
-
-import './index.scss';
-
-const CustomListView = (props) => {
-  return (
-    <div className="custom-list">
-      <p>This is a custom Pages list view</p>
-      <p>Sup</p>
-      <DefaultList {...props} />
-    </div>
-  );
-};
-
-CustomListView.propTypes = {
-  collection: PropTypes.shape({
-    labels: PropTypes.shape({
-      plural: PropTypes.string,
-    }),
-  }).isRequired,
-};
-
-export default CustomListView;

demo/collections/CustomComponents/components/views/List/index.scss

@@ -1,5 +0,0 @@
-$color: purple;
-
-.custom-list {
-  color: $color;
-}

demo/collections/CustomComponents/index.js

@@ -1,102 +0,0 @@
-const path = require('path');
-
-module.exports = {
-  slug: 'custom-components',
-  labels: {
-    singular: 'Custom Component',
-    plural: 'Custom Components',
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-      unique: true,
-      localized: true,
-    },
-    {
-      name: 'description',
-      label: 'Description',
-      type: 'textarea',
-      height: 100,
-      required: true,
-      localized: true,
-      admin: {
-        components: {
-          field: path.resolve(__dirname, 'components/fields/Description/Field/index.js'),
-          cell: path.resolve(__dirname, 'components/fields/Description/Cell/index.js'),
-          filter: path.resolve(__dirname, 'components/fields/Description/Filter/index.js'),
-        },
-      },
-    },
-    {
-      name: 'array',
-      label: 'Array',
-      type: 'array',
-      fields: [
-        {
-          type: 'text',
-          name: 'nestedArrayCustomField',
-          label: 'Nested Array Custom Field',
-          admin: {
-            components: {
-              field: path.resolve(__dirname, 'components/fields/NestedArrayCustomField/Field/index.js'),
-            },
-          },
-        },
-      ],
-    },
-    {
-      name: 'group',
-      label: 'Group',
-      type: 'group',
-      admin: {
-        components: {
-          field: path.resolve(__dirname, 'components/fields/Group/Field/index.js'),
-        },
-      },
-      fields: [
-        {
-          type: 'text',
-          name: 'nestedGroupCustomField',
-          label: 'Nested Group Custom Field',
-          admin: {
-            components: {
-              field: path.resolve(__dirname, 'components/fields/NestedGroupCustomField/Field/index.js'),
-            },
-          },
-        },
-      ],
-    },
-    {
-      type: 'row',
-      fields: [
-        {
-          name: 'nestedText1',
-          label: 'Nested Text 1',
-          type: 'text',
-          admin: {
-            components: {
-              field: path.resolve(__dirname, 'components/fields/NestedText1/Field/index.js'),
-            },
-          },
-        }, {
-          name: 'nestedText2',
-          label: 'Nested Text 2',
-          type: 'text',
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-  admin: {
-    useAsTitle: 'title',
-    components: {
-      views: {
-        List: path.resolve(__dirname, 'components/views/List/index.js'),
-      },
-    },
-  },
-};

demo/collections/File.js

@@ -1,66 +0,0 @@
-const path = require('path');
-const checkRole = require('../access/checkRole');
-
-const access = ({ req: { user } }) => {
-  const isAdmin = checkRole(['admin'], user);
-
-  if (isAdmin) {
-    return true;
-  }
-
-  if (user) {
-    return {
-      owner: {
-        equals: user.id,
-      },
-    };
-  }
-};
-
-module.exports = {
-  slug: 'files',
-  labels: {
-    singular: 'File',
-    plural: 'Files',
-  },
-  upload: {
-    staticURL: '/files',
-    staticDir: path.resolve(__dirname, '../files'),
-  },
-  access: {
-    create: () => true,
-    read: access,
-    update: access,
-    delete: access,
-  },
-  fields: [
-    {
-      name: 'type',
-      label: 'Type',
-      type: 'select',
-      options: [{
-        value: 'Type 1',
-        label: 'Type 1 Label',
-      }, {
-        value: 'Type 2',
-        label: 'Type 2 Label',
-      }, {
-        value: 'Type 3',
-        label: 'Type 3 Label',
-      }],
-      defaultValue: 'Type 1',
-      required: true,
-    },
-    {
-      name: 'owner',
-      label: 'Owner',
-      type: 'relationship',
-      relationTo: 'admins',
-      required: true,
-    },
-  ],
-  timestamps: true,
-  admin: {
-    useAsTitle: 'filename',
-  },
-};

demo/collections/HiddenFields.js

@@ -1,31 +0,0 @@
-const HiddenFields = {
-  slug: 'hidden-fields',
-  labels: {
-    singular: 'Hidden Fields',
-    plural: 'Hidden Fields',
-  },
-  fields: [
-    {
-      name: 'title',
-      type: 'text',
-      label: 'Title - Not Hidden',
-      required: true,
-    },
-    {
-      name: 'hiddenAdmin',
-      type: 'text',
-      label: 'Hidden on Admin',
-      hidden: 'admin',
-      required: true,
-    },
-    {
-      name: 'hiddenAPI',
-      type: 'text',
-      label: 'Hidden on API',
-      hidden: true,
-      required: true, // this should not matter
-    },
-  ],
-};
-
-module.exports = HiddenFields;

demo/collections/Hooks.js

@@ -1,91 +0,0 @@
-/* eslint-disable no-param-reassign */
-module.exports = {
-  slug: 'hooks',
-  labels: {
-    singular: 'Hook',
-    plural: 'Hooks',
-  },
-  admin: {
-    useAsTitle: 'title',
-  },
-  access: {
-    create: () => true,
-    read: () => true,
-    update: () => true,
-    delete: () => true,
-  },
-  hooks: {
-    beforeRead: [
-      (operation) => {
-        if (operation.req.headers.hook === 'beforeRead') {
-          console.log('before reading Hooks document');
-        }
-      },
-    ],
-    beforeChange: [
-      (operation) => {
-        if (operation.req.headers.hook === 'beforeChange') {
-          operation.req.body.description += '-beforeChangeSuffix';
-        }
-        return operation.data;
-      },
-    ],
-    beforeDelete: [
-      (operation) => {
-        if (operation.req.headers.hook === 'beforeDelete') {
-          // TODO: Find a better hook operation to assert against in tests
-          operation.req.headers.hook = 'afterDelete';
-        }
-      },
-    ],
-    afterRead: [
-      (operation) => {
-        const { doc } = operation;
-        doc.afterReadHook = true;
-
-        return doc;
-      },
-    ],
-    afterChange: [
-      (operation) => {
-        if (operation.req.headers.hook === 'afterChange') {
-          operation.doc.afterChangeHook = true;
-        }
-        return operation.doc;
-      },
-    ],
-    afterDelete: [
-      (operation) => {
-        if (operation.req.headers.hook === 'afterDelete') {
-          operation.doc.afterDeleteHook = true;
-        }
-        return operation.doc;
-      },
-    ],
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-      unique: true,
-      localized: true,
-      hooks: {
-        afterRead: [
-          ({ value }) => (value ? value.toUpperCase() : null),
-        ],
-      },
-    },
-    {
-      name: 'description',
-      label: 'Description',
-      type: 'textarea',
-      height: 100,
-      required: true,
-      localized: true,
-    },
-  ],
-  timestamps: true,
-};

demo/collections/LocalOperations.js

@@ -1,31 +0,0 @@
-const LocalOperations = {
-  slug: 'local-operations',
-  labels: {
-    singular: 'Local Operation',
-    plural: 'Local Operations',
-  },
-  hooks: {
-    afterRead: [
-      async ({ req, doc }) => {
-        const formattedData = { ...doc };
-        const localizedPosts = await req.payload.find({
-          collection: 'localized-posts',
-        });
-
-        formattedData.localizedPosts = localizedPosts;
-
-        return formattedData;
-      },
-    ],
-  },
-  fields: [
-    {
-      name: 'title',
-      type: 'text',
-      label: 'title',
-      required: true,
-    },
-  ],
-};
-
-module.exports = LocalOperations;

demo/collections/Localized.js

@@ -1,52 +0,0 @@
-module.exports = {
-  slug: 'localized-posts',
-  labels: {
-    singular: 'Localized Post',
-    plural: 'Localized Posts',
-  },
-  admin: {
-    useAsTitle: 'title',
-    defaultColumns: [
-      'title',
-      'priority',
-      'createdAt',
-    ],
-  },
-  access: {
-    read: () => true,
-  },
-  preview: (doc, token) => {
-    if (doc && doc.title) {
-      return `http://localhost:3000/posts/${doc.title.value}?preview=true&token=${token}`;
-    }
-
-    return null;
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-      unique: true,
-      localized: true,
-    },
-    {
-      name: 'description',
-      label: 'Description',
-      type: 'textarea',
-      height: 100,
-      required: true,
-      localized: true,
-    },
-    {
-      name: 'priority',
-      label: 'Priority',
-      type: 'number',
-      required: true,
-      localized: true,
-    },
-  ],
-  timestamps: true,
-};

demo/collections/LocalizedArray.js

@@ -1,50 +0,0 @@
-const LocalizedArrays = {
-  slug: 'localized-arrays',
-  labels: {
-    singular: 'Localized Array',
-    plural: 'Localized Arrays',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      type: 'array',
-      label: 'Array',
-      name: 'array',
-      localized: true,
-      required: true,
-      minRows: 2,
-      maxRows: 4,
-      fields: [
-        {
-          type: 'row',
-          fields: [
-            {
-              name: 'arrayText1',
-              label: 'Array Text 1',
-              type: 'text',
-              required: true,
-            }, {
-              name: 'arrayText2',
-              label: 'Array Text 2',
-              type: 'text',
-              required: true,
-            },
-          ],
-        },
-        {
-          type: 'text',
-          name: 'arrayText3',
-          label: 'Array Text 3',
-          admin: {
-            readOnly: true,
-          },
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-};
-
-module.exports = LocalizedArrays;

demo/collections/Media.js

@@ -1,66 +0,0 @@
-const path = require('path');
-const checkRole = require('../access/checkRole');
-
-module.exports = {
-  slug: 'media',
-  labels: {
-    singular: 'Media',
-    plural: 'Media',
-  },
-  access: {
-    read: () => true,
-  },
-  upload: {
-    staticURL: '/media',
-    staticDir: path.resolve(__dirname, '../media'),
-    adminThumbnail: 'mobile',
-    imageSizes: [
-      {
-        name: 'tablet',
-        width: 640,
-        height: 480,
-        crop: 'left top',
-      },
-      {
-        name: 'mobile',
-        width: 320,
-        height: 240,
-        crop: 'left top',
-      },
-      {
-        name: 'icon',
-        width: 16,
-        height: 16,
-      },
-    ],
-  },
-  fields: [
-    {
-      name: 'alt',
-      label: 'Alt Text',
-      type: 'text',
-      required: true,
-      localized: true,
-      hooks: {
-        afterRead: [
-          ({ value }) => `${value} alt`,
-        ],
-      },
-    },
-    {
-      name: 'sizes',
-      fields: [
-        {
-          name: 'icon',
-          access: {
-            read: ({ req: { user } }) => {
-              const result = checkRole(['admin'], user);
-              return result;
-            },
-          },
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-};

demo/collections/NestedArrays.js

@@ -1,70 +0,0 @@
-const NestedArray = {
-  slug: 'nested-arrays',
-  labels: {
-    singular: 'Nested Array',
-    plural: 'Nested Arrays',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      type: 'array',
-      label: 'Array',
-      name: 'array',
-      labels: {
-        singular: 'Parent Row',
-        plural: 'Parent Rows',
-      },
-      required: true,
-      minRows: 2,
-      maxRows: 4,
-      fields: [
-        {
-          name: 'parentIdentifier',
-          label: 'Parent Identifier',
-          defaultValue: '',
-          type: 'text',
-          required: true,
-        },
-        {
-          type: 'array',
-          name: 'nestedArray',
-          labels: {
-            singular: 'Child Row',
-            plural: 'Child Rows',
-          },
-          required: true,
-          fields: [
-            {
-              name: 'childIdentifier',
-              label: 'Child Identifier',
-              type: 'text',
-              required: true,
-            },
-            {
-              type: 'array',
-              name: 'deeplyNestedArray',
-              labels: {
-                singular: 'Grandchild Row',
-                plural: 'Grandchild Rows',
-              },
-              required: true,
-              fields: [
-                {
-                  name: 'grandchildIdentifier',
-                  label: 'Grandchild Identifier',
-                  type: 'text',
-                  required: true,
-                },
-              ],
-            },
-          ],
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-};
-
-module.exports = NestedArray;

demo/collections/Preview.js

@@ -1,29 +0,0 @@
-module.exports = {
-  slug: 'previewable-post',
-  labels: {
-    singular: 'Previewable Post',
-    plural: 'Previewable Posts',
-  },
-  admin: {
-    useAsTitle: 'title',
-  },
-  preview: (doc, token) => {
-    if (doc.title) {
-      return `http://localhost:3000/previewable-posts/${doc.title.value}?preview=true&token=${token}`;
-    }
-
-    return null;
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-      unique: true,
-      localized: true,
-    },
-  ],
-  timestamps: true,
-};

demo/collections/PublicUsers.js

@@ -1,51 +0,0 @@
-const checkRole = require('../access/checkRole');
-
-const access = ({ req: { user } }) => checkRole(['admin'], user);
-
-module.exports = {
-  slug: 'public-users',
-  labels: {
-    singular: 'Public User',
-    plural: 'Public Users',
-  },
-  admin: {
-    useAsTitle: 'email',
-  },
-  access: {
-    admin: () => false,
-    create: () => true,
-    read: () => true,
-    update: ({ req: { user } }) => {
-      if (checkRole(['admin'], user)) {
-        return true;
-      }
-
-      if (user) {
-        return {
-          id: user.id,
-        };
-      }
-
-      return false;
-    },
-    delete: ({ req: { user } }) => checkRole(['admin'], user),
-  },
-  auth: {
-    tokenExpiration: 300,
-    secureCookie: process.env.NODE_ENV === 'production',
-  },
-  fields: [
-    {
-      name: 'adminOnly',
-      label: 'This field should only be readable and editable by Admins with "admin" role',
-      type: 'text',
-      defaultValue: 'test',
-      access: {
-        create: access,
-        read: access,
-        update: access,
-      },
-    },
-  ],
-  timestamps: true,
-};

demo/collections/RelationshipA.js

@@ -1,20 +0,0 @@
-module.exports = {
-  slug: 'relationship-a',
-  access: {
-    read: () => true,
-  },
-  labels: {
-    singular: 'Relationship A',
-    plural: 'Relationship A',
-  },
-  fields: [
-    {
-      name: 'post',
-      label: 'Post',
-      type: 'relationship',
-      relationTo: 'relationship-b',
-      localized: false,
-    },
-  ],
-  timestamps: true,
-};

demo/collections/RelationshipB.js

@@ -1,21 +0,0 @@
-module.exports = {
-  slug: 'relationship-b',
-  access: {
-    read: () => true,
-  },
-  labels: {
-    singular: 'Relationship B',
-    plural: 'Relationship B',
-  },
-  fields: [
-    {
-      name: 'post',
-      label: 'Post',
-      type: 'relationship',
-      relationTo: 'relationship-a',
-      localized: false,
-      hasMany: true,
-    },
-  ],
-  timestamps: true,
-};

demo/collections/RichText.js

@@ -1,19 +0,0 @@
-const RichText = {
-  slug: 'rich-text',
-  labels: {
-    singular: 'Rich Text',
-    plural: 'Rich Texts',
-  },
-  fields: [
-    {
-      name: 'richText',
-      type: 'richText',
-      label: 'Rich Text',
-      required: true,
-      disabledElements: [],
-      disabledMarks: [],
-    },
-  ],
-};
-
-module.exports = RichText;

demo/collections/StrictPolicies.js

@@ -1,73 +0,0 @@
-const checkRole = require('../access/checkRole');
-
-module.exports = {
-  slug: 'strict-access',
-  labels: {
-    singular: 'Strict Access',
-    plural: 'Strict Access',
-  },
-  admin: {
-    useAsTitle: 'email',
-  },
-  access: {
-    create: () => true,
-    read: ({ req: { user } }) => {
-      if (checkRole(['admin'], user)) {
-        return true;
-      }
-
-      if (user) {
-        return {
-          owner: {
-            equals: user.id,
-          },
-        };
-      }
-
-      return false;
-    },
-    update: ({ req: { user } }) => {
-      if (checkRole(['admin'], user)) {
-        return true;
-      }
-
-      if (user) {
-        return {
-          owner: {
-            equals: user.id,
-          },
-        };
-      }
-
-      return false;
-    },
-    delete: ({ req: { user } }) => checkRole(['admin'], user),
-  },
-  fields: [
-    {
-      name: 'address',
-      type: 'text',
-      label: 'Address',
-      required: true,
-    },
-    {
-      name: 'city',
-      type: 'text',
-      label: 'City',
-      required: true,
-    },
-    {
-      name: 'state',
-      type: 'text',
-      label: 'State',
-      required: true,
-    },
-    {
-      name: 'zip',
-      type: 'number',
-      label: 'ZIP Code',
-      required: true,
-    },
-  ],
-  timestamps: true,
-};

demo/collections/Validations.js

@@ -1,110 +0,0 @@
-module.exports = {
-  slug: 'validations',
-  labels: {
-    singular: 'Validation',
-    plural: 'Validations',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'text',
-      type: 'text',
-      label: 'Text',
-      required: true,
-      validate: (value) => {
-        const result = value === 'test';
-
-        if (!result) {
-          return 'The only accepted value of this field is "test".';
-        }
-
-        return true;
-      },
-    },
-    {
-      type: 'row',
-      fields: [
-        {
-          name: 'lessThan10',
-          label: 'Less than 10',
-          type: 'number',
-          required: true,
-          validate: (value) => {
-            const result = parseInt(value, 10) < 10;
-
-            if (!result) {
-              return 'The value of this field needs to be less than 10.';
-            }
-
-            return true;
-          },
-        }, {
-          name: 'greaterThan10LessThan50',
-          label: 'Greater than 10, Less than 50',
-          type: 'number',
-          required: true,
-          min: 10,
-          max: 50,
-        },
-      ],
-    },
-    {
-      type: 'array',
-      label: 'Should have at least 3 rows',
-      name: 'atLeast3Rows',
-      required: true,
-      validate: (value) => {
-        const result = value && value.length >= 3;
-
-        if (!result) {
-          return 'This array needs to have at least 3 rows.';
-        }
-
-        return true;
-      },
-      fields: [
-        {
-          type: 'number',
-          name: 'greaterThan30',
-          label: 'Number should be greater than 30',
-          required: true,
-          validate: (value) => {
-            const result = value > 30;
-
-            if (!result) {
-              return 'This value of this field needs to be greater than 30.';
-            }
-
-            return true;
-          },
-        },
-      ],
-    },
-    {
-      type: 'array',
-      label: 'Default array validation',
-      name: 'array',
-      required: true,
-      fields: [
-        {
-          type: 'number',
-          name: 'lessThan20',
-          label: 'Number should be less than 20',
-          required: true,
-          validate: (value) => {
-            const result = value < 30;
-
-            if (!result) {
-              return 'This value of this field needs to be less than 20.';
-            }
-
-            return true;
-          },
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-};

demo/globals/BlocksGlobal.js

@@ -1,21 +0,0 @@
-const checkRole = require('../access/checkRole');
-const Quote = require('../blocks/Quote');
-const CallToAction = require('../blocks/CallToAction');
-
-module.exports = {
-  slug: 'blocks-global',
-  label: 'Blocks Global',
-  access: {
-    update: ({ req: { user } }) => checkRole(['admin'], user),
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'blocks',
-      label: 'Blocks',
-      type: 'blocks',
-      blocks: [Quote, CallToAction],
-      localized: true,
-    },
-  ],
-};

demo/globals/GlobalWithStrictAccess.js

@@ -1,34 +0,0 @@
-const checkRole = require('../access/checkRole');
-
-module.exports = {
-  slug: 'global-with-access',
-  label: 'Global with Strict Access',
-  access: {
-    update: ({ req: { user } }) => checkRole(['admin'], user),
-    read: ({ req: { user } }) => checkRole(['admin'], user),
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Site Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-    },
-    {
-      name: 'relationship',
-      label: 'Test Relationship',
-      type: 'relationship',
-      relationTo: 'localized-posts',
-      hasMany: true,
-      required: true,
-    },
-    {
-      name: 'singleRelationship',
-      label: 'Test Single Relationship',
-      type: 'relationship',
-      relationTo: 'localized-posts',
-      required: true,
-    },
-  ],
-};

demo/globals/NavigationArray.js

@@ -1,27 +0,0 @@
-const checkRole = require('../access/checkRole');
-
-module.exports = {
-  slug: 'navigation-array',
-  label: 'Navigation Array',
-  access: {
-    update: ({ req: { user } }) => checkRole(['admin', 'user'], user),
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'array',
-      label: 'Array',
-      type: 'array',
-      localized: true,
-      fields: [{
-        name: 'text',
-        label: 'Text',
-        type: 'text',
-      }, {
-        name: 'textarea',
-        label: 'Textarea',
-        type: 'textarea',
-      }],
-    },
-  ],
-};

demo/payload.config.js

@@ -1,99 +0,0 @@
-const path = require('path');
-const Admin = require('./collections/Admin');
-const AllFields = require('./collections/AllFields');
-const Code = require('./collections/Code');
-const Conditions = require('./collections/Conditions');
-const CustomComponents = require('./collections/CustomComponents');
-const File = require('./collections/File');
-const Blocks = require('./collections/Blocks');
-const HiddenFields = require('./collections/HiddenFields');
-const Hooks = require('./collections/Hooks');
-const Localized = require('./collections/Localized');
-const LocalizedArray = require('./collections/LocalizedArray');
-const LocalOperations = require('./collections/LocalOperations');
-const Media = require('./collections/Media');
-const NestedArrays = require('./collections/NestedArrays');
-const Preview = require('./collections/Preview');
-const PublicUsers = require('./collections/PublicUsers');
-const RelationshipA = require('./collections/RelationshipA');
-const RelationshipB = require('./collections/RelationshipB');
-const RichText = require('./collections/RichText');
-const StrictPolicies = require('./collections/StrictPolicies');
-const Validations = require('./collections/Validations');
-
-const BlocksGlobal = require('./globals/BlocksGlobal');
-const NavigationArray = require('./globals/NavigationArray');
-const GlobalWithStrictAccess = require('./globals/GlobalWithStrictAccess');
-
-module.exports = {
-  admin: {
-    user: 'admins',
-    disable: false,
-    components: {
-      layout: {
-        // Sidebar: path.resolve(__dirname, 'client/components/layout/Sidebar/index.js'),
-      },
-    },
-  },
-  collections: [
-    Admin,
-    AllFields,
-    Code,
-    Conditions,
-    CustomComponents,
-    File,
-    Blocks,
-    HiddenFields,
-    Hooks,
-    Localized,
-    LocalizedArray,
-    LocalOperations,
-    Media,
-    NestedArrays,
-    Preview,
-    PublicUsers,
-    RelationshipA,
-    RelationshipB,
-    RichText,
-    StrictPolicies,
-    Validations,
-  ],
-  globals: [
-    NavigationArray,
-    GlobalWithStrictAccess,
-    BlocksGlobal,
-  ],
-  cookiePrefix: 'payload',
-  serverURL: 'http://localhost:3000',
-  cors: ['http://localhost', 'http://localhost:8080', 'http://localhost:8081'],
-  routes: {
-    api: '/api',
-    admin: '/admin',
-    graphQL: '/graphql',
-    graphQLPlayground: '/graphql-playground',
-  },
-  defaultDepth: 2,
-  compression: {},
-  paths: {
-    scss: path.resolve(__dirname, 'client/scss/overrides.scss'),
-  },
-  graphQL: {
-    mutations: {},
-    queries: {},
-  },
-  localization: {
-    locales: [
-      'en',
-      'es',
-    ],
-    defaultLocale: 'en',
-    fallback: true,
-  },
-  productionGraphQLPlayground: false,
-  hooks: {
-    afterError: () => {
-      console.error('global error config handler');
-    },
-  },
-  webpack: (config) => config,
-};

demo/server.js

@@ -1,55 +0,0 @@
-/* eslint-disable no-console */
-const express = require('express');
-const path = require('path');
-const payload = require('../src');
-const logger = require('../src/utilities/logger')();
-
-const expressApp = express();
-
-expressApp.use('/static', express.static(path.resolve(__dirname, 'client/static')));
-
-payload.init({
-  email: {
-    provider: 'mock',
-  },
-  secret: 'SECRET_KEY',
-  mongoURL: 'mongodb://localhost/payload',
-  express: expressApp,
-  onInit: () => {
-    logger.info('Payload is initialized');
-    // console.log('Payload is initialized');
-  },
-});
-
-const externalRouter = express.Router();
-
-externalRouter.use(payload.authenticate);
-
-externalRouter.get('/', (req, res) => {
-  if (req.user) {
-    return res.send(`Authenticated successfully as ${req.user.email}.`);
-  }
-
-  return res.send('Not authenticated');
-});
-
-expressApp.use('/external-route', externalRouter);
-
-exports.start = (cb) => {
-  const server = expressApp.listen(3000, async () => {
-    logger.info(`listening on ${3000}...`);
-    if (cb) cb();
-
-    const creds = await payload.getMockEmailCredentials();
-    logger.info(`Mock email account username: ${creds.user}`);
-    logger.info(`Mock email account password: ${creds.pass}`);
-    logger.info(`Log in to mock email provider at ${creds.web}`);
-  });
-
-  return server;
-};
-
-// when server.js is launched directly
-if (module.id === require.main.id) {
-  exports.start();
-}

docs/access-control/collections.mdx

@@ -0,0 +1,186 @@
+---
+title: Collection Access Control
+label: Collections
+order: 20
+desc: With Collection-level Access Control you can define which users can create, read, update or delete Collections.
+keywords: collections, access control, permissions, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+You can define Collection-level Access Control within each Collection's `access` property. All Access Control functions accept one `args` argument.
+
+## Available Controls
+
+| Function                | Allows/Denies Access                         |
+| ----------------------- | -------------------------------------------- |
+| **[`create`](#create)** | Used in the `create` operation               |
+| **[`read`](#read)**     | Used in the `find` and `findByID` operations |
+| **[`update`](#update)** | Used in the `update` operation               |
+| **[`delete`](#delete)** | Used in the `delete` operation               |
+
+#### Auth-enabled Controls
+
+If a Collection supports [`Authentication`](/docs/authentication/overview), the following Access Controls become available:
+
+| Function                | Allows/Denies Access                                           |
+| ----------------------- | -------------------------------------------------------------- |
+| **[`admin`](#admin)**   | Used to restrict access to the Payload Admin panel             |
+| **[`unlock`](#unlock)** | Used to restrict which users can access the `unlock` operation |
+
+**Example Collection config:**
+
+```ts
+import { CollectionConfig } from 'payload/types';
+
+export const Posts: CollectionConfig = {
+  slug: "posts",
+  // highlight-start
+  access: {
+    create: ({ req: { user } }) => { ... },
+    read: ({ req: { user } }) => { ... },
+    update: ({ req: { user } }) => { ... },
+    delete: ({ req: { user } }) => { ... },
+    admin: ({ req: { user } }) => { ... },
+  },
+  // highlight-end
+};
+```
+
+### Create
+
+Returns a boolean which allows/denies access to the `create` request.
+
+**Available argument properties:**
+
+| Option     | Description                                                                |
+| ---------- | -------------------------------------------------------------------------- |
+| **`req`**  | The Express `request` object containing the currently authenticated `user` |
+| **`data`** | The data passed to create the document with.                               |
+
+**Example:**
+
+```ts
+const PublicUsers = {
+  slug: 'public-users',
+  access: {
+    // highlight-start
+    // allow guest users to self-registration
+    create: () => true,
+    // highlight-end
+    ...
+  },
+  fields: [ ... ],
+}
+```
+
+### Read
+
+Read access functions can return a boolean result or optionally return a [query constraint](/docs/queries/overview) which limits the documents that are returned to only those that match the constraint you provide. This can be helpful to restrict users' access to only certain documents however you specify.
+
+**Available argument properties:**
+
+| Option    | Description                                                                |
+| --------- | -------------------------------------------------------------------------- |
+| **`req`** | The Express `request` object containing the currently authenticated `user` |
+| **`id`**  | `id` of document requested, if within `findByID`                           |
+
+**Example:**
+
+```ts
+import { Access } from 'payload/config'
+
+const canReadPage: Access = ({ req: { user } }) => {
+  // allow authenticated users
+  if (user) {
+    return true
+  }
+  // using a query constraint, guest users can access when a field named 'isPublic' is set to true
+  return {
+    // assumes we have a checkbox field named 'isPublic'
+    isPublic: {
+      equals: true,
+    },
+  }
+}
+```
+
+### Update
+
+Update access functions can return a boolean result or optionally return a [query constraint](/docs/queries/overview) to limit the document(s) that can be updated by the currently authenticated user. For example, returning a `query` from the `update` Access Control is helpful in cases where you would like to restrict a user to only being able to update the documents containing a `createdBy` relationship field equal to the user's ID.
+
+**Available argument properties:**
+
+| Option     | Description                                                                |
+| ---------- | -------------------------------------------------------------------------- |
+| **`req`**  | The Express `request` object containing the currently authenticated `user` |
+| **`id`**   | `id` of document requested to update                                       |
+| **`data`** | The data passed to update the document with                                |
+
+**Example:**
+
+```ts
+import { Access } from 'payload/config'
+
+const canUpdateUser: Access = ({ req: { user }, id }) => {
+  // allow users with a role of 'admin'
+  if (user.roles && user.roles.some((role) => role === 'admin')) {
+    return true
+  }
+  // allow any other users to update only oneself
+  return user.id === id
+}
+```
+
+### Delete
+
+Similarly to the Update function, returns a boolean or a [query constraint](/docs/queries/overview) to limit which documents can be deleted by which users.
+
+**Available argument properties:**
+
+| Option    | Description                                                                                         |
+| --------- | --------------------------------------------------------------------------------------------------- |
+| **`req`** | The Express `request` object with additional `user` property, which is the currently logged in user |
+| **`id`**  | `id` of document requested to delete                                                                |
+
+**Example:**
+
+```ts
+import { Access } from 'payload/config'
+
+const canDeleteCustomer: Access = async ({ req, id }) => {
+  if (!id) {
+    // allow the admin UI to show controls to delete since it is indeterminate without the id
+    return true
+  }
+  // query another collection using the id
+  const result = await req.payload.find({
+    collection: 'contracts',
+    limit: 0,
+    depth: 0,
+    where: {
+      customer: { equals: id },
+    },
+  })
+
+  return result.totalDocs === 0
+}
+```
+
+### Admin
+
+If the Collection is [used to access the Payload Admin panel](/docs/admin/overview#the-admin-user-collection), the `Admin` Access Control function determines whether or not the currently logged in user can access the admin UI.
+
+**Available argument properties:**
+
+| Option    | Description                                                                |
+| --------- | -------------------------------------------------------------------------- |
+| **`req`** | The Express `request` object containing the currently authenticated `user` |
+
+### Unlock
+
+Determines which users can [unlock](/docs/authentication/operations#unlock) other users who may be blocked from authenticating successfully due to [failing too many login attempts](/docs/authentication/config#options).
+
+**Available argument properties:**
+
+| Option    | Description                                                                |
+| --------- | -------------------------------------------------------------------------- |
+| **`req`** | The Express `request` object containing the currently authenticated `user` |

docs/access-control/fields.mdx

@@ -0,0 +1,81 @@
+---
+title: Field-level Access Control
+label: Fields
+order: 30
+desc: Field-level Access Control is specified within a field's config, and allows you to define which users can create, read or update Fields.
+keywords: fields, access control, permissions, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Field Access Control is specified with functions inside a field's config. All field-level Controls return a boolean value to allow or deny access for the specified operation. No field-level Access Controls support returning query constraints. All Access Control functions accept one `args` argument.
+
+## Available Controls
+
+| Function                | Purpose                                                                          |
+| ----------------------- | -------------------------------------------------------------------------------- |
+| **[`create`](#create)** | Allows or denies the ability to set a field's value when creating a new document |
+| **[`read`](#read)**     | Allows or denies the ability to read a field's value                             |
+| **[`update`](#update)** | Allows or denies the ability to update a field's value                           |
+
+**Example Collection config:**
+
+```ts
+import { CollectionConfig } from 'payload/types';
+
+export const Posts: CollectionConfig = {
+  slug: 'posts',
+  fields: [
+    {
+      name: 'title',
+      type: 'text',
+      // highlight-start
+      access: {
+        create: ({ req: { user } }) => { ... },
+        read: ({ req: { user } }) => { ... },
+        update: ({ req: { user } }) => { ... },
+      },
+      // highlight-end
+    };
+  ],
+};
+```
+
+### Create
+
+Returns a boolean which allows or denies the ability to set a field's value when creating a new document. If `false` is returned, any passed values will be discarded.
+
+**Available argument properties:**
+
+| Option            | Description                                                                |
+| ----------------- | -------------------------------------------------------------------------- |
+| **`req`**         | The Express `request` object containing the currently authenticated `user` |
+| **`data`**        | The full data passed to create the document.                               |
+| **`siblingData`** | Immediately adjacent field data passed to create the document.             |
+
+### Read
+
+Returns a boolean which allows or denies the ability to read a field's value. If `false`, the entire property is omitted from the resulting document.
+
+**Available argument properties:**
+
+| Option            | Description                                                                |
+| ----------------- | -------------------------------------------------------------------------- |
+| **`req`**         | The Express `request` object containing the currently authenticated `user` |
+| **`id`**          | `id` of the document being read                                            |
+| **`doc`**         | The full document data.                                                    |
+| **`siblingData`** | Immediately adjacent field data of the document being read.                |
+
+### Update
+
+Returns a boolean which allows or denies the ability to update a field's value. If `false` is returned, any passed values will be discarded.
+
+If `false` is returned and you attempt to update the field's value, the operation will **not** throw an error however the field will be omitted from the update operation and the value will remain unchanged.
+
+**Available argument properties:**
+
+| Option            | Description                                                                |
+| ----------------- | -------------------------------------------------------------------------- |
+| **`req`**         | The Express `request` object containing the currently authenticated `user` |
+| **`id`**          | `id` of the document being updated                                         |
+| **`data`**        | The full data passed to update the document.                               |
+| **`siblingData`** | Immediately adjacent field data passed to update the document with.        |
+| **`doc`**         | The full document data, before the update is applied.                      |

docs/access-control/globals.mdx

@@ -0,0 +1,61 @@
+---
+title: Globals Access Control
+label: Globals
+order: 40
+desc: Global-level Access Control is specified within each Global's `access` property and allows you to define which users can read or update Globals.
+keywords: globals, access control, permissions, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+You can define Global-level Access Control within each Global's `access` property. All Access Control functions accept one `args` argument.
+
+\*\*Available argument properties:
+
+## Available Controls
+
+| Function                | Allows/Denies Access                   |
+| ----------------------- | -------------------------------------- |
+| **[`read`](#read)**     | Used in the `findOne` Global operation |
+| **[`update`](#update)** | Used in the `update` Global operation  |
+
+**Example Global config:**
+
+```ts
+import { GlobalConfig } from 'payload/types'
+
+const Header: GlobalConfig = {
+  slug: 'header',
+  // highlight-start
+  access: {
+    read: ({ req: { user } }) => {
+      /* */
+    },
+    update: ({ req: { user } }) => {
+      /* */
+    },
+  },
+  // highlight-end
+}
+
+export default Header
+```
+
+### Read
+
+Returns a boolean result or optionally a [query constraint](/docs/queries/overview) which limits who can read this global based on its current properties.
+
+**Available argument properties:**
+
+| Option    | Description                                                                |
+| --------- | -------------------------------------------------------------------------- |
+| **`req`** | The Express `request` object containing the currently authenticated `user` |
+
+### Update
+
+Returns a boolean result or optionally a [query constraint](/docs/queries/overview) which limits who can update this global based on its current properties.
+
+**Available argument properties:**
+
+| Option     | Description                                                                |
+| ---------- | -------------------------------------------------------------------------- |
+| **`req`**  | The Express `request` object containing the currently authenticated `user` |
+| **`data`** | The data passed to update the global with.                                 |

docs/access-control/overview.mdx

@@ -0,0 +1,83 @@
+---
+title: Access Control
+label: Overview
+order: 10
+desc: Payload makes it simple to define and manage access control. By declaring roles, you can set permissions and restrict what your users can interact with.
+keywords: overview, access control, permissions, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Access control within Payload is extremely powerful while remaining easy and intuitive to manage. Declaring who should have access to what documents is no more complex than writing a simple JavaScript function that either returns a `boolean` or a [`query`](/docs/queries/overview) constraint to restrict which documents users can interact with.
+
+<YouTube id="DoPLyXG26Dg" title="Overview of Payload Access Control" />
+
+**Example use cases:**
+
+- Allowing anyone `read` access to all `Post`s
+- Only allowing public access to `Post`s where a `status` field is equal to `published`
+- Giving only `User`s with a `role` field equal to `admin` the ability to delete `Page`(s)
+- Allowing anyone to create `ContactSubmission`s, but only logged in users to `read`, `update` or `delete` them
+- Restricting a `User` to only be able to see their own `Order`(s), but no others
+- Allowing `User`s that belong to a certain `Organization` to access only that `Organization`'s `Resource`s
+
+### Default Settings
+
+**By default, all Collections and Globals require that a user is logged in to be able to interact in any way.** The default Access Control function evaluates the `user` from the Express `req` and returns `true` if a user is logged in, and `false` if not.
+
+**Default Access function:**
+
+```ts
+const defaultPayloadAccess = ({ req: { user } }) => {
+  // Return `true` if a user is found
+  // and `false` if it is undefined or null
+  return Boolean(user)
+}
+```
+
+<Banner type="success">
+  <strong>Note:</strong>
+  <br />
+  In the Local API, all Access Control functions are skipped by default, allowing your server to do
+  whatever it needs. But, you can opt back in by setting the option <strong>
+    overrideAccess
+  </strong>{' '}
+  to <strong>false</strong>.
+</Banner>
+
+### Access Control Types
+
+You can manage access within Payload on three different levels:
+
+- [Collections](/docs/access-control/collections)
+- [Fields](/docs/access-control/fields)
+- [Globals](/docs/access-control/globals)
+
+### When Access Control is Executed
+
+<Banner type="success">
+  <strong>Note:</strong>
+  <br />
+  Access control functions are utilized in two places. It's important to understand how and when
+  your access control is executed.
+</Banner>
+
+#### As you execute operations
+
+When you perform Payload operations like `create`, `read`, `update`, and `delete`, your access control functions will be executed before any changes or operations are completed.
+
+#### Within the Admin UI
+
+The Payload Admin UI responds dynamically to the access control that you define. For example, if you restrict editing a `ExampleCollection` to only users that feature a `role` of `admin`, the Payload Admin UI will **hide** the `ExampleCollection` from the Admin UI entirely. This is super powerful and allows you to control who can do what with your Admin UI.
+
+To accomplish this, Payload ships with an `Access` operation, which is executed when a user logs into the Admin UI. Payload will execute each one of your access control functions, across all collections, globals, and fields, at the top level and return a response that contains a reflection of what the currently authenticated user can do with your application.
+
+### Argument Availability
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  When your access control functions are executed via the <strong>access</strong> operation, the{' '}
+  <strong>id</strong> and <strong>data</strong> arguments will be <strong>undefined</strong>,
+  because Payload is executing your functions without referencing a specific document.
+</Banner>
+
+If you use `id` or `data` within your access control functions, make sure to check that they are defined first. If they are not, then you can assume that your access control is being executed via the `access` operation, to determine solely what the user can do within the Admin UI.

docs/admin/bundlers.mdx

@@ -0,0 +1,54 @@
+---
+title: Bundlers
+label: Bundlers
+order: 60
+desc: Bundlers are used to bundle the code that serves Payload's Admin Panel.
+---
+
+Payload has two official bundlers, the [Webpack Bundler](/docs/admin/webpack) and the [Vite Bundler](/docs/admin/vite). You must install a bundler to use the admin panel.
+
+##### Install a bundler
+
+Webpack (recommended):
+
+```text
+yarn add @payloadcms/bundler-webpack
+```
+
+Vite (beta):
+
+```text
+yarn add @payloadcms/bundler-vite
+```
+
+##### Configure the bundler
+
+```ts
+// payload.config.ts
+
+import { buildConfig } from 'payload/config'
+import { webpackBundler } from '@payloadcms/bundler-webpack'
+// import { viteBundler } from '@payloadcms/bundler-vite'
+
+export default buildConfig({
+  // highlight-start
+  admin: {
+    bundler: webpackBundler() // or viteBundler()
+  },
+  // highlight-end
+})
+```
+
+### What are bundlers?
+
+At their core, a bundler's main goal is to take a bunch of files and turn them into a few optimized files that you ship to the browser. The admin UI has a root `index.html` entry point, and from there the bundler traverses the dependency tree, bundling all of the files that are required from that point on.
+
+Since the bundled file is sent to the browser, it can't include any server-only code. You will need to remove any server-only code from your admin UI before bundling it. You can learn more about [excluding server code](/docs/admin/excluding-server-code) section.
+
+<Banner type="warning">
+  <strong>Using environment variables in the admin UI</strong>
+  <br />
+  Bundles should not contain sensitive information. By default, Payload
+  excludes env variables from the bundle. If you need to use env variables in your payload config,
+  you need to prefix them with `PAYLOAD_PUBLIC_` to make them available to the client-side code.
+</Banner>

docs/admin/components.mdx

@@ -0,0 +1,544 @@
+---
+title: Swap in your own React components
+label: Custom Components
+order: 20
+desc: Fully customize your Admin Panel by swapping in your own React components. Add fields, remove views, update routes and change functions to sculpt your perfect Dashboard.
+keywords: admin, components, custom, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+While designing the Payload Admin panel, we determined it should be as minimal and straightforward as possible to allow easy customization and control. There are many times where you may want to completely control how a whole view or a field works. You might even want to add in new views entirely. In order for Payload to support this level of customization without introducing versioning / future-proofing issues, Payload provides for a pattern to supply your own React components via your Payload config.
+
+To swap in your own React component, first, consult the list of available component overrides below. Determine the scope that corresponds to what you are trying to accomplish, and then author your React component accordingly.
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  Custom components will automatically be provided with all props that the default component normally
+  accepts.
+</Banner>
+
+### Base Component Overrides
+
+You can override a set of admin panel-wide components by providing a component to your base Payload config's `admin.components` property. The following options are available:
+
+| Path                  | Description                                                                                                                                                                                                 |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`Nav`**             | Contains the sidebar / mobile menu in its entirety.                                                                                                                                                         |
+| **`BeforeNavLinks`**  | Array of components to inject into the built-in Nav, _before_ the links themselves.                                                                                                                         |
+| **`AfterNavLinks`**   | Array of components to inject into the built-in Nav, _after_ the links.                                                                                                                                     |
+| **`BeforeDashboard`** | Array of components to inject into the built-in Dashboard, _before_ the default dashboard contents.                                                                                                         |
+| **`AfterDashboard`**  | Array of components to inject into the built-in Dashboard, _after_ the default dashboard contents. [Demo](https://github.com/payloadcms/payload/tree/main/test/admin/components/AfterDashboard/index.tsx) |
+| **`BeforeLogin`**     | Array of components to inject into the built-in Login, _before_ the default login form.                                                                                                                     |
+| **`AfterLogin`**      | Array of components to inject into the built-in Login, _after_ the default login form.                                                                                                                      |
+| **`logout.Button`**   | A custom React component.                                                                                                                                                                                   |
+| **`graphics.Icon`**   | Used as a graphic within the `Nav` component. Often represents a condensed version of a full logo.                                                                                                          |
+| **`graphics.Logo`**   | The full logo to be used in contexts like the `Login` view.                                                                                                                                                 |
+| **`providers`**       | Define your own provider components that will wrap the Payload Admin UI. [More](#custom-providers)                                                                                                          |
+| **`views`**           | Override or create new views within the Payload Admin UI. [More](#views)                                                                                                                             |
+
+Here is a full example showing how to swap some of these components for your own.
+
+`payload.config.js`
+
+```ts
+import { buildConfig } from 'payload/config'
+
+import {
+  MyCustomNav,
+  MyCustomLogo,
+  MyCustomIcon,
+  MyCustomAccount,
+  MyCustomDashboard,
+  MyProvider,
+} from './customComponents'
+
+export default buildConfig({
+  admin: {
+    components: {
+      Nav: MyCustomNav,
+      graphics: {
+        Icon: MyCustomIcon,
+        Logo: MyCustomLogo,
+      },
+      views: {
+        Account: MyCustomAccount,
+        Dashboard: MyCustomDashboard,
+      },
+      providers: [MyProvider],
+    },
+  },
+})
+```
+
+#### Views
+
+You can easily swap entire views with your own by using the `admin.components.views` property. At the root level, Payload renders the following views dy default, all of which can be overridden:
+
+| Property           | Description                                                                                                                  |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| **`Account`**      | The Account view is used to show the currently logged in user's Account page.                                                |
+| **`Dashboard`**    | The main landing page of the Admin panel.                                                                                    |
+
+To swap out any of these views, simply pass in your custom component to the `admin.components.views` property of your Payload config. For example:
+
+```ts
+// payload.config.ts
+{
+  // ...
+  admin: {
+    components: {
+      views: {
+        Account: MyCustomAccountView,
+        Dashboard: MyCustomDashboardView,
+      },
+    },
+  },
+}
+```
+
+For more granular control, pass a configuration object instead. Payload exposes all of the properties of `<Route />` component in [React Router v5](https://v5.reactrouter.com):
+
+| Property           | Description                                                                                                                  |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| **`Component`** \* | Pass in the component that should be rendered when a user navigates to this route.                                           |
+| **`path`** \*      | React Router `path`. [See the React Router docs](https://v5.reactrouter.com/web/api/Route/path-string-string) for more info. |
+| **`exact`**        | React Router `exact` property. [More](https://v5.reactrouter.com/web/api/Route/exact-bool)                                   |
+| **`strict`**       | React Router `strict` property. [More](https://v5.reactrouter.com/web/api/Route/strict-bool)                                 |
+| **`sensitive`**    | React Router `sensitive` property. [More](https://v5.reactrouter.com/web/api/Route/sensitive-bool)                           |
+
+_\* An asterisk denotes that a property is required._
+
+#### Adding new views
+
+To add a _new_ view to the Admin Panel, simply add another key to the `views` object with at least a `path` and `Component` property. For example:
+
+```ts
+// payload.config.ts
+{
+  // ...
+  admin: {
+    components: {
+      views: {
+        MyCustomView: {
+          Component: MyCustomView,
+          path: '/my-custom-view',
+        },
+      },
+    },
+  },
+}
+```
+
+_For more examples regarding how to customize components, look at the following [examples](https://github.com/payloadcms/payload/tree/master/test/admin/components)._
+
+For help on how to build your own custom view components, see [building a custom view component](#building-a-custom-view-component).
+
+### Collections
+
+You can override components on a collection-by-collection basis via their `admin` property.
+
+| Path                       | Description                                                                                                            |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| **`BeforeList`**           | Array of components to inject _before_ the built-in List view                                                          |
+| **`BeforeListTable`**      | Array of components to inject _before_ the built-in List view's table                                                  |
+| **`AfterList`**            | Array of components to inject _after_ the built-in List view                                                           |
+| **`AfterListTable`**       | Array of components to inject _after_ the built-in List view's table                                                   |
+| **`edit.SaveButton`**      | Replace the default `Save` button with a custom component. Drafts must be disabled                                     |
+| **`edit.SaveDraftButton`** | Replace the default `Save Draft` button with a custom component. Drafts must be enabled and autosave must be disabled. |
+| **`edit.PublishButton`**   | Replace the default `Publish` button with a custom component. Drafts must be enabled.                                  |
+| **`edit.PreviewButton`**   | Replace the default `Preview` button with a custom component.                                                          |
+| **`views`**                | Override or create new views within the Payload Admin UI. [More](#collection-views)                                    |
+
+Here is a full example showing how to swap some of these components for your own:
+
+`Collection.ts`
+
+```tsx
+import * as React from 'react'
+
+import {
+  CustomSaveButtonProps,
+  CustomSaveDraftButtonProps,
+  CustomPublishButtonProps,
+  CustomPreviewButtonProps,
+} from 'payload/types'
+
+export const CustomSaveButton: CustomSaveButtonProps = ({ DefaultButton, label }) => {
+  return <DefaultButton label={label} />
+}
+
+export const CustomSaveDraftButton: CustomSaveDraftButtonProps = ({
+  DefaultButton,
+  disabled,
+  label,
+  saveDraft,
+}) => {
+  return <DefaultButton label={label} disabled={disabled} saveDraft={saveDraft} />
+}
+
+export const CustomPublishButton: CustomPublishButtonProps = ({
+  DefaultButton,
+  disabled,
+  label,
+  publish,
+}) => {
+  return <DefaultButton label={label} disabled={disabled} publish={publish} />
+}
+
+export const CustomPreviewButton: CustomPreviewButtonProps = ({
+  DefaultButton,
+  disabled,
+  label,
+  preview,
+}) => {
+  return <DefaultButton label={label} disabled={disabled} preview={preview} />
+}
+
+export const MyCollection: SanitizedCollectionConfig = {
+  slug: 'my-collection',
+  admin: {
+    components: {
+      edit: {
+        SaveButton: CustomSaveButton,
+        SaveDraftButton: CustomSaveDraftButton,
+        PublishButton: CustomPublishButton,
+        PreviewButton: CustomPreviewButton,
+      },
+    },
+  }
+}
+```
+
+#### Collection views
+
+To swap out entire views on collections, you can use the `admin.components.views` property on the collection's config. Payload renders the following views dy default, all of which can be overridden:
+
+| Property           | Description                                                                                                                  |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| **`Edit`**         | The Edit view is used to edit a single document for a given collection.                                                      |
+| **`List`**         | The List view is used to show a list of documents for a given collection.                                                    |
+
+To swap out any of these views, simply pass in your custom component to the `admin.components.views` property of your Payload config. This will replace the entire view, including the page breadcrumbs, title, tabs, etc, _as well as all nested routes_.
+
+```ts
+// Collection.ts
+{
+  // ...
+  admin: {
+    components: {
+      views: {
+        Edit: MyCustomEditView,
+        List: MyCustomListView,
+      },
+    },
+  },
+}
+```
+
+_For help on how to build your own custom view components, see [building a custom view component](#building-a-custom-view-component)._
+
+To swap specific _nested_ views within the parent `Edit` view, you can use the `admin.components.views.Edit` property on the globals's config. This will only replace the nested view, leaving the page breadcrumbs, title, tabs, etc intact.
+
+```ts
+// Collection.ts
+{
+  // ...
+  admin: {
+    components: {
+      views: {
+        Edit: {
+          Default: MyCustomDefaultTab,
+        },
+      },
+    },
+  },
+}
+```
+
+You can also add _new_ tabs to the `Edit` view by adding another key to the `components.views.Edit[key]` object with a `path` and `Component` property. See [Custom Tabs](#custom-tabs) for more information.
+
+### Globals
+
+As with Collections, you can override components on a global-by-global basis via their `admin` property.
+
+| Path                       | Description                                                                                                            |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| **`edit.SaveButton`**      | Replace the default `Save` button with a custom component. Drafts must be disabled                                     |
+| **`edit.SaveDraftButton`** | Replace the default `Save Draft` button with a custom component. Drafts must be enabled and autosave must be disabled. |
+| **`edit.PublishButton`**   | Replace the default `Publish` button with a custom component. Drafts must be enabled.                                  |
+| **`edit.PreviewButton`**   | Replace the default `Preview` button with a custom component.                                                          |
+| **`views`**                | Override or create new views within the Payload Admin UI. [More](#global-views)                                        |
+
+#### Global views
+
+To swap out views for globals, you can use the `admin.components.views` property on the global's config. Payload renders the following views dy default, all of which can be overridden:
+
+| Property           | Description                                                                                                                  |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| **`Edit`**         | The Edit view is used to edit a single document for a given Global.                                                          |
+
+To swap out any of these views, simply pass in your custom component to the `admin.components.views` property of your Payload config. This will replace the entire view, including the page breadcrumbs, title, and tabs, _as well as all nested views_.
+
+```ts
+// Global.ts
+{
+  // ...
+  admin: {
+    components: {
+      views: {
+        Edit: MyCustomEditView,
+      },
+    },
+  },
+}
+```
+
+_For help on how to build your own custom view components, see [building a custom view component](#building-a-custom-view-component)._
+
+To swap specific _nested_ views within the parent `Edit` view, you can use the `admin.components.views.Edit` property on the globals's config. This will only replace the nested view, leaving the page breadcrumbs, title, and tabs intact.
+
+```ts
+// Global.ts
+{
+  // ...
+  admin: {
+    components: {
+      views: {
+        Edit: {
+          Default: MyCustomDefaultTab,
+        },
+      },
+    },
+  },
+}
+```
+
+You can also add _new_ tabs to the `Edit` view by adding another key to the `components.views.Edit[key]` object with a `path` and `Component` property. See [Custom Tabs](#custom-tabs) for more information.
+
+### Custom Tabs
+
+You can easily swap individual collection or global edit views. To do this, pass an _object_ to the `admin.components.views.Edit` property of the config. Payload renders the following views dy default, all of which can be overridden:
+
+| Property           | Description                                                                                                                  |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| **`Default`**      | The Default view is the primary view in which your document is edited.                                                       |
+| **`Versions`**     | The Versions view is used to view the version history of a single document. [More details](../versions)                      |
+| **`Version`**      | The Version view is used to view a single version of a single document for a given collection. [More details](../versions).  |
+| **`API`**          | The API view is used to display the REST API JSON response for a given document.                                             |
+| **`LivePreview`**  | The LivePreview view is used to display the Live Preview interface. [More details](../live-preview)                          |
+
+Here is an example:
+
+```ts
+// Collection.ts or Global.ts
+export const MyCollection: SanitizedCollectionConfig = {
+  slug: 'my-collection',
+  admin: {
+    components: {
+      views: {
+        Edit: { // You can also define `components.views.Edit` as a component, this will override _all_ nested views
+          Default: MyCustomDefaultTab,
+          Versions: MyCustomVersionsTab,
+          Version: MyCustomVersionTab,
+          API: MyCustomAPITab,
+          LivePreview: MyCustomLivePreviewTab,
+        },
+      },
+    },
+  },
+}
+```
+
+To add a _new_ tab to the `Edit` view, simply add another key to `components.views.Edit[key]` with at least a `path` and `Component` property. For example:
+
+```ts
+// `Collection.ts` or `Global.ts`
+export const MyCollection: SanitizedCollectionConfig = {
+  slug: 'my-collection',
+  admin: {
+    components: {
+      views: {
+        Edit: {
+          MyCustomTab: {
+            Component: MyCustomTab,
+            path: '/my-custom-tab',
+            // You an swap the entire tab component out for your own
+            Tab: MyCustomTab
+          },
+          AnotherCustomView: {
+            Component: AnotherCustomView,
+            path: '/another-custom-view',
+            // Or you can use the default tab component and just pass in your own label and href
+            Tab: {
+              label: 'Another Custom View',
+              href: '/another-custom-view',
+            }
+          },
+        },
+      },
+    },
+  },
+}
+```
+
+### Building a custom view component
+
+Your custom view components will be given all the props that a React Router `<Route />` typically would receive, as well as two props from Payload:
+
+| Prop                    | Description                                                                  |
+| ----------------------- | ---------------------------------------------------------------------------- |
+| **`user`**              | The currently logged in user. Will be `null` if no user is logged in.        |
+| **`canAccessAdmin`** \* | If the currently logged in user is allowed to access the admin panel or not. |
+
+<Banner type="warning">
+  <strong>Note:</strong>
+  <br />
+  It's up to you to secure your custom views. If your view requires a user to be logged in or to
+  have certain access rights, you should handle that within your view component yourself.
+</Banner>
+
+#### Example
+
+You can find examples of custom views in the [Payload source code `/test/admin/components/views` folder](https://github.com/payloadcms/payload/tree/master/test/admin/components/views). There, you'll find two custom views:
+
+1. A custom view that uses the `DefaultTemplate`, which is the built-in Payload template that displays the sidebar and "eyebrow nav"
+1. A custom view that uses the `MinimalTemplate` - which is just a centered template used for things like logging in or out
+
+To see how to pass in your custom views to create custom views of your own, take a look at the `admin.components.views` property of the [Payload test admin config](https://github.com/payloadcms/payload/blob/master/test/admin/config.ts).
+
+### Fields
+
+All Payload fields support the ability to swap in your own React components. So, for example, instead of rendering a default Text input, you might need to render a color picker that provides the editor with a custom color picker interface to restrict the data entered to colors only.
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  Don't see a built-in field type that you need? Build it! Using a combination of custom validation
+  and custom components, you can override the entirety of how a component functions within the admin
+  panel and effectively create your own field type.
+</Banner>
+
+**Fields support the following custom components:**
+
+| Component    | Description                                                                                                                 |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------- |
+| **`Filter`** | Override the text input that is presented in the `List` view when a user is filtering documents by the customized field.    |
+| **`Cell`**   | Used in the `List` view's table to represent a table-based preview of the data stored in the field. [More](#cell-component) |
+| **`Field`**  | Swap out the field itself within all `Edit` views. [More](#field-component)                                                 |
+
+## Cell Component
+
+These are the props that will be passed to your custom Cell to use in your own components.
+
+| Property         | Description                                                       |
+| ---------------- | ----------------------------------------------------------------- |
+| **`field`**      | An object that includes the field configuration.                  |
+| **`colIndex`**   | A unique number for the column in the list.                       |
+| **`collection`** | An object with the config of the collection that the field is in. |
+| **`cellData`**   | The data for the field that the cell represents.                  |
+| **`rowData`**    | An object with all the field values for the row.                  |
+
+#### Example
+
+```tsx
+import React from 'react'
+import './index.scss'
+const baseClass = 'custom-cell'
+
+const CustomCell: React.FC<Props> = (props) => {
+  const { field, colIndex, collection, cellData, rowData } = props
+
+  return <span className={baseClass}>{cellData}</span>
+}
+```
+
+## Field Component
+
+When writing your own custom components you can make use of a number of hooks to set data, get reactive changes to other fields, get the id of the document or interact with a context from a custom provider.
+
+### Sending and receiving values from the form
+
+When swapping out the `Field` component, you'll be responsible for sending and receiving the field's `value` from the form itself. To do so, import the `useField` hook as follows:
+
+```tsx
+import { useField } from 'payload/components/forms'
+
+type Props = { path: string }
+
+const CustomTextField: React.FC<Props> = ({ path }) => {
+  // highlight-start
+  const { value, setValue } = useField<Props>({ path })
+  // highlight-end
+
+  return <input onChange={(e) => setValue(e.target.value)} value={value.path} />
+}
+```
+
+<Banner type="success">
+  For more information regarding the hooks that are available to you while you build custom
+  components, including the <strong>useField</strong> hook, [click here](/docs/admin/hooks).
+</Banner>
+
+## Custom providers
+
+As your admin customizations gets more complex you may want to share state between fields or other components. You can add custom providers to do add your own context to any Payload app for use in other custom components within the admin panel. Within your config add `admin.components.providers`, these can be used to share context or provide other custom functionality. Read the [React context](https://reactjs.org/docs/context.html) docs to learn more.
+
+<Banner type="warning">
+  <strong>Reminder:</strong> Don't forget to pass the **children** prop through the provider
+  component for the admin UI to show
+</Banner>
+
+### Styling Custom Components
+
+Payload exports its SCSS variables and mixins for reuse in your own custom components. This is helpful in cases where you might want to style a custom input similarly to Payload's built-ini styling, so it blends more thoroughly into the existing admin UI.
+
+To make use of Payload SCSS variables / mixins to use directly in your own components, you can import them as follows:
+
+```
+@import '~payload/scss';
+```
+
+### Getting the current language
+
+When developing custom components you can support multiple languages to be consistent with Payload's i18n support. The best way to do this is to add your translation resources to the [i18n configuration](https://payloadcms.com/docs/configuration/i18n) and import `useTranslation` from `react-i18next` in your components.
+
+For example:
+
+```tsx
+import { useTranslation } from 'react-i18next'
+
+const CustomComponent: React.FC = () => {
+  // highlight-start
+  const { t, i18n } = useTranslation('namespace1')
+  // highlight-end
+
+  return (
+    <ul>
+      <li>{t('key', { variable: 'value' })}</li>
+      <li>{t('namespace2:key', { variable: 'value' })}</li>
+      <li>{i18n.language}</li>
+    </ul>
+  )
+}
+```
+
+### Getting the current locale
+
+In any custom component you can get the selected locale with `useLocale` hook. `useLocale` returns the full locale object, consisting of a `label`, `rtl`(right-to-left) property, and then `code`. Here is a simple example:
+
+```tsx
+import { useLocale } from 'payload/components/utilities'
+
+const Greeting: React.FC = () => {
+  // highlight-start
+  const locale = useLocale()
+  // highlight-end
+
+  const trans = {
+    en: 'Hello',
+    es: 'Hola',
+  }
+
+  return <span> {trans[locale.code]} </span>
+}
+```

docs/admin/customizing-css.mdx

@@ -0,0 +1,51 @@
+---
+title: Customizing CSS & SCSS
+label: Customizing CSS
+order: 40
+desc: Customize your Payload admin panel further by adding your own CSS or SCSS style sheet to the configuration, powerful theme and design options are waiting for you.
+keywords: admin, css, scss, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+### Adding your own CSS / SCSS
+
+You can add your own CSS by providing your base Payload config with a path to your own CSS or SCSS. Customize the styling of any part of the Payload dashboard as necessary.
+
+To do so, provide your base Payload config with a path to your own stylesheet. It can be either a CSS or SCSS file.
+
+**Example in payload.config.js:**
+
+```ts
+import { buildConfig } from 'payload/config'
+import path from 'path'
+
+const config = buildConfig({
+  admin: {
+    css: path.resolve(__dirname, 'relative/path/to/stylesheet.scss'),
+  },
+})
+```
+
+### Overriding built-in styles
+
+To make it as easy as possible for you to override our styles, Payload uses [BEM naming conventions](http://getbem.com/) for all CSS within the Admin UI. If you provide your own CSS, you can override any built-in styles easily.
+
+In addition to adding your own style definitions, you can also override Payload's built-in CSS variables. We use as much as possible behind the scenes, and you can override any of them that you'd like to.
+
+You can find the built-in Payload CSS variables within [`./src/admin/scss/app.scss`](https://github.com/payloadcms/payload/blob/main/packages/payload/src/admin/scss/app.scss) and [`./src/admin/scss/colors.scss`](https://github.com/payloadcms/payload/blob/main/packages/payload/src/admin/scss/colors.scss). The following variables are defined and can be overridden:
+
+- Breakpoints
+- Base color shades (white to black by default)
+- Success / warning / error color shades
+- Theme-specific colors (background, input background, text color, etc.)
+- Elevation colors (used to determine how "bright" something should be when compared to the background)
+- Fonts
+- Horizontal gutter
+
+#### Dark mode
+
+<Banner type="warning">
+  If you're overriding colors or theme elevations, make sure to consider how your changes will
+  affect dark mode.
+</Banner>
+
+By default, Payload automatically overrides all `--theme-elevation`s and inverts all success / warning / error shades to suit dark mode. We also update some base theme variables like `--theme-bg`, `--theme-text`, etc.

docs/admin/environment-vars.mdx

@@ -0,0 +1,27 @@
+---
+title: Environment Variables in Admin UI
+label: Environment Variables
+order: 100
+desc: NEEDS TO BE WRITTEN
+---
+
+## Admin environment vars
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  Be careful about what variables you provide to your client-side code. Analyze every single one to
+  make sure that you're not accidentally leaking anything that an attacker could exploit. Only keys
+  that are safe for anyone to read in plain text should be provided to your Admin panel.
+</Banner>
+
+By default, `env` variables are **not** provided to the Admin panel for security and safety reasons.
+But, Payload provides you with a way to still provide `env` vars to your frontend code.
+
+**Payload will automatically supply any present `env` variables that are prefixed with `PAYLOAD_PUBLIC_` directly to the Admin panel.**
+
+For example, if you've got the following environment variable:
+
+`PAYLOAD_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_XXXXXXXXXXXXXXXXXX`
+
+This key will automatically be made available to the Payload bundle and can be referenced in your Admin component code as `process.env.PAYLOAD_PUBLIC_STRIPE_PUBLISHABLE_KEY`.

docs/admin/excluding-server-code.mdx

@@ -0,0 +1,131 @@
+---
+title: Excluding server-only code from admin UI
+label: Excluding server code
+order: 70
+desc: Learn how to exclude server-only code from the Payload Admin UI bundle
+---
+
+Because the Admin Panel browser bundle includes your Payload Config file, files using server-only modules need to be excluded.
+It's common for your config to rely on server only modules to perform logic in access control functions, hooks, and other contexts.
+
+Any file that imports a server-only module such as `fs`, `stripe`, `authorizenet`, `nodemailer`, etc. **cannot** be included in the browser bundle.
+
+#### Example Scenario
+
+Say we have a collection called `Subscriptions` that has a `beforeChange` hook that creates a Stripe subscription whenever a Subscription document is created in Payload.
+
+**Collection config**:
+
+```ts
+// collections/Subscriptions/index.ts
+
+import { CollectionConfig } from 'payload/types'
+import createStripeSubscription from './hooks/createStripeSubscription'
+
+export const Subscription: CollectionConfig = {
+  slug: 'subscriptions',
+  hooks: {
+    beforeChange: [createStripeSubscription],
+  },
+  fields: [
+    {
+      name: 'stripeSubscriptionID',
+      type: 'text',
+      required: true,
+    },
+  ],
+}
+```
+
+**Collection hook**:
+
+```ts
+// collections/Subscriptions/hooks/createStripeSubscription.ts
+
+// highlight-start
+import Stripe from 'stripe' // <-- server-only module
+// highlight-end
+
+const stripe = new Stripe(process.env.STRIPE_SECRET_KEY)
+
+export const createStripeSubscription = async ({ data, operation }) => {
+  if (operation === 'create') {
+    const dataWithStripeID = { ...data }
+
+    // use Stripe to create a Stripe subscription
+    const subscription = await stripe.subscriptions.create({
+      // Configure the subscription accordingly
+    })
+
+    // Automatically add the Stripe subscription ID
+    // to the data that will be saved to this Subscription doc
+    dataWithStripeID.stripeSubscriptionID = subscription.id
+
+    return dataWithStripeID
+  }
+
+  return data
+}
+```
+
+<Banner type="error">
+  <strong>Warning:</strong>
+  <br />
+  The above code is NOT production-ready and should not be referenced to create Stripe
+  subscriptions. Although creating a beforeChange hook is a completely valid spot to do things like
+  create subscriptions, the code above is incomplete and insecure, meant for explanation purposes
+  only.
+</Banner>
+
+**As-is, this collection will prevent your Admin panel from bundling or loading correctly, because Stripe relies on some Node-only packages.**
+
+#### How to fix this
+
+You need to make sure that you use `alias`es to tell your bundler to import "safe" files vs. attempting to import any server-side code that you need to get rid of. Depending on your bundler (Webpack, Vite, etc.) the steps involved may be slightly different.
+
+The basic idea is to create a file that exports an empty object, and then alias import paths of any files that import server-only modules to that empty object file.
+
+This way when your bundler goes to import a file that contains server-only modules, it will instead import the empty object file, which will not break the browser bundle.
+
+### Aliasing server-only modules
+
+To remove files that contain server-only modules from your bundle, you can use an `alias`.
+
+First create new file that exports an empty object:
+```js
+// mocks/emptyObject.js
+
+export default {}
+```
+
+Then, in your Payload config, you can alias the file containing the server-only module to the mock module. For example, here's how you'd do this in Webpack:
+
+```ts
+// payload.config.ts
+
+import { buildConfig } from 'payload/config'
+import { webpackBundler } from '@payloadcms/bundler-webpack'
+
+const mockModulePath = path.resolve(__dirname, 'mocks/emptyObject.js')
+const pathToFileWithServerOnlyModule = path.resolve(__dirname, 'hooks/syncStripeCustomer.ts')
+
+export default buildConfig({
+  admin: {
+    bundler: webpackBundler(),
+    webpack: (config) => {
+      return {
+        ...config,
+        resolve: {
+          ...config.resolve,
+          // highlight-start
+          alias: {
+            ...config.resolve.alias,
+            [pathToFileWithServerOnlyModule]: mockModulePath,
+          },
+          // highlight-end
+        },
+      }
+    },
+  },
+})
+```

docs/admin/hooks.mdx

@@ -0,0 +1,760 @@
+---
+title: React Hooks
+label: React Hooks
+order: 30
+desc: Make use of all of the powerful React hooks that Payload provides.
+keywords: admin, components, custom, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload provides a variety of powerful hooks that can be used within your own React components. With them, you can interface with Payload itself and build just about any type of complex customization you can think of—directly in familiar React code.
+
+### useField
+
+The `useField` hook is used internally within every applicable Payload field component, and it manages sending and receiving a field's state from its parent form.
+
+Outside of internal use, its most common use-case is in custom `Field` components. When you build a custom React `Field` component, you'll be responsible for sending and receiving the field's `value` from the form itself. To do so, import the `useField` hook as follows:
+
+```tsx
+import { useField } from 'payload/components/forms'
+
+type Props = { path: string }
+
+const CustomTextField: React.FC<Props> = ({ path }) => {
+  // highlight-start
+  const { value, setValue } = useField<string>({ path })
+  // highlight-end
+
+  return <input onChange={(e) => setValue(e.target.value)} value={value.path} />
+}
+```
+
+The `useField` hook accepts an `args` object and sends back information and helpers for you to make use of:
+
+```ts
+const field = useField<string>({
+  path: 'fieldPathHere', // required
+  validate: myValidateFunc, // optional
+  disableFormData?: false, // if true, the field's data will be ignored
+  condition?: myConditionHere, // optional, used to skip validation if condition fails
+})
+
+// Here is what `useField` sends back
+const {
+  showError, // whether or not the field should show as errored
+  errorMessage, // the error message to show, if showError
+  value, // the current value of the field from the form
+  formSubmitted, // if the form has been submitted
+  formProcessing, // if the form is currently processing
+  setValue, // method to set the field's value in form state
+  initialValue, // the initial value that the field mounted with
+} = field;
+
+// The rest of your component goes here
+```
+
+### useFormFields
+
+There are times when a custom field component needs to have access to data from other fields, and you have a few options to do so. The `useFormFields` hook is a powerful and highly performant way to retrieve a form's field state, as well as to retrieve the `dispatchFields` method, which can be helpful for setting other fields' form states from anywhere within a form.
+
+<Banner type="success">
+  <strong>This hook is great for retrieving only certain fields from form state</strong> because it
+  ensures that it will only cause a rerender when the items that you ask for change.
+</Banner>
+
+Thanks to the awesome package [`use-context-selector`](https://github.com/dai-shi/use-context-selector), you can retrieve a specific field's state easily. This is ideal because you can ensure you have an up-to-date field state, and your component will only re-render when _that field's state_ changes.
+
+You can pass a Redux-like selector into the hook, which will ensure that you retrieve only the field that you want. The selector takes an argument with type of `[fields: Fields, dispatch: React.Dispatch<Action>]]`.
+
+```tsx
+import { useFormFields } from 'payload/components/forms'
+
+const MyComponent: React.FC = () => {
+  // Get only the `amount` field state, and only cause a rerender when that field changes
+  const amount = useFormFields(([fields, dispatch]) => fields.amount)
+
+  // Do the same thing as above, but to the `feePercentage` field
+  const feePercentage = useFormFields(([fields, dispatch]) => fields.feePercentage)
+
+  if (typeof amount?.value !== 'undefined' && typeof feePercentage?.value !== 'undefined') {
+    return <span>The fee is ${(amount.value * feePercentage.value) / 100}</span>
+  }
+}
+```
+
+### useAllFormFields
+
+**To retrieve more than one field**, you can use the `useAllFormFields` hook. Your component will re-render when _any_ field changes, so use this hook only if you absolutely need to. Unlike the `useFormFields` hook, this hook does not accept a "selector", and it always returns an array with type of `[fields: Fields, dispatch: React.Dispatch<Action>]]`.
+
+You can do lots of powerful stuff by retrieving the full form state, like using built-in helper functions to reduce field state to values only, or to retrieve sibling data by path.
+
+```tsx
+import { useAllFormFields, reduceFieldsToValues, getSiblingData } from 'payload/components/forms';
+
+const ExampleComponent: React.FC = () => {
+  // the `fields` const will be equal to all fields' state,
+  // and the `dispatchFields` method is usable to send field state up to the form
+  const [fields, dispatchFields] = useAllFormFields();
+
+  // Pass in fields, and indicate if you'd like to "unflatten" field data.
+  // The result below will reflect the data stored in the form at the given time
+  const formData = reduceFieldsToValues(fields, true);
+
+  // Pass in field state and a path,
+  // and you will be sent all sibling data of the path that you've specified
+  const siblingData = getSiblingData(fields, 'someFieldName');
+
+  return (
+    // return some JSX here if necessary
+  )
+};
+```
+
+##### Updating other fields' values
+
+If you are building a custom component, then you should use `setValue` which is returned from the `useField` hook to programmatically set your field's value. But if you're looking to update _another_ field's value, you can use `dispatchFields` returned from `useFormFields`.
+
+You can send the following actions to the `dispatchFields` function.
+
+| Action                 | Description                                                                |
+| ---------------------- | -------------------------------------------------------------------------- |
+| **`ADD_ROW`**          | Adds a row of data (useful in array / block field data)                    |
+| **`DUPLICATE_ROW`**    | Duplicates a row of data (useful in array / block field data)              |
+| **`MODIFY_CONDITION`** | Updates a field's conditional logic result (true / false)                  |
+| **`MOVE_ROW`**         | Moves a row of data (useful in array / block field data)                   |
+| **`REMOVE`**           | Removes a field from form state                                            |
+| **`REMOVE_ROW`**       | Removes a row of data from form state (useful in array / block field data) |
+| **`REPLACE_STATE`**    | Completely replaces form state                                             |
+| **`UPDATE`**           | Update any property of a specific field's state                            |
+
+To see types for each action supported within the `dispatchFields` hook, check out the Form types [here](https://github.com/payloadcms/payload/blob/main/packages/payload/src/admin/components/forms/Form/types.ts).
+
+### useForm
+
+The `useForm` hook can be used to interact with the form itself, and sends back many methods that can be used to reactively fetch form state without causing rerenders within your components each time a field is changed. This is useful if you have action-based callbacks that your components fire, and need to interact with form state _based on a user action_.
+
+<Banner type="warning">
+  <strong>Warning:</strong>
+  <br />
+  This hook is optimized to avoid causing rerenders when fields change, and as such, its `fields`
+  property will be out of date. You should only leverage this hook if you need to perform actions
+  against the form in response to your users' actions. Do not rely on its returned "fields" as being
+  up-to-date. They will be removed from this hook's response in an upcoming version.
+</Banner>
+
+The `useForm` hook returns an object with the following properties: |
+
+<TableWithDrawers
+  columns={[
+    'Action',
+    'Description',
+    'Example',
+  ]}
+  rows={[
+    [
+      {
+        value: <strong><code>fields</code></strong>,
+      },
+      {
+        value: "Deprecated. This property cannot be relied on as up-to-date.",
+      },
+      {
+        value: ''
+      }
+    ],
+    [
+      {
+        value: <strong><code>submit</code></strong>,
+      },
+      {
+        value: "Method to trigger the form to submit",
+      },
+      {
+        value: ''
+      }
+    ],
+    [
+      {
+        value: <strong><code>dispatchFields</code></strong>,
+      },
+      {
+        value: "Dispatch actions to the form field state",
+      },
+      {
+        value: ''
+      }
+    ],
+    [
+      {
+        value: <strong><code>validateForm</code></strong>,
+      },
+      {
+        value: "Trigger a validation of the form state",
+      },
+      {
+        value: ''
+      }
+    ],
+    [
+      {
+        value: <strong><code>createFormData</code></strong>,
+      },
+      {
+        value: <>Create a <code>multipart/form-data</code> object from the current form's state</>,
+      },
+      {
+        value: ''
+      }
+    ],
+    [
+      {
+        value: <strong><code>disabled</code></strong>,
+      },
+      {
+        value: "Boolean denoting whether or not the form is disabled",
+      },
+      {
+        value: ''
+      }
+    ],
+    [
+      {
+        value: <strong><code>getFields</code></strong>,
+      },
+      {
+        value: 'Gets all fields from state',
+      },
+      {
+        value: '',
+      }
+    ],
+    [
+      {
+        value: <strong><code>getField</code></strong>,
+      },
+      {
+        value: 'Gets a single field from state by path',
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>getData</code></strong>,
+      },
+      {
+        value: 'Returns the data stored in the form',
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>getSiblingData</code></strong>,
+      },
+      {
+        value: 'Returns form sibling data for the given field path',
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>setModified</code></strong>,
+      },
+      {
+        value: <>Set the form\'s <code>modified</code> state</>,
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>setProcessing</code></strong>,
+      },
+      {
+        value: <>Set the form\'s <code>processing</code> state</>,
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>setSubmitted</code></strong>,
+      },
+      {
+        value: <>Set the form\'s <code>submitted</code> state</>,
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>formRef</code></strong>,
+      },
+      {
+        value: 'The ref from the form HTML element',
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>reset</code></strong>,
+      },
+      {
+        value: 'Method to reset the form to its initial state',
+      },
+      {
+        value: '',
+      },
+    ],
+    [
+      {
+        value: <strong><code>addFieldRow</code></strong>,
+      },
+      {
+        value: "Method to add a row on an array or block field",
+      },
+      {
+        drawerTitle: 'addFieldRow',
+        drawerDescription: 'A useful method to programtically add a row to an array or block field.',
+        drawerSlug: 'addFieldRow',
+        drawerContent: (
+<>
+  <TableWithDrawers
+    columns={[
+      'Prop',
+      'Description',
+    ]}
+    rows={[
+      [
+        {
+          value: <strong><code>path</code></strong>,
+        },
+        {
+          value: "The path to the array or block field",
+        },
+      ],
+      [
+        {
+          value: <strong><code>rowIndex</code></strong>,
+        },
+        {
+          value: "The index of the row to add. If omitted, the row will be added to the end of the array.",
+        },
+      ],
+      [
+        {
+          value: <strong><code>data</code></strong>,
+        },
+        {
+          value: "The data to add to the row",
+        },
+      ],
+    ]}
+  />
+
+{' '}
+
+<br />
+
+{' '}
+
+<pre>
+  {`import { useForm } from "payload/components/forms";
+
+export const CustomArrayManager = () => {
+  const { addFieldRow } = useForm()
+
+  return (
+    <button
+      type="button"
+      onClick={() => {
+        addFieldRow({
+          path: "arrayField",
+          rowIndex: 0,
+          data: {
+            textField: "text",
+            // blockType: "yourBlockSlug",
+            // ^ if managing a block array, you need to specify the block type
+          },
+        })
+      }}
+    >
+      Add Row
+    </button>
+  )
+}`}
+</pre>
+
+  <p>An example config to go along with the custom component</p>
+  <pre>
+{`const ExampleCollection = {
+  slug: "example-collection",
+  fields: [
+    {
+      name: "arrayField",
+      type: "array",
+      fields: [
+        {
+          name: "textField",
+          type: "text",
+        },
+      ],
+    },
+    {
+      type: "ui",
+      name: "customArrayManager",
+      admin: {
+        components: {
+          Field: CustomArrayManager,
+        },
+      },
+    },
+  ],
+}`}
+  </pre>
+</>
+        )
+      }
+    ],
+    [
+      {
+        value: <strong><code>removeFieldRow</code></strong>,
+      },
+      {
+        value: "Method to remove a row from an array or block field",
+      },
+      {
+        drawerTitle: 'removeFieldRow',
+        drawerDescription: 'A useful method to programtically remove a row from an array or block field.',
+        drawerSlug: 'removeFieldRow',
+        drawerContent: (
+<>
+  <TableWithDrawers
+    columns={[
+      'Prop',
+      'Description',
+    ]}
+    rows={[
+      [
+        {
+          value: <strong><code>path</code></strong>,
+        },
+        {
+          value: "The path to the array or block field",
+        },
+      ],
+      [
+        {
+          value: <strong><code>rowIndex</code></strong>,
+        },
+        {
+          value: "The index of the row to remove",
+        },
+      ],
+    ]}
+  />
+
+{' '}
+
+<br />
+
+{' '}
+
+<pre>
+  {`import { useForm } from "payload/components/forms";
+
+export const CustomArrayManager = () => {
+  const { removeFieldRow } = useForm()
+
+  return (
+    <button
+      type="button"
+      onClick={() => {
+        removeFieldRow({
+          path: "arrayField",
+          rowIndex: 0,
+        })
+      }}
+    >
+      Remove Row
+    </button>
+  )
+}`}
+</pre>
+
+  <p>An example config to go along with the custom component</p>
+  <pre>
+{`const ExampleCollection = {
+  slug: "example-collection",
+  fields: [
+    {
+      name: "arrayField",
+      type: "array",
+      fields: [
+        {
+          name: "textField",
+          type: "text",
+        },
+      ],
+    },
+    {
+      type: "ui",
+      name: "customArrayManager",
+      admin: {
+        components: {
+          Field: CustomArrayManager,
+        },
+      },
+    },
+  ],
+}`}
+  </pre>
+</>
+        )
+      }
+    ],
+    [
+      {
+        value: <strong><code>replaceFieldRow</code></strong>,
+      },
+      {
+        value: "Method to replace a row from an array or block field",
+      },
+      {
+        drawerTitle: 'replaceFieldRow',
+        drawerDescription: 'A useful method to programtically replace a row from an array or block field.',
+        drawerSlug: 'replaceFieldRow',
+        drawerContent: (
+<>
+  <TableWithDrawers
+    columns={[
+      'Prop',
+      'Description',
+    ]}
+    rows={[
+      [
+        {
+          value: <strong><code>path</code></strong>,
+        },
+        {
+          value: "The path to the array or block field",
+        },
+      ],
+      [
+        {
+          value: <strong><code>rowIndex</code></strong>,
+        },
+        {
+          value: "The index of the row to replace",
+        },
+      ],
+      [
+        {
+          value: <strong><code>data</code></strong>,
+        },
+        {
+          value: "The data to replace within the row",
+        },
+      ],
+    ]}
+  />
+
+{' '}
+
+<br />
+
+{' '}
+
+<pre>
+  {`import { useForm } from "payload/components/forms";
+
+export const CustomArrayManager = () => {
+  const { replaceFieldRow } = useForm()
+
+  return (
+    <button
+      type="button"
+      onClick={() => {
+        replaceFieldRow({
+          path: "arrayField",
+          rowIndex: 0,
+          data: {
+            textField: "updated text",
+            // blockType: "yourBlockSlug",
+            // ^ if managing a block array, you need to specify the block type
+          },
+        })
+      }}
+    >
+      Replace Row
+    </button>
+  )
+}`}
+</pre>
+
+  <p>An example config to go along with the custom component</p>
+  <pre>
+{`const ExampleCollection = {
+  slug: "example-collection",
+  fields: [
+    {
+      name: "arrayField",
+      type: "array",
+      fields: [
+        {
+          name: "textField",
+          type: "text",
+        },
+      ],
+    },
+    {
+      type: "ui",
+      name: "customArrayManager",
+      admin: {
+        components: {
+          Field: CustomArrayManager,
+        },
+      },
+    },
+  ],
+}`}
+  </pre>
+</>
+        )
+      }
+    ],
+  ]}
+/>
+
+### useDocumentInfo
+
+The `useDocumentInfo` hook provides lots of information about the document currently being edited, including the following:
+
+| Property                  | Description                                                                                                        |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------|
+| **`collection`**          | If the doc is a collection, its collection config will be returned                                                 |
+| **`global`**              | If the doc is a global, its global config will be returned                                                         |
+| **`id`**                  | If the doc is a collection, its ID will be returned                                                                |
+| **`preferencesKey`**      | The `preferences` key to use when interacting with document-level user preferences                                 |
+| **`versions`**            | Versions of the current doc                                                                                        |
+| **`unpublishedVersions`** | Unpublished versions of the current doc                                                                            |
+| **`publishedDoc`**        | The currently published version of the doc being edited                                                            |
+| **`getVersions`**         | Method to trigger the retrieval of document versions                                                               |
+| **`docPermissions`**      | The current documents permissions. Collection document permissions fallback when no id is present (i.e. on create) |
+| **`getDocPermissions`**   | Method to trigger the retrieval of document level permissions                                                      |
+
+**Example:**
+
+```tsx
+import { useDocumentInfo } from 'payload/components/utilities'
+
+const LinkFromCategoryToPosts: React.FC = () => {
+  // highlight-start
+  const { id } = useDocumentInfo()
+  // highlight-end
+
+  // id will be undefined on the create form
+  if (!id) {
+    return null
+  }
+
+  return (
+    <a href={`/admin/collections/posts?where[or][0][and][0][category][in][0]=[${id}]`}>
+      View posts
+    </a>
+  )
+}
+```
+
+### useLocale
+
+In any custom component you can get the selected locale object with the `useLocale` hook. `useLocale`gives you the full locale object, consisting of a `label`, `rtl`(right-to-left) property, and then `code`. Here is a simple example:
+
+```tsx
+import { useLocale } from 'payload/components/utilities'
+
+const Greeting: React.FC = () => {
+  // highlight-start
+  const locale = useLocale()
+  // highlight-end
+
+  const trans = {
+    en: 'Hello',
+    es: 'Hola',
+  }
+
+  return <span> {trans[locale.code]} </span>
+}
+```
+
+### useAuth
+
+Useful to retrieve info about the currently logged in user as well as methods for interacting with it. It sends back an object with the following properties:
+
+| Property                 | Description                                                                             |
+| ------------------------ | --------------------------------------------------------------------------------------- |
+| **`user`**               | The currently logged in user                                                            |
+| **`logOut`**             | A method to log out the currently logged in user                                        |
+| **`refreshCookie`**      | A method to trigger the silent refreshing of a user's auth token                        |
+| **`setToken`**           | Set the token of the user, to be decoded and used to reset the user and token in memory |
+| **`token`**              | The logged in user's token (useful for creating preview links, etc.)                    |
+| **`refreshPermissions`** | Load new permissions (useful when content that effects permissions has been changed)    |
+| **`permissions`**        | The permissions of the current user                                                     |
+
+```tsx
+import { useAuth } from 'payload/components/utilities'
+import { User } from '../payload-types.ts'
+
+const Greeting: React.FC = () => {
+  // highlight-start
+  const { user } = useAuth<User>()
+  // highlight-end
+
+  return <span>Hi, {user.email}!</span>
+}
+```
+
+### useConfig
+
+Used to easily fetch the full Payload config.
+
+```tsx
+import { useConfig } from 'payload/components/utilities'
+
+const MyComponent: React.FC = () => {
+  // highlight-start
+  const config = useConfig()
+  // highlight-end
+
+  return <span>{config.serverURL}</span>
+}
+```
+
+### useEditDepth
+
+Sends back how many editing levels "deep" the current component is. Edit depth is relevant while adding new documents / editing documents in modal windows and other cases.
+
+```tsx
+import { useEditDepth } from 'payload/components/utilities'
+
+const MyComponent: React.FC = () => {
+  // highlight-start
+  const editDepth = useEditDepth()
+  // highlight-end
+
+  return <span>My component is {editDepth} levels deep</span>
+}
+```
+
+### usePreferences
+
+Returns methods to set and get user preferences. More info can be found [here](https://payloadcms.com/docs/admin/preferences).

docs/admin/overview.mdx

@@ -0,0 +1,91 @@
+---
+title: The Admin Panel
+label: Overview
+order: 10
+desc: Manage your data and customize the Admin Panel by swapping in your own React components. Create, modify or remove views, fields, styles and much more.
+keywords: admin, components, custom, customize, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload dynamically generates a beautiful, fully functional React admin panel to manage your data. It's extremely powerful and can be customized / extended upon easily by swapping in your own React components. You can add additional views, modify how built-in views look / work, swap out Payload branding for your client's, build your own field types and much more.
+
+The Payload Admin panel can be bundled with our officially supported [Vite](/docs/admin/vite) and [webpack](/docs/admin/webpack) bundlers or you can integrate another bundler following our adapter pattern approach.
+When bundled, it is code-split, highly performant (even with 100+ fields), and written fully in TypeScript.
+
+<Banner type="success">
+  The Admin panel is meant to be simple enough to give you a starting point but not bring too much
+  complexity, so that you can easily customize it to suit the needs of your application and your
+  editors.
+</Banner>
+
+<LightDarkImage
+  srcLight="https://payloadcms.com/images/docs/admin.jpg"
+  srcDark="https://payloadcms.com/images/docs/admin-dark.jpg"
+  alt="Admin panel with collapsible sidebar"
+  caption="Redesigned admin panel with a collapsible sidebar that's open by default, providing greater extensibility and enhanced horizontal real estate."
+/>
+
+## Admin Options
+
+All options for the Admin panel are defined in your base Payload config file.
+
+| Option                | Description                                                                                                                                                                                                                                                  |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `user`                | The `slug` of a Collection that you want be used to log in to the Admin dashboard. [More](/docs/admin/overview#the-admin-user-collection)                                                                                                                    |
+| `buildPath`           | Specify an absolute path for where to store the built Admin panel bundle used in production. Defaults to `path.resolve(process.cwd(), 'build')`.                                                                                                             |
+| `meta`                | Base meta data to use for the Admin panel. Included properties are `titleSuffix`, `ogImage`, and `favicon`.                                                                                                                                                  |
+| `disable`             | If set to `true`, the entire Admin panel will be disabled.                                                                                                                                                                                                   |
+| `indexHTML`           | Optionally replace the entirety of the `index.html` file used by the Admin panel. Reference the [base index.html file](https://github.com/payloadcms/payload/blob/main/packages/payload/src/admin/index.html) to ensure your replacement has the appropriate HTML elements. |
+| `css`                 | Absolute path to a stylesheet that you can use to override / customize the Admin panel styling. [More](/docs/admin/customizing-css).                                                                                                                         |
+| `scss`                | Absolute path to a Sass variables / mixins stylesheet meant to override Payload styles to make for an easy re-skinning of the Admin panel. [More](/docs/admin/customizing-css#overriding-scss-variables).                                                    |
+| `dateFormat`          | Global date format that will be used for all dates in the Admin panel. Any valid [date-fns](https://date-fns.org/) format pattern can be used.                                                                                                               |
+| `avatar`              | Set account profile picture. Options: `gravatar`, `default` or a custom React component.                                                                                                                                                                     |
+| `autoLogin`           | Used to automate admin log-in for dev and demonstration convenience. [More](/docs/authentication/config).                                                                                                                                                    |
+| `livePreview`         | Enable real-time editing for instant visual feedback of your front-end application. [More](/docs/live-preview/overview).                                                                                                                                     |
+| `components`          | Component overrides that affect the entirety of the Admin panel. [More](/docs/admin/components)                                                                                                                                                              |
+| `webpack`             | Customize the Webpack config that's used to generate the Admin panel. [More](/docs/admin/webpack)                                                                                                                                                            |
+| `vite`                | Customize the Vite config that's used to generate the Admin panel. [More](/docs/admin/vite)                                                                                                                                                                  |
+| **`bundler`**         | The bundler that you would like to use to bundle the admin panel. Officially supported bundlers: [Webpack](/docs/admin/webpack) and [Vite](/docs/admin/vite).                                                                                                |
+| **`logoutRoute`**     | The route for the `logout` page.                                                                                                                                                                                                                             |
+| **`inactivityRoute`** | The route for the `logout` inactivity page.                                                                                                                                                                                                                  |
+
+### The Admin User Collection
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  The Payload Admin panel can only be used by one Collection that supports
+  [Authentication](/docs/authentication/overview).
+</Banner>
+
+To specify which Collection to use to log in to the Admin panel, pass the `admin` options a `user` key equal to the slug of the Collection that you'd like to use.
+
+`payload.config.js`:
+
+```ts
+import { buildConfig } from 'payload/config'
+
+const config = buildConfig({
+  admin: {
+    user: 'admins', // highlight-line
+  },
+})
+```
+
+By default, if you have not specified a Collection, Payload will automatically provide you with a `User` Collection which will be used to access the Admin panel. You can customize or override the fields and settings of the default `User` Collection by passing your own collection using `users` as its `slug` to Payload. When this is done, Payload will use your provided `User` Collection instead of its default version.
+
+**Note: you can use whatever Collection you'd like to access the Admin panel as long as the Collection supports Authentication. It doesn't need to be called `users`!**
+
+For example, you may wish to have two Collections that both support `Authentication`:
+
+- `admins` - meant to have a higher level of permissions to manage your data and access the Admin panel
+- `customers` - meant for end users of your app that should not be allowed to log into the Admin panel
+
+This is totally possible. For the above scenario, by specifying `admin: { user: 'admins' }`, your Payload Admin panel will use `admins`. Any users logged in as `customers` will not be able to log in via the Admin panel.
+
+### Light and dark modes
+
+Users in the admin panel have access to choosing between light mode and dark mode for their editing experience. The setting is managed while logged into the admin UI within the user account page and will be stored with the browser. By default, the operating system preference is detected and used.
+
+### Restricting user access
+
+If you would like to restrict which users from a single Collection can access the Admin panel, you can use the `admin` access control function. [Click here](/docs/access-control/overview#admin) to learn more.

docs/admin/preferences.mdx

@@ -0,0 +1,159 @@
+---
+title: Managing User Preferences
+label: Preferences
+order: 50
+desc: Store the preferences of your users as they interact with the Admin panel.
+keywords: admin, preferences, custom, customize, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+As your users interact with your Admin panel, you might want to store their preferences in a persistent manner, so that when they revisit the Admin panel, they can pick right back up where they left off.
+
+Out of the box, Payload handles the persistence of your users' preferences in a handful of ways, including:
+
+1. Collection `List` view active columns, and their order, that users define
+1. Their last active locale
+1. The "collapsed" state of blocks, on a document level, as users edit or interact with documents
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  All preferences are stored on an individual user basis. Payload automatically recognizes the user
+  that is reading or setting a preference via all provided authentication methods.
+</Banner>
+
+### Use cases
+
+This API is used significantly for internal operations of the Admin panel, as mentioned above. But, if you're building your own React components for use in the Admin panel, you can allow users to set their own preferences in correspondence to their usage of your components. For example:
+
+- If you have built a "color picker", you could "remember" the last used colors that the user has set for easy access next time
+- If you've built a custom `Nav` component, and you've built in an "accordion-style" UI, you might want to store the `collapsed` state of each Nav collapsible item. This way, if an editor returns to the panel, their `Nav` state is persisted automatically
+- You might want to store `recentlyAccessed` documents to give admin editors an easy shortcut back to their recently accessed documents on the `Dashboard` or similar
+- Many other use cases exist. Invent your own! Give your editors an intelligent and persistent editing experience.
+
+### Database
+
+Payload automatically creates an internally used `payload-preferences` collection that stores user preferences. Each document in the `payload-preferences` collection contains the following shape:
+
+| Key               | Value                                                             |
+| ----------------- | ----------------------------------------------------------------- |
+| `id`              | A unique ID for each preference stored.                           |
+| `key`             | A unique `key` that corresponds to the preference.                |
+| `user.value`      | The ID of the `user` that is storing its preference.              |
+| `user.relationTo` | The `slug` of the collection that the `user` is logged in as.     |
+| `value`           | The value of the preference. Can be any data shape that you need. |
+| `createdAt`       | A timestamp of when the preference was created.                   |
+| `updatedAt`       | A timestamp set to the last time the preference was updated.      |
+
+### APIs
+
+Preferences are available to both [GraphQL](/docs/graphql/overview#preferences) and [REST](/docs/rest-api/overview#) APIs.
+
+### Adding or reading Preferences in your own components
+
+The Payload admin panel offers a `usePreferences` hook. The hook is only meant for use within the admin panel itself. It provides you with two methods:
+
+##### `getPreference`
+
+This async method provides an easy way to retrieve a user's preferences by `key`. It will return a promise containing the resulting preference value.
+
+**Arguments**
+
+- `key`: the `key` of your preference to retrieve.
+
+##### `setPreference`
+
+Also async, this method provides you with an easy way to set a user preference. It returns `void`.
+
+**Arguments:**
+
+- `key`: the `key` of your preference to set.
+- `value`: the `value` of your preference that you're looking to set.
+
+## Example
+
+Here is an example for how you can utilize `usePreferences` within your custom Admin panel components. Note - this example is not fully useful and is more just a reference for how to utilize the Preferences API. In this case, we are demonstrating how to set and retrieve a user's last used colors history within a `ColorPicker` or similar type component.
+
+```
+import React, { Fragment, useState, useEffect, useCallback } from 'react';
+import { usePreferences } from 'payload/components/preferences';
+
+const lastUsedColorsPreferenceKey = 'last-used-colors';
+
+const CustomComponent = (props) => {
+  const { getPreference, setPreference } = usePreferences();
+
+  // Store the last used colors in local state
+  const [lastUsedColors, setLastUsedColors] = useState([]);
+
+  // Callback to add a color to the last used colors
+  const updateLastUsedColors = useCallback((color) => {
+    // First, check if color already exists in last used colors.
+    // If it already exists, there is no need to update preferences
+    const colorAlreadyExists = lastUsedColors.indexOf(color) > -1;
+
+    if (!colorAlreadyExists) {
+      const newLastUsedColors = [
+        ...lastUsedColors,
+        color,
+      ];
+
+      setLastUsedColors(newLastUsedColors);
+      setPreference(lastUsedColorsPreferenceKey, newLastUsedColors);
+    }
+  }, [lastUsedColors, setPreference]);
+
+  // Retrieve preferences on component mount
+  // This will only be run one time, because the `getPreference` method never changes
+  useEffect(() => {
+    const asyncGetPreference = async () => {
+      const lastUsedColorsFromPreferences = await getPreference(lastUsedColorsPreferenceKey);
+      setLastUsedColors(lastUsedColorsFromPreferences);
+    };
+
+    asyncGetPreference();
+  }, [getPreference]);
+
+  return (
+    <div>
+      <button
+        type="button"
+        onClick={() => updateLastUsedColors('red')}
+      >
+        Use red
+      </button>
+      <button
+        type="button"
+        onClick={() => updateLastUsedColors('blue')}
+      >
+        Use blue
+      </button>
+      <button
+        type="button"
+        onClick={() => updateLastUsedColors('purple')}
+      >
+        Use purple
+      </button>
+      <button
+        type="button"
+        onClick={() => updateLastUsedColors('yellow')}
+      >
+        Use yellow
+      </button>
+      {lastUsedColors && (
+        <Fragment>
+          <h5>Last used colors:</h5>
+          <ul>
+            {lastUsedColors?.map((color) => (
+              <li key={color}>
+                {color}
+              </li>
+            ))}
+          </ul>
+        </Fragment>
+      )}
+    </div>
+  );
+};
+
+export default CustomComponent;
+```

docs/admin/vite.mdx

@@ -0,0 +1,82 @@
+---
+title: Vite
+label: Vite
+order: 90
+desc: NEEDS TO BE WRITTEN
+---
+
+Payload has a Vite bundler that you can install and bundle the Admin Panel with. This is an alternative to the [Webpack](/docs/admin/webpack) bundler and might give some performance boosts to your development workflow.
+
+To use Vite as your bundler, first you need to install the package:
+
+```bash
+yarn add @payloadcms/bundler-vite
+```
+
+<Banner>
+  The Vite bundler is currently in beta. If you would like to help us test this package, we'd love to hear if you find any bugs or issues!
+</Banner>
+
+Vite works fundamentally differently than Webpack. In development mode, it will first pre-bundle any of your dependencies that are CommonJS-only, and then it'll leverage ESM directly in your browser for a better HMR experience.
+
+It then uses Rollup to create production builds of your admin UI. With Vite, you should see a decent performance boost—especially after your first cold start. However, that first cold start might take a few more seconds.
+
+<Banner type="warning">
+  In most cases, Vite should work out of the box. But existing Payload plugins may need to make compatibility changes to support Vite.
+</Banner>
+
+This is because Vite aliases work fundamentally differently than Webpack aliases, and Payload relies on aliasing server-only code out of the Payload config to ensure that the bundled admin JS works within your browser.
+
+Here are the main differences between how Vite aliases work and how Webpack aliases work.
+
+**Vite aliases do not work with absolute paths.** 
+
+In Vite, an alias will only match if the `find` property _exactly matches_ how you are importing your server-only file. So if you are importing a file with a relative path, i.e. `'../../my-module'`, and your alias is absolute, your alias will not work.
+
+
+**Vite aliases do not get applied to pre-bundled dependencies.**
+
+This especially affects plugins, as plugins will be pre-bundled by Vite using `esbuild`. To get around this and support Vite, plugin authors need to configure an alias to their plugin at the top level, so that the alias will work accordingly.
+
+Here's an example. Say your plugin is called `payload-plugin-cool`. It's imported as follows:
+
+```ts
+import { myCoolPlugin } from 'payload-plugin-cool'
+```
+
+That plugin should create an alias to support Vite as follows:
+
+```ts
+{
+  // aliases go here
+  'payload-plugin-cool': path.resolve(__dirname, './my-admin-plugin.js')
+}
+
+```
+
+This will effectively alias the entire plugin and work with Vite. If the plugin requires admin-specific code, then the `./my-admin-plugin.js` alias target file should reflect any changes necessary to the admin UI that the main server-side plugin performs.
+
+### Extending the Vite config
+
+The Payload config supports a new property for plugins to be able to extend the Vite config specifically. That property exists on the main Payload config under `admin.vite`. 
+
+It's a function that takes a Vite config, and returns an updated Vite config. Here's an example:
+
+```ts
+export const buildConfig({
+  collections: [],
+  admin: {
+    vite: (incomingViteConfig) => ({
+      ...incomingViteConfig,
+      resolve: {
+        ...incomingViteConfig.resolve,
+        // Do whatever you need here 
+      }
+    })
+  }
+})
+```
+
+Even though there is a new property for Vite configs specifically, we have implemented some "compatibility" between Webpack and Vite out-of-the-box.
+
+If your config specifies Webpack aliases, we attempt to leverage them automatically within the Vite config. They are merged into the Vite alias configuration seamlessly and may work out-of-the-box.

docs/admin/webpack.mdx

@@ -0,0 +1,67 @@
+---
+title: Webpack
+label: Webpack
+order: 80
+desc: The Payload admin panel uses Webpack 5 and supports many common functionalities such as SCSS and Typescript out of the box to give you more freedom.
+keywords: admin, webpack, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload has a Webpack (v5) bundler that you can build the Admin panel with. For now, we recommended using it because it is stable. If you are feeling a bit more adventurous you can give the [Vite](/docs/admin/vite) bundler a shot.
+
+Out of the box, the Webpack bundler supports common functionalities such as SCSS and Typescript, but there are many cases where you may need to add support for additional functionalities.
+
+#### Installation
+
+```bash
+yarn add @payloadcms/bundler-webpack
+```
+
+#### Import the bundler
+
+```ts
+// payload.config.ts
+
+import { buildConfig } from 'payload/config'
+import { webpackBundler } from '@payloadcms/bundler-webpack'
+
+export default buildConfig({
+  // highlight-start
+  admin: {
+    bundler: webpackBundler()
+  },
+  // highlight-end
+})
+```
+
+### Extending Webpack
+
+If you need to extend the Webpack config, you can do so by passing a function to the `admin.webpack` property on your Payload config.
+The function will receive the Webpack config as an argument and should return the modified config.
+
+```ts
+// payload.config.ts
+
+import { buildConfig } from 'payload/config'
+import { webpackBundler } from '@payloadcms/bundler-webpack'
+
+export default buildConfig({
+  admin: {
+    bundler: webpackBundler()
+    // highlight-start
+    webpack: (config) => {
+      // full control of the Webpack config
+
+      return config
+    },
+    // highlight-end
+  },
+})
+```
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  If changes to your Webpack aliases are not surfacing, they might be
+  [cached](https://webpack.js.org/configuration/cache/) in `node_modules/.cache/webpack`. Try
+  deleting that folder and restarting your server.
+</Banner>

docs/authentication/config.mdx

@@ -0,0 +1,285 @@
+---
+title: Authentication Config
+label: Config
+order: 20
+desc: Enable and customize options in the Authentication config for features including Forgot Password, Login Attempts, API key usage and more.
+keywords: authentication, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload's Authentication is extremely powerful and gives you everything you need when you go to build a new app or site in a secure and responsible manner.
+
+To enable Authentication on a collection, define an `auth` property and set it to either `true` or to an object containing the options below.
+
+## Options
+
+| Option                     | Description                                                                                                                                                                                                                         |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`useAPIKey`**            | Payload Authentication provides for API keys to be set on each user within an Authentication-enabled Collection. [More](/docs/authentication/config#api-keys)                                                                       |
+| **`tokenExpiration`**      | How long (in seconds) to keep the user logged in. JWTs and HTTP-only cookies will both expire at the same time.                                                                                                                     |
+| **`maxLoginAttempts`**     | Only allow a user to attempt logging in X amount of times. Automatically locks out a user from authenticating if this limit is passed. Set to `0` to disable.                                                                       |
+| **`lockTime`**             | Set the time (in milliseconds) that a user should be locked out if they fail authentication more times than `maxLoginAttempts` allows for.                                                                                          |
+| **`depth`**                | How many levels deep a `user` document should be populated when creating the JWT and binding the `user` to the express `req`. Defaults to `0` and should only be modified if absolutely necessary, as this will affect performance. |
+| **`cookies`**              | Set cookie options, including `secure`, `sameSite`, and `domain`. For advanced users.                                                                                                                                               |
+| **`forgotPassword`**       | Customize the way that the `forgotPassword` operation functions. [More](/docs/authentication/config#forgot-password)                                                                                                                |
+| **`verify`**               | Set to `true` or pass an object with verification options to require users to verify by email before they are allowed to log into your app. [More](/docs/authentication/config#email-verification)                                  |
+| **`disableLocalStrategy`** | Advanced - disable Payload's built-in local auth strategy. Only use this property if you have replaced Payload's auth mechanisms with your own.                                                                                     |
+| **`strategies`**           | Advanced - an array of PassportJS authentication strategies to extend this collection's authentication with. [More](/docs/authentication/config#strategies)                                                                         |
+
+### API keys
+
+To integrate with third-party APIs or services, you might need the ability to generate API keys that can be used to identify as a certain user within Payload.
+
+In Payload, users are essentially documents within a collection. Just like you can authenticate as a user with an email and password, which is considered as our default local auth strategy, you can also authenticate as a user with an API key. API keys are generated on a user-by-user basis, similar to email and passwords, and are meant to represent a single user.
+
+For example, if you have a third-party service or external app that needs to be able to perform protected actions at its discretion, you have two options:
+
+1. Create a user for the third-party app, and log in each time to receive a token before you attempt to access any protected actions
+1. Enable API key support for the Collection, where you can generate a non-expiring API key per user in the collection. This is particularly useful as you can create a "user" that reflects an integration with a specific external service and assign a "role" or specific access only needed by that service/integration. Alternatively, you could create a "super admin" user and assign an API key to that user so that any requests made with that API key are considered as being made by that super user.
+
+Technically, both of these options will work for third-party integrations but the second option with API key is simpler, because it reduces the amount of work that your integrations need to do to be authenticated properly.
+
+To enable API keys on a collection, set the `useAPIKey` auth option to `true`. From there, a new interface will appear in the Admin panel for each document within the collection that allows you to generate an API key for each user in the Collection.
+
+<Banner type="success">
+  User API keys are encrypted within the database, meaning that if your database is compromised,
+  your API keys will not be.
+</Banner>
+
+#### Authenticating via API Key
+
+To authenticate REST or GraphQL API requests using an API key, set the `Authorization` header. The header is case-sensitive and needs the slug of the `auth.useAPIKey` enabled collection, then " API-Key ", followed by the `apiKey` that has been assigned. Payload's built-in middleware will then assign the user document to `req.user` and handle requests with the proper access control. By doing this, Payload recognizes the request being made as a request by the user associated with that API key.
+
+**For example, using Fetch:**
+
+```ts
+import User from '../collections/User'
+
+const response = await fetch('http://localhost:3000/api/pages', {
+  headers: {
+    Authorization: `${User.slug} API-Key ${YOUR_API_KEY}`,
+  },
+})
+```
+
+Payload ensures that the same, uniform access control is used across all authentication strategies. This enables you to utilize your existing access control configurations with both API keys and the standard email/password authentication. This consistency can aid in maintaining granular control over your API keys.
+
+#### API Key _Only_ Authentication
+
+If you want to use API keys as the only authentication method for a collection, you can disable the default local strategy by setting `disableLocalStrategy` to `true` on the collection's `auth` property. This will disable the ability to authenticate with email and password, and will only allow for authentication via API key.
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Customers: CollectionConfig = {
+  slug: 'customers',
+  auth: {
+    useAPIKey: true,
+    disableLocalStrategy: true,
+  },
+}
+```
+
+### Forgot Password
+
+You can customize how the Forgot Password workflow operates with the following options on the `auth.forgotPassword` property:
+
+**`generateEmailHTML`**
+
+Function that accepts one argument, containing `{ req, token, user }`, that allows for overriding the HTML within emails that are sent to users attempting to reset their password. The function should return a string that supports HTML, which can be a full HTML email.
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  HTML templating can be used to create custom email templates, inline CSS automatically, and more.
+  You can make a reusable function that standardizes all email sent from Payload, which makes
+  sending custom emails more DRY. Payload doesn't ship with an HTML templating engine, so you are
+  free to choose your own.
+</Banner>
+
+Example:
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Customers: CollectionConfig = {
+  slug: 'customers',
+  auth: {
+    forgotPassword: {
+      // highlight-start
+      generateEmailHTML: ({ req, token, user }) => {
+        // Use the token provided to allow your user to reset their password
+        const resetPasswordURL = `https://yourfrontend.com/reset-password?token=${token}`
+
+        return `
+          <!doctype html>
+          <html>
+            <body>
+              <h1>Here is my custom email template!</h1>
+              <p>Hello, ${user.email}!</p>
+              <p>Click below to reset your password.</p>
+              <p>
+                <a href="${resetPasswordURL}">${resetPasswordURL}</a>
+              </p>
+            </body>
+          </html>
+        `
+      },
+      // highlight-end
+    },
+  },
+}
+```
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  If you specify a different URL to send your users to for resetting their password, such as a page
+  on the frontend of your app or similar, you need to handle making the call to the Payload REST or
+  GraphQL reset-password operation yourself on your frontend, using the token that was provided for
+  you. Above, it was passed via query parameter.
+</Banner>
+
+**`generateEmailSubject`**
+
+Similarly to the above `generateEmailHTML`, you can also customize the subject of the email. The function argument are the same but you can only return a string - not HTML.
+
+Example:
+
+```ts
+{
+  slug: 'customers',
+  auth: {
+    forgotPassword: {
+      // highlight-start
+      generateEmailSubject: ({ req, user }) => {
+        return `Hey ${user.email}, reset your password!`;
+      }
+      // highlight-end
+    }
+  }
+}
+```
+
+### Email Verification
+
+If you'd like to require email verification before a user can successfully log in, you can enable it by passing `true` or an `options` object to `auth.verify`. The following options are available:
+
+**`generateEmailHTML`**
+
+Function that accepts one argument, containing `{ req, token, user }`, that allows for overriding the HTML within emails that are sent to users indicating how to validate their account. The function should return a string that supports HTML, which can optionally be a full HTML email.
+
+Example:
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Customers: CollectionConfig = {
+  slug: 'customers',
+  auth: {
+    verify: {
+      // highlight-start
+      generateEmailHTML: ({ req, token, user }) => {
+        // Use the token provided to allow your user to verify their account
+        const url = `https://yourfrontend.com/verify?token=${token}`
+
+        return `Hey ${user.email}, verify your email by clicking here: ${url}`
+      },
+      // highlight-end
+    },
+  },
+}
+```
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  If you specify a different URL to send your users to for email verification, such as a page on the
+  frontend of your app or similar, you need to handle making the call to the Payload REST or GraphQL
+  verification operation yourself on your frontend, using the token that was provided for you.
+  Above, it was passed via query parameter.
+</Banner>
+
+**`generateEmailSubject`**
+
+Similarly to the above `generateEmailHTML`, you can also customize the subject of the email. The function argument are the same but you can only return a string - not HTML.
+
+Example:
+
+```ts
+{
+  slug: 'customers',
+  auth: {
+    forgotPassword: {
+      // highlight-start
+      generateEmailSubject: ({ req, user }) => {
+        return `Hey ${user.email}, reset your password!`;
+      }
+      // highlight-end
+    }
+  }
+}
+```
+
+### Strategies
+
+As of Payload `1.0.0`, you can add additional authentication strategies to Payload easily by passing them to your collection's `auth.strategies` array.
+
+Behind the scenes, Payload uses PassportJS to power its local authentication strategy, so most strategies listed on the PassportJS website will work seamlessly. Combined with adding custom components to the admin panel's `Login` view, you can create advanced authentication strategies directly within Payload.
+
+<Banner type="warning">
+  This is an advanced feature, so only attempt this if you are an experienced developer. Otherwise,
+  just let Payload's built-in authentication handle user auth for you.
+</Banner>
+
+The `strategies` property is an array that takes objects with the following properties:
+
+**`strategy`**
+
+This property can accept a Passport strategy directly, or you can pass a function that takes a `payload` argument, and returns a Passport strategy.
+
+**`name`**
+
+If you pass a strategy to the `strategy` property directly, the `name` property is optional and allows you to override the strategy's built-in name.
+
+However, if you pass a function to `strategy`, `name` is a required property.
+
+In either case, Payload will prefix the strategy name with the collection `slug` that the strategy is passed to.
+
+### Admin autologin
+
+For testing and demo purposes you may want to skip forcing the admin user to login in order to access the panel.
+The `admin.autologin` property is used to configure the how visitors are handled when accessing the admin panel.
+The default is that all users will have to login and this should not be enabled for environments where data needs to protected.
+
+#### autoLogin Options
+
+| Option            | Description                                                                                                     |
+| ----------------- | --------------------------------------------------------------------------------------------------------------- |
+| **`email`**       | The email address of the user to login as                                                                       |
+| **`password`**    | The password of the user to login as                                                                            |
+| **`prefillOnly`** | If set to true, the login credentials will be prefilled but the user will still need to click the login button. |
+
+The recommended way to use this feature is behind an environment variable to ensure it is disabled when in production.
+
+**Example:**
+
+```ts
+export default buildConfig({
+  admin: {
+    user: 'users',
+    // highlight-start
+    autoLogin:
+      process.env.PAYLOAD_PUBLIC_ENABLE_AUTOLOGIN === 'true'
+        ? {
+            email: 'test@example.com',
+            password: 'test',
+            prefillOnly: true,
+          }
+        : false,
+    // highlight-end
+  },
+  collections: [
+    /** */
+  ],
+})
+```

docs/authentication/operations.mdx

@@ -0,0 +1,405 @@
+---
+title: Authentication Operations
+label: Operations
+order: 30
+desc: Enabling Authentication automatically makes key operations available such as Login, Logout, Verify, Unlock, Reset Password and more.
+keywords: authentication, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Enabling Authentication on a Collection automatically exposes additional auth-based operations in the Local, REST, and GraphQL APIs.
+
+### Access
+
+The Access operation returns what a logged in user can and can't do with the collections and globals that are registered via your config. This data can be immensely helpful if your app needs to show and hide certain features based on access control, as the Payload Admin panel does.
+
+**REST API endpoint**:
+
+`GET http://localhost:3000/api/access`
+
+Example response:
+
+```ts
+{
+  canAccessAdmin: true,
+  collections: {
+    pages: {
+      create: {
+        permission: true,
+      },
+      read: {
+        permission: true,
+      },
+      update: {
+        permission: true,
+      },
+      delete: {
+        permission: true,
+      },
+      fields: {
+        title: {
+          create: {
+            permission: true,
+          },
+          read: {
+            permission: true,
+          },
+          update: {
+            permission: true,
+          },
+        }
+      }
+    }
+  }
+}
+```
+
+**Example GraphQL Query**:
+
+```graphql
+query {
+  Access {
+    pages {
+      read {
+        permission
+      }
+    }
+  }
+}
+```
+
+Document access can also be queried on a collection/global basis. Access on a global can queried like `http://localhost:3000/api/global-slug/access`, Collection document access can be queried like `http://localhost:3000/api/collection-slug/access/:id`.
+
+### Me
+
+Returns either a logged in user with token or null when there is no logged in user.
+
+**REST API endpoint**:
+
+`GET http://localhost:3000/api/[collection-slug]/me`
+
+Example response:
+
+```ts
+{
+  user: { // The JWT "payload" ;) from the logged in user
+    email: 'dev@payloadcms.com',
+    createdAt: "2020-12-27T21:16:45.645Z",
+    updatedAt: "2021-01-02T18:37:41.588Z",
+    id: "5ae8f9bde69e394e717c8832"
+  },
+  token: '34o4345324...', // The token that can be used to authenticate the user
+  exp: 1609619861, // Unix timestamp representing when the user's token will expire
+}
+```
+
+**Example GraphQL Query**:
+
+```graphql
+query {
+  me[collection-singular-label] {
+    user {
+      email
+    }
+    exp
+  }
+}
+```
+
+### Login
+
+Accepts an `email` and `password`. On success, it will return the logged in user as well as a token that can be used to authenticate. In the GraphQL and REST APIs, this operation also automatically sets an HTTP-only cookie including the user's token. If you pass an Express `res` to the Local API operation, Payload will set a cookie there as well.
+
+**Example REST API login**:
+
+```ts
+const res = await fetch('http://localhost:3000/api/[collection-slug]/login', {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+  body: JSON.stringify({
+    email: 'dev@payloadcms.com',
+    password: 'this-is-not-our-password...or-is-it?',
+  }),
+})
+
+const json = await res.json()
+
+// JSON will be equal to the following:
+/*
+{
+  user: {
+    email: 'dev@payloadcms.com',
+    createdAt: "2020-12-27T21:16:45.645Z",
+    updatedAt: "2021-01-02T18:37:41.588Z",
+    id: "5ae8f9bde69e394e717c8832"
+  },
+  token: '34o4345324...',
+  exp: 1609619861
+}
+*/
+```
+
+**Example GraphQL Mutation**:
+
+```graphql
+mutation {
+  login[collection-singular-label](email: "dev@payloadcms.com", password: "yikes") {
+    user {
+      email
+    }
+    exp
+    token
+  }
+}
+```
+
+**Example Local API login**:
+
+```ts
+const result = await payload.login({
+  collection: '[collection-slug]',
+  data: {
+    email: 'dev@payloadcms.com',
+    password: 'get-out',
+  },
+})
+```
+
+### Logout
+
+As Payload sets HTTP-only cookies, logging out cannot be done by just removing a cookie in JavaScript, as HTTP-only cookies are inaccessible by JS within the browser. So, Payload exposes a `logout` operation to delete the token in a safe way.
+
+**Example REST API logout**:
+
+```ts
+const res = await fetch('http://localhost:3000/api/[collection-slug]/logout', {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+})
+```
+
+**Example GraphQL Mutation**:
+
+```
+mutation {
+  logout[collection-singular-label]
+}
+```
+
+### Refresh
+
+Allows for "refreshing" JWTs. If your user has a token that is about to expire, but the user is still active and using the app, you might want to use the `refresh` operation to receive a new token by sending the operation the token that is about to expire.
+
+This operation requires a non-expired token to send back a new one. If the user's token has already expired, you will need to allow them to log in again to retrieve a new token.
+
+If successful, this operation will automatically renew the user's HTTP-only cookie and will send back the updated token in JSON.
+
+**Example REST API token refresh**:
+
+```ts
+const res = await fetch('http://localhost:3000/api/[collection-slug]/refresh-token', {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+})
+
+const json = await res.json()
+
+// JSON will be equal to the following:
+/*
+{
+  user: {
+    email: 'dev@payloadcms.com',
+    createdAt: "2020-12-27T21:16:45.645Z",
+    updatedAt: "2021-01-02T18:37:41.588Z",
+    id: "5ae8f9bde69e394e717c8832"
+  },
+  refreshedToken: '34o4345324...',
+  exp: 1609619861
+}
+*/
+```
+
+**Example GraphQL Mutation**:
+
+```
+mutation {
+  refreshToken[collection-singular-label] {
+    user {
+      email
+    }
+    refreshedToken
+  }
+}
+```
+
+<Banner type="success">
+  The Refresh operation will automatically find the user's token in either a JWT header or the
+  HTTP-only cookie. But, you can specify the token you're looking to refresh by providing the REST
+  API with a `token` within the JSON body of the request, or by providing the GraphQL resolver a
+  `token` arg.
+</Banner>
+
+### Verify by Email
+
+If your collection supports email verification, the Verify operation will be exposed which accepts a verification token and sets the user's `_verified` property to `true`, thereby allowing the user to authenticate with the Payload API.
+
+**Example REST API user verification**:
+
+```ts
+const res = await fetch(`http://localhost:3000/api/[collection-slug]/verify/${TOKEN_HERE}`, {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+})
+```
+
+**Example GraphQL Mutation**:
+
+```graphql
+mutation {
+  verifyEmail[collection-singular-label](token: "TOKEN_HERE")
+}
+```
+
+**Example Local API verification**:
+
+```ts
+const result = await payload.verifyEmail({
+  collection: '[collection-slug]',
+  token: 'TOKEN_HERE',
+})
+```
+
+### Unlock
+
+If a user locks themselves out and you wish to deliberately unlock them, you can utilize the Unlock operation. The Admin panel features an Unlock control automatically for all collections that feature max login attempts, but you can programmatically unlock users as well by using the Unlock operation.
+
+To restrict who is allowed to unlock users, you can utilize the [`unlock`](/docs/access-control/overview#unlock) access control function.
+
+**Example REST API unlock**:
+
+```ts
+const res = await fetch(`http://localhost:3000/api/[collection-slug]/unlock`, {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+})
+```
+
+**Example GraphQL Mutation**:
+
+```
+mutation {
+  unlock[collection-singular-label]
+}
+```
+
+**Example Local API unlock**:
+
+```ts
+const result = await payload.unlock({
+  collection: '[collection-slug]',
+})
+```
+
+### Forgot Password
+
+Payload comes with built-in forgot password functionality. Submitting an email address to the Forgot Password operation will generate an email and send it to the respective email address with a link to reset their password.
+
+The link to reset the user's password contains a token which is what allows the user to securely reset their password.
+
+By default, the Forgot Password operations send users to the Payload Admin panel to reset their password, but you can customize the generated email to send users to the frontend of your app instead by [overriding the email HTML](/docs/authentication/config#forgot-password).
+
+**Example REST API Forgot Password**:
+
+```ts
+const res = await fetch(`http://localhost:3000/api/[collection-slug]/forgot-password`, {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+  body: JSON.stringify({
+    email: 'dev@payloadcms.com',
+  }),
+})
+```
+
+**Example GraphQL Mutation**:
+
+```
+mutation {
+  forgotPassword[collection-singular-label](email: "dev@payloadcms.com")
+}
+```
+
+**Example Local API forgot password**:
+
+```ts
+const token = await payload.forgotPassword({
+  collection: '[collection-slug]',
+  data: {
+    email: 'dev@payloadcms.com',
+  },
+  disableEmail: false, // you can disable the auto-generation of email via local API
+})
+```
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  You can stop the reset-password email from being sent via using the local API. This is helpful if
+  you need to create user accounts programmatically, but not set their password for them. This
+  effectively generates a reset password token which you can then use to send to a page you create,
+  allowing a user to "complete" their account by setting their password. In the background, you'd
+  use the token to "reset" their password.
+</Banner>
+
+### Reset Password
+
+After a user has "forgotten" their password and a token is generated, that token can be used to send to the reset password operation along with a new password which will allow the user to reset their password securely.
+
+**Example REST API Reset Password**:
+
+```ts
+const res = await fetch(`http://localhost:3000/api/[collection-slug]/reset-password`, {
+  method: 'POST',
+  headers: {
+    'Content-Type': 'application/json',
+  },
+  body: JSON.stringify({
+    token: 'TOKEN_GOES_HERE'
+    password: 'not-today',
+  }),
+});
+
+const json = await res.json();
+
+// JSON will be equal to the following:
+/*
+{
+  user: {
+    email: 'dev@payloadcms.com',
+    createdAt: "2020-12-27T21:16:45.645Z",
+    updatedAt: "2021-01-02T18:37:41.588Z",
+    id: "5ae8f9bde69e394e717c8832"
+  },
+  token: '34o4345324...',
+  exp: 1609619861
+}
+*/
+```
+
+**Example GraphQL Mutation**:
+
+```graphql
+mutation {
+  resetPassword[collection-singular-label](token: "TOKEN_GOES_HERE", password: "not-today")
+}
+```

docs/authentication/overview.mdx

@@ -0,0 +1,181 @@
+---
+title: Authentication Overview
+label: Overview
+order: 10
+desc: Payload provides highly secure user Authentication out of the box, and you can fully customize, override, or remove the default Authentication support.
+keywords: authentication, config, configuration, overview, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+<YouTube
+  id="CT4KafeJjTI"
+  title="Simplified Authentication for Headless CMS: Unlocking Reusability in One Line"
+/>
+
+<Banner>
+  Payload provides for highly secure and customizable user Authentication out of the box, which
+  allows for users to identify themselves to Payload.
+</Banner>
+
+Authentication is used within the Payload Admin panel itself as well as throughout your app(s) themselves however you determine necessary.
+
+![Authentication admin panel functionality](https://payloadcms.com/images/docs/auth-admin.jpg)
+_Admin panel screenshot depicting an Admins Collection with Auth enabled_
+
+**Here are some common use cases of Authentication outside of Payload's dashboard itself:**
+
+- Customer accounts for an ecommerce app
+- Customer accounts for a SaaS product
+- P2P app or social site where users need to log in and manage their profiles
+- Online game where players need to track their progress over time
+
+By default, Payload provides you with a `User` collection that supports Authentication, which is used to access the Admin panel. But, you can add support to one or many Collections of your own. For more information on how to customize, override, or remove the default `User` collection, [click here](/docs/admin/overview#the-admin-user-collection).
+
+### Enabling Auth on a collection
+
+Every Payload Collection can opt-in to supporting Authentication by specifying the `auth` property on the Collection's config to either `true` or to an object containing `auth` options.
+
+**For a full list of all `auth` options, [click here](/docs/authentication/config).**
+
+Simple example collection:
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Admins: CollectionConfig = {
+  slug: 'admins',
+  // highlight-start
+  auth: {
+    tokenExpiration: 7200, // How many seconds to keep the user logged in
+    verify: true, // Require email verification before being allowed to authenticate
+    maxLoginAttempts: 5, // Automatically lock a user out after X amount of failed logins
+    lockTime: 600 * 1000, // Time period to allow the max login attempts
+    // More options are available
+  },
+  // highlight-end
+  fields: [
+    {
+      name: 'role',
+      type: 'select',
+      required: true,
+      options: [
+        'user',
+        'admin',
+        'editor',
+        'developer',
+      ],
+    },
+  ],
+}
+```
+
+**By enabling Authentication on a config, the following modifications will automatically be made to your Collection:**
+
+1. `email` as well as password `salt` & `hash` fields will be added to your Collection's schema
+1. The Admin panel will feature a new set of corresponding UI to allow for changing password and editing email
+1. [A new set of `operations`](/docs/authentication/operations) will be exposed via Payload's REST, Local, and GraphQL APIs
+
+Once enabled, each document that is created within the Collection can be thought of as a `user` - who can make use of commonly required authentication functions such as logging in / out, resetting their password, and more.
+
+### Logging in / out, resetting password, etc.
+
+[Click here](/docs/authentication/operations) for a list of all automatically-enabled Auth operations, including `login`, `logout`, `refresh`, and others.
+
+### Token-based auth
+
+Successfully logging in returns a `JWT` (JSON web token) which is how a user will identify themselves to Payload. By providing this JWT via either an HTTP-only cookie or an `Authorization` header, Payload will automatically identify the user and add its user JWT data to the Express `req`, which is available throughout Payload including within access control, hooks, and more.
+
+You can specify what data gets encoded to the JWT token by setting `saveToJWT` to true in your auth collection fields. If you wish to use a different key other than the field `name`, you can provide it to `saveToJWT` as a string. It is also possible to use `saveToJWT` on fields that are nested in inside groups and tabs. If a group has a `saveToJWT` set it will include the object with all sub-fields in the token. You can set `saveToJWT: false` for any fields you wish to omit. If a field inside a group has `saveToJWT` set, but the group does not, the field will be included at the top level of the token.
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  You can access the logged-in user from access control functions and hooks via the Express{' '}
+  <strong>req</strong>. The logged-in user is automatically added as the <strong>user</strong>{' '}
+  property.
+</Banner>
+
+### HTTP-only cookies
+
+Payload `login`, `logout`, and `refresh` operations make use of HTTP-only cookies for authentication purposes. HTTP-only cookies are a highly secure method of storing identifiable data on a user's device so that Payload can automatically recognize a returning user until their cookie expires. They are totally protected from common XSS attacks and cannot be read at all via JavaScript in the browser.
+
+##### Automatic browser inclusion
+
+Modern browsers automatically include `http-only` cookies when making requests directly to URLs—meaning that if you are running your API on http://example.com, and you have logged in and visit http://example.com/test-page, your browser will automatically include the Payload authentication cookie for you.
+
+##### Using Fetch or other HTTP APIs
+
+However, if you use `fetch` or similar APIs to retrieve Payload resources from its REST or GraphQL API, you need to specify to include credentials (cookies).
+
+Fetch example, including credentials:
+
+```ts
+const response = await fetch('http://localhost:3000/api/pages', {
+  credentials: 'include',
+})
+
+const pages = await response.json()
+```
+
+For more about how to automatically include cookies in requests from your app to your Payload API, [click here](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#Sending_a_request_with_credentials_included).
+
+<Banner type="success">
+  <strong>Tip:</strong>
+  <br />
+  To make sure you have a Payload cookie set properly in your browser after logging in, you can use
+  Chrome's Developer Tools - Application - Cookies - [your-domain-here]. The Chrome Developer tools
+  will still show HTTP-only cookies, even when JavaScript running on the page can't.
+</Banner>
+
+### CSRF Protection
+
+CSRF (cross-site request forgery) attacks are common and dangerous. By using an HTTP-only cookie, Payload removes many XSS vulnerabilities, however, CSRF attacks can still be possible.
+
+For example, let's say you have a very popular app running at coolsite.com. This app allows users to manage finances and send / receive money. As Payload is using HTTP-only cookies, that means that browsers automatically will include cookies when sending requests to your domain - no matter what page created the request.
+
+So, if a user of coolsite.com is logged in and just browsing around on the internet, they might stumble onto a page with bad intentions. That bad page might automatically make requests to all sorts of sites to see if they can find one that they can log into - and coolsite.com might be on their list. If your user was logged in while they visited that evil site, the attacker could do whatever they wanted as if they were your coolsite.com user by just sending requests to the coolsite API (which would automatically include the auth cookie). They could send themselves a bunch of money from your user's account, change the user's password, etc. This is what a CSRF attack is.
+
+<Banner type="warning">
+  <strong>
+    To protect against CSRF attacks, Payload only accepts cookie-based authentication from domains
+    that you explicitly whitelist.
+  </strong>
+</Banner>
+
+To define domains that should allow users to identify themselves via the Payload HTTP-only cookie, use the `csrf` option on the base Payload config to whitelist domains that you trust.
+
+`payload.config.ts`:
+
+```ts
+import { buildConfig } from 'payload/config'
+
+const config = buildConfig({
+  collections: [
+    // collections here
+  ],
+  // highlight-start
+  csrf: [
+    // whitelist of domains to allow cookie auth from
+    'https://your-frontend-app.com',
+    'https://your-other-frontend-app.com',
+  ],
+  // highlight-end
+})
+
+export default config
+```
+
+### Identifying users via the Authorization Header
+
+In addition to authenticating via an HTTP-only cookie, you can also identify users via the `Authorization` header on an HTTP request.
+
+Example:
+
+```ts
+const request = await fetch('http://localhost:3000', {
+  headers: {
+    Authorization: `JWT ${token}`,
+  },
+})
+```
+
+You can retrieve a user's token via the response to `login`, `refresh`, and `me` auth operations.

docs/authentication/using-middleware.mdx

@@ -0,0 +1,56 @@
+---
+title: Using the Payload Auth Middleware
+label: Using the Middleware
+order: 40
+desc: Make full use of Payload's built-in authentication with your own custom Express endpoints by adding Payload's authentication middleware.
+keywords: authentication, middleware, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Because Payload uses your existing Express server, you are free to add whatever logic you need to your app through endpoints of your own. However, Payload does not add its middleware to your Express app itself—instead, it scopes all of its middleware to Payload-specific routers.
+
+This approach has a ton of benefits - it's great for isolation of concerns and limiting scope, but it also means that your additional routes won't have access to Payload's user authentication.
+
+<Banner type="success">
+  You can make full use of Payload's built-in authentication within your own custom Express
+  endpoints by adding Payload's authentication middleware.
+</Banner>
+
+<Banner type="warning">
+  Payload must be initialized before the `payload.authenticate` middleware can be used. This is done
+  by calling `payload.init()` prior to adding the middleware.
+</Banner>
+
+Example in `server.js`:
+
+```ts
+import express from 'express'
+import payload from 'payload'
+
+const app = express()
+
+const start = async () => {
+  await payload.init({
+    secret: 'PAYLOAD_SECRET_KEY',
+    express: app,
+  })
+
+  const router = express.Router()
+
+  // Note: Payload must be initialized before the `payload.authenticate` middleware can be used
+  router.use(payload.authenticate) // highlight-line
+
+  router.get('/', (req, res) => {
+    if (req.user) {
+      return res.send(`Authenticated successfully as ${req.user.email}.`)
+    }
+
+    return res.send('Not authenticated')
+  })
+
+  app.use('/some-route-here', router)
+
+  app.listen(3000)
+}
+
+start()
+```

docs/cloud/configuration.mdx

@@ -0,0 +1,61 @@
+---
+title: Project Configuration
+label: Configuration
+order: 20
+desc: Quickly configure and deploy your Payload Cloud project in a few simple steps.
+keywords: configuration, config, settings, project, cloud, payload cloud, deploy, deployment
+---
+
+### Select your plan
+
+Once you have created a project, you will need to select your plan. This will determine the resources that are allocated to your project and the features that are available to you.
+
+<Banner type="success">
+  Note: All Payload Cloud teams that deploy a project require a card on file. This helps us prevent
+  fraud and abuse on our platform. If you select a plan with a free trial, you will not be charged
+  until your trial period is over. We’ll remind you 7 days before your trial ends and you can cancel
+  anytime.
+</Banner>
+
+### Project Details
+
+| Option           | Description                                                                                                                                                                                                                                   |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Region**       | Select the region closest to your audience. This will ensure the fastest communication between your data and your client.                                                                                                                     |
+| **Project Name** | A name for your project. You can change this at any time.                                                                                                                                                                                     |
+| **Project Slug** | Choose a unique slug to identify your project. This needs to be unique for your team and you can change it any time.                                                                                                                          |
+| **Team**         | Select the team you want to create the project under. If this is your first project, a personal team will be created for you automatically. You can modify your team settings and invite new members at any time from the Team Settings page. |
+
+### Build Settings
+
+If you are deploying a new project from a template, the following settings will be automatically configured for you. If you are using your own repository, you need to make sure your build settings are accurate for your project to deploy correctly.
+
+| Option               | Description                                                                                                                                                       |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Root Directory**   | The folder where your `package.json` file lives.                                                                                                                  |
+| **Install Command**  | The command used to install your modules, for example: `yarn install` or `npm install`                                                                            |
+| **Build Command**    | The command used to build your application, for example: `yarn build` or `npm run build`                                                                          |
+| **Serve Command**    | The command used to serve your application, for example: `yarn serve` or `npm run serve`                                                                          |
+| **Branch to Deploy** | Select the branch of your repository that you want to deploy from. This is the branch that will be used to build your project when you commit new changes.        |
+| **Default Domain**   | Set a default domain for your project. This must be unique and you will not able to change it. You can always add a custom domain later in your project settings. |
+
+### Environment Variables
+
+Any of the features in Payload Cloud that require environment variables will automatically be provided to your application. If your app requires any custom environment variables, you can set them here.
+
+<Banner type="warning">
+  Note: For security reasons, any variables you wish to provide to the Admin panel must be prefixed
+  with `PAYLOAD_PUBLIC_`.  Learn more
+  [here](https://payloadcms.com/docs/admin/webpack#admin-environment-vars).
+</Banner>
+
+### Payment
+
+Payment methods can be set per project and can be updated any time. You can use team’s default payment method, or add a new one. Modify your payment methods in your Project settings / Team settings.
+
+<Banner type="success">
+  <strong>Note:</strong> All Payload Cloud teams that deploy a project require a card on file. This
+  helps us prevent fraud and abuse on our platform. If you select a plan with a free trial, you will
+  not be charged until your trial period is over. We’ll remind you 7 days before your trial ends and
+  you can cancel anytime.
+</Banner>

docs/cloud/creating-a-project.mdx

@@ -0,0 +1,51 @@
+---
+title: Getting Started
+label: Getting Started
+order: 10
+desc: Get started with Payload Cloud, a deployment solution specifically designed for Node + MongoDB applications.
+keywords: cloud, hosted, database, storage, email, deployment, serverless, node, mongodb, s3, aws, cloudflare, atlas, resend, payload, cms
+---
+
+A deployment solution specifically designed for Node.js + MongoDB applications, offering seamless deployment of your entire stack in one place. You can get started in minutes with a one-click template or bring your own codebase with you.
+
+Payload Cloud offers various plans tailored to meet your specific needs, including a MongoDB Atlas database, S3 file storage, and email delivery powered by [Resend](https://resend.com). To see a full breakdown of features and plans, see our [Cloud Pricing page](https://payloadcms.com/cloud-pricing).
+
+To get started, you first need to create an account. Head over to [the login screen](https://payloadcms.com/login) and **Register for Free**.
+
+<Banner type="success">
+  To create your first project, you can either select [a template](#starting-from-a-template) or
+  [import an existing project](#importing-from-an-existing-codebase) from GitHub.
+</Banner>
+
+## Starting from a Template
+
+Templates come preconfigured and provide a one-click solution to quickly deploy a new application.
+
+![Screen for creating a new project from a template](https://payloadcms.com/images/docs/cloud/create-from-template.jpg)
+_Creating a new project from a template._
+
+After creating an account, select your desired template from the Projects page. At this point, you need to connect to authorize the Payload Cloud application with your GitHub account. Click Continue with GitHub and follow the prompts to authorize the app.
+
+Next, select your `GitHub Scope`. If you belong to multiple organizations, they will show up here. If you do not see the organization you are looking for, you may need to adjust your GitHub app permissions.
+
+After selecting your scope, create a unique `repository name` and select whether you want your repository to be public or private on GitHub.
+
+<Banner type="warning">
+  <strong>Note:</strong> Public repositories can be accessed by anyone online, while private
+  repositories grant access only to you and anyone you explicitly authorize.
+</Banner>
+
+Once you are ready, click **Create Project**. This will clone the selected template to a new repository in your GitHub account, and take you to the configuration page to set up your project for deployment.
+
+## Importing from an Existing Codebase
+
+Payload Cloud works for any Node.js + MongoDB app. From the New Project page, select **import an existing Git codebase**. Choose the organization and select the repository you want to import. From here, you will be taken to the configuration page to set up your project for deployment.
+
+![Screen for creating a new project from an existing repository](https://payloadcms.com/images/docs/cloud/create-from-existing.jpg)
+_Creating a new project from an existing repository._
+
+<Banner type="warning">
+  <strong>Note:</strong> In order to make use of the features of Payload Cloud in your own codebase,
+  you will need to add the [Cloud Plugin](https://github.com/payloadcms/plugin-cloud) to your
+  Payload app.
+</Banner>

docs/cloud/projects.mdx

@@ -0,0 +1,109 @@
+---
+title: Cloud Projects
+label: Projects
+order: 40
+desc: Manage your Payload Cloud projects.
+keywords: cloud, payload cloud, projects, project, overview, database, file storage, build settings, environment variables, custom domains, email, developing locally
+---
+
+### Overview
+
+<Banner>
+  The overview tab shows your most recent deployment, along with build and deployment logs. From
+  here, you can see your live URL, deployment details like timestamps and commit hash, as well as
+  the status of your deployment. You can also trigger a redeployment manually, which will rebuild
+  your project using the current configuration.
+</Banner>
+
+![Payload Cloud Overview Page](https://payloadcms.com/images/docs/cloud/overview-page.jpg)
+_A screenshot of the Overview page for a Cloud project._
+
+### Database
+
+Your Payload Cloud project comes with a MongoDB serverless Atlas DB instance or a Dedicated Atlas cluster, depending on your plan. To interact with your cloud database, you will be provided with a MongoDB connection string. This can be found under the **Database** tab of your project.
+
+`mongodb+srv://your_connection_string`
+
+### File Storage
+
+Payload Cloud gives you S3 file storage backed by Cloudflare as a CDN, and this plugin extends Payload so that all of your media will be stored in S3 rather than locally.
+
+AWS Cognito is used for authentication to your S3 bucket. The [Payload Cloud Plugin](https://github.com/payloadcms/plugin-cloud) will automatically pick up these values. These values are only if you'd like to access your files directly, outside of Payload Cloud.
+
+### Build Settings
+
+You can update settings from your Project’s Settings tab. Changes to your build settings will trigger a redeployment of your project.
+
+### Environment Variables
+
+From the Environment Variables page of the Settings tab, you can add, update and delete variables for use in your project. Like build settings, these changes will trigger a redeployment of your project.
+
+<Banner>
+  Note: For security reasons, any variables you wish to provide to the Admin panel must be prefixed
+  with `PAYLOAD_PUBLIC_`.  Learn more
+  [here](https://payloadcms.com/docs/admin/webpack#admin-environment-vars).
+</Banner>
+
+### Custom Domains
+
+With Payload Cloud, you can add custom domain names to your project. To do so, first go to the Domains page of the Settings tab of your project. Here you can see your default domain. To add a new domain, type in the domain name you wish to use.
+
+<Banner>
+  Note: do not include the protocol (http:// or https://) or any paths (/page). Only include the
+  domain name and extension, and optionally a subdomain. - your-domain.com - backend.your-domain.com
+</Banner>
+
+Once you click save, a DNS record will be generated for your domain name to point to your live project. Add this record into your DNS provider’s records, and once the records are resolving properly (this can take 1hr to 48hrs in some cases), your domain will now to point to your live project.
+
+You will also need to configure your Payload project to use your specified domain. In your `payload.config.ts` file, specify your `serverURL` with your domain:
+
+```ts
+export default buildConfig({
+  serverURL: 'https://example.com',
+  // the rest of your config,
+})
+```
+
+### Email
+
+Powered by [Resend](https://resend.com), Payload Cloud comes with integrated email support out of the box. No configuration is needed, and you can use `payload.sendEmail()` to send email right from your Payload app. To learn more about sending email with Payload, checkout the [Email Configuration](https://payloadcms.com/docs/email/overview) overview.
+
+If you are on the Pro or Enterprise plan, you can add your own custom Email domain name. From the Email page of your project’s Settings, add the domain you wish to use for email delivery. This will generate a set of DNS records. Add these records to your DNS provider and click verify to check that your records are resolving properly. Once verified, your emails will now be sent from your custom domain name.
+
+### Developing Locally
+
+To make changes to your project, you will need to clone the repository defined in your project settings to your local machine. In order to run your project locally, you will need configure your local environment first. Refer to your repository’s `README.md` file to see the steps needed for your specific template.
+
+From there, you are ready to make updates to your project. When you are ready to make your changes live, commit your changes to the branch you specified in your Project settings, and your application will automatically trigger a redeploy and build from your latest commit.
+
+### Cloud Plugin
+
+Projects generated from a template will come pre-configured with the official Cloud Plugin, but if you are using your own repository you will need to add this into your project. To do so, add the plugin to your Payload config:
+
+`yarn add @payloadcms/plugin-cloud`
+
+```js
+import { payloadCloud } from '@payloadcms/plugin-cloud'
+import { buildConfig } from 'payload/config'
+
+export default buildConfig({
+  plugins: [payloadCloud()],
+  // rest of config
+})
+```
+
+<Banner type="warning">
+  **Note:** If your Payload config already has an email with transport, this will take precedence
+  over Payload Cloud's email service.
+</Banner>
+
+##### **Optional configuration**
+
+If you wish to opt-out of any Payload cloud features, the plugin also accepts options to do so.
+
+```js
+payloadCloud({
+  storage: false, // Disable file storage
+  email: false, // Disable email delivery
+})
+```

docs/cloud/teams.mdx

@@ -0,0 +1,35 @@
+---
+title: Cloud Teams
+label: Teams
+order: 30
+desc: Manage your Payload Cloud team and billing settings.
+keywords: team, teams, billing, subscription, payment, plan, plans, cloud, payload cloud
+---
+
+<Banner>
+  Within Payload Cloud, the team management feature offers you the ability to manage your
+  organization, team members, billing, and subscription settings.
+</Banner>
+
+![Payload Cloud Team Settings](https://payloadcms.com/images/docs/cloud/team-settings.jpg)
+_A screenshot of the Team Settings page._
+
+### Members
+
+Each team has members that can interact with your projects. You can invite multiple people to your team and each individual can belong to more than one team. You can assign them either `owner` or `user` permissions. Owners are able to make admin-only changes, such as deleting projects, and editing billing information.
+
+### Adding Members
+
+To add a new member to your team, visit your Team’s Settings page, and click “Invite Teammate”. You can then add their email address, and assign their role. Press “Save” to send the invitations, which will send an email to the invited team member where they can create a new account.
+
+### Billing
+
+Users can update billing settings and subscriptions for any teams where they are designated as an `owner`. To make updates to the team’s payment methods, visit the Billing page under the Team Settings tab. You can add new cards, delete cards, and set a payment method as a default. The default payment method will be used in the event that another payment method fails.
+
+### Subscriptions
+
+From the Subscriptions page, a team owner can see all current plans for their team. From here, you can see the price of each plan, if there is an active trial, and when you will be billed next.
+
+### Invoices
+
+The Invoices page will you show you the invoices for your account, as well as the status on their payment.

docs/configuration/collections.mdx

@@ -0,0 +1,233 @@
+---
+title: Collection Configs
+label: Collections
+order: 20
+desc: Structure your Collections for your needs by defining fields, adding slugs and labels, establishing access control, tying in hooks, setting timestamps and more.
+keywords: collections, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload Collections are defined through configs of their own, and you can define as many as your application needs. Each
+Collection will scaffold a new collection automatically in your database of choice, based on fields that you define.
+
+It's often best practice to write your Collections in separate files and then import them into the main Payload config.
+
+## Options
+
+| Option            | Description                                                                                                                                                                                                              |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **`slug`** \*     | Unique, URL-friendly string that will act as an identifier for this Collection.                                                                                                                                          |
+| **`fields`** \*   | Array of field types that will determine the structure and functionality of the data stored within this Collection. [Click here](/docs/fields/overview) for a full list of field types as well as how to configure them. |
+| **`labels`**      | Singular and plural labels for use in identifying this Collection throughout Payload. Auto-generated from slug if not defined.                                                                                           |
+| **`admin`**       | Admin-specific configuration. See below for [more detail](#admin-options).                                                                                                                                               |
+| **`hooks`**       | Entry points to "tie in" to Collection actions at specific points. [More](/docs/hooks/overview#collection-hooks)                                                                                                         |
+| **`access`**      | Provide access control functions to define exactly who should be able to do what with Documents in this Collection. [More](/docs/access-control/overview/#collections)                                                   |
+| **`auth`**        | Specify options if you would like this Collection to feature authentication. For more, consult the [Authentication](/docs/authentication/config) documentation.                                                          |
+| **`upload`**      | Specify options if you would like this Collection to support file uploads. For more, consult the [Uploads](/docs/upload/overview) documentation.                                                                         |
+| **`timestamps`**  | Set to false to disable documents' automatically generated `createdAt` and `updatedAt` timestamps.                                                                                                                       |
+| **`versions`**    | Set to true to enable default options, or configure with object properties. [More](/docs/versions/overview#collection-config)                                                                                            |
+| **`endpoints`**   | Add custom routes to the REST API. Set to `false` to disable routes. [More](/docs/rest-api/overview#custom-endpoints)                                                                                                    |
+| **`graphQL`**     | An object with `singularName` and `pluralName` strings used in schema generation. Auto-generated from slug if not defined. Set to `false` to disable GraphQL.                                                            |
+| **`typescript`**  | An object with property `interface` as the text used in schema generation. Auto-generated from slug if not defined.                                                                                                      |
+| **`defaultSort`** | Pass a top-level field to sort by default in the collection List view. Prefix the name of the field with a minus symbol ("-") to sort in descending order.                                                               |
+| **`custom`**      | Extension point for adding custom data (e.g. for plugins)                                                                                                                                                                |
+
+_\* An asterisk denotes that a property is required._
+
+#### Simple collection example
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Orders: CollectionConfig = {
+  slug: 'orders',
+  fields: [
+    {
+      name: 'total',
+      type: 'number',
+      required: true,
+    },
+    {
+      name: 'placedBy',
+      type: 'relationship',
+      relationTo: 'customers',
+      required: true,
+    },
+  ],
+}
+```
+
+#### More collection config examples
+
+You can find an assortment
+of [example collection configs](https://github.com/payloadcms/public-demo/tree/master/src/collections) in the Public
+Demo source code on GitHub.
+
+### Admin options
+
+You can customize the way that the Admin panel behaves on a collection-by-collection basis by defining the `admin`
+property on a collection's config.
+
+| Option                       | Description                                                                                                                                                                                           |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `group`                      | Text used as a label for grouping collection and global links together in the navigation.                                                                                                             |
+| `hidden`                     | Set to true or a function, called with the current user, returning true to exclude this collection from navigation and admin routing.                                                                 |
+| `hooks`                      | Admin-specific hooks for this collection. [More](#admin-hooks)                                                                                                                                        |
+| `useAsTitle`                 | Specify a top-level field to use for a document title throughout the Admin panel. If no field is defined, the ID of the document is used as the title.                                                |
+| `description`                | Text or React component to display below the Collection label in the List view to give editors more information.                                                                                      |
+| `defaultColumns`             | Array of field names that correspond to which columns to show by default in this collection's List view.                                                                                              |
+| `disableDuplicate `          | Disables the "Duplicate" button while editing documents within this collection.                                                                                                                       |
+| `hideAPIURL`                 | Hides the "API URL" meta field while editing documents within this collection.                                                                                                                        |
+| `enableRichTextLink`         | The [Rich Text](/docs/fields/rich-text) field features a `Link` element which allows for users to automatically reference related documents within their rich text. Set to `true` by default.         |
+| `enableRichTextRelationship` | The [Rich Text](/docs/fields/rich-text) field features a `Relationship` element which allows for users to automatically reference related documents within their rich text. Set to `true` by default. |
+| `preview`                    | Function to generate preview URLS within the Admin panel that can point to your app. [More](#preview).                                                                                                |
+| `livePreview`                | Enable real-time editing for instant visual feedback of your front-end application. [More](/docs/live-preview/overview).                                                                              |
+| `components`                 | Swap in your own React components to be used within this collection. [More](/docs/admin/components#collections)                                                                                       |
+| `listSearchableFields`       | Specify which fields should be searched in the List search view. [More](#list-searchable-fields)                                                                                                      |
+| **`pagination`**             | Set pagination-specific options for this collection. [More](#pagination)                                                                                                                              |
+
+### Preview
+
+Collection `admin` options can accept a `preview` function that will be used to generate a link pointing to the frontend
+of your app to preview data.
+
+If the function is specified, a Preview button will automatically appear in the corresponding collection's Edit view.
+Clicking the Preview button will link to the URL that is generated by the function.
+
+**The preview function accepts two arguments:**
+
+1. The document being edited
+1. An `options` object, containing `locale` and `token` properties. The `token` is the currently logged-in user's JWT.
+
+**Example collection with preview function:**
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Posts: CollectionConfig = {
+  slug: 'posts',
+  fields: [
+    {
+      name: 'slug',
+      type: 'text',
+      required: true,
+    },
+  ],
+  admin: {
+    preview: (doc, { locale }) => {
+      if (doc?.slug) {
+        return `https://bigbird.com/preview/posts/${doc.slug}?locale=${locale}`
+      }
+
+      return null
+    },
+  },
+}
+```
+
+### Pagination
+
+Here are a few options that you can specify options for pagination on a collection-by-collection basis:
+
+| Option         | Description                                                                                         |
+|----------------|-----------------------------------------------------------------------------------------------------|
+| `defaultLimit` | Integer that specifies the default per-page limit that should be used. Defaults to 10.              |
+| `limits`       | Provide an array of integers to use as per-page options for admins to choose from in the List view. |
+
+### Access control
+
+You can specify extremely granular access control (what users can do with documents in a collection) on a collection by
+collection basis. To learn more, go to the [Access Control](/docs/access-control/overview) docs.
+
+### Hooks
+
+Hooks are a powerful way to extend collection functionality and execute your own logic, and can be defined on a
+collection by collection basis. To learn more, go to the [Hooks](/docs/hooks/overview) documentation.
+
+### Field types
+
+Collections support all field types that Payload has to offer—including simple fields like text and checkboxes all the
+way to more complicated layout-building field groups like Blocks. [Click here](/docs/fields/overview) to learn more
+about field types.
+
+### List Searchable Fields
+
+In the List view, there is a "search" box that allows you to quickly find a document with a search. By default, it
+searches on the ID field. If you have `admin.useAsTitle` defined, the list search will use that field. However, you can
+define more than one field to search to make it easier on your admin editors to find the data they need.
+
+For example, let's say you have a Posts collection with `title`, `metaDescription`, and `tags` fields - and you want all
+three of those fields to be searchable in the List view. You can simply
+add `admin.listSearchableFields: ['title', 'metaDescription', 'tags']` - and the admin UI will automatically search on
+those three fields plus the ID field.
+
+<Banner type="warning">
+  <strong>Note:</strong>
+  <br />
+  If you are adding <strong>listSearchableFields</strong>, make sure you index each of these fields
+  so your admin queries can remain performant.
+</Banner>
+
+### Admin Hooks
+
+In addition to collection hooks themselves, Payload provides for admin UI-specific hooks that you can leverage.
+
+**`beforeDuplicate`**
+
+The `beforeDuplicate` hook is an async function that accepts an object containing the data to duplicate, as well as the
+locale of the doc to duplicate. Within this hook, you can modify the data to be duplicated, which is useful in cases
+where you have unique fields that need to be incremented or similar, as well as if you want to automatically modify a
+document's `title`.
+
+Example:
+
+```ts
+import { BeforeDuplicate, CollectionConfig } from 'payload/types'
+// Your auto-generated Page type
+import { Page } from '../payload-types.ts'
+
+const beforeDuplicate: BeforeDuplicate<Page> = ({ data }) => {
+  return {
+    ...data,
+    title: `${data.title} Copy`,
+    uniqueField: data.uniqueField ? `${data.uniqueField}-copy` : '',
+  }
+}
+
+export const Page: CollectionConfig = {
+  slug: 'pages',
+  admin: {
+    hooks: {
+      beforeDuplicate,
+    },
+  },
+  fields: [
+    {
+      name: 'title',
+      type: 'text',
+    },
+    {
+      name: 'uniqueField',
+      type: 'text',
+      unique: true,
+    },
+  ],
+}
+```
+
+### TypeScript
+
+You can import collection types as follows:
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+// This is the type used for incoming collection configs.
+// Only the bare minimum properties are marked as required.
+```
+
+```ts
+import { SanitizedCollectionConfig } from 'payload/types'
+
+// This is the type used after an incoming collection config is fully sanitized.
+// Generally, this is only used internally by Payload.
+```

docs/configuration/express.mdx

@@ -0,0 +1,81 @@
+---
+title: Express
+label: Express
+order: 60
+desc: Payload utilizes Express middleware packages, you can customize how they work by passing in configuration options.
+keywords: config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload utilizes a few Express-specific middleware packages within its own routers. You can customize how they work by passing in configuration options to the main Payload config's `express` property.
+
+### Custom Middleware
+
+Payload allows you to pass in custom Express middleware to be used on all of the routes it opens. This is useful for adding logging or any other custom functionality to your endpoints.
+
+There are 2 exposed properties. Each property is an array of middleware functions.
+
+- `preMiddleware` - runs before any of the Payload middleware
+- `postMiddleware` - runs after all of the Payload middleware
+
+```ts
+{
+  express: {
+    preMiddleware: [
+      (req, res, next) => {
+        // do something
+        next()
+      }
+    ],
+    postMiddleware: [
+      (req, res, next) => {
+        // do something
+        next()
+      }
+    ]
+  }
+}
+
+// Example logging middleware function
+const requestLoggerMiddleware = (req, res, next) => {
+  req.payload.logger.info(`request: ${req.method} ${req.url}`)
+  next()
+}
+```
+
+### JSON
+
+`express.json()` is used to parse JSON body content into JavaScript objects accessible on the Express `req`. Payload allows you to customize all of the `json` method's options. Common examples of customization use-cases are increasing the max allowed JSON body size which defaults to `2MB`.
+
+**Example payload.config.js for how to increase the max JSON size allowed to be sent to Payload endpoints:**
+
+```js
+{
+	express: {
+		json: {
+			limit: '4mb',
+		}
+	}
+}
+```
+
+You can find a list of all available options that are able to be passed to `express.json()` [here](https://expressjs.com/en/api.html).
+
+### Compression
+
+Payload uses the `compression` package to optimize transfer size for all of the routes it opens, and you can pass customization options through the Payload config.
+
+To customize compression options, pass an object to the Payload config's `express` property.
+
+**Example payload.config.js:**
+
+```js
+{
+  express: {
+    compression: {
+      // settings go here
+    }
+  }
+}
+```
+
+Typically, the default options for this package are suitable. However, for a list of all available customization options, [click here](http://expressjs.com/en/resources/middleware/compression.html).

docs/configuration/globals.mdx

@@ -0,0 +1,142 @@
+---
+title: Global Configs
+label: Globals
+order: 30
+desc: Set up your Global config for your needs by defining fields, adding slugs and labels, establishing access control, tying in hooks and more.
+keywords: globals, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Global configs are in many ways similar to [Collections](/docs/configuration/collections). The big difference is that Collections will potentially contain _many_ documents, while a Global is a "one-off". Globals are perfect for things like header nav, site-wide banner alerts, app-wide localized strings, and other "global" data that your site or app might rely on.
+
+As with Collection configs, it's often best practice to write your Globals in separate files and then import them into the main Payload config.
+
+## Options
+
+| Option             | Description                                                                                                                                                                                                          |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`slug`** \*      | Unique, URL-friendly string that will act as an identifier for this Global.                                                                                                                                          |
+| **`fields`** \*    | Array of field types that will determine the structure and functionality of the data stored within this Global. [Click here](/docs/fields/overview) for a full list of field types as well as how to configure them. |
+| **`label`**        | Text for the name in the Admin panel or an object with keys for each language. Auto-generated from slug if not defined.                                                                                              |
+| **`description`**  | Text or React component to display below the Global header to give editors more information.                                                                                                                         |
+| **`admin`**        | Admin-specific configuration. See below for [more detail](/docs/configuration/globals#admin-options).                                                                                                                |
+| **`hooks`**        | Entry points to "tie in" to collection actions at specific points. [More](/docs/hooks/overview#global-hooks)                                                                                                         |
+| **`access`**       | Provide access control functions to define exactly who should be able to do what with this Global. [More](/docs/access-control/overview/#globals)                                                                    |
+| **`versions`**     | Set to true to enable default options, or configure with object properties. [More](/docs/versions/overview#globals-config)                                                                                           |
+| **`endpoints`**    | Add custom routes to the REST API. [More](/docs/rest-api/overview#custom-endpoints)                                                                                                                                  |
+| **`graphQL.name`** | Text used in schema generation. Auto-generated from slug if not defined.                                                                                                                                             |
+| **`typescript`**   | An object with property `interface` as the text used in schema generation. Auto-generated from slug if not defined.                                                                                                  |
+| **`custom`**       | Extension point for adding custom data (e.g. for plugins)                                                                                                                                                            |
+
+_\* An asterisk denotes that a property is required._
+
+#### Simple Global example
+
+```ts
+import { GlobalConfig } from 'payload/types'
+
+const Nav: GlobalConfig = {
+  slug: 'nav',
+  fields: [
+    {
+      name: 'items',
+      type: 'array',
+      required: true,
+      maxRows: 8,
+      fields: [
+        {
+          name: 'page',
+          type: 'relationship',
+          relationTo: 'pages', // "pages" is the slug of an existing collection
+          required: true,
+        },
+      ],
+    },
+  ],
+}
+
+export default Nav
+```
+
+#### Global config example
+
+You can find an [example Global config](https://github.com/payloadcms/public-demo/blob/master/src/globals/MainMenu.ts) in the Public Demo source code on GitHub.
+
+### Admin options
+
+You can customize the way that the Admin panel behaves on a Global-by-Global basis by defining the `admin` property on a Global's config.
+
+| Option       | Description                                                                                                                               |
+| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `group`      | Text used as a label for grouping collection and global links together in the navigation.                                                 |
+| `hidden`     | Set to true or a function, called with the current user, returning true to exclude this global from navigation and admin routing.         |
+| `components` | Swap in your own React components to be used within this Global. [More](/docs/admin/components#globals)                                   |
+| `preview`    | Function to generate a preview URL within the Admin panel for this global that can point to your app. [More](#preview).                   |
+| `livePreview`| Enable real-time editing for instant visual feedback of your front-end application. [More](/docs/live-preview/overview).                  |
+| `hideAPIURL` | Hides the "API URL" meta field while editing documents within this collection.                                                            |
+
+### Preview
+
+Global `admin` options can accept a `preview` function that will be used to generate a link pointing to the frontend of your app to preview data.
+
+If the function is specified, a Preview button will automatically appear in the corresponding global's Edit view. Clicking the Preview button will link to the URL that is generated by the function.
+
+**The preview function accepts two arguments:**
+
+1. The document being edited
+1. An `options` object, containing `locale` and `token` properties. The `token` is the currently logged-in user's JWT.
+
+**Example global with preview function:**
+
+```ts
+import { GlobalConfig } from 'payload/types'
+
+export const MyGlobal: GlobalConfig = {
+  slug: 'my-global',
+  fields: [
+    {
+      name: 'slug',
+      type: 'text',
+      required: true,
+    },
+  ],
+  admin: {
+    preview: (doc, { locale }) => {
+      if (doc?.slug) {
+        return `https://bigbird.com/preview/${doc.slug}?locale=${locale}`
+      }
+
+      return null
+    },
+  },
+}
+```
+
+### Access control
+
+As with Collections, you can specify extremely granular access control (what users can do with this Global) on a Global-by-Global basis. However, Globals only have `update` and `read` access control due to their nature of only having one document. To learn more, go to the [Access Control](/docs/access-control/overview) docs.
+
+### Hooks
+
+Globals also fully support a smaller subset of Hooks. To learn more, go to the [Hooks](/docs/hooks/overview) documentation.
+
+### Field types
+
+Globals support all field types that Payload has to offer—including simple fields like text and checkboxes all the way to more complicated layout-building field groups like Blocks. [Click here](/docs/fields/overview) to learn more about field types.
+
+### TypeScript
+
+You can import global types as follows:
+
+```ts
+import { GlobalConfig } from 'payload/types'
+
+// This is the type used for incoming global configs.
+// Only the bare minimum properties are marked as required.
+```
+
+```ts
+import { SanitizedGlobalConfig } from 'payload/types'
+
+// This is the type used after an incoming global config is fully sanitized.
+// Generally, this is only used internally by Payload.
+```

docs/configuration/i18n.mdx

@@ -0,0 +1,110 @@
+---
+title: I18n
+label: I18n
+order: 40
+desc: Manage and customize internationalization support in your CMS editor experience
+keywords: internationalization, i18n, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Not only does Payload support managing localized content, it also has internationalization support so that admin users can work in their preferred language. Payload's i18n support is built on top of [i18next](https://www.i18next.com). It comes included by default and can be extended in your config.
+
+While Payload's built-in features come translated, you may want to also translate parts of your project's configuration too. This is possible in places like collections and globals labels and groups, field labels, descriptions and input placeholder text. The admin UI will display all the correct translations you provide based on the user's language.
+
+Here is an example of a simple collection supporting both English and Spanish editors:
+
+```ts
+import { CollectionConfig } from 'payload/types'
+
+export const Articles: CollectionConfig = {
+  slug: 'articles',
+  labels: {
+    singular: {
+      en: 'Article',
+      es: 'Artículo',
+    },
+    plural: {
+      en: 'Articles',
+      es: 'Artículos',
+    },
+  },
+  admin: {
+    group: { en: 'Content', es: 'Contenido' },
+  },
+  fields: [
+    {
+      name: 'title',
+      type: 'text',
+      label: {
+        en: 'Title',
+        es: 'Título',
+      },
+      admin: {
+        placeholder: { en: 'Enter title', es: 'Introduce el título' },
+      },
+    },
+    {
+      name: 'type',
+      type: 'radio',
+      options: [
+        {
+          value: 'news',
+          label: { en: 'News', es: 'Noticias' },
+        }, // etc...
+      ],
+    },
+  ],
+}
+```
+
+### Admin UI
+
+The Payload admin panel reads the language settings of a user's browser and display all text in that language, or will fall back to English if the user's language is not yet supported.
+After a user logs in, they can change their language selection in the `/account` view.
+
+<Banner>
+  <strong>Note:</strong>
+  <br />
+  If there is a language that Payload does not yet support, we accept code
+  [contributions](https://github.com/payloadcms/payload/blob/main/contributing.md).
+</Banner>
+
+### Node Express
+
+Payload's backend uses express middleware to set the language on incoming requests before they are handled. This allows backend validation to return error messages in the user's own language or system generated emails to be sent using the correct translation. You can make HTTP requests with the `accept-language` header and Payload will use that language.
+
+Anywhere in your Payload app that you have access to the `req` object, you can access i18next's extensive internationalization features assigned to `req.i18n`. To access text translations you can use `req.t('namespace:key')`.
+
+Read the i18next [API documentation](https://www.i18next.com/overview/api) to learn more.
+
+### Configuration Options
+
+In your Payload config, you can add translations and customize the settings in `i18n`. Payload will use your custom options and merge it with the default, allowing you to override the settings Payload provides.
+
+**Example Payload config extending i18n:**
+
+```ts
+import { buildConfig } from 'payload/config'
+
+export default buildConfig({
+  //...
+  i18n: {
+    fallbackLng: 'en', // default
+    debug: false, // default
+    resources: {
+      en: {
+        custom: {
+          // namespace can be anything you want
+          key1: 'Translation with {{variable}}', // translation
+        },
+        // override existing translation keys
+        general: {
+          dashboard: 'Home',
+        },
+      },
+    },
+  },
+  //...
+})
+```
+
+See the i18next [configuration options](https://www.i18next.com/overview/configuration-options) to learn more.

docs/configuration/localization.mdx

@@ -0,0 +1,180 @@
+---
+title: Localization
+label: Localization
+order: 50
+desc: Add and maintain as many locales as you need by adding Localization to your Payload config, set options for default locale, fallbacks, fields and more.
+keywords: localization, internationalization, i18n, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+Payload features deep field-based localization support. Maintaining as many locales as you need is easy. All localization support is opt-in by default. To do so, follow the two steps below.
+
+### Enabling in the Payload config
+
+Add the `localization` property to your Payload config to enable localization project-wide. You'll need to provide a list of all locales that you'd like to support as well as set a few other options.
+
+**Example Payload config set up for localization:**
+
+```ts
+import { buildConfig } from 'payload/config'
+
+export default buildConfig({
+  collections: [
+    // collections go here
+  ],
+  localization: {
+    locales: ['en', 'es', 'de'],
+    defaultLocale: 'en',
+    fallback: true,
+  },
+})
+```
+
+**Example Payload config set up for localization with full locales objects:**
+
+```ts
+import { buildConfig } from 'payload/config'
+
+export default buildConfig({
+  collections: [
+    // collections go here
+  ],
+  localization: {
+    locales: [
+      {
+        label: 'English',
+        code: 'en',
+      },
+      {
+        label: 'Arabic',
+        code: 'ar',
+        // opt-in to setting default text-alignment on Input fields to rtl (right-to-left) when current locale is rtl
+        rtl: true,
+      },
+    ],
+    defaultLocale: 'en',
+    fallback: true,
+  },
+})
+```
+
+**Here is a brief explanation of each of the options available within the `localization` property:**
+
+**`locales`**
+
+Array-based list of all locales that you would like to support. These can be strings of locale codes or objects with a `label`, a locale `code`, and the `rtl` (right-to-left) property. The locale codes do not need to be in any specific format. It's up to you to define how to represent your locales. Common patterns are to use two-letter ISO 639 language codes or four-letter language and country codes (ISO 3166‑1) such as `en-US`, `en-UK`, `es-MX`, etc.
+
+**`defaultLocale`**
+
+Required string that matches one of the locale codes from the array provided. By default, if no locale is specified, documents will be returned in this locale.
+
+**`fallback`**
+
+Boolean enabling "fallback" locale functionality. If a document is requested in a locale, but a field does not have a localized value corresponding to the requested locale, then if this property is enabled, the document will automatically fall back to the fallback locale value. If this property is not enabled, the value will not be populated.
+
+### Field by field localization
+
+Payload localization works on a **field** level—not a document level. In addition to configuring the base Payload config to support localization, you need to specify each field that you would like to localize.
+
+**Here is an example of how to enable localization for a field:**
+
+```js
+{
+  name: 'title',
+  type: 'text',
+  // highlight-start
+  localized: true,
+  // highlight-end
+}
+```
+
+With the above configuration, the `title` field will now be saved in the database as an object of all locales instead of a single string.
+
+All field types with a `name` property support the `localized` property—even the more complex field types like `array`s and `block`s.
+
+<Banner>
+  <strong>Note:</strong>
+  <br />
+  Enabling localization for field types that support nested fields will automatically create
+  localized "sets" of all fields contained within the field. For example, if you have a page layout
+  using a blocks field type, you have the choice of either localizing the full layout, by enabling
+  localization on the top-level blocks field, or only certain fields within the layout.
+</Banner>
+
+<Banner type="warning">
+  <strong>Important:</strong>
+  <br />
+  When converting an existing field to or from `localized: true` the data structure in the document
+  will change for this field and so existing data for this field will be lost. Before changing the
+  localization setting on fields with existing data, you may need to consider a field migration
+  strategy.
+</Banner>
+
+### Retrieving localized docs
+
+When retrieving documents, you can specify which locale you'd like to receive as well as which fallback locale should be used.
+
+##### REST API
+
+REST API locale functionality relies on URL query parameters.
+
+**`?locale=`**
+
+Specify your desired locale by providing the `locale` query parameter directly in the endpoint URL.
+
+**`?fallback-locale=`**
+
+Specify fallback locale to be used by providing the `fallback-locale` query parameter. This can be provided as either a valid locale as provided to your base Payload config, or `'null'`, `'false'`, or `'none'` to disable falling back.
+
+**Example:**
+
+```
+fetch('https://localhost:3000/api/pages?locale=es&fallback-locale=none');
+```
+
+##### GraphQL API
+
+In the GraphQL API, you can specify `locale` and `fallbackLocale` args to all relevant queries and mutations.
+
+The `locale` arg will only accept valid locales, but locales will be formatted automatically as valid GraphQL enum values (dashes or special characters will be converted to underscores, spaces will be removed, etc.). If you are curious to see how locales are auto-formatted, you can use the [GraphQL playground](/docs/graphql/overview#graphql-playground).
+
+The `fallbackLocale` arg will accept valid locales as well as `none` to disable falling back.
+
+**Example:**
+
+```graphql
+query {
+  Posts(locale: de, fallbackLocale: none) {
+    docs {
+      title
+    }
+  }
+}
+```
+
+<Banner>
+  In GraphQL, specifying the locale at the top level of a query will automatically apply it
+  throughout all nested relationship fields. You can override this behavior by re-specifying locale
+  arguments in nested related document queries.
+</Banner>
+
+##### Local API
+
+You can specify `locale` as well as `fallbackLocale` within the Local API as well as properties on the `options` argument. The `locale` property will accept any valid locale, and the `fallbackLocale` property will accept any valid locale as well as `'null'`, `'false'`, `false`, and `'none'`.
+
+**Example:**
+
+```js
+const posts = await payload.find({
+  collection: 'posts',
+  locale: 'es',
+  fallbackLocale: false,
+})
+```
+
+<Banner type="alert">
+  <strong>Tip:</strong>
+  <br />
+  The REST and Local APIs can return all localization data in one request by passing 'all' or '*' as
+  the <strong>locale</strong> parameter. The response will be structured so that field values come
+  back as the full objects keyed for each locale instead of the single, translated value.
+</Banner>