chore(release): v1.1.25

Saves tabs to user preferences

.eslintrc.js

@@ -21,6 +21,28 @@ module.exports = {
     },
   },
   overrides: [
+    {
+      files: ['test/**/int.spec.ts'],
+      rules: {
+        '@typescript-eslint/no-use-before-define': 'off',
+        '@typescript-eslint/consistent-type-imports': 'warn',
+        'jest/prefer-strict-equal': 'off',
+      }
+    },
+    {
+      files: ['test/**/e2e.spec.ts'],
+      extends: [
+        'plugin:playwright/playwright-test'
+      ],
+      rules: {
+        'jest/consistent-test-it': 'off',
+        'jest/require-top-level-describe': 'off',
+        'jest/no-test-callback': 'off',
+        'jest/prefer-strict-equal': 'off',
+        'jest/expect-expect': 'off',
+        'jest-dom/prefer-to-have-attribute': 'off',
+      }
+    },
     {
       files: ['*.ts', '*.tsx'],
       parser: '@typescript-eslint/parser',
@@ -28,8 +50,8 @@ module.exports = {
         'plugin:@typescript-eslint/recommended',
       ],
       rules: {
-        "no-shadow": "off",
-        "@typescript-eslint/no-shadow": ["error"],
+        'no-shadow': 'off',
+        '@typescript-eslint/no-shadow': ['error'],
         'import/no-unresolved': [
           2,
           {
@@ -38,18 +60,35 @@ module.exports = {
             ],
           },
         ],
-      }
+      },
+    },
+    {
+      files: ['*.spec.ts'],
+      rules: {
+        '@typescript-eslint/no-use-before-define': 'off',
+      },
+    },
+    {
+      files: ['*.e2e.ts'],
+      rules: {
+        '@typescript-eslint/no-use-before-define': 'off',
+        'jest/expect-expect': 'off',
+      },
     },
   ],
   rules: {
-    'no-sparse-arrays': 'off',
-    'import/no-extraneous-dependencies': ["error", { "packageDir": "./" }],
+    'import/no-extraneous-dependencies': ['error', { packageDir: './' }],
     'react/jsx-filename-extension': [2, { extensions: ['.js', '.jsx', '.ts', '.tsx'] }],
     'import/prefer-default-export': 'off',
     'react/prop-types': 'off',
     'react/require-default-props': 'off',
     'react/no-unused-prop-types': 'off',
+    'no-console': 'warn',
+    'no-sparse-arrays': 'off',
     'no-underscore-dangle': 'off',
+    'no-use-before-define': 'off',
+    'arrow-body-style': 0,
+    '@typescript-eslint/no-use-before-define': 'off',
     'import/extensions': [
       'error',
       'ignorePackages',

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -1,27 +1,28 @@
 ---
 name: Bug Report
 about: Create a bug report for Payload
-labels: 'bug'
+labels: 'possible-bug'
 ---
 
 # Bug Report
 
 <!--- Provide a general summary of the issue in the Title above -->
 
-## Expected Behavior
-
-<!--- Tell us what should happen -->
-
 ## Current Behavior
 
 <!--- Tell us what happens instead of the expected behavior -->
 
+## Expected Behavior
+
+<!--- Tell us what you expected happen -->
+
 ## Possible Solution
 
-<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- Optional. If familiar with the codebase, suggest a fix/reason for the bug. -->
 
 ## Steps to Reproduce
 <!--- Steps to reproduce this bug. Include any code, if relevant -->
+
 1.
 2.
 3.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,8 @@
 blank_issues_enabled: false
 contact_links:
+  - name: Security Vulnerability
+    url: https://github.com/payloadcms/payload/blob/master/SECURITY.md
+    about: See instructions to privately disclose any security concerns
   - name: Feature Request
     url: https://github.com/payloadcms/payload/discussions
     about: Suggest an idea to improve Payload in our GitHub Discussions

.github/workflows/tests.yml

@@ -1,13 +1,17 @@
 name: build
 
-on: [push]
+on:
+  pull_request:
+    types: [opened, reopened, edited, synchronize]
+  push:
+    branches: ['master']
 
 jobs:
   build_yarn:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [12.x, 14.x, 15.x, 16.x]
+        node-version: [14.x, 16.x, 18.x]
 
     steps:
     - uses: actions/checkout@v2
@@ -31,10 +35,26 @@ jobs:
       env:
         NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
     - run: yarn build
-    - run: yarn test:client
-    - run: yarn test:int # In-memory db + api tests
-      env:
-        CI: true
+
+    - name: Component Tests
+      run: yarn test:components
+    - name: Integration Tests
+      run: yarn test:int
+
+    - name: Generate Payload Types
+      run: yarn dev:generate-types fields
+
+    - name: Install Playwright Browsers
+      run: npx playwright install --with-deps
+    - name: E2E Tests
+      run: yarn test:e2e --bail
+
+    # - uses: actions/upload-artifact@v2
+    #   if: always()
+    #   with:
+    #     name: playwright-report
+    #     path: playwright-report/
+    #     retention-days: 30
   install_npm:
     runs-on: ubuntu-latest
     strategy:

.gitignore

@@ -86,6 +86,15 @@ typings/
 # Yarn Integrity file
 .yarn-integrity
 
+# Yarn Berry
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/sdks
+!.yarn/versions
+.pnp.*
+
 # dotenv environment variables file
 .env
 
@@ -228,3 +237,7 @@ build
 # Ignore built components
 components/index.js
 components/styles.css
+
+# Ignore generated
+demo/generated-types.ts
+demo/generated-schema.graphql

.node-version

@@ -0,0 +1 @@
+v16.14.2

.vscode/launch.json

@@ -29,42 +29,18 @@
       "request": "launch",
       "name": "Launch Program",
       "env": {
-        "PAYLOAD_CONFIG_PATH": "demo/payload.config.ts",
         "BABEL_ENV": "development"
       },
-      "program": "${workspaceFolder}/demo/index.js",
+      "program": "${workspaceFolder}/test/dev.js",
       "skipFiles": [
         "<node_internals>/**"
       ],
-      "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/babel-node",
       "runtimeArgs": [
         "--nolazy"
       ],
+      "args": [
+        "fields"
+      ]
     },
-    {
-      "type": "node",
-      "request": "launch",
-      "name": "Launch Program - Production",
-      "env": {
-        "PAYLOAD_CONFIG_PATH": "demo/payload.config.ts",
-        "NODE_ENV": "production",
-        "BABEL_ENV": "development"
-      },
-      "program": "${workspaceFolder}/demo/index.js",
-      "skipFiles": [
-        "<node_internals>/**"
-      ],
-      "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/babel-node",
-      "runtimeArgs": [
-        "--nolazy"
-      ],
-    },
-    {
-      "type": "chrome",
-      "request": "launch",
-      "name": "Launch Chrome against Localhost",
-      "url": "http://localhost:3000/admin",
-      "webRoot": "${workspaceFolder}"
-    }
   ]
 }

README.md

@@ -1,15 +1,22 @@
 <h1 align="center">Payload</h1>
-<p align="center">A self-hosted, JavaScript headless CMS & application framework built with Express, MongoDB and React.</p>
+<p align="center">A free and open-source TypeScript headless CMS & application framework built with Express, MongoDB and React.</p>
 <p align="center">
+  <a href="https://opensource.org/licenses/MIT">
+    <img src="https://img.shields.io/badge/License-MIT-blue.svg" />
+  </a>
   <a href="https://github.com/payloadcms/payload/actions">
-    <img src="https://github.com/payloadcms/payload/workflows/build/badge.svg">
+    <img src="https://github.com/payloadcms/payload/workflows/build/badge.svg" />
   </a>
   <a href="https://www.npmjs.com/package/payload">
-    <img alt="npm" src="https://img.shields.io/npm/v/payload">
+    <img alt="npm" src="https://img.shields.io/npm/v/payload" />
   </a>
 
   <a href="https://twitter.com/intent/tweet?text=Payload%20-%20A%20self-hosted%2C%20headless%20JavaScript%20CMS%20%26%20application%20framework&url=https%3A%2F%2Fgithub.com%2Fpayloadcms%2Fpayload">
-  <img alt="Tweet Payload" src="https://img.shields.io/twitter/url/http/shields.io.svg?style=social">
+  <img alt="Tweet Payload" src="https://img.shields.io/twitter/url/http/shields.io.svg?style=social" />
+  </a>
+
+  <a href="https://discord.com/invite/r6sCXqVk3v">
+    <img alt="Discord" src="https://img.shields.io/discord/967097582721572934?label=Discord&color=7289da" />
   </a>
 </p>
 
@@ -17,25 +24,15 @@
   <img src="https://payloadcms.com/images/og-image.jpg" alt="Payload headless CMS Admin panel built with React" />
 </a>
 
-### Quick Start
-
-```
-npx create-payload-app
-```
-
-Alternatively, it only takes about five minutes to [create an app from scratch](https://payloadcms.com/docs/getting-started/installation#from-scratch).
-
-### 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.
-
 ### 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)
@@ -49,18 +46,14 @@ Check out the [Payload website](https://payloadcms.com/docs/getting-started/what
 
 ### Code-first
 
-If you know JavaScript, you know Payload. Payload is a _code-first_ CMS, which allows us to do a lot of things right:
+Payload is a CMS that has been designed for developers from the ground up to deliver them what they need to build great digital products. If you know JavaScript, you know Payload. It's a _code-first_ CMS, which allows us to do a lot of things right:
 
-- Payload gives you everything you need, but then steps back and lets you build what you want in JavaScript or TypeScript - with no unnecessary complexity brought by GUIs. You'll understand how your CMS works, because you will have written it exactly how you want it.
+- Payload gives you everything you need, but then steps back and lets you build what you want in JavaScript or TypeScript - with no unnecessary complexity brought by GUIs. You'll understand how your CMS works because you will have written it exactly how you want it.
 - Bring your own Express server and do whatever you need on top of Payload. Payload doesn't impose anything on you or your app.
 - Completely control the Admin panel by using your own React components. Swap out fields or even entire views with ease.
-- Use your data however and wherever you need thanks to auto-generated, yet fully extensible REST, GraphQL and Local Node APIs.
+- Use your data however and wherever you need thanks to auto-generated, yet fully extensible REST, GraphQL, and Local Node APIs.
 
-### Free forever for personal use and small projects
-
-Payload is 100% free for personal projects or small use cases where only one admin user is required. You can also get started without an account whatsoever while running on `localhost`.
-
-## Installation
+### Quick Start
 
 Before beginning to work with Payload, make sure you have all of the [required software](https://payloadcms.com/docs/getting-started/installation).
 
@@ -70,8 +63,22 @@ From there, the easiest way to get started with Payload is to use the `create-pa
 npx create-payload-app
 ```
 
-Alternatively, it only takes about five minutes to [write out your own app from scratch](https://payloadcms.com/docs/getting-started/installation#from-scratch).
+Alternatively, it only takes about five minutes to [create an app from scratch](https://payloadcms.com/docs/getting-started/installation#from-scratch).
 
-## License
+### Documentation
 
-Find the Payload license [here](https://github.com/payloadcms/payload/blob/master/license.md).
+Check out the [Payload website](https://payloadcms.com/docs/getting-started/what-is-payload) to find in-depth documentation for everything that Payload offers.
+
+### Contributing
+
+If you want to add contributions to this repository, please follow the instructions in [contributing.md](./contributing.md).
+
+### Other Resources
+
+##### Discussions
+
+There are lots of good conversations and resources in our [GitHub Discussions board](https://github.com/payloadcms/payload/discussions). If you're struggling with something, chances are, someone's already solved what you're up against. Searching Discussions will often provide very helpful tips and tricks.
+
+##### Discord
+
+Join [Payload's Discord channel](https://discord.com/invite/r6sCXqVk3v) to interact with Payload developers in realtime.

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).

components/elements.ts

@@ -0,0 +1,5 @@
+export { default as Button } from '../dist/admin/components/elements/Button';
+export { default as Card } from '../dist/admin/components/elements/Card';
+export { default as Eyebrow } from '../dist/admin/components/elements/Eyebrow';
+export { default as Nav } from '../dist/admin/components/elements/Nav';
+export { Gutter } from '../dist/admin/components/elements/Gutter';

components/forms.ts

@@ -1,20 +1,38 @@
 export {
   useForm,
+  /**
+   * @deprecated useWatchForm is no longer preferred. If you need all form fields, prefer `useAllFormFields`.
+   */
   useWatchForm,
+  useFormFields,
+  useAllFormFields,
   useFormSubmitted,
   useFormProcessing,
   useFormModified,
 } from '../dist/admin/components/forms/Form/context';
 
-export { default as useFieldType } from '../dist/admin/components/forms/useFieldType';
+export { default as useField } from '../dist/admin/components/forms/useField';
+
+/**
+ * @deprecated This method is now called useField. The useFieldType alias will be removed in an upcoming version.
+ */
+export { default as useFieldType } from '../dist/admin/components/forms/useField';
 
 export { default as Form } from '../dist/admin/components/forms/Form';
 
 export { default as Text } from '../dist/admin/components/forms/field-types/Text';
+export { default as TextInput } from '../dist/admin/components/forms/field-types/Text/Input';
+
 export { default as Group } from '../dist/admin/components/forms/field-types/Group';
+
 export { default as Select } from '../dist/admin/components/forms/field-types/Select';
+export { default as SelectInput } from '../dist/admin/components/forms/field-types/Select/Input';
+
 export { default as Checkbox } from '../dist/admin/components/forms/field-types/Checkbox';
 export { default as Submit } from '../dist/admin/components/forms/Submit';
 export { default as Label } from '../dist/admin/components/forms/Label';
 
 export { default as reduceFieldsToValues } from '../dist/admin/components/forms/Form/reduceFieldsToValues';
+export { default as getSiblingData } from '../dist/admin/components/forms/Form/getSiblingData';
+
+export { default as withCondition } from '../dist/admin/components/forms/withCondition';

components/hooks.ts

@@ -0,0 +1 @@
+export { useStepNav } from '../dist/admin/components/elements/StepNav';

components/icons.ts

@@ -0,0 +1,2 @@
+export { default as Chevron } from '../src/admin/components/icons/Chevron';
+export { default as X } from '../src/admin/components/icons/X';

components/templates.ts

@@ -0,0 +1,2 @@
+export { default as DefaultTemplate } from '../dist/admin/components/templates/Default';
+export { default as MinimalTemplate } from '../dist/admin/components/templates/Minimal';

components/utilities.ts

@@ -0,0 +1,6 @@
+export { default as Meta } from '../dist/admin/components/utilities/Meta';
+export { useLocale } from '../dist/admin/components/utilities/Locale';
+export { useDocumentInfo } from '../dist/admin/components/utilities/DocumentInfo';
+export { useConfig } from '../dist/admin/components/utilities/Config';
+export { useAuth } from '../dist/admin/components/utilities/Auth';
+export { useEditDepth } from '../dist/admin/components/utilities/EditDepth';

components/views/Dashboard.ts

@@ -0,0 +1,3 @@
+export { default as Dashboard } from '../../dist/admin/components/views/Dashboard/Default';
+
+export type { Props } from '../../dist/admin/components/views/Dashboard/types';

contributing.md

@@ -2,10 +2,6 @@
 
 Below you'll find a set of guidelines for how to contribute to Payload CMS.
 
-## Payload is proprietary software
-
-Even though you can read Payload's source code, it's technically not "open source". Payload requires an active license to be used in all production purposes. That said, we do not expect PRs from the public, but we still welcome pull requests of any kind.
-
 ## 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.
@@ -22,12 +18,41 @@ Payload documentation can be found directly within its codebase and you can feel
 
 ## 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. If your proposed feature is accepted by our team and is significant enough, pending our discretion, we'd be happy to hook you up with a pro-bono license.
+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.
 
-To help us work on new features, you can reach out to our Development team at [`dev@payloadcms.com`](mailto:dev@payloadcms.com). Be as complete and descriptive as possible regarding your vision and we'll go from there!
+### 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/r6sCXqVk3v). 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 `yarn 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: `yarn dev my-test-dir`. This command will start up Payload using your config and refresh a test database on every restart.
+
+When switching between test directories, you will want to remove your `node_modules/.cache ` manually or by running `yarn clean:cache`.
+
+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.
 
 ## 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.
-
-By opening a Pull Request against Payload's codebase, you automatically give the entirety of the contribution within your PR to Payload CMS, LLC and retain no personal ownership whatsoever afterward. For more information, please read the full [Payload license](https://github.com/payloadcms/payload/blob/master/license.md).

demo/access/checkRole.ts

@@ -1,17 +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) => user.roles && user.roles.some((individualRole) => individualRole === role))) {
-      return true;
-    }
-  }
-
-  return false;
-};
-
-export default checkRole;

demo/access/roles.ts

@@ -1,7 +0,0 @@
-export default [
-  'admin',
-  'editor',
-  'moderator',
-  'user',
-  'viewer',
-];

demo/blocks/CallToAction.ts

@@ -1,26 +0,0 @@
-import { Block } from '../../src/fields/config/types';
-
-const CTA: Block = {
-  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',
-      required: true,
-    },
-  ],
-};
-
-export default CTA;

demo/blocks/Email.ts

@@ -1,19 +0,0 @@
-import { Block } from '../../src/fields/config/types';
-
-const Email: Block = {
-  slug: 'email',
-  labels: {
-    singular: 'Email',
-    plural: 'Emails',
-  },
-  fields: [
-    {
-      name: 'testEmail',
-      label: 'Test Email Field',
-      type: 'email',
-      required: true,
-    },
-  ],
-};
-
-export default Email;

demo/blocks/Number.ts

@@ -1,20 +0,0 @@
-import { Block } from '../../src/fields/config/types';
-
-const NumberBlock: Block = {
-  slug: 'number',
-  labels: {
-    singular: 'Number',
-    plural: 'Numbers',
-  },
-  fields: [
-    {
-      name: 'testNumber',
-      label: 'Test Number Field',
-      type: 'number',
-      max: 100,
-      required: true,
-    },
-  ],
-};
-
-export default NumberBlock;

demo/blocks/Quote.ts

@@ -1,34 +0,0 @@
-import { Block } from '../../src/fields/config/types';
-
-const Quote: Block = {
-  imageURL: '/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',
-      required: true,
-    },
-    {
-      name: 'color',
-      label: 'Color',
-      type: 'text',
-      maxLength: 7,
-      required: true,
-    },
-  ],
-};
-
-export default Quote;

demo/client/index.html

@@ -1,14 +0,0 @@
-<!DOCTYPE HTML>
-<html>
-
-<head>
-  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-  <meta name="viewport" content="width=device-width, initial-scale=1" />
-</head>
-
-<body>
-  <div id="app"></div>
-  <div id="portal"></div>
-</body>
-
-</html>

demo/client/static/assets/images/generic-block-image.svg

@@ -1,9 +0,0 @@
-<svg width="82" height="53" viewBox="0 0 82 53" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-<rect x="0.713013" width="80.574" height="52.7791" fill="url(#pattern0)"/>
-<defs>
-<pattern id="pattern0" patternContentUnits="objectBoundingBox" width="1" height="1">
-<use xlink:href="#image0" transform="scale(0.00387597 0.00591716)"/>
-</pattern>
-<image id="image0" width="258" height="169" xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQIAAACpCAYAAADA4zPJAAALpklEQVR4Ae2dSY/UOhSF+///DCSGHQuEgAVI7BBITAI2zCCGZuhmpqEBP53W8yOvK1UdO3Zyr/NFilJdXalyTo4/X984zlZgQQEUWLwCW4tXAAFQAAUCIMAEKIACgAAPoAAKBECACVAABQABHkABFAiAABOgAAoAAjyAAiggBbhqgA9QAAUAAR5AARQgIsADKIACdA3wAAqggBQgR4APUAAFAAEeQAEUICLAAyiAAnQN8AAKoIAUIEeAD1AABQABHkABFCAiwAMogAJ0DfAACqCAFCBHgA9QAAUAAR5AARQgIsADKIACdA3wAAqggBQgR4APUAAFAAEeQAEUICLAAyiAAnQN8AAKoIAUIEeAD1AABQABHkABFCAiwAMogAJ0DfAACqCAFCBHgA9QAAUAAR5AARQgIsADKIACdA3wAAqggBQgR4APUAAFAAEeQAEUICLAAyiAAnQN8AAKoIAUIEeAD1AABQABHkABFCAiwAMLVmB/fz98+/YtfPr0KXz48CHs7u6GnZ2dg+3Hjx/D169fw48fP8KfP3+aV4muQfOnmAPsKqDKr4r/9u3bsL29PXgVKPb29pqFAiDouoTXzSrw8+fPg5Y+pfL3ffbdu3fh+/fvzekECJo7pRxQVwGF9YoA+ir1mPfUhVB00coCCFo5kxzHigKqqGrBx1T4Tfu+efOmmegAEKzYhzdaUEBdAVXUTRW51P+UVPS+AALvZ5DyryigSGAqCESYeIcBIFixEW94VuDXr1/JVwRiZR671VUFrwsg8HrmKPeKAkoMKok3tkLn7q8oRCDyuAACj2eNMvcqoMFBuZW41H4alORxAQQezxplXlHg9+/fk+cF1sHDYxcBEKxYijc8KvDly5fZo4EIhvfv37uTEBC4O2UU+LACyg2kDhmOlbbWVpcvPS2AwNPZoqy9CigUr1Whc79Xoxk9LYDA09mirL0K1BhCnAuAuJ8iFE8LIPB0tihrrwI1hxHHip2z9XQpERD0Wos3vSig/EBOJZ1iH09XDwCBF8dTzl4FNJx4ikqd8xu6kuFlAQRezhTl7FVAMwjlVNIp9vn8+XNvmS2+aR4E6md56mtZPMktl8niFYMIGU9XDkyDQCdZ47e1eupvtVzxrB0bEUGZM2ISBEoAafLISNa4FWH1PxYUiApo4E70h7UtOYJ4ljK2OrGbLgfpfy1NEZUhEbt0FNA9BtYAEMvjaW5DMxGBWnpN7hBFPGrrfSKIjpd5OVIBa8OLo3c9DTM2AQJRXbdvRgGHbrWP9mVZtgKaanyoZ6b6nPJanrqxs4MgJgRzTxCJxGVDQEevEDzXP7X2E5w8LbOBQLQsOUZ8TCLx9evX4fHjx+HRo0esTjW4efNmKL3eu3cvyBs5sPB2lWsWENSaZlr3gacmEi9fvhyOHTvGiga9Hjh79mwyDJSz8NQtUOQyOQhSEoI5JNY+mrJqyPLy5cvekw8YAGPXA7du3UqKCob6b4hHp/rMZCDITQjmwmBIIvH+/fuAgEjgSA9cuXJlMAh0edtbNCDYTAICjf6a4xKPflO/vW4BBLT83ZZ/3esUEHi6ZNitF1VBIDLqxovcVr3UfipDH6UBASBYV/m77w8FgaeRhF0I6HU1EChpp+Rdqco89nv6EomAABB0K/y610NAoCHxfY3N4Qpn9e8qILAwv3wfODTmoJvIef78+ZH9w3Xm4P3lQOTGjRsbGzSNGfAMgeIRgRKCFkd5HYaCyqiyaj1//jwwIGG41gOnT58Ourp02EPx7zHjVyxFB8UigrkSgvGEpG5jIlEw0ECiO3fusDaowe3bt8PVq1eDwvvU9fr162sh0NqI1tEgsJIQTAVB/Py6RKIlWlOWcQrIo+oSlrpypShADUhLyygQaOYgSwnBWLlTtzoGZkFqydb9xxKBkONZQUSNRqs+yQaBbvRQeJRa6ax+Xsfi6f7xfqvz7lAFVKEVJSjbLzCookc/a6uBQcol6ZKgxgZ4TwYepUsyCBQSeUgI5gJHxmgt7DvKBPwfBZJAIDKW6mflVtQp9tMxeh0hhqVRIEeBQSBQWKQQaYpKaOk3dMyth4Q5pmGf9hQ4EgTqS+3s7CwOAhFIOvZWE0Tt2ZkjylVgIwhaSwjGyp26JZGYay/286JALwiULOubTjy1ArX2ee/jyb2YknJOr8AKCJQk06WT1ipxqeORNiQSpzcqv1hXgf9AsNSEYC4gSCTWNSbfPq0CByBYekIwFwYkEqc1K79WT4GtsdOJ51aiVvZTItHbjLX17MQ3e1Vgq5UKOfdxtHI7ajSy7iYlFxLVaH8LCLa3iyVGlUhMnU7dmsWUK+pOL6dZpxlUZe0slS8PICgIghiV6F4M3ct+6dIlV+vFixcPJmo5d+5c6K4XLlwI+p/l47l27RpdtBF8AAQVQHDmzJm1M94wxVm9Kc6kOzeM5dEAEBQGgR6dRmWvV9mP0lbdM5Z0BQBBYRA8ePAAEMw4B6KeVciSrgAgAARNgQsQpENAewACQAAI8upOU3sBgsIgePjwYVMV66g+ubX/ExHk8QkQFAaB5sA/ceIEMJghT3D8+HHmnczjAF2DeO2/5Pbu3bvh1KlTwGBCGJw8eTI8efIksxqwGxFB4YggAuXVq1fh2bNn4enTp0euL168OJj/QaP4Sq26O1JzLw75/Rqf0czApY5lyPcwfmAczABBJRBEIAzd6ual7nMZx5xWK3eTxkfLjTkW9p1GAUBgBAQRGGMrj7W7SRWV6AYmFtsKAAJjIBAQciqPbgyyPL0cj5YDBMXu7out5lK2QyuPl+nleLScXRgQERiMCLqg2zQLkqIAJdK6n7f+mhmhbcIAEBgHgSp2X+VRlnx3d9cVBLqQGpsLsVmd/JYKEDgAQaxA8bmM1hKCsXypWx4tZwccgMARCFTRFB2kVjjrn2dG6PmBAAicgcB6pc4t36ZcyPzVpP0SAAJAYCbC6MuFtF8FbRwhIAAEZkAQowkeLTc9HAABIDAHAgGBR8tNCwNAAAhMgiBGByQSpwECIAAEpkEgIJBIrA8DQAAIzINAMFAikUfL1QMCIAAELkAQuwqtPVquXtVO+2ZAAAhcgUBAaOHRcmnVtP6nAQEgcAeCGB3ohiuWMgoAAkDgFgQCgm68Ypqy8TAABIDANQgEAxKJgMC9iWOYy3b84+lJJOYDgYiAiKApmGoWpP39/fwasdA9AQEgaAoEMbIqNSP0UrgACABBkyAQEEgkDscYIAAEzYJAMMiZEXp49Wnnk4AAEDQNgthVGDojdDtVO+1IAAEgWAQIBAQSievhAAgAwWJAIBhozAGJxFUgAAJAsCgQxK4C06n/HwaAABAsEgQCAonEvzAABIBgsSCI0QGJxBAAASBYPAgEhKU/lxEQAAJA8K8HljydOiAABIDgkAfio+X+9qDbfwUIDpkg9hvZjr8b0LOGS3suIyAABEQEGzywlOnUAcEGE3hu0Sh7uYhmCdOpAwJAQEQwwAOtJxIBwQAT0LqWa129a9nqcxkBASAgIkj0QIvPZQQEiSbw3qJR/nLRTUuJREAACIgIRniglUQiIBhhAlrXcq2rZy1bmE4dEAACIoJCHvA8nTogKGQCzy0aZS8X2Xh9LiMgAAREBBU84O25jICgggloYcu1sJ619DSdOiAABEQEFT3gJZEICCqawHNrRtnLRjXWE4mAABAQEUzkAcvTqQOCiUxAC1u2hfWsp8Xp1AEBICAimMED1hKJgGAGE3huzSh7ucjG0nTqgAAQEBHM7AEL06kDgplNQAtbroX1rOXciURAAAiICIx4QGMO5kokAgIjJvDcmlH2slHNHM9lBASAgIjAoAemTiQCAoMmoIUt28J61nOqRCIgAAREBMY9MMUsSIDAuAk8t2aUvVxkU3s6dUAACIgIHHmg1nMZAYEjE9DClmthPWtZYzp1QAAIiAiceqDkdOqAwKkJPLdolL1cZFMqkbilkUysaIAH/Hpgb28vjF3+AbSb48mcXO9tAAAAAElFTkSuQmCC"/>
-</defs>
-</svg>

demo/collections/Admin.ts

@@ -1,67 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import roles from '../access/roles';
-import checkRole from '../access/checkRole';
-
-const access = ({ req: { user } }) => {
-  const result = checkRole(['admin'], user);
-  return result;
-};
-
-const Admin: CollectionConfig = {
-  slug: 'admins',
-  labels: {
-    singular: 'Admin',
-    plural: 'Admins',
-  },
-  access: {
-    create: access,
-    read: access,
-    update: access,
-    delete: access,
-    admin: () => true,
-  },
-  auth: {
-    tokenExpiration: 7200, // 2 hours
-    verify: false,
-    maxLoginAttempts: 5,
-    lockTime: 600 * 1000, // lock time in ms
-    useAPIKey: true,
-    depth: 0,
-    cookies: {
-      secure: false,
-      sameSite: 'lax',
-      domain: undefined,
-    },
-  },
-  fields: [
-    {
-      name: 'roles',
-      label: 'Role',
-      type: 'select',
-      options: roles,
-      defaultValue: 'user',
-      required: true,
-      saveToJWT: true,
-      hasMany: true,
-    },
-    {
-      name: 'publicUser',
-      type: 'relationship',
-      hasMany: true,
-      relationTo: 'public-users',
-    },
-    {
-      name: 'apiKey',
-      type: 'text',
-      access: {
-        read: ({ req: { user } }) => checkRole(['admin'], user),
-      },
-    },
-  ],
-  timestamps: true,
-  admin: {
-    useAsTitle: 'email',
-  },
-};
-
-export default Admin;

demo/collections/AllFields.ts

@@ -1,339 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import checkRole from '../access/checkRole';
-import Email from '../blocks/Email';
-import Quote from '../blocks/Quote';
-import NumberBlock from '../blocks/Number';
-import CallToAction from '../blocks/CallToAction';
-import CollectionDescription from '../customComponents/CollectionDescription';
-
-const AllFields: CollectionConfig = {
-  slug: 'all-fields',
-  labels: {
-    singular: 'All Fields',
-    plural: 'All Fields',
-  },
-  admin: {
-    useAsTitle: 'text',
-    preview: (doc, { token }) => {
-      const { text } = doc;
-
-      if (doc && text) {
-        return `http://localhost:3000/previewable-posts/${text}?preview=true&token=${token}`;
-      }
-
-      return null;
-    },
-    description: CollectionDescription,
-  },
-  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: 'descriptionText',
-      type: 'text',
-      label: 'Text with text description',
-      defaultValue: 'Default Value',
-      admin: {
-        description: 'This text describes the field',
-      },
-    },
-    {
-      name: 'descriptionFunction',
-      type: 'text',
-      label: 'Text with function description',
-      defaultValue: 'Default Value',
-      maxLength: 20,
-      admin: {
-        description: ({ value }) => (typeof value === 'string' ? `${20 - value.length} characters left` : ''),
-      },
-    },
-    {
-      name: 'image',
-      type: 'upload',
-      label: 'Image',
-      relationTo: 'media',
-      admin: {
-        description: 'No selfies',
-      },
-    },
-    {
-      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: 'dayOnlyDateFieldExample',
-      label: 'Day Only',
-      type: 'date',
-      required: true,
-      admin: {
-        date: {
-          pickerAppearance: 'dayOnly',
-          monthsToShow: 2,
-        },
-      },
-    },
-    {
-      name: 'timeOnlyDateFieldExample',
-      label: 'Time Only',
-      type: 'date',
-      admin: {
-        date: {
-          pickerAppearance: 'timeOnly',
-        },
-      },
-    },
-    {
-      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,
-      admin: {
-        readOnly: 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,
-              admin: {
-                width: '50%',
-              },
-            },
-            {
-              name: 'arrayText2',
-              label: 'Array Text 2',
-              type: 'text',
-              required: true,
-              admin: {
-                width: '50%',
-              },
-              access: {
-                read: ({ req: { user } }) => Boolean(user),
-                update: ({ req: { user } }) => checkRole(['admin'], user),
-              },
-            },
-          ],
-        },
-        {
-          type: 'text',
-          name: 'arrayText3',
-          label: 'Array Text 3',
-          admin: {
-            readOnly: true,
-          },
-        },
-        {
-          name: 'checkbox',
-          label: 'Checkbox',
-          type: 'checkbox',
-        },
-      ],
-    },
-    {
-      type: 'blocks',
-      label: 'Blocks Content',
-      name: 'blocks',
-      minRows: 2,
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      localized: true,
-      required: true,
-    },
-    {
-      type: 'relationship',
-      label: 'Relationship to One Collection',
-      name: 'relationship',
-      relationTo: 'conditions',
-      admin: {
-        description: 'Relates to description',
-      },
-    },
-    {
-      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',
-      admin: {
-        description: 'Hello textarea description',
-      },
-    },
-    {
-      name: 'richText',
-      type: 'richText',
-      label: 'Rich Text',
-      required: true,
-      admin: {
-        elements: [
-          'h1',
-          'h2',
-          'h3',
-          'h4',
-          'h5',
-          'h6',
-          'blockquote',
-          'ul',
-          'ol',
-          'link',
-        ],
-        leaves: [
-          'bold',
-          'italic',
-          'underline',
-          'strikethrough',
-        ],
-      },
-    },
-    {
-      name: 'slug',
-      type: 'text',
-      label: 'Slug',
-      admin: {
-        position: 'sidebar',
-      },
-      localized: true,
-      unique: true,
-      required: true,
-    },
-    {
-      name: 'checkbox',
-      type: 'checkbox',
-      label: 'Checkbox',
-      admin: {
-        position: 'sidebar',
-      },
-    },
-    {
-      name: 'dateFieldExample',
-      label: 'Day and Time',
-      type: 'date',
-      admin: {
-        position: 'sidebar',
-        date: {
-          timeIntervals: 30,
-        },
-      },
-    },
-  ],
-  timestamps: true,
-};
-
-export default AllFields;

demo/collections/AutoLabel.ts

@@ -1,102 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const AutoLabel: CollectionConfig = {
-  slug: 'auto-label',
-  admin: {
-    useAsTitle: 'autoLabelField',
-    enableRichTextRelationship: true,
-  },
-  fields: [
-    {
-      name: 'autoLabelField',
-      type: 'text',
-    },
-    {
-      name: 'noLabel',
-      type: 'text',
-      label: false,
-    },
-    {
-      name: 'labelOverride',
-      type: 'text',
-      label: 'Custom Label',
-    },
-    {
-      name: 'testRelationship',
-      type: 'relationship',
-      relationTo: 'all-fields',
-    },
-    {
-      name: 'specialBlock',
-      type: 'blocks',
-      minRows: 1,
-      maxRows: 20,
-      // Will auto-label
-      // labels: {
-      //   singular: 'Special Block',
-      //   plural: 'Special Blocks',
-      // },
-      blocks: [
-        {
-          slug: 'number',
-          // Will auto-label
-          // labels: {
-          //   singular: 'Number',
-          //   plural: 'Numbers',
-          // },
-          fields: [
-            {
-              name: 'testNumber',
-              type: 'number',
-            },
-          ],
-        },
-      ],
-    },
-    {
-      name: 'noLabelBlock',
-      type: 'blocks',
-      label: false,
-      minRows: 1,
-      maxRows: 20,
-      blocks: [
-        {
-          slug: 'number',
-          // labels: {
-          //   singular: 'Number',
-          //   plural: 'Numbers',
-          // },
-          fields: [
-            {
-              name: 'testNumber',
-              type: 'number',
-            },
-          ],
-        },
-      ],
-    },
-    {
-      name: 'items',
-      type: 'array',
-      fields: [
-        {
-          name: 'itemName',
-          type: 'text',
-        },
-      ],
-    },
-    {
-      name: 'noLabelArray',
-      type: 'array',
-      label: false,
-      fields: [
-        {
-          type: 'text',
-          name: 'textField',
-        },
-      ],
-    },
-  ],
-};
-
-export default AutoLabel;

demo/collections/Blocks.ts

@@ -1,43 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import Email from '../blocks/Email';
-import Quote from '../blocks/Quote';
-import NumberBlock from '../blocks/Number';
-import CallToAction from '../blocks/CallToAction';
-
-const Blocks: CollectionConfig = {
-  slug: 'blocks',
-  labels: {
-    singular: 'Blocks',
-    plural: 'Blocks',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'layout',
-      label: 'Layout Blocks',
-      labels: {
-        singular: 'Block',
-        plural: 'Blocks',
-      },
-      type: 'blocks',
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      localized: true,
-      required: true,
-    },
-    {
-      name: 'nonLocalizedLayout',
-      label: 'Non Localized Layout',
-      labels: {
-        singular: 'Layout',
-        plural: 'Layouts',
-      },
-      type: 'blocks',
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      required: true,
-    },
-  ],
-};
-
-export default Blocks;

demo/collections/Code.ts

@@ -1,23 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const Code: CollectionConfig = {
-  slug: 'code',
-  labels: {
-    singular: 'Code',
-    plural: 'Codes',
-  },
-  fields: [
-    {
-      name: 'code',
-      type: 'code',
-      label: 'Code',
-      required: true,
-      admin: {
-        language: 'js',
-        description: 'javascript example',
-      },
-    },
-  ],
-};
-
-export default Code;

demo/collections/Conditions.ts

@@ -1,73 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import Email from '../blocks/Email';
-import Quote from '../blocks/Quote';
-import NumberBlock from '../blocks/Number';
-import CallToAction from '../blocks/CallToAction';
-
-const Conditions: CollectionConfig = {
-  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),
-      },
-    },
-    {
-      name: 'blocks',
-      label: 'Blocks',
-      labels: {
-        singular: 'Block',
-        plural: 'Blocks',
-      },
-      type: 'blocks',
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      required: true,
-      admin: {
-        condition: (_, siblings) => siblings?.enableTest === true,
-      },
-    },
-  ],
-};
-
-export default Conditions;

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

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

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

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

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

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

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

@@ -1,15 +0,0 @@
-import React from 'react';
-import { Props } from './types';
-
-import './index.scss';
-
-const Filter: React.FC<Props> = ({ onChange, value }) => (
-  <input
-    className="custom-description-filter"
-    type="text"
-    onChange={(e) => onChange(e.target.value)}
-    value={value}
-  />
-);
-
-export default Filter;

demo/collections/CustomComponents/components/fields/Description/Filter/types.ts

@@ -1,4 +0,0 @@
-export type Props = {
-  value?: string
-  onChange?: (value: string) => void
-}

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

@@ -1,19 +0,0 @@
-import React from 'react';
-import PropTypes from 'prop-types';
-import { Group } from '../../../../../../../components/forms';
-
-const CustomGroup: React.FC = (props) => (
-  <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.tsx

@@ -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.tsx

@@ -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.tsx

@@ -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.scss

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

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

@@ -1,14 +0,0 @@
-import React from 'react';
-import DefaultList from '../../../../../../src/admin/components/views/collections/List/Default';
-
-import './index.scss';
-
-const CustomListView: React.FC = (props) => (
-  <div className="custom-list">
-    <p>This is a custom Pages list view</p>
-    <p>Sup</p>
-    <DefaultList {...props} />
-  </div>
-);
-
-export default CustomListView;

demo/collections/CustomComponents/index.ts

@@ -1,120 +0,0 @@
-import { CollectionConfig } from '../../../src/collections/config/types';
-import DescriptionField from './components/fields/Description/Field';
-import DescriptionCell from './components/fields/Description/Cell';
-import DescriptionFilter from './components/fields/Description/Filter';
-import NestedArrayField from './components/fields/NestedArrayCustomField/Field';
-import GroupField from './components/fields/Group/Field';
-import NestedGroupField from './components/fields/NestedGroupCustomField/Field';
-import NestedText1Field from './components/fields/NestedText1/Field';
-import ListView from './components/views/List';
-import CustomDescriptionComponent from '../../customComponents/Description';
-
-const CustomComponents: CollectionConfig = {
-  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',
-      required: true,
-      localized: true,
-      admin: {
-        components: {
-          Field: DescriptionField,
-          Cell: DescriptionCell,
-          Filter: DescriptionFilter,
-        },
-      },
-    },
-    {
-      name: 'componentDescription',
-      label: 'Component ViewDescription',
-      type: 'text',
-      admin: {
-        description: CustomDescriptionComponent,
-      },
-    },
-    {
-      name: 'array',
-      label: 'Array',
-      type: 'array',
-      fields: [
-        {
-          type: 'text',
-          name: 'nestedArrayCustomField',
-          label: 'Nested Array Custom Field',
-          admin: {
-            components: {
-              Field: NestedArrayField,
-            },
-          },
-        },
-      ],
-    },
-    {
-      name: 'group',
-      label: 'Group',
-      type: 'group',
-      admin: {
-        components: {
-          Field: GroupField,
-        },
-      },
-      fields: [
-        {
-          type: 'text',
-          name: 'nestedGroupCustomField',
-          label: 'Nested Group Custom Field',
-          admin: {
-            components: {
-              Field: NestedGroupField,
-            },
-          },
-        },
-      ],
-    },
-    {
-      type: 'row',
-      fields: [
-        {
-          name: 'nestedText1',
-          label: 'Nested Text 1',
-          type: 'text',
-          admin: {
-            components: {
-              Field: NestedText1Field,
-            },
-          },
-        }, {
-          name: 'nestedText2',
-          label: 'Nested Text 2',
-          type: 'text',
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-  admin: {
-    useAsTitle: 'title',
-    components: {
-      views: {
-        List: ListView,
-      },
-    },
-  },
-};
-
-export default CustomComponents;

demo/collections/CustomID.ts

@@ -1,22 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const CustomID: CollectionConfig = {
-  slug: 'custom-id',
-  labels: {
-    singular: 'CustomID',
-    plural: 'CustomIDs',
-  },
-  fields: [
-    {
-      name: 'id',
-      type: 'number',
-    },
-    {
-      name: 'name',
-      type: 'text',
-      required: true,
-    },
-  ],
-};
-
-export default CustomID;

demo/collections/DefaultValues.ts

@@ -1,287 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import checkRole from '../access/checkRole';
-import Email from '../blocks/Email';
-import Quote from '../blocks/Quote';
-import NumberBlock from '../blocks/Number';
-import CallToAction from '../blocks/CallToAction';
-
-const DefaultValues: CollectionConfig = {
-  slug: 'default-values',
-  labels: {
-    singular: 'Default Value Test',
-    plural: 'Default Value Tests',
-  },
-  admin: {
-    useAsTitle: 'text',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'text',
-      type: 'text',
-      label: 'Text',
-      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',
-    },
-    {
-      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', 'option-4'],
-      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',
-    },
-    {
-      type: 'row',
-      fields: [
-        {
-          name: 'email',
-          label: 'Email',
-          type: 'email',
-          defaultValue: 'some@email.com',
-        }, {
-          name: 'number',
-          label: 'Number',
-          type: 'number',
-          defaultValue: 5,
-        },
-      ],
-    },
-    {
-      type: 'group',
-      label: 'Group',
-      name: 'group',
-      defaultValue: {
-        nestedText1: 'neat',
-      },
-      fields: [
-        {
-          type: 'row',
-          fields: [
-            {
-              name: 'nestedText1',
-              label: 'Nested Text 1',
-              type: 'text',
-              defaultValue: 'nested default text 1',
-            }, {
-              name: 'nestedText2',
-              label: 'Nested Text 2',
-              type: 'text',
-              defaultValue: 'nested default text 2',
-            },
-          ],
-        },
-      ],
-    },
-    {
-      type: 'array',
-      label: 'Array',
-      name: 'array',
-      admin: {
-        readOnly: true,
-      },
-      defaultValue: [
-        {
-          arrayText1: 'Get out',
-        },
-      ],
-      fields: [
-        {
-          type: 'row',
-          fields: [
-            {
-              name: 'arrayText1',
-              label: 'Array Text 1',
-              type: 'text',
-              admin: {
-                width: '50%',
-              },
-              defaultValue: 'default array text',
-            },
-            {
-              name: 'arrayText2',
-              label: 'Array Text 2',
-              type: 'text',
-              admin: {
-                width: '50%',
-              },
-              access: {
-                read: ({ req: { user } }) => Boolean(user),
-                update: ({ req: { user } }) => checkRole(['admin'], user),
-              },
-            },
-          ],
-        },
-        {
-          type: 'text',
-          name: 'arrayText3',
-          label: 'Array Text 3',
-          admin: {
-            readOnly: true,
-          },
-        },
-        {
-          name: 'checkbox',
-          label: 'Checkbox',
-          type: 'checkbox',
-          defaultValue: true,
-        },
-      ],
-    },
-    {
-      type: 'blocks',
-      label: 'Blocks Content',
-      name: 'blocks',
-      labels: {
-        singular: 'Block',
-        plural: 'Blocks',
-      },
-      blocks: [Email, NumberBlock, Quote, CallToAction],
-      localized: true,
-      admin: {
-        readOnly: true,
-      },
-      defaultValue: [
-        {
-          blockType: 'email',
-          testEmail: 'dev@payloadcms.com',
-        },
-      ],
-    },
-    {
-      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',
-      defaultValue: 'my textarea text',
-    },
-    {
-      name: 'slug',
-      type: 'text',
-      label: 'Slug',
-      admin: {
-        position: 'sidebar',
-      },
-      localized: true,
-      unique: true,
-      defaultValue: 'my-slug',
-    },
-    {
-      name: 'checkbox',
-      type: 'checkbox',
-      label: 'Checkbox',
-      admin: {
-        position: 'sidebar',
-      },
-      defaultValue: true,
-    },
-    {
-      name: 'richText',
-      type: 'richText',
-      label: 'Rich Text',
-      admin: {
-        elements: [
-          'h1',
-          'h2',
-          'h3',
-          'h4',
-          'h5',
-          'h6',
-          'blockquote',
-          'ul',
-          'ol',
-          'link',
-        ],
-        leaves: [
-          'bold',
-          'italic',
-          'underline',
-          'strikethrough',
-        ],
-      },
-      defaultValue: [{
-        children: [{ text: 'Cookin now' }],
-      }],
-    },
-  ],
-  timestamps: true,
-};
-export default DefaultValues;

demo/collections/File.ts

@@ -1,70 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import checkRole from '../access/checkRole';
-
-const access = ({ req: { user } }) => {
-  const isAdmin = checkRole(['admin'], user);
-
-  if (isAdmin) {
-    return true;
-  }
-
-  if (user) {
-    return {
-      owner: {
-        equals: user.id,
-      },
-    };
-  }
-
-  return false;
-};
-
-const Files: CollectionConfig = {
-  slug: 'files',
-  labels: {
-    singular: 'File',
-    plural: 'Files',
-  },
-  upload: {
-    staticURL: '/files',
-    staticDir: './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',
-  },
-};
-
-export default Files;

demo/collections/HiddenFields.ts

@@ -1,35 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const HiddenFields: CollectionConfig = {
-  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',
-      admin: {
-        hidden: true,
-      },
-      required: true,
-    },
-    {
-      name: 'hiddenAPI',
-      type: 'text',
-      label: 'Hidden on API',
-      hidden: true,
-      required: true, // this should not matter
-    },
-  ],
-};
-
-export default HiddenFields;

demo/collections/Hooks.ts

@@ -1,95 +0,0 @@
-/* eslint-disable no-param-reassign */
-
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const Hooks: CollectionConfig = {
-  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.data.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',
-      required: true,
-      localized: true,
-    },
-  ],
-  timestamps: true,
-};
-
-export default Hooks;

demo/collections/LocalOperations.ts

@@ -1,38 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const LocalOperations: CollectionConfig = {
-  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',
-        });
-
-        const blocksGlobal = await req.payload.findGlobal({
-          slug: 'blocks-global',
-        });
-
-        formattedData.localizedPosts = localizedPosts;
-        formattedData.blocksGlobal = blocksGlobal;
-
-        return formattedData;
-      },
-    ],
-  },
-  fields: [
-    {
-      name: 'title',
-      type: 'text',
-      label: 'title',
-      required: true,
-    },
-  ],
-};
-
-export default LocalOperations;

demo/collections/Localized.ts

@@ -1,142 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import { PayloadRequest } from '../../src/express/types';
-import { Block } from '../../src/fields/config/types';
-
-const validateLocalizationTransform = (hook: string, value, req: PayloadRequest) => {
-  if (req.locale !== 'all' && value !== undefined && typeof value !== 'string') {
-    console.error(hook, value);
-    throw new Error('Locale transformation should happen before hook is called');
-  }
-  return value;
-};
-
-const RichTextBlock: Block = {
-  slug: 'richTextBlock',
-  labels: {
-    singular: 'Rich Text Block',
-    plural: 'Rich Text Blocks',
-  },
-  fields: [
-    {
-      name: 'content',
-      localized: true,
-      type: 'richText',
-      admin: {
-        hideGutter: true,
-      },
-    },
-  ],
-};
-
-const LocalizedPosts: CollectionConfig = {
-  slug: 'localized-posts',
-  labels: {
-    singular: 'Localized Post',
-    plural: 'Localized Posts',
-  },
-  admin: {
-    useAsTitle: 'title',
-    defaultColumns: [
-      'title',
-      'priority',
-      'createdAt',
-    ],
-    enableRichTextRelationship: true,
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-      unique: true,
-      localized: true,
-      hooks: {
-        beforeValidate: [({ value, req }) => validateLocalizationTransform('beforeValidate', value, req)],
-        beforeChange: [({ value, req }) => validateLocalizationTransform('beforeChange', value, req)],
-        afterChange: [({ value, req }) => validateLocalizationTransform('afterChange', value, req)],
-        afterRead: [({ value, req }) => validateLocalizationTransform('afterRead', value, req)],
-      },
-    },
-    {
-      name: 'summary',
-      label: 'Summary',
-      type: 'text',
-      index: true,
-    },
-    {
-      name: 'description',
-      label: 'Description',
-      type: 'textarea',
-      required: true,
-      localized: true,
-    },
-    {
-      type: 'richText',
-      name: 'richText',
-      label: 'Rich Text',
-    },
-    {
-      name: 'priority',
-      label: 'Priority',
-      type: 'number',
-      required: true,
-      localized: true,
-    },
-    {
-      name: 'localizedGroup',
-      label: 'Localized Group',
-      type: 'group',
-      localized: true,
-      fields: [
-        {
-          type: 'text',
-          name: 'text',
-          label: 'Text',
-        },
-      ],
-    },
-    {
-      name: 'nonLocalizedGroup',
-      label: 'Non-Localized Group',
-      type: 'group',
-      fields: [
-        {
-          type: 'text',
-          name: 'text',
-          label: 'Text',
-          localized: true,
-        },
-      ],
-    },
-    {
-      type: 'array',
-      label: 'Non-Localized Array',
-      name: 'nonLocalizedArray',
-      maxRows: 3,
-      fields: [
-        {
-          type: 'text',
-          name: 'localizedEmbeddedText',
-          label: 'Localized Embedded Text',
-          localized: true,
-        },
-      ],
-    },
-    {
-      label: 'Blocks',
-      name: 'richTextBlocks',
-      type: 'blocks',
-      blocks: [
-        RichTextBlock,
-      ],
-    },
-  ],
-  timestamps: true,
-};
-
-export default LocalizedPosts;

demo/collections/LocalizedArray.ts

@@ -1,79 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import { FieldAccess } from '../../src/fields/config/types';
-import checkRole from '../access/checkRole';
-
-const PublicReadabilityAccess: FieldAccess = ({ req: { user }, siblingData }) => {
-  if (checkRole(['admin'], user)) {
-    return true;
-  }
-
-  if (siblingData?.allowPublicReadability) return true;
-
-  return false;
-};
-
-const LocalizedArrays: CollectionConfig = {
-  slug: 'localized-arrays',
-  labels: {
-    singular: 'Localized Array',
-    plural: 'Localized Arrays',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      type: 'array',
-      label: false,
-      name: 'array',
-      localized: true,
-      required: true,
-      minRows: 2,
-      maxRows: 4,
-      fields: [
-        {
-          type: 'row',
-          fields: [
-            {
-              name: 'allowPublicReadability',
-              label: 'Allow Public Readability',
-              type: 'checkbox',
-            },
-            {
-              name: 'arrayText1',
-              label: 'Array Text 1',
-              type: 'text',
-              required: true,
-              admin: {
-                width: '50%',
-              },
-              access: {
-                read: PublicReadabilityAccess,
-              },
-            },
-            {
-              name: 'arrayText2',
-              label: 'Array Text 2',
-              type: 'text',
-              required: true,
-              admin: {
-                width: '50%',
-              },
-            },
-          ],
-        },
-        {
-          type: 'text',
-          name: 'arrayText3',
-          label: 'Array Text 3',
-          admin: {
-            readOnly: true,
-          },
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-};
-
-export default LocalizedArrays;

demo/collections/Media.ts

@@ -1,78 +0,0 @@
-import { CollectionConfig, BeforeChangeHook } from '../../src/collections/config/types';
-
-const checkForUploadSizesHook: BeforeChangeHook = ({ req: { payloadUploadSizes }, data }) => {
-  if (typeof payloadUploadSizes === 'object') {
-    return {
-      ...data,
-      foundUploadSizes: true,
-    };
-  }
-
-  return data;
-};
-
-const Media: CollectionConfig = {
-  slug: 'media',
-  labels: {
-    singular: 'Media',
-    plural: 'Media',
-  },
-  access: {
-    read: () => true,
-  },
-  admin: {
-    enableRichTextRelationship: true,
-    description: 'No selfies please',
-  },
-  hooks: {
-    beforeChange: [
-      checkForUploadSizesHook,
-    ],
-  },
-  upload: {
-    staticURL: '/media',
-    staticDir: './media',
-    adminThumbnail: ({ doc }) => `/media/${doc.filename}`,
-    imageSizes: [
-      {
-        name: 'maintainedAspectRatio',
-        width: 1024,
-        height: null,
-        crop: 'center',
-      },
-      {
-        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,
-    },
-    {
-      name: 'foundUploadSizes',
-      type: 'checkbox',
-    },
-  ],
-  timestamps: true,
-};
-
-export default Media;

demo/collections/NestedArrays.ts

@@ -1,71 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const NestedArray: CollectionConfig = {
-  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',
-                },
-              ],
-            },
-          ],
-        },
-      ],
-    },
-  ],
-  timestamps: true,
-};
-
-export default NestedArray;

demo/collections/Preview.ts

@@ -1,34 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const Preview: CollectionConfig = {
-  slug: 'previewable-post',
-  labels: {
-    singular: 'Previewable Post',
-    plural: 'Previewable Posts',
-  },
-  admin: {
-    useAsTitle: 'title',
-    preview: (doc, { token }) => {
-      const { title } = doc;
-      if (title) {
-        return `http://localhost:3000/previewable-posts/${title}?preview=true&token=${token}`;
-      }
-
-      return null;
-    },
-  },
-  fields: [
-    {
-      name: 'title',
-      label: 'Title',
-      type: 'text',
-      maxLength: 100,
-      required: true,
-      unique: true,
-      localized: true,
-    },
-  ],
-  timestamps: true,
-};
-
-export default Preview;

demo/collections/PublicUsers.ts

@@ -1,61 +0,0 @@
-import checkRole from '../access/checkRole';
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const access = ({ req: { user } }) => checkRole(['admin'], user);
-
-const PublicUsers: CollectionConfig = {
-  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,
-    verify: true,
-    maxLoginAttempts: 5,
-    lockTime: 600 * 1000, // lock time in ms
-    cookies: {
-      secure: process.env.NODE_ENV === 'production',
-      sameSite: 'lax',
-      domain: undefined,
-    },
-  },
-  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,
-};
-
-export default PublicUsers;

demo/collections/RelationshipA.ts

@@ -1,64 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const RelationshipA: CollectionConfig = {
-  slug: 'relationship-a',
-  access: {
-    read: () => true,
-  },
-  labels: {
-    singular: 'Relationship A',
-    plural: 'Relationship A',
-  },
-  fields: [
-    {
-      name: 'post',
-      label: 'Post',
-      type: 'relationship',
-      relationTo: 'relationship-b',
-      localized: true,
-    },
-    {
-      name: 'LocalizedPost',
-      label: 'Localized Post',
-      type: 'relationship',
-      relationTo: 'localized-posts',
-      hasMany: true,
-      localized: true,
-    },
-    {
-      name: 'postLocalizedMultiple',
-      label: 'Localized Post Multiple',
-      type: 'relationship',
-      relationTo: ['localized-posts', 'all-fields', 'custom-id'],
-      hasMany: true,
-      localized: true,
-    },
-    {
-      name: 'postManyRelationships',
-      label: 'Post Many Relationships',
-      type: 'relationship',
-      relationTo: ['relationship-b'],
-      localized: true,
-      hasMany: false,
-    },
-    {
-      name: 'postMaxDepth',
-      maxDepth: 0,
-      label: 'Post With MaxDepth',
-      type: 'relationship',
-      relationTo: 'relationship-b',
-      hasMany: false,
-    },
-    {
-      name: 'customID',
-      label: 'CustomID Relation',
-      type: 'relationship',
-      relationTo: 'custom-id',
-      hasMany: true,
-      localized: true,
-    },
-  ],
-  timestamps: true,
-};
-
-export default RelationshipA;

demo/collections/RelationshipB.ts

@@ -1,40 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const RelationshipB: CollectionConfig = {
-  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,
-    },
-    {
-      name: 'postManyRelationships',
-      label: 'Post Many Relationships',
-      type: 'relationship',
-      relationTo: ['relationship-a', 'media'],
-      localized: true,
-      hasMany: false,
-    },
-    {
-      name: 'localizedPosts',
-      label: 'Localized Posts',
-      type: 'relationship',
-      hasMany: true,
-      relationTo: ['localized-posts', 'previewable-post'],
-    },
-  ],
-  timestamps: true,
-};
-
-export default RelationshipB;

demo/collections/RichText.ts

@@ -1,41 +0,0 @@
-import Button from '../client/components/richText/elements/Button';
-import PurpleBackground from '../client/components/richText/leaves/PurpleBackground';
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const RichText: CollectionConfig = {
-  slug: 'rich-text',
-  labels: {
-    singular: 'Rich Text',
-    plural: 'Rich Texts',
-  },
-  access: {
-    read: () => true,
-  },
-  fields: [
-    {
-      name: 'defaultRichText',
-      type: 'richText',
-      label: 'Default Rich Text',
-      required: true,
-    },
-    {
-      name: 'customRichText',
-      type: 'richText',
-      label: 'Customized Rich Text',
-      required: true,
-      admin: {
-        elements: [
-          'h2',
-          'h3',
-          Button,
-        ],
-        leaves: [
-          'bold',
-          PurpleBackground,
-        ],
-      },
-    },
-  ],
-};
-
-export default RichText;

demo/collections/Select.ts

@@ -1,70 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const Select: CollectionConfig = {
-  slug: 'select',
-  labels: {
-    singular: 'Select',
-    plural: 'Selects',
-  },
-  fields: [
-    {
-      name: 'Select',
-      type: 'select',
-      options: [{
-        value: 'one',
-        label: 'One',
-      }, {
-        value: 'two',
-        label: 'Two',
-      }, {
-        value: 'three',
-        label: 'Three',
-      }],
-      label: 'Select From',
-      required: true,
-    },
-    {
-      name: 'SelectHasMany',
-      type: 'select',
-      options: [{
-        value: 'one',
-        label: 'One',
-      }, {
-        value: 'two',
-        label: 'Two',
-      }, {
-        value: 'three',
-        label: 'Three',
-      }],
-      label: 'Select HasMany',
-      required: true,
-      hasMany: true,
-    },
-    {
-      name: 'SelectJustStrings',
-      type: 'select',
-      options: ['blue', 'green', 'yellow'],
-      label: 'Select Just Strings',
-      required: true,
-      hasMany: true,
-    },
-    {
-      name: 'Radio',
-      type: 'radio',
-      options: [{
-        value: 'one',
-        label: 'One',
-      }, {
-        value: 'two',
-        label: 'Two',
-      }, {
-        value: 'three',
-        label: 'Three',
-      }],
-      label: 'Choose From',
-      required: true,
-    },
-  ],
-};
-
-export default Select;

demo/collections/StrictPolicies.ts

@@ -1,76 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-import checkRole from '../access/checkRole';
-
-const StrictAccess: CollectionConfig = {
-  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,
-};
-
-export default StrictAccess;

demo/collections/Uniques.ts

@@ -1,25 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const Uniques: CollectionConfig = {
-  slug: 'uniques',
-  labels: {
-    singular: 'Unique',
-    plural: 'Uniques',
-  },
-  fields: [
-    {
-      name: 'title',
-      type: 'text',
-      label: 'Title',
-      required: true,
-      unique: true,
-    },
-    {
-      name: 'description',
-      type: 'textarea',
-      label: 'Description',
-    },
-  ],
-};
-
-export default Uniques;

demo/collections/UnstoredMedia.ts

@@ -1,35 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const UnstoredMedia: CollectionConfig = {
-  slug: 'unstored-media',
-  labels: {
-    singular: 'Unstored Media',
-    plural: 'Unstored Media',
-  },
-  access: {
-    read: () => true,
-  },
-  upload: {
-    staticURL: '/unstored-media',
-    disableLocalStorage: true,
-    imageSizes: [
-      {
-        name: 'tablet',
-        width: 640,
-        height: 480,
-        crop: 'left top',
-      },
-    ],
-  },
-  fields: [
-    {
-      name: 'alt',
-      label: 'Alt Text',
-      type: 'text',
-      required: true,
-      localized: true,
-    },
-  ],
-};
-
-export default UnstoredMedia;

demo/collections/Validations.ts

@@ -1,113 +0,0 @@
-import { CollectionConfig } from '../../src/collections/config/types';
-
-const Validations: CollectionConfig = {
-  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;
-          },
-        },
-      ],
-    },
-  ],
-};
-
-export default Validations;

demo/custom-index.html

@@ -1,15 +0,0 @@
-<!DOCTYPE HTML>
-<html>
-
-<head>
-  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-  <meta name="viewport" content="width=device-width, initial-scale=1" />
-  <meta name="application-name" content="My Payload Application" />
-</head>
-
-<body>
-  <div id="app"></div>
-  <div id="portal"></div>
-</body>
-
-</html>

demo/customComponents/CollectionDescription/index.tsx

@@ -1,9 +0,0 @@
-import React from 'react';
-
-const CollectionDescription: React.FC = () => (
-  <div>
-    Collection description
-  </div>
-);
-
-export default CollectionDescription;

demo/customComponents/Description/index.tsx

@@ -1,11 +0,0 @@
-import React from 'react';
-
-const CustomDescriptionComponent: React.FC = ({ value }) => (
-  <div>
-    Character count:
-    {' '}
-    { value?.length || 0 }
-  </div>
-);
-
-export default CustomDescriptionComponent;

demo/customComponents/views/Account/index.tsx

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const CustomAccountView: React.FC = () => <div>fake account view</div>;
-
-export default CustomAccountView;

demo/customComponents/views/Dashboard/index.tsx

@@ -1,5 +0,0 @@
-import React from 'react';
-
-const CustomDashboardView: React.FC = () => <div>fake dashboard view</div>;
-
-export default CustomDashboardView;

demo/globals/BlocksGlobal.ts

@@ -1,22 +0,0 @@
-import checkRole from '../access/checkRole';
-import Quote from '../blocks/Quote';
-import CallToAction from '../blocks/CallToAction';
-import { GlobalConfig } from '../../src/globals/config/types';
-
-export default {
-  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,
-    },
-  ],
-} as GlobalConfig;

demo/globals/GlobalWithStrictAccess.ts

@@ -1,35 +0,0 @@
-import { GlobalConfig } from '../../src/globals/config/types';
-import checkRole from '../access/checkRole';
-
-export default {
-  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,
-    },
-  ],
-} as GlobalConfig;

demo/globals/NavigationArray.ts

@@ -1,30 +0,0 @@
-import { GlobalConfig } from '../../src/globals/config/types';
-import checkRole from '../access/checkRole';
-
-export default {
-  slug: 'navigation-array',
-  access: {
-    update: ({ req: { user } }) => checkRole(['admin', 'user'], user),
-    read: () => true,
-  },
-  admin: {
-    description: 'A description for the editor',
-  },
-  fields: [
-    {
-      name: 'array',
-      label: 'Array',
-      type: 'array',
-      localized: true,
-      fields: [{
-        name: 'text',
-        label: 'Text',
-        type: 'text',
-      }, {
-        name: 'textarea',
-        label: 'Textarea',
-        type: 'textarea',
-      }],
-    },
-  ],
-} as GlobalConfig;

demo/index.js

@@ -1,14 +0,0 @@
-const babelConfig = require('../babel.config');
-
-require('@babel/register')({
-  ...babelConfig,
-  extensions: ['.ts', '.tsx', '.js', '.jsx'],
-  env: {
-    development: {
-      sourceMaps: 'inline',
-      retainLines: true,
-    },
-  },
-});
-
-require('./server.ts');

demo/payload.config.ts

@@ -1,143 +0,0 @@
-import path from 'path';
-import { buildConfig } from '../src/config/build';
-
-import Admin from './collections/Admin';
-import AllFields from './collections/AllFields';
-import AutoLabel from './collections/AutoLabel';
-import Code from './collections/Code';
-import Conditions from './collections/Conditions';
-import CustomComponents from './collections/CustomComponents';
-import File from './collections/File';
-import Blocks from './collections/Blocks';
-import CustomID from './collections/CustomID';
-import DefaultValues from './collections/DefaultValues';
-import HiddenFields from './collections/HiddenFields';
-import Hooks from './collections/Hooks';
-import Localized from './collections/Localized';
-import LocalizedArray from './collections/LocalizedArray';
-import LocalOperations from './collections/LocalOperations';
-import Media from './collections/Media';
-import NestedArrays from './collections/NestedArrays';
-import Preview from './collections/Preview';
-import PublicUsers from './collections/PublicUsers';
-import RelationshipA from './collections/RelationshipA';
-import RelationshipB from './collections/RelationshipB';
-import RichText from './collections/RichText';
-import Select from './collections/Select';
-import StrictPolicies from './collections/StrictPolicies';
-import Validations from './collections/Validations';
-import Uniques from './collections/Uniques';
-import Geolocation from './collections/Geolocation';
-
-import BlocksGlobal from './globals/BlocksGlobal';
-import NavigationArray from './globals/NavigationArray';
-import GlobalWithStrictAccess from './globals/GlobalWithStrictAccess';
-import UnstoredMedia from './collections/UnstoredMedia';
-
-export default buildConfig({
-  cookiePrefix: 'payload',
-  serverURL: 'http://localhost:3000',
-  admin: {
-    user: 'admins',
-    indexHTML: path.resolve(__dirname, './client/index.html'),
-    // meta: {
-    //   titleSuffix: '- Payload Demo',
-    //   // ogImage: '/static/find-image-here.jpg',
-    //   // favicon: '/img/whatever.png',
-    // },
-    disable: false,
-    scss: path.resolve(__dirname, './client/scss/overrides.scss'),
-    components: {
-      // Nav: () => (
-      //   <div>Hello</div>
-      // ),
-      views: {
-        // Dashboard: CustomDashboardView,
-        // Account: CustomAccountView,
-      },
-    },
-    webpack: (config) => config,
-  },
-  collections: [
-    Admin,
-    AllFields,
-    AutoLabel,
-    Code,
-    Conditions,
-    CustomComponents,
-    CustomID,
-    File,
-    DefaultValues,
-    Blocks,
-    HiddenFields,
-    Hooks,
-    Localized,
-    LocalizedArray,
-    LocalOperations,
-    Media,
-    NestedArrays,
-    Preview,
-    PublicUsers,
-    RelationshipA,
-    RelationshipB,
-    RichText,
-    Select,
-    StrictPolicies,
-    Validations,
-    Uniques,
-    UnstoredMedia,
-    Geolocation,
-  ],
-  globals: [
-    NavigationArray,
-    GlobalWithStrictAccess,
-    BlocksGlobal,
-  ],
-  cors: [
-    'http://localhost',
-    'http://localhost:3000',
-    'http://localhost:8080',
-    'http://localhost:8081',
-  ],
-  csrf: [
-    'http://localhost:3000',
-    'https://other-app-here.com',
-  ],
-  routes: {
-    api: '/api',
-    admin: '/admin',
-    graphQL: '/graphql',
-    graphQLPlayground: '/graphql-playground',
-  },
-  defaultDepth: 2,
-  graphQL: {
-    maxComplexity: 1000,
-    disablePlaygroundInProduction: false,
-    disable: false,
-  },
-  // rateLimit: {
-  //   window: 15 * 60 * 100,
-  //   max: 100,
-  //   trustProxy: true,
-  //   skip: (req) => req.ip === '127.0.0.1',
-  // },
-  maxDepth: 10,
-  localization: {
-    locales: [
-      'en',
-      'es',
-    ],
-    defaultLocale: 'en',
-    fallback: true,
-  },
-  hooks: {
-    afterError: (err) => {
-      console.error('global error config handler', err);
-    },
-  },
-  upload: {
-    limits: {
-      fileSize: 10000000, // 10MB
-    },
-  },
-});

demo/server.ts

@@ -1,40 +0,0 @@
-/* eslint-disable no-console */
-import express from 'express';
-import path from 'path';
-import payload from '../src';
-
-const expressApp = express();
-
-expressApp.use('/static', express.static(path.resolve(__dirname, 'client/static')));
-
-payload.init({
-  secret: 'SECRET_KEY',
-  mongoURL: 'mongodb://localhost/payload',
-  express: expressApp,
-  email: {
-    fromName: 'Payload',
-    fromAddress: 'hello@payloadcms.com',
-  },
-  onInit: (app) => {
-    app.logger.info('Payload Demo 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);
-
-expressApp.listen(3000, async () => {
-  payload.logger.info(`Admin URL on ${payload.getAdminURL()}`);
-  payload.logger.info(`API URL on ${payload.getAPIURL()}`);
-});

docs/access-control/collections.mdx

@@ -27,8 +27,10 @@ If a Collection supports [`Authentication`](/docs/authentication/overview), the
 | **[`unlock`](#unlock)** | Used to restrict which users can access the `unlock` operation |
 
 **Example Collection config:**
-```js
-export default {
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const Posts: CollectionConfig = {
   slug: "posts",
   // highlight-start
   access: {
@@ -40,56 +42,135 @@ export default {
   },
   // highlight-end
 };
+
+export default Categories;
 ```
 
 ### Create
 
 Returns a boolean which allows/denies access to the `create` request.
 
-**Available argument properties :**
+**Available argument properties:**
 
-| Option    | Description |
-| --------- | ----------- |
-| **`req`** | The Express `request` object containing the currently authenticated `user` |
+| 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 :**
+**Available argument properties:**
 
 | Option    | Description |
 | --------- | ----------- |
 | **`req`** | The Express `request` object containing the currently authenticated `user` |
-| **`id`**  | `id` of document requested, if within `findByID`. Otherwise, `id` is undefined. |
+| **`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 :**
+**Available argument properties:**
 
-| Option    | Description |
-| --------- | ----------- |
-| **`req`** | The Express `request` object containing the currently authenticated `user` |
-| **`id`**  | `id` of document requested to update |
+| 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 :**
+**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 :**
+**Available argument properties:**
 
 | Option    | Description |
 | --------- | ----------- |
@@ -99,7 +180,7 @@ If the Collection is [used to access the Payload Admin panel](/docs/admin/overvi
 
 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 :**
+**Available argument properties:**
 
 | Option    | Description |
 | --------- | ----------- |

docs/access-control/fields.mdx

@@ -17,8 +17,10 @@ Field Access Control is specified with functions inside a field's config. All fi
 | **[`update`](#update)**  | Allows or denies the ability to update a field's value |
 
 **Example Collection config:**
-```js
-export default {
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const Posts: CollectionConfig = {
   slug: 'posts',
   fields: [
     {
@@ -33,7 +35,7 @@ export default {
       // highlight-end
     };
   ],
-}
+};
 ```
 
 ### Create
@@ -58,7 +60,7 @@ Returns a boolean which allows or denies the ability to read a field's value. If
 | ----------------- | ----------- |
 | **`req`**         | The Express `request` object containing the currently authenticated `user` |
 | **`id`**          | `id` of the document being read |
-| **`data`**        | The full data of the document being read. |
+| **`doc`**         | The full document data. |
 | **`siblingData`** | Immediately adjacent field data of the document being read. |
 
 ### Update
@@ -73,3 +75,4 @@ Returns a boolean which allows or denies the ability to update a field's value.
 | **`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

@@ -18,21 +18,25 @@ You can define Global-level Access Control within each Global's `access` propert
 | **[`update`](#update)**  | Used in the `update` Global operation |
 
 **Example Global config:**
-```js
-export default {
+```ts
+import { GlobalConfig } from 'payload/types';
+
+const Header: GlobalConfig = {
   slug: "header",
   // highlight-start
   access: {
-    read: ({ req: { user } }) => { ... },
-    update: ({ req: { user } }) => { ... },
+    read: ({ req: { user } }) => { /* */ },
+    update: ({ req: { user } }) => { /* */ },
   },
   // highlight-end
 };
+
+export default Header;
 ```
 
 ### Read
 
-Returns a boolean result to allow or deny a user's ability to read the Global.
+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:**
 
@@ -42,10 +46,11 @@ Returns a boolean result to allow or deny a user's ability to read the Global.
 
 ### Update
 
-Returns a boolean result to allow or deny a user's ability to update the Global.
+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` |
+| 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

@@ -8,6 +8,11 @@ keywords: overview, access control, permissions, documentation, Content Manageme
 
 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
@@ -23,7 +28,7 @@ Access control within Payload is extremely powerful while remaining easy and int
 
 **Default Access function:**
 
-```js
+```ts
 const defaultPayloadAccess = ({ req: { user } }) => {
   // Return `true` if a user is found
   // and `false` if it is undefined or null
@@ -43,3 +48,30 @@ 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/components.mdx

@@ -11,31 +11,49 @@ While designing the Payload Admin panel, we determined it should be as minimal a
 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 would accept.
+  <strong>Tip:</strong>
+  <br />
+  Custom components will automatically be provided with all props that the
+  default component would accept.
 </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 and mobile Nav in its entirety. |
-| **`views.Account`**   | The Account view is used to show the currently logged in user's Account page. |
-| **`views.Dashboard`** | The main landing page of the Admin panel. |
-| **`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. |
+| Path                         | Description                                                                                                                                                                                                 |
+| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`Nav`**                    | Contains the sidebar and mobile Nav in its entirety.                                                                                                                                                        |
+| **`logout.Button`**          | A custom React component.
+| **`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/master/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.                                                                                                                      |
+| **`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.                                                                                                                                     |
+| **`views.Account`**          | The Account view is used to show the currently logged in user's Account page.                                                                                                                               |
+| **`views.Dashboard`**        | The main landing page of the Admin panel.                                                                                                                                                                   |
+| **`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.                                                                                                                                                 |
+| **`routes`**                 | Define your own routes to add to the Payload Admin UI. [More](#custom-routes)                                                                                                                               |
+| **`providers`**              | Define your own provider components that will wrap the Payload Admin UI. [More](#custom-providers)                                                                                                          |
 
 #### Full example:
 
 `payload.config.js`
-```js
-import { buildConfig } from 'payload/config';
-import { MyCustomNav, MyCustomLogo, MyCustomIcon, MyCustomAccount, MyCustomDashboard } from './customComponents.js';
+
+```ts
+import { buildConfig } from "payload/config";
+import {
+  MyCustomNav,
+  MyCustomLogo,
+  MyCustomIcon,
+  MyCustomAccount,
+  MyCustomDashboard,
+  MyProvider,
+} from "./customComponents";
 
 export default buildConfig({
-  serverURL: 'http://localhost:3000',
   admin: {
     components: {
       Nav: MyCustomNav,
@@ -46,73 +64,190 @@ export default buildConfig({
       views: {
         Account: MyCustomAccount,
         Dashboard: MyCustomDashboard,
-      }
-    }
-  }
-})
+      },
+      providers: [MyProvider],
+    },
+  },
+});
 ```
 
-*For more examples regarding how to customize components, look at the [demo app](https://github.com/payloadcms/payload/tree/master/demo).*
+_For more examples regarding how to customize components, look at the following [examples](https://github.com/payloadcms/payload/tree/master/test/admin/components)._
 
 ### Collections
 
 You can override components on a Collection-by-Collection basis via each Collection's `admin` property.
 
-| Path    | Description  |
-| ----------------  | -------------|
-| **`views.Edit`**  | Used while a document within this Collection is being edited. |
-| **`views.List`**  | The `List` view is used to render a paginated, filterable table of Documents in this Collection. |
+| Path             | Description                                                                                      |
+| ---------------- | ------------------------------------------------------------------------------------------------ |
+| **`views.Edit`** | Used while a document within this Collection is being edited.                                    |
+| **`views.List`** | The `List` view is used to render a paginated, filterable table of Documents in this Collection. |
 
 ### Globals
 
 As with Collections, You can override components on a global-by-global basis via their `admin` property.
 
-| Path    | Description  |
-| ----------------  | -------------|
-| **`views.Edit`**  | Used while this Global is being edited. |
+| Path             | Description                             |
+| ---------------- | --------------------------------------- |
+| **`views.Edit`** | Used while this Global is being edited. |
 
 ### 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.
+  <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. |
-| **`Field`**     | Swap out the field itself within all `Edit` views. |
+| 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)                                                 |
 
-#### Sending and receiving values from the form
+## Cell Component
 
-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 `useFieldType` hook as follows:
+These are the props that will be passed to your custom Cell to use in your own components.
 
-```js
-import { useFieldType } from 'payload/components/forms';
+| 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.                  |
 
-const CustomTextField = ({ path }) => {
-  const { value, setValue } = useFieldType({ path });
+#### 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}
-    />
-  )
-}
+    <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,{" "}
+  <a href="/docs/admin/hooks" style={{ color: "black" }}>
+    click here
+  </a>
+  .
+</Banner>
+
+## Custom routes
+
+You can easily add your own custom routes to the Payload Admin panel using the `admin.components.routes` property. Payload currently uses the extremely powerful React Router v5.x and custom routes support all the properties of the React Router `<Route />` component.
+
+**Custom routes support the following properties:**
+
+| 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._
+
+#### Custom route components
+
+Your custom route 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 routes. If your route requires a user to
+  be logged in or to have certain access rights, you should handle that within
+  your route component yourself.
+</Banner>
+
+#### Example
+
+You can find examples of custom route 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 routes:
+
+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 routes of your own, take a look at the `admin.components.routes` property of the [Payload test admin config](https://github.com/payloadcms/payload/blob/master/test/admin/config.ts).
+
+## 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.
+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 locale
+
+In any custom component you can get the selected locale with the `useLocale` hook. 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]} </span>;
+};
+```

docs/admin/customizing-css.mdx

@@ -1,7 +1,7 @@
 ---
 title: Customizing CSS & SCSS
 label: Customizing CSS
-order: 30
+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
 ---
@@ -13,51 +13,37 @@ You can add your own CSS by providing your base Payload config with a path to yo
 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:**
-```js
+```ts
 import { buildConfig } from 'payload/config';
 import path from 'path';
 
 const config = buildConfig({
-	serverURL: 'http://localhost:3000',
 	admin: {
 		css: path.resolve(__dirname, 'relative/path/to/stylesheet.scss'),
 	},
-})
+});
 ```
 
-### Overriding SCSS variables
+### Overriding built-in styles
 
-You can specify your own SCSS variable stylesheet that will allow for the override of Payload's base theme. This unlocks a ton of powerful theming and design options such as:
+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.
 
-- Changing dashboard font families
-- Modifying color palette
-- Creating a dark theme
-- Etc.
+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.
 
-To do so, provide your base Payload config with a path to your own SCSS variable sheet.
+You can find the built-in Payload CSS variables within [`./src/admin/scss/app.scss`](https://github.com/payloadcms/payload/blob/master/src/admin/scss/app.scss) and [`./src/admin/scss/colors.scss`](https://github.com/payloadcms/payload/blob/master/src/admin/scss/colors.scss). The following variables are defined and can be overridden:
 
-**Example in payload.config.js:**
-```js
-import { buildConfig } from 'payload/config';
-import path from 'path';
+- 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
 
-const config = buildConfig({
-	serverURL: 'http://localhost:3000',
-	admin: {
-		scss: path.resolve(__dirname, 'relative/path/to/vars.scss'),
-	},
-})
-```
+#### Dark mode
 
-**Example stylesheet override:**
-```scss
-$font-body: 'Papyrus';
-$style-radius-m: 10px;
-```
-
-To reference all Sass variables that you can override, look at the default [SCSS variable stylesheet](https://github.com/payloadcms/payload/blob/master/src/admin/scss/vars.scss) within the Payload source code.
-
-<Banner type="error">
-	<strong>Warning:</strong><br />
-	Only SCSS variables, mixins, functions, and extends are allowed in <strong>your SCSS overrides</strong>. Do not attempt to add any CSS declarations to this file, as this variable stylesheet is imported by many components throughout the Payload Admin panel and will result in your CSS definition(s) being duplicated many times. If you need to add real CSS definitions, see "Adding your own CSS / SCSS" the top of this page.
+<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/hooks.mdx

@@ -0,0 +1,289 @@
+---
+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/master/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:
+
+| Action               | Description                                                         |
+|----------------------|---------------------------------------------------------------------|
+| **`fields`**         | Deprecated. This property cannot be relied on as up-to-date.        |
+| **`submit`**         | Method to trigger the form to submit                                |
+| **`dispatchFields`** | Dispatch actions to the form field state                            |
+| **`validateForm`**   | Trigger a validation of the form state                              |
+| **`createFormData`** | Create a `multipart/form-data` object from the current form's state |
+| **`disabled`**       | Boolean denoting whether or not the form is disabled                |
+| **`getFields`**      | Gets all fields from state                                          |
+| **`getField`**       | Gets a single field from state by path                              |
+| **`getData`**        | Returns the data stored in the form                                 |
+| **`getSiblingData`** | Returns form sibling data for the given field path                  |
+| **`setModified`**    | Set the form's `modified` state                                     |
+| **`setProcessing`**  | Set the form's `processing` state                                   |
+| **`setSubmitted`**   | Set the form's `submitted` state                                    |
+| **`formRef`**        | The ref from the form HTML element                                  |
+| **`reset`**          | Method to reset the form to its initial state                       |
+
+### 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                         |
+| **`type`**                | The type of document being edited (collection or global)                           |
+| **`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                               |
+
+**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 with the `useLocale` hook. 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] } </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.)                    |
+| **`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 } = useConfig<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

@@ -14,7 +14,7 @@ The Payload Admin panel is built with Webpack, code-split, highly performant (ev
   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>
 
-![Payload's Admin panel built in React](https://payloadcms.com/images/admin.jpg)
+![Payload's Admin panel built in React](https://payloadcms.com/images/docs/admin.jpg)
 
 *Screenshot of the Admin panel while editing a document from an example `AllFields` collection*
 
@@ -22,17 +22,20 @@ The Payload Admin panel is built with Webpack, code-split, highly performant (ev
 
 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) |
-| `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/master/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.
-| `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) |
+| 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) |
+| `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/master/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. |
+| `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) |                                                                                                                                                                                   |
+| **`logoutRoute`**     | The route for the `logout` page.                                                                                                                                                                 |
+| **`inactivityRoute`** | The route for the `logout` inactivity page.                                                                                                                                                         |
 
 
 ### The Admin User Collection
@@ -45,15 +48,14 @@ All options for the Admin panel are defined in your base Payload config file.
 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`:
-```js
+```ts
 import { buildConfig } from 'payload/config';
 
 const config = buildConfig({
-  serverURL: 'http://localhost:3000',
   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.
@@ -67,10 +69,10 @@ For example, you may wish to have two Collections that both support `Authenticat
 
 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.
-
-## License enforcement
-
-Payload requires a valid license key to be used on production domains. You can use it as much as you'd like locally and on staging / UAT domains, but when you deploy to production, you'll need a license key to activate Payload's Admin panel. For more information, [click here](/docs/production/licensing).

docs/admin/preferences.mdx

@@ -1,7 +1,7 @@
 ---
 title: Managing User Preferences
 label: Preferences
-order: 40
+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
 ---

docs/admin/webpack.mdx

@@ -1,7 +1,7 @@
 ---
 title: Webpack
 label: Webpack
-order: 50
+order: 60
 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
 ---
@@ -10,12 +10,11 @@ Payload uses Webpack 5 to build the Admin panel. It comes with support for many
 
 To extend the Webpack config, add the `webpack` key to your base Payload config, and provide a function that accepts the default Webpack config as its only argument:
 
-`payload.config.js`
-```js
+`payload.config.ts`
+```ts
 import { buildConfig } from 'payload/config';
 
 export default buildConfig({
-	serverURL: 'http://localhost:3000',
 	admin: {
 		// highlight-start
 		webpack: (config) => {
@@ -25,7 +24,7 @@ export default buildConfig({
 		}
 		// highlight-end
 	}
-})
+});
 ```
 
 ### Aliasing server-only modules
@@ -53,16 +52,17 @@ You may rely on server-only packages such as the above to perform logic in acces
 <br/><br/>
 
 `collections/Subscriptions/index.js`
-```js
+```ts
+import { CollectionConfig } from 'payload/types';
 import createStripeSubscription from './hooks/createStripeSubscription';
 
-const Subscription = {
+const Subscription: CollectionConfig = {
 	slug: 'subscriptions',
 	hooks: {
 		beforeChange: [
 			createStripeSubscription,
 		]
-	}
+	},
 	fields: [
 		{
 			name: 'stripeSubscriptionID',
@@ -70,7 +70,7 @@ const Subscription = {
 			required: true,
 		}
 	]
-}
+};
 
 export default Subscription;
 ```
@@ -128,7 +128,6 @@ const createStripeSubscriptionPath = path.resolve(__dirname, 'collections/Subscr
 const mockModulePath = path.resolve(__dirname, 'mocks/emptyObject.js');
 
 export default buildConfig({
-	serverURL: 'http://localhost:3000',
 	collections: [
 		Subscription
 	],
@@ -156,6 +155,11 @@ export default {};
 
 Now, when Webpack sees that you're attempting to import your `createStripeSubscriptionPath` file, it'll disregard that actual file and load your mock file instead. Not only will your Admin panel now bundle successfully, you will have optimized its filesize by removing unnecessary code! And you might have learned something about Webpack, too.
 
+<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>
+
 ## Admin environment vars
 
 <Banner type="warning">

docs/authentication/config.mdx

@@ -12,16 +12,18 @@ To enable Authentication on a collection, define an `auth` property and set it t
 
 ## 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 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) |
+| 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 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
 
@@ -37,7 +39,8 @@ Technically, both of these options will work for third-party integrations but th
 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.
+  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
@@ -45,14 +48,17 @@ To enable API keys on a collection, set the `useAPIKey` auth option to `true`. F
 To utilize your API key while interacting with the REST or GraphQL API, add the `Authorization` header.
 
 **For example, using Fetch:**
-```js
-const response = await fetch('http://localhost:3000/api/pages', {
+
+```ts
+const response = await fetch("http://localhost:3000/api/pages", {
   headers: {
     Authorization: `${collection.labels.singular} API-Key ${YOUR_API_KEY}`,
   },
 });
 ```
 
+Note: The label portion of the header is case-sensitive and will likely have a capitalized first character unless the label has been customized.
+
 ### Forgot Password
 
 You can customize how the Forgot Password workflow operates with the following options on the `auth.forgotPassword` property:
@@ -62,14 +68,21 @@ You can customize how the Forgot Password workflow operates with the following o
 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.
+  <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:
 
-```js
-{
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const Customers: CollectionConfig = {
   slug: 'customers',
   auth: {
     forgotPassword: {
@@ -95,12 +108,17 @@ Example:
       // 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.
+  <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`**
@@ -109,7 +127,7 @@ Similarly to the above `generateEmailHTML`, you can also customize the subject o
 
 Example:
 
-```js
+```ts
 {
   slug: 'customers',
   auth: {
@@ -134,8 +152,11 @@ Function that accepts one argument, containing `{ req, token, user }`, that allo
 
 Example:
 
-```js
-{
+```ts
+import { CollectionConfig } from 'payload/types';
+
+
+const Customers: CollectionConfig = {
   slug: 'customers',
   auth: {
     verify: {
@@ -149,12 +170,17 @@ Example:
       // 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.
+  <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`**
@@ -163,7 +189,7 @@ Similarly to the above `generateEmailHTML`, you can also customize the subject o
 
 Example:
 
-```js
+```ts
 {
   slug: 'customers',
   auth: {
@@ -177,3 +203,29 @@ Example:
   }
 }
 ```
+
+### 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.

docs/authentication/operations.mdx

@@ -17,10 +17,9 @@ The Access operation returns what a logged in user can and can't do with the col
 `GET http://localhost:3000/api/access`
 
 Example response:
-```js
+```ts
 {
   canAccessAdmin: true,
-  license: 'LICENSE_KEY_HERE',
   collections: {
     pages: {
       create: {
@@ -55,7 +54,7 @@ Example response:
 
 **Example GraphQL Query**:
 
-```
+```graphql
 query {
   Access {
     pages {
@@ -76,7 +75,7 @@ Returns either a logged in user with token or null when there is no logged in us
 `GET http://localhost:3000/api/[collection-slug]/me`
 
 Example response:
-```js
+```ts
 {
   user: { // The JWT "payload" ;) from the logged in user
     email: 'dev@payloadcms.com',
@@ -91,7 +90,7 @@ Example response:
 
 **Example GraphQL Query**:
 
-```
+```graphql
 query {
   Me[collection-singular-label] {
     user {
@@ -107,7 +106,7 @@ query {
 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**:
-```js
+```ts
 const res = await fetch('http://localhost:3000/api/[collection-slug]/login', {
   method: 'POST',
   headers: {
@@ -138,7 +137,7 @@ const json = await res.json();
 
 **Example GraphQL Mutation**:
 
-```
+```graphql
 mutation {
   login[collection-singular-label](email: "dev@payloadcms.com", password: "yikes") {
     user {
@@ -152,7 +151,7 @@ mutation {
 
 **Example Local API login**:
 
-```js
+```ts
 const result = await payload.login({
   collection: '[collection-slug]',
   data: {
@@ -167,7 +166,7 @@ const result = await payload.login({
 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**:
-```js
+```ts
 const res = await fetch('http://localhost:3000/api/[collection-slug]/logout', {
   method: 'POST',
   headers: {
@@ -193,7 +192,7 @@ This operation requires a non-expired token to send back a new one. If the user'
 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**:
-```js
+```ts
 const res = await fetch('http://localhost:3000/api/[collection-slug]/refresh-token', {
   method: 'POST',
   headers: {
@@ -240,18 +239,18 @@ mutation {
 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**:
-```js
+```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")
 }
@@ -259,7 +258,7 @@ mutation {
 
 **Example Local API verification**:
 
-```js
+```ts
 const result = await payload.verifyEmail({
   collection: '[collection-slug]',
   token: 'TOKEN_HERE',
@@ -273,7 +272,7 @@ If a user locks themselves out and you wish to deliberately unlock them, you can
 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**:
-```js
+```ts
 const res = await fetch(`http://localhost:3000/api/[collection-slug]/unlock`, {
   method: 'POST',
   headers: {
@@ -292,7 +291,7 @@ mutation {
 
 **Example Local API unlock**:
 
-```js
+```ts
 const result = await payload.unlock({
   collection: '[collection-slug]',
 })
@@ -307,7 +306,7 @@ The link to reset the user's password contains a token which is what allows the
 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**:
-```js
+```ts
 const res = await fetch(`http://localhost:3000/api/[collection-slug]/forgot-password`, {
   method: 'POST',
   headers: {
@@ -316,7 +315,7 @@ const res = await fetch(`http://localhost:3000/api/[collection-slug]/forgot-pass
   body: JSON.stringify({
     email: 'dev@payloadcms.com',
   }),
-})
+});
 ```
 
 **Example GraphQL Mutation**:
@@ -329,14 +328,14 @@ mutation {
 
 **Example Local API forgot password**:
 
-```js
+```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">
@@ -349,7 +348,7 @@ const token = await payload.forgotPassword({
 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**:
-```js
+```ts
 const res = await fetch(`http://localhost:3000/api/[collection-slug]/reset-password`, {
   method: 'POST',
   headers: {
@@ -359,7 +358,7 @@ const res = await fetch(`http://localhost:3000/api/[collection-slug]/reset-passw
     token: 'TOKEN_GOES_HERE'
     password: 'not-today',
   }),
-})
+});
 
 const json = await res.json();
 
@@ -380,7 +379,7 @@ const json = await res.json();
 
 **Example GraphQL Mutation**:
 
-```
+```graphql
 mutation {
   resetPassword[collection-singular-label](token: "TOKEN_GOES_HERE", password: "not-today")
 }

docs/authentication/overview.mdx

@@ -12,7 +12,7 @@ keywords: authentication, config, configuration, overview, documentation, Conten
 
 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/auth-admin.jpg)
+![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:**
@@ -32,8 +32,10 @@ Every Payload Collection can opt-in to supporting Authentication by specifying t
 
 Simple example collection:
 
-```js
-const Admins = {
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const Admins: CollectionConfig = {
   slug:
   // highlight-start
   auth: {
@@ -60,7 +62,7 @@ const Admins = {
 }
 ```
 
-**By enabling Authetication on a config, the following modifications will automatically be made to your Collection:**
+**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
@@ -95,7 +97,7 @@ However, if you use `fetch` or similar APIs to retrieve Payload resources from i
 
 Fetch example, including credentials:
 
-```js
+```ts
 const response = await fetch('http://localhost:3000/api/pages', {
   credentials: 'include',
 });
@@ -124,12 +126,11 @@ So, if a user of coolsite.com is logged in and just browsing around on the inter
 
 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.js`:
-```js
+`payload.config.ts`:
+```ts
 import { buildConfig } from 'payload/config';
 
 const config = buildConfig({
-  serverURL: 'http://localhost:3000',
   collections: [
     // collections here
   ],
@@ -149,7 +150,7 @@ export default config;
 In addition to authenticating via an HTTP-only cookie, you can also identify users via the `Authorization` header on an HTTP request.
 
 Example:
-```js
+```ts
 const request = await fetch('http://localhost:3000', {
   headers: {
     Authorization: `JWT ${token}`

docs/authentication/using-middleware.mdx

@@ -6,7 +6,7 @@ desc: Make full use of Payload's built-in authentication with your own custom Ex
 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, ist scopes all of its middleware to Payload-specific routers.
+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.
 
@@ -15,7 +15,7 @@ This approach has a ton of benefits - it's great for isolation of concerns and l
 </Banner>
 
 Example in `server.js`:
-```js
+```ts
 import express from 'express';
 import payload from 'payload';
 

docs/configuration/collections.mdx

@@ -17,20 +17,23 @@ It's often best practice to write your Collections in separate files and then im
 | **`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. |
-| **`description`**| Text or React component to display below the Collection label in the List view to give editors more information. |
 | **`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. [More](/docs/rest-api/overview#custom-endpoints) |
 
 *\* An asterisk denotes that a property is required.*
 
 #### Simple collection example
 
-```js
-const Orders = {
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const Orders: CollectionConfig = {
 	slug: 'orders',
 	fields: [
 		{
@@ -45,25 +48,29 @@ const Orders = {
 			required: true,
 		}
 	]
-}
+};
 ```
 
 #### More collection config examples
 
-You can find an assortment of [example collection configs](https://github.com/payloadcms/payload/blob/master/demo/collections) in the Payload source code on GitHub.
+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  |
-| ---------------------------- | -------------|
-| `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. |
-| `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. |
+| Option                      | Description  |
+| --------------------------- | -------------|
+| `group`                     | Text used as a label for grouping collection links together in the navigation. |
+| `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. |
 | `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). |
-| `components`                 | Swap in your own React components to be used within this collection. [More](/docs/admin/components#collections) |
+| `preview`                   | Function to generate preview URLS within the Admin panel that can point to your app. [More](#preview). |
+| `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) |
 
 ### Preview
 
@@ -74,30 +81,32 @@ If the function is specified, a Preview button will automatically appear in the
 **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.
+1. An `options` object, containing `locale` and `token` properties. The `token` is the currently logged-in user's JWT.
 
 **Example collection with preview function:**
 
-```js
-{
+```ts
+import { CollectionConfig } from 'payload/types';
+
+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 `https://bigbird.com/preview/posts/${doc.slug}?locale=${locale}`;
 			}
 
 			return null;
-		}
-	}
-}
+		},
+	},
+};
 ```
 
 ### Access control
@@ -112,18 +121,73 @@ Hooks are a powerful way to extend collection functionality and execute your own
 
 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:
 
-```js
+```ts
 import { CollectionConfig } from 'payload/types';
 
 // This is the type used for incoming collection configs.
 // Only the bare minimum properties are marked as required.
 ```
 
-```js
+```ts
 import { SanitizedCollectionConfig } from 'payload/types';
 
 // This is the type used after an incoming collection config is fully sanitized.

docs/configuration/express.mdx

@@ -16,7 +16,6 @@ Payload utilizes a few Express-specific middleware packages within its own route
 
 ```js
 {
-	serverURL: 'http://localhost:3000',
 	express: {
 		json: {
 			limit: '4mb',
@@ -37,7 +36,6 @@ To customize compression options, pass an object to the Payload config's `expres
 
 ```js
 {
-	serverURL: 'http://localhost:3000',
 	express: {
 		compression: {
 			// settings go here

docs/configuration/globals.mdx

@@ -21,13 +21,17 @@ As with Collection configs, it's often best practice to write your Globals in se
 | **`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)|
 
 *\* An asterisk denotes that a property is required.*
 
 #### Simple Global example
 
-```js
-const Nav = {
+```ts
+import { GlobalConfig } from 'payload/types';
+
+const Nav: GlobalConfig = {
 	slug: 'nav',
 	fields: [
 		{
@@ -45,12 +49,14 @@ const Nav = {
 			]
 		},
 	]
-}
+};
+
+export default Nav;
 ```
 
-#### More Global config examples
+#### Global config example
 
-You can find an assortment of [example Global configs](https://github.com/payloadcms/payload/blob/master/demo/globals) in the Payload source code on GitHub.
+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
 
@@ -76,14 +82,14 @@ Globals support all field types that Payload has to offer—including simple fie
 
 You can import global types as follows:
 
-```js
+```ts
 import { GlobalConfig } from 'payload/types';
 
 // This is the type used for incoming global configs.
 // Only the bare minimum properties are marked as required.
 ```
 
-```js
+```ts
 import { SanitizedGlobalConfig } from 'payload/types';
 
 // This is the type used after an incoming global config is fully sanitized.

docs/configuration/localization.mdx

@@ -14,22 +14,23 @@ Add the `localization` property to your Payload config to enable localization pr
 
 **Example Payload config set up for localization:**
 
-```js
-{
-	serverURL: 'http://localhost:3000',
-	collections: [
-		... // collections go here
-	],
-	localization: {
-		locales: [
-			'en',
-			'es',
-			'de',
-		],
-		defaultLocale: 'en',
-		fallback: true,
-	},
-}
+```ts
+import { buildConfig } from 'payload/config'
+
+export default buildConfig({
+  collections: [
+    // collections go here
+  ],
+  localization: {
+    locales: [
+      'en',
+      'es',
+      'de',
+    ],
+    defaultLocale: 'en',
+    fallback: true,
+  },
+});
 ```
 
 **Here is a brief explanation of each of the options available within the `localization` property:**
@@ -54,11 +55,11 @@ Payload localization works on a **field** level—not a document level. In addit
 
 ```js
 {
-	name: 'title',
-	type: 'text',
-	// highlight-start
-	localized: true,
-	// highlight-end
+  name: 'title',
+  type: 'text',
+  // highlight-start
+  localized: true,
+  // highlight-end
 }
 ```
 
@@ -67,8 +68,8 @@ With the above configuration, the `title` field will now be saved in the databas
 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.
+  <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>
 
 ### Retrieving localized docs
@@ -105,16 +106,16 @@ The `fallbackLocale` arg will accept valid locales as well as `none` to disable
 
 ```graphql
 query {
-	Posts(locale: de, fallbackLocale: none) {
-		docs {
-			title
-		}
-	}
+  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.
+  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
@@ -125,9 +126,9 @@ You can specify `locale` as well as `fallbackLocale` within the Local API as wel
 
 ```js
 const posts = await payload.find({
-	collection: 'posts',
-	locale: 'es',
-	fallbackLocale: false,
+  collection: 'posts',
+  locale: 'es',
+  fallbackLocale: false,
 })
 ```
 

docs/configuration/overview.mdx

@@ -8,7 +8,7 @@ keywords: overview, config, configuration, documentation, Content Management Sys
 
 Payload is a *config-based*, code-first CMS and application framework. The Payload config is central to everything that Payload does. It scaffolds the data that Payload stores as well as maintains custom React components, hook logic, custom validations, and much more. The config itself and all of its dependencies are run through Babel, so you can take full advantage of newer JavaScript features and even directly import React components containing JSX.
 
-<strong>Also, because the Payload source code is fully written in TypeScript, its configs are strongly typed—meaning that even if you aren't using TypeScript to build your project, your IDE (such as VSCode) may still provide helpful information like type-ahead suggestions while you write your config.</strong>
+**Also, because the Payload source code is fully written in TypeScript, its configs are strongly typed—meaning that even if you aren't using TypeScript to build your project, your IDE (such as VSCode) may still provide helpful information like type-ahead suggestions while you write your config.**
 
 <Banner type="warning">
 	<strong>Important:</strong><br />This file is included in the Payload admin bundle, so make sure you do not embed any sensitive information.
@@ -18,33 +18,35 @@ Payload is a *config-based*, code-first CMS and application framework. The Paylo
 
 | Option               | Description  |
 | -------------------- | -------------|
-| `serverURL`          | A _required_ string used to define the absolute URL of your app including the protocol, for example `https://'example.com`. No paths allowed, only protocol, domain and (optionally) port |
+| `serverURL`          | A string used to define the absolute URL of your app including the protocol, for example `https://example.com`. No paths allowed, only protocol, domain and (optionally) port |
 | `collections`        | An array of all Collections that Payload will manage. To read more about how to define your collection configs, [click here](/docs/configuration/collections). |
+| `cors`               | Either a whitelist array of URLS to allow CORS requests from, or a wildcard string (`'*'`) to accept incoming requests from any domain. |
 | `globals`            | An array of all Globals that Payload will manage. For more on Globals and their configs, [click here](/docs/configuration/globals). |
 | `admin`              | Base Payload admin configuration. Specify custom components, control metadata, set the Admin user collection, and [more](/docs/admin/overview#admin-options). |
 | `localization`       | Opt-in and control how Payload handles the translation of your content into multiple locales. [More](/docs/configuration/localization) |
-| `graphQL`            | Manage GraphQL-specific functionality here. Define your own queries and mutations, manage query complexity limits, and [more](/docs/graphql/overview). |
+| `graphQL`            | Manage GraphQL-specific functionality here. Define your own queries and mutations, manage query complexity limits, and [more](/docs/graphql/overview#graphql-options). |
 | `cookiePrefix`       | A string that will be prefixed to all cookies that Payload sets. |
-| `cors`               | Either a whitelist array of URLS to allow CORS requests from, or a wildcard string (`'*'`) to accept incoming requests from any domain. |
 | `csrf`               | A whitelist array of URLs to allow Payload cookies to be accepted from as a form of CSRF protection. [More](/docs/authentication/overview#csrf-protection) |
 | `defaultDepth`       | If a user does not specify `depth` while requesting a resource, this depth will be used. [More](/docs/getting-started/concepts#depth) |
 | `maxDepth`           | The maximum allowed depth to be permitted application-wide. This setting helps prevent against malicious queries. Defaults to `10`. |
+| `indexSortableFields`| Automatically index all sortable top-level fields in the database to improve sort performance and add database compatibility for Azure Cosmos and similar. |
 | `upload`             | Base Payload upload configuration. [More](/docs/upload/overview#payload-wide-upload-options). |
 | `routes`             | Control the routing structure that Payload binds itself to. Specify `admin`, `api`, `graphQL`, and `graphQLPlayground`. |
 | `email`              | Base email settings to allow Payload to generate email such as Forgot Password requests and other requirements. [More](/docs/email/overview#configuration) |
-| `express`            | Express-specific middleware options such as compression and JSON parsing. [More](/docs/configuration/express). |
+| `express`            | Express-specific middleware options such as compression and JSON parsing. [More](/docs/configuration/express) |
 | `debug`              | Enable to expose more detailed error information. |
+| `telemetry`          | Disable Payload telemetry by passing `false`. [More](/docs/configuration/overview#telemetry) |
 | `rateLimit`          | Control IP-based rate limiting for all Payload resources. Used to prevent DDoS attacks and [more](/docs/production/preventing-abuse#rate-limiting-requests). |
 | `hooks`              | Tap into Payload-wide hooks. [More](/docs/hooks/overview) |
 | `plugins`            | An array of Payload plugins. [More](/docs/plugins/overview) |
+| `endpoints`          | An array of custom API endpoints added to the Payload router. [More](/docs/rest-api/overview#custom-endpoints) |
 
 #### Simple example
 
-```js
+```ts
 import { buildConfig } from 'payload/config';
 
-const config = buildConfig({
-	serverURL: 'http://localhost:3000',
+export default buildConfig({
 	collections: [
 		{
 			slug: 'pages',
@@ -81,14 +83,11 @@ const config = buildConfig({
 		}
 	]
 });
-
-export default config;
-
 ```
 
 #### Full example config
 
-You can see a full [example config](https://github.com/payloadcms/payload/blob/master/demo/payload.config.ts) in the Payload source code on GitHub.
+You can see a full [example config](https://github.com/payloadcms/public-demo/blob/master/src/payload.config.ts) in the Public Demo source code on GitHub.
 
 ### Using environment variables in your config
 
@@ -138,7 +137,9 @@ The Payload config itself, as well as all files that it requires or imports, are
 
 Payload comes with `isomorphic-fetch` installed which means that even in Node, you can use the `fetch` API just as you would within the browser. No need to import `axios` or similar, unless you want to!
 
-#### Re-using the Payload `babel.config.js`
+#### Payload Config and Babel
+
+The entire Payload config is transpiled automatically by Payload via `babel`.
 
 If for any reason you need to re-use the built-in Payload `babel.config.js`, you can do so by importing it as follows:
 
@@ -146,20 +147,46 @@ If for any reason you need to re-use the built-in Payload `babel.config.js`, you
 import { config } from 'payload/babel';
 ```
 
+<Banner type="warning">
+  <strong>Note:</strong><br/>
+  Because the Payload config is transpiled internally, if you want to import it to share or reuse any of its properties within your own Node server's code, you need to make sure that <em>you manually transpile it</em> using <strong>babel-register</strong> or similar. For example, if you try to import your config directly into your server, your Node process will likely crash because the Payload config supports React components, TypeScript, and new ES6+ features.
+</Banner>
+
+However, you can share code, like for example your config's `serverURL` property by "hoisting" your shared properties above your config and writing any "shared" code in a module that is compatible with your Node environment.
+
+For example, to share your `serverURL`, you could create a file like the following:
+
+`serverURL.js`:
+
+```js
+const serverURL = 'http://localhost:3000';
+
+module.exports = serverURL;
+```
+
+Then, you could import this file into both your Payload config and your server, in an effort to avoid importing your full Payload config directly into your server.
+
+
 ### TypeScript
 
 You can import config types as follows:
 
-```js
+```ts
 import { Config } from 'payload/config';
 
 // This is the type used for an incoming Payload config.
 // Only the bare minimum properties are marked as required.
 ```
 
-```js
+```ts
 import { SanitizedConfig } from 'payload/config';
 
 // This is the type used after an incoming Payload config is fully sanitized.
 // Generally, this is only used internally by Payload.
 ```
+
+### Telemetry
+
+Payload collects **completely anonymous** telemetry data about general usage. This data is super important to us and helps us accurately understand how we're growing and what we can do to build the software into everything that it can possibly be. The telemetry that we collect also help us demonstrate our growth in an accurate manner, which helps us as we seek investment to build and scale our team. If we can accurately demonstrate our growth, we can more effectively continue to support Payload as free and open-source software. To opt out of telemetry, you can pass `telemetry: false` within your Payload config.
+
+For more information about what we track, take a look at our [privacy policy](/privacy).

docs/email/overview.mdx

@@ -27,10 +27,11 @@ The following options are configurable in the `email` property object as part of
 
 | Option                       | Description  |
 | ---------------------------- | -------------|
-| **`transport`**              | The NodeMailer transport object for when you want to do it yourself, not needed when transportOptions is set |
-| **`transportOptions`**       | An object that configures the transporter that Payload will create. For all the available options see the [NodeMailer documentation](https://nodemailer.com/smtp/) or see the examples below |
 | **`fromName`** *             | The name part of the From field that will be seen on the delivered email |
 | **`fromAddress`** *          | The email address part of the From field that will be used when delivering email |
+| **`transport`**              | The NodeMailer transport object for when you want to do it yourself, not needed when transportOptions is set |
+| **`transportOptions`**       | An object that configures the transporter that Payload will create. For all the available options see the [NodeMailer documentation](https://nodemailer.com/smtp/) or see the examples below |
+| **`logMockCredentials`**          | If set to true and no transport/transportOptions, ethereal credentials will be logged to console on startup |
 
 *\* An asterisk denotes that a property is required.*
 
@@ -39,7 +40,7 @@ The following options are configurable in the `email` property object as part of
 Simple Mail Transfer Protocol, also known as SMTP can be passed in using the `transportOptions` object on the `email` options.
 
 **Example email part using SMTP:**
-```js
+```ts
 payload.init({
   email: {
     transportOptions: {
@@ -59,6 +60,7 @@ payload.init({
     fromAddress: 'hello@example.com'
   }
   // ...
+})
 ```
 
 <Banner type="warning">
@@ -69,9 +71,9 @@ payload.init({
 
 Many third party mail providers are available and offer benefits beyond basic SMTP. As an example your payload init could look this if you wanted to use SendGrid.com though the same approach would work for any other [NodeMailer transports](https://nodemailer.com/transports/) shown here or provided by another third party.
 
-```js
-const nodemailerSendgrid = require('nodemailer-sendgrid');
-const payload = require('payload');
+```ts
+import payload from 'payload'
+import nodemailerSendgrid from 'nodemailer-sendgrid'
 
 const sendGridAPIKey = process.env.SENDGRID_API_KEY;
 
@@ -91,7 +93,10 @@ payload.init({
 ### Use a custom NodeMailer transport
 To take full control of the mail transport you may wish to use `nodemailer.createTransport()` on your server and provide it to Payload init.
 
-```js
+```ts
+import payload from 'payload'
+import nodemailer from 'nodemailer'
+
 const payload = require('payload');
 const nodemailer = require('nodemailer');
 
@@ -111,6 +116,7 @@ payload.init({
     transport
   },
   // ...
+});
 ```
 
 ### Sending Mail
@@ -119,7 +125,20 @@ With a working transport you can call it anywhere you have access to payload by
 ### Mock transport
 By default, Payload uses a mock implementation that only sends mail to the [ethereal](https://ethereal.email) capture service that will never reach a user's inbox. While in development you may wish to make use of the captured messages which is why the payload output during server output helpfully logs this out on the server console.
 
-**Console output when starting payload with a mock email instance**
+To see ethereal credentials, add `logMockCredentials: true` to the email options. This will cause them to be logged to console on startup.
+
+```ts
+payload.init({
+  email: {
+    fromName: 'Admin',
+    fromAddress: 'admin@example.com',
+    logMockCredentials: true, // Optional
+  },
+  // ...
+});
+```
+
+**Console output when starting payload with a mock email instance and logMockCredentials: true**
 ```
 [06:37:21] INFO  (payload): Starting Payload...
 [06:37:22] INFO  (payload): Payload Demo Initialized

docs/fields/array.mdx

@@ -16,7 +16,7 @@ keywords: array, fields, config, configuration, documentation, Content Managemen
 - Navigational structures where editors can specify nav items containing pages ([relationship field](/docs/fields/relationship)), an "open in new tab" [checkbox field](/docs/fields/checkbox)
 - Event agenda "timeslots" where you need to specify start & end time ([date field](/docs/fields/date)), label ([text field](/docs/fields/text)), and Learn More page [relationship](/docs/fields/relationship)
 
-![Array field in Payload admin panel](https://payloadcms.com/images/fields/array.jpg)
+![Array field in Payload admin panel](https://payloadcms.com/images/docs/fields/array.jpg)
 *Admin panel screenshot of an Array field with a Row containing two text fields, a read-only text field and a checkbox*
 
 ### Config
@@ -31,19 +31,30 @@ keywords: array, fields, config, configuration, documentation, Content Managemen
 | **`hooks`**          | Provide field-based hooks to control logic for this field. [More](/docs/fields/overview#field-level-hooks) |
 | **`access`**         | Provide field-based access control to denote what users can see and do with this field's data. [More](/docs/fields/overview#field-level-access-control) |
 | **`hidden`**         | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin panel. |
-| **`defaultValue`**   | Provide an array of row data to be used for this field's default value. |
+| **`defaultValue`**   | Provide an array of row data to be used for this field's default value. [More](/docs/fields/overview#default-values) |
 | **`localized`**      | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config. If enabled, a separate, localized set of all data within this Array will be kept, so there is no need to specify each nested field as `localized`. |
 | **`required`**       | Require this field to have a value. |
 | **`labels`**         | Customize the row labels appearing in the Admin dashboard. |
-| **`admin`**          | Admin-specific configuration. See the [default field admin config](/docs/fields/overview#admin-config) for more details. |
+| **`admin`**        | Admin-specific configuration. See below for [more detail](#admin-config).                                                                                                                                  |
 
 *\* An asterisk denotes that a property is required.*
 
+### Admin Config
+
+In addition to the default [field admin config](/docs/fields/overview#admin-config), you can adjust the following properties:
+
+| Option                 | Description                     |
+| ---------------------- | ------------------------------- |
+| **`initCollapsed`**    | Set the initial collapsed state |
+
+
 ### Example
 
-`collections/ExampleCollection.js`
-```js
-{
+`collections/ExampleCollection.ts`
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const ExampleCollection: CollectionConfig = {
   slug: 'example-collection',
   fields: [
     {
@@ -70,6 +81,5 @@ keywords: array, fields, config, configuration, documentation, Content Managemen
       ]
     }
   ]
-}
-
+};
 ```

docs/fields/blocks.mdx

@@ -16,7 +16,7 @@ keywords: blocks, fields, config, configuration, documentation, Content Manageme
 - A form builder tool where available block configs might be `Text`, `Select`, or `Checkbox`.
 - Virtual event agenda "timeslots" where a timeslot could either be a `Break`, a `Presentation`, or a `BreakoutSession`.
 
-![Blocks field in Payload admin panel](https://payloadcms.com/images/fields/blocks.jpg)
+![Blocks field in Payload admin panel](https://payloadcms.com/images/docs/fields/blocks.jpg)
 *Admin panel screenshot of a Blocks field type with Call to Action and Number block examples*
 
 
@@ -32,14 +32,22 @@ keywords: blocks, fields, config, configuration, documentation, Content Manageme
 | **`hooks`**          | Provide field-level hooks to control logic for this field. [More](/docs/fields/overview#field-level-hooks) |
 | **`access`**         | Provide field-level access control to denote what users can see and do with this field's data. [More](/docs/fields/overview#field-level-access-control) |
 | **`hidden`**         | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API response or the Admin panel. |
-| **`defaultValue`**   | Provide an array of block data to be used for this field's default value. |
+| **`defaultValue`**   | Provide an array of block data to be used for this field's default value. [More](/docs/fields/overview#default-values) |
 | **`localized`**      | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config. If enabled, a separate, localized set of all data within this field will be kept, so there is no need to specify each nested field as `localized`. || **`required`**       | Require this field to have a value. |
 | **`unique`**         | Enforce that each entry in the Collection has a unique value for this field. |
 | **`labels`**         | Customize the block row labels appearing in the Admin dashboard. |
-| **`admin`**          | Admin-specific configuration. See the [default field admin config](/docs/fields/overview#admin-config) for more details. |
+| **`admin`**        | Admin-specific configuration. See below for [more detail](#admin-config).                                                                                                                                  |
 
 *\* An asterisk denotes that a property is required.*
 
+### Admin Config
+
+In addition to the default [field admin config](/docs/fields/overview#admin-config), you can adjust the following properties:
+
+| Option                 | Description                     |
+| ---------------------- | ------------------------------- |
+| **`initCollapsed`**    | Set the initial collapsed state |
+
 ### Block configs
 
 Blocks are defined as separate configs of their own.
@@ -72,8 +80,10 @@ The Admin panel provides each block with a `blockName` field which optionally al
 ### Example
 
 `collections/ExampleCollection.js`
-```js
-const QuoteBlock = {
+```ts
+import { Block, CollectionConfig } from 'payload/types';
+
+const QuoteBlock: Block = {
   slug: 'Quote', // required
   imageURL: 'https://google.com/path/to/image.jpg',
   imageAltText: 'A nice thumbnail image to show what this block looks like',
@@ -90,7 +100,7 @@ const QuoteBlock = {
   ]
 };
 
-const ExampleCollection = {
+const ExampleCollection: CollectionConfig = {
   slug: 'example-collection',
   fields: [
     {
@@ -106,3 +116,12 @@ const ExampleCollection = {
 }
 
 ```
+
+### TypeScript
+
+As you build your own Block configs, you might want to store them in separate files but retain typing accordingly. To do so, you can import and use Payload's `Block` type:
+
+```ts
+import type { Block } from 'payload/types';
+
+```

docs/fields/checkbox.mdx

@@ -22,7 +22,7 @@ keywords: checkbox, fields, config, configuration, documentation, Content Manage
 | **`hooks`**          | Provide field-based hooks to control logic for this field. [More](/docs/fields/overview#field-level-hooks) |
 | **`access`**         | Provide field-based access control to denote what users can see and do with this field's data. [More](/docs/fields/overview#field-level-access-control) |
 | **`hidden`**         | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin panel. |
-| **`defaultValue`**   | Provide data to be used for this field's default value. |
+| **`defaultValue`**   | Provide data to be used for this field's default value, will default to false if field is also `required`. [More](/docs/fields/overview#default-values) |
 | **`localized`**      | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config. |
 | **`required`**       | Require this field to have a value. |
 | **`admin`**          | Admin-specific configuration. See the [default field admin config](/docs/fields/overview#admin-config) for more details. |
@@ -31,9 +31,11 @@ keywords: checkbox, fields, config, configuration, documentation, Content Manage
 
 ### Example
 
-`collections/ExampleCollection.js`
-```js
-{
+`collections/ExampleCollection.ts`
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const ExampleCollection: CollectionConfig = {
   slug: 'example-collection',
   fields: [
     {
@@ -43,6 +45,5 @@ keywords: checkbox, fields, config, configuration, documentation, Content Manage
       defaultValue: false,
     }
   ]
-}
-
+};
 ```

docs/fields/code.mdx

@@ -28,7 +28,7 @@ This field uses `prismjs` for syntax highlighting and `react-simple-code-editor`
 | **`hooks`**          | Provide field-based hooks to control logic for this field. [More](/docs/fields/overview#field-level-hooks) |
 | **`access`**         | Provide field-based access control to denote what users can see and do with this field's data. [More](/docs/fields/overview#field-level-access-control) |
 | **`hidden`**         | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin panel. |
-| **`defaultValue`**   | Provide data to be used for this field's default value. |
+| **`defaultValue`**   | Provide data to be used for this field's default value. [More](/docs/fields/overview#default-values) |
 | **`localized`**      | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config. |
 | **`required`**       | Require this field to have a value. |
 | **`admin`**          | Admin-specific configuration. See below for [more detail](#admin-config). |
@@ -39,13 +39,27 @@ This field uses `prismjs` for syntax highlighting and `react-simple-code-editor`
 
 In addition to the default [field admin config](/docs/fields/overview#admin-config), the Code field type also allows for the customization of a `language` property.
 
-Currently, the `language` property only supports JavaScript syntax but more support will be added as requested.
+The following `prismjs` plugins are imported, enabling the `language` property to accept the following values:
+
+| Plugin                       | Language |
+| ---------------------------- | ----------- |
+| **`prism-css`**              | `css` |
+| **`prism-clike`**            | `clike` |
+| **`prism-markup`**           | `markup`, `html`, `xml`, `svg`, `mathml`, `ssml`, `atom`, `rss` |
+| **`prism-javascript`**       | `javascript`, `js` |
+| **`prism-json`**             | `json` |
+| **`prism-jsx`**              | `jsx` |
+| **`prism-typescript`**       | `typescript`, `ts` |
+| **`prism-tsx`**              | `tsx` |
+| **`prism-yaml`**             | `yaml`, `yml` |
 
 ### Example
 
-`collections/ExampleCollection.js`
-```js
-{
+`collections/ExampleCollection.ts
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const ExampleCollection: CollectionConfig = {
   slug: 'example-collection',
   fields: [
     {
@@ -57,6 +71,5 @@ Currently, the `language` property only supports JavaScript syntax but more supp
       }
     }
   ]
-}
-
+};
 ```

docs/fields/collapsible.mdx

@@ -0,0 +1,53 @@
+---
+title: Collapsible Field
+label: Collapsible
+order: 60
+desc: With the Collapsible field, you can place fields within a collapsible layout component that can be collapsed / expanded.
+keywords: row, fields, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
+---
+
+<Banner >
+  The Collapsible field is presentational-only and only affects the Admin panel. By using it, you can place fields within a nice layout component that can be collapsed / expanded.
+</Banner>
+
+### Config
+
+| Option         | Description                                                               |
+| -------------- | ------------------------------------------------------------------------- |
+| **`label`** *  | A label to render within the header of the collapsible component.         |
+| **`fields`** * | Array of field types to nest within this Collapsible.                     |
+| **`admin`**    | Admin-specific configuration. See below for [more detail](#admin-config). |
+
+*\* An asterisk denotes that a property is required.*
+
+### Admin Config
+
+In addition to the default [field admin config](/docs/fields/overview#admin-config), you can adjust the following properties:
+
+| Option                 | Description                     |
+| ---------------------- | ------------------------------- |
+| **`initCollapsed`**    | Set the initial collapsed state |
+
+### Example
+
+`collections/ExampleCollection.ts`
+```ts
+import { CollectionConfig } from 'payload/types';
+
+const ExampleCollection: CollectionConfig = {
+  slug: 'example-collection',
+  fields: [
+    {
+      label: 'Header of collapsible goes here',
+      type: 'collapsible', // required
+      fields: [ // required
+        {
+          name: 'someTextField',
+          type: 'text',
+          required: true,
+        },
+      ],
+    }
+  ]
+};
+```