diff --git a/docs/Admin/overview.mdx b/docs/Admin/overview.mdx index 04346a2478..1b9f7219b9 100644 --- a/docs/Admin/overview.mdx +++ b/docs/Admin/overview.mdx @@ -38,7 +38,7 @@ All options for the Admin panel are defined in your base Payload config file. Important:
- The Payload Admin panel can only be used by one Collection that supports Authentication. + The Payload Admin panel can only be used by one Collection that supports Authentication. 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. diff --git a/docs/authentication/overview.mdx b/docs/authentication/overview.mdx index 80fa69a6eb..23f01c37bb 100644 --- a/docs/authentication/overview.mdx +++ b/docs/authentication/overview.mdx @@ -22,7 +22,7 @@ Authentication is used within the Payload Admin panel itself as well as througho - P2P app or social site where users need to log in and manage their profiles - Online game where players need to track their progress over time -By default, Payload provides you with a `User` collection that supports Authentication, which is used to access the Admin panel. But, you can add support to one or many Collections of your own. For more information on how to customize, override, or remove the default `User` collection, [click here](/docs/admin#the-admin-user-collection). +By default, Payload provides you with a `User` collection that supports Authentication, which is used to access the Admin panel. But, you can add support to one or many Collections of your own. For more information on how to customize, override, or remove the default `User` collection, [click here](/docs/admin/overview#the-admin-user-collection). ### Enabling Auth on a collection diff --git a/docs/configuration/collections.mdx b/docs/configuration/collections.mdx index a737ff4fea..7cc048b90b 100644 --- a/docs/configuration/collections.mdx +++ b/docs/configuration/collections.mdx @@ -17,11 +17,11 @@ 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. | -| **`admin`** | Admin-specific configuration. See below for [more detail](/docs/collections#admin). | +| **`admin`** | Admin-specific configuration. See below for [more detail](/docs/admin/overview#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/uploads/overview) 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. | *\* An asterisk denotes that a property is required.* diff --git a/docs/configuration/globals.mdx b/docs/configuration/globals.mdx index c93e530c2d..c8534c3c0d 100644 --- a/docs/configuration/globals.mdx +++ b/docs/configuration/globals.mdx @@ -71,4 +71,4 @@ Globals also fully support a smaller subset of Hooks. To learn more, go to the [ ### Field types -Globals support all field types that Payload has to offer—including simple fields like text and checkboxes all the way to more complicated layout-building field groups like Blocks. [Click here](/docs/fields/config) to learn more about field types. +Globals support all field types that Payload has to offer—including simple fields like text and checkboxes all the way to more complicated layout-building field groups like Blocks. [Click here](/docs/fields/overview) to learn more about field types. diff --git a/docs/email/overview.mdx b/docs/email/overview.mdx index afcb2cfc7b..59cb3f941b 100644 --- a/docs/email/overview.mdx +++ b/docs/email/overview.mdx @@ -19,7 +19,7 @@ in the `email` property object of your payload init call. Payload will make use **Three ways to set it up** -1. **Default**: When email is not needed, a mock email handler will be created and used when nothing is provided. This is ideal for development environments and can be changed later when ready to [go to production](/docs/production). +1. **Default**: When email is not needed, a mock email handler will be created and used when nothing is provided. This is ideal for development environments and can be changed later when ready to [go to production](/docs/production/deployment). 1. **Recommended**: Set the `transportOptions` and Payload will do the set up for you. 1. **Advanced**: The `transport` object can be assigned a nodemailer transport object set up in your server scripts and given for Payload to use. @@ -139,4 +139,4 @@ The mock email handler is used when payload is started with neither `transport` ### Using multiple mail providers -Payload supports the use of a single transporter of email, but there is nothing stopping you from having more. Consider a use case where sending bulk email is handled differently than transactional email and could be done using a [hook](/docs/hooks/config). +Payload supports the use of a single transporter of email, but there is nothing stopping you from having more. Consider a use case where sending bulk email is handled differently than transactional email and could be done using a [hook](/docs/hooks/overview). diff --git a/docs/fields/upload.mdx b/docs/fields/upload.mdx index 89a24b0241..7f93eabf8e 100644 --- a/docs/fields/upload.mdx +++ b/docs/fields/upload.mdx @@ -12,7 +12,7 @@ keywords: upload, images media, fields, config, configuration, documentation, Co Important:
- To use this field, you need to have a Collection configured to allow Uploads. For more information, click here to read about how to enable Uploads on a collection by collection basis. + To use this field, you need to have a Collection configured to allow Uploads. For more information, click here to read about how to enable Uploads on a collection by collection basis. **Example uses:** diff --git a/docs/production/preventing-abuse.mdx b/docs/production/preventing-abuse.mdx index 4104dee77e..0f12fcc03e 100644 --- a/docs/production/preventing-abuse.mdx +++ b/docs/production/preventing-abuse.mdx @@ -40,7 +40,7 @@ CSRF prevention will verify the authenticity of each request to your API to prev #### Cross Origin Resource Sharing (CORS) -To securely allow headless operation you will need to configure the allowed origins for requests to be able to use the Payload API. You can see how to set CORS as well as other payload configuration settings [here](http://localhost:3000/docs/configuration/overview) +To securely allow headless operation you will need to configure the allowed origins for requests to be able to use the Payload API. You can see how to set CORS as well as other payload configuration settings [here](/docs/configuration/overview) ### Limiting GraphQL Complexity Because GraphQL gives the power of query writing outside a server's control, someone with bad intentions might write a maliciously complex query and bog down your server. To prevent resource-intensive GraphQL requests, Payload provides a way specify complexity limits which are based on a complexity score that is calculated for each request.