Example: `strapi install graphql` will install the plugin `strapi-plugin-graphql`
-::: warning
+:::caution
Some plugins have admin panel integrations, your admin panel might have to be rebuilt. This can take some time.
:::
@@ -396,7 +299,7 @@ options [--delete-files]
Example: `strapi uninstall graphql --delete-files` will remove the plugin `strapi-plugin-graphql` and all the files in `./extensions/graphql`
-::: warning
+:::caution
Some plugins have admin panel integrations, your admin panel might have to be rebuilt. This can take some time.
:::
diff --git a/docs/developer-docs/latest/developer-resources/content-api/content-api.md b/docs/developer-docs/latest/developer-resources/content-api/content-api.md
index 80d26632d1..e69de29bb2 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/content-api.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/content-api.md
@@ -1,1109 +0,0 @@
----
-title: Content API - Strapi Developer Documentation
-description: Interact with your Content-Types using the REST API endpoints Strapi generates for you.
-sidebarDepth: 3
----
-
-# Content API
-
-## API Endpoints
-
-When you create a `Content Type` you will have a certain number of **REST API endpoints** available to interact with it.
-
-::: warning
-Components don't have API endpoints
-:::
-
-As an **example**, let's consider the following models:
-
-**Content Types**:
-
-- `Restaurant` (Collection Type)
-- `Homepage` (Single Type)
-
-**Components**:
-
-- `Opening hours` (category: `restaurant`)
-- `Title With Subtitle` (category: `content`)
-- `Image With Description` (category: `content`)
-
----
-
-:::: tabs
-
-::: tab Content Types
-
-#### `Restaurant` Content Type
-
-| Fields | Type | Description | Options |
-| :------------ | :---------- | :----------------------------------- | :------------------- |
-| name | string | Restaurant's title | |
-| slug | uid | Restaurant's slug | `targetField="name"` |
-| cover | media | Restaurant's cover image | |
-| content | dynamiczone | The restaurant profile content | |
-| opening_hours | component | Restaurant's opening hours component | `repeatable` |
-
----
-
-#### `Homepage` Content Type
-
-| Fields | Type | Description | Options |
-| :------- | :---------- | :----------------- | :------ |
-| title | string | Homepage title | |
-| subTitle | string | Homepage sub title | |
-| content | dynamiczone | Homepage content | |
-
-:::
-
-::: tab Components
-
-#### `Opening hours` Component
-
-| Fields | Type | Description |
-| :----------- | :----- | :------------------ |
-| day_interval | string | Meta's day interval |
-| opening_hour | string | Meta's opening hour |
-| closing_hour | string | Meta's closing hour |
-
----
-
-#### `Title With Subtitle` Component
-
-| Fields | Type | Description |
-| :------- | :----- | :------------ |
-| title | string | The title |
-| subTitle | string | The sub title |
-
----
-
-#### `Image With Description` Component
-
-| Fields | Type | Description |
-| :---------- | :----- | :-------------------- |
-| image | media | The image file |
-| title | string | The image title |
-| description | text | The image description |
-
-:::
-
-::::
-
-### Endpoints
-
-Here is the list of endpoints generated for each of your **Content Types**.
-
-
-
-:::: tabs
-
-::: tab Collection Type
-
-
-
-| Method | Path | Description |
-| :----- | :---------------------- | :----------------------------------- |
-| GET | `/{content-type}` | Get a list of {content-type} entries |
-| GET | `/{content-type}/:id` | Get a specific {content-type} entry |
-| GET | `/{content-type}/count` | Count {content-type} entries |
-| POST | `/{content-type}` | Create a {content-type} entry |
-| DELETE | `/{content-type}/:id` | Delete a {content-type} entry |
-| PUT | `/{content-type}/:id` | Update a {content-type} entry |
-
-
-
-:::
-
-::: tab Single Type
-
-
-
-| Method | Path | Description |
-| :----- | :---------------- | :-------------------------------- |
-| GET | `/{content-type}` | Get the {content-type} content |
-| PUT | `/{content-type}` | Update the {content-type} content |
-| DELETE | `/{content-type}` | Delete the {content-type} content |
-
-
-
-:::
-
-::::
-
-#### Examples
-
-Here are some Content Type examples
-
-##### Single Types
-
-:::: tabs
-
-::: tab Homepage
-
-`Homepage` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :---------- | :-------------------------- |
-| GET | `/homepage` | Get the homepage content |
-| PUT | `/homepage` | Update the homepage content |
-| DELETE | `/homepage` | Delete the homepage content |
-
-
-
-:::
-
-::: tab Contact
-
-`Contact` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :--------- | :------------------------- |
-| GET | `/contact` | Get the contact content |
-| PUT | `/contact` | Update the contact content |
-| DELETE | `/contact` | Delete the contact content |
-
-
-
-:::
-
-::::
-
-##### Collection Types
-
-:::: tabs
-
-::: tab Restaurant
-
-`Restaurant` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :------------------- | :------------------------ |
-| GET | `/restaurants` | Get a list of restaurants |
-| GET | `/restaurants/:id` | Get a specific restaurant |
-| GET | `/restaurants/count` | Count restaurants |
-| POST | `/restaurants` | Create a restaurant |
-| DELETE | `/restaurants/:id` | Delete a restaurant |
-| PUT | `/restaurants/:id` | Update a restaurant |
-
-
-
-:::
-
-::: tab Article
-
-`Article` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :---------------- | :--------------------- |
-| GET | `/articles` | Get a list of articles |
-| GET | `/articles/:id` | Get a specific article |
-| GET | `/articles/count` | Count articles |
-| POST | `/articles` | Create a article |
-| DELETE | `/articles/:id` | Delete a article |
-| PUT | `/articles/:id` | Update a article |
-
-
-
-:::
-
-::: tab Product
-
-`Product` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :---------------- | :--------------------- |
-| GET | `/products` | Get a list of products |
-| GET | `/products/:id` | Get a specific product |
-| GET | `/products/count` | Count products |
-| POST | `/products` | Create a product |
-| DELETE | `/products/:id` | Delete a product |
-| PUT | `/products/:id` | Update a product |
-
-
-
-:::
-
-::: tab Category
-
-`Category` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :------------------ | :----------------------- |
-| GET | `/categories` | Get a list of categories |
-| GET | `/categories/:id` | Get a specific category |
-| GET | `/categories/count` | Count categories |
-| POST | `/categories` | Create a category |
-| DELETE | `/categories/:id` | Delete a category |
-| PUT | `/categories/:id` | Update a category |
-
-
-
-:::
-
-::: tab Tag
-
-`Tag` **Content Type**
-
-
-
-| Method | Path | Description |
-| :----- | :------------ | :----------------- |
-| GET | `/tags` | Get a list of tags |
-| GET | `/tags/:id` | Get a specific tag |
-| GET | `/tags/count` | Count tags |
-| POST | `/tags` | Create a tag |
-| DELETE | `/tags/:id` | Delete a tag |
-| PUT | `/tags/:id` | Update a tag |
-
-
-
-:::
-
-::::
-
-### Get entries
-
-Returns entries matching the query filters. You can read more about parameters [here](#api-parameters).
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```js
-GET http://localhost:1337/restaurants
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-[
- {
- "id": 1,
- "name": "Restaurant 1",
- "cover": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "content": [
- {
- "__component": "content.title-with-subtitle",
- "id": 1,
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "id": 1,
- "image": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- "id": 1,
- "day_interval": "Tue - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
- }
-]
-```
-
-:::
-
-::::
-
-### Get an entry
-
-Returns an entry by id.
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```js
-GET http://localhost:1337/restaurants/1
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "id": 1,
- "title": "Restaurant 1",
- "cover": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "content": [
- {
- "__component": "content.title-with-subtitle",
- "id": 1,
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "id": 1,
- "image": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- "id": 1,
- "day_interval": "Tue - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
-}
-```
-
-:::
-
-::::
-
-### Count entries
-
-Returns the count of entries matching the query filters. You can read more about parameters [here](#api-parameters).
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```js
-GET http://localhost:1337/restaurants/count
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```
-1
-```
-
-:::
-
-::::
-
-### Create an entry
-
-Creates an entry and returns its value.
-
-If the [Internationalization (i18n) plugin](/developer-docs/latest/development/plugins/i18n.md) is installed, it's possible to use POST requests to the Content API to [create localized entries](/developer-docs/latest/development/plugins/i18n.md#creating-a-new-localized-entry).
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```js
-POST http://localhost:1337/restaurants
-```
-
-```json
-{
- "title": "Restaurant 1",
- "cover": 1,
- "content": [
- {
- "__component": "content.title-with-subtitle",
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "image": 1, // user form data to upload the file or an id to reference an exisiting image
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- "day_interval": "Tue - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "id": 1,
- "title": "restaurant 1",
- "cover": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "content": [
- {
- "__component": "content.title-with-subtitle",
- "id": 1,
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "id": 1,
- "image": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- "id": 1,
- "day_interval": "Tue - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
-}
-```
-
-:::
-
-::::
-
-
-### Update an entry
-
-Partially updates an entry by `id` and returns its value.
-Fields that aren't sent in the query are not changed in the database. Send a `null` value if you want to clear them.
-
-::: tip NOTE
-It's currently not possible to [update the locale of an entry](/developer-docs/latest/development/plugins/i18n.md#updating-an-entry).
-:::
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```js
-PUT http://localhost:1337/restaurants/1
-```
-
-```json
-{
- "title": "Restaurant 1",
- "content": [
- {
- "__component": "content.title-with-subtitle",
- // editing one of the previous item by passing its id
- "id": 2,
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "image": 1, // user form data to upload the file or an id to reference an exisiting image
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- // adding a new item
- "day_interval": "Sun",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- },
- {
- // editing one of the previous item by passing its id
- "id": 1,
- "day_interval": "Mon - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "id": 1,
- "title": "Restaurant 1",
- "cover": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "content": [
- {
- "__component": "content.title-with-subtitle",
- "id": 1,
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "id": 2,
- "image": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- "id": 1,
- "day_interval": "Mon - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- },
- {
- "id": 2,
- "day_interval": "Sun",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
-}
-```
-
-:::
-
-::::
-
-### Delete an entry
-
-Deletes an entry by id and returns its value.
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```js
-DELETE http://localhost:1337/restaurants/1
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "id": 1,
- "title": "Restaurant 1",
- "cover": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "content": [
- {
- "__component": "content.title-with-subtitle",
- "id": 1,
- "title": "Restaurant 1 title",
- "subTitle": "Cozy restaurant in the valley"
- },
- {
- "__component": "content.image-with-description",
- "id": 2,
- "image": {
- "id": 1,
- "name": "image.png",
- "hash": "123456712DHZAUD81UDZQDAZ",
- "sha256": "v",
- "ext": ".png",
- "mime": "image/png",
- "size": 122.95,
- "url": "http://localhost:1337/uploads/123456712DHZAUD81UDZQDAZ.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2019-12-09T00:00:00.000Z",
- "updated_at": "2019-12-09T00:00:00.000Z"
- },
- "title": "Amazing photography",
- "description": "This is an amazing photography taken..."
- }
- ],
- "opening_hours": [
- {
- "id": 1,
- "day_interval": "Mon - Sat",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- },
- {
- "id": 2,
- "day_interval": "Sun",
- "opening_hour": "7:30 PM",
- "closing_hour": "10:00 PM"
- }
- ]
-}
-```
-
-:::
-
-::::
-
-
-## API Parameters
-
-
-
-
-::: warning
-By default, the filters can only be used from `find` and `count` endpoints generated by the Content-Types Builder and the [CLI](../cli/CLI.md).
-:::
-
-
-
-
-Queries to Strapi Content API can use several API parameters:
-
-- [Filters](#filters)
-- [Sort](#sort)
-- [Limit](#limit)
-- [Start](#start)
-- [Publication State](#publication-state)
-- [Locale](#locale)
-
-### Filters
-
-When using filters you can either pass simple filters in the root of the query parameters or pass them in a `_where` parameter.
-
-Filters are used as a suffix of a field name:
-
-| Filter | Description |
-| :---------------- | :------------------------------ |
-| No suffix or `eq` | Equal |
-| `ne` | Not equal |
-| `lt` | Less than |
-| `gt` | Greater than |
-| `lte` | Less than or equal to |
-| `gte` | Greater than or equal to |
-| `in` | Included in an array |
-| `nin` | Not included in an array |
-| `contains` | Contains |
-| `ncontains` | Doesn't contain |
-| `containss` | Contains, case sensitive |
-| `ncontainss` | Doesn't contain, case sensitive |
-| `null` | Is null or not null |
-
-#### Examples
-
-##### Find users having `John` as first name.
-
-`GET /users?firstName=John`
-or
-`GET /users?firstName_eq=John`
-
-##### Find restaurants having a price equal or greater than `3`.
-
-`GET /restaurants?price_gte=3`
-
-##### Find multiple restaurant with id 3, 6, 8.
-
-`GET /restaurants?id_in=3&id_in=6&id_in=8`
-
-##### Using `_where`
-
-`GET /restaurants?_where[price_gte]=3`
-
-`GET /restaurants?_where[0][price_gte]=3&[0][price_lte]=7`
-
-#### Complex queries
-
-::: tip NOTE
-`OR` and `AND` operations are available starting from v3.1.0
-:::
-
-When building more complex queries you must use the `_where` query parameter in combination with the [`qs`](https://github.com/ljharb/qs) library.
-
-We are taking advantage of the capability of `qs` to parse nested objects to create more complex queries.
-
-This will give you full power to create complex queries with logical `AND` and `OR` operations.
-
-::: tip NOTE
-We strongly recommend using `qs` directly to generate complex queries instead of creating them manually.
-:::
-
-##### `AND` operator
-
-The filtering implicitly supports the `AND` operation when specifying an array of expressions in the filtering.
-
-**Examples**
-
-Restaurants that have 1 `stars` and a `pricing` less than or equal to 20:
-
-```js
-const query = qs.stringify({
- _where: [{ stars: 1 }, { pricing_lte: 20 }],
-});
-
-await request(`/restaurants?${query}`);
-// GET /restaurants?_where[0][stars]=1&_where[1][pricing_lte]=20
-```
-
-Restaurants that have a `pricing` greater than or equal to 20 and a `pricing` less than or equal to 50:
-
-```js
-const query = qs.stringify({
- _where: [{ pricing_gte: 20 }, { pricing_lte: 50 }],
-});
-
-await request(`/restaurants?${query}`);
-// GET /restaurants?_where[0][pricing_gte]=20&_where[1][pricing_lte]=50
-```
-
-##### `OR` operator
-
-To use the `OR` operation, you will need to use the `_or` filter and specify an array of expressions on which to perform the operation.
-
-**Examples**
-
-Restaurants that have 1 `stars` OR a `pricing` greater than 30:
-
-```js
-const query = qs.stringify({ _where: { _or: [{ stars: 1 }, { pricing_gt: 30 }] } });
-
-await request(`/restaurant?${query}`);
-// GET /restaurants?_where[_or][0][stars]=1&_where[_or][1][pricing_gt]=30
-```
-
-Restaurants that have a `pricing` less than 10 OR greater than 30:
-
-```js
-const query = qs.stringify({ _where: { _or: [{ pricing_lt: 10 }, { pricing_gt: 30 }] } });
-
-await request(`/restaurant?${query}`);
-// GET /restaurants?_where[_or][0][pricing_lt]=10&_where[_or][1][pricing_gt]=30
-```
-
-##### Implicit `OR` operator
-
-The query engine implicitly uses the `OR` operation when you pass an array of values in an expression.
-
-**Examples**
-
-Restaurants that have 1 or 2 `stars`:
-
-`GET /restaurants?stars=1&stars=2`
-
-or
-
-```js
-const query = qs.stringify({ _where: { stars: [1, 2] } });
-
-await request(`/restaurant?${query}`);
-// GET /restaurants?_where[stars][0]=1&_where[stars][1]=2
-```
-
-::: tip NOTE
-When using the `in` and `nin` filters the array is not transformed into a OR.
-:::
-
-##### Combining AND and OR operators
-
-Restaurants that have (2 `stars` AND a `pricing` less than 80) OR (1 `stars` AND a `pricing` greater than or equal to 50)
-
-```js
-const query = qs.stringify({
- _where: {
- _or: [
- [{ stars: 2 }, { pricing_lt: 80 }], // implicit AND
- [{ stars: 1 }, { pricing_gte: 50 }], // implicit AND
- ],
- },
-});
-
-await request(`/restaurants?${query}`);
-// GET /restaurants?_where[_or][0][0][stars]=2&_where[_or][0][1][pricing_lt]=80&_where[_or][1][0][stars]=1&_where[_or][1][1][pricing_gte]=50
-```
-
-**This also works with deep filtering**
-
-Restaurants that have (2 `stars` AND a `pricing` less than 80) OR (1 `stars` AND serves French food)
-
-```js
-const query = qs.stringify({
- _where: {
- _or: [
- [{ stars: 2 }, { pricing_lt: 80 }], // implicit AND
- [{ stars: 1 }, { 'categories.name': 'French' }], // implicit AND
- ],
- },
-});
-
-await request(`/restaurants?${query}`);
-// GET /restaurants?_where[_or][0][0][stars]=2&_where[_or][0][1][pricing_lt]=80&_where[_or][1][0][stars]=1&_where[_or][1][1][categories.name]=French
-```
-
-::: warning
-When creating nested queries, make sure the depth is less than 20 or the query string parsing will fail for now.
-:::
-
-#### Deep filtering
-
-Find restaurants owned by a chef who belongs to a restaurant with star equal to 5
-`GET /restaurants?chef.restaurant.star=5`
-
-::: warning
-Querying your API with deep filters may cause performance issues.
-If one of your deep filtering queries is too slow, we recommend building a custom route with an optimized version of your query.
-:::
-
-::: tip
-This feature doesn't allow you to filter nested models, e.g. `Find users and only return their posts older than yesterday`.
-
-To achieve this, there are three options:
-
-- Build a custom route.
-- Modify your services.
-- Use [GraphQL](/developer-docs/latest/development/plugins/graphql.md#query-api).
- :::
-
-::: warning
-This feature isn't available for **polymorphic** relations. This relation type is used in `media`, `component` and `dynamic zone` fields.
-:::
-
-### Sort
-
-Sort according to a specific field.
-
-#### Example
-
-##### Sort users by email.
-
-- ASC: `GET /users?_sort=email:ASC`
-- DESC: `GET /users?_sort=email:DESC`
-
-##### Sorting on multiple fields
-
-- `GET /users?_sort=email:asc,dateField:desc`
-- `GET /users?_sort=email:DESC,username:ASC`
-
-### Limit
-
-Limit the size of the returned results.
-
-The default limit is `100`
-
-#### Example
-
-##### Limit the result length to 30.
-
-`GET /users?_limit=30`
-
-You can require the full data set by passing a limit equal to `-1`.
-
-### Start
-
-Skip a specific number of entries (especially useful for pagination).
-
-#### Example
-
-##### Get the second page of results.
-
-`GET /users?_start=10&_limit=10`
-
-### Publication State
-
-::: tip NOTE
-This parameter can only be used on models with the **Draft & Publish** feature activated
-:::
-
-Only select entries matching the publication state provided.
-
-Handled states are:
-
-- `live`: Return only published entries (default)
-- `preview`: Return both draft entries & published entries
-
-#### Example
-
-##### Get published articles
-
-`GET /articles`
-OR
-`GET /articles?_publicationState=live`
-
-##### Get both published and draft articles
-
-`GET /articles?_publicationState=preview`
-
-::: tip NOTE
-If you only want to retrieve your draft entries, you can combine the `preview` mode and the `published_at` field.
-`GET /articles?_publicationState=preview&published_at_null=true`
-:::
-
-### Locale
-
-If the [Internationalization (i18n) plugin](/developer-docs/latest/development/plugins/i18n.md) is installed and [localization is enabled for the content-type](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-content-type), the `locale` API parameter can be used to [get entries from a specific locale](/developer-docs/latest/development/plugins/i18n.md#getting-localized-entries-with-the-locale-parameter).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations.md b/docs/developer-docs/latest/developer-resources/content-api/integrations.md
index f0ef126c36..bce05fa668 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations.md
@@ -1,6 +1,7 @@
---
-title: Integrations - Strapi Developer Documentation
+title: Integrations - Strapi Developer Docs
description: Integrate Strapi with a multitude of frameworks, frontend or backend programming languages.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations.html
---
# Integrations
@@ -15,7 +16,7 @@ In case you want to connect a React application with Strapi, we say that React i
If your Strapi application contains restaurants and you want to list them in your React application, all you need to do is to make an HTTP request to Strapi which will take care to give you a response containing your restaurants.
-The [API Endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints) documentation will give you all the keys in hand to interact with your Strapi API.
+The [API Endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints) documentation will give you all the keys in hand to interact with your Strapi API.
## Get started
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/11ty.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/11ty.md
index 5909a0236b..0956ba0b87 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/11ty.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/11ty.md
@@ -1,10 +1,13 @@
---
-title: Get started with 11ty - Strapi Developer Documentation
+title: Get started with 11ty - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless CMS and 11ty.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/11ty.html
---
# Getting Started with 11ty
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [11ty](https://www.11ty.dev/) remains the same except that you will not fetch the same content.
@@ -13,7 +16,7 @@ If you haven't gone through the Quick Start Guide, the way you request a Strapi
Create a `package.json` file, install and save Eleventy into your project.
-:::: tabs
+:::: tabs card
::: tab npm
@@ -44,7 +47,7 @@ npx @11ty/eleventy
## Configure 11ty
-11ty do not create any file structure for you. It's up to you to do it.
+11ty does not create any file structure for you. It's up to you to do it.
- Create a `./src/_data` folder containing a `categories.js` and a `restaurants.js` file. They will be used to fetch your content from Strapi.
- Create a `./src/_templates` folder containing a `default.liquid` file. It will be the default template of your project.
@@ -102,7 +105,7 @@ module.exports = eleventyConfig => {
- Finally, add the following packages to your application:
-:::: tabs
+:::: tabs card
::: tab npm
@@ -128,7 +131,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```js
const { default: axios } = require('axios');
@@ -142,8 +146,9 @@ module.exports = async () => {
}
};
```
+:::
-_Response_
+:::response Example response
```json
[
@@ -178,6 +183,8 @@ _Response_
}
]
```
+:::
+::::
### Example
@@ -246,7 +253,8 @@ Execute a `GET` request on the `category` Collection Type in order to fetch a sp
Be sure that you activated the `find` permission for the `category` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```js
const { default: axios } = require('axios');
@@ -260,8 +268,9 @@ module.exports = async () => {
}
};
```
+:::
-_Response_
+::: response Example response
```json
[
@@ -306,6 +315,9 @@ _Response_
}
]
```
+:::
+
+::::
### Example
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/angular.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/angular.md
index a7e3aa82a2..4e498cb90e 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/angular.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/angular.md
@@ -1,10 +1,13 @@
---
-title: Get started with Angular - Strapi Developer Documentation
+title: Get started with Angular - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Angular.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/angular.html
---
# Getting Started with Angular
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Angular](https://angular.io) remains the same except that you will not fetch the same content.
@@ -21,7 +24,7 @@ npx -p @angular/cli ng new angular-app
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab axios
@@ -45,11 +48,10 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-:::: tabs
-
-::: tab axios
+::::: tabs card
-_Request_
+:::: tab axios
+::: request Example GET request with axios
```js
import axios from 'axios';
@@ -60,11 +62,11 @@ axios.get('http://localhost:1337/restaurants').then(response => {
```
:::
+::::
-::: tab fetch
-
-_Request_
+:::: tab fetch
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'GET',
@@ -77,9 +79,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
[
{
@@ -113,12 +116,11 @@ _Response_
}
]
```
-
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -223,11 +225,10 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
+::::: tabs card
-::: tab axios
-
-_Request_
+:::: tab axios
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -244,11 +245,11 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
+:::: tab fetch
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'POST',
@@ -266,9 +267,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -290,12 +292,12 @@ _Response_
]
}
```
+:::
-::::
### Example
-:::: tabs
+:::: tabs card
`./src/app.module.ts`
@@ -536,14 +538,13 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
We consider that the id of your restaurant is `2`.
and the id of your category is `2`.
-::: tab axios
-
-_Request_
+:::: tab axios
+::: request Example PUT request with axios
```js
import axios from 'axios';
@@ -558,10 +559,10 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
+:::: tab fetch
+::: request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
@@ -580,8 +581,10 @@ fetch('http://localhost:1337/restaurants/2', {
```
:::
+::::
+:::::
-_Response_
+::: response Example response
```json
{
@@ -604,8 +607,7 @@ _Response_
]
}
```
-
-::::
+:::
## Starter
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/dart.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/dart.md
index 9c6c4f4560..fa01ff32f5 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/dart.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/dart.md
@@ -1,10 +1,13 @@
---
-title: Get started with Dart - Strapi Developer Documentation
+title: Get started with Dart - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Dart.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/dart.html
---
# Getting Started with Dart
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Dart](https://dart.dev/) remains the same except that you will not fetch the same content.
@@ -42,7 +45,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```dart
Map headers = {
@@ -57,8 +61,9 @@ var response = await http.get(
print(response.body)
```
+:::
-_Response_
+::: response Example response
```json
[
@@ -93,6 +98,8 @@ _Response_
}
]
```
+:::
+::::
### Example
@@ -127,7 +134,8 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-_Request_
+:::: api-call
+::: request Example POST request
```dart
Map headers = {
@@ -145,8 +153,9 @@ var response = await http.post(
});
);
```
+:::
-_Response_
+::: response Example response
```json
{
@@ -169,6 +178,8 @@ _Response_
]
}
```
+:::
+::::
### Example
@@ -215,7 +226,8 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example PUT request
```dart
Map headers = {
@@ -231,8 +243,9 @@ var response = await http.put(
});
);
```
+:::
-_Response_
+::: response Example response
```json
{
@@ -255,6 +268,8 @@ _Response_
]
}
```
+:::
+::::
### Example
@@ -301,4 +316,4 @@ void main() {
## Conclusion
-Here is how to request your Collection Types in Strapi using Dart. When you create a Collection Type or a Single Type you will have a certain number of [REST API endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints) available to interact with.
+Here is how to request your Collection Types in Strapi using Dart. When you create a Collection Type or a Single Type you will have a certain number of [REST API endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints) available to interact with.
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/flutter.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/flutter.md
index 1af7bdbfc0..8d710f6186 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/flutter.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/flutter.md
@@ -1,10 +1,13 @@
---
-title: Get started with Flutter - Strapi Developer Documentation
+title: Get started with Flutter - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Flutter.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/flutter.html
---
# Getting Started with Flutter
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Flutter](https://flutter.dev/) remains the same except that you will not fetch the same content.
@@ -51,7 +54,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```dart
Map headers = {
@@ -66,9 +70,9 @@ var response = await http.get(
print(response.body)
```
+:::
-_Response_
-
+::: response Example response
```json
[
{
@@ -102,6 +106,8 @@ _Response_
}
]
```
+:::
+::::
## POST Request your collection type
@@ -111,7 +117,8 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-_Request_
+:::: api-call
+::: request Example POST request
```dart
Map headers = {
@@ -129,8 +136,9 @@ var response = await http.post(
});
);
```
+:::
-_Response_
+::: response Example response
```json
{
@@ -153,6 +161,8 @@ _Response_
]
}
```
+:::
+::::
## PUT Request your collection type
@@ -160,7 +170,8 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example PUT request
```dart
Map headers = {
@@ -176,8 +187,9 @@ var response = await http.put(
});
);
```
+:::
-_Response_
+::: response Example Response
```json
{
@@ -200,7 +212,9 @@ _Response_
]
}
```
+:::
+::::
## Conclusion
-Here is how to request your Collection Types in Strapi using Dart/Flutter. When you create a Collections Type or a Single Type you will have a certain number of [REST API endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints) available to interact with.
+Here is how to request your Collection Types in Strapi using Dart/Flutter. When you create a Collections Type or a Single Type you will have a certain number of [REST API endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints) available to interact with.
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/gatsby.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/gatsby.md
index 915dab2a36..b695ddc938 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/gatsby.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/gatsby.md
@@ -1,10 +1,13 @@
---
-title: Get started with Gatsby - Strapi Developer Documentation
-description: Build powerful applications using Strapi, the leading open-source headless cms and Gatsby.
+title: Get started with Gatsby - Strapi Developer Docs
+description: Build powerful applications using Strapi, the leading open-source headless CMS and Gatsby.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/gatsby.html
---
# Getting Started with Gatsby
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Gatsby](https://www.gatsbyjs.org/) remains the same except that you will not fetch the same content.
@@ -47,7 +50,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+:::request Example GET request
```graphql
query {
@@ -62,8 +66,9 @@ query {
}
}
```
+:::
-_Response_
+:::response Example response
```json
{
@@ -82,6 +87,8 @@ _Response_
}
}
```
+:::
+::::
### Example
@@ -126,7 +133,8 @@ Execute a `GET` request on the `category` Collection Type in order to fetch a sp
Be sure that you activated the `findOne` permission for the `category` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```graphql
query {
@@ -141,7 +149,9 @@ query {
}
```
-_Response_
+:::
+
+::: response Example response
```json
{
@@ -160,6 +170,8 @@ _Response_
"extensions": {}
}
```
+:::
+::::
### Example
@@ -295,4 +307,4 @@ Feel free to do the same for your restaurants!
## Conclusion
Here is how to request your Collection Types in Strapi using Gatsby.
-Learn more about [GraphQL](/developer-docs/latest/development/plugins/graphql.md).
+Learn more about [GraphQL](/developer-docs/latest/plugins/graphql.md).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/go.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/go.md
index cb56b8c11c..71161d25fd 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/go.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/go.md
@@ -1,10 +1,13 @@
---
-title: Get started with Go - Strapi Developer Documentation
+title: Get started with Go - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Go.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/go.html
---
# Getting Started with GO
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start guide, the way you request a Strapi API with [GO](https://golang.org/) remains the same except that you will not fetch the same content.
@@ -18,8 +21,8 @@ Be sure to have [Go installed](https://golang.org/doc/install) on your computer.
touch strapi.go
```
-Go has inbuilt module/package needed to make HTTP Requests like GET, POST PUT, DELETE.
-We will use it("net/http") along with other modules/packages.
+Go has built-in packages to make HTTP Requests like GET, POST, PUT, and DELETE.
+We will use the "net/http" package along with other packages.
## GET Request your collection type
@@ -28,14 +31,15 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-
-_Request_
+:::: api-call
+::: request Example GET request
```go
response, error := http.Get("http://localhost:1337/restaurants")
```
+:::
-_Response_
+::: response Example response
```json
[{
@@ -62,6 +66,8 @@ _Response_
]
}]
```
+:::
+::::
### Example
@@ -96,8 +102,8 @@ Execute a `POST` request on the `restaurant` Collection Type in order to create
Be sure that you activated the `create` permission for the `restaurant` Collection Type and the `find` permission for the `category` Collection type.
-
-_Request_
+:::: api-call
+::: request Example POST request
```go
postRest, _ := json.Marshal(map[string]string{
@@ -107,8 +113,9 @@ postRest, _ := json.Marshal(map[string]string{
responseBody := bytes.NewBuffer(postRest)
resp, error := http.Post("http://localhost:1337/restaurants", "application/json", responseBody)
```
+:::
-_Response_
+::: response Example response
```json
{
@@ -120,6 +127,8 @@ _Response_
"categories": []
}
```
+:::
+::::
### Example
@@ -181,8 +190,8 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `update` permission for the `restaurant` Collection Type.
PUT Request is sligtly different as we need to target the particular thing we want update. We do this by first making a request to http://localhost:1337/restaurants/1 and then update what we want to update. In this example, we are going to update "Biscotte Restaurant" to "Restaurant Home".
-
-_Request_
+:::: api-call
+::: request Example PUT request
```go
putRest, _ := json.Marshal(map[string]string {
@@ -193,8 +202,9 @@ url := "http://localhost:1337/restaurants/1"
req, error := http.NewRequest(http.MethodPut, url, bytes.NewBuffer(putRest))
req.Header.Set("Content-Type", "application/json")
```
+:::
-_Response_
+::: response Example response
```json
{
@@ -221,6 +231,8 @@ _Response_
]
}
```
+:::
+::::
### Example
@@ -306,4 +318,4 @@ func putD() {
Here is how to request your Collection Types in Strapi using Go. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
-We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/content-api/content-api.md#get-an-entry), [get how much entry you have](/developer-docs/latest/developer-resources/content-api/content-api.md#count-entries) and [delete](/developer-docs/latest/developer-resources/content-api/content-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#get-an-entry), and [delete](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/graphql.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/graphql.md
index 5587d87272..14a73e0e7c 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/graphql.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/graphql.md
@@ -1,52 +1,50 @@
---
-title: Get started with GraphQL - Strapi Developer Documentation
+title: Get started with GraphQL - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and GraphQL.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/graphql.html
---
# Getting Started with GraphQL
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [GraphQL](https://graphql.org/) remains the same except that you will not fetch the same content.
## Install the GraphQL plugin
-Install the graphql plugin in your Strapi project.
-
-:::: tabs
-
-::: tab yarn
+Install the GraphQL plugin in your Strapi project.
-```bash
-yarn strapi install graphql
-```
+
-:::
-
-::: tab npm
-
-```bash
+
+```sh
npm run strapi install graphql
```
+
-:::
+
+```sh
+yarn strapi install graphql
+```
+
-::: tab strapi
-```bash
+
+```sh
strapi install graphql
```
+
-:::
-
-::::
+
## Fetch your Restaurant collection type
Play with the [GraphQL Playground](http://localhost:1337/graphql) to fetch your content.
-_Request_
-
+::::api-call
+:::request Example query
```graphql
query Restaurants {
restaurants {
@@ -59,9 +57,9 @@ query Restaurants {
}
}
```
+:::
-_Response_
-
+:::response Example response
```json
{
"data": {
@@ -80,12 +78,14 @@ _Response_
}
}
```
+:::
+::::
### Examples
These examples do not guide you to configure your client with Apollo for your [GraphQL endpoint](http://localhost:1337/graphql). Please follow the associated documentation for each client: ([React](https://www.apollographql.com/docs/react/get-started/) and [Vue.js](https://apollo.vuejs.org/guide/installation.html#_1-apollo-client) here)
-:::: tabs
+:::: tabs card
::: tab React
@@ -170,7 +170,8 @@ export default {
## Fetch your Category collection type
-_Request_
+:::: api-call
+::: request Example request
```graphql
query Category {
@@ -185,8 +186,9 @@ query Category {
}
}
```
+:::
-_Response_
+:::response Example response
```json
{
@@ -205,10 +207,12 @@ _Response_
}
}
```
+:::
+::::
## Examples
-:::: tabs
+:::: tabs card
::: tab React
@@ -313,4 +317,4 @@ export default {
This is how you request your Collection Types in Strapi using GraphQL.
-Feel free to explore more about [GraphQL](/developer-docs/latest/development/plugins/graphql.md).
+Feel free to explore more about [GraphQL](/developer-docs/latest/plugins/graphql.md).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/gridsome.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/gridsome.md
index e2adee7461..aeae545cb6 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/gridsome.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/gridsome.md
@@ -1,10 +1,13 @@
---
-title: Get started with Gridsome - Strapi Developer Documentation
+title: Get started with Gridsome - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Gridsome.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/gridsome.html
---
# Getting Started with Gridsome
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Gridsome](https://gridsome.org/) remains the same except that you will not fetch the same content.
@@ -49,7 +52,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```graphql
query {
@@ -64,9 +68,9 @@ query {
}
}
```
+:::
-_Response_
-
+:::response Example response
```json
{
"data": {
@@ -85,12 +89,14 @@ _Response_
}
}
```
+:::
+::::
### Example
`./src/pages/Index.vue`
-```js
+```jsx
@@ -128,8 +134,8 @@ Execute a `GET` request on the `category` Collection Type in order to fetch a sp
Be sure that you activated the `findOne` permission for the `category` Collection Type.
-_Request_
-
+:::: api-call
+::: request Example GET request
```graphql
query {
strapiCategory(id: 1) {
@@ -142,8 +148,9 @@ query {
}
}
```
+:::
-_Response_
+:::response Example response
```json
{
@@ -162,12 +169,15 @@ _Response_
"extensions": {}
}
```
+:::
+
+::::
### Example
`./src/pages/Index.vue`
-```js
+```jsx
{{ $page.strapiCategory.name }}
@@ -257,7 +267,7 @@ You can find your restaurant categories by browsing `http://localhost:8080/categ
Feel free to do the same for your restaurants!
-## Starter
+## Starters
- [Gridsome Blog starter](https://github.com/strapi/strapi-starter-gridsome-blog)
- [Gridsome Portfolio starter](https://github.com/strapi/strapi-starter-gridsome-portfolio)
@@ -266,4 +276,4 @@ Feel free to do the same for your restaurants!
Here is how to request your Collection Types in Strapi using Gridsome.
-Learn more about [GraphQL](/developer-docs/latest/development/plugins/graphql.md)
+Learn more about [GraphQL](/developer-docs/latest/plugins/graphql.md)
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/jekyll.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/jekyll.md
index fdf464c649..2425182c60 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/jekyll.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/jekyll.md
@@ -1,10 +1,13 @@
---
-title: Get started with Jekyll - Strapi Developer Documentation
+title: Get started with Jekyll - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Jekyll.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/jekyll.html
---
# Getting Started with Jekyll
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Jekyll](https://jekyllrb.com) remains the same except that you will not fetch the same content.
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/laravel.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/laravel.md
index ef1afd7de2..2a3ee734d4 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/laravel.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/laravel.md
@@ -1,10 +1,13 @@
---
-title: Get started with Laravel - Strapi Developer Documentation
+title: Get started with Laravel - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Laravel.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/laravel.html
---
# Getting Started with Laravel
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
Should you wish to use standalone PHP, you may also be interested in the [PHP integration guide](/developer-docs/latest/developer-resources/content-api/integrations/php.md).
@@ -19,6 +22,12 @@ composer require dbfx/laravel-strapi
This will install [Laravel-Strapi](https://github.com/dbfx/laravel-strapi), a Laravel specific package for interacting with Strapi.
+You will need to publish a config file:
+
+```bash
+php artisan vendor:publish --provider="Dbfx\LaravelStrapi\LaravelStrapiServiceProvider" --tag="strapi-config"
+```
+
You will also need to define your `STRAPI_URL` and `STRAPI_CACHE_TIME` in the `.env` file:
``` json
@@ -32,12 +41,13 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+::: request Example GET request
```php
$strapi = new Dbfx\LaravelStrapi();
$restaurants = $strapi->collection('restaurants');
```
+:::
You may now iterate over the $restaurants array which will contain all your restaurants. More options are available as well:
@@ -76,6 +86,6 @@ $entry = $strapi->entry('restaurants', $id = 5);
## Conclusion
-Here is how to request your Collection Types in Strapi using PHP. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
+Here is how to request your Collection Types in Strapi using Laravel. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
-There is more documentation available in the [README](https://github.com/dbfx/laravel-strapi) or in the [PHP integration guide](/developer-docs/latest/developer-resources/content-api/integrations/php.html).
+There is more documentation available in the [README](https://github.com/dbfx/laravel-strapi) or in the [PHP integration guide](/developer-docs/latest/developer-resources/content-api/integrations/php.md).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/next-js.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/next-js.md
index df27dde5b0..39da8dec14 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/next-js.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/next-js.md
@@ -1,10 +1,13 @@
---
-title: Get started with Next.js - Strapi Developer Documentation
+title: Get started with Next.js - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Next.js.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/next-js.html
---
# Getting Started with Next.js
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Next.js](https://nextjs.org/) remains the same except that you will not fetch the same content.
@@ -13,31 +16,27 @@ If you haven't gone through the Quick Start Guide, the way you request a Strapi
Create a basic Next.js application.
-:::: tabs
-
-::: tab yarn
-
-```bash
-yarn create next-app nextjs-app
-```
+
-:::
-
-::: tab npx
-
-```bash
+
+```sh
npx create-next-app nextjs-app
```
+
-:::
+
+```sh
+yarn create next-app nextjs-app
+```
+
-::::
+
## Use an HTTP client
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab axios
@@ -61,12 +60,10 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-:::: tabs
-
-::: tab axios
-
-_Request_
+::::: tabs card
+:::: tab axios
+::: request Example GET request with axios
```js
import axios from 'axios';
@@ -74,12 +71,12 @@ axios.get('http://localhost:1337/restaurants').then(response => {
console.log(response);
});
```
-
:::
-::: tab fetch
+::::
-_Request_
+:::: tab fetch
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
@@ -93,9 +90,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
[
{
@@ -134,7 +132,7 @@ _Response_
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -235,11 +233,10 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
-
-::: tab axios
+::::: tabs card
-_Request_
+:::: tab axios
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -256,11 +253,10 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
-
+:::: tab fetch
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'POST',
@@ -278,9 +274,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -302,12 +299,12 @@ _Response_
]
}
```
+:::
-::::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -563,14 +560,13 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
We consider that the id of your restaurant is `2`.
and the id of your category is `2`.
-::: tab axios
-
-_Request_
+:::: tab axios
+::: request Example PUT request with axios
```js
import axios from 'axios';
@@ -585,11 +581,10 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
-
+:::: tab fetch
+::: request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
method: 'PUT',
@@ -607,8 +602,10 @@ fetch('http://localhost:1337/restaurants/2', {
```
:::
+::::
+:::::
-_Response_
+:::response Example response
```json
{
@@ -631,8 +628,8 @@ _Response_
]
}
```
+:::
-::::
## Starter
@@ -643,4 +640,4 @@ _Response_
Here is how to request your Collection Types in Strapi using Next.js. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
-We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/content-api/content-api.md#get-an-entry), [get how much entry you have](/developer-docs/latest/developer-resources/content-api/content-api.md#count-entries) and [delete](/developer-docs/latest/developer-resources/content-api/content-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#get-an-entry), and [delete](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/nuxt-js.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/nuxt-js.md
index 2865dec7c3..33afacfc16 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/nuxt-js.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/nuxt-js.md
@@ -1,10 +1,13 @@
---
-title: Get started with Nuxt.js - Strapi Developer Documentation
+title: Get started with Nuxt.js - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Nuxt.js.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/nuxt-js.html
---
# Getting Started with Nuxt.js
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Nuxt.js](https://nuxtjs.org/) remains the same except that you will not fetch the same content.
@@ -13,31 +16,27 @@ If you haven't gone through the Quick Start Guide, the way you request a Strapi
Create a basic Nuxt.js application with [create-nuxt-app](https://github.com/nuxt/create-nuxt-app).
-:::: tabs
-
-::: tab yarn
+
-```bash
-yarn create nuxt-app nuxtjs-app
-```
-
-:::
-
-::: tab npx
-
-```bash
+
+```sh
npx create-nuxt-app nuxtjs-app
```
+
-:::
+
+```sh
+yarn create nuxt-app nuxtjs-app
+```
+
-::::
+
## Use an HTTP client
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab @nuxtjs/strapi
@@ -81,12 +80,11 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-:::: tabs
-
-::: tab @nuxtjs/strapi
+::::: tabs card
-_Request_
+:::: tab @nuxtjs/strapi
+::: request Example GET request with @nuxtjs/strapi
```js
try {
await this.$strapi.find('restaurants');
@@ -94,13 +92,13 @@ try {
console.error(error);
}
```
-
:::
-::: tab axios
+::::
-_Request_
+:::: tab axios
+::: request Example GET request with axios
```js
import axios from 'axios';
@@ -108,13 +106,13 @@ axios.get('http://localhost:1337/restaurants').then(response => {
console.log(response);
});
```
-
:::
-::: tab fetch
+::::
-_Request_
+:::: tab fetch
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'GET',
@@ -127,9 +125,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
[
{
@@ -163,12 +162,12 @@ _Response_
}
]
```
+:::
-::::
### Example
-:::: tabs
+:::: tabs card
::: tab @nuxt/strapi
@@ -323,9 +322,10 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
+::::: tabs card
-::: tab @nuxtjs/strapi
+:::: tab @nuxtjs/strapi
+::: request Example POST request with @nuxtjs/strapi
```js
try {
@@ -340,11 +340,11 @@ try {
```
:::
+::::
-::: tab axios
-
-_Request_
+:::: tab axios
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -360,11 +360,10 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
-
+:::: tab fetch
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'POST',
@@ -382,9 +381,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -406,12 +406,12 @@ _Response_
]
}
```
+:::
-::::
### Example
-:::: tabs
+:::: tabs card
::: tab @nuxtjs/strapi
@@ -687,12 +687,13 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
We consider that the id of your restaurant is `2`.
and the id of your category is `2`.
-::: tab @nuxtjs/strapi
+:::: tab @nuxtjs/strapi
+::: request Example PUT request with @nuxtjs/strapi
```js
try {
@@ -705,11 +706,10 @@ try {
```
:::
+::::
-::: tab axios
-
-_Request_
-
+:::: tab axios
+::: request Example PUT request with axios
```js
import axios from 'axios';
@@ -721,13 +721,12 @@ axios
console.log(response);
});
```
-
:::
-::: tab fetch
-
-_Request_
+::::
+:::: tab fetch
+::: request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
method: 'PUT',
@@ -745,9 +744,10 @@ fetch('http://localhost:1337/restaurants/2', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -769,10 +769,9 @@ _Response_
]
}
```
+:::
-::::
-
-## Starter
+## Starters
- [Nuxt.js Blog starter](https://github.com/strapi/strapi-starter-nuxt-blog).
- [Nuxt.js E-commerce starter](https://github.com/strapi/strapi-starter-nuxt-e-commerce).
@@ -781,4 +780,4 @@ _Response_
Here is how to request your Collection Types in Strapi using Nuxt.js. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
-We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/content-api/content-api.md#get-an-entry), [get how much entry you have](/developer-docs/latest/developer-resources/content-api/content-api.md#count-entries) and [delete](/developer-docs/latest/developer-resources/content-api/content-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#get-an-entry), and [delete](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/php.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/php.md
index e4fe387a0a..64890ee0a6 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/php.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/php.md
@@ -1,10 +1,13 @@
---
-title: Get started with PHP - Strapi Developer Documentation
+title: Get started with PHP - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and PHP.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/php.html
---
# Getting Started with PHP
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [PHP](https://php.net/) remains the same except that you will not fetch the same content.
@@ -24,7 +27,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```php
curl_setopt($curl, CURLOPT_URL, 'http://localhost:1337/restaurants');
@@ -32,8 +36,8 @@ curl_setopt($curl, CURLOPT_URL, 'http://localhost:1337/restaurants');
Running the PHP file on the browser will give you this response:
-
-_Response_
+:::
+::: response Example response
```json
[{
@@ -60,6 +64,8 @@ _Response_
]
}]
```
+:::
+::::
### Example
```php
@@ -87,7 +93,8 @@ Execute a `POST` request on the `restaurant` Collection Type in order to create
Be sure that you activated the `create` permission for the `restaurant` Collection Type and the `find` permission for the `category` Collection type.
-_Request_
+:::: api-call
+::: request Example POST request
```php
$restaurants = array(
@@ -109,7 +116,8 @@ curl_setopt($curl, CURLOPT_POST, true);
Running the PHP file on the browser will give you this response:
-_Response_
+:::
+::: response Example response
```json
[{
@@ -129,6 +137,8 @@ _Response_
]
}]
```
+:::
+::::
### Example
@@ -187,7 +197,8 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `update` permission for the `restaurant` Collection Type.
PUT Request is sligtly different as we need to target the particular entry we want update. We do this by first making a request to http://localhost:1337/restaurants/1 and then update what we want to update. In this example, we are going to update "Biscotte Restaurant" to "Femoni Kitchen".
-_Request_
+:::: api-call
+::: request Example PUT request
```php
$restaurants = array(
@@ -200,11 +211,11 @@ curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_CUSTOMREQUEST, 'PUT');
```
+:::
+::: response Example response
Running the PHP file on the browser will give you this response:
-_Response_
-
```json
[{
"id": 1,
@@ -223,6 +234,8 @@ _Response_
]
}]
```
+:::
+::::
### Example
@@ -293,9 +306,9 @@ putRestaurant();
```
-Running an authentication request (getting JWT)
+Running an authentication request (getting JWT):
-_Response_
+::: response
```json
@@ -323,6 +336,7 @@ _Response_
}
}]
```
+:::
### Example
```php
@@ -367,7 +381,7 @@ print_r($strapi_res);
Running an authenticated POST request with JWT
-_Response_
+::: response Example response
```json
[{
"id": 2,
@@ -386,6 +400,8 @@ _Response_
]
}]
```
+:::
+
### Example
```php
-:::
-
-::: tab npx
-
-```bash
+
+```sh
npx create-react-app react-app
```
+
-:::
+
+```sh
+yarn create react-app react-app
+```
+
-::::
+
## Use an HTTP client
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab axios
@@ -61,12 +61,11 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type
-:::: tabs
+::::: tabs card
-::: tab axios
-
-_Request_
+:::: tab axios
+::: request Example GET request with axios
```js
import axios from 'axios';
@@ -74,13 +73,13 @@ axios.get('http://localhost:1337/restaurants').then(response => {
console.log(response);
});
```
-
:::
-::: tab fetch
+::::
-_Request_
+:::: tab fetch
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'GET',
@@ -91,10 +90,11 @@ fetch('http://localhost:1337/restaurants', {
.then(response => response.json())
.then(data => console.log(data));
```
-
:::
-_Response_
+::::
+
+:::response Example response
```json
[
@@ -129,12 +129,12 @@ _Response_
}
]
```
+:::
-::::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -266,12 +266,11 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
-
-::: tab axios
+::::: tabs card
-_Request_
+:::: tab axios
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -285,13 +284,13 @@ axios
console.log(response);
});
```
-
:::
-::: tab fetch
+::::
-_Request_
+:::: tab fetch
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'POST',
@@ -307,11 +306,12 @@ fetch('http://localhost:1337/restaurants', {
.then(response => response.json())
.then(data => console.log(data));
```
-
:::
-_Response_
+::::
+:::::
+::: response Example response
```json
{
"id": 2,
@@ -333,12 +333,11 @@ _Response_
]
}
```
-
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -649,14 +648,13 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
-We consider that the id of your restaurant is `2`.
-and the id of your category is `2`.
+We consider that the id of your restaurant is `2`, and the id of your category is `2`.
-::: tab axios
+:::: tab axios
-_Request_
+::: request Example PUT request with axios
```js
import axios from 'axios';
@@ -671,11 +669,11 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
+:::: tab fetch
+::: request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
method: 'PUT',
@@ -691,11 +689,11 @@ fetch('http://localhost:1337/restaurants/2', {
console.log(data);
});
```
-
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -717,8 +715,8 @@ _Response_
]
}
```
+:::
-::::
## Starter
@@ -728,4 +726,4 @@ _Response_
Here is how to request your Collection Types in Strapi using React. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
-We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/content-api/content-api.md#get-an-entry), [get how much entry you have](/developer-docs/latest/developer-resources/content-api/content-api.md#count-entries) and [delete](/developer-docs/latest/developer-resources/content-api/content-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#get-an-entry), and [delete](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/ruby.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/ruby.md
index 56c25b3ce2..e0e3f65df9 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/ruby.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/ruby.md
@@ -1,10 +1,13 @@
---
-title: Get started with Ruby - Strapi Developer Documentation
+title: Get started with Ruby - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Ruby.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/ruby.html
---
# Getting Started with Ruby
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Ruby](https://www.ruby-lang.org/en/) remains the same except that you will not fetch the same content.
@@ -42,7 +45,8 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example GET request
```ruby
HTTParty.get('http://localhost:1337/restaurants',
@@ -51,7 +55,9 @@ HTTParty.get('http://localhost:1337/restaurants',
})
```
-_Response_
+:::
+
+::: response Example response
```json
[
@@ -86,6 +92,8 @@ _Response_
}
]
```
+:::
+::::
### Example
@@ -117,7 +125,8 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-_Request_
+:::: api-call
+::: request Example POST request
```ruby
HTTParty.post("http://localhost:1337/restaurants",
@@ -132,7 +141,9 @@ HTTParty.post("http://localhost:1337/restaurants",
)
```
-_Response_
+:::
+
+::: response Example response
```json
{
@@ -155,6 +166,8 @@ _Response_
]
}
```
+:::
+::::
### Example
@@ -201,7 +214,8 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-_Request_
+:::: api-call
+::: request Example PUT request
```ruby
HTTParty.put("http://localhost:1337/restaurants/2",
@@ -214,7 +228,9 @@ HTTParty.put("http://localhost:1337/restaurants/2",
)
```
-_Response_
+:::
+
+::: response Example response
```json
{
@@ -237,6 +253,8 @@ _Response_
]
}
```
+:::
+::::
### Example
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/sapper.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/sapper.md
index 59c28561ff..37dfc11601 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/sapper.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/sapper.md
@@ -1,10 +1,13 @@
---
-title: Get started with Sapper - Strapi Developer Documentation
+title: Get started with Sapper - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Sapper.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/sapper.html
---
# Getting Started with Sapper
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Sapper](https://sapper.svelte.dev) remains the same except that you will not fetch the same content.
@@ -25,7 +28,7 @@ npx degit "sveltejs/sapper-template#webpack" sapper-app
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab axios
@@ -49,11 +52,11 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type
-:::: tabs
+::::: tabs card
-::: tab axios
+:::: tab axios
-_Request_
+::: request Example GET request with axios
```js
import axios from 'axios';
@@ -62,12 +65,13 @@ axios.get('http://localhost:1337/restaurants').then(response => {
console.log(response);
});
```
-
:::
-::: tab fetch
+::::
+
+:::: tab fetch
-_Request_
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
@@ -79,10 +83,12 @@ fetch('http://localhost:1337/restaurants', {
.then(response => response.json())
.then(data => console.log(data));
```
-
:::
-_Response_
+::::
+:::::
+
+::: response Example response
```json
[
@@ -117,12 +123,12 @@ _Response_
}
]
```
+:::
-::::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -227,12 +233,11 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
+::::: tabs card
-::: tab axios
-
-_Request_
+:::: tab axios
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -246,12 +251,12 @@ axios
console.log(response);
});
```
-
:::
+::::
-::: tab fetch
+:::: tab fetch
-_Request_
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
@@ -268,10 +273,12 @@ fetch('http://localhost:1337/restaurants', {
.then(response => response.json())
.then(data => console.log(data));
```
-
:::
-_Response_
+::::
+:::::
+
+::: response Example response
```json
{
@@ -295,11 +302,11 @@ _Response_
}
```
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -461,14 +468,14 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
We consider that the id of your restaurant is `2`.
and the id of your category is `2`.
-::: tab axios
+:::: tab axios
-_Request_
+::: request Example PUT request with axios
```js
import axios from 'axios';
@@ -483,10 +490,11 @@ axios
```
:::
+::::
-::: tab fetch
+:::: tab fetch
-_Request_
+::: request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
@@ -505,8 +513,10 @@ fetch('http://localhost:1337/restaurants/2', {
```
:::
+::::
+:::::
-_Response_
+::: response Example response
```json
{
@@ -530,7 +540,7 @@ _Response_
}
```
-::::
+:::
## Conclusion
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/svelte.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/svelte.md
index 73de09b030..ab7ad6f433 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/svelte.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/svelte.md
@@ -1,10 +1,13 @@
---
-title: Get started with Svelte - Strapi Developer Documentation
+title: Get started with Svelte - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Svelte.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/svelte.html
---
# Getting Started with Svelte
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Svelte](https://svelte.dev) remains the same except that you will not fetch the same content.
@@ -25,7 +28,7 @@ npx degit sveltejs/template svelte-app
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab axios
@@ -49,11 +52,11 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-:::: tabs
+:::::: tabs card
-::: tab axios
+::::: tab axios
-_Request_
+:::request Example GET request with axios
```js
import axios from 'axios';
@@ -62,12 +65,13 @@ axios.get('http://localhost:1337/restaurants').then(response => {
console.log(response);
});
```
-
:::
-::: tab fetch
+:::::
+
+::::: tab fetch
-_Request_
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
@@ -81,8 +85,9 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+:::::
-_Response_
+::: response Example response
```json
[
@@ -117,12 +122,11 @@ _Response_
}
]
```
-
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -227,11 +231,11 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
+:::::: tabs card
-::: tab axios
+::::: tab axios
-_Request_
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -248,10 +252,11 @@ axios
```
:::
+:::::
-::: tab fetch
+::::: tab fetch
-_Request_
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
@@ -270,8 +275,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+:::::
+::::::
-_Response_
+::: response Example response
```json
{
@@ -295,11 +302,11 @@ _Response_
}
```
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -461,14 +468,14 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
We consider that the id of your restaurant is `2`.
and the id of your category is `2`.
-::: tab axios
+:::: tab axios
-_Request_
+::: request Example PUT request with axios
```js
import axios from 'axios';
@@ -483,10 +490,11 @@ axios
```
:::
+::::
-::: tab fetch
+:::: tab fetch
-_Request_
+::: request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
@@ -505,8 +513,10 @@ fetch('http://localhost:1337/restaurants/2', {
```
:::
+::::
+:::::
-_Response_
+::: response Example response
```json
{
@@ -530,7 +540,7 @@ _Response_
}
```
-::::
+:::
## Conclusion
diff --git a/docs/developer-docs/latest/developer-resources/content-api/integrations/vue-js.md b/docs/developer-docs/latest/developer-resources/content-api/integrations/vue-js.md
index 04f835ebf9..10b811caef 100644
--- a/docs/developer-docs/latest/developer-resources/content-api/integrations/vue-js.md
+++ b/docs/developer-docs/latest/developer-resources/content-api/integrations/vue-js.md
@@ -1,10 +1,13 @@
---
-title: Get started with Vue.js - Strapi Developer Documentation
+title: Get started with Vue.js - Strapi Developer Docs
description: Build powerful applications using Strapi, the leading open-source headless cms and Vue.js.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/content-api/integrations/vue-js.html
---
# Getting Started with Vue.js
+!!!include(developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md)!!!
+
This integration guide is following the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md). We assume that you have fully completed its "Hands-on" path, and therefore can consume the API by browsing this [url](http://localhost:1337/restaurants).
If you haven't gone through the Quick Start Guide, the way you request a Strapi API with [Vue.js](https://vuejs.org/) remains the same except that you will not fetch the same content.
@@ -21,7 +24,7 @@ vue create vue-app
Many HTTP clients are available but in this documentation we'll use [Axios](https://github.com/axios/axios) and [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-:::: tabs
+:::: tabs card
::: tab axios
@@ -45,12 +48,11 @@ Execute a `GET` request on the `restaurant` Collection Type in order to fetch al
Be sure that you activated the `find` permission for the `restaurant` Collection Type.
-:::: tabs
-
-::: tab axios
+::::: tabs card
-_Request_
+:::: tab axios
+::: request Example GET request with axios
```js
import axios from 'axios';
@@ -58,12 +60,13 @@ axios.get('http://localhost:1337/restaurants').then(response => {
console.log(response);
});
```
-
:::
-::: tab fetch
+::::
-_Request_
+:::: tab fetch
+
+::: request Example GET request with fetch
```js
fetch('http://localhost:1337/restaurants', {
@@ -77,9 +80,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
[
{
@@ -113,12 +117,11 @@ _Response_
}
]
```
-
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -222,9 +225,9 @@ export default {
```
:::
-
::::
+
## POST Request your collection type
Execute a `POST` request on the `restaurant` Collection Type in order to create a restaurant.
@@ -233,11 +236,11 @@ Be sure that you activated the `create` permission for the `restaurant` Collecti
In this example a `japanese` category has been created which has the id: 3.
-:::: tabs
+::::: tabs card
-::: tab axios
+:::: tab axios
-_Request_
+::: request Example POST request with axios
```js
import axios from 'axios';
@@ -254,11 +257,11 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
+:::: tab fetch
+::: request Example POST request with fetch
```js
fetch('http://localhost:1337/restaurants', {
method: 'POST',
@@ -276,9 +279,10 @@ fetch('http://localhost:1337/restaurants', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -300,12 +304,11 @@ _Response_
]
}
```
-
-::::
+:::
### Example
-:::: tabs
+:::: tabs card
::: tab axios
@@ -500,14 +503,14 @@ Execute a `PUT` request on the `restaurant` Collection Type in order to update t
Be sure that you activated the `put` permission for the `restaurant` Collection Type.
-:::: tabs
+::::: tabs card
We consider that the id of your restaurant is `2`.
and the id of your category is `2`.
-::: tab axios
+:::: tab axios
-_Request_
+:::request Example PUT request with axios
```js
import axios from 'axios';
@@ -522,10 +525,10 @@ axios
```
:::
+::::
-::: tab fetch
-
-_Request_
+:::: tab fetch
+:::request Example PUT request with fetch
```js
fetch('http://localhost:1337/restaurants/2', {
@@ -544,9 +547,10 @@ fetch('http://localhost:1337/restaurants/2', {
```
:::
+::::
+:::::
-_Response_
-
+:::response Example response
```json
{
"id": 2,
@@ -568,8 +572,7 @@ _Response_
]
}
```
-
-::::
+:::
## Starter
@@ -579,4 +582,4 @@ _Response_
Here is how to request your Collection Types in Strapi using Vue.js. When you create a Collection Type or a Single Type you will have a certain number of REST API endpoints available to interact with.
-We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/content-api/content-api.md#get-an-entry), [get how much entry you have](/developer-docs/latest/developer-resources/content-api/content-api.md#count-entries) and [delete](/developer-docs/latest/developer-resources/content-api/content-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+We just used the GET, POST and PUT methods here but you can [get one entry](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#get-an-entry), and [delete](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#delete-an-entry) an entry too. Learn more about [API Endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
diff --git a/docs/developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md b/docs/developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md
new file mode 100644
index 0000000000..51659b8bb0
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/content-api/snippets/integration-guide-not-updated.md
@@ -0,0 +1,3 @@
+::: caution
+This third-party integration guide might not be up-to-date with Strapi v4. [Contributions](https://github.com/strapi/documentation/blob/main/CONTRIBUTING.md) are most welcome.
+:::
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md
new file mode 100644
index 0000000000..ab84ec8aec
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md
@@ -0,0 +1,26 @@
+---
+title: Entity Service API - Strapi Developer Docs
+description: The Entity Service is the layer that handles Strapi's complex data structures like components and dynamic zones, and uses the Query Engine API under the hood to execute database queries.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.html
+---
+
+# Entity Service API
+
+Strapi provides an Entity Service API, built on top of the [Query Engine API](/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.md). The Entity Service is the layer that handles Strapi's complex data structures like [components](/developer-docs/latest/development/backend-customization/models.md#components-2) and [dynamic zones](/developer-docs/latest/development/backend-customization/models.md#dynamic-zones), and uses the Query Engine API under the hood to execute database queries.
+
+## Basic usage
+
+The Entity Service is available through `strapi.entityService`:
+
+```js
+const entry = await strapi.entityService.findOne('api::article.article', 1, {
+ populate: { someRelation: true },
+});
+```
+
+## Available operations
+
+The Entity Service API allows:
+
+- [CRUD operations on entities](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.md) (e.g. `findOne`, `findMany`, `create`, `update`, `delete`) with the ability to [filter](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md), [order and paginate results](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md), and [populate relations, components and dynamic zones](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md)
+- the [creation and update of components and dynamic zones](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/components-dynamic-zones.md)
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/components-dynamic-zones.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/components-dynamic-zones.md
new file mode 100644
index 0000000000..0fb30dd8a8
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/components-dynamic-zones.md
@@ -0,0 +1,79 @@
+---
+title: Components and Dynamic Zones with Entity Service API - Strapi Developer Docs
+description: Use Strapi's Entity Service to create and update components and dynamic zones.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/entity-service/components-dynamic-zones.html
+---
+
+# Entity Service API: Components and dynamic zones
+
+The [Entity Service](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) is the layer that handles [components](/developer-docs/latest/development/backend-customization/models.md#components-2) and [dynamic zones](/developer-docs/latest/development/backend-customization/models.md#dynamic-zones) logic. With the Entity Service API, components and dynamic zones can be [created](#creation) and [updated](#update) while creating or updating entries.
+
+## Creation
+
+A [component](/developer-docs/latest/development/backend-customization/models.md#components-2) can be created while creating an entry with the Entity Service API:
+
+```js
+strapi.entityService.create('api::article.article', {
+ data: {
+ myComponent: {
+ foo: 'bar',
+ },
+ },
+});
+```
+
+A [dynamic zone](/developer-docs/latest/development/backend-customization/models.md#dynamic-zones) (i.e. a list of components) can be created while creating an entry with the Entity Service API:
+
+```js
+strapi.entityService.create('api::article.article', {
+ data: {
+ myDynamicZone: [
+ {
+ __component: 'compo.type',
+ foo: 'bar',
+ },
+ {
+ __component: 'compo.type2',
+ foo: 'bar',
+ },
+ ],
+ },
+});
+```
+
+## Update
+
+A [component](/developer-docs/latest/development/backend-customization/models.md#components-2) can be updated while updating an entry with the Entity Service API. If a component `id` is specified, the component is updated, otherwise the old one is deleted and a new one is created:
+
+```js
+strapi.entityService.update('api::article.article', 1, {
+ data: {
+ myComponent: {
+ id: 1, // will update component with id: 1 (if not specified, would have deleted it and created a new one)
+ foo: 'bar',
+ },
+ },
+});
+```
+
+A [dynamic zone](/developer-docs/latest/development/backend-customization/models.md#dynamic-zones) (i.e. a list of components) can be updated while updating an entry with the Entity Service API. If a component `id` is specified, the component is updated, otherwise the old one is deleted and a new one is created:
+
+```js
+strapi.entityService.update('api::article.article', 1, {
+ data: {
+ myDynamicZone: [
+ {
+ // will update
+ id: 2,
+ __component: 'compo.type',
+ foo: 'bar',
+ },
+ {
+ // will add a new & delete old ones
+ __component: 'compo.type2',
+ foo: 'bar2',
+ },
+ ],
+ },
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.md
new file mode 100644
index 0000000000..61dead7b9d
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.md
@@ -0,0 +1,131 @@
+---
+title: CRUD operations with Entity Service API - Strapi Developer Docs
+description: Use Strapi's Entity Service API to perform CRUD (create, read, update, delete) operations on your content.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.html
+---
+
+# Entity Service API: CRUD operations
+
+The [Entity Service API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) is built on top of the the [Query Engine API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) and uses it to perform CRUD operations on entities.
+
+## findOne()
+
+Finds the first entry matching the parameters.
+
+Syntax: `findOne(uid: string, id: ID, parameters: Params)` ⇒ `Entry`
+
+### Parameters
+
+| Parameter | Description | Type |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `fields` | Attributes to return | `String[]` |
+| `populate` | Relations, components and dynamic zones to [populate](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) |
+
+### Example
+
+```js
+const entry = await strapi.entityService.findOne('api:article.article', 1, {
+ fields: ['title', 'description'],
+ populate: { category: true },
+});
+```
+
+## findMany()
+
+Finds entries matching the parameters.
+
+Syntax: `findMany(uid: string, parameters: Params)` ⇒ `Entry[]`
+
+### Parameters
+
+| Parameter | Description | Type |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `fields` | Attributes to return | `String[]` |
+| `filters` | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md) to use | [`FiltersParameters`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md) |
+| `start` | Number of entries to skip (see [pagination](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md#pagination)) | `Number` |
+| `limit` | Number of entries to return (see [pagination](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md#pagination)) | `Number` |
+| `sort` | [Order](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md) definition | [`OrderByParameter`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md) |
+| `populate` | Relations, components and dynamic zones to [populate](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) |
+| `publicationState` | Publication state, can be:- `live` to return only published entries (default)
- `preview` to return both draft entries & published entries
| `PublicationStateParameter` |
+
+### Example
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ fields: ['title', 'description'],
+ filters { title: 'Hello World' },
+ sort: { createdAt: 'DESC' },
+ populate: { category: true },
+});
+```
+
+## create()
+
+Creates one entry and returns it
+
+Syntax: `create(uid: string, parameters: Params)` ⇒ `Entry`
+
+### Parameters
+
+| Parameter | Description | Type |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `fields` | Attributes to return | `String[]` |
+| `populate` | Relations, components and dynamic zones to [populate](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) |
+| `data` | Input data | `Object` |
+
+### Example
+
+```js
+const entry = await strapi.entityService.create('api::article.article', {
+ data: {
+ title: 'My Article',
+ },
+});
+```
+
+## update()
+
+Updates one entry and returns it.
+
+:::note
+`update()` only performs a partial update, so existing fields that are not included won't be replaced.
+:::
+
+Syntax: `update(uid: string, id: ID, parameters: Params)` ⇒ `Entry`
+
+### Parameters
+
+| Parameter | Description | Type |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `fields` | Attributes to return | `String[]` |
+| `populate` | Relations, components and dynamic zones to [populate](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) |
+| `data` | Input data | `object` |
+
+### Example
+
+```js
+const entry = await strapi.entityService.update('api::article.article', 1, {
+ data: {
+ title: 'xxx',
+ },
+});
+```
+
+## delete()
+
+Deletes one entry and returns it.
+
+Syntax: `delete(uid: string, id: ID, parameters: Params)` ⇒ `Entry`
+
+### Parameters
+
+| Parameter | Description | Type |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `fields` | Attributes to return | `String[]` |
+| `populate` | Relations, components and dynamic zones to [populate](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md) |
+
+### Example
+
+```js
+const entry = await strapi.entityService.delete('api::article.article', 1);
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md
new file mode 100644
index 0000000000..dd597a1ff6
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md
@@ -0,0 +1,407 @@
+---
+title: Filtering with Entity Service API - Strapi Developer Docs
+description: Use Strapi's Entity Service API to filter your queries results.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.html
+---
+
+# Entity Service API: Filtering
+
+The [Entity Service API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) offers the ability to filter results found with its [findMany()](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.md#findmany) method.
+
+Results are filtered with the `filters` parameter that accepts [logical operators](#logical-operators) and [attribute operators](#attribute-operators). Every operator should be prefixed with `$`.
+
+## Logical operators
+
+### `$and`
+
+All nested conditions must be true.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ $and: [
+ {
+ title: 'Hello World',
+ },
+ {
+ createdAt: { $gt: '2021-11-17T14:28:25.843Z' },
+ },
+ ],
+ },
+});
+```
+
+`$and` will be used implicitly when passing an object with nested conditions:
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: 'Hello World',
+ rating: 12,
+ },
+});
+```
+
+### `$or`
+
+One or many nested conditions must be `true`.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ $or: [
+ {
+ title: 'Hello World',
+ },
+ {
+ title: {
+ $contains: 'Hello',
+ },
+ },
+ ],
+ },
+});
+```
+
+### `$not`
+
+Negates the nested conditions.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ $not: {
+ title: 'Hello World',
+ },
+ },
+});
+```
+
+:::note
+`$not` can be used:
+
+- as a logical operator (e.g. in `filters: { $not: { // conditions… }}`)
+- or [as an attribute operator](#not-2) (e.g. in `filters: { attribute-name: $not: { … } }`).
+ :::
+
+:::tip
+`$and`, `$or` and `$not` operators are nestable inside of another `$and`, `$or` or `$not` operator.
+:::
+## Attribute Operators
+
+### `$not`
+
+Negates the nested condition(s).
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $not: {
+ $contains: 'Hello World',
+ },
+ },
+ },
+});
+```
+
+### `$eq`
+
+Attribute equals input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $eq: 'Hello World',
+ },
+ },
+});
+```
+
+`$eq` can be omitted:
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: 'Hello World',
+ },
+});
+```
+
+### `$ne`
+
+Attribute does not equal input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $ne: 'ABCD',
+ },
+ },
+});
+```
+
+### `$in`
+
+Attribute is contained in the input list.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $in: ['Hello', 'Hola', 'Bonjour'],
+ },
+ },
+});
+```
+
+`$in` can be ommited when passing an array of values:
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: ['Hello', 'Hola', 'Bonjour'],
+ },
+});
+```
+
+### `$notIn`
+
+Attribute is not contained in the input list.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $notIn: ['Hello', 'Hola', 'Bonjour'],
+ },
+ },
+});
+```
+
+### `$lt`
+
+Attribute is less than the input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ rating: {
+ $lt: 10,
+ },
+ },
+});
+```
+
+### `$lte`
+
+Attribute is less than or equal to the input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ rating: {
+ $lte: 10,
+ },
+ },
+});
+```
+
+### `$gt`
+
+Attribute is greater than the input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ rating: {
+ $gt: 5,
+ },
+ },
+});
+```
+
+### `$gte`
+
+Attribute is greater than or equal to the input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ rating: {
+ $gte: 5,
+ },
+ },
+});
+```
+
+### `$between`
+
+Attribute is between the 2 input values.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ rating: {
+ $between: [1, 20],
+ },
+ },
+});
+```
+
+### `$contains`
+
+Attribute contains the input value (case-sensitive).
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $contains: 'Hello',
+ },
+ },
+});
+```
+
+### `$notContains`
+
+Attribute does not contain the input value (case-sensitive).
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $notContains: 'Hello',
+ },
+ },
+});
+```
+
+### `$containsi`
+
+Attribute contains the input value. `$containsi` is not case-sensitive, while [$contains](#contains) is.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $contains: 'hello',
+ },
+ },
+});
+```
+
+### `$notContainsi`
+
+Attribute does not contain the input value. `$notContainsi` is not case-sensitive, while [$notContains](#notcontains) is.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $notContains: 'hello',
+ },
+ },
+});
+```
+
+### `$startsWith`
+
+Attribute starts with input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $startsWith: 'ABCD',
+ },
+ },
+});
+```
+
+### `$endsWith`
+
+Attribute ends with input value.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $endsWith: 'ABCD',
+ },
+ },
+});
+```
+
+### `$null`
+
+Attribute is `null`.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $null: true,
+ },
+ },
+});
+```
+
+### `$notNull`
+
+Attribute is not null.
+
+**Example**
+
+```js
+const entries = await strapi.entityService.findMany('api::article.article', {
+ filters: {
+ title: {
+ $notNull: true,
+ },
+ },
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md
new file mode 100644
index 0000000000..d106259204
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.md
@@ -0,0 +1,74 @@
+---
+title: Ordering & Pagination with Entity Service API - Strapi Developer Docs
+description: Use Strapi's Entity Service API to order and paginate queries results.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/entity-service/order-pagination.html
+---
+
+# Entity Service API: Ordering & Pagination
+
+The [Entity Service API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) offers the ability to [order](#ordering) and [paginate](#pagination) results found with its [findMany()](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/crud.md#findmany) method.
+
+## Ordering
+
+To order results returned by the Entity Service API, use the `orderBy` parameter. Results can be ordered based on a [single](#single) or on [multiple](#multiple) attribute(s) and can also use [relational ordering](#relational-ordering).
+
+### Single
+
+To order results by a single field, just pass it to the `orderBy` parameter:
+
+- either as a string to sort with the default ascending order
+- or as an object to define both the field name and the order (i.e. `'asc'` for ascending order or `'desc'` for descending order)
+
+```js
+strapi.entityService('api::article.article').findMany({
+ orderBy: 'id',
+});
+
+// single with direction
+strapi.entityService('api::article.article').findMany({
+ orderBy: { id: 'desc' },
+});
+```
+
+### Multiple
+
+To order results by multiple fields, pass the fields as an array to the `orderBy` parameter:
+
+- either as an array of strings to sort multiple fields using the default ascending order
+- or as an array of objects to define both the field name and the order (i.e. `'asc'` for ascending order or `'desc'` for descending order)
+
+```js
+strapi.entityService('api::article.article').findMany({
+ orderBy: ['publishDate', 'name'],
+});
+
+// multiple with direction
+strapi.entityService('api::article.article').findMany({
+ orderBy: [{ title: 'asc' }, { publishedAt: 'desc' }],
+});
+```
+
+### Relational ordering
+
+Fields can also be sorted based on fields from relations:
+
+```js
+strapi.entityService('api::article.article').findMany({
+ orderBy: {
+ author: {
+ name: 'asc',
+ },
+ },
+});
+```
+
+## Pagination
+
+To paginate results returned by the Entity Service API, use the `start` and `limit` parameters:
+
+```js
+strapi.entityService('api::article.article').findMany({
+ start: 10,
+ limit: 15,
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md
new file mode 100644
index 0000000000..b2bb8716d7
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.md
@@ -0,0 +1,70 @@
+---
+title: Entity Service API - Populating - Strapi Developer Docs
+description: Use Strapi's Entity Service API to populate relations in your queries.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/entity-service/populate.html
+---
+
+# Entity Service API: Populating
+
+The [Entity Service API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) does not populate relations, components or dynamic zones by default.
+
+## Basic populating
+
+To populate all the root level relations, use `populate: true`:
+
+```js
+strapi.entityService('api::article.article').findMany({
+ populate: true,
+});
+```
+
+Select which data to populate by passing an array of attribute names:
+
+```js
+strapi.entityService('api::article.article').findMany({
+ populate: ['componentA', 'relationA'],
+});
+```
+
+## Advanced populating
+
+An object can be passed for more advanced populating:
+
+```js
+strapi.entityService('api::article.article').findMany({
+ populate: {
+ componentB: true,
+ dynamiczoneA: true,
+ repeatableComponent: {
+ fields: ['fieldA'],
+ filters: {},
+ sort: 'fieldA:asc',
+ populate: false,
+ },
+ },
+});
+```
+
+Complex populating can be achieved by using the [`filters` parameter](/developer-docs/latest/developer-resources/database-apis-reference/entity-service/filter.md) and select or populate nested relations or components:
+
+```js
+strapi.entityService('api::article.article').findMany({
+ populate: {
+ relationA: {
+ filters: {
+ name: {
+ $contains: 'Strapi',
+ },
+ },
+ },
+
+ repeatableComponent: {
+ fields: ['someAttributeName'],
+ orderBy: ['someAttributeName'],
+ populate: {
+ componentRelationA: true,
+ },
+ },
+ },
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md
new file mode 100644
index 0000000000..5eb5361f13
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md
@@ -0,0 +1,434 @@
+---
+title: GraphQL API - Strapi Developer Docs
+description: Use a GraphQL endpoint in your Strapi project to fetch and mutate your content.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.html
+---
+
+# GraphQL API
+
+::: prerequisites
+To use the GraphQL API, install the [GraphQL](/developer-docs/latest/plugins/graphql.md) plugin.
+:::
+
+The GraphQL API allows performing queries and mutations to interact with the [content-types](/developer-docs/latest/development/backend-customization/models.md#content-types) through Strapi's [GraphQL plugin](/developer-docs/latest/plugins/graphql.md). Results can be [filtered](#filters), [sorted](#sorting) and [paginated](#pagination).
+
+## Unified response format
+
+Responses are unified with the GraphQL API in that:
+
+- queries and mutations that return information for a single entry mainly use a `XxxEntityResponse` type
+- queries and mutations that return i️nformation for multiple entries mainly use a `XxxEntityResponseCollection` type, which includes `meta` information (with [pagination](#pagination)) in addition to the data itself
+
+Responses can also include an `error` (see [error handling documentation](/developer-docs/latest/developer-resources/error-handling.md)).
+
+::: details Example: Response formats for queries and mutations with an example 'Article' content-type
+
+```graphql
+type ArticleEntityResponse {
+ data: ArticleEntity
+}
+
+type ArticleEntityResponseCollection {
+ data: [ArticleEntityResponse!]!
+ meta: ResponseCollectionMeta!
+}
+
+query {
+ article(...): ArticleEntityResponse # find one
+ articles(...): ArticleEntityResponseCollection # find many
+}
+
+mutation {
+ createArticle(...): ArticleEntityResponse # create
+ updateArticle(...): ArticleEntityResponse # update
+ deleteArticle(...): ArticleEntityResponse # delete
+}
+```
+
+:::
+
+## Queries
+
+Queries in GraphQL are used to fetch data without modifying it.
+
+We assume that the [Shadow CRUD](/developer-docs/latest/plugins/graphql.md#shadow-crud) feature is enabled. For each model, the GraphQL plugin auto-generates queries and mutations that mimics basic CRUD operations (findMany, findOne, create, update, delete).
+
+### Fetch a single entry
+
+Single entries can be found by their `id`.
+
+:::request Example query: Find the entry with id 1
+```graphql
+query {
+ document(id: 1) {
+ data {
+ id
+ attributes {
+ title
+ categories {
+ data {
+ id
+ attributes {
+ name
+ }
+ }
+ }
+ }
+ }
+ }
+}
+
+```
+
+:::
+
+### Fetch multiple entries
+
+:::request Example query: Find all documents and populate 'categories' relation with the `name` attribute
+
+```graphql
+query {
+ documents {
+ data {
+ id
+ attributes {
+ title
+ categories {
+ data {
+ id
+ attributes {
+ name
+ }
+ }
+ }
+ }
+ }
+ meta {
+ pagination {
+ page
+ pageSize
+ total
+ pageCount
+ }
+ }
+ }
+}
+
+```
+
+:::
+
+### Fetch dynamic zone data
+
+Dynamic zones are union types in graphql so you need to use fragments to query the fields.
+
+:::request Query
+```graphql
+query {
+ restaurants {
+ data {
+ attributes {
+ dynamiczone {
+ __typename
+ ...on ComponentDefaultClosingperiod {
+ label
+ }
+ }
+ }
+ }
+ }
+}
+```
+:::
+
+## Mutations
+
+Mutations in GraphQL are used to modify data (e.g. create, update, delete data).
+### Create a new entry
+
+:::request Mutation
+
+```graphql
+mutation createArticle {
+ createArticle(data: { title: "Hello"}) {
+ data {
+ id
+ attributes {
+ title
+ }
+ }
+ }
+}
+```
+
+:::
+
+The implementation of the mutations also supports relational attributes. For example, you can create a new `User` and attach many `Restaurant` to it by writing your query like this:
+
+:::request Mutation
+
+```graphql
+mutation {
+ createUser(
+ data: {
+ username: "John"
+ email: "john@doe.com"
+ restaurants: ["1", "2"]
+ }
+ ) {
+ data {
+ id
+ attributes {
+ username
+ email
+ restaurants {
+ data {
+ id
+ attributes {
+ name
+ description
+ price
+ }
+ }
+ }
+ }
+ }
+ }
+}
+```
+
+:::
+
+### Update an existing entry
+
+:::request Mutation
+
+```graphql
+mutation updateArticle {
+ updateArticle(id: "1", data: { title: "Hello" }) {
+ data {
+ id
+ attributes {
+ title
+ }
+ }
+ }
+}
+```
+
+:::
+
+You can also update relational attributes by passing an ID or an array of IDs (depending on the relationship).
+
+:::request Mutation
+```graphql
+mutation {
+ updateRestaurant(
+ id: "5b5b27f8164f75c29c728110"
+ data: {
+ chef: "1" // User ID
+ }
+ }) {
+ data {
+ id
+ attributes {
+ chef {
+ data {
+ attributes {
+ username
+ email
+ }
+ }
+ }
+ }
+ }
+ }
+}
+```
+:::
+
+### Delete an entry
+
+:::request Mutation
+
+```graphql
+mutation deleteArticle {
+ deleteArticle(id: 1) {
+ data {
+ id
+ attributes {
+ title
+ }
+ }
+ }
+}
+```
+
+:::
+
+## Filters
+
+Queries can accept a `filters` parameter with the following syntax:
+
+`filters: { field: { operator: value } }`
+
+Logical operators (`and`, `or`, `not`) can also be used and accept arrays of objects.
+
+The following operators are available:
+
+| Operator | Description |
+| -------------- | ---------------------------------- |
+| `eq` | Equal |
+| `ne` | Not equal |
+| `lt` | Less than |
+| `lte` | Less than or equal to |
+| `gt` | Greater than |
+| `gte` | Greater than or equal to |
+| `in` | Included in an array |
+| `notIn` | Not included in an array |
+| `contains` | Contains, case sensitive |
+| `notContains` | Does not contain, case sensitive |
+| `containsi` | Contains, case insensitive |
+| `notContainsi` | Does not contain, case insensitive |
+| `null` | Is null |
+| `notNull` | Is null |
+| `between` | Is between |
+| `startsWith` | Starts with |
+| `endsWith` | Ends with |
+| `and` | Logical `and` |
+| `or` | Logical `or` |
+| `not` | Logical `not` |
+
+::: request Example query with filters
+
+```graphql
+{
+ documents(filters: { name: { eq: "test" }, or: [{ price: { gt: 10 }}, { title: { startsWith: "Book" }}] }) {
+ data {
+ id
+ }
+ }
+}
+```
+
+:::
+
+## Sorting
+
+Queries can accept a `sort` parameter with the following syntax:
+
+- to sort based on a single value: `sort: "value"`
+- to sort based on multiple values: `sort: ["value1", "value2"]`
+
+The sorting order can be defined with `:asc` (ascending order, default, can be omitted) or `:desc` (for descending order).
+
+::: request Example request: Sorting on title by ascending order
+
+```graphql
+{
+ documents(sort: "title") {
+ data {
+ id
+ }
+ }
+}
+```
+
+:::
+
+::: request Example request: Sorting on title by descending order
+
+```graphql
+{
+ documents(sort: "title:desc") {
+ data {
+ id
+ }
+ }
+}
+```
+
+:::
+
+::: request Example request: Sorting on title by ascending order, then on price by descending order
+
+```graphql
+{
+ documents(sort: ["title:asc", "price:desc"]) {
+ data {
+ id
+ }
+ }
+}
+```
+
+:::
+
+## Pagination
+
+Queries can accept a `pagination` parameter. Results can be paginated either by page or by offset.
+
+:::note
+Pagination methods can not be mixed. Always use either `page` with `pageSize` **or** `start` with `limit`.
+:::
+
+### Pagination by page
+
+| Parameter | Description | Default |
+| ---------------------- | ----------- | ------- |
+| `pagination[page]` | Page number | 1 |
+| `pagination[pageSize]` | Page size | 10 |
+
+::: request Example query: Pagination by page
+
+```graphql
+{
+ documents(pagination: { page: 1, pageSize: 10 }) {
+ data {
+ id
+ }
+ meta {
+ pagination {
+ page
+ pageSize
+ pageCount
+ total
+ }
+ }
+ }
+}
+```
+
+:::
+
+### Pagination by offset
+
+| Parameter | Description | Default | Maximum |
+| ------------------- | ---------------------------- | ------- | ------- |
+| `pagination[start]` | Start value | 0 | - |
+| `pagination[limit]` | Number of entities to return | 10 | -1 |
+
+::: request Example query: Pagination by offset
+
+```graphql
+{
+ documents(pagination: { start: 20, limit: 30 }) {
+ data {
+ id
+ }
+ meta {
+ pagination {
+ start
+ limit
+ }
+ }
+ }
+}
+```
+
+:::
+
+::: tip
+The default and maximum values for `pagination[limit]` can be [configured in the `./config/plugins.js`](/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md#graphql-configuration) file with the `graphql.config.defaultLimit` and `graphql.config.maxLimit` keys.
+:::
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.md
new file mode 100644
index 0000000000..44ff4cee2a
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.md
@@ -0,0 +1,36 @@
+---
+title: Query Engine API - Strapi Developer Docs
+description: Strapi provides a Query Engine API to give unrestricted internal access to the database layer at a lower level.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.html
+---
+
+# Query Engine API
+
+Strapi provides a Query Engine API to interact with the database layer at a lower level. It should mostly be used by plugin developers and developers adding custom business logic to their applications.
+
+Strapi's Query Engine API gives unrestricted internal access to the database layer. It is not aware of the complex data structures like components and dynamic zones, as opposed to the [Entity Service API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md).
+
+## Basic usage
+
+The Query Engine is available through `strapi.db.query`:
+
+```js
+strapi.db.query('api::blog.article').findMany({ // uid syntax: 'api::api-name.content-type-name'
+ where: {
+ title: {
+ $startWith: '2021',
+ $endsWith: 'v4',
+ },
+ },
+ populate: {
+ category: true,
+ },
+});
+```
+
+## Available operations
+
+The Query Engine allows operations on database entries, such as:
+
+- CRUD operations on [single entries](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/single-operations.md) or [multiple entries](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/bulk-operations.md)
+- [filtering entries](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md), [populating relations](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) and [ordering and paginating queries results](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md)
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/bulk-operations.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/bulk-operations.md
new file mode 100644
index 0000000000..df660965dd
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/bulk-operations.md
@@ -0,0 +1,120 @@
+---
+title: Bulk Operations for Query Engine API - Strapi Developer Docs
+description: Use Strapi's Query Engine API to perform operations on multiple entries.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/query-engine/bulk-operations.html
+---
+
+# Query Engine API: Bulk Operations
+
+:::caution
+To avoid performance issues, bulk operations are not allowed on relations.
+:::
+
+## createMany()
+
+Creates multiple entries.
+
+Syntax: `createMany(parameters) => { count: number }`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | ---------- | ------------------- |
+| `data` | Array of objects | Array of input data |
+
+### Example
+
+```js
+await strapi.db.query('api::blog.article').createMany({
+ data: [
+ {
+ title: 'ABCD',
+ },
+ {
+ title: 'EFGH',
+ },
+ ],
+});
+
+// { count: 2 }
+```
+
+## updateMany()
+
+Updates multiple entries matching the parameters.
+
+Syntax: `updateMany(parameters) => { count: number }`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | -------------------------- | ------------------- |
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+| `data` | Object | Input data |
+
+### Example
+
+```js
+await strapi.db.query('api::shop.article').updateMany({
+ where: {
+ price: 20,
+ },
+ data: {
+ price: 18,
+ },
+});
+
+// { count: 42 }
+```
+
+## deleteMany()
+
+Deletes multiple entries matching the parameters.
+
+Syntax: `deleteMany(parameters) => { count: number }`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | -------------------------- | ----------- |
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+
+### Example
+
+```js
+await strapi.db.query('api::blog.article').deleteMany({
+ where: {
+ title: {
+ $startsWith: 'v3',
+ },
+ },
+});
+
+// { count: 42 }
+```
+
+## Aggregations
+
+### count()
+
+Counts entries matching the parameters.
+
+Syntax: `count(parameters) => number`
+
+#### Parameters
+
+| Parameter | Type | Description |
+| --------- | -------------------------- | ----------- |
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+
+```js
+const count = await strapi.db.query('api::blog.article').count({
+ where: {
+ title: {
+ $startsWith: 'v3',
+ },
+ },
+});
+
+// 12
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md
new file mode 100644
index 0000000000..79f450420e
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md
@@ -0,0 +1,357 @@
+---
+title: Filtering Operations for Query Engine API - Strapi Developer Docs
+description: Use Strapi's Query Engine API to filter the results of your queries.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.html
+---
+
+# Query Engine API: Filtering
+
+The [Query Engine API](/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.md) offers the ability to filter results found with its [findMany()](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/single-operations.md#findmany) method.
+
+Results are filtered with the `filters` parameter that accepts [logical operators](#logical-operators) and [attribute operators](#attribute-operators). Every operator should be prefixed with `$`.
+
+## Logical operators
+
+### `$and`
+
+All nested conditions must be `true`.
+
+**Example**
+
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ $and: [
+ {
+ rating: {
+ $gte: 12,
+ }
+ },
+ {
+ title: {
+ $contains: 'Hello',
+ },
+ },
+ ],
+ },
+});
+```
+
+`$and` is used implicitly when passing an object with nested conditions:
+
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ title: 'Hello World',
+ rating: 12,
+ },
+});
+```
+
+### `$or`
+
+One or many nested conditions must be `true`.
+
+**Example**
+
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ $or: [
+ {
+ title: 'Hello World',
+ },
+ {
+ title: {
+ $contains: 'Hello',
+ },
+ },
+ ],
+ },
+});
+```
+
+### `$not`
+
+Negates the nested conditions.
+
+**Example**
+
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ $not: {
+ title: {
+ $contains: 'Hello'
+ },
+ },
+ },
+});
+```
+
+## Attribute Operators
+
+:::caution
+Using these operators may give different results depending on the database's implementation, as the comparison is handled by the database and not by Strapi.
+:::
+
+### `$not`
+
+Negates nested condition. The `not` operator can be used in an attribute condition too.
+
+**Example**
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $not: 'Hello World',
+ },
+ },
+});
+```
+
+### `$eq`
+
+Attribute equals input value.
+
+**Example**
+
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $eq: 'Hello World',
+ },
+ },
+});
+```
+
+`$eq` can be omitted:
+
+```js
+const entries = await strapi.db.query('api::article.article').findMany({
+ where: {
+ title: 'Hello World',
+ },
+});
+```
+
+### `$ne`
+
+Attribute does not equal input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $ne: 'ABCD',
+ },
+ },
+});
+```
+
+### `$in`
+
+Attribute is contained in the input list.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $in: ['Hello', 'Hola', 'Bonjour'],
+ },
+ },
+});
+```
+
+`$in` can be ommited when passing an array of values
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: ['Hello', 'Hola', 'Bonjour'],
+ },
+});
+```
+
+### `$nin`
+
+Attribute is not contained in the input list.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $nin: ['Hello', 'Hola', 'Bonjour'],
+ },
+ },
+});
+```
+
+### `$lt`
+
+Attribute is less than the input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ rating: {
+ $lt: 10,
+ },
+ },
+});
+```
+
+### `$lte`
+
+Attribute is less than or equal to the input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ rating: {
+ $lte: 10,
+ },
+ },
+});
+```
+
+### `$gt`
+
+Attribute is greater than the input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ rating: {
+ $gt: 5,
+ },
+ },
+});
+```
+
+### `$gte`
+
+Attribute is greater than or equal to the input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ rating: {
+ $gte: 5,
+ },
+ },
+});
+```
+
+### `$between`
+
+Attribute is between the 2 input values.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ rating: {
+ $between: [1, 20],
+ },
+ },
+});
+```
+
+
+### `$contains`
+
+Attribute contains the input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $contains: 'ABCD',
+ },
+ },
+});
+```
+
+### `$startsWith`
+
+Attribute starts with input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $startsWith: 'ABCD',
+ },
+ },
+});
+```
+
+### `$endsWith`
+
+Attribute ends with input value.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $endsWith: 'ABCD',
+ },
+ },
+});
+```
+
+### `$null`
+
+Attribute is `null`.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $null: false,
+ },
+ },
+});
+```
+
+### `$notNull`
+
+Attribute is not `null`.
+
+**Example**
+
+```js
+const entries = strapi.db.query('api::article.article').findMany({
+ where: {
+ title: {
+ $notNull: true,
+ },
+ },
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md
new file mode 100644
index 0000000000..ab54863df4
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md
@@ -0,0 +1,62 @@
+---
+title: Ordering & Pagination for Query Engine API - Strapi Developer Docs
+description: Use Strapi's Query Engine API to order and paginate the results of your queries.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.html
+---
+
+# Query Engine API: Ordering & Paginating
+
+The [Query Engine API](/developer-docs/latest/developer-resources/database-apis-reference/query-engine-api.md) offers the ability to [order](#ordering) and [paginate](#pagination) results.
+
+## Ordering
+
+To order results returned by the Query Engine, use the `orderBy` parameter. Results can be ordered based on a [single](#single) or on [multiple](#multiple) attributes and can also use [relational ordering](#relational-ordering).
+
+### Single
+
+```js
+strapi.db.query('api::article.article').findMany({
+ orderBy: 'id',
+});
+
+// single with direction
+strapi.db.query('api::article.article').findMany({
+ orderBy: { id: 'asc' },
+});
+```
+
+### Multiple
+
+```js
+strapi.db.query('api::article.article').findMany({
+ orderBy: ['id', 'name'],
+});
+
+// multiple with direction
+strapi.db.query('api::article.article').findMany({
+ orderBy: [{ title: 'asc' }, { publishedAt: 'desc' }],
+});
+```
+
+### Relational ordering
+
+```js
+strapi.db.query('api::article.article').findMany({
+ orderBy: {
+ author: {
+ name: 'asc',
+ },
+ },
+});
+```
+
+## Pagination
+
+To paginate results returned by the Query Engine API, use the `offset` and `limit` parameters:
+
+```js
+strapi.db.query('api::article.article').findMany({
+ offset: 15,
+ limit: 10,
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md
new file mode 100644
index 0000000000..013f057edc
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md
@@ -0,0 +1,63 @@
+---
+title: Populating for Query Engine API - Strapi Developer Docs
+description: Use Strapi's Query Engine API to populate relations when querying your content.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.html
+---
+
+# Query Engine API: Populating
+
+Relations and components have a unified API for populating them.
+
+To populate all the root level relations, use `populate: true`:
+
+```js
+strapi.db.query('api::article.article').findMany({
+ populate: true,
+});
+```
+
+Select which data to populate by passing an array of attribute names:
+
+```js
+strapi.db.query('api::article.article').findMany({
+ populate: ['componentA', 'relationA'],
+});
+```
+
+An object can be passed for more advanced usage:
+
+```js
+strapi.db.query('api::article.article').findMany({
+ populate: {
+ componentB: true,
+ dynamiczoneA: true,
+ relation: someLogic || true,
+ },
+});
+```
+
+Complex populating can also be achieved by applying `where` filters and select or populate nested relations:
+
+```js
+strapi.db.query('api::article.article').findMany({
+ populate: {
+ relationA: {
+ where: {
+ name: {
+ $contains: 'Strapi',
+ },
+ },
+ },
+
+ repeatableComponent: {
+ select: ['someAttributeName'],
+ orderBy: ['someAttributeName'],
+ populate: {
+ componentRelationA: true,
+ },
+ },
+
+ dynamiczoneA: true,
+ },
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/single-operations.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/single-operations.md
new file mode 100644
index 0000000000..f46944c662
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/query-engine/single-operations.md
@@ -0,0 +1,162 @@
+---
+title: Single Operations for Query Engine API - Strapi Developer Docs
+description: Use Strapi's Query Engine API to perform operations on single entries.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/query-engine/single-operations.html
+---
+
+# Query Engine API: Single Operations
+
+## findOne()
+
+Finds the first entry matching the parameters.
+
+Syntax: `findOne(parameters) ⇒ Entry`
+
+### Parameters
+
+| Parameter | Type | Description |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `select` | String, or Array of strings | [Attributes](/developer-docs/latest/development/backend-customization/models.md#model-attributes) to return |
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+| `offset` | Integer | Number of entries to skip |
+| `orderBy` | [`OrderByParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md) | [Order](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md) definition |
+| `populate` | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) | Relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md)
+
+### Example
+
+```js
+const entry = await strapi.db.query('api::blog.article').findOne({
+ select: ['title', 'description'],
+ where: { title: 'Hello World' },
+ populate: { category: true },
+});
+```
+
+## findMany()
+
+Finds entries matching the parameters.
+
+Syntax: `findMany(parameters) ⇒ Entry[]`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | ------------------------------ | ------------------------------------------ |
+| `select` | String, or Array of strings | [Attributes](/developer-docs/latest/development/backend-customization/models.md#model-attributes) to return |
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+| `limit` | Integer | Number of entries to return |
+| `offset` | Integer | Number of entries to skip |
+| `orderBy` | [`OrderByParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md) | [Order](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md) definition |
+| `populate` | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) | Relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md)
+
+### Example
+
+```js
+const entries = await strapi.db.query('api::blog.article').findMany({
+ select: ['title', 'description'],
+ where: { title: 'Hello World' },
+ orderBy: { publishedAt: 'DESC' },
+ populate: { category: true },
+});
+```
+
+## findWithCount()
+
+Finds and counts entries matching the parameters.
+
+Syntax: `findWithCount(parameters) => [Entry[], number]`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | ------------------------------ | ------------------------------------------ |
+| `select` | String, or Array of strings | [Attributes](/developer-docs/latest/development/backend-customization/models.md#model-attributes) to return |
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+| `limit` | Integer | Number of entries to return |
+| `offset` | Integer | Number of entries to skip |
+| `orderBy` | [`OrderByParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md) | [Order](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/order-pagination.md) definition |
+| `populate` | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) | Relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md)
+|
+
+### Example
+
+```js
+const [entries, count] = await strapi.db.query('api::blog.article').findWithCount({
+ select: ['title', 'description'],
+ where: { title: 'Hello World' },
+ orderBy: { title: 'DESC' },
+ populate: { category: true },
+});
+```
+
+## create()
+
+Creates one entry and returns it.
+
+Syntax: `create(parameters) => Entry`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | ------------------------------ | ------------------------------------------ |
+| `select` | String, or Array of strings | [Attributes](/developer-docs/latest/development/backend-customization/models.md#model-attributes) to return |
+| `populate` | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) | Relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md)
+| data | Object | Input data |
+
+### Example
+
+```js
+const entry = await strapi.db.query('api::blog.article').create({
+ data: {
+ title: 'My Article',
+ },
+});
+```
+
+## update()
+
+Updates one entry and returns it.
+
+Syntax: `update(parameters) => Entry`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | ------------------------------ | ------------------------------------------ |
+| `select` | String, or Array of strings | [Attributes](/developer-docs/latest/development/backend-customization/models.md#model-attributes) to return |
+| `populate` | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) | Relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md)
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+| `data` | Object | Input data |
+
+### Example
+
+```js
+const entry = await strapi.db.query('api::blog.article').update({
+ where: { id: 1 },
+ data: {
+ title: 'xxx',
+ },
+});
+```
+
+## delete()
+
+Deletes one entry and returns it.
+
+Syntax: `delete(parameters) => Entry`
+
+### Parameters
+
+| Parameter | Type | Description |
+| --------- | ------------------------------ | ------------------------------------------ |
+| `select` | String, or Array of strings | [Attributes](/developer-docs/latest/development/backend-customization/models.md#model-attributes) to return |
+| `populate` | [`PopulateParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md) | Relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/populating.md)
+| `where` | [`WhereParameter`](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) | [Filters](/developer-docs/latest/developer-resources/database-apis-reference/query-engine/filtering.md) to use |
+
+### Example
+
+```js
+const entry = await strapi.db.query('api::blog.article').delete({
+ where: { id: 1 },
+});
+```
diff --git a/docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md b/docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md
new file mode 100644
index 0000000000..6f639c0fa2
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md
@@ -0,0 +1,676 @@
+---
+title: REST API - Strapi Developer Docs
+description: Interact with your Content-Types using the REST API endpoints Strapi generates for you.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/database-apis-reference/rest-api.html
+---
+
+# REST API
+
+The REST API allows accessing the [content-types](/developer-docs/latest/development/backend-customization/models.md#content-types) through API endpoints that Strapi automatically creates.
+
+[API parameters](#api-parameters) can be used to [filter](#filters), [sort](#sorting), and [paginate](#pagination) results and to [select fields](#fields-selection) and relations to [populate](#relations-population). Additionally, specific parameters related to optional Strapi features can be used, like [publication state](#publication-state) and [locale](#locale).
+
+## API Endpoints
+
+Creating a content-type automatically creates some REST API endpoints available to interact with it.
+
+:::note
+[Components](/developer-docs/latest/development/backend-customization/models.md#components) don't have API endpoints.
+:::
+
+### Endpoints
+
+For each Content-Type, the following endpoints are automatically generated:
+
+
+
+:::: tabs card
+
+::: tab Collection Type
+
+
+
+| Method | URL | Description |
+| -------- | ------------------------------- | ------------------------------------- |
+| `GET` | `/api/:pluralApiId` | [Get a list of entries](#get-entries) |
+| `POST` | `/api/:pluralApiId` | [Create an entry](#create-an-entry) |
+| `GET` | `/api/:pluralApiId/:documentId` | [Get an entry](#get-an-entry) |
+| `PUT` | `/api/:pluralApiId/:documentId` | [Update an entry](#update-an-entry) |
+| `DELETE` | `/api/:pluralApiId/:documentId` | [Delete an entry](#delete-an-entry) |
+
+
+
+:::
+
+::: tab Single Type
+
+
+
+| Method | URL | Description |
+| -------- | --------------------- | ----------------------------------- |
+| `GET` | `/api/:singularApiId` | [Get an entry](#get-an-entry) |
+| `PUT` | `/api/:singularApiId` | [Update/Create an entry](#update-an-entry) |
+| `DELETE` | `/api/:singularApiId` | [Delete an entry](#delete-an-entry) |
+
+
+
+:::
+
+::::
+
+::::: details Examples
+
+:::: tabs card
+
+::: tab Collection Type
+
+`Restaurant` **Content Type**
+
+
+
+| Method | URL | Description |
+| ------ | ------------------------ | ------------------------- |
+| GET | `/api/restaurants` | Get a list of restaurants |
+| POST | `/api/restaurants` | Create a restaurant |
+| GET | `/api/restaurants/:id` | Get a specific restaurant |
+| DELETE | `/api/restaurants/:id` | Delete a restaurant |
+| PUT | `/api/restaurants/:id` | Update a restaurant |
+
+
+
+:::
+
+::: tab Single Type
+
+`Homepage` **Content Type**
+
+
+
+| Method | URL | Description |
+| ------ | --------------- | ---------------------------------- |
+| GET | `/api/homepage` | Get the homepage content |
+| PUT | `/api/homepage` | Update/create the homepage content |
+| DELETE | `/api/homepage` | Delete the homepage content |
+
+
+
+:::
+::::
+:::::
+
+### Unified response format
+
+Whatever the query, the response is always an object with the following keys:
+
+- `data`: the response data itself, which could be:
+ - a single entry, as an object with the following keys:
+ - `id` (number)
+ - `attributes` (object)
+ - `meta` (object)
+ - a list of entries, as an array of objects
+ - a custom response
+
+- `meta`(object): information about pagination, publication state, available locales, etc.
+
+- `error` (object, _optional_): information about any [error](/developer-docs/latest/developer-resources/error-handling.md) thrown by the request
+
+### Get entries
+
+Returns entries matching the query filters (see [parameters](#api-parameters) documentation).
+
+:::: api-call
+
+::: request Example request
+
+`GET http://localhost:1337/api/restaurants`
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": [
+ {
+ "id": 1,
+ "attributes": {
+ "title": "Restaurant A",
+ "description": "Restaurant A's description",
+ "categories": [
+ {
+ "id": 1,
+ "attributes": {
+ "name": "My category"
+ },
+ "meta": {
+ "availableLocales": []
+ }
+ }
+ ]
+ },
+ "meta": {
+ "availableLocales": []
+ }
+ },
+ {
+ "id": 2,
+ "attributes": {
+ "title": "Restaurant B",
+ "description": "Restaurant B's description",
+ "categories": [
+ {
+ "id": 1,
+ "attributes": {
+ "name": "My category"
+ },
+ "meta": {
+ "availableLocales": []
+ }
+ }
+ ]
+ },
+ "meta": {
+ "availableLocales": []
+ }
+ },
+ ],
+ "meta": {}
+}
+
+```
+
+:::
+
+::::
+
+### Get an entry
+
+Returns an entry by id.
+
+:::: api-call
+
+::: request Example request
+
+`GET http://localhost:1337/api/restaurants/1`
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "id": 1,
+ "attributes": {
+ "title": "Restaurant A",
+ "description": "Restaurant A's description",
+ "categories": [
+ {
+ "id": 1,
+ "attributes": {
+ "name": "My category"
+ },
+ "meta": {
+ "availableLocales": []
+ }
+ }
+ ]
+ },
+ "meta": {
+ "availableLocales": []
+ }
+ },
+ "meta": {}
+}
+
+```
+
+:::
+
+::::
+
+### Create an entry
+
+Creates an entry and returns its value.
+
+If the [Internationalization (i18n) plugin](/developer-docs/latest/plugins/i18n.md) is installed, it's possible to use POST requests to the Content API to [create localized entries](/developer-docs/latest/plugins/i18n.md#creating-a-new-localized-entry).
+
+:::: api-call
+
+::: request Example request
+
+`POST http://localhost:1337/api/restaurants`
+
+```json
+{
+ "data": {
+ "title": "Hello",
+ "relation": 2,
+ "relations": [2, 4],
+ "link": {
+ "id": 1,
+ "type": "abc"
+ }
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "id": 1,
+ "attributes": { … },
+ "meta": {}
+ },
+ "meta": {}
+}
+```
+
+:::
+
+::::
+
+### Update an entry
+
+Partially updates an entry by `id` and returns its value.
+Fields that aren't sent in the query are not changed in the database. Send a `null` value if you want to clear them.
+
+:::: api-call
+
+::: request Example request
+
+`PUT http://localhost:1337/api/restaurants/1`
+
+```json
+{
+ "data": {
+ "title": "Hello",
+ "relation": 2,
+ "relations": [2, 4],
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "id": 1,
+ "attributes": {},
+ "meta": {}
+ },
+ "meta": {}
+}
+```
+
+:::
+
+::::
+
+:::note
+If the [Internationalization (i18n) plugin](/developer-docs/latest/plugins/i18n.md) is installed, it's currently not possible to [update the locale of an entry](/developer-docs/latest/plugins/i18n.md#updating-an-entry).
+:::
+
+### Delete an entry
+
+Deletes an entry by id and returns its value.
+
+:::: api-call
+
+::: request Example request
+
+`DELETE http://localhost:1337/api/restaurants/1`
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "id": 1,
+ "attributes": {},
+ "meta": {}
+ },
+ "meta": {}
+}
+```
+
+:::
+::::
+
+## API Parameters
+
+Query parameters use the LHS bracket syntax (i.e. they are encoded using square brackets `[]`).
+
+::::tip
+Strapi takes advantage of the ability of [`qs`](https://github.com/ljharb/qs) to parse nested objects to create more complex queries.
+Use `qs` directly to generate complex queries instead of creating them manually.
+
+:::details Example
+
+```js
+const qs = require('qs');
+const query = qs.stringify({
+ filters: {
+ $or: [
+ {
+ date: {
+ $eq: '2020-01-01'
+ },
+ },
+ {
+ date: {
+ $eq: '2020-01-02'
+ },
+ }
+ ],
+ title: {
+ $eq: 'hello'
+ },
+ author: {
+ name: {
+ $eq: 'Kai doe'
+ },
+ },
+ },
+}, {
+ encodeValuesOnly: true, // prettify url
+});
+
+await request(`/api/books?${query}`);
+// GET /api/books?filters[$or][0][date][$eq]=2020-01-01&filters[$or][1][date][$eq]=2020-01-02&filters[title][$eq]=hello&filters[author][name][$eq]=Kai%20doe
+```
+
+:::
+::::
+
+### Filters
+
+Queries can accept a `filters` parameter with the following syntax:
+
+`GET /api/:pluralApiId?filters[field][operator]=value`
+
+The following operators are available:
+
+| Operator | Description |
+| --------------- | --------------------------------- |
+| `$eq` | Equal |
+| `$ne` | Not equal |
+| `$lt` | Less than |
+| `$lte` | Less than or equal to |
+| `$gt` | Greater than |
+| `$gte` | Greater than or equal to |
+| `$in` | Included in an array |
+| `$notIn` | Not included in an array |
+| `$contains` | Contains (case-sensitive) |
+| `$notContains` | Does not contain (case-sensitive) |
+| `$containsi` | Contains |
+| `$notContainsi` | Does not contain |
+| `$null` | Is null |
+| `$notNull` | Is not null |
+| `$between` | Is between |
+| `$startsWith` | Starts with |
+| `$endsWith` | Ends with |
+
+:::request Example request: Find users having 'John' as first name
+`GET /api/users?filters[firstName][$eq]=John`
+:::
+
+:::request Example request: Find restaurants having a price equal or greater than `3`
+`GET /api/restaurants?filters[price][$gte]=3`
+:::
+
+:::request Example request: Find multiple restaurant with id 3, 6, 8
+`GET /api/restaurants?filters[id][$in][0]=3&filters[id][$in][1]=6&filters[id][$in][2]=8`
+:::
+
+:::caution
+By default, the filters can only be used from `find` endpoints generated by the Content-Type Builder and the CLI.
+:::
+
+#### Deep filtering
+
+Deep filtering is filtering on a relation's fields.
+
+:::request Example request: Find restaurants owned by a chef who belongs to a 5-star restaurant
+`GET /api/restaurants?filters[chef][restaurant][star][$eq]=5`
+:::
+
+::: caution
+
+- Querying your API with deep filters may cause performance issues. If one of your deep filtering queries is too slow, we recommend building a custom route with an optimized version of the query.
+- Deep filtering isn't available for polymorphic relations.
+
+:::
+
+### Sorting
+
+Queries can accept a `sort` parameter with the following syntax:
+
+`GET /api/:pluralApiId?sort=field1,field2`
+
+The sorting order can be defined with `:asc` (ascending order, default, can be omitted) or `:desc` (for descending order).
+
+:::request Example requests: Sort users by email
+`GET /api/users?sort=email` to sort by ascending order (default)
+
+`GET /api/users?sort=email:desc` to sort by descending order
+:::
+
+:::request Example requests: Sort books on multiple fields
+`GET /api/books?sort=title,price:desc`
+
+`GET /api/books?sort=title,author.name`
+
+`GET /api/books?sort[0]=title&sort[1][author]=name` using an array format
+
+:::
+
+### Pagination
+
+Queries can accept `pagination` parameters. Results can be paginated:
+
+- either by page (i.e. specifying a page number and the number of entries per page)
+- or by offset (i.e. specifying how many entries to skip and to return)
+
+:::note
+Pagination methods can not be mixed. Always use either `page` with `pageSize` **or** `start` with `limit`.
+:::
+
+#### Pagination by page
+
+Use the following parameters:
+
+
+
+| Parameter | Type | Description | Default |
+| ----------------------- | ------- | ------------------------------------------------------------------------- | ------- |
+| `pagination[page]` | Integer | Page number | 1 |
+| `pagination[pageSize]` | Integer | Page size | 100 |
+| `pagination[withCount]` | Boolean | Adds the total numbers of entries and the number of pages to the response | True |
+
+:::: api-call
+
+::: request Example request
+`GET /api/:pluralApiId?pagination[page]=1&pagination[pageSize]=10`
+:::
+
+::: response Example response
+
+```json
+{
+ "data": […],
+ "meta": {
+ "pagination": {
+ "page": 1,
+ "pageSize": 10,
+ "pageCount": 5,
+ "total": 48
+ }
+ }
+}
+```
+
+:::
+::::
+
+#### Pagination by offset
+
+Use the following parameters:
+
+| Parameter | Type | Description | Default |
+| ----------------------- | ------- | -------------------------------------------------------------- | ------- |
+| `pagination[start]` | Integer | Start value (first entry to return) value | 0 |
+| `pagination[limit]` | Integer | Number of entries to return | 25 |
+| `pagination[withCount]` | Boolean | Toggles displaying the total number of entries to the response | `true` |
+
+::: tip
+The default and maximum values for `pagination[limit]` can be [configured in the `./config/api.js`](/developer-docs/latest/setup-deployment-guides/configurations/optional/api.md) file with the `api.rest.defaultLimit` and `api.rest.maxLimit` keys.
+:::
+
+:::: api-call
+
+::: request Example request
+`GET /api/:pluralApiId?pagination[start]=20&pagination[limit]=30`
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": [],
+ "meta": {
+ "pagination": {
+ "start": 0,
+ "limit": 10,
+ "total": 42,
+ }
+ }
+}
+```
+
+:::
+::::
+
+### Fields selection
+
+Queries can accept a `fields` parameter to select only some fields. Use one of the following syntaxes:
+
+`GET /api/:pluralApiId?fields=field1,field2`
+
or
+`GET /api/:pluralApiId?fields[0]=field1&fields[1]=field2`
+
+To get all fields, use the `*` wildcard.
+
+::: request Example request: Get only firstName and lastName of all users
+`GET /api/users?fields=firstName,lastName`
+:::
+
+::: request Example request: Get all fields for all users
+`GET /api/users?fields=*`
+:::
+
+### Relations population
+
+By default, relations are not populated when fetching entries.
+
+Queries can accept a `populate` parameter to explicitly define which fields to populate, with the following syntax:
+
+`GET /api/:pluralApiId?populate=field1,field2`
+
+::: request Example request: Get books and populate relations with the author's name and address
+`GET /api/books?populate=author.name,author.address`
+:::
+
+For convenience, the `*` wildcard can be used to populate all first-level relations:
+
+::: request Example request: Get all books and populate all their first-level relations
+`GET /api/books?populate=*`
+:::
+
+::: request Example request: Get all books and populate with authors and all their relations
+`GET /api/books?populate[author]=*`
+:::
+
+
+
+Only first-level relations are populated with `populate=*`. Use the LHS bracket syntax (i.e. `[populate]=*`) to populate deeper:
+
+::: request Example request: Get all relations nested inside a "navigation" component in the "global" single type
+`GET /api/global?populate[navigation][populate]=*`
+:::
+
+:::tip
+Adding `?populate=*` to the query URL will include dynamic zones in the results.
+:::
+
+### Publication State
+
+:::prerequisites
+The [Draft & Publish](/developer-docs/latest/concepts/draft-and-publish.md) feature should be enabled.
+:::
+
+Queries can accept a `publicationState` parameter to fetch entries based on their publication state:
+
+- `live`: returns only published entries (default)
+- `preview`: returns both draft entries & published entries
+
+:::request Example requests: Get published articles
+`GET /api/articles`
+
+or
+
+`GET /api/articles?publicationState=live`
+:::
+
+:::request Example request: Get both published and draft articles
+`GET /api/articles?publicationState=preview`
+:::
+
+:::tip
+To retrieve only draft entries, combine the `preview` publication state and the `published_at` fields:
+
+`GET /api/articles?publicationState=preview&published_at_null=true`
+:::
+
+### Locale
+
+:::prerequisites
+
+- The [Internationalization (i18n) plugin](/developer-docs/latest/plugins/i18n.md) should be installed.
+- [Localization should be enabled for the content-type](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-content-type).
+:::
+
+The `locale` API parameter can be used to [get entries from a specific locale](/developer-docs/latest/plugins/i18n.md#getting-localized-entries-with-the-locale-parameter).
diff --git a/docs/developer-docs/latest/developer-resources/error-handling.md b/docs/developer-docs/latest/developer-resources/error-handling.md
new file mode 100644
index 0000000000..f5bc265bd8
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/error-handling.md
@@ -0,0 +1,91 @@
+---
+title: Error handling - Strapi Developer Docs
+description: With Strapi's error handling feature it's easy to send and receive errors in your application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/error-handling.html
+---
+
+# Error handling
+
+Strapi is natively handling errors with a standard format.
+
+There are 2 use cases for error handling:
+
+- As a developer querying content through the [REST](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md) or [GraphQL](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md) APIs, you might [receive errors](#receiving-errors) in response to the requests.
+- As a developer customizing the backend of your Strapi application, you could use controllers and services to [throw errors](#throwing-errors).
+
+## Receiving errors
+
+Errors are included in the response object with the `error` key and include information such as the HTTP status code, the name of the error, and additional information.
+
+### REST errors
+
+Errors thrown by the REST API are included in the [response](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#unified-response-format) that has the following format:
+
+```json
+{
+ "data": null,
+ "error": {
+ "status": "", // HTTP status
+ "name": "", // Strapi error name ('ApplicationError' or 'ValidationError')
+ "message": "", // A human reable error message
+ "details": {
+ // error info specific to the error type
+ }
+ }
+}
+```
+
+### GraphQL errors
+
+Errors thrown by the GraphQL API are included in the [response](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md#unified-response-format) that has the following format:
+
+```json
+{ "errors": [
+ {
+ "message": "", // A human reable error message
+ "extensions": {
+ "error": {
+ "name": "", // Strapi error name ('ApplicationError' or 'ValidationError'),
+ "message": "", // A human reable error message (same one as above);
+ "details": {}, // Error info specific to the error type
+ },
+ "code": "" // GraphQL error code (ex: BAD_USER_INPUT)
+ }
+ }
+ ],
+ "data": {
+ "graphQLQueryName": null
+ }
+}
+```
+
+## Throwing errors
+
+The recommended way to throw errors when developing any custom logic with Strapi is to have the [controller](/developer-docs/latest/development/backend-customization/controllers.md) respond with the correct status and body.
+
+This can be done by calling an error function on the context (i.e. `ctx`). Available error functions are listed in the [http-errors documentation](https://github.com/jshttp/http-errors#list-of-all-constructors) but their name should be camel-cased to be used by Strapi (e.g. `badRequest`).
+
+Error functions accept 2 parameters that correspond to the `error.message` and `error.details` attributes [received](#receiving-errors) by a developer querying the API:
+
+- the first parameter of the function is the error `message`
+- and the second one is the object that will be set as `details` in the response received
+
+```js
+
+// path: ./src/api/[api-name]/controllers/my-controller.js
+
+module.exports = {
+ renameDog: async (ctx, next) => {
+ const newName = ctx.request.body.name;
+ if (!newName) {
+ return ctx.badRequest('name is missing', { foo: 'bar' })
+ }
+ ctx.body = strapi.service('api::dog.dog').rename(newName);
+ }
+}
+
+```
+
+:::note
+[Services](/developer-docs/latest/development/backend-customization/services.md) don't have access to the controller's `ctx` object. If services need to throw errors, these need to be caught by the controller, that in turn is in charge of calling the proper error function.
+:::
diff --git a/docs/developer-docs/latest/developer-resources/global-strapi/api-reference.md b/docs/developer-docs/latest/developer-resources/global-strapi/api-reference.md
index 2d1f0bdc91..e69de29bb2 100644
--- a/docs/developer-docs/latest/developer-resources/global-strapi/api-reference.md
+++ b/docs/developer-docs/latest/developer-resources/global-strapi/api-reference.md
@@ -1,104 +0,0 @@
----
-title: API Reference - Strapi Developer Documentation
-description: Discover our concise reference documentation containing all the information to work with your Strapi API
----
-
-# API reference
-
-- strapi
- - [.admin](#strapi-admin)
- - [.api](#strapi-api)
- - [.app](#strapi-app)
- - [.config](#strapi-config)
- - [.controllers](#strapi-controllers)
- - [.hook](#strapi-hook)
- - [.load()](#strapi-load)
- - [.log](#strapi-log)
- - [.middleware](#strapi-middleware)
- - [.models](#strapi-models)
- - [.plugins](#strapi-plugins)
- - [.query()](#strapi-query)
- - [.reload()](#strapi-reload)
- - [.router](#strapi-router)
- - [.server](#strapi-server)
- - [.services](#strapi-services)
- - [.start()](#strapi-start)
- - [.stop()](#strapi-stop)
-
-## strapi.admin
-
-This object contains the controllers, models, services and configurations contained in the `strapi-admin` package.
-
-## strapi.api
-
-This object contains APIs contained in the `./api` folder.
-And by using `strapi.api[:name]` you can access the controllers, services, the model definition and also the configurations of the `./api/:name` folder
-
-## strapi.app
-
-Returns the Koa instance.
-
-## strapi.config
-
-Returns an object that represents the configurations of the project. Every JavaScript or JSON file located in the `./config` folder will be parsed into the `strapi.config` object.
-
-## strapi.controllers
-
-Returns an object of the controllers which is available in the project. Every JavaScript file located in the `./api/**/controllers` folder will be parsed into the `strapi.controllers` object. Thanks to this object, you can access every controller's actions everywhere in the project.
-
-::: tip
-This object doesn't include the admin's controllers and plugin's controllers.
-:::
-
-## strapi.hook
-
-Returns an object of the hooks available in the project. Every folder that follows this pattern `strapi-*` and located in the `./node_modules` or `/hooks` folder will be mounted into the `strapi.hook` object.
-
-## strapi.load
-
-Returns a function that parses the configurations, hooks, middlewares and APIs of your app. It also loads the middlewares and hooks with the previously loaded configurations. This method could be useful to update references available through the `strapi` global variable without having to restart the server. However, without restarting the server, the new configurations will not be taken in account.
-
-## strapi.log
-
-Returns the Logger (Pino) instance.
-
-## strapi.middleware
-
-Returns an object of the middlewares available in the project. Every folder in the `./middlewares` folder will be also mounted into the `strapi.middleware` object.
-
-## strapi.models
-
-Returns an object of models available in the project. Every JavaScript or JSON file located in the `./api/**/models` folders will be parsed into the `strapi.models` object. Also every `strapi.models.**` object is merged with the model's instance returned by the ORM (Mongoose, Bookshelf). It allows to call the ORM methods through the `strapi.models.**` object (ex: `strapi.models.users.find()`).
-
-## strapi.plugins
-
-Returns an object of plugins available within the project. Each plugin object contains the associated controllers, models, services and configurations.
-
-## strapi.query
-
-This utility function allows to bind models with query functions specific to each ORM (e.g: `mongoose` or `bookshelf`).
-For more details, see the [Queries section](/developer-docs/latest/development/backend-customization.md#queries).
-
-## strapi.reload
-
-Returns a function that reloads the entire app (with downtime).
-
-## strapi.router
-
-Returns the Router (Joi router) instance.
-
-## strapi.server
-
-Returns the [`http.Server`](https://nodejs.org/api/http.md#http_class_http_server) instance.
-
-## strapi.services
-
-Returns an object of services available in the project. Every JavaScript file located in the `./api/**/services` folders will be parsed into the `strapi.services` object.
-
-## strapi.start
-
-Returns a function that loads the configurations, middlewares and hooks. Then, it executes the bootstrap file, freezes the global variable and listens the configured port.
-
-## strapi.stop
-
-Returns a function that shuts down the server and destroys the current connections.
diff --git a/docs/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md b/docs/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md
new file mode 100644
index 0000000000..5c800f4d1f
--- /dev/null
+++ b/docs/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md
@@ -0,0 +1,640 @@
+---
+title: Admin Panel API - Strapi Developer Docs
+description: Strapi's Admin Panel API for plugins allows a Strapi plugin to customize the front end part (i.e. the admin panel) of your application.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.html
+---
+
+# Admin Panel API for plugins
+
+A Strapi [plugin](/developer-docs/latest/plugins/plugins-intro.md) can interact with both the [back end](/developer-docs/latest/developer-resources/plugin-api-reference/server.md) or the front end of the Strapi app. The Admin Panel API is about the front end part, i.e. it allows a plugin to customize Strapi's [admin panel](/developer-docs/latest/development/admin-customization.md).
+
+The admin panel is a [React](https://reactjs.org/) application that can embed other React applications. These other React applications are the admin parts of each Strapi plugin.
+
+To create a plugin that interacts with the Admin Panel API:
+
+1. Create an [entry file](#entry-file).
+2. Within this file, declare and export a plugin interface that uses the [available actions](#available-actions).
+3. Require this plugin interface in a `strapi-admin.js` file at the root of the plugin package folder:
+
+ ```js
+ // path: [plugin-name]/strapi-admin.js
+
+ 'use strict';
+
+ module.exports = require('./admin/src').default;
+ ```
+
+## Entry file
+
+The entry file for the Admin Panel API is `[plugin-name]/admin/src/index.js`. This file exports the required interface, with the following functions available:
+
+| Function type | Available functions |
+| ------------------- | ------------------------------------------------------------------------ |
+| Lifecycle functions | - [register](#register)
- [bootstrap](#bootstrap)
|
+| Async function | [registerTrads](#registertrads) |
+
+## Lifecycle functions
+
+### register()
+
+**Type:** `Function`
+
+This function is called to load the plugin, even before the app is actually [bootstrapped](#bootstrap). It takes the running Strapi application as an argument (`app`).
+
+Within the register function, a plugin can:
+
+* [register itself](#registerplugin) so it's available to the admin panel
+* add a new link to the main navigation (see [Menu API](#menu-api))
+* [create a new settings section](#createsettingsection)
+* define [injection zones](#injection-zones-api)
+* [add reducers](#reducers-api)
+
+#### registerPlugin()
+
+**Type:** `Function`
+
+Registers the plugin to make it available in the admin panel.
+
+This function returns an object with the following parameters:
+
+| Parameter | Type | Description |
+| ---------------- | ------------------------ | -------------------------------------------------------------------------------------------------- |
+| `id` | String | Plugin id |
+| `name` | String | Plugin name |
+| `injectionZones` | Object | Declaration of available [injection zones](#injection-zones-api) |
+
+::: note
+Some parameters can be imported from the `package.json` file.
+:::
+
+**Example:**
+
+```js
+// path: my-plugin/admin/src/index.js
+
+// Auto-generated component
+import PluginIcon from './components/PluginIcon';
+import pluginId from './pluginId'
+
+export default {
+ register(app) {
+ app.addMenuLink({
+ to: `/plugins/${pluginId}`,
+ icon: PluginIcon,
+ intlLabel: {
+ id: `${pluginId}.plugin.name`,
+ defaultMessage: 'My plugin',
+ },
+ Component: async () => {
+ const component = await import(/* webpackChunkName: "my-plugin" */ './pages/App');
+
+ return component;
+ },
+ permissions: [], // array of permissions (object), allow a user to access a plugin depending on its permissions
+ });
+ app.registerPlugin({
+ id: pluginId,
+ name,
+ });
+ },
+};
+```
+
+### bootstrap()
+
+**Type**: `Function`
+
+Exposes the bootstrap function, executed after all the plugins are [registered](#register).
+
+Within the bootstrap function, a plugin can:
+
+* extend another plugin, using `getPlugin('plugin-name')`,
+* register hooks (see [Hooks API](#hooks-api))
+* [add links to a settings section](#settings-api)
+
+**Example:**
+
+```js
+module.exports = () => {
+ return {
+ //...
+ bootstrap(app) {
+ // execute some bootstrap code
+ app
+ .getPlugin('content-manager')
+ .injectContentManagerComponent('editView', 'right-links', { name: 'my-compo', Component: () => 'my-compo' })
+ },
+ };
+};
+```
+
+## Async function
+
+While [`register()`](#register) and [`bootstrap()`](#bootstrap) are lifecycle functions, `registerTrads()` is an async function.
+
+### registerTrads()
+
+**Type**: `Function`
+
+To reduce the build size, the admin panel is only shipped with 2 locales by default (`en` and `fr`). The `registerTrads()` function is used to register a plugin's translations files and to create separate chunks for the application translations. It does not need to be modified.
+
+::: details Example: Register a plugin's translation files
+
+```jsx
+export default {
+ async registerTrads({ locales }) {
+ const importedTrads = await Promise.all(
+ locales.map(locale => {
+ return import(
+ /* webpackChunkName: "[pluginId]-[request]" */ `./translations/${locale}.json`
+ )
+ .then(({ default: data }) => {
+ return {
+ data: prefixPluginTranslations(data, pluginId),
+ locale,
+ };
+ })
+ .catch(() => {
+ return {
+ data: {},
+ locale,
+ };
+ });
+ })
+ );
+
+ return Promise.resolve(importedTrads);
+ },
+};
+```
+
+:::
+
+## Available actions
+
+The Admin Panel API allows a plugin to take advantage of several small APIs to perform actions. Use this table as a reference:
+
+| Action | API to use | Function to use | Related lifecycle function |
+| ---------------------------------------- | --------------------------------------- | ------------------------------------------------- | --------------------------- |
+| Add a new link to the main navigation | [Menu API](#menu-api) | [`addMenuLink()`](#menu-api) | [`register()`](#register) |
+| Create a new settings section | [Settings API](#settings-api) | [`createSettingSection()`](#createsettingsection) | [`register()`](#register) |
+| Declare an injection zone | [Injection Zones API](#injection-zones-api) | [`registerPlugin()`](#registerplugin) | [`register()`](#register) |
+| Add a reducer | [Reducers API](#reducers-api) | [`addReducers()`](#reducers-api) | [`register()`](#register) |
+| Create a hook | [Hooks API](#hooks-api) | [`createHook()`](#hooks-api) | [`register()`](#register) |
+| Add a single link to a settings section | [Settings API](#settings-api) | [`addSettingsLink()`](#addsettingslink) | [`bootstrap()`](#bootstrap) |
+| Add multiple links to a settings section | [Settings API](#settings-api) | [`addSettingsLinks()`](#addsettingslinks) | [`bootstrap()`](#bootstrap) |
+| Inject a Component in an injection zone | [Injection Zones API](#injection-zones-api) | [`injectComponent()`](#injection-zones-api) | [`bootstrap()`](#register) |
+| Register a hook | [Hooks API](#hooks-api) | [`registerHook()`](#hooks-api) | [`bootstrap()`](#bootstrap) |
+
+::: tip
+The admin panel supports dotenv variables.
+
+All variables defined in a `.env` file and prefixed by `STRAPI_ADMIN_` are available while customizing the admin panel through `process.env`.
+:::
+
+### Menu API
+
+The Menu API allows a plugin to add a new link to the main navigation through the `addMenuLink()` function with the following parameters:
+
+| Parameter | Type | Description |
+| ------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `to` | String | Path the link should point to |
+| `icon` | React Component | Icon to display in the main navigation |
+| `intlLabel` | Object | Label for the link, following the [React Int'l](https://formatjs.io/docs/react-intl) convention, with:- `id`: id used to insert the localized label
- `defaultMessage`: default label for the link
|
+| `Component` | Async function | Returns a dynamic import of the plugin entry point |
+| `permissions` | Array of Objects | Permissions declared in the `permissions.js` file of the plugin |
+
+:::note
+`intlLabel.id` are ids used in translation files (`[plugin-name]/admin/src/translations/[language].json`)
+:::
+
+**Example:**
+
+```jsx
+// path: my-plugin/admin/src/index.js
+import PluginIcon from './components/PluginIcon';
+
+export default {
+ register(app) {
+ app.addMenuLink({
+ to: '/plugins/my-plugin',
+ icon: PluginIcon,
+ intlLabel: {
+ id: 'my-plugin.plugin.name',
+ defaultMessage: 'My plugin',
+ },
+ Component: () => 'My plugin',
+ permissions: [], // permissions to apply to the link
+ });
+ app.registerPlugin({ ... });
+ },
+ bootstrap() {},
+};
+```
+
+### Settings API
+
+The Settings API allows:
+
+* [creating a new setting section](#createsettingsection)
+* adding [a single link](#addsettingslink) or [multiple links at once](#addsettingslinks) to existing settings sections
+
+::: note
+Adding a new section happens in the [register](#register) lifecycle while adding links happens during the [bootstrap](#bootstrap) lifecycle.
+:::
+
+All functions accept links as objects with the following parameters:
+
+| Parameter | Type | Description |
+| ------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `id` | String | React id |
+| `to` | String | Path the link should point to |
+| `intlLabel` | Object | Label for the link, following the [React Int'l](https://formatjs.io/docs/react-intl) convention, with:- `id`: id used to insert the localized label
- `defaultMessage`: default label for the link
|
+| `Component` | Async function | Returns a dynamic import of the plugin entry point |
+| `permissions` | Array of Objects | Permissions declared in the `permissions.js` file of the plugin |
+
+#### createSettingSection()
+
+**Type**: `Function`
+
+Create a new settings section.
+
+The function takes 2 arguments:
+
+| Argument | Type | Description |
+| --------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| first argument | Object | Section label:- `id` (String): section id
- `intlLabel` (Object): localized label for the section, following the [React Int'l](https://formatjs.io/docs/react-intl) convention, with:
- `id`: id used to insert the localized label
- `defaultMessage`: default label for the section
|
+| second argument | Array of Objects | Links included in the section |
+
+:::note
+`intlLabel.id` are ids used in translation files (`[plugin-name]/admin/src/translations/[language].json`)
+:::
+
+**Example:**
+
+```jsx
+// path: my-plugin/admin/src/index.js
+
+const myComponent = async () => {
+ const component = await import(
+ /* webpackChunkName: "users-providers-settings-page" */ './pages/Providers'
+ );
+
+ return component;
+};
+
+export default {
+ register(app) {
+ app.createSettingSection(
+ { id: String, intlLabel: { id: String, defaultMessage: String }, // Section to create
+ [ // links
+ {
+ intLabel: { id: String, defaultMessage: String },
+ id: String,
+ to: String,
+ Component: myComponent,
+ permissions: Object[]
+ ]
+ }
+}
+```
+
+#### addSettingsLink()
+
+**Type**: `Function`
+
+Add a unique link to an existing settings section.
+
+**Example:**
+
+```jsx
+// path: my-plugin/admin/src/index.js
+
+const myComponent = async () => {
+ const component = await import(
+ /* webpackChunkName: "users-providers-settings-page" */ './pages/Providers'
+ );
+
+ return component;
+};
+
+export default {
+ bootstrap(app) {
+ // Adding a single link
+ app.addSettingsLink(
+ 'global', // id of the section to add the link to
+ {
+ intLabel: { id: String, defaultMessage: String },
+ id: String,
+ to: String,
+ Component: myComponent,
+ permissions: Object[]
+ }
+ )
+ }
+}
+```
+
+#### addSettingsLinks()
+
+**Type**: `Function`
+
+Add multiple links to an existing settings section.
+
+**Example:**
+
+```jsx
+// path: my-plugin/admin/src/index.js
+
+const myComponent = async () => {
+ const component = await import(
+ /* webpackChunkName: "users-providers-settings-page" */ './pages/Providers'
+ );
+
+ return component;
+};
+
+export default {
+ bootstrap(app) {
+ // Adding several links at once
+ app.addSettingsLinks(
+ 'global', // id of the section to addd the link in
+ [{
+ intLabel: { id: String, defaultMessage: String },
+ id: String,
+ to: String,
+ Component: myComponent,
+ permissions: Object[]
+ }]
+ )
+ }
+}
+```
+
+### Injection Zones API
+
+Injection zones refer to areas of a view's layout where a plugin allows another to inject a custom React component (e.g. a UI element like a button).
+
+Plugins can use:
+
+* Strapi's [predefined injection zones](#using-predefined-injection-zones) for the Content Manager,
+* or custom injection zones, created by a plugin
+
+::: note
+Injection zones are defined in the [register()](#register) lifecycle but components are injected in the [bootstrap()](#bootstrap) lifecycle.
+:::
+
+#### Using predefined injection zones
+
+Strapi admin panel comes with predefined injection zones so components can be added to the UI of the [Content Manager](/user-docs/latest/content-manager/introduction-to-content-manager.md):
+
+
+
+| View | Injection zone name & Location |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| List view | - `actions`: sits between Filters and the cogs icon
- `deleteModalAdditionalInfos()`: sits at the bottom of the modal displayed when deleting items
|
+| Edit view | - `informations`: sits at the top right of the edit view
- `right-links`: sits between "Configure the view" and "Edit" buttons
|
+
+#### Creating a custom injection zone
+
+To create a custom injection zone, declare it as a `` React component with an `area` prop that takes a string with the following naming convention: `plugin-name.viewName.injectionZoneName`.
+
+#### Injecting components
+
+A plugin has 2 different ways of injecting a component:
+
+* to inject a component from a plugin into another plugin's injection zones, use the `injectComponent()` function
+* to specifically inject a component into one of the Content Manager's [predefined injection zones](#using-predefined-injection-zones), use the `injectContentManagerComponent()` function instead
+
+::: details Example: Inject a component in the informations box of the Edit View of the Content Manager:
+
+```jsx
+// path: my-plugin/admin/src/index.js
+
+export default {
+ bootstrap(app) {
+ app.injectContentManagerComponent('editView', 'informations', {
+ name: 'my-plugin-my-compo',
+ Component: () => 'my-compo',
+ });
+}
+```
+:::
+
+::: details Example: Creating a new injection zone and injecting it from a plugin to another one:
+
+```jsx
+// Use the injection zone in a view
+// path: my-plugin/admin/src/injectionZones.js
+
+import { InjectionZone } from '@strapi/helper-plugin';
+
+const HomePage = () => {
+ return (
+
+ This is the homepage
+
+
+ );
+};
+
+// Declare this injection zone in the register lifecycle of the plugin
+// path: my-plugin/admin/src/index.js
+
+export default {
+ register() {
+ app.registerPlugin({
+ // ...
+ injectionZones: {
+ homePage: {
+ right: []
+ }
+ }
+ });
+ },
+}
+
+// Inject the component from a plugin in another plugin
+// path: my-other-plugin/admin/src/index.js
+
+export default {
+ register() {
+ // ...
+ },
+ bootstrap(app) {
+ app.getPlugin('my-plugin').injectComponent('homePage', 'right', {
+ name: 'my-other-plugin-component',
+ Component: () => 'This component is injected',
+ });
+ }
+};
+```
+
+:::
+
+#### Accessing data with the `useCMEditViewDataManager` React hook
+
+Once an injection zone is defined, the component to be injected in the Content Manager can have access to all the data of the Edit View through the `useCMEditViewDataManager` React hook.
+
+::: details Example of a basic component using the 'useCMEditViewDataManager' hook
+
+```js
+import { useCMEditViewDataManager } from '@strapi/helper-plugin';
+
+const MyCompo = () => {
+ const {
+ createActionAllowedFields: [], // Array of fields that the user is allowed to edit
+ formErrors: {}, // Object errors
+ readActionAllowedFields: [], // Array of field that the user is allowed to edit
+ slug: 'api::address.address', // Slug of the content type
+ updateActionAllowedFields: [],
+ allLayoutData: {
+ components: {}, // components layout
+ contentType: {}, // content type layout
+ },
+ initialData: {},
+ isCreatingEntry: true,
+ isSingleType: true,
+ status: 'resolved',
+ layout: {}, // Current content type layout
+ hasDraftAndPublish: true,
+ modifiedData: {},
+ onPublish: () => {},
+ onUnpublish: () => {},
+ addComponentToDynamicZone: () => {},
+ addNonRepeatableComponentToField: () => {},
+ addRelation: () => {},
+ addRepeatableComponentToField: () => {},
+ moveComponentDown: () => {},
+ moveComponentField: () => {},
+ moveComponentUp: () => {},
+ moveRelation: () => {},
+ onChange: () => {},
+ onRemoveRelation: () => {},
+ removeComponentFromDynamicZone: () => {},
+ removeComponentFromField: () => {},
+ removeRepeatableField: () => {},
+ } = useCMEditViewDataManager()
+
+ return null
+}
+```
+
+:::
+
+### Reducers API
+
+Reducers are [Redux](https://redux.js.org/) reducers that can be used to share state between components. Reducers can be useful when:
+
+* Large amounts of application state are needed in many places in the application.
+* The application state is updated frequently.
+* The logic to update that state may be complex.
+
+A reducer is declared as an object with this syntax:
+
+`['pluginId_reducerName']: function() {}`
+
+Reducers can be added to a plugin interface with the `addReducers()` function during the [`register`](#register) lifecycle.
+
+**Example:**
+
+```js
+// path: my-plugin/admin/src/index.js
+import { exampleReducer } from './reducers'
+
+const reducers = {
+ [`${pluginId}_exampleReducer`]: exampleReducer
+}
+
+export default {
+ register(app) {
+ app.addReducers(reducers)
+ },
+ bootstrap() {},
+};
+
+
+```
+
+### Hooks API
+
+The Hooks API allows a plugin to create and register hooks, i.e. places in the application where plugins can add personalized behavior.
+
+Hooks should be registered during the [bootstrap](#bootstrap) lifecycle of a plugin.
+
+Hooks can then be run in series, in waterfall or in parallel:
+
+* `runHookSeries` returns an array corresponding to the result of each function executed, ordered
+* `runHookParallel` returns an array corresponding to the result of the promise resolved by the function executed, ordered
+* `runHookWaterfall` returns a single value corresponding to all the transformations applied by the different functions starting with the initial value `args`.
+
+:::details Example: Create a hook in a plugin and use it in another plugin
+
+```jsx
+// path: my-plugin/admin/src/index.js
+// Create a hook in a plugin
+export default {
+ register(app) {
+ app.createHook('My-PLUGIN/MY_HOOK');
+ }
+}
+
+
+// path: my-other-plugin/admin/src/index.js
+// Use the hook in another plugin
+export default {
+ bootstrap(app) {
+ app.registerHook('My-PLUGIN/MY_HOOK', (...args) => {
+ console.log(args)
+
+ // important: return the mutated data
+ return args
+ });
+
+ app.registerPlugin({...})
+ }
+}
+```
+
+:::
+
+#### Predefined hook
+
+Strapi includes a predefined `cm/inject-column-in-table` hook that can be used to add or mutate a column of the List View of the [Content Manager](/user-docs/latest/content-manager/introduction-to-content-manager.md).
+
+::: details Example: 'cm/inject-column-in-table' hook, as used by the Internationalization plugin to add the 'Content available in' column
+
+```jsx
+// ./plugins/my-plugin/admin/src/index.js
+
+export default {
+ bootstrap(app) {
+ app.registerHook('cm/inject-column-in-table', ({ displayedHeaders, layout }) => {
+ const isFieldLocalized = get(layout, 'contentType.pluginOptions.i18n.localized', false);
+
+ if (!isFieldLocalized) {
+ return displayedHeaders;
+ }
+
+ return [
+ ...displayedHeaders,
+ {
+ key: '__locale_key__', // Needed for the table
+ fieldSchema: { type: 'string' }, // Schema of the attribute
+ metadatas: {
+ label: 'Content available in', // Label of the header,
+ sortable: false|true // Define in the column is sortable
+ }, // Metadatas for the label
+ // Name of the key in the data we will display
+ name: 'locales',
+ // Custom renderer
+ cellFormatter: props => Object.keys(props).map(key =>
key
)
- [register](#register)
- [bootstrap](#bootstrap)
- [destroy](#destroy)
|
+| Configuration | [config](#configuration) object |
+| Backend customizations | - [contentTypes](#content-types)
- [routes](#routes)
- [controllers](#controllers)
- [services](#services)
- [policies](#policies)
- [middlewares](#middlewares)
|
+
+## Lifecycle functions
+
+### register()
+
+This function is called to load the plugin, even before the application is actually [bootstrapped](#bootstrap), in order to register [permissions](/developer-docs/latest/plugins/users-permissions.md) or database migrations.
+
+**Type**: `Function`
+
+**Example:**
+
+```js
+// path ./strapi-server.js
+
+module.exports = () => ({
+ register({ strapi }) {
+ // execute some register code
+ },
+});
+```
+
+### bootstrap()
+
+The [bootstrap](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md#bootstrap) function is called right after the plugin has [registered](#register).
+
+**Type**: `Function`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+module.exports = () => ({
+ bootstrap({ strapi }) {
+ // execute some bootstrap code
+ },
+});
+```
+
+### destroy()
+
+The [destroy](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md#destroy) lifecycle function is called to cleanup the plugin (close connections, remove listeners…) when the Strapi instance is destroyed.
+
+**Type**: `Function`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+module.exports = () => ({
+ destroy({ strapi }) {
+ // execute some destroy code
+ },
+});
+```
+
+## Configuration
+
+`config` stores the default plugin configuration.
+
+**Type**: `Object`
+
+| Parameter | Type | Description |
+| ----------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `default` | Object, or Function that returns an Object | Default plugin configuration, merged with the user configuration |
+| `validator` | Function | - Checks if the results of merging the default plugin configuration with the user configuration is valid
- Throws errors when the resulting configuration is invalid
|
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const config = require('./config');
+
+module.exports = () => ({
+ config: {
+ default: ({ env }) => ({ optionA: true }),
+ validator: (config) => {
+ if (typeof config.optionA !== 'boolean') {
+ throw new Error('optionA has to be a boolean');
+ }
+ },
+ },
+});
+```
+
+## Backend customization
+
+### Content-Types
+
+An object with the [Content-Types](/developer-docs/latest/development/backend-customization/models.md) the plugin provides.
+
+**Type**: `Object`
+
+:::note
+Content-Types keys in the `contentTypes` object should re-use the `singularName` defined in the [`info`](/developer-docs/latest/development/backend-customization/models.md#model-information) key of the schema.
+:::
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const contentTypes = require('./content-types');
+
+module.exports = () => ({
+ contentTypes,
+});
+```
+
+```js
+// path: ./content-types/index.js
+
+const contentTypeA = require('./content-type-a');
+const contentTypeB = require('./content-type-b');
+
+module.exports = [
+ 'content-type-a': contentTypeA, // should re-use the singularName of the content-type
+ 'content-type-b': contentTypeB,
+];
+```
+
+```js
+// path: ./content-types/content-type-a.js
+
+module.exports = {
+ info: {
+ tableName: 'content-type',
+ singularName: 'content-type-a', // kebab-case mandatory
+ pluralName: 'content-type-as', // kebab-case mandatory
+ displayName: 'Content Type A',
+ description: 'A regular content type'
+ kind: 'collectionType'
+ },
+ options: {
+ draftAndPublish: true,
+ },
+ pluginOptions: {
+ 'content-manager': {
+ visible: false
+ },
+ 'content-type-builder': {
+ visible: false
+ }
+ },
+ attributes: {
+ name: {
+ type: 'string',
+ min: 1,
+ max: 50,
+ configurable: false
+ },
+ }
+};
+```
+
+### Routes
+
+An array of [routes](/developer-docs/latest/development/backend-customization/routes.md) configuration.
+
+**Type**: `Object[]`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const routes = require('./routes');
+
+module.exports = () => ({
+ routes,
+ type: 'content-api' // can also be 'admin-api' depending on the type of route
+});
+```
+
+```js
+// path: ./routes/index.js
+
+module.exports = [
+ {
+ method: 'GET',
+ path: '/model',
+ handler: 'controllerName.action',
+ config: {
+ policies: ['policyName'],
+ },
+ },
+];
+```
+
+### Controllers
+
+An object with the [controllers](/developer-docs/latest/development/backend-customization/controllers.md) the plugin provides.
+
+**Type**: `Object`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const controllers = require('./controllers');
+
+module.exports = () => ({
+ controllers,
+});
+```
+
+```js
+// path: ./controllers/index.js
+
+const controllerA = require('./controller-a');
+const controllerB = require('./controller-b');
+
+module.exports = {
+ controllerA,
+ controllerB,
+};
+```
+
+```js
+// path: ./controllers/controller-a.js
+
+module.exports = {
+ doSomething(ctx) {
+ ctx.body = { message: 'HelloWorld' };
+ },
+};
+```
+
+### Services
+
+An object with the [services](/developer-docs/latest/development/backend-customization/services.md) the plugin provides.
+
+Services should be functions taking `strapi` as a parameter.
+
+**Type**: `Object`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const services = require('./services');
+
+module.exports = () => ({
+ services,
+});
+```
+
+```js
+// path: ./services/index.js
+
+const serviceA = require('./service-a');
+const serviceB = require('./service-b');
+
+module.exports = {
+ serviceA,
+ serviceB,
+};
+```
+
+```js
+// path: ./services/service-a.js
+
+module.exports = ({ strapi }) => ({
+ someFunction() {
+ return [1, 2, 3];
+ },
+});
+```
+
+### Policies
+
+An object with the [policies](/developer-docs/latest/development/backend-customization/policies.md) the plugin provides.
+
+**Type**: `Object`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const policies = require('./policies');
+
+module.exports = () => ({
+ policies,
+});
+```
+
+```js
+// path: ./policies/index.js
+
+const policyA = require('./policy-a');
+const policyB = require('./policy-b');
+
+module.exports = {
+ policyA,
+ policyB,
+};
+```
+
+```js
+// path: ./policies/policy-a.js
+
+module.exports = (policyContext, config, { strapi }) => {
+ if (ctx.state.user && ctx.state.user.isActive) {
+ return true;
+ }
+
+ return false;
+ },
+};
+```
+
+### Middlewares
+
+An object with the [middlewares](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md) the plugin provides.
+
+**Type**: `Object`
+
+**Example:**
+
+```js
+// path: ./strapi-server.js
+
+const middlewares = require('./middlewares');
+module.exports = () => ({
+ middlewares,
+});
+```
+
+```js
+// path: ./middlewares/index.js
+
+const middlewareA = require('./middleware-a');
+const middlewareB = require('./middleware-b');
+
+module.exports = {
+ middlewareA,
+ middlewareB,
+};
+```
+
+```js
+// path: ./middlewares/middleware-a.js
+
+module.exports = (options, { strapi }) => {
+ return async (ctx, next) => {
+ const start = Date.now();
+ await next();
+ const delta = Math.ceil(Date.now() - start);
+
+ strapi.log.http(`${ctx.method} ${ctx.url} (${delta} ms) ${ctx.status}`);
+ };
+};
+```
+
+## Usage
+
+Once a plugin is exported and loaded into Strapi, its features are accessible in the code through getters. The Strapi instance (`strapi`) exposes top-level getters and global getters.
+
+While top-level getters imply chaining functions, global getters are syntactic sugar that allow direct access using a feature's uid:
+
+```js
+// Access an API or a plugin controller using a top-level getter
+strapi.api('api-name').controller('controller-name')
+strapi.plugin('plugin-name').controller('controller-name')
+
+// Access an API or a plugin controller using a global getter
+strapi.controller('api::api-name.controller-name')
+strapi.controller('plugin::plugin-name.controller-name')
+```
+
+:::details Top-level getter syntax examples
+
+```js
+strapi.plugin('plugin-name').config
+strapi.plugin('plugin-name').routes
+strapi.plugin('plugin-name').controller('controller-name')
+strapi.plugin('plugin-name').service('service-name')
+strapi.plugin('plugin-name').contentType('content-type-name')
+strapi.plugin('plugin-name').policy('policy-name')
+strapi.plugin('plugin-name').middleware('middleware-name')
+```
+
+:::
+
+:::details Global getter syntax examples
+
+```js
+strapi.controller('plugin::plugin-name.controller-name');
+strapi.service('plugin::plugin-name.service-name');
+strapi.contentType('plugin::plugin-name.content-type-name');
+strapi.policy('plugin::plugin-name.policy-name');
+strapi.middleware('plugin::plugin-name.middleware-name');
+```
+
+:::
diff --git a/docs/developer-docs/latest/development/admin-customization.md b/docs/developer-docs/latest/development/admin-customization.md
index 7e4e915def..4f4e991175 100644
--- a/docs/developer-docs/latest/development/admin-customization.md
+++ b/docs/developer-docs/latest/development/admin-customization.md
@@ -1,347 +1,401 @@
---
-title: Admin panel customization - Strapi Developer Documentation
+title: Admin panel customization - Strapi Developer Docs
description: The administration panel of Strapi can be customized according to your needs, so you can make it reflect your identity.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/admin-customization.html
---
# Admin panel customization
-## Admin extension
+The admin panel is a `node_module` that is similar to a plugin, except that it encapsulates all the installed plugins of a Strapi application. Some of its aspects can be [customized](#customization-options), and plugins can also [extend](#extension) it.
-The admin panel is a `node_module` that is similar to a [plugin](/developer-docs/latest/development/plugin-customization.md), with the slight difference that it encapsulates all the installed plugins of your application.
-
-To extend this package you will have to create an `admin` folder at the root of your application.
-
-In this folder you will be able to override admin files and functions.
+To toggle hot reloading and get errors in the console while developing, start Strapi in front-end development mode by running the application with the `--watch-admin` flag:
+```bash
+cd my-app # cd into the root directory of the Strapi application project
+strapi develop --watch-admin
+```
## Customization options
-The administration panel can be customized according to your needs, so you can make it reflect your identity.
+Customizing the admin panel is helpful to better reflect your brand identity or to modify some default Strapi behavior:
-::: warning
-To apply your changes you need to [rebuild](#build) your admin panel
-:::
+- The [access URL, host and port](#access-url) can be modified through the server configuration.
+- The [configuration object](#configuration-options) allows replacing the logos and favicon, defining locales and extending translations, extending the theme, and disabling some Strapi default behaviors like displaying video tutorials or notifications about new Strapi releases.
+- The [WYSIWYG editor](#wysiwyg-editor) can be replaced or customized.
+- The [forgotten password email](#forgotten-password-email) can be customized with a template and variables.
+- The [webpack configuration](#webpack-configuration) based on webpack 5 can also be extended for advanced customization
-### Change access URL
+### Access URL
-By default, the administration panel is exposed via [http://localhost:1337/admin](http://localhost:1337/admin). However, for security reasons, you can easily update this path. For more advanced settings please see the [server config](/developer-docs/latest/setup-deployment-guides/configurations.md#server) documentation.
+By default, the administration panel is exposed via [http://localhost:1337/admin](http://localhost:1337/admin). For security reasons, this path can be updated.
-**Path —** `./config/server.js`.
+**Example:**
+
+To make the admin panel accessible from `http://localhost:1337/dashboard`, use this in the [server configuration](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md) file:
```js
+//path: ./config/server.js
+
module.exports = ({ env }) => ({
host: env('HOST', '0.0.0.0'),
port: env.int('PORT', 1337),
- admin: {
- url: '/dashboard',
- },
+
});
+
+
+// path: ./config/admin.js
+
+module.exports = ({ env }) => ({
+ url: '/dashboard',
+})
```
-The panel will be available through [http://localhost:1337/dashboard](http://localhost:1337/dashboard) with the configuration above.
+:::strapi Advanced settings
+For more advanced settings please see the [admin panel configuration](/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md) documentation.
+:::
-### Development mode
+#### Host and port
-To enable the front-end development mode you need to start your application using the `--watch-admin` flag.
+By default, the front end development server runs on `localhost:8000` but this can be modified:
-```bash
-cd my-app
-strapi develop --watch-admin
-```
+```js
+// path: ./config/server.js
-With this option you can do the following:
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+});
-#### Customize the `strapi-admin` package
-All files added in `my-app/admin/src/` will either be replaced or added
+// path: ./config/admin.js
-**Example: Changing the available locales of your application**
+module.exports = ({ env }) => ({
+ host: 'my-host', // only used along with `strapi develop --watch-admin` command
+ port: 3000, // only used along with `strapi develop --watch-admin` command
+});
-```bash
-# Create both the admin and admin/src/translations folders
-cd my-app && mkdir -p admin/src/translations
-# Change the available locales of the administration panel
-touch admin/src/i18n.js
-# Change the import and exports of the translations files
-touch admin/src/translations/index.js
```
-**Path -** `my-app/admin/src/translations/index.js`
+### Configuration options
-```js
-import en from './en.json';
-import fr from './fr.json';
+The `config` object found at `./src/admin/app.js` stores the admin panel configuration.
-const trads = {
- en,
- fr,
-};
+Any file used by the `config` object (e.g. a custom logo) should be placed in the `./admin/extensions/` folder and imported inside `./src/admin/app.js`.
-export const languageNativeNames = {
- en: 'English',
- fr: 'Français',
-};
+The `config` object accepts the following parameters:
-export default trads;
-```
+| Parameter | Type | Description |
+| --------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `auth` | Object | Accepts a `logo` key to replace the default Strapi [logo](#logos) on login screen |
+| `head` | Object | Accepts a `favicon` key to replace the default Strapi [favicon](#favicon) |
+| `locales` | Array of Strings | Defines availables locales (see [updating locales](/developer-docs/latest/development/admin-customization.md#locales)) |
+| `translations` | Object | [Extends the translations](#extending-translations) |
+| `menu` | Object | Accepts the `logo` key to change the [logo](#logos) in the main navigation |
+| `theme` | Object | Overrides or [extends the theme](#theme-extension) |
+| `tutorial` | Boolean | Toggles [displaying the video tutorials](#tutorial-videos) |
+| `notifications` | Object | Accepts the `release` key (Boolean) to toggle [displaying notifications about new releases](#releases-notifications) |
-::: tip
-With this modification only English and French will be available in your admin
-:::
+::: details Example of a custom configuration for the admin panel:
-#### Customize a plugin
+```jsx
+// path: ./admin/src/app.js
-Similarly to the back-end override system, any file added in `my-app/extensions//admin/` will be copied and used instead of the original one (use with care).
+import AuthLogo from './extensions/my-logo.png';
+import MenuLogo from './extensions/logo.png';
+import favicon from './extensions/favicon.ico';
-**Example: Changing the current WYSIWYG**
+export default {
+ config: {
+ // Replace the Strapi logo in auth (login) views
+ auth: {
+ logo: AuthLogo,
+ },
+ // Replace the favicon
+ head: {
+ favicon: favicon,
+ },
+ // Add a new locale, other than 'en'
+ locales: ['fr', 'de'],
+ // Replace the Strapi logo in the main navigation
+ menu: {
+ logo: MenuLogo,
+ },
+ // Override or extend the theme
+ theme: {
+ colors: {
+ alternative100: '#f6ecfc',
+ alternative200: '#e0c1f4',
+ alternative500: '#ac73e6',
+ alternative600: '#9736e8',
+ alternative700: '#8312d1',
+ danger700: '#b72b1a'
+ },
+ },
+ // Extend the translations
+ translations: {
+ fr: {
+ 'Auth.form.email.label': 'test',
+ Users: 'Utilisateurs',
+ City: 'CITY (FRENCH)',
+ // Customize the label of the Content Manager table.
+ Id: 'ID french',
+ },
+ },
+ // Disable video tutorials
+ tutorials: false,
+ // Disable notifications about new Strapi releases
+ notifications: { release: false },
+ },
+
+ bootstrap() {},
+};
-```bash
-cd my-app/extensions
-# Create the content manager folder
-mkdir content-manager && cd content-manager
-# Create the admin folder
-mkdir -p admin/src
-# Create the components folder and the WysiwygWithErrors one
-cd admin/src && mkdir -p components/WysiwygWithErrors
-# Create the index.js so the original file is overridden
-touch components/WysiwygWithErrors/index.js
```
-**Path -** `my-app/extensions/content-manager/admin/src/components/WysiwygWithErrors/index.js`
+:::
-```js
-import React from 'react';
-import MyNewWYSIWYG from 'my-awesome-lib';
+#### Locales
-// This is a dummy example
-const WysiwygWithErrors = props => ;
+To update the list of available locales in the admin panel, use the `config.locales` array:
-export default WysiwygWithErrors;
-```
+```jsx
+// path: ./my-app/src/admin/app.js
-#### Styles
+module.exports = {
+ // Custom webpack config
+ webpack: (config, webpack) => {
+ // Note: we provide webpack above so you should not `require` it
+ // Perform customizations to webpack config
+ // Important: return the mutated config
+ return config;
+ },
-The AdminUI package source is located in `./node_modules/strapi-admin/admin/src/`.
+ // App customizations
+ app: config => {
+ config.locales = ['ru', 'zh'];
-For example, to change the top-left admin panel's color:
+ return config;
+ },
+};
+```
-1. create a copy of the
-- `./node_modules/strapi-admin/admin/src/components/LeftMenu/LeftMenuHeader` folder to
-- `./admin/src/components/LeftMenu/LeftMenuHeader` (create these folders if they don't exist)
+::: note NOTES
-```
-mkdir -p ./admin/src/components/LeftMenu/LeftMenuHeader
-cp ./node_modules/strapi-admin/admin/src/components/LeftMenu/LeftMenuHeader/Wrapper.js ./admin/src/components/LeftMenu/LeftMenuHeader/Wrapper.js
-```
+* The `en` locale cannot be removed from the build as it is both the fallback (i.e. if a translation is not found in a locale, the `en` will be used) and the default locale (i.e. used when a user opens the administration panel for the first time).
+* The full list of available locales is accessible on [Strapi's Github repo](https://github.com/strapi/strapi/blob/releases/v4/packages/plugins/i18n/server/constants/iso-locales.json).
+:::
-2. modify style within that copy (see also [sourcecode online](https://github.com/strapi/strapi/blob/master/packages/strapi-admin/admin/src/components/LeftMenu/LeftMenuHeader/Wrapper.js#L7)):
+##### Extending translations
+
+Translation key/value pairs are declared in `./translations/[language-name].json` files. These keys can be extended through the `config.translations` key:
-**Path:** `./admin/src/components/LeftMenu/LeftMenuHeader/Wrapper.js`
```js
- background-color: #007eff;
+// path: ./src/admin/app.js
+
+export default {
+ config: {
+ locales: ['fr'],
+ translations: {
+ fr: {
+ or: 'OR',
+ 'request.error.model.unknown': "This model doesn't exist",
+ skipToContent: 'Skip to content',
+ submit: 'Submit',
+ Totos: 'tata',
+ "content-type-builder.my-translation-key": "test"
+ },
+ },
+ },
+ bootstrap() {},
+};
```
-Thus, files in `admin/src/some/file/path` take precedence over `node_modules/strapi-admin/admin/src/file/path`.
+If more translations files should be added, place them in `/extensions/translations` folder.
-::: warning
-To apply your changes you need to [rebuild](#build) your admin panel
-:::
+#### Logos
-#### Logo
+The Strapi admin panel displays a logo in 2 different locations, represented by 2 different keys in the [admin panel configuration](#configuration-options):
-To change the top-left displayed admin panel's logo, add your custom image at `./admin/src/assets/images/logo-strapi.png`.
+| Location in the UI | Configuration key to update |
+| ---------------------- | --------------------------- |
+| On the login page | `config.auth.logo` |
+| In the main navigation | `config.menu.logo` |
-To change the login page's logo, add your custom image at `./admin/src/assets/images/logo_strapi.png`.
+To update the logos, put image files in the `./extensions` folder and update the corresponding keys.
-::: tip
-make sure the size of your image is the same as the existing one (434px x 120px).
-:::
+The size of the custom image should be the same as the default one (434px x 120px).
-#### Tutorial videos
+#### Favicon
-To disable the information box containing the tutorial videos, create a file at `./admin/src/config.js`
+To update the favicon, put a favicon file in the `./extensions` folder and update the `config.head.favicon` key in the [admin panel configuration](#configuration-options).
-Add the following configuration:
+#### Tutorial videos
-```js
-export const LOGIN_LOGO = null;
-export const SHOW_TUTORIALS = false;
-export const SETTINGS_BASE_URL = '/settings';
-export const STRAPI_UPDATE_NOTIF = true;
-```
+To disable the information box containing the tutorial videos, set the `config.tutorials` key to `false`.
-#### Changing the host and port
+#### Releases notifications
-By default, the front-development server runs on `localhost:8000`. However, you can change this setting by updating the following configuration:
+To disable notifications about new Strapi releases, set the `config.notifications.release` key to `false`.
-**Path —** `./config/server.js`.
+#### Theme extension
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- admin: {
- host: 'my-host', // only used along with `strapi develop --watch-admin` command
- port: 3000, // only used along with `strapi develop --watch-admin` command
- },
-});
-```
+
-### Build
+To extend the theme, use the `config.theme` key.
-To build the administration, run the following command from the root directory of your project.
+::: strapi Strapi Parts! theme
+The default [Strapi Parts! theme](https://github.com/strapi/parts/tree/master/packages/strapi-parts/src/themes) defines various theme-related keys (shadows, colors…) that can be updated through the `config.theme` key in `./admin/src/app.js`.
+:::
-:::: tabs
+
-::: tab yarn
+### WYSIWYG editor
-```
-yarn build
-```
+To change the current WYSIWYG, you can either install a third-party plugin, or take advantage of the bootstrap lifecycle (see [Admin Panel API](/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md#bootstrap)).
-:::
+### 'Forgotten password' email
-::: tab npm
+To customize the 'Forgotten password' email, provide your own template (formatted as a [lodash template](https://lodash.com/docs/4.17.15#template)).
-```
-npm run build
-```
+The template will be compiled with the following variables: `url`, `user.email`, `user.username`, `user.firstname`, `user.lastname`.
-:::
+**Example**:
+
+```js
+// path: ./config/admin.js
-::: tab strapi
+const forgotPasswordTemplate = require('./email-templates/forgot-password');
-```
-strapi build
+module.exports = ({ env }) => ({
+ // ...
+ forgotPassword: {
+ from: 'support@mywebsite.fr',
+ replyTo: 'support@mywebsite.fr',
+ emailTemplate: forgotPasswordTemplate,
+ },
+ },
+ // ...
+});
```
-:::
+```js
+// path: ./config/email-templates/forgot-password.js
+
+const subject = `Reset password`;
+
+const html = `Hi <%= user.firstname %>
+Sorry you lost your password. You can click here to reset it: <%= url %>
`;
-::::
+const text = `Hi <%= user.firstname %>
+Sorry you lost your password. You can click here to reset it: <%= url %>`;
-This will replace the folder's content located at `./build`. Visit [http://localhost:1337/admin](http://localhost:1337/admin) to make sure your updates have been taken into account.
+module.exports = {
+ subject,
+ text,
+ html,
+};
+```
-## Custom Webpack Config
+### Webpack configuration
-In order to extend the usage of webpack, you can define a function that extends its config inside `admin/admin.config.js`, like so:
+In order to extend the usage of webpack v5, define a function that extends its configuration inside `./admin/webpack.config.js`:
```js
module.exports = {
webpack: (config, webpack) => {
// Note: we provide webpack above so you should not `require` it
+
// Perform customizations to webpack config
- // Important: return the modified config
config.plugins.push(new webpack.IgnorePlugin(/\/__tests__\//));
+ // Important: return the modified config
return config;
},
};
```
+::: note
+Only `./admin/app.js` and the files under the `./admin/extensions` folder are being watched by the webpack dev server.
+:::
-## Deployment
+## Extension
-The administration is nothing more than a React front-end application calling an API. The front-end and the back-end are independent and can be deployed on different servers which brings us to different scenarios:
+There are 2 use cases to extend the admin panel:
-1. Deploy the entire project on the same server.
-2. Deploy the administration panel on another server (AWS S3, Azure, etc) than the API.
+- A plugin developer wants to develop a Strapi plugin that extends the admin panel everytime it's installed in any Strapi application. This can be done by taking advantage of the [Admin Panel API](/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md).
-Let's dive into the build configurations for each case.
+- A Strapi user only needs to extend a specific instance of a Strapi application. This can be done by directly updating the `./src/admin/app.js` file, which can import any file located in `./src/admin/extensions`.
-### Deploy the entire project on the same server.
+## Deployment
-You don't need to touch anything in your configuration file. This is the default behavior and the build configuration will be automatically set. The server will start on the defined port and the administration panel will be accessible through `http://yourdomain.com:1337/dashboard`.
+The administration is a React front-end application calling an API. The front end and the back end are independent and can be deployed on different servers, which brings us to different scenarios:
-You might want to change the path to access the administration panel. Here is the required configuration to change the path:
+* Deploy the entire project on the same server.
+* Deploy the administration panel on a server (AWS S3, Azure, etc) different from the API server.
-**Path —** `./config/server.js`.
+Build configurations differ for each case.
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- admin: {
- url: '/dashboard', // We change the path to access to the admin (highly recommended for security reasons).
- },
-});
-```
-
-::: warning
-To apply your changes you need to [rebuild](#build) your admin panel
-:::
+Before deployment, the admin panel needs to be built, by running the following command from the project's root directory:
-### Deploy the administration panel on another server (AWS S3, Azure, etc) than the API.
+
-It's very common to deploy the front-end and the back-end on different servers. Here is the required configuration to handle this case:
+
+```sh
+npm run build
+```
+
-**Path —** `./config/server.js`.
+
+```sh
+yarn build
+```
+
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'http://yourbackend.com',
- admin: {
- url: '/', // Note: The administration will be accessible from the root of the domain (ex: http://yourfrontend.com/)
- serveAdminPanel: false, // http://yourbackend.com will not serve any static admin files
- },
-});
+
+```sh
+strapi build
```
+
-After running `yarn build` with this configuration, the folder `build` will be created/overwritten. You can then use this folder to serve it from another server with the domain of your choice (ex: `http://yourfrontend.com`).
+
-The administration URL will then be `http://yourfrontend.com` and every request from the panel will hit the backend at `http://yourbackend.com`.
+This will replace the folder's content located at `./build`. Visit [http://localhost:1337/admin](http://localhost:1337/admin) to make sure customizations have been taken into account.
-::: tip NOTE
-If you add a path to the `url` option, it won't prefix your app. To do so, you need to also use a proxy server like Nginx. More [here](/developer-docs/latest/setup-deployment-guides/deployment.md#optional-software-guides).
-:::
+### Same server
+Deploying the admin panel and the API on the same server is the default behavior. The build configuration will be automatically set. The server will start on the defined port and the administration panel will be accessible through `http://yourdomain.com:1337/admin`.
-## Forgot Password Email
+:::tip
+You might want to [change the path to access the administration panel](#access-url).
+:::
-### Customize forgot password email
+### Different servers
-You may want to customize the forgot password email.
-You can do it by providing your own template (formatted as a [lodash template](https://lodash.com/docs/4.17.15#template)).
+To deploy the front end and the back end on different servers, use the following configuration:
-The template will be compiled with the following variables: `url`, `user.email`, `user.username`, `user.firstname`, `user.lastname`.
+```js
+// path: ./config/server.js
-### Example
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+ url: 'http://yourbackend.com',
+});
-**Path -** `./config/servers.js`
-```js
-const forgotPasswordTemplate = require('./email-templates/forgot-password');
+// path: ./config/admin.js
module.exports = ({ env }) => ({
- // ...
- admin: {
- // ...
- forgotPassword: {
- from: 'support@mywebsite.fr',
- replyTo: 'support@mywebsite.fr',
- emailTemplate: forgotPasswordTemplate,
- },
- // ...
- },
- // ...
+ url: '/', // Note: The administration will be accessible from the root of the domain (ex: http://yourfrontend.com/)
+ serveAdminPanel: false, // http://yourbackend.com will not serve any static admin files
});
```
-**Path -** `./config/email-templates/forgot-password.js`
-
-```js
-const subject = `Reset password`;
-
-const html = `Hi <%= user.firstname %>
-Sorry you lost your password. You can click here to reset it: <%= url %>
`;
+After running `yarn build` with this configuration, the `build` folder will be created/overwritten. Use this folder to serve it from another server with the domain of your choice (e.g. `http://yourfrontend.com`).
-const text = `Hi <%= user.firstname %>
-Sorry you lost your password. You can click here to reset it: <%= url %>`;
+The administration URL will then be `http://yourfrontend.com` and every request from the panel will hit the backend at `http://yourbackend.com`.
-module.exports = {
- subject,
- text,
- html,
-};
-```
+:::note
+If you add a path to the `url` option, it won't prefix your app. To do so, use a proxy server like Nginx (see [optional software guides](/developer-docs/latest/setup-deployment-guides/deployment.md#optional-software-guides)).
+:::
diff --git a/docs/developer-docs/latest/development/backend-customization.md b/docs/developer-docs/latest/development/backend-customization.md
index 3cf8458832..c9a7a0d95c 100644
--- a/docs/developer-docs/latest/development/backend-customization.md
+++ b/docs/developer-docs/latest/development/backend-customization.md
@@ -1,3073 +1,33 @@
---
-title: Backend customization - Strapi Developer Documentation
-description: The backend of Strapi can be customized according to your needs, so you can create your own backend behavior.
+title: Back-end customization - Strapi Developer Docs
+description: All elements of Strapi's back end, like routes, policies, middlewares, controllers, services, models, requests, responses, and webhooks, can be customized.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization.html
---
-# Backend customization
+# Back-end customization
-
+Strapi runs an HTTP server based on [Koa](https://koajs.com/), a back end JavaScript framework.
-## Routing
-
-`./api/**/config/routes.json` files define all available endpoints for the clients.
-
-By default, Strapi generates endpoints for all your Content Types. More information is in the [Content API](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints) documentation.
-
-### How to create a route?
-
-You have to edit the `routes.json` file in one of your APIs folders (`./api/**/config/routes.json`) and manually add a new route object into the `routes` array.
-
-**Path —** `./api/**/config/routes.json`.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/restaurants",
- "handler": "Restaurant.find",
- "config": {
- "policies": []
- }
- },
- {
- "method": "PUT",
- "path": "/restaurants/bulkUpdate",
- "handler": "Restaurant.bulkUpdate",
- "config": {
- "policies": []
- }
- },
- {
- "method": "POST",
- "path": "/restaurants/:id/reservation",
- "handler": "Restaurant.reservation",
- "config": {
- "policies": ["is-authenticated", "has-credit-card"]
- }
- }
- ]
-}
-```
-
-- `method` (string): Method or array of methods to hit the route (e.g. `GET`, `POST`, `PUT`, `HEAD`, `DELETE`, `PATCH`).
-- `path` (string): URL starting with `/` (e.g. `/restaurants`).
-- `handler` (string): Action to execute when the route is hit following this syntax `.`.
-- `config`
- - `policies` (array): Array of policy names or paths ([see more](#policies))
-
-::: tip
-You can exclude the entire `config` object if you do not want the route to be checked by the [Users & Permissions plugin](/developer-docs/latest/development/plugins/users-permissions.md).
-:::
-
-### Dynamic parameters
-
-The router used by Strapi allows you to create dynamic routes where you can use parameters and simple regular expressions. These parameters will be exposed in the `ctx.params` object. For more details, please refer to the [PathToRegex](https://github.com/pillarjs/path-to-regexp) documentation.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/restaurants/:category/:id",
- "handler": "Restaurant.findOneByCategory",
- "config": {
- "policies": []
- }
- },
- {
- "method": "GET",
- "path": "/restaurants/:region(\\d{2}|\\d{3})/:id", // Only match when the first parameter contains 2 or 3 digits.
- "handler": "Restaurant.findOneByRegion",
- "config": {
- "policies": []
- }
- }
- ]
-}
-```
-
-#### Example
-
-Route definition with URL params
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/restaurants/:id",
- "handler": "Restaurant.findOne",
- "config": {
- "policies": []
- }
- }
- ]
-}
-```
-
-Get the URL param in the controller
-
-```js
-module.exports = {
- findOne: async ctx => {
- // const id = ctx.params.id;
- const { id } = ctx.params;
- return id;
- },
-};
-```
-
-
-
-## Policies
-
-Policies are functions which have the ability to execute specific logic on each request before it reaches the controller's action. They are mostly used for securing business logic easily.
-Each route of the project can be associated to an array of policies. For example, you can create a policy named `isAdmin`, which obviously checks that the request is sent by an admin user, and use it for critical routes.
-
-The policies are defined in each `./api/**/config/policies/` folders and plugins. They are respectively exposed through `strapi.api.**.config.policies` and `strapi.plugins.**.config.policies`. The global policies are defined at `./config/policies/` and accessible via `strapi.config.policies`.
-
-### How to create a policy?
-
-There are several ways to create a policy.
-
-- Using the CLI `strapi generate:policy is-authenticated`.
Read the [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI.md) for more information.
-- Manually create a JavaScript file named `is-authenticated.js` in `./config/policies/`.
-
-**Path —** `./config/policies/is-authenticated.js`.
-
-```js
-module.exports = async (ctx, next) => {
- if (ctx.state.user) {
- // Go to next policy or will reach the controller's action.
- return await next();
- }
-
- ctx.unauthorized(`You're not logged in!`);
-};
-```
-
-In this example, we are verifying that a session is open. If it is the case, we call the `next()` method that will execute the next policy or controller's action. Otherwise, a 401 error is returned.
-
-### Usage
-
-To apply policies to a route, you need to associate an array of policies to it. There are two kinds of policies: global and scoped.
-
-::: warning
-To apply policies with GraphQL please see the [following guide](/developer-docs/latest/development/plugins/graphql.md#execute-a-policy-before-a-resolver).
-:::
-
-#### Global policies
-
-The global policies can be associated to any route in your project.
-
-**Path —** `./api/restaurant/routes.json`.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/restaurants",
- "handler": "Restaurant.find",
- "config": {
- "policies": ["global::is-authenticated"]
- }
- }
- ]
-}
-```
-
-Before executing the `find` action in the `Restaurant.js` controller, the global policy `is-authenticated` located in `./config/policies/is-authenticated.js` will be called.
-
-::: tip
-You can put as much policy as you want in this array. However be careful about the performance impact.
-:::
-
-#### Plugins policies
-
-Plugins can add and expose policies into your app. For example, the plugin **Users & Permissions** comes with useful policies to ensure that the user is well authenticated or has the rights to perform an action.
-
-**Path —** `./api/restaurant/config/routes.json`.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/restaurants",
- "handler": "Restaurant.find",
- "config": {
- "policies": ["plugins::users-permissions.isAuthenticated"]
- }
- }
- ]
-}
-```
-
-The policy `isAuthenticated` located in the `users-permissions` plugin will be executed before the `find` action in the `Restaurant.js` controller.
-
-#### API policies
-
-The API policies can be associated to the routes defined in the API where they have been declared.
-
-**Path —** `./api/restaurant/config/policies/isAdmin.js`.
-
-```js
-module.exports = async (ctx, next) => {
- if (ctx.state.user.role.name === 'Administrator') {
- // Go to next policy or will reach the controller's action.
- return await next();
- }
-
- ctx.unauthorized(`You're not allowed to perform this action!`);
-};
-```
-
-**Path —** `./api/restaurant/config/routes.json`.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/restaurants",
- "handler": "Restaurant.find",
- "config": {
- "policies": ["isAdmin"]
- }
- }
- ]
-}
-```
-
-The policy `isAdmin` located in `./api/restaurant/config/policies/isAdmin.js` will be executed before the `find` action in the `Restaurant.js` controller.
-
-#### Using a policy outside its api
-
-To use a policy in another api you can reference it with the following syntax: `{apiName}.{policyName}`.
-
-**Path —** `./api/category/config/routes.json`.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/categories",
- "handler": "Category.find",
- "config": {
- "policies": ["restaurant.isAdmin"]
- }
- }
- ]
-}
-```
-
-### Advanced usage
-
-As it's explained above, the policies are executed before the controller's action. It looks like an action that you can make `before` the controller's action. You can also execute a logic `after`.
-
-**Path —** `./config/policies/custom404.js`.
-
-```js
-module.exports = async (ctx, next) => {
- // Indicate to the server to go to
- // the next policy or to the controller's action.
- await next();
-
- // The code below will be executed after the controller's action.
- if (ctx.status === 404) {
- ctx.body = 'We cannot find the resource.';
- }
-};
-```
-
-
-
-## Controllers
-
-Controllers are JavaScript files which contain a set of methods called **actions** reached by the client according to the requested route. It means that every time a client requests the route, the action performs the business logic code and sends back the response. They represent the _C_ in the _MVC_ pattern. In most cases, the controllers will contain the bulk of a project's business logic.
-
-```js
-module.exports = {
- // GET /hello
- async index(ctx) {
- return 'Hello World!';
- },
-};
-```
-
-In this example, any time a web browser is pointed to the `/hello` URL on your app, the page will display the text: `Hello World!`.
-
-The controllers are defined in each `./api/**/controllers/` folder. Every JavaScript file put in these folders will be loaded as a controller. They are also available through the `strapi.controllers` and `strapi.api.**.controllers` global variables.
-
-### Core controllers
-
-When you create a new `Content Type` you will see a new empty controller has been created. This is because Strapi builds a generic controller for your models by default and allows you to override and extend it in the generated files.
-
-#### Extending a Model Controller
-
-Here are the core methods (and their current implementation).
-You can simply copy and paste this code in your own controller file to customize the methods.
-
-::: warning
-In the following example we will assume your controller, service and model are named `restaurant`
-:::
-
-##### Utils
-
-First require the utility functions
-
-```js
-const { parseMultipartData, sanitizeEntity } = require('strapi-utils');
-```
-
-- `parseMultipartData`: This function parses Strapi's formData format.
-- `sanitizeEntity`: This function removes all private fields from the model and its relations.
-
-##### Collection Type
-
-:::: tabs
-
-::: tab find
-
-##### `find`
-
-```js
-const { sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Retrieve records.
- *
- * @return {Array}
- */
-
- async find(ctx) {
- let entities;
- if (ctx.query._q) {
- entities = await strapi.services.restaurant.search(ctx.query);
- } else {
- entities = await strapi.services.restaurant.find(ctx.query);
- }
-
- return entities.map(entity => sanitizeEntity(entity, { model: strapi.models.restaurant }));
- },
-};
-```
-
-:::
-
-::: tab findOne
-
-##### `findOne`
-
-```js
-const { sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Retrieve a record.
- *
- * @return {Object}
- */
-
- async findOne(ctx) {
- const { id } = ctx.params;
-
- const entity = await strapi.services.restaurant.findOne({ id });
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::: tab count
-
-##### `count`
-
-```js
-module.exports = {
- /**
- * Count records.
- *
- * @return {Number}
- */
-
- count(ctx) {
- if (ctx.query._q) {
- return strapi.services.restaurant.countSearch(ctx.query);
- }
- return strapi.services.restaurant.count(ctx.query);
- },
-};
-```
-
-:::
-
-::: tab create
-
-##### `create`
-
-```js
-const { parseMultipartData, sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Create a record.
- *
- * @return {Object}
- */
-
- async create(ctx) {
- let entity;
- if (ctx.is('multipart')) {
- const { data, files } = parseMultipartData(ctx);
- entity = await strapi.services.restaurant.create(data, { files });
- } else {
- entity = await strapi.services.restaurant.create(ctx.request.body);
- }
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::: tab update
-
-##### `update`
-
-```js
-const { parseMultipartData, sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Update a record.
- *
- * @return {Object}
- */
-
- async update(ctx) {
- const { id } = ctx.params;
-
- let entity;
- if (ctx.is('multipart')) {
- const { data, files } = parseMultipartData(ctx);
- entity = await strapi.services.restaurant.update({ id }, data, {
- files,
- });
- } else {
- entity = await strapi.services.restaurant.update({ id }, ctx.request.body);
- }
-
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::: tab delete
-
-##### `delete`
-
-```js
-const { sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Delete a record.
- *
- * @return {Object}
- */
-
- async delete(ctx) {
- const { id } = ctx.params;
-
- const entity = await strapi.services.restaurant.delete({ id });
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::::
-
-##### Single Type
-
-:::: tabs
-
-::: tab find
-
-##### `find`
-
-```js
-const { sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Retrieve the record.
- *
- * @return {Object}
- */
-
- async find(ctx) {
- const entity = await strapi.services.restaurant.find();
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::: tab update
-
-##### `update`
-
-```js
-const { parseMultipartData, sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Update the record.
- *
- * @return {Object}
- */
-
- async update(ctx) {
- let entity;
- if (ctx.is('multipart')) {
- const { data, files } = parseMultipartData(ctx);
- entity = await strapi.services.restaurant.createOrUpdate(data, {
- files,
- });
- } else {
- entity = await strapi.services.restaurant.createOrUpdate(ctx.request.body);
- }
-
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::: tab delete
-
-##### `delete`
-
-```js
-const { sanitizeEntity } = require('strapi-utils');
-
-module.exports = {
- /**
- * Delete the record.
- *
- * @return {Object}
- */
-
- async delete(ctx) {
- const entity = await strapi.services.restaurant.delete();
- return sanitizeEntity(entity, { model: strapi.models.restaurant });
- },
-};
-```
-
-:::
-
-::::
-
-### Custom controllers
-
-You can also create custom controllers to build your own business logic and API endpoints.
-
-There are two ways to create a controller:
-
-- Using the CLI `strapi generate:controller restaurant`.
Read the [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate-controller) for more information.
-- Manually create a JavaScript file in `./api/**/controllers`.
-
-#### Adding Endpoints
-
-Each controller’s action must be an `async` function.
-Every action receives a `context` (`ctx`) object as first parameter containing the [request context](/developer-docs/latest/development/backend-customization.md#responses) and the [response context](/developer-docs/latest/development/backend-customization.md#responses).
-
-#### Example
-
-In this example, we are defining a specific route in `./api/hello/config/routes.json` that takes `Hello.index` as handler. For more information on routing, please see the [Routing documentation](#routing)
-
-It means that every time a request `GET /hello` is sent to the server, Strapi will call the `index` action in the `Hello.js` controller.
-Our `index` action will return `Hello World!`. You can also return a JSON object.
-
-**Path —** `./api/hello/config/routes.json`.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/hello",
- "handler": "Hello.index",
- "config": {
- "policies": []
- }
- }
- ]
-}
-```
-
-**Path —** `./api/hello/controllers/Hello.js`.
-
-```js
-module.exports = {
- // GET /hello
- async index(ctx) {
- ctx.send('Hello World!');
- },
-};
-```
-
-::: tip
-A route handler can only access the controllers defined in the `./api/**/controllers` folders.
-:::
-
-
-
-## Requests & Responses
-
-### Requests
-
-The context object (`ctx`) contains all the requests related information. They are accessible through `ctx.request`, from [controllers](/developer-docs/latest/development/backend-customization.md#controllers) and [policies](/developer-docs/latest/development/backend-customization.md#policies).
-
-Strapi passes the `body` on `ctx.request.body` and `files` through `ctx.request.files`
-
-For more information, please refer to the [Koa request documentation](http://koajs.com/#request).
-
-### Responses
-
-The context object (`ctx`) contains a list of values and functions useful to manage server responses. They are accessible through `ctx.response`, from [controllers](/developer-docs/latest/development/backend-customization.md#controllers) and [policies](/developer-docs/latest/development/backend-customization.md#policies).
-
-For more information, please refer to the [Koa response documentation](http://koajs.com/#response).
-
-
-
-## Services
-
-Services are a set of reusable functions. They are particularly useful to respect the DRY (don’t repeat yourself) programming concept and to simplify [controllers](#controllers) logic.
-
-### Core services
-
-When you create a new `Content Type` or a new model, you will see a new empty service has been created. It is because Strapi builds a generic service for your models by default and allows you to override and extend it in the generated files.
-
-#### Extending a Model Service
-
-Here are the core methods (and their current implementation).
-You can simply copy and paste this code to your own service file to customize the methods.
-
-You can read about `strapi.query` calls [here](#queries).
-
-::: tip
-In the following example your controller, service and model are named `restaurant`.
-:::
-
-#### Utils
-
-If you're extending the `create` or `update` service, first require the following utility function:
-
-```js
-const { isDraft } = require('strapi-utils').contentTypes;
-```
-
-- `isDraft`: This function checks if the entry is a draft.
-
-
-##### Collection Type
-
-:::: tabs
-
-::: tab find
-
-##### `find`
-
-```js
-module.exports = {
- /**
- * Promise to fetch all records
- *
- * @return {Promise}
- */
- find(params, populate) {
- return strapi.query('restaurant').find(params, populate);
- },
-};
-```
-
-The `find` function accepts the following arguments:
-
-- `params` (object): the filters for the find request,
-
- The object follows the URL query format (see [API parameters](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters)).
-
-```json
-{
- "name": "Tokyo Sushi"
-}
-// or
-{
- "_limit": 20,
- "name_contains": "sushi"
-}
-```
-
-- `populate` (array): the data to populate `["author", "author.name", "comment", "comment.content"]`
-
-:::
-
-::: tab findOne
-
-##### `findOne`
-
-```js
-module.exports = {
- /**
- * Promise to fetch record
- *
- * @return {Promise}
- */
-
- findOne(params, populate) {
- return strapi.query('restaurant').findOne(params, populate);
- },
-};
-```
-
-The `find` function accepts the following arguments:
-
-- `params` (object): the filters for the find request.
-
- The object follows the URL query format (see [API parameters](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters)).
-
-```json
-{
- "name": "Tokyo Sushi"
-}
-// or
-{
- "name_contains": "sushi"
-}
-```
-
-- `populate` (array): the data to populate `["author", "author.name", "comment", "comment.content"]`
-
-:::
-
-::: tab count
-
-##### `count`
-
-```js
-module.exports = {
- /**
- * Promise to count record
- *
- * @return {Promise}
- */
-
- count(params) {
- return strapi.query('restaurant').count(params);
- },
-};
-```
-
-- `params` (object): this represent filters for your find request.
- The object follow the URL query format, [refer to this documentation.](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters).
-
-```json
-{
- "name": "Tokyo Sushi"
-}
-// or
-{
- "name_contains": "sushi"
-}
-```
-
-:::
-
-::: tab create
-
-##### `create`
-
-```js
-const { isDraft } = require('strapi-utils').contentTypes;
-
-module.exports = {
- /**
- * Promise to add record
- *
- * @return {Promise}
- */
-
- async create(data, { files } = {}) {
- const isDraft = isDraft(data, strapi.models.restaurant);
- const validData = await strapi.entityValidator.validateEntityCreation(
- strapi.models.restaurant,
- data,
- { isDraft }
- );
-
- const entry = await strapi.query('restaurant').create(validData);
-
- if (files) {
- // automatically uploads the files based on the entry and the model
- await strapi.entityService.uploadFiles(entry, files, {
- model: 'restaurant',
- // if you are using a plugin's model you will have to add the `source` key (source: 'users-permissions')
- });
- return this.findOne({ id: entry.id });
- }
-
- return entry;
- },
-};
-```
-
-:::
-
-::: tab update
-
-##### `update`
-
-```js
-const { isDraft } = require('strapi-utils').contentTypes;
-
-module.exports = {
- /**
- * Promise to edit record
- *
- * @return {Promise}
- */
-
- async update(params, data, { files } = {}) {
- const existingEntry = await strapi.query('restaurant').findOne(params);
-
- const isDraft = isDraft(existingEntry, strapi.models.restaurant);
- const validData = await strapi.entityValidator.validateEntityUpdate(
- strapi.models.restaurant,
- data,
- { isDraft }
- );
-
- const entry = await strapi.query('restaurant').update(params, validData);
-
- if (files) {
- // automatically uploads the files based on the entry and the model
- await strapi.entityService.uploadFiles(entry, files, {
- model: 'restaurant',
- // if you are using a plugin's model you will have to add the `source` key (source: 'users-permissions')
- });
- return this.findOne({ id: entry.id });
- }
-
- return entry;
- },
-};
-```
-
-- `params` (object): it should look like this `{id: 1}`
-
-:::
-
-::: tab delete
-
-##### `delete`
-
-```js
-module.exports = {
- /**
- * Promise to delete a record
- *
- * @return {Promise}
- */
-
- delete(params) {
- return strapi.query('restaurant').delete(params);
- },
-};
-```
-
-- `params` (object): it should look like this `{id: 1}`
-
-:::
-
-::: tab search
-
-##### `search`
-
-```js
-module.exports = {
- /**
- * Promise to search records
- *
- * @return {Promise}
- */
-
- search(params) {
- return strapi.query('restaurant').search(params);
- },
-};
-```
-
-- `params` (object): this represent filters for your find request.
- The object follow the URL query format, [refer to this documentation.](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters).
-
-```json
-{
- "name": "Tokyo Sushi"
-}
-// or
-{
- "name_contains": "sushi"
-}
-```
-
-:::
-
-::: tab countSearch
-
-##### `countSearch`
-
-```js
-module.exports = {
- /**
- * Promise to count searched records
- *
- * @return {Promise}
- */
- countSearch(params) {
- return strapi.query('restaurant').countSearch(params);
- },
-};
-```
-
-- `params` (object): this represent filters for your find request.
- The object follow the URL query format, [refer to this documentation.](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters).
-
-```json
-{
- "name": "Tokyo Sushi"
-}
-// or
-{
- "name_contains": "sushi"
-}
-```
-
-:::
-
-::::
-
-##### Single Type
-
-:::: tabs
-
-::: tab find
-
-##### `find`
-
-```js
-const _ = require('lodash');
-
-module.exports = {
- /**
- * Promise to fetch the record
- *
- * @return {Promise}
- */
- async find(params, populate) {
- const results = await strapi.query('restaurant').find({ ...params, _limit: 1 }, populate);
- return _.first(results) || null;
- },
-};
-```
-
-The `find` function accepts the following arguments:
-
-- `params` (object): the filters for the find request.
-
- The object follows the URL query format (see [API parameters](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters)).
-
-- `populate` (array): the data to populate `["author", "author.name", "comment", "comment.content"]`
-
-:::
-
-::: tab createOrUpdate
-
-##### `createOrUpdate`
-
-```js
-const _ = require('lodash');
-
-module.exports = {
- /**
- * Promise to add/update the record
- *
- * @return {Promise}
- */
-
- async createOrUpdate(data, { files } = {}) {
- const results = await strapi.query('restaurant').find({ _limit: 1 });
- const entity = _.first(results) || null;
-
- let entry;
- if (!entity) {
- entry = await strapi.query('restaurant').create(data);
- } else {
- entry = await strapi.query('restaurant').update({ id: entity.id }, data);
- }
-
- if (files) {
- // automatically uploads the files based on the entry and the model
- await strapi.entityService.uploadFiles(entry, files, {
- model: 'restaurant',
- // if you are using a plugin's model you will have to add the `plugin` key (plugin: 'users-permissions')
- });
- return this.findOne({ id: entry.id });
- }
-
- return entry;
- },
-};
-```
-
-:::
-
-::: tab delete
-
-##### `delete`
-
-```js
-module.exports = {
- /**
- * Promise to delete a record
- *
- * @return {Promise}
- */
-
- delete() {
- const results = await strapi.query('restaurant').find({ _limit: 1 });
- const entity = _.first(results) || null;
-
- if (!entity) return;
-
- return strapi.query('restaurant').delete({id: entity.id});
- },
-};
-```
-
-:::
-
-::::
-
-### Custom services
-
-You can also create custom services to build your own business logic.
-
-There are two ways to create a service.
-
-- Using the CLI `strapi generate:service restaurant`.
Read the [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI.md) for more information.
-- Manually create a JavaScript file named in `./api/**/services/`.
-
-#### Example
-
-The goal of a service is to store reusable functions. An `email` service could be useful to send emails from different functions in our codebase:
-
-**Path —** `./api/email/services/Email.js`.
-
-```js
-const nodemailer = require('nodemailer');
-
-// Create reusable transporter object using SMTP transport.
-const transporter = nodemailer.createTransport({
- service: 'Gmail',
- auth: {
- user: 'user@gmail.com',
- pass: 'password',
- },
-});
-
-module.exports = {
- send: (from, to, subject, text) => {
- // Setup e-mail data.
- const options = {
- from,
- to,
- subject,
- text,
- };
-
- // Return a promise of the function that sends the email.
- return transporter.sendMail(options);
- },
-};
-```
-
-::: tip
-please make sure you installed `nodemailer` (`npm install nodemailer`) for this example.
-:::
-
-The service is now available through the `strapi.services` global variable. We can use it in another part of our codebase. For example a controller like below:
-
-**Path —** `./api/user/controllers/User.js`.
-
-```js
-module.exports = {
- // GET /hello
- signup: async ctx => {
- // Store the new user in database.
- const user = await User.create(ctx.query);
-
- // Send an email to validate his subscriptions.
- strapi.services.email.send('welcome@mysite.com', user.email, 'Welcome', '...');
-
- // Send response to the server.
- ctx.send({
- ok: true,
- });
- },
-};
-```
-
-
-
-## Queries
-
-Strapi provides a utility function `strapi.query` to make database queries.
-
-You can just call `strapi.query('modelName', 'pluginName')` to access the query API for any model.
-
-These queries handle for you specific Strapi features like `components`, `dynamic zones`, `filters` and `search`.
-
-### API Reference
-
-:::: tabs
-
-::: tab find
-
-#### `find`
-
-This method returns a list of entries matching Strapi filters.
-You can also pass a populate option to specify which relations you want to be populated.
-By default the result will be limited to the first 100 entries.
-To get all entries use `_limit: -1` in the populate options.
-
-##### Examples
-
-**Find by id**:
-
-```js
-strapi.query('restaurant').find({ id: 1 });
-```
-
-**Find by id IN, with a limit**:
-
-```js
-strapi.query('restaurant').find({ _limit: 10, id_in: [1, 2] });
-```
-
-**Find by date orderBy name**:
-
-```js
-strapi.query('restaurant').find({ date_gt: '2019-01-01T00:00:00Z', _sort: 'name:desc' });
-```
-
-**Find by id not in and populate a relation. Skip the first ten results**
-
-```js
-strapi.query('restaurant').find({ id_nin: [1], _start: 10 }, ['category', 'category.name']);
-```
-
-:::
-
-::: tab findOne
-
-#### `findOne`
-
-This method returns the first entry matching some basic params.
-You can also pass a populate option to specify which relations you want to be populated.
-
-##### Examples
-
-**Find one by id**:
-
-```js
-strapi.query('restaurant').findOne({ id: 1 });
-```
-
-**Find one by name**:
-
-```js
-strapi.query('restaurant').findOne({ name: 'restaurant name' });
-```
-
-**Find one by name and creation_date**:
-
-```js
-strapi.query('restaurant').findOne({ name: 'restaurant name', date: '2019-01-01T00:00:00Z' });
-```
-
-**Find one by id and populate a relation**
-
-```js
-strapi.query('restaurant').findOne({ id: 1 }, ['category', 'category.name']);
-```
-
-:::
-
-::: tab create
-
-#### `create`
-
-Creates an entry in the database and returns the entry.
-
-##### Example
-
-```js
-strapi.query('restaurant').create({
- name: 'restaurant name',
- // this is a dynamiczone field. the order is persisted in db.
- content: [
- {
- __component: 'blog.rich-text',
- title: 'Some title',
- subTitle: 'Some sub title',
- },
- {
- __component: 'blog.quote',
- quote: 'Some interesting quote',
- author: 1,
- },
- ],
- // this is a component field. the order is persisted in db.
- opening_hours: [
- {
- day_interval: 'Mon',
- opening_hour: '7:00 PM',
- closing_hour: '11:00 PM',
- },
- {
- day_interval: 'Tue',
- opening_hour: '7:00 PM',
- closing_hour: '11:00 PM',
- },
- ],
- // pass the id of a media to link it to the entry
- cover: 1,
- // automatically creates the relations when passing the ids in the field
- reviews: [1, 2, 3],
-});
-```
-
-:::
-
-::: tab update
-
-#### `update`
-
-Updates an entry in the database and returns the entry.
-
-##### Examples
-
-**Update by id**
-
-```js
-strapi.query('restaurant').update(
- { id: 1 },
- {
- name: 'restaurant name',
- content: [
- {
- __component: 'blog.rich-text',
- title: 'Some title',
- subTitle: 'Some sub title',
- },
- {
- __component: 'blog.quote',
- quote: 'Some interesting quote',
- author: 1,
- },
- ],
- opening_hours: [
- {
- day_interval: 'Mon',
- opening_hour: '7:00 PM',
- closing_hour: '11:00 PM',
- },
- {
- day_interval: 'Tue',
- opening_hour: '7:00 PM',
- closing_hour: '11:00 PM',
- },
- ],
- // pass the id of a media to link it to the entry
- cover: 1,
- // automatically creates the relations when passing the ids in the field
- reviews: [1, 2, 3],
- }
-);
-```
-
-When updating an entry with its components or dynamic zones beware that if you send the components without any `id` the previous components will be deleted and replaced. You can update the components by sending their `id` with the rest of the fields:
-
-**Update by id and update previous components**
-
-```js
-strapi.query('restaurant').update(
- { id: 1 },
- {
- name: 'Mytitle',
- content: [
- {
- __component: 'blog.rich-text',
- id: 1,
- title: 'Some title',
- subTitle: 'Some sub title',
- },
- {
- __component: 'blog.quote',
- id: 1,
- quote: 'Some interesting quote',
- author: 1,
- },
- ],
- opening_hours: [
- {
- id: 2,
- day_interval: 'Mon',
- opening_hour: '7:00 PM',
- closing_hour: '11:00 PM',
- },
- {
- id: 1,
- day_interval: 'Tue',
- opening_hour: '7:00 PM',
- closing_hour: '11:00 PM',
- },
- ],
- // pass the id of a media to link it to the entry
- cover: 1,
- // automatically creates the relations when passing the ids in the field
- reviews: [1, 2, 3],
- }
-);
-```
-
-**Partial update by name**
-
-```js
-strapi.query('restaurant').update(
- { title: 'specific name' },
- {
- title: 'restaurant name',
- }
-);
-```
-
-:::
-
-::: tab delete
-
-#### `delete`
-
-Deletes an entry and returns its value before deletion.
-You can delete multiple entries at once with the passed params.
-
-##### Examples
-
-**Delete one by id**
-
-```js
-strapi.query('restaurant').delete({ id: 1 });
-```
-
-**Delete multiple by field**
-
-```js
-strapi.query('restaurant').delete({ district: '_18th' });
-```
-
-:::
-
-::: tab count
-
-#### `count`
-
-Returns the count of entries matching Strapi filters.
-
-##### Examples
-
-**Count by district**
-
-```js
-strapi.query('restaurant').count({ district: '_1st' });
-```
-
-**Count by name contains**
-
-```js
-strapi.query('restaurant').count({ name_contains: 'food' });
-```
-
-**Count by date less than**
-
-```js
-strapi.query('restaurant').count({ date_lt: '2019-08-01T00:00:00Z' });
-```
-
-:::
-
-::: tab search
-
-#### `search`
-
-Returns entries based on a search on all fields allowing it. (this feature will return all entries on sqlite).
-
-##### Examples
-
-**Search first ten starting at 20**
-
-```js
-strapi.query('restaurant').search({ _q: 'my search query', _limit: 10, _start: 20 });
-```
-
-**Search and sort**
-
-```js
-strapi.query('restaurant').search({ _q: 'my search query', _limit: 100, _sort: 'date:desc' });
-```
-
-:::
-
-::: tab countSearch
-
-#### `countSearch`
-
-Returns the total count of entries based on a search. (this feature will return all entries on sqlite).
-
-##### Example
-
-```js
-strapi.query('restaurant').countSearch({ _q: 'my search query' });
-```
-
-:::
-
-::::
-
-### Custom Queries
-
-When you want to customize your services or create new ones you will have to build your queries with the underlying ORM models.
-
-To access the underlying model:
-
-```js
-strapi.query(modelName, plugin).model;
-```
-
-Then you can run any queries available on the model. You should refer to the specific ORM documentation for more details:
-
-:::: tabs
-
-::: tab SQL
-
-#### Bookshelf
-
-Documentation: [https://bookshelfjs.org/](https://bookshelfjs.org/)
-
-**Example**
-
-```js
-const result = await strapi
- .query('restaurant')
- .model.query(qb => {
- qb.where('id', 1);
- })
- .fetch();
-
-const fields = result.toJSON();
-```
-
-#### Knex
-
-Knex.js can be used to build and make custom queries directly to the database.
-
-Documentation: [http://knexjs.org/#Builder](http://knexjs.org/#Builder)
-
-You can access the Knex instance with:
-
-```js
-const knex = strapi.connections.default;
-```
-
-You can then use Knex to build your own custom queries. You will lose all the functionalities of the model,
-but this could come handy if you are building a more custom schema.
-Please note that if you are using the [draft system](/developer-docs/latest/concepts/draft-and-publish.md), Strapi nullyfies all the Draft columns util they are published.
-
-**Example**
-
-```js
-const _ = require('lodash');
-
-const knex = strapi.connections.default;
-const result = await knex('restaurants')
- .where('cities', 'berlin')
- .whereNot('cities.published_at', null)
- .join('chefs', 'restaurants.id', 'chefs.restaurant_id')
- .select('restaurants.name as restaurant')
- .select('chef.name as chef')
-
-// Lodash's groupBy method can be used to
-// return a grouped key-value object generated from
-// the response
-
-return (_.groupBy(result, 'chef'));
-```
-
-**We strongly suggest to sanitize any strings before making queries to the DB**
-Never attempt to make a raw query with data coming straight from the front-end; if you
-were looking for raw queries, please refer to [this section](http://knexjs.org/#Raw-Bindings)
-of the documentation.
-
-:::
-
-::: tab MongoDB
-
-#### Mongoose
-
-Documentation: [https://mongoosejs.com/](https://mongoosejs.com/)
-
-**Example**
-
-```js
-const result = strapi.query('restaurant').model.find({
- date: { $gte: '2019-01-01T00.00.00Z' },
-});
-
-const fields = result.map(entry => entry.toObject());
-```
-
-:::
-
-::::
-
-
-
-## Models
-
-### Concepts
-
-#### Content Type's models
-
-Models are a representation of the database's structure. They are split into two separate files. A JavaScript file that contains the model options (e.g: lifecycle hooks), and a JSON file that represents the data structure stored in the database.
-
-**Path —** `./api/restaurant/models/Restaurant.js`.
-
-```js
-module.exports = {
- lifecycles: {
- // Called before an entry is created
- beforeCreate(data) {},
- // Called after an entry is created
- afterCreate(result) {},
- },
-};
-```
-
-**Path —** `./api/restaurant/models/Restaurant.settings.json`.
-
-```json
-{
- "kind": "collectionType",
- "connection": "default",
- "info": {
- "name": "restaurant",
- "description": "This represents the Restaurant Model"
- },
- "attributes": {
- "cover": {
- "collection": "file",
- "via": "related",
- "plugin": "upload"
- },
- "name": {
- "default": "",
- "type": "string"
- },
- "description": {
- "default": "",
- "type": "text"
- }
- }
-}
-```
-
-In this example, there is a `Restaurant` model which contains the attributes `cover`, `name` and `description`.
-
-#### Component's models
-
-Another type of model is named `components`. A component is a data structure that can be used in one or many other API's model. There is no lifecycle related, only a JSON file definition.
-
-**Path —** `./components/default/simple.json`
-
-```json
-{
- "connection": "default",
- "collectionName": "components_default_simples",
- "info": {
- "name": "simple",
- "icon": "arrow-circle-right"
- },
- "options": {},
- "attributes": {
- "name": {
- "type": "string"
- }
- }
-}
-```
-
-In this example, there is a `Simple` component which contains the attribute `name`. And the component is in the category `default`.
-
-#### Where are the models defined?
-
-The **Content Types** models are defined in each `./api/**/models/` folder. Every JavaScript or JSON file in these folders will be loaded as a model. They are also available through the `strapi.models` and `strapi.api.**.models` global variables. Usable everywhere in the project, they contain the ORM model object that they refer to. By convention, a model's name should be written in lowercase.
-
-The **Components** models are defined in the `./components` folder. Every component has to be inside a subfolder (the category name of the component).
-
-### How to create a model?
-
-::: tip
-If you are just starting out it is very convenient to generate some models with the Content-Types Builder directly in the admin interface. You can then review the generated model mappings on the code level. The UI takes over a lot of validation tasks and gives you a feeling for available features.
-:::
-
-#### For Content Types models
-
-Use the CLI and run the following command `strapi generate:model restaurant name:string description:text`.
Read the [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI.md) for more information.
-
-This will create two files located at `./api/restaurant/models`:
-
-- `Restaurant.settings.json`: contains the list of attributes and settings. The JSON format makes the file easily editable.
-- `Restaurant.js`: imports `Restaurant.settings.json` and extends it with additional settings and life cycle callbacks.
-
-::: tip
-When you create a new API using the CLI (`strapi generate:api `), a model is automatically created.
-:::
-
-#### For Components models
-
-To create a component you will have to use the Content-Types Builder from the Admin panel, there is not a cli generator for components.
-
-Or you can create your component manually by following the file path described previously and by following the file structure described below.
-
-### Model settings
-
-Additional settings can be set on models:
-
-- `kind` (string) - Define if the model is a Collection Type (`collectionType`) of a Single Type (`singleType`) - _only for Content Types_
-- `connection` (string) - Connection name which must be used. Default value: `default`.
-- `collectionName` (string) - Collection name (or table name) in which the data should be stored.
-- `globalId` (string) - Global variable name for this model (case-sensitive) - _only for Content Types_
-- `attributes` (object) - Define the data structure of your model. Find available options [below](#define-the-attributes).
-
-**Path —** `Restaurant.settings.json`.
-
-```json
-{
- "kind": "collectionType",
- "connection": "mongo",
- "collectionName": "Restaurants_v1",
- "globalId": "Restaurants",
- "attributes": {}
-}
-```
-
-In this example, the model `Restaurant` will be accessible through the `Restaurants` global variable. The data will be stored in the `Restaurants_v1` collection or table and the model will use the `mongo` connection defined in `./config/database.js`
-
-::: warning
-If not set manually in the JSON file, Strapi will adopt the filename as `globalId`.
-The `globalId` serves as a reference to your model within relations and Strapi APIs. If you chose to rename it (either by renaming your file or by changing the value of the `globalId`), you'd have to migrate your tables manually and update the references.
-Please note that you should not alter the Strapi's models `globalId` (plugins and core models) since they are used directly within Strapi APIs and other models' relations.
-:::
-
-::: tip
-The `connection` value can be changed whenever you want, but you should be aware that there is no automatic data migration process. Also if the new connection doesn't use the same ORM you will have to rewrite your queries.
-:::
-
-### Model information
-
-The info key on the model-json states information about the model. This information is used in the admin interface, when showing the model.
-
-- `name`: The name of the model, as shown in admin interface.
-- `description`: The description of the model.
-- `icon`: The fontawesome V5 name - _only for Components_
-
-**Path —** `Restaurant.settings.json`.
-
-```json
-{
- "info": {
- "name": "restaurant",
- "description": ""
- }
-}
-```
-
-### Model options
-
-The options key on the model-json states.
-
-- `timestamps`: This tells the model which attributes to use for timestamps. Accepts either `boolean` or `Array` of strings where first element is create date and second element is update date. Default value when set to `true` for Bookshelf is `["created_at", "updated_at"]` and for MongoDB is `["createdAt", "updatedAt"]`.
-
-- `privateAttributes`: This configuration allows to treat a set of attributes as private, even if they're not actually defined as attributes in the model. Accepts an `Array` of strings. It could be used to remove from API responses timestamps or `_v` when using MongoDB. The set of `privateAttributes` defined in the model are merged with the `privateAttributes` defined in the global Strapi configuration.
-
-- `populateCreatorFields`: Configure whether the API response should include `created_by` and `updated_by` fields or not. Accepts a `boolean`. The default value is `false`.
-
-- `draftAndPublish`: Enable the draft and publish feature. Accepts a `boolean`. The default value is `false`.
-
-**Path —** `Restaurant.settings.json`.
-
-```json
-{
- "options": {
- "timestamps": true,
- "privateAttributes": ["id", "created_at"],
- "populateCreatorFields": true,
- "draftAndPublish": false
- }
-}
-```
-
-### Define the attributes
-
-The following types are currently available:
-
-- `string`
-- `text`
-- `richtext`
-- `email`
-- `password`
-- `integer`
-- `biginteger`
-- `float`
-- `decimal`
-- `date`
-- `time`
-- `datetime`
-- `boolean`
-- `enumeration`
-- `json`
-- `uid`
-
-#### Validations
-
-You can apply basic validations to attributes. The following supported validations are _only supported by MongoDB_ database connections.
-If you're using SQL databases, you should use the native SQL constraints to apply them.
-
-- `required` (boolean) — If true, adds a required validator for this property.
-- `unique` (boolean) — Whether to define a unique index on this property.
-- `index` (boolean) — Adds an index on this property, this will create a [single field index](https://docs.mongodb.com/manual/indexes/#single-field) that will run in the background. _Only supported by MongoDB._
-- `max` (integer) — Checks if the value is greater than or equal to the given maximum.
-- `min` (integer) — Checks if the value is less than or equal to the given minimum.
-
-**Security validations**
-
-To improve the Developer Experience when developing or using the administration panel, the framework enhances the attributes with these "security validations":
-
-- `private` (boolean) — If true, the attribute will be removed from the server response. (This is useful to hide sensitive data).
-- `configurable` (boolean) - If false, the attribute isn't configurable from the Content-Types Builder plugin.
-- `autoPopulate` (boolean) - If false, the related data will not populate within REST responses. (This will not stop querying the relational data on GraphQL)
-
-#### Exceptions
-
-**uid**
-
-- `targetField`(string) — The value is the name of an attribute that has `string` of the `text` type.
-- `options` (string) — The value is a set of options passed to [the underlying `uid` generator](https://github.com/sindresorhus/slugify). A caveat is that the resulting `uid` must abide to the following RegEx `/^[A-Za-z0-9-_.~]*$`.
-
-#### Example
-
-**Path —** `Restaurant.settings.json`.
-
-```json
-{
- ...
- "attributes": {
- "title": {
- "type": "string",
- "min": 3,
- "max": 99,
- "unique": true
- },
- "description": {
- "default": "My description",
- "type": "text",
- "required": true
- },
- "slug": {
- "type": "uid",
- "targetField": "title"
- }
- ...
- }
-}
-```
-
-### Relations
-
-Relations let you create links (relations) between your Content Types.
-
-:::: tabs
-
-::: tab One-Way
-
-One-way relationships are useful to link one entry to one other entry. However, only one of the models can be queried with its linked item.
-
-##### Example
-
-A `pet` can be owned by someone (a `user`).
-
-**Path —** `./api/pet/models/Pet.settings.json`.
-
-```json
-{
- "attributes": {
- "owner": {
- "model": "user"
- }
- }
-}
-```
-
-**Example**
-
-```js
-// Create a pet
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/pets', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- owner: '5c151d9d5b1d55194d3209be', // The id of the user you want to link
- })
-);
-```
-
-:::
-
-::: tab Many-way
-
-Many-way relationships are useful to link one entry to many other entries. However, only one of the models can be queried with its linked items.
-
-##### Example
-
-A `pet` can be owned by many people (multiple `users`).
-
-**Path —** `./api/pet/models/Pet.settings.json`.
-
-```json
-{
- "attributes": {
- "owners": {
- "collection": "user"
- }
- }
-}
-```
-
-**Example**
-
-```js
-// Create a pet
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/pets', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- owners: ['5c151d9d5b1d55194d3209be', '5fc666a5bf16f48ed050ef5b'], // The id of the users you want to link
- })
-);
-```
-
-:::
-
-::: tab One-to-One
-
-One-to-One relationships are useful when you have one entity that could be linked to only one other entity. _**And vice versa**_.
-
-##### Example
-
-A `user` can have one `address`. And this address is only related to this `user`.
-
-**Path —** `./api/user/models/User.settings.json`.
-
-```json
-{
- "attributes": {
- "address": {
- "model": "address",
- "via": "user"
- }
- }
-}
-```
-
-**Path —** `./api/address/models/Address.settings.json`.
-
-```json
-{
- "attributes": {
- "user": {
- "model": "user"
- }
- }
-}
-```
-
-**Example**
-
-```js
-// Create an address
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/addresses', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- user: '5c151d9d5b1d55194d3209be', // The id of the user you want to link
- })
-);
-```
-
-:::
-
-::: tab One-to-Many
-
-One-to-Many relationships are useful when an entry can be linked to multiple entries of another Content Type. And an entry of the other Content Type can be linked to only one entry.
-
-##### Example
-
-A `user` can have many `articles`, and an `article` can be related to only one `user` (author).
-
-**Path —** `./api/user/models/User.settings.json`.
-
-```json
-{
- "attributes": {
- "articles": {
- "collection": "article",
- "via": "author"
- }
- }
-}
-```
-
-**Path —** `./api/article/models/Article.settings.json`.
-
-```json
-{
- "attributes": {
- "author": {
- "model": "user"
- }
- }
-}
-```
-
-**Examples**
-
-```js
-// Create an article
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/articles', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- author: '5c151d9d5b1d55194d3209be', // The id of the user you want to link
- })
-);
-
-// Update an article
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/users/5c151d9d5b1d55194d3209be', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- articles: ['5c151d51eb28fd19457189f6', '5c151d51eb28fd19457189f8'], // Set of ALL articles linked to the user (existing articles + new article or - removed article)
- })
-);
-```
-
-:::
-
-::: tab Many-to-Many
-
-Many-to-Many relationships are useful when an entry can be linked to multiple entries of another Content Type. And an entry of the other Content Type can be linked to many entries.
-
-##### Example
-
-A `product` can be related to many `categories` and a `category` can have many `products`.
-
-**Path —** `./api/product/models/Product.settings.json`.
-
-```json
-{
- "attributes": {
- "categories": {
- "collection": "category",
- "via": "products",
- "dominant": true, // NoSQL only
- "collectionName": "products_categories__categories_products" // SQL only, optional
- }
- }
-}
-```
-
-**NOTE**:
-(NoSQL databases only) The `dominant` key defines which table/collection should store the array that defines the relationship. Because there are no join tables in NoSQL, this key is required for NoSQL databases (e.g. MongoDB).
-
-**NOTE**:
-(SQL databases only) The `collectionName` key defines the name of the join table. It has to be specified once. If it is not specified, Strapi will use a generated default one. It is useful to define the name of the join table when the name generated by Strapi is too long for the database you use.
-
-**Path —** `./api/category/models/Category.settings.json`.
-
-```json
-{
- "attributes": {
- "products": {
- "collection": "product",
- "via": "categories"
- }
- }
-}
-```
-
-**Example**
-
-```js
-// Update a product
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/products/5c151d9d5b1d55194d3209be', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- categories: ['5c151d51eb28fd19457189f6', '5c151d51eb28fd19457189f8'], // Set of ALL categories linked to the product (existing categories + new category or - removed category).
- })
-);
-```
-
-:::
-
-::: tab Polymorphic
-
-Polymorphic relationships are the solution when you don't know which kind of model will be associated to your entry, or when you want to connect different types of models to a model.
-A common use case is an `Image` model that can be associated to different types of models (Article, Product, User, etc.).
-
-##### Single vs Many
-
-Let's stay with our `Image` model which might belong to **a single `Article` or `Product` entry**.
-
-**NOTE**:
-In other words, it means that an `Image` entry can be associated to one entry. This entry can be a `Article` or `Product` entry.
-
-Also our `Image` model might belong to **many `Article` or `Product` entries**.
-
-**NOTE**:
-In other words, it means that an `Article` entry can relate to the same image as a `Product` entry.
-
-**Path —** `./api/image/models/Image.settings.json`.
-
-```json
-{
- "attributes": {
- "related": {
- "collection": "*",
- "filter": "field"
- }
- }
-}
-```
-
-##### Filter
-
-The `filter` attribute is optional (but we highly recommend to use it every time). If it's provided it adds a new match level to retrieve the related data.
-
-For example, the `Product` model might have two attributes which are associated to the `Image` model. To distinguish which image is attached to the `cover` field and which images are attached to the `pictures` field, we need to save and provide this to the database.
-
-**Path —** `./api/article/models/Product.settings.json`.
-
-```json
-{
- "attributes": {
- "cover": {
- "model": "image",
- "via": "related"
- },
- "pictures": {
- "collection": "image",
- "via": "related"
- }
- }
-}
-```
-
-The value of the `filter` attribute is the name of the column where the information is stored.
-
-##### Example
-
-An `Image` model might belong to many `Article` models or `Product` models.
-
-**Path —** `./api/image/models/Image.settings.json`.
-
-```json
-{
- "attributes": {
- "related": {
- "collection": "*",
- "filter": "field"
- }
- }
-}
-```
-
-**Path —** `./api/article/models/Article.settings.json`.
-
-```json
-{
- "attributes": {
- "avatar": {
- "model": "image",
- "via": "related"
- }
- }
-}
-```
-
-**Path —** `./api/article/models/Product.settings.json`.
-
-```json
-{
- "attributes": {
- "pictures": {
- "collection": "image",
- "via": "related"
- }
- }
-}
-```
-
-:::
-
-::::
-
-### Components
-
-Component fields let your create a relation between your Content Type and a Component structure.
-
-##### Example
-
-Lets say we created an `openinghours` component in `restaurant` category.
-
-**Path —** `./api/restaurant/models/Restaurant.settings.json`.
-
-```json
-{
- "attributes": {
- "openinghours": {
- "type": "component",
- "repeatable": true,
- "component": "restaurant.openinghours"
- }
- }
-}
-```
-
-- `repeatable` (boolean): Could be `true` or `false` that let you create a list of data.
-- `component` (string): It follows this format `.`.
-
-:::: tabs
-
-::: tab Create
-
-Create a restaurant with non-repeatable component
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/restaurants', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- openinghour: {
- opening_at: '10am',
- closing_at: '6pm',
- day: 'monday',
- },
- })
-);
-```
-
-Create a restaurant with repeatable component
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/restaurants', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- openinghours: [
- {
- opening_at: '10am',
- closing_at: '6pm',
- day: 'monday',
- },
- {
- opening_at: '10am',
- closing_at: '6pm',
- day: 'tuesday',
- },
- ],
- })
-);
-```
-
-:::
-
-::: tab Update
-
-Update a restaurant with non-repeatable component
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/restaurants/1', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- openinghour: {
- id: 1, // the ID of the entry
- opening_at: '11am',
- closing_at: '7pm',
- day: 'wednesday',
- },
- })
-);
-```
-
-Update a restaurant with repeatable component
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/restaurants/2', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- openinghours: [
- {
- "id": 1 // the ID of the entry you want to update
- "opening_at": "10am",
- "closing_at": "6pm",
- "day": "monday"
- },
- {
- "id": 2, // you also have to put the ID of entries you don't want to update
- "opening_at": "10am",
- "closing_at": "6pm",
- "day": "tuesday"
- }
- ]
- })
-);
-```
-
-**NOTE** if you don't specify the `ID` it will delete and re-create the entry and you will see the `ID` value change.
-
-:::
-
-::: tab Delete
-
-Delete a restaurant with non-repeatable component
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/restaurants/1', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- openinghour: null,
- })
-);
-```
-
-Delete a restaurant with repeatable component
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/restaurants/2', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- openinghours: [
- {
- "id": 1 // the ID of the entry you want to keep
- "opening_at": "10am",
- "closing_at": "6pm",
- "day": "monday"
- }
- ]
- })
-);
-```
-
-:::
-
-::::
-
-### Dynamic Zone
-
-Dynamic Zone fields let you create a flexible space in which to compose content, based on a mixed list of components.
-
-##### Example
-
-Lets say we created an `slider` and `content` component in `article` category.
-
-**Path —** `./api/article/models/Article.settings.json`.
-
-```json
-{
- "attributes": {
- "body": {
- "type": "dynamiczone",
- "components": ["article.slider", "article.content"]
- }
- }
-}
-```
-
-- `components` (array): Array of components that follows this format `.`.
-
-:::: tabs
-
-::: tab Create
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('POST', '/articles', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- body: [
- {
- __component: 'article.content',
- content: 'This is a content',
- },
- {
- __component: 'article.slider',
- name: 'Slider name',
- },
- ],
- })
-);
-```
-
-:::
-
-::: tab Update
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/restaurant/2', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- body: [
- {
- "id": 1 // the ID of the entry you want to update
- "__component": "article.content",
- "content": "This is an updated content",
- },
- {
- "id": 2, // you also have to put the ID of entries you don't want to update
- "__component": "article.slider",
- "name": "Slider name",
- }
- ]
- })
-);
-```
-
-**NOTE** if you don't specify the `ID` it will delete and re-create the entry and you will see the `ID` value change.
-
-:::
-
-::: tab Delete
-
-```js
-const xhr = new XMLHttpRequest();
-xhr.open('PUT', '/restaurant/2', true);
-xhr.setRequestHeader('Content-Type', 'application/json');
-xhr.send(
- JSON.stringify({
- body: [
- {
- "id": 1 // the ID of the entry you want to keep
- "__component": "article.content",
- "content": "This is an updated content",
- }
- ]
- })
-);
-```
-
-:::
-
-::::
-
-### Lifecycle hooks
-
-The lifecycle hooks are functions that get triggered when the Strapi [`queries`](/developer-docs/latest/development/backend-customization.md#queries) are called. They will get triggered automatically when you manage your content in the Admin Panel or when you develop custom code using `queries`·
-
-To configure a `ContentType` lifecycle hook you can set a `lifecycles` key in the `{modelName}.js` file located in the `./api/{apiName}/models` folder.
-
-#### Available Lifecycle hooks
-
-:::: tabs
-
-::: tab find
-
-**`beforeFind(params, populate)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ----------------------------------- |
-| params | Object | Find params _(e.g: limit, filters)_ |
-
----
-
-**`afterFind(results, params, populate)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| -------- | ------------- | -------------------------------------- |
-| results | Array{Object} | The results found for the `find` query |
-| params | Object | Find params _(e.g: limit, filters)_ |
-| populate | Array{string} | Populate specific relations |
-
-:::
-
-::: tab findOne
-
-**`beforeFindOne(params, populate)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------- |
-| params | Object | Find params _(e.g: filters)_ |
-
----
-
-**`afterFindOne(result, params, populate)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| -------- | ------------- | ----------------------------------------- |
-| result | Object | The results found for the `findOne` query |
-| params | Object | Find params _(e.g: filters)_ |
-| populate | Array{string} | Populate specific relations |
-
-:::
-
-::: tab create
-
-**`beforeCreate(data)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ---- | ------ | ---------------------------------------- |
-| data | Object | Input data to the entry was created with |
-
----
-
-**`afterCreate(result, data)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------------------- |
-| result | Object | Created entry |
-| data | Object | Input data to the entry was created with |
-
-:::
-
-::: tab update
-
-**`beforeUpdate(params, data)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------------------- |
-| params | Object | Find params _(e.g: filters)_ |
-| data | Object | Input data to the entry was created with |
-
----
-
-**`afterUpdate(result, params, data)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------------------- |
-| result | Object | Updated entry |
-| params | Object | Find params _(e.g: filters)_ |
-| data | Object | Input data to the entry was created with |
-
-:::
-
-::: tab delete
-
-**`beforeDelete(params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------- |
-| params | Object | Find params _(e.g: filters)_ |
-
----
-
-**`afterDelete(result, params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------- |
-| result | Object | Deleted entry |
-| params | Object | Find params _(e.g: filters)_ |
-
-:::
-
-::: tab count
-
-**`beforeCount(params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------- |
-| params | Object | Find params _(e.g: filters)_ |
-
----
-
-**`afterCount(result, params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------- | ---------------------------- |
-| result | Integer | The count matching entries |
-| params | Object | Find params _(e.g: filters)_ |
-
-:::
-
-::: tab search
-
-**`beforeSearch(params, populate)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| -------- | ------------- | ---------------------------- |
-| params | Object | Find params _(e.g: filters)_ |
-| populate | Array{string} | Populate specific relations |
-
----
-
-**`afterSearch(result, params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| -------- | ------------- | ---------------------------- |
-| results | Array{Object} | The entries found |
-| params | Object | Find params _(e.g: filters)_ |
-| populate | Array{string} | Populate specific relations |
-
-:::
-
-::: tab countSearch
-
-**`beforeCountSearch(params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------ | ---------------------------- |
-| params | Object | Find params _(e.g: filters)_ |
-
----
-
-**`afterCountSearch(result, params)`**
-
-_Parameters:_
-
-| Name | Type | Description |
-| ------ | ------- | ---------------------------- |
-| result | Integer | The count matching entries |
-| params | Object | Find params _(e.g: filters)_ |
-
-:::
-
-::::
-
-#### Example
-
-**Path —** `./api/restaurant/models/Restaurant.js`.
-
-```js
-module.exports = {
- /**
- * Triggered before user creation.
- */
- lifecycles: {
- async beforeCreate(data) {
- data.isTableFull = data.numOfPeople === 4;
- },
- },
-};
-```
-
-::: tip
-You can mutate one of the parameters to change its properties. Make sure not to reassign the parameter as it will have no effect:
-
-**This will Work**
-
-```js
-module.exports = {
- lifecycles: {
- beforeCreate(data) {
- data.name = 'Some fixed name';
- },
- },
-};
-```
-
-**This will NOT Work**
-
-```js
-module.exports = {
- lifecycles: {
- beforeCreate(data) {
- data = {
- ...data,
- name: 'Some fixed name',
- };
- },
- },
-};
-```
-
-:::
-
-#### Custom use
-
-When you are building custom ORM specific queries the lifecycles will not be triggered. You can however call a lifecycle function directly if you wish.
-
-**Bookshelf example**
-
-**Path -** `./api/{apiName}/services/{serviceName}.js`
-
-```js
-module.exports = {
- async createCustomEntry() {
- const ORMModel = strapi.query(modelName).model;
-
- const newCustomEntry = await ORMModel.forge().save();
-
- // trigger manually
- ORMModel.lifecycles.afterCreate(newCustomEntry.toJSON());
- },
-};
-```
-
-::: tip
-When calling a lifecycle function directly, you will need to make sure you call it with the expected parameters.
-:::
-
-
-
-## Webhooks
-
-Webhook is a construct used by an application to notify other applications that an event occurred. More precisely, webhook is a user-defined HTTP callback. Using a webhook is a good way to tell third party providers to start some processing (CI, build, deployment ...).
-
-The way a webhook works is by delivering information to a receiving application through HTTP requests (typically POST requests).
-
-### User content type webhooks
-
-To prevent from unintentionally sending any user's information to other applications, Webhooks will not work for the User content type.
-If you need to notify other applications about changes in the Users collection, you can do so by creating [Lifecycle hooks](#lifecycle-hooks) inside the file `./extensions/users-permissions/models/User.js`.
-
-### Available configurations
-
-You can set webhook configurations inside the file `./config/server.js`.
-
-- `webhooks`
- - `defaultHeaders`: You can set default headers to use for your webhook requests. This option is overwritten by the headers set in the webhook itself.
-
-**Example configuration**
-
-```js
-module.exports = {
- webhooks: {
- defaultHeaders: {
- 'Custom-Header': 'my-custom-header',
- },
- },
-};
-```
-
-### Securing your webhooks
-
-Most of the time, webhooks make requests to public URLs, therefore it is possible that someone may find that URL and send it wrong information.
-
-To prevent this from happening you can send a header with an authentication token. Using the Admin panel you would have to do it for every webhook.
-Another way is to define `defaultHeaders` to add to every webhook requests.
-
-You can configure these global headers by updating the file at `./config/server.js`:
-
-:::: tabs
-
-::: tab Simple token
-
-```js
-module.exports = {
- webhooks: {
- defaultHeaders: {
- Authorization: 'Bearer my-very-secured-token',
- },
- },
-};
-```
-
-:::
-
-::: tab Environment variable
-
-```js
-module.exports = {
- webhooks: {
- defaultHeaders: {
- Authorization: `Bearer ${process.env.WEBHOOK_TOKEN}`,
- },
- },
-};
-```
-
-::::
-
-If you are developing the webhook handler yourself you can now verify the token by reading the headers.
-
-
-
-### Available events
-
-By default Strapi webhooks can be triggered by the following events:
-
-| Name | Description |
-| ----------------- | ----------------------------------------------------- |
-| `entry.create` | Triggered when a Content Type entry is created. |
-| `entry.update` | Triggered when a Content Type entry is updated. |
-| `entry.delete` | Triggered when a Content Type entry is deleted. |
-| `entry.publish` | Triggered when a Content Type entry is published.\* |
-| `entry.unpublish` | Triggered when a Content Type entry is unpublished.\* |
-| `media.create` | Triggered when a media is created. |
-| `media.update` | Triggered when a media is updated. |
-| `media.delete` | Triggered when a media is deleted. |
-
-\*only when `draftAndPublish` is enabled on this Content Type.
-
-### Payloads
-
-:::tip NOTE
-Private fields and passwords are not sent in the payload.
+:::strapi What is Koa?
+If you are not familiar with the Koa back end framework, we highly recommend you to read the [Koa's documentation introduction](http://koajs.com/#introduction).
:::
-#### Headers
-
-When a payload is delivered to your webhook's URL, it will contain specific headers:
-
-| Header | Description |
-| ---------------- | ------------------------------------------ |
-| `X-Strapi-Event` | Name of the event type that was triggered. |
-
-#### `entry.create`
-
-This event is triggered when a new entry is created.
-
-**Example payload**
-
-```json
-{
- "event": "entry.create",
- "created_at": "2020-01-10T08:47:36.649Z",
- "model": "address",
- "entry": {
- "id": 1,
- "geolocation": {},
- "city": "Paris",
- "postal_code": null,
- "category": null,
- "full_name": "Paris",
- "created_at": "2020-01-10T08:47:36.264Z",
- "updated_at": "2020-01-10T08:47:36.264Z",
- "cover": null,
- "images": []
- }
-}
-```
-
-#### `entry.update`
-
-This event is triggered when an entry is updated.
-
-**Example payload**
-
-```json
-{
- "event": "entry.update",
- "created_at": "2020-01-10T08:58:26.563Z",
- "model": "address",
- "entry": {
- "id": 1,
- "geolocation": {},
- "city": "Paris",
- "postal_code": null,
- "category": null,
- "full_name": "Paris",
- "created_at": "2020-01-10T08:47:36.264Z",
- "updated_at": "2020-01-10T08:58:26.210Z",
- "cover": null,
- "images": []
- }
-}
-```
-
-#### `entry.delete`
-
-This event is triggered when an entry is deleted.
-
-**Example payload**
-
-```json
-{
- "event": "entry.delete",
- "created_at": "2020-01-10T08:59:35.796Z",
- "model": "address",
- "entry": {
- "id": 1,
- "geolocation": {},
- "city": "Paris",
- "postal_code": null,
- "category": null,
- "full_name": "Paris",
- "created_at": "2020-01-10T08:47:36.264Z",
- "updated_at": "2020-01-10T08:58:26.210Z",
- "cover": null,
- "images": []
- }
-}
-```
-
-#### `entry.publish`
-
-This event is triggered when an entry is published.
-
-**Example payload**
-
-```json
-{
- "event": "entry.publish",
- "created_at": "2020-01-10T08:59:35.796Z",
- "model": "address",
- "entry": {
- "id": 1,
- "geolocation": {},
- "city": "Paris",
- "postal_code": null,
- "category": null,
- "full_name": "Paris",
- "created_at": "2020-01-10T08:47:36.264Z",
- "updated_at": "2020-01-10T08:58:26.210Z",
- "published_at": "2020-08-29T14:20:12.134Z",
- "cover": null,
- "images": []
- }
-}
-```
-
-#### `entry.unpublish`
-
-This event is triggered when an entry is unpublished.
-
-**Example payload**
-
-```json
-{
- "event": "entry.unpublish",
- "created_at": "2020-01-10T08:59:35.796Z",
- "model": "address",
- "entry": {
- "id": 1,
- "geolocation": {},
- "city": "Paris",
- "postal_code": null,
- "category": null,
- "full_name": "Paris",
- "created_at": "2020-01-10T08:47:36.264Z",
- "updated_at": "2020-01-10T08:58:26.210Z",
- "published_at": null,
- "cover": null,
- "images": []
- }
-}
-```
-
-#### `media.create`
-
-This event is triggered when you upload a file on entry creation or through the media interface.
-
-**Example payload**
+Each part of Strapi's back end can be customized:
-```json
-{
- "event": "media.create",
- "created_at": "2020-01-10T10:58:41.115Z",
- "media": {
- "id": 1,
- "name": "image.png",
- "hash": "353fc98a19e44da9acf61d71b11895f9",
- "sha256": "huGUaFJhmcZRHLcxeQNKblh53vtSUXYaB16WSOe0Bdc",
- "ext": ".png",
- "mime": "image/png",
- "size": 228.19,
- "url": "/uploads/353fc98a19e44da9acf61d71b11895f9.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2020-01-10T10:58:41.095Z",
- "updated_at": "2020-01-10T10:58:41.095Z",
- "related": []
- }
-}
-```
+- the [requests](/developer-docs/latest/development/backend-customization/requests-responses.md#requests) received by the Strapi server,
-#### `media.update`
+- the [routes](/developer-docs/latest/development/backend-customization/routes.md) that handle the requests and trigger the execution of their controller handlers,
-This event is triggered when you replace a media or update the metadata of a media through the media interface.
+- the [policies](/developer-docs/latest/development/backend-customization/policies.md) that can block access to a route,
-**Example payload**
+- the [middlewares](/developer-docs/latest/development/backend-customization/middlewares.md) that can control the request flow and the request before moving forward,
-```json
-{
- "event": "media.update",
- "created_at": "2020-01-10T10:58:41.115Z",
- "media": {
- "id": 1,
- "name": "image.png",
- "hash": "353fc98a19e44da9acf61d71b11895f9",
- "sha256": "huGUaFJhmcZRHLcxeQNKblh53vtSUXYaB16WSOe0Bdc",
- "ext": ".png",
- "mime": "image/png",
- "size": 228.19,
- "url": "/uploads/353fc98a19e44da9acf61d71b11895f9.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2020-01-10T10:58:41.095Z",
- "updated_at": "2020-01-10T10:58:41.095Z",
- "related": []
- }
-}
-```
+- the [controllers](/developer-docs/latest/development/backend-customization/controllers.md) that execute code once a route has been reached,
-#### `media.delete`
+- the [services](/developer-docs/latest/development/backend-customization/services.md) that are used to build custom logic reusable by controllers,
-This event is triggered only when you delete a media through the media interface.
+- the [models](/developer-docs/latest/development/backend-customization/models.md) that are a representation of the content data structure,
-**Example payload**
+- the [responses](/developer-docs/latest/development/backend-customization/requests-responses.md#responses) sent to the application that sent the request,
-```json
-{
- "event": "media.delete",
- "created_at": "2020-01-10T11:02:46.232Z",
- "media": {
- "id": 11,
- "name": "photo.png",
- "hash": "43761478513a4c47a5fd4a03178cfccb",
- "sha256": "HrpDOKLFoSocilA6B0_icA9XXTSPR9heekt2SsHTZZE",
- "ext": ".png",
- "mime": "image/png",
- "size": 4947.76,
- "url": "/uploads/43761478513a4c47a5fd4a03178cfccb.png",
- "provider": "local",
- "provider_metadata": null,
- "created_at": "2020-01-07T19:34:32.168Z",
- "updated_at": "2020-01-07T19:34:32.168Z",
- "related": []
- }
-}
-```
+- and the [webhooks](/developer-docs/latest/development/backend-customization/webhooks.md) that are used to notify other applications of events that occured.
diff --git a/docs/developer-docs/latest/development/backend-customization/controllers.md b/docs/developer-docs/latest/development/backend-customization/controllers.md
new file mode 100644
index 0000000000..4ce2c5001d
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/controllers.md
@@ -0,0 +1,250 @@
+---
+title: Backend customization - Controllers - Strapi Developer Docs
+description: Strapi controllers are files that contain a set of methods reached by the client according to the requested route and can be customized according to your needs.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/controllers.html
+---
+
+# Controllers
+
+Controllers are JavaScript files that contain a set of methods, called actions, reached by the client according to the requested [route](/developer-docs/latest/development/backend-customization/routes.md). Whenever a client requests the route, the action performs the business logic code and sends back the [response](/developer-docs/latest/development/backend-customization/requests-responses.md#responses). Controllers represent the C in the model-view-controller (MVC) pattern.
+
+In most cases, the controllers will contain the bulk of a project's business logic. But as a controller's logic becomes more and more complicated, it's a good practice to use [services](/developer-docs/latest/development/backend-customization/services.md) to organize the code into re-usable parts.
+
+## Implementation
+
+Controllers can be [generated or added manually](#adding-a-new-controller). Strapi provides a `createCoreController` factory function that automatically generates core controllers and allows building custom ones or [extend or replace the generated controllers](#extending-core-controllers).
+
+### Adding a new controller
+
+A new controller can be implemented:
+
+- with the [interactive CLI command `strapi generate`](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate)
+- or manually by creating a JavaScript file:
+ - in `./src/api/[api-name]/controllers/` for API controllers (this location matters as controllers are auto-loaded by Strapi from there)
+ - or in a folder like `./src/plugins/[plugin-name]/controllers/` for plugin controllers, though they can be created elsewhere as long as the plugin interface is properly exported in the `strapi-server.js` file (see [Server API for Plugins documentation](/developer-docs/latest/developer-resources/plugin-api-reference/server.md))
+
+```js
+// path: ./src/api/restaurant/controllers/restaurant.js
+
+const { createCoreController } = require('@strapi/strapi').factories;
+
+module.exports = createCoreController('api::restaurant.restaurant', ({ strapi }) => {
+ // Method 1: Creating an entirely custom action
+ async exampleAction(ctx) {
+ try {
+ ctx.body = 'ok';
+ } catch (err) {
+ ctx.body = err;
+ }
+ },
+
+ // Method 2: Wrapping a core action (leaves core logic in place)
+ async find(ctx) {
+ // some custom logic here
+ ctx.query = { ...ctx.query, local: 'en' }
+
+ // Calling the default core action
+ const { data, meta } = await super.find(ctx);
+
+ // some more custom logic
+ meta.date = Date.now()
+
+ return { data, meta };
+ },
+
+ // Method 3: Replacing a core action
+ async findOne(ctx) {
+ const { id } = ctx.params;
+ const { query } = ctx;
+
+ const entity = await strapi.service('api::restaurant.restaurant').findOne(id, query);
+ const sanitizedEntity = await this.sanitizeOutput(entity, ctx);
+
+ return this.transformResponse(sanitizedEntity);
+ }
+};
+```
+
+Each controller action can be an `async` or `sync` function.
+Every action receives a context object (`ctx`) as a parameter. `ctx` contains the [request context](/developer-docs/latest/development/backend-customization/requests-responses.md#requests) and the [response context](/developer-docs/latest/development/backend-customization/requests-responses.md#responses).
+
+::: details Example: GET /hello route calling a basic controller
+
+A specific `GET /hello` [route](/developer-docs/latest/development/backend-customization/routes.md) is defined, the name of the router file (i.e. `index`) is used to call the controller handler (i.e. `index`). Every time a `GET /hello` request is sent to the server, Strapi calls the `index` action in the `hello.js` controller, which returns `Hello World!`:
+
+```js
+// path: ./src/api/hello/routes/hello.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/hello',
+ handler: 'hello.index',
+ }
+ ]
+}
+```
+
+```js
+// path: ./src/api/hello/controllers/hello.js
+
+module.exports = {
+ async index(ctx, next) { // called by GET /hello
+ ctx.body = 'Hello World!'; // we could also send a JSON
+ },
+};
+```
+
+:::
+
+::: note
+When a new [content-type](/developer-docs/latest/development/backend-customization/models.md#content-types) is created, Strapi builds a generic controller with placeholder code, ready to be customized.
+:::
+
+### Extending core controllers
+
+Default controllers and actions are created for each content-type. These default controllers are used to return responses to API requests (e.g. when `GET /api/articles/3` is accessed, the `findOne` action of the default controller for the "Article" content-type is called). Default controllers can be customized to implement your own logic. The following code examples should help you get started.
+
+:::tip
+An action from a core controller can be replaced entirely by [creating a custom action](#adding-a-new-controller) and naming the action the same as the original action (e.g. `find`, `findOne`, `create`, `update`, or `delete`).
+:::
+
+::::: details Collection type examples
+
+:::: tabs card
+
+::: tab find()
+
+```js
+async find(ctx) {
+ // some logic here
+ const { data, meta } = await super.find(ctx);
+ // some more logic
+
+ return { data, meta };
+}
+```
+
+:::
+
+::: tab findOne()
+
+```js
+async findOne(ctx) {
+ // some logic here
+ const response = await super.findOne(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+
+::: tab create()
+
+```js
+async create(ctx) {
+ // some logic here
+ const response = await super.create(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+
+::: tab update()
+
+```js
+async update(ctx) {
+ // some logic here
+ const response = await super.update(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+
+::: tab delete()
+
+```js
+async delete(ctx) {
+ // some logic here
+ const response = await super.delete(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+::::
+:::::
+
+::::: details Single type examples
+:::: tabs card
+
+::: tab find()
+
+```js
+async find(ctx) {
+ // some logic here
+ const response = await super.find(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+
+::: tab update()
+
+```js
+async update(ctx) {
+ // some logic here
+ const response = await super.update(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+
+::: tab delete()
+
+```js
+async delete(ctx) {
+ // some logic here
+ const response = await super.delete(ctx);
+ // some more logic
+
+ return response;
+}
+```
+
+:::
+::::
+:::::
+
+## Usage
+
+Controllers are declared and attached to a route. Controllers are automatically called when the route is called, so controllers usually do not need to be called explicitly. However, [services](/developer-docs/latest/development/backend-customization/services.md) can call controllers, and in this case the following syntax should be used:
+
+```js
+// access an API controller
+strapi.controller('api::api-name.controller-name');
+// access a plugin controller
+strapi.controller('plugin::plugin-name.controller-name');
+```
+
+::: tip
+To list all the available controllers, run `yarn strapi controllers:list`.
+:::
diff --git a/docs/developer-docs/latest/development/backend-customization/middlewares.md b/docs/developer-docs/latest/development/backend-customization/middlewares.md
new file mode 100644
index 0000000000..f82f25be6a
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/middlewares.md
@@ -0,0 +1,68 @@
+---
+title: Backend customization - Middlewares - Strapi Developer Docs
+description : Strapi middlewares are configured and enabled for the entire Strapi server application. Middlewares can be customized according to your needs.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/middlewares.html
+---
+
+# Middlewares customization
+
+::: strapi Different types of middlewares
+
+In Strapi, 2 middleware concepts coexist:
+
+- **Strapi middlewares** are [configured and enabled](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md) for the entire Strapi server application. These middlewares can be applied at the application level or at the API level.
The present documentation describes how to implement them.
Plugins can also add Strapi middlewares (see [Server API documentation](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#middlewares)).
+
+- **Route middlewares** have a more limited scope and are configured and used as middlewares at the route level. They are described in the [routes documentation](/developer-docs/latest/development/backend-customization/routes.md#middlewares).
+
+:::
+
+## Implementation
+
+A new application-level or API-level middleware can be implemented:
+- with the [interactive CLI command `strapi generate`](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate)
+- or manually by creating a JavaScript file in the appropriate folder (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)):
+ - `./src/middlewares/` for application-level middlewares
+ - `./src/api/[api-name]/middlewares/` for API-level middlewares
+ - `./src/plugins/[plugin-name]/middlewares/` for [plugin middlewares](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#middlewares)
+
+Middlewares working with the REST API are functions like the following:
+
+```js
+// path: ./src/middlewares/my-middleware.js or ./src/api/[api-name]/middlewares/my-middleware.js
+module.exports = (config, { strapi })=> {
+ return (context, next) => {};
+};
+```
+
+Once created, custom middlewares should be added to the [middlewares configuration file](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md#loading-order) or Strapi won't load them.
+
+::: details Example of a custom timer middleware
+
+```js
+module.exports = () => {
+ return async (ctx, next) => {
+ const start = Date.now();
+
+ await next();
+
+ const delta = Math.ceil(Date.now() - start);
+ ctx.set('X-Response-Time', delta + 'ms');
+ };
+};
+```
+
+:::
+
+The GraphQL plugin also allows [implementing custom middlewares](/developer-docs/latest/plugins/graphql.md#middlewares), with a different syntax.
+
+## Usage
+
+Middlewares are called different ways depending on their scope:
+
+- use `global::middleware-name` for application-level middlewares
+- use `api::api-name.middleware-name` for API-level middlewares
+- use `pluigin:plugin-name.middleware-name` for plugin middlewares
+
+::: tip
+To list all the registered middlewares, run `yarn strapi middlewares:list`.
+:::
diff --git a/docs/developer-docs/latest/development/backend-customization/models.md b/docs/developer-docs/latest/development/backend-customization/models.md
new file mode 100644
index 0000000000..2daa47c93a
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/models.md
@@ -0,0 +1,603 @@
+---
+title: Models - Strapi Developer Docs
+description: Strapi models (i.e. content-types, components, and dynamic zones) define a representation of the data structure.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/models.html
+---
+
+# Models
+
+As Strapi is a headless Content Management System (CMS), creating a data structure for the content is one of the most important aspects of using the software. Models define a representation of the data structure.
+
+There are 2 different types of models in Strapi:
+
+- content-types, which can be collection types or single types, depending on how many entries they manage,
+- and components that are data structures re-usable in multiple content-types.
+
+If you are just starting out, it is convenient to generate some models with the [Content-Type Builder](/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md) directly in the admin panel. The user interface takes over a lot of validation tasks and showcases all the options available to create the content's data structure. The generated model mappings can then be reviewed at the code level using this documentation.
+
+## Model creation
+
+Content-types and components models are created and stored differently.
+
+### Content-types
+
+Content-types in Strapi can be created:
+
+- with the [Content-Type Builder in the admin panel](/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md),
+- or with [Strapi's interactive CLI `strapi generate`](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate) command.
+
+Creating a content-type with either method generates 2 files:
+
+- `schema.json` for the model's [schema](#model-schema) definition,
+- `lifecycles.js` for [lifecycle hooks](#lifecycle-hooks).
+
+These models files are stored in `./src/api/[api-name]/content-types/[content-type-name]/`, and any JavaScript or JSON file found in these folders will be loaded as a content-type's model (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)).
+
+### Components
+
+Component models can't be created with CLI tools. Use the [Content-Type Builder](/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md) or create them manually.
+
+Components models are stored in the `./src/components` folder. Every component has to be inside a subfolder, named after the category the component belongs to (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)).
+
+## Model schema
+
+The `schema.json` file of a model consists of:
+
+- [settings](#model-settings), such as the kind of content-type the model represents or the table name in which the data should be stored,
+- [information](#model-information), mostly used to display the model in the admin panel and access it through the REST and GraphQL APIs,
+- [attributes](#model-attributes), which describe the data structure of the model,
+- and [options](#model-options) used to defined specific behaviors on the model.
+
+### Model settings
+
+General settings for the model can be configured with the following parameters:
+
+| Parameter | Type | Description |
+| -------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------- |
+| `tableName` | String | Database table name in which the data should be stored |
+| `kind`
_Optional,
only for content-types_ | String | Defines if the content-type is:- a collection type (`collectionType`)
- or a single type (`singleType`)
|
+
+```json
+// ./api/[api-name]/content-types/restaurant/schema.json
+
+{
+ "kind": "collectionType",
+ "tableName": "Restaurants_v1",
+}
+```
+
+### Model information
+
+The `info` key in the model's schema describes information used to display the model in the admin panel and access it through the Content API. It includes the following parameters:
+
+
+
+| Parameter | Type | Description |
+| -------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `displayName` | String | Default name to use in the admin panel |
+| `singularName` | String | Singular form of the collection type name.
Used to generate the API routes and databases/tables collection.
Should be kebab-case. |
+| `pluralName` | String | Plural form of the collection type name.
Used to generate the API routes and databases/tables collection.
Should be kebab-case. |
+| `description` | String | Description of the model |
+| `icon`
_Optional,_
_only for Components_ | String | [FontAwesome](https://fontawesome.com/) (v5) icon name to use for the component's icon in the admin panel
+
+```json
+// ./src/api/[api-name]/content-types/restaurant/schema.json
+
+ "info": {
+ "displayName": "Restaurant",
+ "singularName": "restaurant",
+ "pluralName": "restaurants",
+ "description": ""
+ },
+```
+
+### Model attributes
+
+The data structure of a model consists of a list of attributes. Each attribute has a `type` parameter, which describes its nature and defines the attribute as a simple piece of data or a more complex structure used by Strapi.
+
+Many types of attributes are available:
+
+- scalar types (e.g. strings, dates, numbers, booleans, etc.),
+- Strapi-specific types, such as:
+ - `media`, for files uploaded through the [Media library](/user-docs/latest/content-types-builder/configuring-fields-content-type.md#media)
+ - `relation` to describe a [relation](#relations) between content-types
+ - `component` to define a [component](#components-2) (i.e. a data structure usable in multiple content-types)
+ - `dynamiczone` to define a [dynamic zone](#dynamic-zones) (i.e. a flexible space based on a list of components)
+ - and the `locale` and `localizations` types, only used by the [Internationalization (i18n) plugin](/developer-docs/latest/plugins/i18n.md)
+
+The `type` parameter of an attribute should be one of the following values:
+
+| Type categories | Available types |
+|------|-------|
+| String types | - `string`
- `text`
- `richtext`
- `enumeration`
- `email`
- `password`
- [`uid`](#uid-type)
|
+| Date types | - `date`
- `time`
- `datetime`
- `timestamp`
|
+| Number types | - `integer`
- `biginteger`
- `float`
- `decimal`
|
+| Other generic types | |
+| Special types unique to Strapi |- `media`
- [`relation`](#relations)
- [`component`](#components)
- [`dynamiczone`](#dynamic-zones)
|
+| Internationalization (i18n)-related types
_Can only be used if the [i18n plugin](/developer-docs/latest/plugins/i18n.md) is installed_| |
+
+#### Validations
+
+Basic validations can be applied to attributes using the following parameters:
+
+| Parameter | Type | Description | Default |
+| -------------- | ------- | --------------------------------------------------------------------------------------------------------- | ------- |
+| `required` | Boolean | If `true`, adds a required validator for this property | `false` |
+| `max` | Integer | Checks if the value is greater than or equal to the given maximum | - |
+| `min` | Integer | Checks if the value is less than or equal to the given minimum | - |
+| `minLength` | Integer | Minimum number of characters for a field input value | - |
+| `maxLength` | Integer | Maximum number of characters for a field input value | - |
+| `private` | Boolean | If `true`, the attribute will be removed from the server response.
💡 This is useful to hide sensitive data. | `false` |
+| `configurable` | Boolean | If `false`, the attribute isn't configurable from the Content-Type Builder plugin. | `true` |
+
+```json
+// ./src/api/[api-name]/content-types/restaurant/schema.json
+
+{
+ ...
+ "attributes": {
+ "title": {
+ "type": "string",
+ "minLength": 3,
+ "maxLength": 99,
+ "unique": true
+ },
+ "description": {
+ "default": "My description",
+ "type": "text",
+ "required": true
+ },
+ "slug": {
+ "type": "uid",
+ "targetField": "title"
+ }
+ ...
+ }
+}
+```
+
+#### `uid` type
+
+The `uid` type is used to automatically prefill the field value in the admin panel with a unique identifier (UID) (e.g. slugs for articles) based on 2 optional parameters:
+
+- `targetField` (string): If used, the value of the field defined as a target is used to auto-generate the UID.
+- `options` (string): If used, the UID is generated based on a set of options passed to [the underlying `uid` generator](https://github.com/sindresorhus/slugify). The resulting `uid` must match the following regular expression pattern: `/^[A-Za-z0-9-_.~]*$`.
+
+#### Relations
+
+Relations link content-types together. Relations are explicitly defined in the [attributes](#model-attributes) of a model with `type: 'relation'` and accept the following additional parameters:
+
+| Parameter | Description |
+| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `relation` | The type of relation among these values:- `oneToOne`
- `oneToMany`
- `manyToOne`
`manyToMany`
|
+| `target` | Accepts a string value as the name of the target content-type |
+| `mappedBy` and `inversedBy`
_Optional_ | In bidirectional relations, the owning side declares the `inversedBy` key while the inversed side declares the `mappedBy` key |
+
+::::: tabs card
+
+:::: tab One-to-One
+
+One-to-One relationships are useful when one entry can be linked to only one other entry.
+
+They can be unidirectional or bidirectional. In unidirectional relationships, only one of the models can be queried with its linked item.
+
+::: details Unidirectional use case example:
+
+ - A blog article belongs to a category.
+ - Querying an article can retrieve its category,
+ - but querying a category won't retrieve the list of articles.
+
+ ```js
+ // ./src/api/[api-name]/content-types/article/schema.json
+
+ const model = {
+ attributes: {
+ category: {
+ type: 'relation',
+ relation: 'oneToOne',
+ target: 'category',
+ },
+ },
+ };
+ ```
+
+:::
+
+::: details Bidirectional use case example:
+
+ - A blog article belongs to a category.
+ - Querying an article can retrieve its category,
+ - and querying a category also retrieves its list of articles.
+
+ ```js
+ // ./src/api/[api-name]/content-types/article/schema.json
+
+ const model = {
+ attributes: {
+ category: {
+ type: 'relation',
+ relation: 'oneToOne',
+ target: 'category',
+ inversedBy: 'article',
+ },
+ },
+ };
+
+
+ // ./src/api/[api-name]/content-types/category/schema.json
+
+ const model = {
+ attributes: {
+ article: {
+ type: 'relation',
+ relation: 'oneToOne',
+ target: 'article',
+ mappedBy: 'category',
+ },
+ },
+ };
+
+ ```
+
+:::
+
+::::
+
+:::: tab One-to-Many
+
+One-to-Many relationships are useful when:
+
+- an entry from a content-type A is linked to many entries of another content-type B,
+- while an entry from content-type B is linked to only one entry of content-type A.
+
+One-to-many relationships are always bidirectional, and are usually defined with the corresponding Many-to-One relationship:
+
+::: details Example:
+A person can own many plants, but a plant is owned by only one person.
+
+```js
+// ./src/api/[api-name]/content-types/plant/schema.json
+
+const model = {
+ attributes: {
+ owner: {
+ type: 'relation',
+ relation: 'manyToOne',
+ target: 'api::person.person',
+ inversedBy: 'plants',
+ },
+ },
+};
+
+// ./src/api/person/models/schema.json
+
+const model = {
+ attributes: {
+ plants: {
+ type: 'relation',
+ relation: 'oneToMany',
+ target: 'api::plant.plant',
+ mappedBy: 'owner',
+ },
+ },
+};
+```
+
+:::
+
+::::
+
+:::: tab Many-to-One
+
+Many-to-One relationships are useful to link many entries to one entry.
+
+They can be unidirectional or bidirectional. In unidirectional relationships, only one of the models can be queried with its linked item.
+
+::: details Unidirectional use case example:
+
+ A book can be written by many authors.
+
+ ```js
+ // ./src/api/[api-name]/content-types/book/schema.json
+
+ const model = {
+ attributes: {
+ author: {
+ type: 'relation',
+ relation: 'manyToOne',
+ target: 'author',
+ },
+ },
+ };
+
+ ```
+
+:::
+
+::: details Bidirectional use case example:
+
+ An article belongs to only one category but a category has many articles.
+
+ ```js
+ // ./src/api/[api-name]/content-types/article/schema.json
+
+ const model = {
+ attributes: {
+ author: {
+ type: 'relation',
+ relation: 'manyToOne',
+ target: 'category',
+ inversedBy: 'article',
+ },
+ },
+ };
+
+
+ // ./src/api/[api-name]/content-types/category/schema.json
+
+ const model = {
+ attributes: {
+ books: {
+ type: 'relation',
+ relation: 'oneToMany',
+ target: 'article',
+ mappedBy: 'category',
+ },
+ },
+ };
+ ```
+:::
+
+::::
+
+:::: tab Many-to-Many
+
+Many-to-Many relationships are useful when:
+
+- an entry from content-type A is linked to many entries of content-type B,
+- and an entry from content-type B is also linked to many entries from content-type A.
+
+Many-to-many relationships can be unidirectional or bidirectional. In unidirectional relationships, only one of the models can be queried with its linked item.
+
+::: details Unidirectional use case example:
+
+ ```js
+ const model = {
+ attributes: {
+ categories: {
+ type: 'relation',
+ relation: 'manyToMany',
+ target: 'category',
+ },
+ },
+ };
+ ```
+
+:::
+
+::: details Bidirectional use case example:
+
+An article can have many tags and a tag can be assigned to many articles.
+
+ ```js
+ // ./src/api/[api-name]/content-types/article/schema.json
+
+ const model = {
+ attributes: {
+ tags: {
+ type: 'relation',
+ relation: 'manyToMany',
+ target: 'tag',
+ inversedBy: 'articles',
+ },
+ },
+ };
+
+
+ // ./src/api/[api-name]/content-types/tag/schema.json
+
+ const model = {
+ attributes: {
+ articles: {
+ type: 'relation',
+ relation: 'manyToMany',
+ target: 'article',
+ mappedBy: 'tag',
+ },
+ },
+ };
+ ```
+
+:::
+
+
+
+::::
+
+:::::
+
+#### Components
+
+Component fields create a relation between a content-type and a component structure. Components are explicitly defined in the [attributes](#model-attributes) of a model with `type: 'component'` and accept the following additional parameters:
+
+| Parameter | Type | Description |
+| ------------ | ------- | ---------------------------------------------------------------------------------------- |
+| `repeatable` | Boolean | Could be `true` or `false` depending on whether the component is repeatable or not |
+| `component` | String | Define the corresponding component, following this format:
`.` |
+
+```json
+// ./src/api/[apiName]/restaurant/content-types/schema.json
+
+{
+ "attributes": {
+ "openinghours": {
+ "type": "component",
+ "repeatable": true,
+ "component": "restaurant.openinghours"
+ }
+ }
+}
+```
+
+
+#### Dynamic zones
+
+Dynamic zones create a flexible space in which to compose content, based on a mixed list of [components](#components-2).
+
+Dynamic zones are explicitly defined in the [attributes](#model-attributes) of a model with `type: 'dynamiczone'`. They also accepts a `components` array, where each component should be named following this format: `.`.
+
+```json
+// ./src/api/[api-name]/content-types/article/schema.json
+
+{
+ "attributes": {
+ "body": {
+ "type": "dynamiczone",
+ "components": ["article.slider", "article.content"]
+ }
+ }
+}
+```
+
+### Model options
+
+The `options` key is used to define specific behaviors and accepts the following parameter:
+
+| Parameter | Type | Description |
+| ----------------------- | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `privateAttributes` | Array of strings | Allows treating a set of attributes as private, even if they're not actually defined as attributes in the model. It could be used to remove them from API responses timestamps.
The set of `privateAttributes` defined in the model are merged with the `privateAttributes` defined in the global Strapi configuration. |
+| `populateCreatorFields` | Boolean | Toggles including the `created_by` and `updated_by` fields in the API response.
Default value: `false` |
+| `draftAndPublish` | Boolean | Enables the draft and publish feature.
Default value: `false` |
+
+```json
+// ./src/api/[api-name]/content-types/restaurant/schema.json
+
+{
+ "options": {
+ "privateAttributes": ["id", "created_at"],
+ "populateCreatorFields": true,
+ "draftAndPublish": false
+ }
+}
+```
+
+## Lifecycle hooks
+
+Lifecycle hooks are functions that get triggered when Strapi queries are called. They are triggered automatically when managing content through the administration panel or when developing custom code using `queries`·
+
+Lifecycle hooks can be customized declaratively or programmatically.
+
+:::caution
+Lifecycles hooks are not triggered when using directly the [knex](https://knexjs.org/) library instead of Strapi functions.
+:::
+
+### Available lifecycle events
+
+The following lifecycle events are available:
+
+- `beforeCreate`
+- `beforeCreateMany`
+- `afterCreate`
+- `afterCreateMany`
+- `beforeUpdate`
+- `beforeUpdateMany`
+- `afterUpdate`
+- `afterUpdateMany`
+- `beforeDelete`
+- `beforeDeleteMany`
+- `afterDelete`
+- `afterDeleteMany`
+- `beforeCount`
+- `afterCount`
+- `beforeFindOne`
+- `afterFindOne`
+- `beforeFindMany`
+- `afterFindMany`
+
+### Hook `event` object
+
+Lifecycle hooks are functions that take an `event` parameter, an object with the following keys:
+
+| Key | Type | Description |
+| -------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | String | Lifecycle event that has been triggered (see [list](#available-lifecycle-events)) |
+| `model` | String | Model name |
+| `em` | EntityManagerObject | EntityManager | |
+| `params` | Object | Accepts the following parameters:- `data`
- `select`
- `where`
- `orderBy`
- `limit`
- `offset`
- `populate`
|
+| `result` | Object | _Optional, only available with `afterXXX` events_
Contains the result of the action. |
+| `state` | Object | Query state, can be used to share state between `beforeXXX` and `afterXXX` events of a query. |
+
+
+### Declarative and programmatic usage
+
+To configure a content-type lifecycle hook, create a `lifecycles.js` file in the `./api/[api-name]/content-types/[content-type-name]/` folder.
+
+Each event listener is called sequentially. They can be synchronous or asynchronous.
+
+```js
+// ./src/api/[api-name]/content-types/restaurant/lifecycles.js
+
+module.exports = {
+ beforeCreate(event: Event) {
+ const { data, where, select, populate } = event.params;
+
+ // let's do a 20% discount everytime
+ event.params.data.price = event.params.data.price * 0.8;
+ },
+
+ afterCreate(event: Event) {
+ const { result, params } = event;
+
+ // do something to the result;
+ },
+};
+```
+
+Using the database layer API, it's also possible to register a subscriber and listen to events programmatically:
+
+```js
+// ./src/api/[api-name]/content-types/restaurant/lifecycles.js
+
+// registering a subscriber
+strapi.db.lifecycles.subscribe({
+ models: [], // optional;
+
+ beforeCreate(event: Event) {
+ const { data, where, select, populate } = event.params;
+
+ event.state = 'doStuffAfterWards';
+ },
+
+ afterCreate(event: Event) {
+ if (event.state === 'doStuffAfterWards') {
+ }
+
+ const { result, params } = event;
+
+ // do something to the result
+ },
+});
+
+// generic subscribe for generic handling
+strapi.db.lifecycles.subscribe((event) => {
+ if (event.action === 'beforeCreate') {
+ // do something
+ }
+});
+```
diff --git a/docs/developer-docs/latest/development/backend-customization/policies.md b/docs/developer-docs/latest/development/backend-customization/policies.md
new file mode 100644
index 0000000000..93863f3f24
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/policies.md
@@ -0,0 +1,186 @@
+---
+title: Policies - Backend customization - Strapi Developer Docs
+description: Strapi policies are functions that execute specific logic on each request before it reaches the controller. Policies can be customized according to your needs.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/policies.html
+---
+
+# Policies
+
+Policies are functions that execute specific logic on each request before it reaches the [controller](/developer-docs/latest/development/backend-customization/controllers.md). They are mostly used for securing business logic.
+
+Each [route](/developer-docs/latest/development/backend-customization/routes.md) of a Strapi project can be associated to an array of policies. For example, a policy named `is-admin` could check that the request is sent by an admin user, and restrict access to critical routes.
+
+Policies can be global or scoped. [Global policies](#global-policies) can be associated to any route in the project. Scoped policies only apply to a specific [API](#api-policies) or [plugin](#plugin-policies).
+
+## Implementation
+
+A new policy can be implemented:
+
+- with the [interactive CLI command `strapi generate`](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate)
+- or manually by creating a JavaScript file in the appropriate folder (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)):
+ - `./src/policies/` for global policies
+ - `./src/api/[api-name]/policies/` for API policies
+ - `./src/plugins/[plugin-name]/policies/` for plugin policies
+
+
+Global policy implementation example:
+
+```js
+// path: ./src/policies/is-authenticated.js
+
+module.exports = (policyContext, config, { strapi }) => {
+ if (policyContext.state.user) { // if a session is open
+ // go to next policy or reach the controller's action
+ return true;
+ }
+
+ return false; // If you return nothing, Strapi considers you didn't want to block the request and will let it pass
+};
+```
+
+`policyContext` is a wrapper arround the [controller](/developer-docs/latest/development/backend-customization/controllers.md) context. It adds some logic that can be useful to implement a policy for both REST and GraphQL.
+
+
+
+Policies can be configured using a `config` object:
+
+```js
+// path: .src/api/[api-name]/policies/my-policy.js
+
+module.exports = (policyContext, config, { strapi }) => {
+ if (policyContext.state.user.role.code === config.role) { // if user's role is the same as the one described in configuration
+ return true;
+ }
+
+ return false; // If you return nothing, Strapi considers you didn't want to block the request and will let it pass
+ }
+};
+```
+
+## Usage
+
+To apply policies to a route, add them to its configuration object (see [routes documentation](/developer-docs/latest/development/backend-customization/routes.md#policies)).
+
+Policies are called different ways depending on their scope:
+
+- use `global::policy-name` for [global policies](#global-policies)
+- use `api::api-name.policy-name` for [API policies](#api-policies)
+- use `plugin::plugin-name.policy-name` for [plugin policies](#plugin-policies)
+
+::: tip
+To list all the available policies, run `yarn strapi policies:list`.
+:::
+
+### Global policies
+
+Global policies can be associated to any route in a project.
+
+```js
+// path: ./src/api/restaurant/routes/router.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/restaurants',
+ handler: 'Restaurant.find',
+ config: {
+ /**
+ Before executing the find action in the Restaurant.js controller,
+ we call the global 'is-authenticated' policy,
+ found at ./src/policies/is-authenticated.js.
+ */
+ policies: ['global::is-authenticated']
+ }
+ }
+ ]
+}
+```
+
+### Plugin policies
+
+[Plugins](/developer-docs/latest/plugins/plugins-intro.md) can add and expose policies to an application. For example, the [Users & Permissions plugin](/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.md) comes with policies to ensure that the user is authenticated or has the rights to perform an action:
+
+```js
+// path: ./src/api/restaurant/routes/router.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/restaurants',
+ handler: 'Restaurant.find',
+ config: {
+ /**
+ The `isAuthenticated` policy prodived with the `users-permissions` plugin
+ is executed before the `find` action in the `Restaurant.js` controller.
+ */
+ policies: ['plugins::users-permissions.isAuthenticated']
+ }
+ }
+ ]
+}
+```
+
+### API policies
+
+API policies are associated to the routes defined in the API where they have been declared.
+
+```js
+
+// path: ./src/api/restaurant/policies/is-admin.js.
+
+module.exports = async (policyContext, config, { strapi }) => {
+ if (policyContext.state.user.role.name === 'Administrator') {
+ // Go to next policy or will reach the controller's action.
+ return true;
+ }
+
+ return false;
+};
+
+
+// path: ./src/api/restaurant/routes/router.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/restaurants',
+ handler: 'Restaurant.find',
+ config: {
+ /**
+ The `is-admin` policy found at `./src/api/restaurant/policies/is-admin.js`
+ is executed before the `find` action in the `Restaurant.js` controller.
+ */
+ policies: ['is-admin']
+ }
+ }
+ ]
+}
+
+```
+
+To use a policy in another API, reference it with the following syntax: `api::[apiName].[policyName]`:
+
+```js
+// path: ./src/api/category/routes/router.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/categories',
+ handler: 'Category.find',
+ config: {
+ /**
+ The `is-admin` policy found at `./src/api/restaurant/policies/is-admin.js`
+ is executed before the `find` action in the `Restaurant.js` controller.
+ */
+ policies: ['api::restaurant.is-admin']
+ }
+ }
+ ]
+}
+```
diff --git a/docs/developer-docs/latest/development/backend-customization/requests-responses.md b/docs/developer-docs/latest/development/backend-customization/requests-responses.md
new file mode 100644
index 0000000000..b1847af79f
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/requests-responses.md
@@ -0,0 +1,21 @@
+---
+title: Requests and Responses - Strapi Developer Docs
+description: Learn more about requests and responses for Strapi, the most popular headless CMS.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/requests-responses.html
+---
+
+# Requests & Responses
+
+## Requests
+
+The context object (`ctx`) contains all the requests related information. They are accessible through `ctx.request`, from [controllers](/developer-docs/latest/development/backend-customization/controllers.md) and [policies](/developer-docs/latest/development/backend-customization/policies.md).
+
+Strapi passes the `body` on `ctx.request.body` and `files` through `ctx.request.files`
+
+For more information, please refer to the [Koa request documentation](http://koajs.com/#request).
+
+## Responses
+
+The context object (`ctx`) contains a list of values and functions useful to manage server responses. They are accessible through `ctx.response`, from [controllers](/developer-docs/latest/development/backend-customization/controllers.md) and [policies](/developer-docs/latest/development/backend-customization/policies.md).
+
+For more information, please refer to the [Koa response documentation](http://koajs.com/#response).
diff --git a/docs/developer-docs/latest/development/backend-customization/routes.md b/docs/developer-docs/latest/development/backend-customization/routes.md
new file mode 100644
index 0000000000..e52ca744b0
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/routes.md
@@ -0,0 +1,324 @@
+---
+title: Routes - Strapi Developer Docs
+description: Strapi routes handle requests to your content and are auto-generated for your content-types. Routes can be customized according to your needs.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/routes.html
+---
+
+# Routes
+
+Requests sent to Strapi on any URL are handled by routes. By default, Strapi generates routes for all the content-types (see [REST API documentation](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md)). Routes can be [added](#implementation) and configured:
+
+- with [policies](#policies), which are a way to block access to a route,
+- and with [middlewares](#middlewares), which are a way to control and change the request flow and the request itself.
+
+Once a route exists, reaching it executes some code handled by a controller (see [controllers documentation](/developer-docs/latest/development/backend-customization/controllers.md)).
+
+## Implementation
+
+Implementing a new route consists in defining it in a router file within the `.src/api/[apiName]/routes` folder (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)).
+
+There are 2 different router file structures, depending on the use case:
+
+- configuring [core routers](#configuring-core-routers)
+- or creating [custom routers](#creating-custom-routers).
+
+### Configuring core routers
+
+Core routers (i.e. `find`, `findOne`, `create`, `update`, and `delete`) correspond to [default routes](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints) automatically created by Strapi when a new [content-type](/developer-docs/latest/development/backend-customization/models.md#model-creation) is created.
+
+Strapi provides a `createCoreRouter` factory function that automatically generates the core routers and allows:
+
+- passing in configuration options to each router
+- and disabling some core routers to [create custom ones](#creating-custom-routers).
+
+The core router file structure has the following parameters:
+
+| Parameter | Description | Type |
+| ----------| -------------------------------------------------------------------------------------------- | -------- |
+| `prefix` | Allows passing in a custom prefix to add to all routers for this model (e.g. `/test`) | `String` |
+| `only` | Core routes that will only be loaded
Anything not in this array is ignored. | `Array` |
+| `except` | Core routes that should not be loaded
This is functionally the opposite of the `only` parameter. | `Array` |
+| `config` | Configuration to handle [policies](#policies), [middlewares](#middlewares) and [public availability](#public-routes) for the route | `Object` |
+
+
+
+```js
+// path: ./src/api/[apiName]/routes/[routerName].js (e.g './src/api/restaurant/routes/restaurant.js')
+
+const { createCoreRouter } = require('@strapi/strapi').factories;
+
+module.exports = createCoreRouter('api::restaurant.restaurant', {
+ prefix: '',
+ only: ['find', 'findOne'],
+ except: [],
+ config: {
+ find: {
+ auth: false,
+ policies: [],
+ middlewares: [],
+ },
+ findOne: {},
+ create: {},
+ update: {},
+ delete: {},
+ },
+});
+```
+
+
+
+Generic implementation example:
+
+```js
+// path: ./src/api/restaurant/routes/restaurant.js
+
+const { createCoreRouter } = require('@strapi/strapi').factories;
+
+module.exports = createCoreRouter('api::restaurant.restaurant', {
+ only: ['find'],
+ config: {
+ find: {
+ auth: false
+ policies: [],
+ middlewares: [],
+ }
+ }
+});
+```
+
+This only allows a `GET` request on the `/restaurants` path from the core `find` [controller](/developer-docs/latest/development/backend-customization/controllers.md) without authentication.
+
+### Creating custom routers
+
+Creating custom routers consists in creating a file that exports an array of objects, each object being a route with the following parameters:
+
+| Parameter | Description | Type |
+| -------------------------- | -------------------------------------------------------------------------------- | -------- |
+| `method` | Method associated to the route (i.e. `GET`, `POST`, `PUT`, `DELETE` or `PATCH`) | `String` |
+| `path` | Path to reach, starting with a forward-leading slash (e.g. `/articles`)| `String` |
+| `handler` | Function to execute when the route is reached.
Should follow this syntax: `.` | `String` |
+| `config`
_Optional_ | Configuration to handle [policies](policies), [middlewares](middlewares) and [public availability](#public-routes) for the route
| `Object` |
+
+
+
+Dynamic routes can be created using parameters and regular expressions. These parameters will be exposed in the `ctx.params` object. For more details, please refer to the [PathToRegex](https://github.com/pillarjs/path-to-regexp) documentation.
+
+::: details Example of a custom router using URL parameters and regular expressions for routes
+```js
+// path: ./src/api/restaurant/routes/custom-restaurant.js
+
+module.exports = {
+ routes: [
+ { // Path defined with a URL parameter
+ method: 'GET',
+ path: '/restaurants/:category/:id',
+ handler: 'Restaurant.findOneByCategory',
+ },
+ { // Path defined with a regular expression
+ method: 'GET',
+ path: '/restaurants/:region(\\d{2}|\\d{3})/:id', // Only match when the first parameter contains 2 or 3 digits.
+ handler: 'Restaurant.findOneByRegion',
+ }
+ ]
+}
+```
+
+:::
+
+## Configuration
+
+Both [core routers](#configuring-core-routers) and [custom routers](#creating-custom-routers) have the same configuration options. The routes configuration is defined in a `config` object that can be used to handle [policies](#policies) and [middlewares](#middlewares) or to [make the route public](#public-routes).
+
+### Policies
+
+[Policies](/developer-docs/latest/development/backend-customization/policies.md) can be added to a route configuration:
+
+- by pointing to a policy registered in `./src/policies`, with or without passing a custom configuration
+- or by declaring the policy implementation directly, as a function that takes `policyContext` to extend [Koa's context](https://koajs.com/#context) (`ctx`) and the `strapi` instance as arguments (see [policies documentation](/developer-docs/latest/development/backend-customization/routes.md))
+
+:::: tabs card
+
+::: tab Core router policy
+
+```js
+// path: ./src/api/restaurant/routes/restaurant.js
+
+const { createCoreRouter } = require('@strapi/strapi').factories;
+
+module.exports = createCoreRouter('api::restaurant.restaurant', {
+ config: {
+ find: {
+ policies: [
+ // point to a registered policy
+ 'policy-name',
+
+ // point to a registered policy with some custom configuration
+ { name: 'policy-name', config: {} },
+
+ // pass a policy implementation directly
+ (policyContext, config, { strapi }) => {
+ return true;
+ },
+ ]
+ }
+ }
+});
+```
+
+:::
+
+::: tab Custom router policy
+
+```js
+// path: ./src/api/restaurant/routes/custom-restaurant.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/articles/customRoute',
+ handler: 'controllerName.actionName',
+ config: {
+ policies: [
+ // point to a registered policy
+ 'policy-name',
+
+ // point to a registered policy with some custom configuration
+ { name: 'policy-name', config: {} },
+
+ // pass a policy implementation directly
+ (policyContext, config, { strapi }) => {
+ return true;
+ },
+ ]
+ },
+ },
+ ],
+};
+```
+
+:::
+
+::::
+
+### Middlewares
+
+[Middlewares](/developer-docs/latest/development/backend-customization/middlewares.md) can be added to a route configuration:
+
+- by pointing to a middleware registered in `./src/middlewares`, with or without passing a custom configuration
+- or by declaring the middleware implementation directly, as a function that takes [Koa's context](https://koajs.com/#context) (`ctx`) and the `strapi` instance as arguments:
+
+:::: tabs card
+
+::: tab Core router middleware
+
+```js
+// path: ./src/api/restaurant/routes/restaurant.js
+
+const { createCoreRouter } = require('@strapi/strapi').factories;
+
+module.exports = createCoreRouter('api::restaurant.restaurant', {
+ config: {
+ find: {
+ middlwares: [
+ // point to a registered middleware
+ 'middleware-name',
+
+ // point to a registered middleware with some custom configuration
+ { name: 'middleware-name', config: {} },
+
+ // pass a middleware implementation directly
+ (ctx, next) => {
+ return next();
+ },
+ ]
+ }
+ }
+});
+```
+
+:::
+
+::: tab Custom router middleware
+
+```js
+// path: ./src/api/restaurant/routes/custom-restaurant.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/articles/customRoute',
+ handler: 'controllerName.actionName',
+ config: {
+ middlewares: [
+ // point to a registered middleware
+ 'middleware-name',
+
+ // point to a registered middleware with some custom configuration
+ { name: 'middleware-name', config: {} },
+
+ // pass a middleware implementation directly
+ (ctx, next) => {
+ return next();
+ },
+ ],
+ },
+ },
+ ],
+};
+```
+
+:::
+
+::::
+
+### Public routes
+
+By default, routes are protected by Strapi's authentication system, which is based on [API tokens](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md) or on the use of the [Users & Permissions plugin](/user-docs/latest/plugins/strapi-plugins.md#users-permissions-plugin).
+
+In some scenarios, it can be useful to have a route publicly available and control the access outside of the normal Strapi authentication system. This can be achieved by setting the `auth` configuration parameter of a route to `false`:
+
+:::: tabs card
+
+::: tab Core router with a public route
+
+```js
+// path: ./src/api/restaurant/routes/restaurant.js
+
+const { createCoreRouter } = require('@strapi/strapi').factories;
+
+module.exports = createCoreRouter('api::restaurant.restaurant', {
+ config: {
+ find: {
+ auth: false
+ }
+ }
+});
+```
+
+:::
+
+::: tab Custom router with a public route
+
+```js
+// path: ./src/api/restaurant/routes/custom-restaurant.js
+
+module.exports = {
+ routes: [
+ {
+ method: 'GET',
+ path: '/articles/customRoute',
+ handler: 'controllerName.actionName',
+ config: {
+ auth: false,
+ },
+ },
+ ],
+};
+```
+
+:::
+
+::::
diff --git a/docs/developer-docs/latest/development/backend-customization/services.md b/docs/developer-docs/latest/development/backend-customization/services.md
new file mode 100644
index 0000000000..ddce995525
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/services.md
@@ -0,0 +1,277 @@
+---
+title: Backend customization - Services - Strapi Developer Docs
+description: Strapi services are a set of reusable functions, useful to simplify controllers logic.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/services.html
+---
+
+# Services
+
+Services are a set of reusable functions. They are particularly useful to respect the "don’t repeat yourself" (DRY) programming concept and to simplify [controllers](/developer-docs/latest/development/backend-customization/controllers.md) logic.
+
+## Implementation
+
+Services can be [generated or added manually](#adding-a-new-service). Strapi provides a `createCoreService` factory function that automatically generates core controllers and allows building custom ones or [extend or replace the generated services](#extending-core-services).
+
+### Adding a new service
+
+A new service can be implemented:
+
+- with the [interactive CLI command `strapi generate`](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate)
+- or manually by creating a JavaScript file in the appropriate folder (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)):
+ - `./src/api/[api-name]/services/` for API services
+ - or `./src/plugins/[plugin-name]/services/` for [plugin services](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#services).
+
+To manually create a service, export a factory function that returns the service implementation (i.e. an object with methods). This factory function receives the `strapi` instance:
+
+```js
+// path: ./src/api/restaurant/services/restaurant.js
+
+const { createCoreService } = require('@strapi/strapi').factories;
+
+module.exports = createCoreService('api::restaurant.restaurant', ({ strapi }) => {
+ // Method 1: Creating an entirely custom service
+ async exampleService(...args) {
+ let response = { okay: true }
+
+ if (response.okay === false) {
+ return { response, error: true }
+ }
+
+ return response
+ },
+
+ // Method 2: Wrapping a core service (leaves core logic in place)
+ async find(...args) {
+ // Calling the default core controller
+ const { results, pagination } = await super.find(...args);
+
+ // some custom logic
+ results.forEach(result => {
+ result.counter = 1;
+ });
+
+ return { results, pagination };
+ },
+
+ // Method 3: Replacing a core service
+ async findOne(entityId, params = {}) {
+ return strapi.entityService.findOne('api::restaurant.restaurant', entityId, this.getFetchParams(params));
+ }
+};
+```
+
+::: strapi Entity Service API
+To get started creating your own services, see Strapi's built-in functions in the [Entity Service API](/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.md) documentation.
+:::
+
+:::: details Example of an email service
+
+The goal of a service is to store reusable functions. An `email` service could be useful to send emails from different functions in our codebase:
+
+```js
+// path: ./src/api/email/services/email.js
+
+const { createCoreService } = require('@strapi/strapi').factories;
+const nodemailer = require('nodemailer'); // Requires nodemailer to be installed (npm install nodemailer)
+
+// Create reusable transporter object using SMTP transport.
+const transporter = nodemailer.createTransport({
+ service: 'Gmail',
+ auth: {
+ user: 'user@gmail.com',
+ pass: 'password',
+ },
+});
+
+module.exports = createCoreService('api::restaurant.restaurant', ({ strapi }) => {
+ send(from, to, subject, text) => {
+ // Setup e-mail data.
+ const options = {
+ from,
+ to,
+ subject,
+ text,
+ };
+
+ // Return a promise of the function that sends the email.
+ return transporter.sendMail(options);
+ },
+};
+```
+
+The service is now available through the `strapi.service('api::email.email').send(...args)` global variable. It can be used in another part of the codebase, like in the following controller:
+
+```js
+// path: ./src/api/user/controllers/user.js
+
+module.exports = createCoreController('api::restaurant.restaurant', ({ strapi }) => {
+ // GET /hello
+ async signup(ctx) => {
+ const { userData } = ctx.body;
+
+ // Store the new user in database.
+ const user = await strapi.service('api::users-permissions.user').add(userData);
+
+ // Send an email to validate his subscriptions.
+ strapi.service('api::email.email').send('welcome@mysite.com', user.email, 'Welcome', '...');
+
+ // Send response to the server.
+ ctx.send({
+ ok: true,
+ });
+ },
+};
+```
+
+::::
+
+::: note
+When a new [content-type](/developer-docs/latest/development/backend-customization/models.md#content-types) is created, Strapi builds a generic service with placeholder code, ready to be customized.
+:::
+
+### Extending core services
+
+Core services are created for each content-type and could be used by [controllers](/developer-docs/latest/development/backend-customization/controllers.md) to execute reusable logic through a Strapi project. Core services can be customized to implement your own logic. The following code examples should help you get started.
+
+:::tip
+A core service can be replaced entirely by [creating a custom service](#adding-a-new-service) and naming it the same as the core service (e.g. `find`, `findOne`, `create`, `update`, or `delete`).
+:::
+
+::::: details Collection type examples
+
+:::: tabs card
+
+::: tab find()
+
+```js
+async find(params) {
+ // some logic here
+ const { results, pagination } = await super.find(params);
+ // some more logic
+
+ return { results, pagination };
+}
+```
+
+:::
+
+::: tab findOne()
+
+```js
+async findOne(entityId, params) {
+ // some logic here
+ const result = await super.findOne(entityId, params);
+ // some more logic
+
+ return result;
+}
+```
+
+:::
+
+::: tab create()
+
+```js
+async create(params) {
+ // some logic here
+ const result = await super.create(params);
+ // some more logic
+
+ return result;
+}
+```
+
+:::
+
+::: tab update()
+
+```js
+async update(entityId, params) {
+ // some logic here
+ const result = await super.update(entityId, params);
+ // some more logic
+
+ return result;
+}
+```
+
+:::
+
+::: tab delete()
+
+```js
+async delete(entityId, params) {
+ // some logic here
+ const result = await super.delete(entityId, params);
+ // some more logic
+
+ return result;
+}
+```
+
+:::
+::::
+:::::
+
+::::: details Single type examples
+:::: tabs card
+
+::: tab find()
+
+```js
+async find(params) {
+ // some logic here
+ const entity = await super.find(params);
+ // some more logic
+
+ return entity;
+}
+```
+
+:::
+
+::: tab update()
+
+```js
+async createOrUpdate({ data, ...params }) {
+ // some logic here
+ const entity = await super.createOrUpdate({ data, ...params });
+ // some more logic
+
+ return entity;
+}
+```
+
+:::
+
+::: tab delete()
+
+```js
+async delete(params) {
+ // some logic here
+ const entity = await super.delete(params);
+ // some more logic
+
+ return entity;
+}
+```
+
+:::
+::::
+:::::
+
+## Usage
+
+Once a service is created, it's accessible from [controllers](/developer-docs/latest/development/backend-customization/controllers.md) or from other services:
+
+```js
+// access an API service
+strapi.service('api::apiName.serviceName');
+// access a plugin service
+strapi.service('plugin::pluginName.serviceName');
+```
+
+::: tip
+To list all the available services, run `yarn strapi services:list`.
+:::
diff --git a/docs/developer-docs/latest/development/backend-customization/webhooks.md b/docs/developer-docs/latest/development/backend-customization/webhooks.md
new file mode 100644
index 0000000000..a02cd827f9
--- /dev/null
+++ b/docs/developer-docs/latest/development/backend-customization/webhooks.md
@@ -0,0 +1,367 @@
+---
+title: Webhooks - Strapi Developer Docs
+description: Strapi webhooks are user-defined HTTP callbacks used by an application to notify other applications that an event occurred.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/webhooks.html
+---
+
+# Webhooks
+
+Webhook is a construct used by an application to notify other applications that an event occurred. More precisely, webhook is a user-defined HTTP callback. Using a webhook is a good way to tell third party providers to start some processing (CI, build, deployment ...).
+
+The way a webhook works is by delivering information to a receiving application through HTTP requests (typically POST requests).
+
+## User content type webhooks
+
+To prevent from unintentionally sending any user's information to other applications, Webhooks will not work for the User content type.
+If you need to notify other applications about changes in the Users collection, you can do so by creating [Lifecycle hooks](/developer-docs/latest/development/backend-customization/models.md#lifecycle-hooks) inside the file `./extensions/users-permissions/models/User.js`.
+
+## Available configurations
+
+You can set webhook configurations inside the file `./config/server.js`.
+
+- `webhooks`
+ - `defaultHeaders`: You can set default headers to use for your webhook requests. This option is overwritten by the headers set in the webhook itself.
+
+**Example configuration**
+
+```js
+module.exports = {
+ webhooks: {
+ defaultHeaders: {
+ 'Custom-Header': 'my-custom-header',
+ },
+ },
+};
+```
+
+## Securing your webhooks
+
+Most of the time, webhooks make requests to public URLs, therefore it is possible that someone may find that URL and send it wrong information.
+
+To prevent this from happening you can send a header with an authentication token. Using the Admin panel you would have to do it for every webhook.
+Another way is to define `defaultHeaders` to add to every webhook requests.
+
+You can configure these global headers by updating the file at `./config/server.js`:
+
+:::: tabs card
+
+::: tab Simple token
+
+```js
+module.exports = {
+ webhooks: {
+ defaultHeaders: {
+ Authorization: 'Bearer my-very-secured-token',
+ },
+ },
+};
+```
+
+:::
+
+::: tab Environment variable
+
+```js
+module.exports = {
+ webhooks: {
+ defaultHeaders: {
+ Authorization: `Bearer ${process.env.WEBHOOK_TOKEN}`,
+ },
+ },
+};
+```
+
+::::
+
+If you are developing the webhook handler yourself you can now verify the token by reading the headers.
+
+
+
+## Available events
+
+By default Strapi webhooks can be triggered by the following events:
+
+| Name | Description |
+| ----------------- | ----------------------------------------------------- |
+| `entry.create` | Triggered when a Content Type entry is created. |
+| `entry.update` | Triggered when a Content Type entry is updated. |
+| `entry.delete` | Triggered when a Content Type entry is deleted. |
+| `entry.publish` | Triggered when a Content Type entry is published.\* |
+| `entry.unpublish` | Triggered when a Content Type entry is unpublished.\* |
+| `media.create` | Triggered when a media is created. |
+| `media.update` | Triggered when a media is updated. |
+| `media.delete` | Triggered when a media is deleted. |
+
+\*only when `draftAndPublish` is enabled on this Content Type.
+
+## Payloads
+
+:::tip NOTE
+Private fields and passwords are not sent in the payload.
+:::
+
+### Headers
+
+When a payload is delivered to your webhook's URL, it will contain specific headers:
+
+| Header | Description |
+| ---------------- | ------------------------------------------ |
+| `X-Strapi-Event` | Name of the event type that was triggered. |
+
+### `entry.create`
+
+This event is triggered when a new entry is created.
+
+**Example payload**
+
+```json
+{
+ "event": "entry.create",
+ "created_at": "2020-01-10T08:47:36.649Z",
+ "model": "address",
+ "entry": {
+ "id": 1,
+ "geolocation": {},
+ "city": "Paris",
+ "postal_code": null,
+ "category": null,
+ "full_name": "Paris",
+ "created_at": "2020-01-10T08:47:36.264Z",
+ "updated_at": "2020-01-10T08:47:36.264Z",
+ "cover": null,
+ "images": []
+ }
+}
+```
+
+### `entry.update`
+
+This event is triggered when an entry is updated.
+
+**Example payload**
+
+```json
+{
+ "event": "entry.update",
+ "created_at": "2020-01-10T08:58:26.563Z",
+ "model": "address",
+ "entry": {
+ "id": 1,
+ "geolocation": {},
+ "city": "Paris",
+ "postal_code": null,
+ "category": null,
+ "full_name": "Paris",
+ "created_at": "2020-01-10T08:47:36.264Z",
+ "updated_at": "2020-01-10T08:58:26.210Z",
+ "cover": null,
+ "images": []
+ }
+}
+```
+
+### `entry.delete`
+
+This event is triggered when an entry is deleted.
+
+**Example payload**
+
+```json
+{
+ "event": "entry.delete",
+ "created_at": "2020-01-10T08:59:35.796Z",
+ "model": "address",
+ "entry": {
+ "id": 1,
+ "geolocation": {},
+ "city": "Paris",
+ "postal_code": null,
+ "category": null,
+ "full_name": "Paris",
+ "created_at": "2020-01-10T08:47:36.264Z",
+ "updated_at": "2020-01-10T08:58:26.210Z",
+ "cover": null,
+ "images": []
+ }
+}
+```
+
+### `entry.publish`
+
+This event is triggered when an entry is published.
+
+**Example payload**
+
+```json
+{
+ "event": "entry.publish",
+ "created_at": "2020-01-10T08:59:35.796Z",
+ "model": "address",
+ "entry": {
+ "id": 1,
+ "geolocation": {},
+ "city": "Paris",
+ "postal_code": null,
+ "category": null,
+ "full_name": "Paris",
+ "created_at": "2020-01-10T08:47:36.264Z",
+ "updated_at": "2020-01-10T08:58:26.210Z",
+ "published_at": "2020-08-29T14:20:12.134Z",
+ "cover": null,
+ "images": []
+ }
+}
+```
+
+### `entry.unpublish`
+
+This event is triggered when an entry is unpublished.
+
+**Example payload**
+
+```json
+{
+ "event": "entry.unpublish",
+ "created_at": "2020-01-10T08:59:35.796Z",
+ "model": "address",
+ "entry": {
+ "id": 1,
+ "geolocation": {},
+ "city": "Paris",
+ "postal_code": null,
+ "category": null,
+ "full_name": "Paris",
+ "created_at": "2020-01-10T08:47:36.264Z",
+ "updated_at": "2020-01-10T08:58:26.210Z",
+ "published_at": null,
+ "cover": null,
+ "images": []
+ }
+}
+```
+
+### `media.create`
+
+This event is triggered when you upload a file on entry creation or through the media interface.
+
+**Example payload**
+
+```json
+{
+ "event": "media.create",
+ "created_at": "2020-01-10T10:58:41.115Z",
+ "media": {
+ "id": 1,
+ "name": "image.png",
+ "hash": "353fc98a19e44da9acf61d71b11895f9",
+ "sha256": "huGUaFJhmcZRHLcxeQNKblh53vtSUXYaB16WSOe0Bdc",
+ "ext": ".png",
+ "mime": "image/png",
+ "size": 228.19,
+ "url": "/uploads/353fc98a19e44da9acf61d71b11895f9.png",
+ "provider": "local",
+ "provider_metadata": null,
+ "created_at": "2020-01-10T10:58:41.095Z",
+ "updated_at": "2020-01-10T10:58:41.095Z",
+ "related": []
+ }
+}
+```
+
+### `media.update`
+
+This event is triggered when you replace a media or update the metadata of a media through the media interface.
+
+**Example payload**
+
+```json
+{
+ "event": "media.update",
+ "created_at": "2020-01-10T10:58:41.115Z",
+ "media": {
+ "id": 1,
+ "name": "image.png",
+ "hash": "353fc98a19e44da9acf61d71b11895f9",
+ "sha256": "huGUaFJhmcZRHLcxeQNKblh53vtSUXYaB16WSOe0Bdc",
+ "ext": ".png",
+ "mime": "image/png",
+ "size": 228.19,
+ "url": "/uploads/353fc98a19e44da9acf61d71b11895f9.png",
+ "provider": "local",
+ "provider_metadata": null,
+ "created_at": "2020-01-10T10:58:41.095Z",
+ "updated_at": "2020-01-10T10:58:41.095Z",
+ "related": []
+ }
+}
+```
+
+### `media.delete`
+
+This event is triggered only when you delete a media through the media interface.
+
+**Example payload**
+
+```json
+{
+ "event": "media.delete",
+ "created_at": "2020-01-10T11:02:46.232Z",
+ "media": {
+ "id": 11,
+ "name": "photo.png",
+ "hash": "43761478513a4c47a5fd4a03178cfccb",
+ "sha256": "HrpDOKLFoSocilA6B0_icA9XXTSPR9heekt2SsHTZZE",
+ "ext": ".png",
+ "mime": "image/png",
+ "size": 4947.76,
+ "url": "/uploads/43761478513a4c47a5fd4a03178cfccb.png",
+ "provider": "local",
+ "provider_metadata": null,
+ "created_at": "2020-01-07T19:34:32.168Z",
+ "updated_at": "2020-01-07T19:34:32.168Z",
+ "related": []
+ }
+}
+```
diff --git a/docs/developer-docs/latest/development/local-plugins-customization.md b/docs/developer-docs/latest/development/local-plugins-customization.md
deleted file mode 100644
index dac7ee053f..0000000000
--- a/docs/developer-docs/latest/development/local-plugins-customization.md
+++ /dev/null
@@ -1,1041 +0,0 @@
----
-title: Local plugins - Strapi Developer Documentation
-description: Strapi allows you to create your own custom local plugins that will work exactly the same as external ones.
----
-
-# Local plugins
-
-## Quick start
-
-Strapi allows you to create local plugins that will work exactly the same as external ones. All your local plugins will be located in the `./plugins` folder of your application.
-
-### Development Environment Setup
-
-Create a development project
-
-1. Create a new project `cd .. && strapi new myDevelopmentProject`.
-2. `cd myDevelopmentProject && strapi develop` To start the Strapi project
-
-### Plugin development Setup
-
-In a new terminal window:
-
-Generate a new plugin: `cd /path/to/myDevelopmentProject && strapi generate:plugin my-plugin`
-
-::: tip NOTE
-After you have successfully generated a plugin, you need to run `strapi build` which adds the new plugin to the admin panel.
-:::
-
-## Plugin Folders and Files Architecture
-
-The logic of a plugin is located at its root directory `./plugins/**`. The admin panel related parts of each plugin are contained in the `/admin` folder.
-The folders and files structure are the following:
-
-```
-plugin/
-└─── admin/ # Contains the plugin's front-end
-| └─── src/ # Source code directory
-| └─── index.js # Entry point of the plugin
-| └─── pluginId.js # Name of the plugin
-| |
-| └─── components/ # Contains the list of React components used by the plugin
-| └─── containers/
-| | └─── App/ # Container used by every others containers
-| | └─── Initializer/ # This container is required, it is used to executed logic right after the plugin is mounted.
-| └─── translations/ # Contains the translations to make the plugin internationalized
-| └─── en.json
-| └─── index.js # File that exports all the plugin's translations.
-| └─── fr.json
-└─── config/ # Contains the configurations of the plugin
-| └─── functions/
-| | └─── bootstrap.js # Asynchronous bootstrap function that runs before the app gets started
-| └─── policies/ # Folder containing the plugin's policies
-| └─── queries/ # Folder containing the plugin's models queries
-| └─── routes.json # Contains the plugin's API routes
-└─── controllers/ # Contains the plugin's API controllers
-└─── middlewares/ # Contains the plugin's middlewares
-└─── models/ # Contains the plugin's API models
-└─── services/ # Contains the plugin's API services
-```
-
-
-
-## Back-end Development
-
-This section explains how the 'back-end part' of your plugin works.
-
-### Routes
-
-The plugin API routes are defined in the `./plugins/**/config/routes.json` file.
-
-::: tip
-Please refer to [router documentation](/developer-docs/latest/development/backend-customization.md#routing) for information.
-:::
-
-**Route prefix**
-
-Each route of a plugin is prefixed by the name of the plugin (eg: `/my-plugin/my-plugin-route`). Using the `prefix` key you can change this option to something custom. You can disable the prefix, by setting the `config.prefix` key to an empty string.
-
-```json
-{
- "method": "GET",
- "path": "/my-plugin-route",
- "handler": "MyPlugin.action",
- "config": {
- "policies": [],
- "prefix": "my-custom-prefix"
- }
-}
-```
-
-### CLI
-
-The CLI can be used to generate files in the plugins folders.
-
-Please refer to the [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI.md) for more information.
-
-### Controllers
-
-Controllers contain functions executed according to the requested route.
-
-Please refer to the [Controllers documentation](/developer-docs/latest/development/backend-customization.md#controllers) for more information.
-
-### Models
-
-A plugin can have its own models.
-
-#### Table/Collection naming
-
-Sometimes it happens that the plugins inject models that have the same name as yours. Let's take a quick example.
-
-You already have `User` model defining in your `./api/user/models/User.settings.json` API. And you decide to install the `Users & Permissions` plugin. This plugin also contains a `User` model. To avoid the conflicts, the plugins' models are not globally exposed which means you cannot access to the plugin's model like this:
-
-```js
-module.exports = {
- findUser: async function(params) {
- // This `User` global variable will always make a reference the User model defining in your `./api/xxx/models/User.settings.json`.
- return await User.find();
- },
-};
-```
-
-Also, the table/collection name won't be `users` because you already have a `User` model. That's why, the framework will automatically prefix the table/collection name for this model with the name of the plugin. Which means in our example, the table/collection name of the `User` model of our plugin `Users & Permissions` will be `users-permissions_users`. If you want to force the table/collection name of the plugin's model, you can add the `collectionName` attribute in your model.
-
-Please refer to the [Models documentation](/developer-docs/latest/development/backend-customization.md#models) for more information.
-
-### Policies
-
-#### Global policies
-
-A plugin can also use a globally exposed policy in the current Strapi project.
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/",
- "handler": "MyPlugin.index",
- "config": {
- "policies": ["global::isAuthenticated"]
- }
- }
- ]
-}
-```
-
-#### Plugin policies
-
-A plugin can have its own policies, such as adding security rules. For instance, if the plugin includes a policy named `isAuthenticated`, the syntax to use this policy would be:
-
-```json
-{
- "routes": [
- {
- "method": "GET",
- "path": "/",
- "handler": "MyPlugin.index",
- "config": {
- "policies": ["plugins::myplugin.isAuthenticated"]
- }
- }
- ]
-}
-```
-
-Please refer to the [Policies documentation](/developer-docs/latest/development/backend-customization.md#policies) for more information.
-
-
-## Front-end Development
-
-Strapi's admin panel and plugins system aim to be an easy and powerful way to create new features.
-
-The admin panel is a [React](https://facebook.github.io/react/) application which can embed other React applications. These other React applications are the `admin` parts of each Strapi's plugins.
-
-### Environment setup
-
-To enable local plugin development, you need to start your application with the front-end development mode activated:
-
-:::: tabs
-
-::: tab yarn
-
-```bash
-$ cd my-app
-$ yarn develop --watch-admin
-```
-
-:::
-
-::: tab npm
-
-```bash
-$ cd my-app
-$ npm run develop -- --watch-admin
-```
-
-:::
-
-::::
-
-### API
-
-#### Strapi global variable
-
-The administration exposes a global variable that is accessible for all the plugins.
-
-##### `strapi.backendURL`
-
-Retrieve the back-end URL. (e.g. `http://localhost:1337`).
-
-##### `strapi.currentLanguage`
-
-Retrieve the administration panel default language (e.g. `en-US`)
-
-##### `strapi.languages`
-
-Array of the administration panel's supported languages. (e.g. `['ar', 'en', 'fr', ...]`).
-
-##### `strapi.lockApp()`
-
-Display a loader that will prevent the user from interacting with the application.
-
-##### `strapi.unlockApp()`
-
-Remove the loader so the user can interact with the application
-
-##### `strapi.notification`
-
-Use this command anywhere in your code.
-
-```js
-strapi.notification.toggle(config);
-```
-
-The properties of the config object are as follows:
-
-| key | type | default | Description |
-| --------------- | ------------- | ------------------------ | :--------------------------------------------------------------------------------------------------------------------------- |
-| type | string | success | `success`, `warning` or `info` |
-| message | object/string | app.notification.success | The main message to display (works with i18n message object, `{ id: 'app.notification.success', defaultMessage: 'Saved!' }`) |
-| title | object/string | null | Add a title to the notification |
-| link | object | null | Add a link to the notification message `{ url: String, label: String|Object, target:String }` |
-| timeout | number | 2500 | Time in ms before the notification is closed |
-| blockTransition | boolean | false | Block the notification transitions to remove the timeout |
-| uid | string | null | Custom the notification uid |
-
-The previous notification API is still working but will display a warning message in the console
-
-```js
-strapi.notification.error('app.notification.error');
-strapi.notification.info('app.notification.info');
-strapi.notification.success('app.notification.success');
-strapi.notification.warning('app.notification.warning');
-```
-
-##### `strapi.remoteURL`
-
-The administration url (e.g. `http://localhost:4000/admin`).
-
-#### Main plugin object
-
-Each plugin exports all its configurations in an object. This object is located in `my-plugin/admin/src/index.js`
-
-Here are its properties:
-
-| key | type | Description |
-| ------------------------- | ------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| blockerComponent | node | Props can be either `null` or React node (e.g. `() => `) |
-| blockerComponentProps | object | Props to provide to customise the [blockerComponent](https://github.com/strapi/strapi/blob/58588e10e5d15921b0966e20ce1bc6cde70df5cc/packages/strapi-helper-plugin/lib/src/components/BlockerComponent/index.js#L81-L86) |
-| description | string | Plugin's description retrieved from the package.json |
-| id | string | Id of the plugin from the `package.json` |
-| initializer | node | Refer to the [Initializer documentation](#initializer) |
-| isReady | boolean | The app will load until this property is true |
-| mainComponent | node | The plugin's App container, |
-| menu | object | Define where the link of your plugin will be set. Without this your plugin will not display a link in the left menu |
-| name | string | The plugin's name retrieved from the package.json |
-| pluginLogo | file | The plugin's logo |
-| preventComponentRendering | boolean | Whether or not display the plugin's blockerComponent instead of the main component |
-| settings | object | Refer to the [Plugins settings API](/developer-docs/latest/development/local-plugins-customization.md#plugin-s-front-end-settings-api) |
-| reducers | object | The plugin's redux reducers |
-| trads | object | The plugin's translation files |
-
-#### Displaying the plugin's link in the main menu
-
-To display a plugin link into the main menu the plugin needs to export a menu object.
-
-**Path —** `plugins/my-plugin/admin/src/index.js`.
-
-```js
-import pluginPkg from '../../package.json';
-import pluginLogo from './assets/images/logo.svg';
-import App from './containers/App';
-import lifecycles from './lifecycles';
-import trads from './translations';
-import pluginId from './pluginId';
-
-export default strapi => {
- const pluginDescription = pluginPkg.strapi.description || pluginPkg.description;
- const icon = pluginPkg.strapi.icon;
- const name = pluginPkg.strapi.name;
- const plugin = {
- blockerComponent: null,
- blockerComponentProps: {},
- description: pluginDescription,
- icon,
- id: pluginId,
- initializer: null,
- isRequired: pluginPkg.strapi.required || false,
- layout: null,
- lifecycles,
- mainComponent: App,
- name,
- pluginLogo,
- preventComponentRendering: false,
- trads,
- menu: {
- // Set a link into the PLUGINS section
- pluginsSectionLinks: [
- {
- destination: `/plugins/${pluginId}`, // Endpoint of the link
- icon,
- label: {
- id: `${pluginId}.plugin.name`, // Refers to a i18n
- defaultMessage: 'My PLUGIN',
- },
- name,
- // If the plugin has some permissions on whether or not it should be accessible
- // depending on the logged in user's role you can set them here.
- // Each permission object performs an OR comparison so if one matches the user's ones
- // the link will be displayed
- permissions: [{ action: 'plugins::content-type-builder.read', subject: null }],
- },
- ],
- },
- };
-
- return strapi.registerPlugin(plugin);
-};
-```
-
-#### Initializer
-
-The component is generated by default when you create a new plugin. Use this component to execute some logic when the app is loading. When the logic has been executed this component should emit the `isReady` event so the user can interact with the application.
-
-::: tip NOTE
-Below is the Initializer component of the content-type-builder plugin.
-
-It checks whether or not the auto-reload feature is enabled and depending on this value changes the mainComponent of the plugin.
-:::
-
-```js
-/**
- *
- * Initializer
- *
- */
-
-import React from 'react';
-import PropTypes from 'prop-types';
-
-import pluginId from '../../pluginId';
-
-class Initializer extends React.PureComponent {
- // eslint-disable-line react/prefer-stateless-function
- componentDidMount() {
- const {
- admin: { autoReload, currentEnvironment },
- } = this.props;
-
- let preventComponentRendering;
- let blockerComponentProps;
-
- if (currentEnvironment === 'production') {
- preventComponentRendering = true;
- blockerComponentProps = {
- blockerComponentTitle: 'components.ProductionBlocker.header',
- blockerComponentDescription: 'components.ProductionBlocker.description',
- blockerComponentIcon: 'fa-ban',
- blockerComponentContent: 'renderButton',
- };
- } else {
- // Don't render the plugin if the server autoReload is disabled
- preventComponentRendering = !autoReload;
- blockerComponentProps = {
- blockerComponentTitle: 'components.AutoReloadBlocker.header',
- blockerComponentDescription: 'components.AutoReloadBlocker.description',
- blockerComponentIcon: 'fa-refresh',
- blockerComponentContent: 'renderIde',
- };
- }
-
- // Prevent the plugin from being rendered if currentEnvironment === PRODUCTION
- this.props.updatePlugin(pluginId, 'preventComponentRendering', preventComponentRendering);
- this.props.updatePlugin(pluginId, 'blockerComponentProps', blockerComponentProps);
- // Emit the event plugin ready
- this.props.updatePlugin(pluginId, 'isReady', true);
- }
-
- render() {
- return null;
- }
-}
-
-Initializer.propTypes = {
- admin: PropTypes.object.isRequired,
- updatePlugin: PropTypes.func.isRequired,
-};
-
-export default Initializer;
-```
-#### Routing
-
-The routing is based on the [React Router V5](https://reacttraining.com/react-router/web/guides/philosophy), due to it's implementation each route is declared in the `containers/App/index.js` file.
-
-::: tip
-Each route defined in a plugin must be prefixed by the plugin's id.
-:::
-
-**Route declaration :**
-
-Let's say that you want to create a route `/user` with params `/:id` associated with the container UserPage.
-
-The declaration would be as follows :
-
-**Path —** `plugins/my-plugin/admin/src/containers/App/index.js`.
-
-```js
-import React from 'react';
-import pluginId from '../../pluginId';
-
-import UserPage from '../UserPage';
-
-// ...
-
-class App extends React.Component {
- // ...
-
- render() {
- return (
-
-
-
-
-
- );
- }
-}
-
-// ...
-```
-
-#### Styling
-
-The administration panel uses [styled-components](https://styled-components.com/) for writing css.
-
-#### i18n
-
-[React Intl](https://github.com/yahoo/react-intl) provides React components and an API to format dates, numbers, and strings, including pluralization and handling translations.
-
-**Usage**
-
-We recommend to set all your components text inside the translations folder.
-
-The example below shows how to use i18n inside your plugin.
-
-**Define all your ids with the associated message:**
-
-**Path —** `./plugins/my-plugin/admin/src/translations/en.json`.
-
-```json
-{
- "notification.error.message": "An error occurred"
-}
-```
-
-**Path —** `./plugins/my-plugin/admin/src/translations/fr.json`
-
-```json
-{
- "notification.error.message": "Une erreur est survenue"
-}
-```
-
-**Usage inside a component**
-
-**Path —** `./plugins/my-plugin/admin/src/components/Foo/index.js`.
-
-```js
-import { FormattedMessage } from 'react-intl';
-import SomeOtherComponent from 'components/SomeOtherComponent';
-
-const Foo = props => (
-
-
-
-
-);
-
-export default Foo;
-```
-
-See [the documentation](https://github.com/yahoo/react-intl/wiki/Components#formattedmessage) for more extensive usage.
-
-#### Global context
-
-All plugins are wrapped inside the `GlobalContextProvider`, in this object you will have access to all plugins object as well as other utilities.
-
-Usage:
-
-**Inside a functional component:**
-
-```js
-import React from 'react';
-import { useGlobalContext } from 'strapi-helper-plugin';
-
-const Foo = () => {
- const globalContext = useGlobalContext();
-
- console.log(globalContext);
-
- return Foo
;
-};
-```
-
-**Inside a class component:**
-
-```js
-import React from 'react';
-import { GlobalContext } from 'strapi-helper-plugin';
-
-class Foo extends React.Component {
- static contextType = GlobalContext;
-
- render() {
- console.log(this.context);
-
- return Foo
;
- }
-}
-```
-
-
-
-## Plugin's front-end Field API
-
-As plugins developer you may need to add custom fields in your application. To do so, a **Field API** is available in order for a plugin to register a field which will be available for all plugins.
-
-::: warning NOTE
-
-Currently, only the content manager uses this API to extend its current fields.
-
-:::
-
-### Registering a new field
-
-Registering a field can be made in two different ways:
-
-1. During the load phase of a plugin
-2. Using the provided `react-hook` in a component.
-
-#### Registering a field during the load of a plugin
-
-Registering a field during the load phase of a plugin can be done as follows:
-
-1. Create a new Field type (in this example a **`media`** field type):
-
-**Path —** `plugins/my-plugin/admin/src/components/InputMedia/index.js`.
-
-```js
-import React from 'react';
-const InputMedia = props => {
- // Check out the provided props
- console.log(props);
-
- return InputMedia
;
-};
-
-export default InputMedia;
-```
-
-2. Register the field into the application:
-
-**Path —** `plugins/my-plugin/admin/src/index.js`.
-
-```js
-import pluginPkg from '../../package.json';
-import InputMedia from './components/InputMedia';
-import pluginId from './pluginId';
-
-export default strapi => {
- const pluginDescription = pluginPkg.strapi.description || pluginPkg.description;
-
- const plugin = {
- blockerComponent: null,
- blockerComponentProps: {},
- description: pluginDescription,
- icon: pluginPkg.strapi.icon,
- id: pluginId,
- initializer: () => null,
- injectedComponents: [],
- isReady: true,
- mainComponent: null,
- name: pluginPkg.strapi.name,
- preventComponentRendering: false,
- trads: {},
- };
-
- strapi.registerField({ type: 'media', Component: InputMedia });
-
- return strapi.registerPlugin(plugin);
-};
-```
-
-By doing so, all the plugins from your project will be able to use the newly registered **Field** type.
-
-#### Registering a field inside a React Component
-
-The other way to register a **Field** is to use the provided `react-hook`: **`useStrapi`** it can be done in the `Initializer` Component so it is accessible directly when the user is logged in, if you decide to register your plugin in another component than the `Initializer` the **Field** will only be registered in the administration panel once the component is mounted (the user has navigated to the view where the **Field** is registered).
-
-1. Register the **Field** in the `Initializer` Component:
-
-**Path —** `plugins/my-plugin/admin/src/containers/Initializer/index.js`.
-
-```js
-/**
- *
- * Initializer
- *
- */
-
-import { useEffect, useRef } from 'react';
-import PropTypes from 'prop-types';
-import { useStrapi } from 'strapi-helper-plugin';
-import pluginId from '../../pluginId';
-import InputMedia from './components/InputMedia';
-
-const Initializer = ({ updatePlugin }) => {
- const {
- strapi: { fieldApi },
- } = useStrapi();
- const ref = useRef();
- ref.current = updatePlugin;
-
- useEffect(() => {
- // Register the new field
- fieldApi.registerField({ type: 'media', Component: InputMedia });
-
- ref.current(pluginId, 'isReady', true);
- }, []);
-
- return null;
-};
-
-Initializer.propTypes = {
- updatePlugin: PropTypes.func.isRequired,
-};
-
-export default Initializer;
-```
-
-2. Add the `Initializer` component to your plugin so it is mounted in the administration panel once the user is logged in:
-
-```js
-import pluginPkg from '../../package.json';
-import pluginLogo from './assets/images/logo.svg';
-import App from './containers/App';
-import Initializer from './containers/Initializer';
-import lifecycles from './lifecycles';
-import trads from './translations';
-import pluginId from './pluginId';
-
-export default strapi => {
- const pluginDescription = pluginPkg.strapi.description || pluginPkg.description;
- const plugin = {
- blockerComponent: null,
- blockerComponentProps: {},
- description: pluginDescription,
- icon: pluginPkg.strapi.icon,
- id: pluginId,
- initializer: Initializer,
- injectedComponents: [],
- isRequired: pluginPkg.strapi.required || false,
- layout: null,
- lifecycles,
- mainComponent: App,
- name: pluginPkg.strapi.name,
- pluginLogo,
- preventComponentRendering: false,
- trads,
- };
-
- return strapi.registerPlugin(plugin);
-};
-```
-
-### Consuming the Field API
-
-Consuming the **Field** API can only be done by using the provided `react-hook` **`useStrapi`**. Here's an example from the **content-manager** plugin:
-
-**Path —** `~/strapi-plugin-content-manager/admin/src/components/Inputs/index.js`.
-
-```js
-import React, { memo, useMemo } from 'react';
-// Other imports
-// ...
-// Import the Inputs component from our component library Buffet.js
-import { Inputs as InputsIndex } from '@buffetjs/custom';
-
-// Import the Hook with which you can access the Field API
-import { useStrapi } from 'strapi-helper-plugin';
-
-function Inputs({ autoFocus, keys, layout, name, onBlur }) {
- // This is where you will access the field API
- const {
- strapi: { fieldApi },
- } = useStrapi();
-
- // Other boilerplate code
- // ...
-
- return (
-
- {error => {
- return (
-
- );
- }}
-
- );
-}
-```
-
-### Field API definition
-
-| Method | Param | Description |
-| :------------ | :------------ | :------------------------------------- |
-| getField | {String} type | Retrieve a Field depending on the type |
-| getFields | | Retrieve all the Fields |
-| registerField | {Object} | Register a Field |
-| removeField | | Remove a Field |
-
-
-## Plugin's front-end settings API
-
-As plugins developer you may need to add some settings into the main application **`Settings`** view (it corresponds to the `Settings` link located in the menu). To do so an API is available in order for a plugin to add links into the main view.
-
-These settings can be declared directly into the main plugin object so they will dynamically be injected into the view.
-
-### Adding a setting
-
-The front-end part of a plugin exports a function which registers the plugin in the administration panel. The argument is composed of two main parameters:
-
-- `registerPlugin`: `Function`
-- `settingsBaseURL`: `String`
-
-#### Creating the links into the view's menu
-
-Each plugin that comes with a setting object will create a new section into the view's menu.
-
-The menu section can be declared as follows:
-
-**Path —** `plugins/my-plugin/admin/src/index.js`.
-
-```js
-import pluginPkg from '../../package.json';
-import pluginId from './pluginId';
-
-export default strapi => {
- const pluginDescription = pluginPkg.strapi.description || pluginPkg.description;
-
- // Declare the links that will be injected into the settings menu
- const menuSection = {
- // Unique id of the section
- id: pluginId,
- // Title of Menu section using i18n
- title: {
- id: `${pluginId}.foo`,
- defaultMessage: 'Super cool setting',
- },
- // Array of links to be displayed
- links: [
- {
- // Using string
- title: 'Setting page 1',
- to: `${strapi.settingsBaseURL}/${pluginId}/setting1`,
- name: 'setting1',
- permissions: [{ action: 'plugins::my-plugin.action-name', subject: null }], // This key is not mandatory it can be null, undefined or an empty array
- },
- {
- // Using i18n with a corresponding translation key
- title: {
- id: `${pluginId}.bar`,
- defaultMessage: 'Setting page 2',
- },
- to: `${strapi.settingsBaseURL}/${pluginId}/setting2`,
- name: 'setting2',
- // Define a specific component if needed:
- Component: () => ,
- },
- ],
- };
-
- const plugin = {
- blockerComponent: null,
- blockerComponentProps: {},
- description: pluginDescription,
- icon: pluginPkg.strapi.icon,
- id: pluginId,
- initializer: () => null,
- injectedComponents: [],
- isReady: true,
- mainComponent: null,
- name: pluginPkg.strapi.name,
- preventComponentRendering: false,
- settings: {
- menuSection,
- },
- trads: {},
- };
-
- return strapi.registerPlugin(plugin);
-};
-```
-
-At this point, the plugin creates a new section (**_Super cool setting_**) which will contains two links `Setting page 1` and `Setting page 2` these links don't point to any component as the corresponding one as not been declared yet.
-
-#### Declaring the setting Component
-
-The exported Setting component which receives `settingsBaseURL` as props in order to generate a dynamic routing which should be used to associate the two endpoints created with their corresponding components.
-
-With the configuration from above we could easily create our plugin Settings view.
-
-**Path —** `plugins/my-plugin/admin/src/containers/Settings/index.js`.
-
-```js
-import React from 'react';
-import PropTypes from 'prop-types';
-import { Switch, Route } from 'react-router-dom';
-import pluginId from '../../pluginId';
-
-const SettingPage1 = () => (
-
-
Setting Page 1
-
-);
-const SettingPage2 = () => (
-
-
Setting Page 2
-
-);
-
-const Settings = ({ settingsBaseURL }) => {
- return (
-
-
-
-
- );
-};
-
-Settings.propTypes = {
- settingsBaseURL: PropTypes.string.isRequired,
-};
-
-export default Settings;
-```
-
-Now that the `Settings` component is declared in your plugin the only thing left is to add it to your settings configuration:
-
-**Path —** `plugins/my-plugin/admin/src/index.js`.
-
-```js
-import pluginPkg from '../../package.json';
-// Import the component
-import Settings from './containers/Settings';
-import pluginId from './pluginId';
-
-export default strapi => {
- const pluginDescription = pluginPkg.strapi.description || pluginPkg.description;
-
- // Declare the links that will be injected into the settings menu
- const menuSection = {
- id: pluginId,
- title: {
- id: `${pluginId}.foo`,
- defaultMessage: 'Super cool setting',
- },
- links: [
- {
- title: 'Setting page 1',
- to: `${strapi.settingsBaseURL}/${pluginId}/setting1`,
- name: 'setting1',
- permissions: [{ action: 'plugins::my-plugin.action-name', subject: null }],
- },
- {
- title: {
- id: `${pluginId}.bar`,
- defaultMessage: 'Setting page 2',
- },
- to: `${strapi.settingsBaseURL}/${pluginId}/setting2`,
- name: 'setting2',
- },
- ],
- };
-
- const plugin = {
- blockerComponent: null,
- blockerComponentProps: {},
- description: pluginDescription,
- icon: pluginPkg.strapi.icon,
- id: pluginId,
- initializer: () => null,
- injectedComponents: [],
- isReady: true,
- mainComponent: null,
- name: pluginPkg.strapi.name,
- preventComponentRendering: false,
- settings: {
- mainComponent: Settings,
- menuSection,
- },
- trads: {},
- };
-
- return strapi.registerPlugin(plugin);
-};
-```
-
-### Adding a setting into the global section
-
-In order to add a link into the global section of the settings view you need to create a global array containing the links you want to add:
-
-**Path —** `plugins/my-plugin/admin/src/index.js`.
-
-```js
-import pluginPkg from '../../package.json';
-// Import the component
-import Settings from './containers/Settings';
-import SettingLink from './components/SettingLink';
-import pluginId from './pluginId';
-
-export default strapi => {
- const pluginDescription = pluginPkg.strapi.description || pluginPkg.description;
-
- // Declare the links that will be injected into the settings menu
- const menuSection = {
- id: pluginId,
- title: {
- id: `${pluginId}.foo`,
- defaultMessage: 'Super cool setting',
- },
- links: [
- {
- title: 'Setting page 1',
- to: `${strapi.settingsBaseURL}/${pluginId}/setting1`,
- name: 'setting1',
- },
- {
- title: {
- id: `${pluginId}.bar`,
- defaultMessage: 'Setting page 2',
- },
- to: `${strapi.settingsBaseURL}/${pluginId}/setting2`,
- name: 'setting2',
- },
- ],
- };
-
- const plugin = {
- blockerComponent: null,
- blockerComponentProps: {},
- description: pluginDescription,
- icon: pluginPkg.strapi.icon,
- id: pluginId,
- initializer: () => null,
- injectedComponents: [],
- isReady: true,
- mainComponent: null,
- name: pluginPkg.strapi.name,
- preventComponentRendering: false,
- settings: {
- // Add a link into the global section of the settings view
- global: {
- links: [
- {
- title: 'Setting link 1',
- to: `${strapi.settingsBaseURL}/setting-link-1`,
- name: 'settingLink1',
- Component: SettingLink,
- // Bool : https://reacttraining.com/react-router/web/api/Route/exact-bool
- exact: false,
- permissions: [{ action: 'plugins::my-plugin.action-name', subject: null }],
- },
- ],
- },
- mainComponent: Settings,
- menuSection,
- },
- trads: {},
- };
-
- return strapi.registerPlugin(plugin);
-};
-```
-
-::: danger
-It is currently not possible to add a link into another plugin's setting section
-:::
diff --git a/docs/developer-docs/latest/development/plugin-customization.md b/docs/developer-docs/latest/development/plugin-customization.md
deleted file mode 100644
index 2bd3159c39..0000000000
--- a/docs/developer-docs/latest/development/plugin-customization.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Strapi plugins - Strapi Developer Documentation
-description: In Strapi you can install plugins in your node_modules. This allows for easy updates and respect best practices.
----
-
-# Strapi plugins
-
-In Strapi you can install plugins in your `node_modules`. This allows for easy updates and respect best practices. To customize those installed plugins you can work in the `/extensions` directory. It contains all the plugins' customizable files.
-
-Some plugins will create files in these folders so you can then modify them. You can also create certain files manually to add some custom configuration.
-
-Extensions folder structure:
-
-- `extensions/`
- - `**`: Plugin Id
- - `admin`: You can extend a plugin's admin by creating a file with the same name, doing so will override the original one.
- - `config`: You can extend a plugin's configuration by adding a settings.json file with your custom configuration.
- - `models`: Contains the plugin's models that you have overwritten (e.g. when you add a relation to the User model).
- - `controllers`: You can extend the plugin's controllers by creating controllers with the same names and override certain methods.
- - `services`: You can extend the plugin's services by creating services with the same names and override certain methods.
-
-::: warning
-When using **extensions** you will need to update your code whenever you upgrade your strapi version. Not updating and comparing your **extensions** with the new changes on the repository, can break your app in unexpected ways that we cannot predict in the [migration guides](/developer-docs/latest/update-migration-guides/migration-guides.md).
-:::
-
-
-
-
diff --git a/docs/developer-docs/latest/development/plugins-development.md b/docs/developer-docs/latest/development/plugins-development.md
new file mode 100644
index 0000000000..62572bdbb2
--- /dev/null
+++ b/docs/developer-docs/latest/development/plugins-development.md
@@ -0,0 +1,46 @@
+---
+title: Plugins development - Strapi Developer Docs
+description: Strapi allows you to create your own custom local plugins that will work exactly the same as external ones.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/plugins-development.html
+---
+
+# Plugins development
+
+Strapi allows you to create local plugins that work exactly like the external ones installed with npm or through the Marketplace.
+
+:::strapi Extending plugins
+If you would rather extend an existing plugin than create a new one, see the [Plugins extension](/developer-docs/latest/development/plugins-extension.md) documentation.
+:::
+
+## Creating a plugin
+
+To create a plugin, use Strapi CLI tools:
+
+1. (_Optional_) If you don't already have an existing project, create a new development project with `strapi new myDevelopmentProject`.
+2. Start the project with `cd myDevelopmentProject && strapi develop`.
+3. In a new terminal window, run `cd /path/to/myDevelopmentProject && strapi generate` to launch the interactive `strapi generate` CLI.
+4. Choose "plugin" from the list, press Enter, and give the plugin a name.
+5. Enable the plugin by adding it to the [plugins configurations](/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md) file:
+ ```js
+ // path: /path/to/myDevelopmentProject/config/plugins.js
+
+ module.exports = {
+ // ...
+ 'my-plugin': {
+ enabled: true,
+ resolve: './src/plugins/my-plugin' // path to plugin folder
+ },
+ // ...
+ }
+ ```
+5. Run `strapi build` to build the plugin.
+
+Plugins created this way are located in the `plugins` folder of the application (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)).
+
+## Adding features to a plugin
+
+Strapi provides programmatic APIs for your plugin to hook into some of Strapi's features.
+
+Plugins can register with the server and/or the admin panel, by looking for entry point files at the root of the package:
+ - `strapi-server.js` for the Server (see [Server API](/developer-docs/latest/developer-resources/plugin-api-reference/server.md)),
+ - `strapi-admin.js` for the admin panel (see [Admin Panel API](/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md)).
diff --git a/docs/developer-docs/latest/development/plugins-extension.md b/docs/developer-docs/latest/development/plugins-extension.md
new file mode 100644
index 0000000000..63517c029b
--- /dev/null
+++ b/docs/developer-docs/latest/development/plugins-extension.md
@@ -0,0 +1,125 @@
+---
+title: Plugins extension - Strapi Developer Docs
+description: Strapi plugins can be extended by extending the content-types or the plugin's interface.
+sidebarDepth: 2
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/plugins-extension.html
+---
+
+# Plugins extension
+
+Strapi comes with [plugins](/developer-docs/latest/plugins/plugins-intro.md) that can be installed from the Marketplace or as npm packages. You can also create your own plugins (see [plugins development](/developer-docs/latest/development/plugins-development.md)) or extend the existing ones.
+
+Plugin extensions code is located in the `./src/extensions` folder (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)). Some plugins automatically create files there, ready to be modified.
+
+:::details Example of extensions folder structure:
+
+```bash
+/extensions
+ /some-plugin-to-extend
+ strapi-admin.js
+ strapi-server.js
+ /content-types
+ /some-content-type-to-extend
+ model.json
+ /another-content-type-to-extend
+ model.json
+ /another-plugin-to-extend
+ strapi-admin.js
+```
+
+:::
+
+Plugins can be extended in 2 ways:
+
+- [extending the plugin's Content-Types](#extending-a-plugin-s-content-types)
+- [extending the plugin's interface](#extending-a-plugin-s-interface) (e.g. to add controllers, services, policies, middlewares and more)
+
+A plugin's Content-Types can be extended in 2 ways: using the programmatic interface within `strapi-server.js` and by overriding the content-types schemas.
+
+The final schema of the content-types depends on the following loading order:
+
+1. the content-types of the original plugin,
+2. the content-types overriden by the declarations in the [schema](/developer-docs/latest/development/backend-customization/models.md#model-schema) defined in `./src/extensions/plugin-name/content-types/content-type-name/schema.json`
+3. the content-types declarations in the [`content-types` key exported from `strapi-server.js`](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#content-types)
+4. the content-types declarations in the [`register()` function](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md#register) of the Strapi application
+
+:::warning
+New versions of Strapi are released with [migration guides](/developer-docs/latest/update-migration-guides/migration-guides.md), but these guides might not cover unexpected breaking changes in your plugin extensions. Consider forking a plugin if extensive customizations are required.
+:::
+
+## Extending a plugin's Content-Types
+
+To overwrite a plugin's [Content-Types](/developer-docs/latest/development/backend-customization/models.md):
+
+1. _(optional)_ Create the `./src/extensions` folder at the root of the app, if the folder does not already exist.
+2. Create a subfolder with the same name as the plugin to be extended.
+3. Create a `content-types` subfolder.
+4. Inside the `content-types` subfolder, create another subfolder with the same [singularName](/developer-docs/latest/development/backend-customization/models.md#model-information) as the content-type to overwrite.
+5. Inside this `content-types/name-of-content-type` subfolder, define the new schema for the Content-Type in a `schema.json` file (see [schema](/developer-docs/latest/development/backend-customization/models.md#model-schema) documentation).
+6. _(optional)_ Repeat steps 4 and 5 for each Content-Type to overwrite.
+
+## Extending a plugin's interface
+
+When a Strapi application is initializing, plugins, extensions and global lifecycle functions events happen in the following order:
+
+1. Plugins are loaded and their interfaces are exposed.
+2. Files in `./src/extensions` are loaded.
+3. The `register()` and `bootstrap()` functions in `./src/index.js` are called.
+
+A plugin's interface can be extended at step 2 (i.e. within `./src/extensions`) or step 3 (i.e. inside `./src/index.js`).
+
+### Within the extensions folder
+
+To extend a plugin's interface using the `./src/extensions` folder:
+
+1. _(optional)_ Create the `./src/extensions` folder at the root of the app, if the folder does not already exist.
+2. Create a subfolder with the same name as the plugin to be extended.
+3. Depending on what needs to be extended:
+ * create a `strapi-server.js` file to extend a plugin's back end using the [Server API](/developer-docs/latest/developer-resources/plugin-api-reference/server.md)
+ * or create a `strapi-admin.js` file to extend the admin panel with the [Admin Panel API](/developer-docs/latest/developer-resources/plugin-api-reference/admin-panel.md).
+4. Within this file, define and export a function. The function receives the `plugin` interface as an argument so it can be extended.
+
+::: details Example of backend extension
+
+```js
+// path: ./src/extensions/some-plugin-to-extend/strapi-server.js
+
+module.exports = (plugin) => {
+ plugin.controllers.controllerA.find = (ctx) => {};
+
+ plugin.policies[newPolicy] = (ctx) => {};
+
+ plugin.routes.push({
+ method: 'GET',
+ path: '/route-path',
+ handler: 'controller.action',
+ });
+
+ return plugin;
+};
+```
+
+:::
+
+### Within the register and bootstrap functions
+
+To extend a plugin's interface within `./src/index.js`, use the `bootstrap()` and `register()` [functions](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md) of the whole project, and access the interface programmatically with [getters](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#usage).
+
+::: details Example of extending a plugin's content-type within ./src/index.js
+
+```js
+// path: ./src/index.js
+
+module.exports = {
+ register({ strapi }) {
+ strapi.contentType('plugin::my-plugin.content-type-name').attributes = {
+ 'toto': {
+ type: 'string',
+ }
+ }
+ },
+ bootstrap({ strapi }) {},
+};
+```
+
+:::
diff --git a/docs/developer-docs/latest/development/plugins/graphql.md b/docs/developer-docs/latest/development/plugins/graphql.md
index b2e54b93a3..49b75dad29 100644
--- a/docs/developer-docs/latest/development/plugins/graphql.md
+++ b/docs/developer-docs/latest/development/plugins/graphql.md
@@ -11,25 +11,21 @@ By default Strapi create [REST endpoints](/developer-docs/latest/developer-resou
To get started with GraphQL in your app, please install the plugin first. To do that, open your terminal and run the following command:
-:::: tabs
+
-::: tab yarn
-
-```
-yarn strapi install graphql
-```
-
-:::
-
-::: tab npm
-
-```
+
+```sh
npm run strapi install graphql
```
+
-:::
+
+```sh
+yarn strapi install graphql
+```
+
-::::
+
Then, start your app and open your browser at [http://localhost:1337/graphql](http://localhost:1337/graphql). You should see the interface (**GraphQL Playground**) that will help you to write GraphQL query to explore your data.
@@ -37,6 +33,7 @@ Then, start your app and open your browser at [http://localhost:1337/graphql](ht
Usually you need to sign up or register before being recognized as a user then perform authorized requests.
+:::request Mutation
```graphql
mutation {
register(input: { username: "username", email: "email", password: "password" }) {
@@ -48,6 +45,7 @@ mutation {
}
}
```
+:::
You should see a new user is created in `Users` collection type in your Strapi admin panel.
@@ -55,6 +53,7 @@ You should see a new user is created in `Users` collection type in your Strapi a
To perform authorized requests, you must first get a JWT:
+:::request Mutation
```graphql
mutation {
login(input: { identifier: "email", password: "password" }) {
@@ -62,6 +61,7 @@ mutation {
}
}
```
+:::
Then on each request, send along an `Authorization` header in the form of `{ "Authorization": "Bearer YOUR_JWT_GOES_HERE" }`. This can be set in the HTTP Headers section of your GraphQL Playground.
@@ -75,7 +75,7 @@ You can also setup any [Apollo Server options](https://www.apollographql.com/doc
You can edit these configurations by creating following file.
-::: warning
+:::caution
Please note the setting for GraphQL `tracing` as changed and has been moved to `apolloServer.tracing`
:::
@@ -105,6 +105,7 @@ In the section, we assume that the [Shadow CRUD](#shadow-crud) feature is enable
- `id`: String
+:::request Query
```graphql
query {
user(id: "5aafe871ad624b7380d7a224") {
@@ -113,9 +114,11 @@ query {
}
}
```
+:::
### Fetch multiple entries
+:::request Query
```graphql
query {
users {
@@ -124,11 +127,13 @@ query {
}
}
```
+:::
### Fetch dynamic zone data
Dynamic zones are union types in graphql so you need to use fragments to query the fields.
+:::request Query
```graphql
query {
restaurants {
@@ -141,12 +146,14 @@ query {
}
}
```
+:::
### Create a new entry
- `input`: Object
- `data`: Object — Values to insert
+:::request Mutation
```graphql
mutation {
createUser(input: { data: { username: "John", email: "john@doe.com" } }) {
@@ -157,9 +164,11 @@ mutation {
}
}
```
+:::
The implementation of the mutations also supports relational attributes. For example, you can create a new `User` and attach many `Restaurant` to it by writing your query like this:
+:::request Mutation
```graphql
mutation {
createUser(
@@ -183,6 +192,7 @@ mutation {
}
}
```
+:::
### Update an existing entry
@@ -190,6 +200,7 @@ mutation {
- `where`: Object - Entry's ID to update
- `data`: Object — Values to update
+:::request Mutation
```graphql
mutation {
updateUser(
@@ -205,9 +216,11 @@ mutation {
}
}
```
+:::
You can also update relational attributes by passing an ID or an array of IDs (depending on the relationship).
+:::request Mutation
```graphql
mutation {
updateRestaurant(input: {
@@ -227,12 +240,14 @@ mutation {
}
}
```
+:::
### Delete an entry
- `input`: Object
- `where`: Object - Entry's ID to delete
+:::request Mutation
```graphql
mutation {
deleteUser(input: { where: { id: "5b28f1747c739e4afb48605c" } }) {
@@ -243,6 +258,7 @@ mutation {
}
}
```
+:::
### Filters
@@ -252,13 +268,12 @@ You can also apply different parameters to the query to make more complex querie
- `start` (integer): Define the amount of entries to skip.
- `sort` (string): Define how the data should be sorted.
- `publicationState` (PublicationState): Only select entries matching the publication state provided.
-- `locale` (string): Define the locale to fetch the content for, if the [Internationalization (i18n) plugin](/developer-docs/latest/development/plugins/i18n.md) is installed and [localization is enabled for the content-type](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-content-type).
Handled states are:
-
- `live`: Return only published entries (default)
- `preview`: Return both draft entries & published entries
+- `locale` (string): Define the locale to fetch the content for, if the [Internationalization (i18n) plugin](/developer-docs/latest/development/plugins/i18n.md) is installed and [localization is enabled for the content-type](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-content-type).
- `:asc` or `:desc`
- `where` (object): Define the filters to apply in the query.
- ``: Equals.
@@ -279,6 +294,7 @@ You can also apply different parameters to the query to make more complex querie
Return the second decade of users which have an email that contains `@strapi.io` ordered by username.
+:::request Query
```graphql
query {
users(limit: 10, start: 10, sort: "username:asc", where: { email_contains: "@strapi.io" }) {
@@ -294,9 +310,11 @@ query {
}
}
```
+:::
Return the users which have been created after the March, 19th 2018 4:21 pm.
+:::request Query
```graphql
query {
users(where: { createdAt_gt: "2018-03-19 16:21:07.161Z" }) {
@@ -305,12 +323,13 @@ query {
}
}
```
+:::
## Shadow CRUD
To simplify and automate the build of the GraphQL schema, we introduced the Shadow CRUD feature. It automatically generates the type definition, queries, mutations and resolvers based on your models. The feature also lets you make complex query with many arguments such as `limit`, `sort`, `start` and `where`.
-::: tip NOTE
+:::note
If you use a local plugin, the controller methods of your plugin are not created by default. In order for the Shadow CRUD to work you have to define them in your controllers for each of your models. You can find examples of controllers `findOne`, `find`, `create`, `update` and `delete` there : [Core controllers](/developer-docs/latest/development/backend-customization.md#controllers).
:::
@@ -371,7 +390,7 @@ The queries and mutations will use the generated controller's actions as resolve
## Aggregation & Grouping
-::: warning
+:::caution
This feature is only available on Mongoose ORM.
:::
@@ -439,6 +458,7 @@ type Query {
Getting the total count and the average likes of restaurants:
+:::request Query
```graphql
query {
restaurantsConnection {
@@ -451,9 +471,11 @@ query {
}
}
```
+:::
Let's say we want to do the same query but for only open restaurants
+:::request Query
```graphql
query {
restaurantsConnection(where: { open: true }) {
@@ -466,9 +488,12 @@ query {
}
}
```
+:::
Getting the average likes of open and non open restaurants
+:::: api-call
+:::request Query
```graphql
query {
restaurantsConnection {
@@ -487,9 +512,9 @@ query {
}
}
```
+:::
-Result
-
+:::response
```json
{
"data": {
@@ -522,6 +547,8 @@ Result
}
}
```
+:::
+::::
## Customize the GraphQL schema
@@ -720,7 +747,7 @@ One of the most powerful features of GraphQL is the auto-documentation of the sc
It might happen that you want to add a description to a query or deprecate it. To do that, you need to use the `schema.graphql.js` file.
-::: warning
+:::caution
The `schema.graphql.js` file has to be placed into the config folder of each API `./api/*/config/schema.graphql.js` or plugin `./extensions/*/config/schema.graphql.js`.
:::
@@ -946,7 +973,7 @@ The type name is the global ID of the model. You can find the global ID of a mod
We recommend putting the field description and deprecated reason in the model. Right now, the GraphQL plugin is the only which uses these fields. Another plugin could use this description in the future as well. However, sometimes you don't have the choice, especially when you're defining a custom type.
-::: tip
+:::note
It's not a bad practice to put the description and deprecated attribute in the `schema.graphql.js`, though.
:::
diff --git a/docs/developer-docs/latest/development/plugins/i18n.md b/docs/developer-docs/latest/development/plugins/i18n.md
deleted file mode 100644
index a7511b32ff..0000000000
--- a/docs/developer-docs/latest/development/plugins/i18n.md
+++ /dev/null
@@ -1,721 +0,0 @@
----
-title: Internationalization (i18n) - Strapi Developer Documentation
-description: Instructions on how to use Strapi Content API with the Internationalization (i18n) optional plugin
----
-
-
-
-# 🌍 Internationalization (i18n)
-
-The Internationalization (i18n) plugin allows Strapi users to create, manage and distribute localized content in different languages, called "locales". For more information about the concept of internationalization, please refer to the
-[W3C definition](https://www.w3.org/International/questions/qa-i18n.en#i18n).
-
-The i18n plugin:
-
-- allows admin panel users to create several localized versions of their content (see [user guide](/user-docs/latest/content-manager/translating-content.md))
-- allows developers to build localized projects by fetching and consuming the right content depending on the country/language of the audience.
-
-::: tip NOTE
-The i18n plugin does not automatically translate the users' content nor adapt the admin interface to languages specificities (e.g. displaying the admin panel in Right To Left format).
-:::
-
-## Installation
-
-::: warning PREREQUISITES
-The Internationalization plugin is installed by default on all Strapi applications running on version 3.6.0 or higher. For lower versions, a migration is needed (see [Update Strapi version](/developer-docs/latest/update-migration-guides/update-version.md)), as well as a manual installation of the plugin.
-:::
-
-The plugin can be installed:
-
-- [from the Marketplace](/user-docs/latest/plugins/installing-plugins-via-marketplace.md),
-- or using the Terminal, by running one of the following commands:
-
-:::: tabs
-
-::: tab yarn
-
-``` bash
-yarn strapi install i18n
-```
-
-:::
-
-::: tab npm
-
-``` bash
-npm run strapi install i18n
-```
-
-:::
-
-::::
-
-## Usage with Strapi Content API
-
-The i18n plugin adds new features to the [Content API](/developer-docs/latest/developer-resources/content-api/content-api.md):
-
-- a new [`locale`](#getting-localized-entries-with-the-locale-parameter) parameter to fetch content only for a specified locale
-- the ability to create a localized entry, either [from scratch](#creating-a-new-localized-entry) or [for an existing localized entry](#creating-a-localization-for-an-existing-entry)
-
-### Getting localized entries with the `locale` parameter
-
-The `locale` [API parameter](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters) can be used to fetch entries only for a specified locale. It takes a locale code as value (see [full list of available locales](https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-i18n/constants/iso-locales.json)).
-
-:::tip TIP
- To fetch content for a locale, make sure it has been already [added to Strapi in the admin panel](/user-docs/latest/settings/managing-global-settings.md#configuring-internationalization-locales).
-:::
-
-The format for a GET request is the following:
-
-```http
-GET /{content-type}?_locale={locale-code}
-```
-
-Use `all` as a value for the locale code, as in `http://localhost:1337/restaurants?_locale=all`, to fetch entries for all locales that have been configured in the admin panel.
-
-If the `locale` parameter isn't defined, it will be set to the default locale. `en` is the default locale when i18n plugin is installed, so by default a GET request to `http://localhost:1337/restaurants` will return the same response as a request to `http://localhost:1337/restaurants?_locale=en`.
-
-::: tip TIP
-Another locale can be [set as the default locale](/user-docs/latest/settings/managing-global-settings.md#adding-a-new-locale) in the admin panel.
-:::
-
-When the i18n plugin is installed, the response to requests includes fields that are specific to internationalization:
-
-- `locale` (string) is the locale code for the content entry
-- `localizations` (array) lists the existing localizations for this content entry; these localizations objects have 3 properties:
- - `id` (number|string) is the id of the localized content entry
- - `locale`(string) is the locale code for the localized content entry
- - `published_at` (string) is the date and time when the localized content entry was [published](/developer-docs/latest/concepts/draft-and-publish.md#publishing-a-draft), in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format
-
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```http
-GET http://localhost:1337/restaurants?_locale=fr
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-[
- {
- "id": 4,
- "name": "Can Alegria",
- "description": "Can Alegria restaurant description in French",
- "locale": "fr",
- "localizations": [
- {
- "id": 3,
- "locale": "en",
- "published_at": "2021-04-07T10:10:31.949Z"
- }
- ]
- },
- {
- "id": 8,
- "name": "She's Cake",
- "description": "She's Cake restaurant description in French",
- "locale": "fr",
- "localizations": []
- }
-]
-```
-
-In the example response above:
-
-- restaurant with `"id": 4` is a French (`"locale": "fr"`) localization of the existing restaurant with `"id": 3` (created for the default `en` locale), as shown in the `localizations` object included in the response (see [creating a localization for an existing entry](#creating-a-localization-for-an-existing-entry)).
-- restaurant with `"id": "8"` was created from scratch using the API, passing the `locale: fr` in the request body (see [creating a new localized entry](#creating-a-new-localized-entry)).
-:::
-::::
-
-### Creating a new localized entry
-
-To create a localized entry from scratch, send a POST request to the Content API.
-
-If no locale has been passed in the request body, the entry is created using the default locale for the application:
-
-:::: tabs
-::: tab Request
-
-**Example request**
-
-```http
-POST http://localhost:1337/restaurants
-```
-
-```json
-{
- "name": "Oplato",
- "description": "Oplato restaurant description in English"
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "id": 5,
- "name": "Oplato",
- "description": "Oplato restaurant description in English",
- "locale": "en",
- "localizations": []
-}
-```
-
-:::
-::::
-
-To create a localized entry for a locale different from the default one, add the `locale` attribute to the body of the POST request:
-
-:::: tabs
-::: tab Request
-
-**Example request**
-
-```http
-POST http://localhost:1337/restaurants
-```
-
-```json
-{
- "name": "She's Cake",
- "description": "She's Cake restaurant description in French",
- "locale": "fr"
-}
-```
-
-:::
-
-::: tab Response
-**Example response**
-
-```json
-{
- "id": 8,
- "name": "She's Cake",
- "description": "She's Cake restaurant description in French",
- "locale": "fr",
- "localizations": []
-}
-```
-
-:::
-::::
-
-### Creating a localization for an existing entry
-
-To create another localization for an existing localized entry, send a POST request to the appropriate URL depending on the type of content:
-
-| Content-Type | Request URL format |
-|:----------------|:-----------------------------------------|
-| Collection type | `POST /{content-type}/:id/localizations` |
-| Single type | `POST /{content-type}/localizations` |
-
-When creating a localization for existing localized entries, the body of the POST request can only accept localized fields.
-
-::: tip TIP
-The Content-Type should have the [`createlocalization` permission](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#collection-and-single-types) enabled, otherwise the POST request will return a `403: Forbidden` status.
-:::
-
-#### Creating a localization for a collection type
-
-When sending a POST request to a collection type, Strapi will:
-
-1. use the `id` as a base entry for the non-localized fields and copy them in the new entry
-2. then create a new entry for the given locale and link it with the base entry.
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```http
-POST http://localhost:1337/restaurants/8/localizations
-```
-
-```json
-{
- "locale": "en",
- "name": "She's Cake",
- "description": "She's Cake restaurant description in English"
-}
-```
-
-This request:
-
-1. creates a new entry in `en`
-2. links the created entry with `restaurant:8` (they will share the same `localizations` object)
-3. copies every non-localized fields from `restaurant:8` into the new entry and keeps the localized fields from the request's body
-
-:::
-
-::: tab Response
-
-**Example reponse**
-
-```json
-{
- "id": 9,
- "name": "She's Cake",
- "description": "She's Cake restaurant description in English",
- "locale": "en",
- "localizations": [
- {
- "id": 8,
- "locale": "fr",
- "published_at": "2021-04-07T13:22:46.589Z"
- }
- ]
-}
-```
-
-:::
-
-::::
-
-#### Creating a localization for a single type
-
-:::: tabs
-
-::: tab Request
-
-**Example request**
-
-```http
-POST http://localhost:1337/homepage/localizations
-```
-
-```json
-{
- "locale": "fr",
- "title": "Bienvenue sur FoodAdvisor !"
-}
-```
-
-:::
-
-::: tab Response
-
-**Example reponse**
-
-```json
-{
- "id": 2,
- "title": "Bienvenue sur FoodAdvisor!",
- "locale": "fr",
- "localizations": [
- {
- "id": 1,
- "locale": "en",
- "published_at": "2021-04-14T12:49:37.055Z"
- }
- ]
-}
-```
-
-:::
-
-::::
-
-### Updating an entry
-
-Currently, it is not possible to change the locale of an existing localized entry.
-
-When updating a localized entry (with `PUT /{localized-content-type}/:id`), if you set a `locale` attribute in the request body, it will be ignored.
-
-## Usage with the GraphQL plugin
-
-The i18n plugin adds new features to the [GraphQL plugin](/developer-docs/latest/development/plugins/graphql.md):
-
-- The `locale` and `localizations` fields are added to the [GraphQL](https://graphql.org/) schema.
-- The GraphQL [query API](/developer-docs/latest/development/plugins/graphql.md#query-api) can be used to:
- - [query with the `locale` argument](#getting-localized-entries-with-graphql) on collection types and single types
- - [create new localizations with a mutation](#creating-new-localized-entries-with-graphql) for collection types and single types
- - [update](#updating-a-localized-single-type-with-graphql) and [delete](#deleting-a-localization-for-a-single-type-with-graphql) a localization with a mutation on single types
-
-### Getting localized entries with GraphQL
-
-Queries can use the `locale` argument to fetch entries only for a specified locale.
-
-::: tip TIP
-To fetch entries for all locales, use `locale: "all"` in the query.
-:::
-#### Fetching a collection type
-
-:::: tabs
-
-::: tab Query
-
-**Example query**
-
-```graphql
-query {
- restaurants(locale: "en") {
- id
- name
- locale
- localizations {
- id
- locale
- }
- }
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "data": {
- "restaurants": [
- {
- "id": "3",
- "name": "Can Alegria",
- "locale": "en",
- "localizations": [
- {
- "id": "4",
- "locale": "fr"
- }
- ]
- },
- {
- "id": "5",
- "name": "Oplato",
- "locale": "en",
- "localizations": []
- },
- {
- "id": "9",
- "name": "She's Cake",
- "locale": "en",
- "localizations": [
- {
- "id": "8",
- "locale": "fr"
- }
- ]
- }
- ]
- }
-}
-```
-
-:::
-
-::::
-#### Fetching a single type
-
-:::: tabs
-
-::: tab Query
-
-**Example query**
-
-```graphql
-query {
- homepage(locale: "en") {
- id
- title
- locale
- localizations {
- id
- locale
- }
- }
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "data": {
- "homepage": {
- "id": "1",
- "title": "Welcome on FoodAdvisor!",
- "locale": "en",
- "localizations": [
- {
- "id": "2",
- "locale": "fr"
- }
- ]
- }
- }
-}
-```
-
-:::
-
-::::
-
-
-### Creating new localized entries with GraphQL
-
-The `locale` field can be passed in the `data` object of the mutation to create a localized entry for this specific locale (for more information, see [create a new entry with the GraphQL plugin](/developer-docs/latest/development/plugins/graphql.md#create-a-new-entry)).
-
-#### Creating a new localization for a collection type
-
-
-:::: tabs
-
-::: tab Mutation
-
-**Example mutation**
-
-```graphql
-mutation {
- createRestaurantLocalization(
- input: { where: { id: 8 }, data: {
- locale: "en",
- name: "She's Cake",
- description: "She's Cake restaurant description in English"
- }}
- ) {
- id
- locale
- name
- description
- localizations {
- id
- locale
- description
- }
- }
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "data": {
- "createRestaurantLocalization": {
- "id": "9",
- "locale": "en",
- "name": "She's Cake",
- "description": "She's Cake restaurant description in English",
- "localizations": [
- {
- "id": "8",
- "locale": "fr",
- "description": "She's Cake restaurant description in French"
- }
- ]
- }
- }
-}
-
-```
-
-:::
-
-::::
-
-#### Creating a new localization for a single type
-
-:::: tabs
-
-::: tab Mutation
-
-**Example mutation**
-
-```graphql
-mutation {
- createHomepageLocalization(
- input: {
- data: {
- locale: "fr"
- title: "Bienvenue sur FoodAdvisor !"
- }
- }
- ) {
- id
- locale
- title
- localizations {
- id
- locale
- title
- }
- }
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "data": {
- "createHomepageLocalization": {
- "id": "2",
- "locale": "fr",
- "title": "Bienvenue sur FoodAdvisor !",
- "localizations": [
- {
- "id": "1",
- "locale": "en",
- "title": "Welcome on FoodAdvisor!"
- }
- ]
- }
- }
-}
-```
-:::
-
-::::
-
-### Updating a localized single type with GraphQL
-
-A `locale` argument can be passed in the mutation to update content for a given locale (for more information, see [update an existing entry with the GraphQL plugin](/developer-docs/latest/development/plugins/graphql.md#update-an-existing-entry)).
-
-Currently, it is not possible to change the locale of an existing localized entry. If you set a `locale` field in the `data` object of the mutation, it will be ignored.
-
-:::: tabs
-
-::: tab Mutation
-
-**Example mutation**
-
-```graphql
-mutation {
- updateHomepage(
- locale: "fr"
- input: { data: { title: "Bienvenue sur l'annuaire FoodAdvisor !" } }
- ) {
- homepage {
- id
- title
- }
- }
-}
-
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "data": {
- "updateHomepage": {
- "homepage": {
- "id": "2",
- "title": "Bienvenue sur l'annuaire FoodAdvisor !"
- }
- }
- }
-}
-```
-
-:::
-
-::::
-
-### Deleting a localization for a single type with GraphQL
-
-Pass the `locale` argument in the mutation to delete a specific localization for a single type:
-
-:::: tabs
-
-::: tab Mutation
-
-**Example mutation**
-
-```graphql
-mutation {
- deleteHomepage(locale: "fr") {
- homepage {
- id
- title
- }
- }
-}
-```
-
-:::
-
-::: tab Response
-
-**Example response**
-
-```json
-{
- "data": {
- "deleteHomepage": {
- "homepage": {
- "id": "2",
- "title": "Bienvenue sur FoodAdvisor !"
- }
- }
- }
-}
-```
-
-The response returns the entry that has just been deleted.
-
-:::
-
-::::
-
-## Configuration in production environments
-
-A `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` [environment variable](/developer-docs/latest/setup-deployment-guides/configurations.md#environment-variables) can be configured to set the initialization locale for your environment. The value used for this variable should be a string (see [full list of available locales](https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-i18n/constants/iso-locales.json)).
-
-This is useful when a Strapi app is deployed in production, with the i18n plugin installed and enabled on your content types for the first time. On a fresh i18n plugin installation, `en` is the default locale. So if the database does not contain any locale, and no `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` is set for the environment, the content of the content types with i18n enabled will be automatically migrated to the `en` locale. But if the `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` is defined, then the content will be migrated to this locale. Using this environment variable saves you from having to manually update the locale for existing content entries.
diff --git a/docs/developer-docs/latest/getting-started/introduction.md b/docs/developer-docs/latest/getting-started/introduction.md
index a0ca95c264..86d0fa2e3b 100644
--- a/docs/developer-docs/latest/getting-started/introduction.md
+++ b/docs/developer-docs/latest/getting-started/introduction.md
@@ -1,60 +1,14 @@
---
-title: Strapi Developer Documentation
+title: Strapi Developer Docs
description: This documentation contains all technical documentation related to the setup, deployment, update and customization of your Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/getting-started/introduction.html
---
-
-
-# Welcome to the Strapi developer documentation!
+# Welcome to the Strapi v4 developer documentation!
This documentation contains all technical documentation related to the setup, deployment, update and customization of your Strapi application.
-::: danger 🤓 Can't wait to start using Strapi?
+::: strapi Can't wait to start using Strapi?
You can directly head to the [Quick Start](quick-start.md)!
If demos are more your thing, we have a [video demo](https://youtu.be/zd0_S_FPzKg), or you can request a [live demo](https://strapi.io/demo)!
:::
@@ -68,22 +22,20 @@ As it goes hand in hand with the open-source ecosystem, Strapi is open to contri
- [`strapi/strapi`](https://github.com/strapi/strapi): main repository of Strapi, which contains the core of the project. You can find the admin panel, core plugins, plugin providers, and the whole code that runs your Strapi application. Please read the [`CONTRIBUTING.md`](https://github.com/strapi/strapi/blob/master/CONTRIBUTING.md) file to have more information about contributions to the main repository.
- [`strapi/documentation`](https://github.com/strapi/documentation): contains the whole documentation of Strapi. Please read the [contribution guide](https://github.com/strapi/documentation/blob/main/CONTRIBUTING.md) to have more information about contributions to the Strapi documentation.
-- [`strapi/buffet`](https://github.com/strapi/buffet): [Buffet](https://buffetjs.io) is the component library that is used in the admin panel. It brings consistency between the different admin plugins.
+- [`strapi/design-system`](https://github.com/strapi/design-system): is the design system that is used in the admin panel. It brings consistency between the different admin plugins.
- [`strapi/strapi-docker`](https://github.com/strapi/strapi-docker): contains the code used to generate the official Docker images for Strapi (available through our [Docker Hub](https://hub.docker.com/r/strapi/strapi)).
- [`strapi/awesome-strapi`](https://github.com/strapi/awesome-strapi): contains everything the community built and all managed plugins. It is used as a central place to find and submit new packages such as plugins, middlewares, hooks, and general enhancements to the core of Strapi.
-
## Strapi Community
Strapi is a community-oriented project with an emphasis on transparency. The Strapi team has at heart to share their vision and build the future of Strapi with the Strapi community. This is why the [roadmap](https://portal.productboard.com/strapi) is open: as all insights are very important and will help steer the project in the right direction, any community member is most welcome to share ideas and opinions there.
Community members also take great part in providing the whole community a plethora of resources about Strapi. You can find [tutorials](https://strapi.io/tutorials/) on the Strapi website, where you can also create your own. Also, as an open-source project, the technical documentation of Strapi is open to contributions (see [Open-source & Contribution](#open-source-contribution)).
-::: danger 🤓 Want to join the community?
-You can join [GitHub](https://github.com/strapi/strapi) and the [forum](https://forum.strapi.io/) and share your ideas and opinions with other community members and members of the Strapi team. If you're looking for news and updates about Strapi, [Twitter](https://twitter.com/strapijs) and the [blog](https://strapi.io/blog) are pretty good places to start!
+::: strapi Want to join the community?
+You can join [GitHub](https://github.com/strapi/strapi), the [Forum](https://forum.strapi.io/), and the [Discord](https://discord.strapi.io) to share your ideas and opinions with other community members and members of the Strapi team. If you're looking for news and updates about Strapi, [Twitter](https://twitter.com/strapijs) and the [blog](https://strapi.io/blog) are pretty good places to start!
:::
-
## Support
Strapi is offered as free and open-source for users who wish to self-host the software. When having an issue or a question, the [forum](https://forum.strapi.io) is great first place to reach out for help. Both the Strapi community and core developers often check this platform and answer posts.
diff --git a/docs/developer-docs/latest/getting-started/quick-start.md b/docs/developer-docs/latest/getting-started/quick-start.md
index 2ac38627ed..cb3a82e365 100644
--- a/docs/developer-docs/latest/getting-started/quick-start.md
+++ b/docs/developer-docs/latest/getting-started/quick-start.md
@@ -1,8 +1,9 @@
---
-title: Quick Start Guide - Strapi Developer Documentation
+title: Quick Start Guide - Strapi Developer Docs
description: Get ready to get Strapi, your favorite open-source headless cms up and running in less than 3 minutes.
sidebarDepth: 0
next: ./troubleshooting
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/getting-started/quick-start.html
---
# Quick Start Guide
@@ -34,51 +35,6 @@ next: ./troubleshooting
padding-left: .3em;
}
- /*
- We override the :::warning and :::danger callouts for specific uses here.
- The CSS is scoped so this won't affect the rest of the docs.
-
- Eventually this will be turned into custom blocks or VuePress components,
- once I understand better how markdown-it and markdown-it-custom-block work.
- */
- .custom-block.congrats,
- .custom-block.warning,
- .custom-block.danger {
- border-left-width: .25rem;
- }
-
- .custom-block.warning {
- background-color: #f8f8f8;
- border-color: #bbbbba;
- }
-
- .custom-block.warning,
- .custom-block.danger {
- margin-top: 2em;
- margin-bottom: 2em;
-
- .custom-block-title, p, li {
- color: rgb(44, 62, 80);
- }
- a {
- color: #007eff;
- }
- }
-
- .custom-block.danger {
- background-color: rgba(129,107,250, .05);
- border-color: rgb(129,107,250);
-
- .custom-block-title {
- color: rgb(129,107,250);
- font-weight: bold;
- }
- }
-
- .custom-block.details {
- color: rgb(44, 62, 80);
- }
-
@@ -110,12 +66,6 @@ next: ./troubleshooting
border: solid 1px #bbbbba !important;
}
- .el-tabs--card > .el-tabs__header > .el-tabs__nav-wrap > .el-tabs__nav-scroll > .el-tabs__nav > .el-tabs__item.is-active {
- /* border: none; */
- /* height: 62px; */
- /* border-bottom: solid 1px red !important; */
- }
-
.el-tabs--card > .el-tabs__header > .el-tabs__nav-wrap > .el-tabs__nav-scroll > .el-tabs__nav > .el-tabs__item:first-child {
border-radius: 8px 0 0 8px !important;
border-right: none !important;
@@ -136,41 +86,42 @@ next: ./troubleshooting
Strapi offers a lot of flexibility. Whether you want to go fast and quickly see the final result, or would rather dive deeper into the product, we got you covered.
-:::warning PREREQUISITES
-
+::: prerequisites
Make sure [Node.js and npm are properly installed](/developer-docs/latest/setup-deployment-guides/installation/cli.md#preparing-the-installation) on your machine. It is also possible to use Yarn instead of npm (see [install the Yarn package](https://yarnpkg.com/en/)).
-
:::
👇 Let's get started! Using the big buttons below, please choose between:
-* the **Hands-on** path for a DIY approach to run your project
-* or the **Starters** path for the quickest way to spin up a fullstack application powered by a Strapi back end.
+- the **Hands-on** path for a DIY approach to run your project
+- or the **Starters** path for the quickest way to spin up a fullstack application powered by a Strapi back end.
:::::: tabs type:card
+
::::: tab Hands-on
-## 🚀 Part A: Create a new project with Strapi
+## 🚀 Part A: Create a new project with Strapi
### Step 1: Run the installation script
Run the following command in a terminal:
-:::: tabs card
-::: tab npm
+
+
+
```bash
- npx create-strapi-app my-project --quickstart
+npx create-strapi-app@latest my-project --quickstart
```
-:::
+
-::: tab yarn
+
```bash
- yarn create strapi-app my-project --quickstart
+yarn create strapi-app my-project --quickstart
```
-:::
-::::
+
+
+
### Step 2: Register the first administrator user
@@ -180,9 +131,9 @@ By completing the form, you create your own account. Once done, you become the f
You now have access to the [admin panel](http://localhost:1337/admin):
-
+
-:::warning 🥳 CONGRATULATIONS!
+::: callout 🥳 CONGRATULATIONS!
You have just created a new Strapi project! You can start playing with Strapi and discover the product by yourself using our [User Guide](/user-docs/latest/getting-started/introduction.md), or proceed to part B below.
:::
@@ -198,92 +149,93 @@ The admin panel of Strapi runs at [http://localhost:1337/admin](http://localhost
If the server is not already running, in your terminal, `cd` into the `my-project` folder and run `npm run develop` (or `yarn develop`) to launch it.
:::
-### Step 1: Create collection types with the Content-Types Builder
+### Step 1: Create collection types with the Content-Type Builder
-The Content-Types Builder plugin helps you create your data structure. When creating an empty project with Strapi, this is where to get the party started!
+The Content-Type Builder plugin helps you create your data structure. When creating an empty project with Strapi, this is where to get the party started!
#### Create a "Restaurant" collection type
Your restaurants directory will eventually include many restaurants, so we need to create a "Restaurant" collection type. Then we can describe the fields to display when adding a new restaurant entry:
-1. Go to [Plugins > Content-Types Builder](http://localhost:1337/admin/plugins/content-type-builder) in the main navigation.
+1. Go to Plugins  [Content-Type Builder](http://localhost:1337/admin/plugins/content-type-builder) in the main navigation.
2. Click on **Create new collection type**.
-3. Type `restaurant` for the _Display name_, and click **Continue**.
+3. Type `Restaurant` for the _Display name_, and click **Continue**.
4. Click the Text field.
5. Type `name` in the _Name_ field.
6. Switch to the _Advanced Settings_ tab, and check the **Required field** and the **Unique field** settings.
-7. Click on **Add another Field**.
-8. Choose the Rich Text field.
+7. Click on **Add another field**.
+8. Choose the Rich text field.
9. Type `description` under the _Name_ field, then click **Finish**.
10. Finally, click **Save** and wait for Strapi to restart.
-
+
-Once Strapi has restarted, "Restaurants" is listed under Collection Types in the main navigation. Wow, you have just created your very first content type! It was so cool — let's create another one right now, just for pleasure.
+Once Strapi has restarted, "Restaurant" is listed under  _Content Manager > Collection types_ in the navigation. Wow, you have just created your very first content type! It was so cool — let's create another one right now, just for pleasure.
#### Create a "Category" collection type
It would help getting a bit more organized if our restaurants directory had some categories. Let's create a "Category" collection type:
-1. Go to [Plugins > Content-Types Builder](http://localhost:1337/admin/plugins/content-type-builder) in the main navigation.
+1. Go to Plugins  [Content-Type Builder](http://localhost:1337/admin/plugins/content-type-builder) in the main navigation.
2. Click on **Create new collection type**.
-3. Type `category` for the _Display name_, and click **Continue**.
+3. Type `Category` for the _Display name_, and click **Continue**.
4. Click the Text field.
5. Type `name` in the _Name_ field.
6. Switch to the _Advanced Settings_ tab, and check the **Required field** and the **Unique field** settings.
-7. Click on **Add another Field**.
+7. Click on **Add another field**.
8. Choose the Relation field.
9. On the right side, click the _Category_ relational fields box and select "Restaurant".
10. In the center, select the icon that represents "many-to-many" . The text should read `Categories has and belongs to many Restaurants`.
-
+
9. Finally, click **Finish**, then the **Save** button, and wait for Strapi to restart.
### Step 2: Use the collection types to create new entries
Now that we have created a basic data structure with 2 collection types, "Restaurant" and "Category", let's use them to actually add content by creating new entries.
+
#### Create an entry for the "Restaurant" collection type
-1. Go to [Collection types > Restaurants](http://localhost:1337/admin/plugins/content-manager/collectionType/application::restaurant.restaurant) in the main navigation.
-2. Click on **Add New Restaurants**.
+1. Go to  [Content Manager > Collection types - Restaurant](http://localhost:1337/admin/content-manager/collectionType/api::restaurant.restaurant) in the navigation.
+2. Click on **Add new entry**.
3. Type the name of your favorite local restaurant in the _Name_ field. Let's say it's `Biscotte Restaurant`.
4. In the _Description_ field, write a few words about it. If you're lacking some inspiration, you can use `Welcome to Biscotte restaurant! Restaurant Biscotte offers a cuisine based on fresh, quality products, often local, organic when possible, and always produced by passionate producers.`
-5. Click **Save**.
+5. Click **Save**.
-The restaurant is now listed in the [Collection types > Restaurants](http://localhost:1337/admin/plugins/content-manager/collectionType/application::restaurant.restaurant) view.
+The restaurant is now listed in the [Collection types - Restaurant](http://localhost:1337/admin/content-manager/collectionType/api::restaurant.restaurant) view.
#### Add Categories
-Let's go to [Collection types > Categories](http://localhost:1337/admin/plugins/content-manager/collectionType/application::category.category) and create 2 categories:
+Let's go to  [Content Manager > Collection types - Category](http://localhost:1337/admin/content-manager/collectionType/api::category.category) and create 2 categories:
-1. Click on **Add New Categories**.
+1. Click on **Add new entry**.
2. Type `French Food` in the _Name_ field.
4. Click **Save**.
-5. Go back to _Collection types > Categories_, then click again on **Add New Categories**.
+5. Go back to _Collection types - Category_, then click again on **Add new entry**.
6. Type `Brunch` in the _Name_ field, then click **Save**.
-The "French Food" and "Brunch" categories are now listed in the [Collection types > Categories](http://localhost:1337/admin/plugins/content-manager/collectionType/application::category.category) view.
+The "French Food" and "Brunch" categories are now listed in the [Collection types - Category](http://localhost:1337/admin/content-manager/collectionType/api::category.category) view.
#### Add a Category to a Restaurant
-Go to [Collection types > Restaurants](http://localhost:1337/admin/plugins/content-manager/collectionType/application::restaurant.restaurant) in the main navigation, and click on "Biscotte Restaurant".
+Go to  [Content Manager > Collection types - Restaurant](http://localhost:1337/admin/content-manager/collectionType/api::restaurant.restaurant) in the navigation, and click on "Biscotte Restaurant".
-In the right sidebar, in the **Categories** drop-down list, select "Brunch". Click **Save**.
+In the right sidebar, in the **Categories** drop-down list, select "Brunch". Click **Save**.
### Step 3: Set Roles & Permissions
We have just added a restaurant and 2 categories. We now have enough content to consume (pun intended). But first, we need to make sure that the content is publicly accessible through the API:
-1. Click on _General > Settings_ at the bottom of the main navigation.
+1. Click on _General  Settings_ at the bottom of the main navigation.
2. Under _Users & Permissions Plugin_, choose [Roles](http://localhost:1337/admin/settings/users-permissions/roles).
3. Click the **Public** role.
4. Scroll down under _Permissions_.
-5. In the _Application_ tab, find _Restaurant_.
+5. In the _Permissions_ tab, find _Restaurant_ and click on it.
6. Click the checkboxes next to **find** and **findone**.
7. Repeat with _Category_: click the checkboxes next to **find** and **findone**.
8. Finally, click **Save**.
@@ -294,76 +246,67 @@ We have just added a restaurant and 2 categories. We now have enough content to
By default, any content you create is saved as a draft. Let's publish our categories and restaurant.
-First, navigate to [Collection types > Categories](http://localhost:1337/admin/plugins/content-manager/collectionType/application::category.category). From there:
+First, navigate to  [Content Manager > Collection types - Category](http://localhost:1337/admin/content-manager/collectionType/api::category.category). From there:
1. Click the "Brunch" entry.
2. On the next screen, click **Publish**.
-3. In the _Please confirm_ window, click **Yes, publish**.
+3. In the _Confirmation_ window, click **Yes, publish**.
-Then, go back to the Categories list and repeat for the "French food" category.
+Then, go back to the Categories list and repeat for the "French Food" category.
-Finally, to publish your favorite restaurant, go to [Collection types > Restaurants](http://localhost:1337/admin/plugins/content-manager/collectionType/application::restaurant.restaurant), click the restaurant entry, and **Publish** it.
+Finally, to publish your favorite restaurant, go to  [Content Manager > Collection types - Restaurant](http://localhost:1337/admin/content-manager/collectionType/api::restaurant.restaurant), click the restaurant entry, and **Publish** it.
+
### Step 5: Use the API
OK dear gourmet, we have just finished creating our content and making it accessible through the API. You can give yourself a pat on the back — but you have yet to see the final result of your hard work.
-There you are: the list of restaurants is accessible at [http://localhost:1337/restaurants](http://localhost:1337/restaurants).
+There you are: the list of restaurants is accessible at [http://localhost:1337/api/restaurants](http://localhost:1337/api/restaurants).
Try it now! The result should be similar to the example response below 👇.
::: details Click me to view an example of API response
```json
-[
- {
- "id":1,
- "name":"Biscotte Restaurant",
- "description":"Welcome to Biscotte restaurant! Restaurant Biscotte offers a cuisine based on fresh, quality products, often local, organic when possible, and always produced by passionate producers.",
- "published_at":"2021-05-27T15:46:43.097Z",
- "created_at":"2021-05-27T15:40:01.290Z",
- "updated_at":"2021-05-27T15:46:43.110Z",
- "categories":[
- {
- "id":1,
- "name":"French Food",
- "published_at":"2021-05-27T15:46:14.704Z",
- "created_at":"2021-05-27T15:41:59.725Z",
- "updated_at":"2021-05-27T15:46:14.725Z"
- },
- {
- "id":2,
- "name":"Brunch",
- "published_at":"2021-05-27T15:46:02.015Z",
- "created_at":"2021-05-27T15:42:29.201Z",
- "updated_at":"2021-05-27T15:46:02.035Z"
+{
+ "data": [
+ {
+ "id": 1,
+ "attributes": {
+ "name": "Biscotte Restaurant",
+ "description": "Welcome to Biscotte restaurant! Restaurant Biscotte offers a cuisine based on fresh, quality products, often local, organic when possible, and always produced by passionate producers.",
+ "createdAt": "2021-11-18T13:34:53.885Z",
+ "updatedAt": "2021-11-18T13:59:05.035Z",
+ "publishedAt": "2021-11-18T13:59:05.033Z"
}
- ]
+ }
+ ],
+ "meta": {
+ "pagination": {
+ "page": 1,
+ "pageSize": 25,
+ "pageCount": 1,
+ "total": 1
+ }
}
-]
+}
```
:::
-:::warning 🥳 CONGRATULATIONS!
+::: callout 🥳 CONGRATULATIONS!
Now your content is created, published, and you have permissions to request it through the API.
Keep on creating amazing content!
:::
-## ⏩ What to do next?
-
-### Consume your API
-
-You can learn how to consume your API with your favorite frameworks, front-end or back-end programming languages by choosing one in the list below.
+## ⏩ What to do next?
-
+Now that you know the basics of creating and publishing content with Strapi, we encourage you to explore and dig deeper into some Strapi features:
-### Deploy your project
-
-The next step is to deploy both your Strapi back end and the front end on the platforms of your choice.
-
-👉 You can deploy the Strapi back end on various services: Amazon AWS, Microsoft Azure, DigitalOcean, Google App Engine, Heroku, and many more (see our [Deployment guides](/developer-docs/latest/setup-deployment-guides/deployment.md)).
+- 👉 [create an API token](/user-docs/latest/settings/managing-global-settings.md#managing-api-tokens) to restrict access to your API,
+- 👉 learn how to use Strapi's [REST](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md) and [GraphQL](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md) APIs to query the content,
+- 👉 and [customize your Strapi back end](/developer-docs/latest/development/backend-customization.md) and [admin panel](/developer-docs/latest/development/admin-customization.md).
:::::
@@ -371,41 +314,44 @@ The next step is to deploy both your Strapi back end and the front end on the pl
## 🚀 Part A: Create a new project with Strapi starters
-Strapi [starters](https://strapi.io/starters) are the fastest way to kickstart your project. They cover many use cases (blog, e-commerce solution, corporate website, portfolio) and integrate with various technologies (Gatsby, Gridsome, Next, Nuxt).
+Strapi [starters](https://strapi.io/starters) are the fastest way to kickstart your project. They cover many use cases (blog, e-commerce solution, corporate website, portfolio) and integrate with various technologies (Next, Gridsome, Next, Nuxt).
-This quick start guide has been specifically tailored to use the [Gatsby blog starter](https://strapi.io/starters/strapi-starter-gatsby-blog). We highly recommend you to follow along with this starter. Once you get a better understanding of Strapi, you will be able to play with other starters on your own.
+This quick start guide has been specifically tailored to use the [Next blog starter](https://strapi.io/starters/strapi-starter-next-js-blog). We highly recommend you to follow along with this starter. Once you get a better understanding of Strapi, you will be able to play with other starters on your own.
### Step 1: Run the installation script
-To create a [Gatsby](https://www.gatsbyjs.com/) blog using Strapi, run the following command in a terminal:
+To create a [Next](https://nextjs.org/) blog using Strapi, run the following command in a terminal:
:::: tabs card
::: tab npm
+
```bash
- npx create-strapi-starter my-project gatsby-blog
+ npx create-strapi-starter my-project next-blog
```
+
:::
::: tab yarn
+
```bash
- yarn create strapi-starter my-project gatsby-blog
+ yarn create strapi-starter my-project next-blog
```
+
::::
During the installation, when terminal asks `Choose your installation type`: select the default `Quickstart (recommended)` option by pressing Enter. The installation then resumes — just let the magic happen!
### Step 2: Register & have a look at your blog
-Once the installation is complete, your browser automatically opens 2 tabs:
+Once the installation is complete, your browser automatically opens a tab at ([http://localhost:1337/admin/auth/register-admin](http://localhost:1337/admin/auth/register-admin)). It's for Strapi's admin panel, the back end of your application.
-* The first tab ([http://localhost:1337/admin/auth/register-admin](http://localhost:1337/admin/auth/register-admin)) is the admin panel, it's for the back end of your application.
-* The second tab ([http://localhost:8000](http://localhost:8000)) is for the front end of your application, and you can already see the Gatsby blog in action.
+By completing the form in the admin panel tab, you create your own account. Once done, you become the first administator user of this Strapi application. Welcome aboard, commander!
-
-
+Now, open [http://localhost:3000](http://localhost:3000) in another tab. This is the front end of your application, and you can already see the Next blog in action.
-By completing the form in the first tab, you create your own account. Once done, you become the first administator user of this Strapi application. Welcome aboard, commander!
+
+
-:::warning CONGRATULATIONS! 🥳
+:::callout CONGRATULATIONS! 🥳
Your blog is ready! You can start playing with Strapi and discover the product by yourself using our [User Guide](/user-docs/latest/getting-started/introduction.md), or proceed to part B below.
Writing a blog is not your cup of tea? You can leave this guide and play with other [Starters](https://strapi.io/starters) on your own.
@@ -417,7 +363,7 @@ Strapi [starters](https://strapi.io/starters) build a full stack application and
We are about to contribute to the blog we have just created. Let's play with your application, by adding yourself as a writer and creating your own article, updating the homepage, and restarting the servers to look at the final result.
-:::tip TIP
+:::tip
If the Strapi server is not already running, in your terminal, `cd` into the `my-project` folder and run `npm run develop` (or `yarn develop`) to launch it.
:::
@@ -425,7 +371,7 @@ If the Strapi server is not already running, in your terminal, `cd` into the `my
You have several ideas for great articles in mind. But first, the world needs to know who you are!
-Click on [Collection types > Writers](http://localhost:1337/admin/plugins/content-manager/collectionType/application::writer.writer?page=1&pageSize=10&_sort=name:ASC) in the main navigation, and click the **Add New Writers** button.
+Click on  [Content Manager > Collection types - Writer](http://localhost:1337/admin/content-manager/collectionType/api::writer.writer) in the navigation, and click the **Add new entry** button.
@@ -435,11 +381,11 @@ Click on [Collection types > Writers](http://localhost:1337/admin/plugins/conten
### Step 2: Write & publish your first article
-To write an article, we need to add a new entry to the "Articles" collection type and fill in a few fields.
+To write an article, we need to add a new entry to the "Article" collection type and fill in a few fields.
-Click on [Collection types > Articles](http://localhost:1337/admin/plugins/content-manager/collectionType/application::article.article?page=1&pageSize=10&_sort=title:ASC) in the main navigation, and click the **Add New Articles** button.
+Click on  [Content Manager > Collection types - Article](http://localhost:1337/admin/content-manager/collectionType/api::article.article) in the main navigation, and click the **Add new entry** button.
#### Give your article a title, a description, and add some content
@@ -454,19 +400,21 @@ In the sidebar on the right, choose your name in the _Author_ drop-down list. Yo
While there, you might also want to choose a _Category_ for your article from the list.
+🤓 Don't forget to click on **Save** to save the article.
+
#### Turn your draft into a publication
By default, your new article would be saved as a draft. Let's not be too shy and publish it right away.
To publish an article, click the **Publish** button at the top of the window.
-You have just created and published your first article, "Hello World!". You can find it in the [Collection types > Articles](http://localhost:1337/admin/plugins/content-manager/collectionType/application::article.article?page=1&pageSize=10&_sort=id:DESC) view.
+You have just created and published your first article, "Hello World!". You can find it in the  [Content Manager > Collection types - Article](http://localhost:1337/admin/content-manager/collectionType/api::article.article?page=1&pageSize=10&sort=id:DESC) view.
### Step 3: Update the `Homepage` single type
It's time to make this blog a bit more yours.
-Click on [Single Types > Homepage](http://localhost:1337/admin/plugins/content-manager/singleType/application::homepage.homepage) in the main navigation. Let's edit this homepage:
+Click on  [Content Manager > Single types - Homepage](http://localhost:1337/admin/content-manager/singleType/api::homepage.homepage) in the main navigation. Let's edit this homepage:
1. Replace the image in the _ShareImage_ field.
2. At the bottom of the page, update the _Title_ to `My Wonderful Strapi Blog` in the _Hero_ field group.
@@ -474,32 +422,26 @@ Click on [Single Types > Homepage](http://localhost:1337/admin/plugins/content-m
### Step 4: Restart the servers to reflect latest changes
-Gatsby is a static-site generator. It means that you need to restart the servers for changes to appear on the front end:
+Next is a static-site generator. It means that you need to restart the servers for changes to appear on the front end:
1. In your terminal, press `Ctrl-C` to stop the servers.
2. Make sure you are in the `my-project` folder. If not, type `cd my-project` and press Enter.
3. Restart the servers by typing `npm run develop` (or `yarn develop`) and press Enter.
-After a few moments, you should see your blog with its updated title running at [http://localhost:8000](http://localhost:8000). The "Hello World!" article you have just created is also visible at the bottom of the page.
+After a few moments, you should see your blog with its updated title running at [http://localhost:3000](http://localhost:3000). The "Hello World!" article you have just created is also visible at the bottom of the page.
-
+
-:::warning CONGRATULATIONS! 🥳
+:::callout CONGRATULATIONS! 🥳
Now you know how to use Strapi to create and update your blog. Keep on creating amazing content!
:::
-## ⏩ What to do next?
-
-The beauty of using Strapi [starters](https://strapi.io/starters) is that the Strapi back end comes with a front end ready out-of-the-box. Now you probably want to show your shiny new website to the world! The next step is then to deploy both the Strapi back end and the front end on the platforms of your choice:
-
-👉 You can deploy the Strapi back end on various services: Amazon AWS, Microsoft Azure, DigitalOcean, Google App Engine, Heroku, and many more (see our [Deployment guides](/developer-docs/latest/setup-deployment-guides/deployment.md)).
-
-👉 Deploying the front end mostly depends on the technology it's based on. The easiest way to deploy your Gatsby blog front end is probably to [deploy on Gatsby Cloud](https://support.gatsbyjs.com/hc/en-us/articles/360052324714-Connecting-to-Strapi).
+## ⏩ What to do next?
-:::danger 🤓 To go further with starters
+Now that you know the basics of kickstarting your project with a Strapi starter, we encourage you to explore and play a bit further:
-* Read more about the [starters CLI](https://strapi.io/blog/announcing-the-strapi-starter-cli) on our blog.
-* Start another project! We have lots of other [Starters](https://strapi.io/starters) you can use to kickstart your blog, e-commerce, corporate website, or portfolio project.
+* 👉 Start another project! We have lots of other [Starters](https://strapi.io/starters) you can use to kickstart your blog, e-commerce, corporate website, or portfolio project.
+* 👉 Read more about the [starters CLI](https://strapi.io/blog/announcing-the-strapi-starter-cli) on our blog.
:::::
diff --git a/docs/developer-docs/latest/getting-started/troubleshooting.md b/docs/developer-docs/latest/getting-started/troubleshooting.md
index 4725786c97..b99ce79127 100644
--- a/docs/developer-docs/latest/getting-started/troubleshooting.md
+++ b/docs/developer-docs/latest/getting-started/troubleshooting.md
@@ -1,7 +1,8 @@
---
-title: Troubleshooting - Strapi Developer Documentation
+title: Troubleshooting - Strapi Developer Docs
description: Find some answers and solutions to most common issues that you may experience when working with Strapi.
sidebarDepth: 0
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/getting-started/troubleshooting.html
---
# Frequently Asked Questions
@@ -10,7 +11,7 @@ Below are answers and solutions to most common issues that you may experience wh
## Why can't I create or update content-types in production/staging?
-Strapi stores model configuration files (what defines the model schema) in files such as `api/restaurant/models/restaurant.settings.json`. Due to how Node.js works, in order for changes to take effect, that would require Node to restart the server. This could potentially cause downtime of your production service and likewise these changes should be tracked in some kind of source control.
+Strapi stores model configuration files (what defines the model schema) in files such as `./src/api/restaurant/content-types/restaurant/schema.json`. Due to how Node.js works, in order for changes to take effect, that would require Node to restart the server. This could potentially cause downtime of your production service and likewise these changes should be tracked in some kind of source control.
Generally your "flow" of development would follow the following path:
@@ -19,7 +20,7 @@ Generally your "flow" of development would follow the following path:
- Production - If no other changes are needed, deploy into production
- Repeat as needed, it is recommended that you properly version and test your application as you go
-At this time and in the future there is no plan to allow model creating or updating while in a production environment, and there is currently no plans to move model settings into the database. There is no known nor recommended workarounds for this.
+At this time and in the future there is no plan to allow model creating or updating while in a production environment, and there is currently no plans to move model settings into the database. There are no known nor recommended workarounds for this.
## Does Strapi handle deploying or migrating of content?
@@ -44,13 +45,15 @@ With the components there is a hidden field called `order` that allows entries t
For the time being there is no recommended way to handle this automatically and instead it may be required for you to create custom controllers to handle this within your own project.
-## Why is my app's database and uploads resetting on PaaS
+We are evaluating if we will natively add support for this in the future. We will add more details when they become available.
+
+## Why are my application's database and uploads resetting on PaaS?
If you used `--quickstart` to create your Strapi project, by default this uses the SQLite database. PaaS systems (Heroku, DigitalOcean Apps, Google App Engine, ect) file systems are typically [ephemeral](https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem) or read-only meaning that each time a dyno (container) is reset all filesystem changes are lost. And since both SQLite and local uploads are stored on the filesystem, any changes made to these since the last dyno reset will be deleted. Typically dynos are reset at least once a day, and in most cases multiple times per day or when new code is pushed to these services.
-It is recommended you use a database add-on like Heroku's PostgreSQL or use something like MongoDB's Atlas for your database. For file uploads, you will need to use one of the 3rd party providers such as Cloudinary or AWS S3.
+It is recommended you use a database add-on like Heroku's PostgreSQL. For file uploads, you will need to use one of the 3rd party providers such as Cloudinary or AWS S3.
-## Can I store my Content Manager layout configurations in the model settings
+## Can I store my Content Manager layout configurations in the model settings?
Currently Strapi does not support this, a `config:dump` and `config:restore` command has been added to make migration of these settings easier when moving between different deployments and environments.
@@ -62,27 +65,29 @@ We don't offer the ability to store these configurations in the model settings f
For all these reasons, and others, we think it'll be a mistake and might confuse users if we store the configuration in the model settings file. The final solution is to make the migration and deployment across environment easier.
-## How do I customize a plugin
+## How do I customize a plugin?
-Strapi uses a system called [extensions](/developer-docs/latest/development/plugin-customization.md) as plugins are stored in the `node_modules` folder. Due to this extensions work by Strapi detecting newer versions of files and using that as a replacement for the ones stored within the `node_modules`. If you are familiar with React and "ejecting" a file, the concept is similar.
+Strapi uses a system called [extensions](/developer-docs/latest/development/plugins-extension) as plugins are stored in the `node_modules` folder. Due to this extensions work by Strapi detecting newer versions of files and using that as a replacement for the ones stored within the `node_modules`.
You gain the ability to modify these files without forking the plugin package, however you lose the ability to easily update. After each version release you will need to compare your changes to those in the new version and modify your version of the files accordingly.
-## Can I add my own 3rd party auth provider
+
+
+## Can I add my own 3rd party auth provider?
-Yes, you can either follow the following [guide](/developer-docs/latest/development/plugins/users-permissions.md#adding-a-new-provider-to-your-project) or you can take a look at the [users-permissions](https://github.com/strapi/strapi/tree/master/packages/strapi-plugin-users-permissions) and submit a pull request to include the provider for everyone. Eventually Strapi does plan to move from the current grant/purest provider to a split natured system similar to the upload providers.
+Yes, you can either follow the following [guide](/developer-docs/latest/plugins/users-permissions.md#adding-a-new-provider-to-your-project) or you can take a look at the [users-permissions](https://github.com/strapi/strapi/tree/master/packages/strapi-plugin-users-permissions) and submit a pull request to include the provider for everyone. Eventually Strapi does plan to move from the current grant/purest provider to a split natured system similar to the upload providers.
There is currently no ETA on this migration however.
-## Does Strapi allow me to change the default ID type or name
+## Does Strapi allow me to change the default ID type or name?
-No, currently does not have the ability to allow for changing the default id name nor does it allow you to switch the data type (such as UUID on bookshelf and integer on mongoose), support for this is being looked at for Strapi v4.
+No, currently does not have the ability to allow for changing the default id name nor does it allow you to switch the data type (such as UUID in PostgreSQL), support for this is being looked at in future.
-## Can you filter / deep filter on components, dynamic zones, and polymorphic relations
+## Can you filter and/or deep filter on dynamic zones and polymorphic relations?
-Currently it is not possible to filter on components, dynamic zones, or polymorphic relations. This is something we are looking into, if you want see more information please take a look at the following [GitHub issue](https://github.com/strapi/strapi/issues/5124).
+At this time we do not plan to allow for filtering on dynamic zones or polymorphic relations due to various complexity and performance issues that come from doing so.
-## How do I setup SSL with Strapi
+## How do I setup SSL with Strapi?
Strapi implements no SSL solution natively, this is due to the fact that it is extremely insecure to directly offer a Node.js application to the public web on a low port.
@@ -90,8 +95,10 @@ On Linux based operating systems you need root permissions to bind to any port b
Likewise since Strapi is Node.js based, in order for changes with the SSL certificate to take place (say when it expires) you would need to restart your application for that change to take effect.
-Due to these two issues, it is recommended you use a proxy application such as Nginx, Apache, Traefik, or many others to handle your edge routing to Strapi. There are settings in the environment [server.json](/developer-docs/latest/setup-deployment-guides/configurations.md#server) to handle upstream proxies. The proxy block requires all settings to be filled out and will modify any backend plugins such as authentication providers and the upload plugin to replace your standard `localhost:1337` with the proxy URL.
+Due to these two issues, it is recommended you use a proxy application such as [Nginx](/developer-docs/latest/setup-deployment-guides/deployment/optional-software/nginx-proxy), [Caddy](/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy), [HAProxy](/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy), Apache, Traefik, or many others to handle your edge routing to Strapi. There are settings in the environment [server.json](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md) to handle upstream proxies. The proxy block requires all settings to be filled out and will modify any backend plugins such as authentication providers and the upload plugin to replace your standard `localhost:1337` with the proxy URL.
-## Is X feature available yet
+## Is X feature available yet?
You can see the [ProductBoard roadmap](https://portal.productboard.com/strapi) to see which feature requests are currently being worked on and which have not been started yet.
+
+
diff --git a/docs/developer-docs/latest/getting-started/usage-information.md b/docs/developer-docs/latest/getting-started/usage-information.md
index ce717df02b..fab9e0eb6c 100644
--- a/docs/developer-docs/latest/getting-started/usage-information.md
+++ b/docs/developer-docs/latest/getting-started/usage-information.md
@@ -1,7 +1,8 @@
---
-title: Usage information - Strapi Developer Documentation
+title: Usage information - Strapi Developer Docs
description: We are committed to providing a solution, with Strapi, that exceeds the expectations of the users and community. We are also committed to continuing to develop and make Strapi even better than it is today.
sidebarDepth: 0
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/getting-started/usage-information.html
---
# Collected Usage Information
@@ -33,7 +34,7 @@ The following data is collected:
- System information (OS)
- Build configurations
-::: warning GDPR
+::: caution GDPR
The collected data are of a non-sensitive nature and no personal data is collected. We are compliant with the European GDPR recommendations (see our [Privacy Policy](https://strapi.io/privacy)). We do not collect databases configurations, password or custom variables. Any data collected (as above) is secured, encrypted and anonymized.
:::
@@ -54,6 +55,6 @@ Should you decide to opt-out, you may do so by removing the `uuid` property in t
}
```
-::: tip NOTE
+::: note
Should you have any questions regarding this feature, feel free to email [privacy@strapi.io](mailto:privacy@strapi.io).
:::
diff --git a/docs/developer-docs/latest/guides/api-token.md b/docs/developer-docs/latest/guides/api-token.md
deleted file mode 100644
index 81aa11b65b..0000000000
--- a/docs/developer-docs/latest/guides/api-token.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: API Tokens - Strapi Developer Documentation
-description: Learn in this guide how to create an API token system in your Strapi project to execute request as an authenticated user.
----
-
-# API tokens
-
-In this guide we will see how you can create an API token system to execute request as an authenticated user.
-
-This feature is in our [roadmap](https://portal.productboard.com/strapi/1-public-roadmap/c/40-api-access-token-with-permissions).
-This guide is a workaround to achieve this feature before we support it natively in strapi.
-
-## Introduction
-
-The goal is to be able to request API endpoints with a query parameter `token` that authenticates as a user. `eg. /restaurants?token=my-secret-token`.
-
-To achieve this feature in development, we will have to customize the `users-permissions` plugin. This guide will help you understand how to customize all your applications. You can read more about [Strapi plugins and customization](/developer-docs/latest/development/plugin-customization.md).
-
-## Create the Token Content Type
-
-To manage your tokens, you will have to create a new Content Type named `token`.
-
-- `string` attribute named `token`
-- `relation` attribute **Token** (`user`) - **Token** has and belongs to one **User** - **User** (`token`)
-
-Then add some users and create some token linked to these users.
-
-## Setup the file to override
-
-We now have to customize the function that verifies the `token` token. Strapi has an Authentication process that uses `JWT` tokens, we will reuse this function to customize the verification.
-
-[Here is the function](https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-users-permissions/config/policies/permissions.js) that manages the JWT validation.
-
-To be able to customize it, you will have to create a new file in your application `./extensions/users-permissions/config/policies/permissions.js`.
-
-Then copy the original function that is on GitHub and paste it in your new file.
-
-When it's done, the Strapi application will use this function instead of the core one. We are ready to customize it.
-
-## Add token validation logic
-
-You will have to update the first lines of this function.
-
-**Path —** `./extensions/users-permissions/config/policies/permissions.js`
-
-```js
-const _ = require('lodash');
-
-module.exports = async (ctx, next) => {
- let role;
-
- if (ctx.state.user) {
- // request is already authenticated in a different way
- return next();
- }
-
- // add the detection of `token` query parameter
- if (
- (ctx.request && ctx.request.header && ctx.request.header.authorization) ||
- (ctx.request.query && ctx.request.query.token)
- ) {
- try {
- // init `id` and `isAdmin` outside of validation blocks
- let id;
- let isAdmin;
-
- if (ctx.request.query && ctx.request.query.token) {
- // find the token entry that match the token from the request
- const [token] = await strapi.query('token').find({token: ctx.request.query.token});
-
- if (!token) {
- throw new Error(`Invalid token: This token doesn't exist`);
- } else {
- if (token.user && typeof token.token === 'string') {
- id = token.user.id;
- }
- isAdmin = false;
- }
-
- delete ctx.request.query.token;
- } else if (ctx.request && ctx.request.header && ctx.request.header.authorization) {
- // use the current system with JWT in the header
- const decoded = await strapi.plugins[
- 'users-permissions'
- ].services.jwt.getToken(ctx);
-
- id = decoded.id;
- isAdmin = decoded.isAdmin || false;
- }
-
- // this is the line that already exist in the code
- if (id === undefined) {
- throw new Error('Invalid token: Token did not contain required fields');
- }
-
- ...
-```
-
-And tada! You can now create a token, link it to a user and use it in your URLs with `token` as query parameters.
diff --git a/docs/developer-docs/latest/guides/auth-request.md b/docs/developer-docs/latest/guides/auth-request.md
index 437f2041ea..53583826c3 100644
--- a/docs/developer-docs/latest/guides/auth-request.md
+++ b/docs/developer-docs/latest/guides/auth-request.md
@@ -1,17 +1,20 @@
---
-title: Authenticated request - Strapi Developer Documentation
+title: Authenticated request - Strapi Developer Docs
description: Learn in this guide how you can request the API of your Strapi project as an authenticated user.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/auth-request.html
---
# Authenticated request
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide you will see how you can request the API as an authenticated user.
## Introduction
-To show you many of the concepts on the [roles and permissions](/developer-docs/latest/development/plugins/users-permissions.md) part, we will use many users and roles.
+To show you many of the concepts on the [roles and permissions](/developer-docs/latest/plugins/users-permissions.md) part, we will use many users and roles.
-After that we will see the [authentication workflow](/developer-docs/latest/development/plugins/users-permissions.md#authentication) to get a `JWT` and use it for an API request.
+After that we will see the [authentication workflow](/developer-docs/latest/plugins/users-permissions.md#authentication) to get a `JWT` and use it for an API request.
We will have one group of users that will be able to only fetch **Articles** and an other group that will be able to fetch, create and update **Articles**.
@@ -21,7 +24,7 @@ We will have one group of users that will be able to only fetch **Articles** and
Lets create a new Content Type **Article**
-- Click on `Content-Types Builder` in the left menu
+- Click on `Content-Type Builder` in the left menu
- Then `+ Create new content-type`
- Fill `Display name` with `article`
- Create 2 fields
@@ -64,13 +67,13 @@ Finally create **2 users** with the following data.
## Login as a Reader
-To login as a user your will have to follow the [login documentation](/developer-docs/latest/development/plugins/users-permissions.md#login).
+To login as a user your will have to follow the [login documentation](/developer-docs/latest/plugins/users-permissions.md#login).
Here is the API route for the authentication `/auth/local`.
You have to request it in **POST**.
-:::: tabs
+:::: tabs card
::: tab axios
diff --git a/docs/developer-docs/latest/guides/client.md b/docs/developer-docs/latest/guides/client.md
index fd18de0fe6..9395f9a116 100644
--- a/docs/developer-docs/latest/guides/client.md
+++ b/docs/developer-docs/latest/guides/client.md
@@ -1,10 +1,14 @@
---
-title: Client - Strapi Developer Documentation
+title: Client - Strapi Developer Docs
description: Learn in this guide how to setup a connection with a third party client and use it everywhere in your code.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/client.html
---
-
# Setup a third party client
+:::caution
+This guide is outdated as hooks have been removed from Strapi v4. We recommend taking advantage of [plugins](/developer-docs/latest/development/plugins-development.md) instead.
+:::
+
This guide will explain how to setup a connection with a third party client and use it everywhere in your code.
In our example we will use the GitHub Node.JS client [OctoKit REST.js](https://github.com/octokit/rest.js/).
@@ -15,21 +19,25 @@ This guide could also be used to setup an Axios client instance.
First you will have to install the client package in your application by running one of the following commands:
-:::: tabs
+:::: tabs card
::: tab yarn
-`yarn add @octokit/rest`
+```sh
+yarn add @octokit/rest
+```
:::
::: tab npm
-`npm install @octokit/rest`
+```sh
+npm install @octokit/rest
+```
:::
::::
## Create a hook
-To init the client, we will use the [hooks system](/developer-docs/latest/setup-deployment-guides/configurations.md#hooks). Hooks let you add new features in your Strapi application.
+To init the client, we will use the hooks system. Hooks let you add new features in your Strapi application.
Hooks are loaded once at server start.
diff --git a/docs/developer-docs/latest/guides/count-graphql.md b/docs/developer-docs/latest/guides/count-graphql.md
index 37b4325d9d..a6767774e7 100644
--- a/docs/developer-docs/latest/guides/count-graphql.md
+++ b/docs/developer-docs/latest/guides/count-graphql.md
@@ -1,17 +1,20 @@
---
-title: Count with GraphQL - Strapi Developer Documentation
+title: Count with GraphQL - Strapi Developer Docs
description: Learn in this guide how to count data with a GraphQL query.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/count-graphql.html
---
# Count with GraphQL
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
This guide explains how to count data with a GraphQL query.
The count aggregation currently has some issues and this feature is also not available for Bookshelf (SQL databases).
With this guide we will code our own count query.
-Here is the [GraphQL documentation](/developer-docs/latest/development/plugins/graphql.md#customize-the-graphql-schema) which we will use to achieve our goal.
+Here is the [GraphQL documentation](/developer-docs/latest/plugins/graphql.md#customization) which we will use to achieve our goal.
## Setup the application
@@ -36,7 +39,7 @@ module.exports = {
## Create count query
-The `count` query will call the [`count`](/developer-docs/latest/development/backend-customization.md#core-services) service function of the **Restaurant** API.
+The `count` query will call the [`count`](/developer-docs/latest/development/backend-customization/services.md#core-services) service function of the **Restaurant** API.
It needs a JSON object as params, so we will add a `where` options in the GraphQL query.
diff --git a/docs/developer-docs/latest/guides/custom-admin.md b/docs/developer-docs/latest/guides/custom-admin.md
index c19b3b596e..e921634d55 100644
--- a/docs/developer-docs/latest/guides/custom-admin.md
+++ b/docs/developer-docs/latest/guides/custom-admin.md
@@ -1,12 +1,14 @@
---
-title: Custom Admin - Strapi Developer Documentation
+title: Custom Admin - Strapi Developer Docs
description: Learn in this guide how you can customize the admin panel of your Strapi project.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/custom-admin.html
---
# Custom admin
-In this guide we will see how you can customize the admin panel.
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+In this guide we will see how you can customize the admin panel.
## Introduction
For this example, we will see two things:
@@ -36,7 +38,7 @@ In this new file, paste the current [HomePage container](https://github.com/stra
To run your application, run the following command:
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -114,7 +116,7 @@ In this new file, paste the current [dateFormats](https://github.com/strapi/stra
To run your application, run the following command:
-:::: tabs
+:::: tabs card
::: tab yarn
diff --git a/docs/developer-docs/latest/guides/custom-data-response.md b/docs/developer-docs/latest/guides/custom-data-response.md
index 8a590bb85f..9c6200d28b 100644
--- a/docs/developer-docs/latest/guides/custom-data-response.md
+++ b/docs/developer-docs/latest/guides/custom-data-response.md
@@ -1,19 +1,22 @@
---
-title: Custom Data Response - Strapi Developer Documentation
+title: Custom Data Response - Strapi Developer Docs
description: Learn in this guide how you can customize your Strapi project API's response.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/custom-date-response.html
---
# Custom data response
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how you can customize your API's response.
## Introduction
To be able to update the default data response you have first to understand how it works.
-When you create a content type, it generates an API with the following list of [endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+When you create a content type, it generates an API with the following list of [endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
-Each of these endpoint triggers a controller action. Here is the list of [controller actions](/developer-docs/latest/development/backend-customization.md#controllers) that exist by default when a content type is created.
+Each of these endpoint triggers a controller action. Here is the list of [controller actions](/developer-docs/latest/development/backend-customization/controllers.md) that exist by default when a content type is created.
If you check the controller file of your generated API `./api/{content-type}/controller/{Content-Type}.js`, you will see an empty file. It is because all the default logic is managed by Strapi. But you can override these actions with your own code.
@@ -57,7 +60,7 @@ After saving the new function, let's restart the `GET /restaurants` request. We
We now know the function we have to update, but we just want to customize the returned restaurant values.
-In the [controller documentation](/developer-docs/latest/development/backend-customization.md#extending-a-model-controller) you will find the default implementation of every actions. It will help you overwrite the fetch logic.
+In the [controller documentation](/developer-docs/latest/development/backend-customization/controllers.md#extending-core-controllers) you will find the default implementation of every actions. It will help you overwrite the fetch logic.
**Path —** `./api/restaurant/controller/Restaurant.js`
@@ -115,6 +118,6 @@ module.exports = {
And tada! The email disappeared.
-::: tip
+:::tip
This guide can be applied to any other controller action.
:::
diff --git a/docs/developer-docs/latest/guides/draft.md b/docs/developer-docs/latest/guides/draft.md
index 2f46eff4bd..9ebe886a5b 100644
--- a/docs/developer-docs/latest/guides/draft.md
+++ b/docs/developer-docs/latest/guides/draft.md
@@ -1,29 +1,30 @@
---
-title: Draft System - Strapi Developer Documentation
+title: Draft System - Strapi Developer Docs
description: Learn in this guide how to create a draft system that will allow you to manage draft, published, and archive status inside your Strapi project.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/draft.html
---
# Draft system
-This guide will explain how to create a draft system that will allow you to manage draft, published, and archive status.
-
-::: warning
-The native **Draft & Publish feature** has been released in **version 3.2**. We suggest you to use the native feature instead of this guide.
+:::caution
+The native [**Draft & Publish feature**](/user-docs/latest/content-manager/saving-and-publishing-content.md#saving-publishing-content) has been released in Strapi v3.2. We suggest you to use the native feature instead of this guide.
This guide is still useful if you want to see the concept of "force filtering" in action.
:::
+This guide will explain how to create a draft system that will allow you to manage draft, published, and archive status.
+
## Introduction
What we want here is to fetch only data that has a `published` status.
-But we don't want to use [parameters](/developer-docs/latest/developer-resources/content-api/content-api.md#api-parameters) (eg. /articles?status=published) because you can easily fake the params.
+But we don't want to use [parameters](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-parameters) (eg. /articles?status=published) because you can easily fake the params.
To be able to do that, you have first to understand some concepts.
-When you create a content type, it generates an API with the following list of [endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+When you create a content type, it generates an API with the following list of [endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
-Each of these endpoint triggers a controller action. Here is the list of [controller actions](/developer-docs/latest/development/backend-customization.md#controllers) that exist by default when a content type is created.
+Each of these endpoint triggers a controller action. Here is the list of [controller actions](/developer-docs/latest/development/backend-customization/controllers.md) that exist by default when a content type is created.
If you check the controller file of your generated API `./api/{content-type}/controller/{Content-Type}.js`, you will see an empty file. It is because all the default logic is managed by Strapi. But you can override these actions with your own code.
@@ -86,7 +87,7 @@ After saving the new function, let's restart the `GET /articles` request. We wil
We now know the function we have to update, but we just want to customize the returned article values.
-In the [controller documentation](/developer-docs/latest/development/backend-customization.md#extending-a-model-controller) you will find the default implementation of every action. It will help you overwrite the fetch logic.
+In the [controller documentation](/developer-docs/latest/development/backend-customization/controllers.md#extending-core-controllers) you will find the default implementation of every action. It will help you overwrite the fetch logic.
**Path —** `./api/article/controller/Article.js`
diff --git a/docs/developer-docs/latest/guides/error-catching.md b/docs/developer-docs/latest/guides/error-catching.md
index b1b0009bc4..3b2b7d77d7 100644
--- a/docs/developer-docs/latest/guides/error-catching.md
+++ b/docs/developer-docs/latest/guides/error-catching.md
@@ -1,10 +1,15 @@
---
-title: Error Catching - Strapi Developer Documentation
+title: Error Catching - Strapi Developer Docs
description: Learn in this guide how you can catch errors and send them to the Application Monitoring / Error Tracking Software you want.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/error-catching.html
---
# Error catching
+:::caution
+This guide is outdated and we recommend using [the official Sentry plugin for Strapi](https://www.npmjs.com/package/strapi-plugin-sentry) instead.
+:::
+
In this guide we will see how you can catch errors and send them to the Application Monitoring / Error Tracking Software you want.
::: tip
@@ -13,7 +18,7 @@ In this example we will use [Sentry](https://sentry.io).
## Create a middleware
-A [middleware](/developer-docs/latest/setup-deployment-guides/configurations.md#middlewares) will be used in order to catch the errors which will then be sent to Sentry.
+A [middleware](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md) will be used in order to catch the errors which will then be sent to Sentry.
- Create a `./middlewares/sentry/index.js` file.
@@ -64,7 +69,7 @@ module.exports = strapi => {
};
```
-::: warning
+:::caution
It's important to call `throw(error);` to avoid stopping the middleware stack. If you don't re-throw the error, it won't be handled by the Strapi's error formatter and the api will never respond to the client.
:::
diff --git a/docs/developer-docs/latest/guides/external-data.md b/docs/developer-docs/latest/guides/external-data.md
index 1b078bea4c..7ebcfcdafb 100644
--- a/docs/developer-docs/latest/guides/external-data.md
+++ b/docs/developer-docs/latest/guides/external-data.md
@@ -1,10 +1,13 @@
---
-title: External Data - Strapi Developer Documentation
+title: External Data - Strapi Developer Docs
description: Learn in this guide how to fetch data from an external service to use it in your Strapi project.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/external-data.html
---
# Fetching external data
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
This guide explains how to fetch data from an external service to use it in your app.
In this example we will see how to daily fetch Docker pull count to store the result in your database.
@@ -84,7 +87,7 @@ With this code, everytime this function is called it will fetch the docker repo'
Here is how to call the function in your application `strapi.config.functions.docker()`
-So let's execute this function everyday at 2am. For this we will use a [CRON tasks](/developer-docs/latest/setup-deployment-guides/configurations.md#cron-tasks).
+So let's execute this function everyday at 2am. For this we will use a [CRON tasks](/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md).
**Path —** `./config/functions/cron.js`
diff --git a/docs/developer-docs/latest/guides/is-owner.md b/docs/developer-docs/latest/guides/is-owner.md
index ee18d0f3d8..b37dee9d31 100644
--- a/docs/developer-docs/latest/guides/is-owner.md
+++ b/docs/developer-docs/latest/guides/is-owner.md
@@ -1,10 +1,13 @@
---
-title: Is Owner - Strapi Developer Documentation
+title: Is Owner - Strapi Developer Docs
description: Learn in this guide how to restrict content editing to content authors only.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/is-owner.html
---
# Create is owner policy
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
This guide will explain how to restrict content editing to content authors only.
## Introduction
@@ -32,8 +35,8 @@ When we are creating a new Article via `POST /articles` we will need to set the
To do so we will customize the `create` controller function of the Article API.
**Concepts we will use:**
-Here is the code of [core controllers](/developer-docs/latest/development/backend-customization.md#core-controllers).
-We will also use this [documentation](/developer-docs/latest/development/plugins/users-permissions.md#user-object-in-strapi-context) to access the current authenticated user information.
+Here is the code of [core controllers](/developer-docs/latest/development/backend-customization/controllers.md#extending-core-controllers).
+We will also use this [documentation](/developer-docs/latest/plugins/users-permissions.md#user-object-in-strapi-context) to access the current authenticated user information.
**Path —** `./api/article/controllers/Article.js`
@@ -131,6 +134,6 @@ module.exports = {
And tada!
-::: tip
+:::tip
For the delete action, it will be the exact same check as the update action.
:::
diff --git a/docs/developer-docs/latest/guides/jwt-validation.md b/docs/developer-docs/latest/guides/jwt-validation.md
index 0fd6494788..689929afed 100644
--- a/docs/developer-docs/latest/guides/jwt-validation.md
+++ b/docs/developer-docs/latest/guides/jwt-validation.md
@@ -1,10 +1,13 @@
---
-title: JWT validation - Strapi Developer Documentation
+title: JWT validation - Strapi Developer Docs
description: Learn in this guide how to validate a JWT (JSON Web Token) with a third party service.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/jwt-validation.html
---
# JWT validation
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how to validate a `JWT` (JSON Web Token) with a third party service.
When you sign in with the authentication route `POST /auth/local`, Strapi generates a `JWT` which lets your users request your API as an authenticated one.
@@ -26,7 +29,7 @@ We can now imagine you have a `JWT` that comes from [Auth0](https://auth0.com) a
## Customize the JWT validation function
-We will update the function that validates the `JWT`. This feature is powered by the **Users & Permissions** [plugin](/developer-docs/latest/development/plugin-customization.md).
+We will update the function that validates the `JWT`. This feature is powered by the **Users & Permissions** [plugin](/developer-docs/latest/plugins/upload.md).
Here is the file we will have to customize: [permission.js](https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-users-permissions/config/policies/permissions.js)
@@ -101,6 +104,6 @@ module.exports = async (ctx, next) => {
}
```
-::: warning
+:::caution
In the code example we use `axios`, so you will have to install the dependency to make it work. You can choose another library if you prefer.
:::
diff --git a/docs/developer-docs/latest/guides/process-manager.md b/docs/developer-docs/latest/guides/process-manager.md
index 06373c3e8b..b14537457e 100644
--- a/docs/developer-docs/latest/guides/process-manager.md
+++ b/docs/developer-docs/latest/guides/process-manager.md
@@ -1,11 +1,14 @@
---
-title: Process Manager - Strapi Developer Documentation
+title: Process Manager - Strapi Developer Docs
description: Learn in this guide how you can start a Strapi application using a process manager.
sidebarDepth: 2
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/process-manager.html
---
# Process manager
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how you can start a Strapi application using a process manager.
::: tip
@@ -18,14 +21,18 @@ PM2 allows you to keep your Strapi project alive and to reload it without downti
You will install PM2 globally
-:::: tabs
+:::: tabs card
::: tab yarn
-`yarn global add pm2`
+```sh
+yarn global add pm2
+```
:::
::: tab npm
-`npm install pm2 -g`
+```sh
+npm install pm2 -g
+```
:::
::::
diff --git a/docs/developer-docs/latest/guides/registering-a-field-in-admin.md b/docs/developer-docs/latest/guides/registering-a-field-in-admin.md
index 23ef8e73dc..69b8928569 100644
--- a/docs/developer-docs/latest/guides/registering-a-field-in-admin.md
+++ b/docs/developer-docs/latest/guides/registering-a-field-in-admin.md
@@ -1,10 +1,13 @@
---
-title: Field Registering - Strapi Developer Documentation
+title: Field Registering - Strapi Developer Docs
description: Learn in this guide how you can create a new Field for your administration panel.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/registering-a-field-in-admin.html
---
# Creating a new Field in the administration panel
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how you can create a new Field for your administration panel.
## Introduction
@@ -15,7 +18,7 @@ For this example, we will see how to change the WYSIWYG with [CKEditor](https://
1. Create a new project:
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -32,7 +35,7 @@ yarn create strapi-app my-app --quickstart --no-run
```
# Create an application using SQLite and prevent the server from starting automatically as we will create a plugin
# right after the project generation
-npx create-strapi-app my-app --quickstart --no-run
+npx create-strapi-app@latest my-app --quickstart --no-run
```
:::
@@ -41,7 +44,7 @@ npx create-strapi-app my-app --quickstart --no-run
2. Generate a plugin:
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -74,7 +77,7 @@ strapi generate:plugin wysiwyg
3. Install the needed dependencies:
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -98,7 +101,7 @@ npm install @ckeditor/ckeditor5-react @ckeditor/ckeditor5-build-classic
4. Start your application with the front-end development mode:
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -429,9 +432,9 @@ export default strapi => {
};
```
-Finally you will have to rebuild strapi so the new plugin is loaded correctly
+Finally you will have to rebuild strapi so the new plugin is loaded correctly:
-:::: tabs
+:::: tabs card
::: tab yarn
diff --git a/docs/developer-docs/latest/guides/scheduled-publication.md b/docs/developer-docs/latest/guides/scheduled-publication.md
index ae214fad02..8bc9121b6f 100644
--- a/docs/developer-docs/latest/guides/scheduled-publication.md
+++ b/docs/developer-docs/latest/guides/scheduled-publication.md
@@ -1,10 +1,13 @@
---
-title: Scheduled Publication - Strapi Developer Documentation
+title: Scheduled Publication - Strapi Developer Docs
description: Learn in this guide how to create an article schedule system.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/scheduled-publication.html
---
# Scheduled publication
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
This guide will explain how to create an article schedule system.
## Introduction
@@ -15,7 +18,7 @@ What we want here is to be able to set a publication date for an article, and at
For this example, we will have to add a `publish_at` attribute to the **Article** Content Type.
-- Click on the Content-Types Builder link in the left menu
+- Click on the Content-Type Builder link in the left menu
- Select the **Article** Content Type
- Add another field
- `date` attribute named `publish_at` with `datetime` type
@@ -29,7 +32,7 @@ The goal will be to check every minute if there are draft articles that have a `
To execute a function every minutes, we will use a CRON task.
-Here is the [full documentation](/developer-docs/latest/setup-deployment-guides/configurations.md#cron-tasks) of this feature. If your CRON task requires to run based on a specific timezone then do look into the full documentation.
+Here is the [full documentation](/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md) of this feature. If your CRON task requires to run based on a specific timezone then do look into the full documentation.
**Path —** `./config/functions/cron.js`
diff --git a/docs/developer-docs/latest/guides/secure-your-app.md b/docs/developer-docs/latest/guides/secure-your-app.md
index 13bd73ce62..6aa04f9ecb 100644
--- a/docs/developer-docs/latest/guides/secure-your-app.md
+++ b/docs/developer-docs/latest/guides/secure-your-app.md
@@ -1,10 +1,13 @@
---
-title: Secure your application - Strapi Developer Documentation
+title: Secure your application - Strapi Developer Docs
description: Learn in this guide how you can secure your Strapi application by using a third party provider.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/secure-your-app.html
---
# Secure your application
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how you can secure your Strapi application by using a third party provider.
::: tip
@@ -19,14 +22,18 @@ Sqreen is an Application Security Management tool that enables protection tailor
You will have to install Sqreen node_module in your application.
-:::: tabs
+:::: tabs card
::: tab yarn
-`yarn add sqreen`
+```sh
+yarn add sqreen
+```
:::
::: tab npm
-`npm install sqreen`
+```sh
+npm install sqreen
+```
:::
::::
diff --git a/docs/developer-docs/latest/guides/send-email.md b/docs/developer-docs/latest/guides/send-email.md
index 8a8c231246..ead096936b 100644
--- a/docs/developer-docs/latest/guides/send-email.md
+++ b/docs/developer-docs/latest/guides/send-email.md
@@ -1,10 +1,13 @@
---
-title: Send Email - Strapi Developer Documentation
+title: Send Email - Strapi Developer Docs
description: Learn in this guide how to use the Email plugin to send email where you want in your Strapi app.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/send-email.html
---
# Send email programmatically
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how to use the Email plugin to send email where you want in your app.
For this example we want to receive an email when a new article's comment is posted and if it contains bad words.
@@ -15,9 +18,9 @@ What we want here is to add some custom logic and call the email service when a
To be able to do that, you have first to understand some concepts.
-When you create a content type, it generates an API with the following list of [endpoints](/developer-docs/latest/developer-resources/content-api/content-api.md#api-endpoints).
+When you create a content type, it generates an API with the following list of [endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints).
-Each of these endpoint triggers a controller action. Here is the list of [controller actions](/developer-docs/latest/development/backend-customization.md#controllers) that exist by default when a content type is created.
+Each of these endpoint triggers a controller action. Here is the list of [controller actions](/developer-docs/latest/development/backend-customization/controllers.md) that exist by default when a content type is created.
If you check the controller file of your generated API `./api/{content-type}/controller/{Content-Type}.js`, you will see an empty file. It is because all the default logic is managed by Strapi. But you can override these actions with your own code.
@@ -58,7 +61,7 @@ After saving the new function, let's restart the `POST /comment` request. We wil
We now know the function we have to update. Let's get back to the original function.
-In the [controller documentation](/developer-docs/latest/development/backend-customization.md#extending-a-model-controller) you will find the default implementation of every action. It will help you overwrite the create logic.
+In the [controller documentation](/developer-docs/latest/development/backend-customization/controllers.md#extending-core-controllers) you will find the default implementation of every action. It will help you overwrite the create logic.
**Path —** `./api/comment/controller/Comment.js`
@@ -85,7 +88,7 @@ And now the comment creation is back.
We want to check if the content of the comment contains any bad words.
-If it does, we want to send an email using the [Email plugin](/developer-docs/latest/development/plugins/email.md)
+If it does, we want to send an email using the [Email plugin](/developer-docs/latest/plugins/email.md)
**Path —** `./api/comment/controller/Comment.js`
diff --git a/docs/developer-docs/latest/guides/slug.md b/docs/developer-docs/latest/guides/slug.md
index 46bab2b4e6..3e9aa55249 100644
--- a/docs/developer-docs/latest/guides/slug.md
+++ b/docs/developer-docs/latest/guides/slug.md
@@ -1,10 +1,13 @@
---
-title: Slug System - Strapi Developer Documentation
+title: Slug System - Strapi Developer Docs
description: Learn in this guide how to create a slug system for a Post, Article or any Content Type you want in your Strapi project.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/slug.html
---
# Create a slug system
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
This guide will explain how to create a slug system for a Post, Article or any Content Type you want.
## Create attributes
@@ -30,7 +33,7 @@ Here we will be able to setup the `slug` field.
- And click **OFF** for **Editable field** option.
- Don't forget to save your updates.
-:::: tabs
+:::: tabs card
::: tab View before
@@ -60,30 +63,7 @@ When it's done, you have to update the life cycle of the **Article** Content Typ
**Path —** `./api/article/models/Article.js`
-:::: tabs
-
-::: tab Mongoose
-
-```js
-const slugify = require('slugify');
-
-module.exports = {
- lifecycles: {
- beforeCreate: async (data) => {
- if (data.title) {
- data.slug = slugify(data.title);
- }
- },
- beforeUpdate: async (params, data) => {
- if (data.title) {
- data.slug = slugify(data.title);
- }
- },
- },
-};
-```
-
-:::
+:::: tabs card
::: tab Bookshelf
diff --git a/docs/developer-docs/latest/guides/snippets/guide-not-updated.md b/docs/developer-docs/latest/guides/snippets/guide-not-updated.md
new file mode 100644
index 0000000000..4b8efb75cd
--- /dev/null
+++ b/docs/developer-docs/latest/guides/snippets/guide-not-updated.md
@@ -0,0 +1,3 @@
+::: caution
+This guide might not be up-to-date with Strapi v4. We are currently reworking the "Guides" section as most of the features they cover are now part of Strapi's core.
+:::
diff --git a/docs/developer-docs/latest/guides/unit-testing.md b/docs/developer-docs/latest/guides/unit-testing.md
index af14a52452..7748b337d3 100644
--- a/docs/developer-docs/latest/guides/unit-testing.md
+++ b/docs/developer-docs/latest/guides/unit-testing.md
@@ -1,11 +1,14 @@
---
-title: Unit Testing - Strapi Developer Documentation
+title: Unit Testing - Strapi Developer Docs
description: Learn in this guide how you can run basic unit tests for a Strapi application using a testing framework.
sidebarDepth: 2
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/guides/unit-testing.html
---
# Unit testing
+!!!include(developer-docs/latest/guides/snippets/guide-not-updated.md)!!!
+
In this guide we will see how you can run basic unit tests for a Strapi application using a testing framework.
::: tip
@@ -13,8 +16,8 @@ In this example we will use [Jest](https://jestjs.io/) Testing Framework with a
[Supertest](https://github.com/visionmedia/supertest) Super-agent driven library for testing node.js HTTP servers using a fluent API
:::
-::: warning
-Please note that this guide will not work if you are on Windows using the SQLite database due to how windows locks the SQLite file
+:::caution
+Please note that this guide will not work if you are on Windows using the SQLite database due to how windows locks the SQLite file.
:::
## Install test tools
@@ -25,7 +28,7 @@ Please note that this guide will not work if you are on Windows using the SQLite
`sqlite3` is used to create an on-disk database that is created and deleted between tests.
-:::: tabs
+:::: tabs card
::: tab yarn
`yarn add --dev jest supertest sqlite3`
@@ -71,7 +74,7 @@ Those will inform `Jest` not to look for test inside the folder where it shouldn
Test framework must have a clean empty environment to perform valid test and also not to interfere with current database.
-Once `jest` is running it uses the `test` [environment](/developer-docs/latest/setup-deployment-guides/configurations.md#environment) (switching `NODE_ENV` to `test`)
+Once `jest` is running it uses the `test` [environment](http://localhost:8080/documentation/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md) (switching `NODE_ENV` to `test`)
so we need to create a special environment setting for this purpose.
Create a new config for test env `./config/env/test/database.json` and add the following value `"filename": ".tmp/test.db"` - the reason of that is that we want to have a separate sqlite database for tests, so our test will not touch real data.
This file will be temporary, each time test is finished, we will remove that file that every time tests are run on the clean database.
@@ -184,12 +187,15 @@ Ran all test suites.
✨ Done in 5.73s.
```
-> Note: if you receive a timeout error for Jest, please add the following line right before the `beforeAll` method in the `app.test.js` file: `jest.setTimeout(15000)` and adjust the milliseconds value as you need.
+:::tip
+If you receive a timeout error for Jest, please add the following line right before the `beforeAll` method in the `app.test.js` file: `jest.setTimeout(15000)` and adjust the milliseconds value as you need.
+:::
+
### Testing basic endpoint controller.
::: tip
-In the example we'll use and example `Hello world` `/hello` endpoint from [controllers](/developer-docs/latest/development/backend-customization.md#example-2) section.
+In the example we'll use and example `Hello world` `/hello` endpoint from [controllers](/developer-docs/latest/development/backend-customization/controllers.md) section.
:::
@@ -239,7 +245,9 @@ Ran all test suites.
✨ Done in 9.09s.
```
-> Note: if you receive an error `Jest has detected the following 1 open handles potentially keeping Jest from exiting` check `jest` version as `26.6.3` works without an issue.
+:::tip
+If you receive an error `Jest has detected the following 1 open handles potentially keeping Jest from exiting` check `jest` version as `26.6.3` works without an issue.
+:::
### Testing `auth` endpoint controller.
diff --git a/docs/developer-docs/latest/development/plugins/documentation.md b/docs/developer-docs/latest/plugins/documentation.md
similarity index 97%
rename from docs/developer-docs/latest/development/plugins/documentation.md
rename to docs/developer-docs/latest/plugins/documentation.md
index 9058a862f4..58a6c75158 100644
--- a/docs/developer-docs/latest/development/plugins/documentation.md
+++ b/docs/developer-docs/latest/plugins/documentation.md
@@ -1,6 +1,7 @@
---
-title: API Documentation - Strapi Developer Documentation
+title: API Documentation - Strapi Developer Docs
description: By using Swagger UI, the API documentation plugin takes out most of your pain to generate your documentation.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/documentation.html
---
# API Documentation
@@ -15,32 +16,25 @@ You'll be able to visualize all your end-points directly from the SWAGGER UI.
As usual run the following in your terminal:
-:::: tabs
-::: tab yarn
+
-```
-yarn strapi install documentation
-```
-
-:::
-
-::: tab npm
-
-```
+
+```sh
npm run strapi install documentation
```
+
-:::
+
+```sh
+yarn strapi install documentation
+```
+
-::::
+
When your plugin is installed, you just have to start your application and it will generate your API documentation.
-The administration panel lets you configure the basic settings of this plugin.
-
-
-
## Administration panel
This plugin comes with an interface that is available in your administration panel and a configuration file.
@@ -137,13 +131,13 @@ Here are the file that needs to be created in order to change the documentation
The `openapi`, `info`, `x-strapi-config`, `servers`, `externalDocs` and `security` fields are located in the `./extensions/documentation/config/settings.json` file. Here you can specify all your environment variables, licenses, external documentation and so on...
You can add all the entries listed in the [specification](https://swagger.io/specification/).
-::: danger
+:::warning
Do not change the `openapi` field of the `settings.json`
:::
-::: tip NOTE
+:::note
When you change a field in the settings.json file you need to manually restart your server.
diff --git a/docs/developer-docs/latest/development/plugins/email.md b/docs/developer-docs/latest/plugins/email.md
similarity index 94%
rename from docs/developer-docs/latest/development/plugins/email.md
rename to docs/developer-docs/latest/plugins/email.md
index a308221c51..408107093d 100644
--- a/docs/developer-docs/latest/development/plugins/email.md
+++ b/docs/developer-docs/latest/plugins/email.md
@@ -1,6 +1,7 @@
---
-title: Email - Strapi Developer Documentation
+title: Email - Strapi Developer Docs
description: Send email from your server or externals providers.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/email.html
---
# Email
@@ -71,25 +72,23 @@ You can check all the available providers developed by the community on npmjs.or
To install a new provider run:
-:::: tabs
-::: tab yarn
-```
-yarn add strapi-provider-email-sendgrid --save
-```
-
-:::
+
-::: tab npm
-
-```
+
+```sh
npm install strapi-provider-email-sendgrid --save
```
+
-:::
+
+```sh
+yarn add strapi-provider-email-sendgrid --save
+```
+
-::::
+
#### Using scoped packages as providers
@@ -130,7 +129,7 @@ module.exports = ({ env }) => ({
```
::: tip
-If you're using a different provider depending on your environment, you can specify the correct configuration in `config/env/${yourEnvironment}/plugins.js`. More info here: [Environments](/developer-docs/latest/setup-deployment-guides/configurations.md#environment)
+If you're using a different provider depending on your environment, you can specify the correct configuration in `config/env/${yourEnvironment}/plugins.js`. More info here: [Environments](http://localhost:8080/documentation/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md)
:::
::: tip
@@ -139,7 +138,7 @@ Only one email provider will be active at all time. If the email provider settin
::: tip
When testing the new email provider with those two email templates created during strapi setup, the _shipper email_ on the template, with default no-reply@strapi.io need to be updated in according to your email provider, otherwise it will fail the test.
-More info here: [Configure templates Locally](/user-docs/latest/settings/configuring-users-permissions-plugin-settings.html#configuring-email-templates)
+More info here: [Configure templates Locally](/user-docs/latest/settings/configuring-users-permissions-plugin-settings.md#configuring-email-templates)
:::
## Create new provider
diff --git a/docs/developer-docs/latest/plugins/graphql.md b/docs/developer-docs/latest/plugins/graphql.md
new file mode 100644
index 0000000000..87899bc071
--- /dev/null
+++ b/docs/developer-docs/latest/plugins/graphql.md
@@ -0,0 +1,586 @@
+---
+title: GraphQL - Strapi Developer Docs
+description: Use a GraphQL endpoint in your Strapi project to fetch and mutate your content.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/graphql.html
+---
+
+# GraphQL
+
+By default Strapi create [REST endpoints](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-endpoints) for each of your content types. With the GraphQL plugin, you will be able to add a GraphQL endpoint to fetch and mutate your content.
+
+:::strapi Looking for the GraphQL API documentation?
+The [GraphQL API reference](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md) describes queries, mutations and parameters you can use to interact with your API using Strapi's GraphQL plugin.
+:::
+
+## Usage
+
+To get started with GraphQL in your app, please install the plugin first. To do that, open your terminal and run the following command:
+
+
+
+
+```sh
+npm run strapi install graphql
+```
+
+
+
+```sh
+yarn strapi install graphql
+```
+
+
+
+
+Then, start your app and open your browser at [http://localhost:1337/graphql](http://localhost:1337/graphql). You should see the interface (**GraphQL Playground**) that will help you to write GraphQL query to explore your data.
+
+## Configurations
+
+By default, the [Shadow CRUD](#shadow-crud) feature is enabled and the GraphQL path is set to `/graphql`. The Playground is enabled by default for both the development and staging environments, however it is disabled in production. By changing the config option `playgroundAlways` to true, you can enable it.
+
+
+
+Security limits on maximum number of items in your response by default is limited to 100, however you can change this on the following config option `amountLimit`. This should only be changed after careful consideration of the drawbacks of a large query which can cause what would basically be a DDoS (Distributed Denial of Service). And may cause abnormal load on your Strapi server, as well as your database server.
+
+You can also setup any [Apollo Server options](https://www.apollographql.com/docs/apollo-server/api/apollo-server/#apolloserver) with the `apolloServer` option. For example, you can enable the tracing feature, which is supported by the playground to track the response time of each part of your query. To enable this feature just change/add the `"tracing": true` option in the GraphQL settings file. You can read more about the tracing feature from Apollo [here](https://www.apollographql.com/docs/apollo-server/federation/metrics/).
+
+You can edit these [configurations](/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md) by creating the following file:
+
+:::caution
+Please note the setting for GraphQL `tracing` as changed and has been moved to `apolloServer.tracing`
+:::
+
+```js
+// path: ./config/plugins.js
+
+module.exports = {
+ //
+ graphql: {
+ endpoint: '/graphql',
+ shadowCRUD: true,
+ playgroundAlways: false,
+ depthLimit: 7,
+ amountLimit: 100,
+ apolloServer: {
+ tracing: false,
+ },
+ },
+};
+```
+
+## Shadow CRUD
+
+To simplify and automate the build of the GraphQL schema, we introduced the Shadow CRUD feature. It automatically generates the type definitions, queries, mutations and resolvers based on your models.
+
+**Example:**
+
+If you've generated an API called `Restaurant` using [the interactive `strapi generate` CLI](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate) or the administration panel, your model looks like this:
+
+```json
+// path: ./src/api/[api-name]/content-types/restaurant/schema.json
+
+{
+ "kind": "collectionType",
+ "collectionName": "documents",
+ "info": {
+ "singularName": "document",
+ "pluralName": "documents",
+ "displayName": "document",
+ "name": "document"
+ },
+ "options": {
+ "draftAndPublish": true
+ },
+ "pluginOptions": {},
+ "attributes": {
+ "name": {
+ "type": "string"
+ },
+ "description": {
+ "type": "richtext"
+ },
+ "locked": {
+ "type": "boolean"
+ }
+ }
+}
+```
+
+::: details Generated GraphQL type and queries
+
+```graphql
+# Document's Type definition
+input DocumentFiltersInput {
+ name: StringFilterInput
+ description: StringFilterInput
+ locked: BooleanFilterInput
+ createdAt: DateTimeFilterInput
+ updatedAt: DateTimeFilterInput
+ publishedAt: DateTimeFilterInput
+ and: [DocumentFiltersInput]
+ or: [DocumentFiltersInput]
+ not: DocumentFiltersInput
+}
+
+input DocumentInput {
+ name: String
+ description: String
+ locked: Boolean
+ createdAt: DateTime
+ updatedAt: DateTime
+ publishedAt: DateTime
+}
+
+type Document {
+ name: String
+ description: String
+ locked: Boolean
+ createdAt: DateTime
+ updatedAt: DateTime
+ publishedAt: DateTime
+}
+
+type DocumentEntity {
+ id: ID
+ attributes: Document
+}
+
+type DocumentEntityResponse {
+ data: DocumentEntity
+}
+
+type DocumentEntityResponseCollection {
+ data: [DocumentEntity!]!
+ meta: ResponseCollectionMeta!
+}
+
+type DocumentRelationResponseCollection {
+ data: [DocumentEntity!]!
+}
+
+# Queries to retrieve one or multiple restaurants.
+type Query {
+ document(id: ID): DocumentEntityResponse
+ documents(
+ filters: DocumentFiltersInput
+ pagination: PaginationArg = {}
+ sort: [String] = []
+ publicationState: PublicationState = LIVE
+):DocumentEntityResponseCollection
+}
+
+# Mutations to create, update or delete a restaurant.
+type Mutation {
+ createDocument(data: DocumentInput!): DocumentEntityResponse
+ updateDocument(id: ID!, data: DocumentInput!): DocumentEntityResponse
+ deleteDocument(id: ID!): DocumentEntityResponse
+}
+```
+
+:::
+
+## Customization
+
+Strapi provides a programmatic API to customize GraphQL, which allows:
+
+* disabling some operations for the [Shadow CRUD](#shadow-crud)
+* [using getters](#using-getters) to return information about allowed operations
+* registering and using an `extension` object to [extend the existing schema](#extending-the-schema) (e.g. extend types or define custom resolvers, policies and middlewares)
+
+::: details Example of GraphQL customizations
+
+```js
+// path: ./src/index.js
+
+module.exports = {
+/**
+ * An asynchronous register function that runs before
+ * your application is initialized.
+ *
+ * This gives you an opportunity to extend code.
+ */
+ register({ strapi }) => {
+ const extensionService = strapi.plugin('graphql').service('extension');
+
+ extensionService.shadowCRUD('api::restaurant.restaurant').disable();
+ extensionService.shadowCRUD('api::category.category').disableQueries();
+ extensionService.shadowCRUD('api::address.address').disableMutations();
+ extensionService.shadowCRUD('api::document.document').field('locked').disable();
+ extensionService.shadowCRUD('api::like.like').disableActions(['create', 'update', 'delete']);
+
+ const extension = ({ nexus }) => ({
+ // Nexus
+ types: [
+ nexus.objectType({
+ name: 'Book',
+ definition(t) {
+ t.string('title');
+ },
+ }),
+ ],
+ plugins: [
+ nexus.plugin({
+ name: 'MyPlugin',
+
+ onAfterBuild(schema) {
+ console.log(schema);
+ },
+ }),
+ ],
+
+ // GraphQL SDL
+ typeDefs: `
+ type Article {
+ name: String
+ }
+ `,
+ resolvers: {
+ Query: {
+ address: {
+ resolve() {
+ return { value: { city: 'Montpellier' } };
+ },
+ },
+ },
+ },
+
+ resolversConfig: {
+ 'Query.address': {
+ auth: false,
+ },
+ },
+ });
+
+ extensionService.use(extension);
+ },
+};
+```
+
+:::
+
+### Disabling operations in the Shadow CRUD
+
+The `extension` [service](/developer-docs/latest/development/backend-customization/services.md) provided with the GraphQL plugin exposes functions that can be used to disable operations on Content-Types:
+
+| Content-type function | Description | Argument type | Possible argument values |
+| -------------------- | ---------------------------------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `disable()` | Fully disable the Content-Type | - | - |
+| `disableQueries()` | Only disable queries for the Content-Type | - | - |
+| `disableMutations()` | Only disable mutations for the Content-Type | - | - |
+| `disableAction()` | Disable a specific action for the Content-Type | String | One value from the list:- `create`
- `find`
- `findOne`
- `update`
- `delete`
|
+| `disableActions()` | Disable specific actions for the Content-Type | Array of Strings | Multiple values from the list: - `create`
- `find`
- `findOne`
- `update`
- `delete`
|
+
+Actions can also be disabled at the field level, with the following functions:
+
+| Field function | Description |
+| ------------------ | -------------------------------- |
+| `disable()` | Fully disable the field |
+| `disableOutput()` | Disable the output on a field |
+| `disableInput()` | Disable the input on a field |
+| `disableFilters()` | Disable filters input on a field |
+
+**Examples:**
+
+```js
+// Disable the 'find' operation on the 'restaurant' content-type in the 'restaurant' API
+strapi
+ .plugin('graphql')
+ .service('extension')
+ .shadowCRUD('api::restaurant.restaurant')
+ .disableAction('find')
+
+// Disable the 'name' field on the 'document' content-type in the 'document' API
+strapi
+ .plugin('graphql')
+ .service('extension')
+ .shadowCRUD('api::document.document')
+ .field('name')
+ .disable()
+```
+
+### Using getters
+
+The following getters can be used to retrieve information about operations allowed on content-types:
+
+| Content-type getter | Description | Argument type | Possible argument values |
+| -------------------------- | ----------------------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `isEnabled()` | Returns whether a content-type is enabled | - | - |
+| `isDisabled()` | Returns whether a content-type is disabled | - | - |
+| `areQueriesEnabled()` | Returns whether queries are enabled on a content-type | - | - |
+| `areQueriesDisabled()` | Returns whether queries are disabled on a content-type | - | - |
+| `areMutationsEnabled()` | Returns whether mutations are enabled on a content-type | - | - |
+| `areMutationsDisabled()` | Returns whether mutations are disabled on a content-type | - | - |
+| `isActionEnabled(action)` | Returns whether the passed `action` is enabled on a content-type | String | One value from the list:- `create`
- `find`
- `findOne`
- `update`
- `delete`
|
+| `isActionDisabled(action)` | Returns whether the passed `action` is disabled on a content-type | String | One value from the list:- `create`
- `find`
- `findOne`
- `update`
- `delete`
|
+
+The following getters can be used to retrieve information about operations allowed on fields:
+
+| Field getter | Description |
+| --------------------- | --------------------------------------------- |
+| `isEnabled()` | Returns whether a field is enabled |
+| `isDisabled()` | Returns whether a field is disabled |
+| `hasInputEnabled()` | Returns whether a field has input enabled |
+| `hasOutputEnabled()` | Returns whether a field has output enabled |
+| `hasFiltersEnabled()` | Returns whether a field has filtering enabled |
+
+### Extending the schema
+
+The schema generated by the Content API can be extended by registering an extension.
+
+This extension, defined either as an object or a function returning an object, will be used by the `use()` function exposed by the `extension` [service](/developer-docs/latest/development/backend-customization/services.md) provided with the GraphQL plugin.
+
+The object describing the extension accepts the following parameters:
+
+| Parameter | Type | Description |
+| ----------------- | ------ | -------------------------------------------------------------------------------------------- |
+| `types` | Array | Allows extending the schema types using [Nexus](https://nexusjs.org/)-based type definitions |
+| `typeDefs` | String | Allows extending the schema types using [GraphQL SDL](https://graphql.org/learn/schema/) |
+| `plugins` | Array | Allows extending the schema using Nexus [plugins](https://nexusjs.org/docs/plugins) |
+| `resolvers` | Object | Defines custom resolvers |
+| `resolversConfig` | Object | Defines [configuration options for the resolvers](#custom-configuration-for-resolvers), such as [authorization](#authorization-configuration), [policies](#policies) and [middlewares](#middlewares) |
+
+::::tip
+The `types` and `plugins` parameters are based on [Nexus](https://nexusjs.org/). To use them, register the extension as a function that takes `nexus` as a parameter:
+
+::: details Example:
+
+```js
+
+// path: ./src/index.js
+
+module.exports = {
+ register({ strapi }) {
+ const extension = ({ nexus }) => ({
+ types: [
+ nexus.objectType({
+ …
+ }),
+ ],
+ plugins: [
+ nexus.plugin({
+ …
+ })
+ ]
+ })
+
+ strapi.plugin('graphql').service('extension').use(extension)
+ }
+}
+```
+
+:::
+::::
+
+#### Custom configuration for resolvers
+
+A resolver is a GraphQL query or mutation handler (i.e. a function, or a collection of functions, that generate(s) a response for a GraphQL query or mutation). Each field has a default resolver.
+
+When [extending the GraphQL schema](#extending-the-schema), the `resolversConfig` key can be used to define a custom configuration for a resolver, which can include:
+
+* [authorization configuration](#authorization-configuration) with the `auth` key
+* [policies with the `policies`](#policies) key
+* and [middlewares with the `middlewares`](#middlewares) key
+
+##### Authorization configuration
+
+By default, the authorization of a GraphQL request is handled by the registered authorization strategy that can be either [API token](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md) or through the [Users & Permissions plugin](#usage-with-the-users-permissions-plugin). The Users & Permissions plugin offers a more granular control.
+
+::: details Authorization with the Users & Permissions plugin
+With the Users & Permissions plugin, a GraphQL request is allowed if the appropriate permissions are given.
+
+For instance, if a 'Category' content-type exists and is queried through GraphQL with the `Query.categories` handler, the request is allowed if the appropriate `find` permission for the 'Categories' content-type is given.
+
+To query a single category, which is done with the `Query.category` handler, the request is allowed if the the `findOne` permission is given.
+
+Please refer to the user guide on how to [define permissions with the Users & Permissions plugin](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#editing-a-role).
+:::
+
+To change how the authorization is configured, use the resolver configuration defined at `resolversConfig.[MyResolverName]`. The authorization can be configured:
+
+* either with `auth: false` to fully bypass the authorization system and allow all requests,
+* or with a `scope` attribute that accepts an array of strings to define the permissions required to authorize the request.
+
+::: details Examples of authorization configuration
+
+```js
+
+// path: ./src/index.js
+
+module.exports = {
+ register({ strapi }) {
+ const extensionService = strapi.plugin('graphql').service('extension');
+
+ extensionService.use({
+ resolversConfig: {
+ 'Query.categories': {
+ /**
+ * Querying the Categories content-type
+ * bypasses the authorization system.
+ */
+ auth: false
+ },
+ 'Query.restaurants': {
+ /**
+ * Querying the Restaurants content-type
+ * requires the find permission
+ * on the 'Address' content-type
+ * of the 'Address' API
+ */
+ auth: {
+ scope: ['api::address.address.find']
+ }
+ },
+ }
+ })
+ }
+}
+
+```
+
+:::
+
+##### Policies
+
+[Policies](/developer-docs/latest/development/backend-customization/policies.md) can be applied to a GraphQL resolver through the `resolversConfig.[MyResolverName].policies` key.
+
+The `policies` key is an array accepting a list of policies, each item in this list being either a reference to an already registered policy or an implementation that is passed directly (see [policies configuration documentation](/developer-docs/latest/development/backend-customization/routes.md#policies)).
+
+Policies directly implemented in `resolversConfig` are functions that take a `context` object and the `strapi` instance as arguments.
+The `context` object gives access to:
+
+* the `parent`, `args`, `context` and `info` arguments of the GraphQL resolver,
+* Koa's [context](https://koajs.com/#context) with `context.http` and [state](https://koajs.com/#ctx-state) with `context.state`.
+
+::: details Example of a custom GraphQL policy applied to a resolver
+
+```js
+
+// path: ./src/index.js
+
+module.exports = {
+ register({ strapi }) {
+ const extensionService = strapi.plugin('graphql').service('extension');
+
+ extensionService.use({
+ resolversConfig: {
+ 'Query.categories': {
+ policies: [
+ (context, { strapi }) => {
+ console.log('hello', context.parent)
+ /**
+ * If 'categories' have a parent, the function returns true,
+ * so the request won't be blocked by the policy.
+ */
+ return context.parent !== undefined;
+ }
+ ],
+ auth: false,
+ },
+ }
+ })
+ }
+}
+```
+
+:::
+
+#### Middlewares
+
+[Middlewares](/developer-docs/latest/development/backend-customization/middlewares.md) can be applied to a GraphQL resolver through the `resolversConfig.[MyResolverName].middlewares` key.
+
+The `middlewares` key is an array accepting a list of middlewares, each item in this list being either a reference to an already registered policy or an implementation that is passed directly (see [middlewares configuration documentation](/developer-docs/latest/development/backend-customization/routes.md#middlewares)).
+
+Middlewares directly implemented in `resolversConfig` can take the GraphQL resolver's `parent`, `args`, `context` and `info` objects as arguments.
+
+:::tip
+Middlewares with GraphQL can even act on nested resolvers, which offer a more granular control than with REST.
+:::
+
+:::details Examples of custom GraphQL middlewares applied to a resolver
+
+```js
+
+// path: ./src/index.js
+
+module.exports = {
+ register({ strapi }) {
+ const extensionService = strapi.plugin('graphql').service('extension');
+
+ extensionService.use({
+ resolversConfig: {
+ 'Query.categories': {
+ middlewares: [
+ /**
+ * Basic middleware example #1
+ * Log resolving time in console
+ */
+ async (next, parent, args, context, info ) => {
+ console.time('Start resolving categories');
+ console.timeEnd('Stop resolving categories');
+
+ return res;
+ },
+ /**
+ * Basic middleware example #2
+ * change the 'name' attribute of parent with id 1 to 'foobar'
+ */
+ (resolve, parent, ...rest) => {
+ if (parent.id === 1) {
+ return resolve({...parent, name: 'foobar' }, ...rest);
+ }
+
+ return resolve(parent, ...rest);
+ }
+ ],
+ auth: false,
+ },
+ }
+ })
+ }
+}
+```
+
+:::
+
+## Usage with the Users & Permissions plugin
+
+The [Users & Permissions plugin](/developer-docs/latest/plugins/users-permissions.md) is an optional plugin that allows protecting the API with a full authentication process.
+
+### Registration
+
+Usually you need to sign up or register before being recognized as a user then perform authorized requests.
+
+:::request Mutation
+```graphql
+mutation {
+ register(input: { username: "username", email: "email", password: "password" }) {
+ jwt
+ user {
+ username
+ email
+ }
+ }
+}
+```
+:::
+
+You should see a new user is created in the `Users` collection type in your Strapi admin panel.
+
+### Authentication
+
+To perform authorized requests, you must first get a JWT:
+
+:::request Mutation
+
+```graphql
+mutation {
+ login(input: { identifier: "email", password: "password" }) {
+ jwt
+ }
+}
+```
+
+:::
+
+Then on each request, send along an `Authorization` header in the form of `{ "Authorization": "Bearer YOUR_JWT_GOES_HERE" }`. This can be set in the HTTP Headers section of your GraphQL Playground.
diff --git a/docs/developer-docs/latest/plugins/i18n.md b/docs/developer-docs/latest/plugins/i18n.md
new file mode 100644
index 0000000000..f424f2f4ca
--- /dev/null
+++ b/docs/developer-docs/latest/plugins/i18n.md
@@ -0,0 +1,721 @@
+---
+title: Internationalization (i18n) - Strapi Developer Docs
+description: Instructions on how to use Strapi Content API with the Internationalization (i18n) optional plugin
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/i18n.html
+---
+
+# 🌍 Internationalization (i18n)
+
+The Internationalization (i18n) plugin allows Strapi users to create, manage and distribute localized content in different languages, called "locales". For more information about the concept of internationalization, please refer to the
+[W3C definition](https://www.w3.org/International/questions/qa-i18n.en#i18n).
+
+The i18n plugin:
+
+- allows admin panel users to create several localized versions of their content (see [user guide](/user-docs/latest/content-manager/translating-content.md))
+- allows developers to build localized projects by fetching and consuming the right content depending on the country/language of the audience.
+
+::: note
+The i18n plugin does not automatically translate the users' content nor adapt the admin interface to languages specificities (e.g. displaying the admin panel in Right To Left format).
+:::
+
+## Installation
+
+::: prerequisites
+The Internationalization plugin is installed by default on all Strapi applications running on version 3.6.0 or higher. For lower versions, a migration is needed (see [Update Strapi version](/developer-docs/latest/update-migration-guides/update-version.md)), as well as a manual installation of the plugin.
+:::
+
+The plugin can be installed:
+
+- [from the Marketplace](/user-docs/latest/plugins/installing-plugins-via-marketplace.md),
+- or using the Terminal, by running one of the following commands:
+
+
+
+
+```sh
+npm run strapi install i18n
+```
+
+
+
+```sh
+yarn strapi install i18n
+```
+
+
+
+
+## Usage with the REST API
+
+
+
+The i18n plugin adds new features to the [REST API](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md):
+
+- a new [`locale`](#getting-localized-entries-with-the-locale-parameter) parameter to fetch content only for a specified locale
+- the ability to create a localized entry, either [from scratch](#creating-a-new-localized-entry) or [for an existing localized entry](#creating-a-localization-for-an-existing-entry)
+
+### Getting localized entries with the `locale` parameter
+
+The `locale` [API parameter](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#api-parameters) can be used to fetch entries only for a specified locale. It takes a locale code as value (see [full list of available locales](https://github.com/strapi/strapi/blob/master/packages/plugins/i18n/server/constants/iso-locales.json)).
+
+:::tip
+ To fetch content for a locale, make sure it has been already [added to Strapi in the admin panel](/user-docs/latest/settings/managing-global-settings.md#configuring-internationalization-locales).
+:::
+
+The format for a GET request is the following:
+
+:::request
+`GET /api/{content-type}?locale={locale-code}`
+:::
+
+Use `all` as a value for the locale code, as in `http://localhost:1337/api/restaurants?locale=all`, to fetch entries for all locales that have been configured in the admin panel.
+
+If the `locale` parameter isn't defined, it will be set to the default locale. `en` is the default locale when the i18n plugin is installed, so by default a GET request to `http://localhost:1337/api/restaurants` will return the same response as a request to `http://localhost:1337/api/restaurants?locale=en`.
+
+::: tip
+Another locale can be [set as the default locale](/user-docs/latest/settings/managing-global-settings.md#adding-a-new-locale) in the admin panel.
+:::
+
+When the i18n plugin is installed, the response to requests can include fields that are specific to internationalization:
+
+- The `locale` (string) field is always included, it's the locale code for the content entry.
+
+- The `localizations` (object) can be included if specifically requested by appending `?populate=localizations` to the URL (see [relations population documentation](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#relations-population). It includes a `data` array with a list of objects, each of them including the `id` and `attributes` of the localization.
+
+:::: api-call
+
+::: request Example request
+
+`GET http://localhost:1337/api/restaurants?locale=fr`
+
+:::
+
+::: response Example Response
+
+```json
+{
+ "data": [
+ {
+ "id": 4,
+ "attributes": {
+ "name": "Can Alegria",
+ "description": "description in French",
+ "locale": "fr",
+ "createdAt": "2021-10-28T15:24:42.129Z",
+ "publishedAt": "2021-10-28T15:24:42.129Z",
+ }
+ },
+ {
+ "id": 8,
+ "attributes": {
+ "name": "She's Cake",
+ "description": "description in French",
+ "locale": "fr",
+ "createdAt": "2021-10-28T16:17:42.129Z",
+ "publishedAt": "2021-10-28T16:18:24.126Z",
+ }
+ }
+ ],
+ "meta": {
+ "pagination": {
+ "page": 1,
+ "pageSize": 25,
+ "pageCount": 2,
+ "total": 2
+ }
+ }
+}
+```
+
+:::
+::::
+
+In the example response above:
+
+- restaurant with `"id": 4` is a French (`"locale": "fr"`) localization of the existing restaurant with `"id": 3` (created for the default `en` locale).
+- restaurant with `"id": "8"` was created from scratch using the API, passing the `locale: fr` in the request body (see [creating a new localized entry](#creating-a-new-localized-entry)).
+
+### Creating a new localized entry
+
+To create a localized entry from scratch, send a POST request to the Content API.
+
+If no locale has been passed in the request body, the entry is created using the default locale for the application:
+
+:::: api-call
+::: request Example request
+
+`POST http://localhost:1337/api/restaurants`
+
+```json
+{
+ "data": {
+ "name": "Oplato",
+ "description": "description in English"
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "id": 3,
+ "attributes": {
+ "name": "Oplato",
+ "description": "description in English",
+ "createdAt": "2021-10-28T16:57:26.352Z",
+ "updatedAt": "2021-10-28T16:57:26.352Z",
+ "publishedAt": "2021-10-28T16:57:26.345Z",
+ "locale": "en"
+ }
+ },
+ "meta": {}
+}
+```
+
+:::
+::::
+
+To create a localized entry for a locale different from the default one, add the `locale` attribute to the body of the POST request:
+
+:::: api-call
+::: request Example request
+
+`POST http://localhost:1337/api/restaurants`
+
+```json
+{
+ "data": {
+ "name": "She's Cake",
+ "description": "description in French",
+ "locale": "fr"
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "id": 8,
+ "attributes": {
+ "name": "She's Cake",
+ "description": "description in French",
+ "createdAt": "2021-10-28T17:01:47.089Z",
+ "updatedAt": "2021-10-28T17:01:47.089Z",
+ "publishedAt": "2021-10-28T17:01:47.082Z",
+ "locale": "en"
+ }
+ },
+ "meta": {}
+}
+```
+
+:::
+::::
+
+### Creating a localization for an existing entry
+
+To create another localization for an existing localized entry, send a POST request to the appropriate URL depending on the type of content:
+
+| Content-Type | Request URL format |
+| --------------- | -------------------------------------------- |
+| Collection type | `POST /api/{content-type}/:id/localizations` |
+| Single type | `POST /api/{content-type}/localizations` |
+
+When creating a localization for existing localized entries, the body of the POST request can only accept localized fields.
+
+::: tip
+The Content-Type should have the [`createLocalization` permission](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#collection-and-single-types) enabled, otherwise the POST request will return a `403: Forbidden` status.
+:::
+
+#### Creating a localization for a collection type
+
+When sending a POST request to a collection type, Strapi will:
+
+1. use the `id` as a base entry for the non-localized fields and copy them in the new entry
+2. then create a new entry for the given locale and link it with the base entry.
+
+:::: api-call
+
+::: request Example request
+
+`POST http://localhost:1337/api/restaurants/8/localizations`
+
+```json
+{
+ "locale": "en",
+ "name": "She's Cake",
+ "description": "description in English"
+}
+```
+
+This request:
+
+1. creates a new entry in `en`
+2. links the created entry with `restaurant:8` (they will share the same `localizations` object)
+3. copies every non-localized fields from `restaurant:8` into the new entry and keeps the localized fields from the request's body
+:::
+
+::: response Example response
+
+
+```json
+{
+ "id": 9,
+ "name": "She's Cake",
+ "description": "description in English",
+ "createdAt": "2021-10-29T08:39:29.709Z",
+ "updatedAt": "2021-10-29T08:39:29.709Z",
+ "publishedAt": null,
+ "locale": "en",
+ "localizations": [
+ {
+ "id": 8,
+ "name": "She's Cake",
+ "description": "description in French",
+ "createdAt": "2021-10-28T16:57:26.352Z",
+ "updatedAt": "2021-10-29T08:38:04.106Z",
+ "publishedAt": "2021-10-28T16:57:26.345Z",
+ "locale": "fr"
+ }
+ ]
+}
+```
+
+:::
+
+::::
+
+#### Creating a localization for a single type
+
+:::: api-call
+
+::: request Example request
+
+`POST http://localhost:1337/api/homepage/localizations`
+
+```json
+
+{
+ "title": "Bienvenue sur FoodAdvisor !",
+ "locale": "fr",
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+
+{
+ "id": 2,
+ "title": "Bienvenue sur FoodAdvisor!",
+ "locale": "fr",
+ // ...
+ "localizations": [
+ {
+ "id": 1,
+ "locale": "en",
+ // ...
+ }
+ ]
+}
+```
+
+:::
+
+::::
+
+### Updating an entry
+
+It is not possible to change the locale of an existing localized entry.
+
+When updating a localized entry (with `PUT /{localized-content-type}/:id`), if you set a `locale` attribute in the request body, it will be ignored.
+
+## Usage with the GraphQL plugin
+
+The i18n plugin adds new features to the [GraphQL plugin](/developer-docs/latest/plugins/graphql.md):
+
+- The `locale` and `localizations` fields are added to the [GraphQL](https://graphql.org/) schema.
+- The GraphQL [query API](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md) can be used to:
+ - [query with the `locale` argument](/developer-docs/latest/plugins/i18n.md#usage-with-the-graphql-plugin) on collection types and single types
+ - [create new localizations with a mutation](/developer-docs/latest/plugins/i18n.md#creating-new-localized-entries-with-graphql) for collection types and single types
+ - [update](/developer-docs/latest/plugins/i18n.md#updating-a-localized-single-type-with-graphql) and [delete](/developer-docs/latest/plugins/i18n.md#deleting-a-localization-for-a-single-type-with-graphql) a localization with a mutation on single types
+
+### Getting localized entries with GraphQL
+
+Queries can use the `locale` argument to fetch entries only for a specified locale.
+
+::: tip
+To fetch entries for all locales, use `locale: "all"` in the query.
+:::
+#### Fetching a collection type
+
+:::: api-call
+
+::: request Example query
+
+```graphql
+query {
+ restaurants(locale: "en") {
+ data {
+ id
+ attributes {
+ name
+ locale
+ localizations {
+ data {
+ id
+ attributes {
+ name
+ description
+ }
+ }
+ }
+ }
+ }
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "restaurants": {
+ "data": [
+ {
+ "id": "1",
+ "attributes": {
+ "name": "can alegria",
+ "locale": "en",
+ "localizations": {
+ "data": [
+ {
+ "id": "2",
+ "attributes": {
+ "name": "can alegria (fr)",
+ "description": "description en français"
+ }
+ }
+ ]
+ }
+ }
+ },
+ {
+ "id": "2",
+ ...
+ },
+ ...
+ ]
+ }
+ }
+}
+```
+
+:::
+
+::::
+#### Fetching a single type
+
+:::: api-call
+
+::: request Example query
+
+```graphql
+query {
+ homepage(locale: "en") {
+ data {
+ id
+ attributes {
+ title
+ }
+ }
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "homepage": {
+ "data": {
+ "id": "1",
+ "attributes": {
+ "title": "Welcome on FoodAdvisor!",
+ }
+ }
+ }
+ }
+}
+```
+
+:::
+
+::::
+
+### Creating new localized entries with GraphQL
+
+The `locale` field can be passed in the `data` object of the mutation to create a localized entry for this specific locale (for more information, see [create a new entry with the GraphQL plugin](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md#create-a-new-entry)).
+
+#### Creating a new localization for a collection type
+
+:::: api-call
+
+::: request Example mutation
+
+```graphql
+mutation {
+ createRestaurantLocalization(
+ id: 8
+ locale: "en"
+ data: {
+ name: "She's Cake"
+ description: "description in english"
+ }
+ ) {
+ data {
+ id
+ attributes {
+ name
+ description
+ locale
+ localizations {
+ data {
+ attributes {
+ locale
+ description
+ }
+ }
+ }
+ }
+ }
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "createRestaurantLocalization": {
+ "id": "9",
+ "locale": "en",
+ "name": "She's Cake",
+ "description": "description in English",
+ "localizations": [
+ {
+ "id": "8",
+ "locale": "fr",
+ "description": "description in French"
+ }
+ ]
+ }
+ }
+}
+{
+ "data": {
+ "createRestaurantLocalization": {
+ "data": {
+ "id": "6",
+ "attributes": {
+ "name": "She's Cake",
+ "description": "description in English",
+ "locale": "fr",
+ "localizations": {
+ "data": [
+ {
+ "attributes": {
+ "locale": "en",
+ "description": "description in English"
+ }
+ },
+ {
+ "attributes": {
+ "locale": "fr",
+ "description": "description in French"
+ }
+ }
+ ]
+ }
+ }
+ }
+ }
+ }
+}
+
+```
+
+:::
+
+::::
+
+#### Creating a new localization for a single type
+
+:::: api-call
+
+::: request Example mutation
+
+```graphql
+mutation {
+ createHomepageLocalization(
+ locale: "fr"
+ data: {
+ title: "Bienvenue sur FoodAdvisor !"
+ }
+ ) {
+ data {
+ id
+ attributes {
+ locale
+ title
+ }
+ }
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "createHomepageLocalization": {
+ "data": {
+ "id": "2",
+ "attributes": {
+ "locale": "fr",
+ "title": "Bienvenue sur FoodAdvisor !"
+ }
+ }
+ }
+ }
+}
+
+```
+
+:::
+
+::::
+
+### Updating a localized single type with GraphQL
+
+A `locale` argument can be passed in the mutation to update content for a given locale (for more information, see [update an existing entry with the GraphQL plugin](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md#update-an-existing-entry)).
+
+Currently, it is not possible to change the locale of an existing localized entry. If you set a `locale` field in the `data` object of the mutation, it will be ignored.
+
+:::: api-call
+
+::: request Example mutation
+
+```graphql
+mutation {
+ updateHomepage(
+ locale: "fr"
+ data: { title: "Bienvenue sur l'annuaire FoodAdvisor !" }
+ ) {
+ data {
+ id
+ attributes {
+ title
+ }
+ }
+ }
+}
+
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "updateHomepage": {
+ "data": {
+ "id": "1",
+ "attributes": {
+ "title": "Bienvenue sur l'annuaire FoodAdvisor !"
+ }
+ }
+ }
+ }
+}
+```
+
+:::
+::::
+
+### Deleting a localization for a single type with GraphQL
+
+Pass the `locale` argument in the mutation to delete a specific localization for a single type:
+
+:::: api-call
+
+::: request Example mutation
+
+```graphql
+mutation {
+ deleteHomepage(locale: "fr") {
+ data {
+ id
+ attributes {
+ title
+ }
+ }
+ }
+}
+```
+
+:::
+
+::: response Example response
+
+```json
+{
+ "data": {
+ "deleteHomepage": {
+ "data": {
+ "id": "1",
+ "attributes": {
+ "title": "Bienvenue sur l'annuaire FoodAdvisor !"
+ }
+ }
+ }
+ }
+}
+```
+
+The response returns the entry that has just been deleted.
+
+:::
+
+::::
+
+## Configuration in production environments
+
+A `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` [environment variable](http://localhost:8080/documentation/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md-variables) can be configured to set the initialization locale for your environment. The value used for this variable should be a string (see [full list of available locales](https://github.com/strapi/strapi/blob/releases/v4/packages/plugins/i18n/server/constants/iso-locales.json)).
+
+This is useful when a Strapi app is deployed in production, with the i18n plugin installed and enabled on your content types for the first time. On a fresh i18n plugin installation, `en` is the default locale. So if the database does not contain any locale, and no `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` is set for the environment, the content of the content types with i18n enabled will be automatically migrated to the `en` locale. But if the `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE` is defined, then the content will be migrated to this locale. Using this environment variable saves you from having to manually update the locale for existing content entries.
diff --git a/docs/developer-docs/latest/plugins/plugins-intro.md b/docs/developer-docs/latest/plugins/plugins-intro.md
new file mode 100644
index 0000000000..e13c70dd1f
--- /dev/null
+++ b/docs/developer-docs/latest/plugins/plugins-intro.md
@@ -0,0 +1,33 @@
+---
+title: Strapi plugins - Strapi Developer Docs
+description: Strapi comes with built-in plugins (i18n, GraphQL, Users & Permissions, Upload, API documentation, and Email) and you can install plugins as npm packages.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/plugins-intro.html
+---
+
+# Strapi plugins
+
+Strapi comes with these officially supported plugins:
+
+
+
+
+## Automatic plugins discovery
+
+Strapi automatically loads plugins installed with npm. Under the hood, Strapi scans every `package.json` file of the project dependencies, and looks for the following declaration:
+
+```json
+"strapi": {
+ "kind": "plugin"
+}
+```
+
+Installed plugins can also be manually enabled or disabled.
+
+## Manual enabling/disabling
+
+To disable a plugin without uninstalling it, switch its `enabled` key to `false` in the [`/config/plugins.js` file](/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md).
+
+::: strapi To go further
+* To know more about plugins installation, see the [User guide](/user-docs/latest/plugins/introduction-to-plugins.md).
+* Existing plugins can be [extended](/developer-docs/latest/development/plugins-extension.md), or you can even [create your own](/developer-docs/latest/development/plugins-development.md)!
+:::
diff --git a/docs/developer-docs/latest/development/plugins/upload.md b/docs/developer-docs/latest/plugins/upload.md
similarity index 94%
rename from docs/developer-docs/latest/development/plugins/upload.md
rename to docs/developer-docs/latest/plugins/upload.md
index fc23a50e93..06f39c081a 100644
--- a/docs/developer-docs/latest/development/plugins/upload.md
+++ b/docs/developer-docs/latest/plugins/upload.md
@@ -1,6 +1,7 @@
---
-title: Upload - Strapi Developer Documentation
+title: Upload - Strapi Developer Docs
description: Upload any kind of file on your server or external providers.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/upload.html
---
# Upload
@@ -54,7 +55,7 @@ module.exports = {
}
}
```
-::: warning
+:::caution
Breakpoint changes will only apply to new images, existing images will not be resized or have new sizes generated.
:::
@@ -126,8 +127,8 @@ To upload files into your application.
```
-::: warning
-You have to send FormData in your request body
+:::caution
+You have to send FormData in your request body.
:::
## Upload files related to an entry
@@ -187,8 +188,8 @@ Code
```
-::: warning
-You have to send FormData in your request body
+:::caution
+You have to send FormData in your request body.
:::
## Upload file during entry creation
@@ -241,15 +242,9 @@ Code
if (!['submit', 'file'].includes(currentElement.type)) {
data[currentElement.name] = currentElement.value;
} else if (currentElement.type === 'file') {
- if (currentElement.files.length === 1) {
- const file = currentElement.files[0];
+ for (let i = 0; i < currentElement.files.length; i++) {
+ const file = currentElement.files[i];
formData.append(`files.${currentElement.name}`, file, file.name);
- } else {
- for (let i = 0; i < currentElement.files.length; i++) {
- const file = currentElement.files[i];
-
- formData.append(`files.${currentElement.name}`, file, file.name);
- }
}
}
}
@@ -273,8 +268,8 @@ If you want to upload files for a component, you will have to specify the index
Example `files.my_component_name[the_index].attribute_name`
:::
-::: warning
-You have to send FormData in your request body
+:::caution
+You have to send FormData in your request body.
:::
## Models definition
@@ -336,25 +331,21 @@ You can check all the available providers developed by the community on npmjs.or
To install a new provider run:
-:::: tabs
-
-::: tab yarn
+
-```
-yarn add strapi-provider-upload-aws-s3
-```
-
-:::
-
-::: tab npm
-
-```
+
+```sh
npm install strapi-provider-upload-aws-s3 --save
```
+
-:::
+
+```sh
+yarn add strapi-provider-upload-aws-s3
+```
+
-::::
+
### Local server
diff --git a/docs/developer-docs/latest/development/plugins/users-permissions.md b/docs/developer-docs/latest/plugins/users-permissions.md
similarity index 99%
rename from docs/developer-docs/latest/development/plugins/users-permissions.md
rename to docs/developer-docs/latest/plugins/users-permissions.md
index 5689cdda19..9abc86a142 100644
--- a/docs/developer-docs/latest/development/plugins/users-permissions.md
+++ b/docs/developer-docs/latest/plugins/users-permissions.md
@@ -1,7 +1,8 @@
---
-title: Roles & Permissions - Strapi Developer Documentation
+title: Roles & Permissions - Strapi Developer Docs
description: Protect your API with a full authentication process based on JWT and manage the permissions between the groups of users.
sidebarDepth: 2
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/plugins/users-permissions.html
---
# Roles & Permissions
@@ -206,7 +207,7 @@ In the following examples, the frontend app will be the [react login example app
It (the frontend app) will be running on `http://localhost:3000`.
Strapi (the backend) will be running on `http://localhost:1337`.
-:::: tabs
+:::: tabs card
::: tab GitHub
@@ -704,7 +705,7 @@ Once you have configured strapi and the provider, in your frontend app you have
Now you can make authenticated requests 🎉 More info here: [token usage](#token-usage).
-:::warning Troubleshooting
+:::caution Troubleshooting
- **Error 429**: It's most likely because your login flow fell into a loop. To make new requests to the backend, you need to wait a few minutes or restart the backend.
- **Grant: missing session or misconfigured provider**: It may be due to many things.
@@ -786,8 +787,8 @@ Congrats, you're done!
### Email validation
-:::tip NOTE
-In production, make sure the `url` config property is set. Otherwise the validation link will redirect to `localhost`. More info on the config [here](/developer-docs/latest/setup-deployment-guides/configurations.md#server).
+:::note
+In production, make sure the `url` config property is set. Otherwise the validation link will redirect to `localhost`. More info on the config [here](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md).
:::
After having registered, if you have set **Enable email confirmation** to **ON**, the user will receive a confirmation link by email. The user has to click on it to validate his/her registration.
@@ -849,7 +850,7 @@ extensions/users-permissions/services/Providers.js
extensions/users-permissions/config/functions/bootstrap.js
```
-If these files don't exist you will need to copy from your `node_modules` or the Strapi mono-repo. You can see [plugin extensions](/developer-docs/latest/development/plugin-customization.md) for more information on how it works.
+If these files don't exist you will need to copy from your `node_modules` or the Strapi mono-repo. You can see [plugin extensions](/developer-docs/latest/development/plugins-extension.md) for more information on how it works.
We will go step by step.
@@ -954,7 +955,6 @@ discord: {
```
-
## Templating emails
@@ -993,5 +993,5 @@ module.exports = {
```
::: tip
-You can learn more on configuration in the documentation [here](/developer-docs/latest/setup-deployment-guides/configurations.md)
+You can learn more on configuration in the documentation [here](/developer-docs/latest/setup-deployment-guides/configurations.md).
:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations.md b/docs/developer-docs/latest/setup-deployment-guides/configurations.md
index c4ba626e72..0b5d736d85 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/configurations.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations.md
@@ -1,38 +1,15 @@
---
-title: Configurations - Strapi Developer Documentation
+title: Configurations - Strapi Developer Docs
description: Learn how you can manage and customize the configuration of your Strapi application.
-sidebarDepth: 3
+sidebarDepth: auto
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations.html
---
-
-
# Configurations
-Your application configuration lives in the `config` folder. All the configuration files are loaded on startup and can be accessed through the configuration provider.
+The application configuration lives in the `./config` folder (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)). All the configuration files are loaded on startup and can be accessed through the configuration provider.
-When you have a file `./config/server.js` with the following config:
+If the `./config/server.js` file has the following config:
```js
module.exports = {
@@ -40,1705 +17,59 @@ module.exports = {
};
```
-You can access it as
+The `server.host` key can be accessed as:
```js
strapi.config.get('server.host', 'defaultValueIfUndefined');
```
-Nested keys are accessible with `dot-notation`.
-
-:::tip NOTE
-Notice that the filename is used as a prefix to access the configurations.
-:::
-
-## Required configurations
-
-### Database
-
-This file lets you define database connections that will be used to store your application content.
-
-::: tip NOTE
-You can find [supported database and versions](/developer-docs/latest/setup-deployment-guides/installation/cli.html#preparing-the-installation) in the local installation process.
-:::
-
-**Path —** `./config/database.js`.
-
-:::: tabs
-
-::: tab Bookshelf
-
-- `defaultConnection` (string): Connection by default for models which are not related to a specific `connection`. Default value: `default`.
-- `connections` List of all available connections.
- - `default`
- - `connector` (string): Connector used by the current connection. Will be `bookshelf`.
- - `settings` Useful for external session stores such as Redis.
- - `client` (string): Database client to create the connection. `sqlite` or `postgres` or `mysql`.
- - `host` (string): Database host name. Default value: `localhost`.
- - `port` (integer): Database port.
- - `database` (string): Database name.
- - `username` (string): Username used to establish the connection.
- - `password` (string): Password used to establish the connection.
- - `timezone` (string): Set the default behavior for local time. Default value: `utc` [Timezone options](https://www.php.net/manual/en/timezones.php).
- - `schema` (string): Set the default database schema. **Used only for Postgres DB.**
- - `ssl` (boolean/object): For ssl database connection. Object is used to pass certificate files as strings.
- - `options` Options used for database connection.
- - `debug` (boolean): Show database exchanges and errors.
- - `autoMigration` (boolean): To disable auto tables/columns creation for SQL database.
- - `pool` Options used for database connection pooling. For default value and more information, look at [Knex's pool config documentation](https://knexjs.org/#Installation-pooling).
- - `min` (integer): Minimum number of connections to keep in the pool.
- - `max` (integer): Maximum number of connections to keep in the pool.
- - `acquireTimeoutMillis` (integer): Maximum time in milliseconds to wait for acquiring a connection from the pool.
- - `createTimeoutMillis` (integer): Maximum time in milliseconds to wait for creating a connection to be added to the pool.
- - `idleTimeoutMillis` (integer): Number of milliseconds to wait before destroying idle connections.
- - `reapIntervalMillis` (integer): How often to check for idle connections in milliseconds.
- - `createRetryIntervalMillis` (integer): How long to idle after a failed create before trying again in milliseconds.
-
-:::
-
-::: tab Mongoose
-
-- `defaultConnection` (string): Connection by default for models which are not related to a specific `connection`. Default value: `default`.
-- `connections` List of all available connections.
- - `default`
- - `connector` (string): Connector used by the current connection. Will be `mongoose`.
- - `settings` Useful for external session stores such as Redis.
- - `client` (string): Database client to create the connection. Will be `mongo`.
- - `host` (string): Database host name. Default value: `localhost`.
- - `port` (integer): Database port. Default value: `27017`.
- - `database` (string): Database name.
- - `username` (string): Username used to establish the connection.
- - `password` (string): Password used to establish the connection.
- - `uri` (string): This can overide all previous configurations - _optional_
- - `options` Options used for database connection.
- - `ssl` (boolean): For ssl database connection.
- - `sslCA` (string): Pass content (not filepath!) of server's root CA for ssl connection.
- - `debug` (boolean): Show database exchanges and errors.
- - `authenticationDatabase` (string): Connect with authentication.
-
-:::
-
-::::
-
-::::: tabs
-
-:::: tab PostgreSQL
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'bookshelf',
- settings: {
- client: 'postgres',
- host: env('DATABASE_HOST', 'localhost'),
- port: env.int('DATABASE_PORT', 5432),
- database: env('DATABASE_NAME', 'strapi'),
- username: env('DATABASE_USERNAME', 'strapi'),
- password: env('DATABASE_PASSWORD', 'strapi'),
- schema: env('DATABASE_SCHEMA', 'public'), // Not Required
- ssl: {
- rejectUnauthorized: env.bool('DATABASE_SSL_SELF', false), // For self-signed certificates
- },
- },
- options: {},
- },
- },
-});
-```
-
-::: warning
-We are aware that there is an issue regarding **SSL support for the server**.
-In order to fix it, you have to to set the `ssl:{}` object as a boolean in order to disable it. See below for example:
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'bookshelf',
- settings: {
- client: 'postgres',
- ...
- ssl: env('DATABASE_SSL', false)
- },
- options: {},
- },
- },
-});
-```
-:::
-
-Please note that if you need client side SSL CA verification you will need to use the `ssl:{}` object with the fs module to convert your CA certificate to a string. You can see an example below:
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'bookshelf',
- settings: {
- client: 'postgres',
- ...
- ssl: {
- ca: fs.readFileSync(`${__dirname}/path/to/your/ca-certificate.crt`).toString(),
- },
- },
- options: {},
- },
- },
-});
-```
-
-::::
-
-:::: tab MySQL/MariaDB
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'bookshelf',
- settings: {
- client: 'mysql',
- host: env('DATABASE_HOST', 'localhost'),
- port: env.int('DATABASE_PORT', 3306),
- database: env('DATABASE_NAME', 'strapi'),
- username: env('DATABASE_USERNAME', 'strapi'),
- password: env('DATABASE_PASSWORD', 'strapi'),
- },
- options: {},
- },
- },
-});
-```
-
-::::
-
-:::: tab SQLite
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'bookshelf',
- settings: {
- client: 'sqlite',
- filename: env('DATABASE_FILENAME', '.tmp/data.db'),
- },
- options: {
- useNullAsDefault: true,
- },
- },
- },
-});
-```
-
-::::
-
-:::: tab MongoDB
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {
- client: 'mongo',
- host: env('DATABASE_HOST', 'localhost'),
- port: env.int('DATABASE_PORT', 27017),
- database: env('DATABASE_NAME', 'strapi'),
- username: env('DATABASE_USERNAME', 'strapi'),
- password: env('DATABASE_PASSWORD', 'strapi'),
- },
- options: {
- authenticationDatabase: env('AUTHENTICATION_DATABASE'),
- ssl: env('DATABASE_SSL'),
- },
- },
- },
-});
-```
-
-::::
-
-:::::
-
-::: tip
-Take a look at the [database's guide](/developer-docs/latest/setup-deployment-guides/configurations.md#databases-installation-guides) for more details.
-:::
-
-#### Configuration in database
-
-Configuration files are not multi server friendly. So we created a data store for config you will want to update in production.
-
-##### Get settings
-
-- `environment` (string): Sets the environment you want to store the data in. By default it's current environment (can be an empty string if your config is environment agnostic).
-- `type` (string): Sets if your config is for an `api`, `plugin` or `core`. By default it's `core`.
-- `name` (string): You have to set the plugin or api name if `type` is `api` or `plugin`.
-- `key` (string, required): The name of the key you want to store.
-
-```js
-// strapi.store(object).get(object);
-
-// create reusable plugin store variable
-const pluginStore = strapi.store({
- environment: strapi.config.environment,
- type: 'plugin',
- name: 'users-permissions',
-});
-
-await pluginStore.get({ key: 'grant' });
-```
-
-##### Set settings
-
-- `value` (any, required): The value you want to store.
-
-```js
-// strapi.store(object).set(object);
-
-// create reusable plugin store variable
-const pluginStore = strapi.store({
- environment: strapi.config.environment,
- type: 'plugin',
- name: 'users-permissions'
-});
-
-await pluginStore.set({
- key: 'grant',
- value: {
- ...
- }
-});
-```
-
-#### Databases installation guides
-
-Strapi gives you the option to choose the most appropriate database for your project. It currently supports **PostgreSQL**, **MongoDB**, **SQLite**, **MySQL** and
-**MariaDB**. The following documentation covers how to install these databases locally (for development purposes) and on various hosted or cloud server solutions (for staging or production purposes).
-
-::: tip
-Deploying **Strapi** itself is covered in the [Deployment Guide](/developer-docs/latest/setup-deployment-guides/deployment.md).
-:::
-
-
-
-
-### Server
-
-:::: tabs
-
-::: tab Minimal
-
-#### Minimal Server Config
-
-This is the default config created with any new project, all these keys are required at the very least, environmental configs do not need to contain all these values so long as they exist in the default `./config/server.js`.
-
-**Path —** `./config/server.js`.
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- admin: {
- auth: {
- secret: env('ADMIN_JWT_SECRET', 'someSecretKey'),
- },
- },
-});
-```
-
-:::
-
-::: tab Full
-
-#### Full Server Config
-
-This is an example of a full configuration, typically certain keys do not need to present in environmental configs, and not all of these keys are required. Please see the table below to see what each key does.
-
-**Path —** `./config/server.js`.
-
-```javascript
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- socket: '/tmp/nginx.socket', // only use if absolutely required
- emitErrors: false,
- url: env('PUBLIC_URL', 'https://api.example.com'),
- proxy: env.bool('IS_PROXIED', true),
- cron: {
- enabled: env.bool('CRON_ENABLED', false),
- },
- admin: {
- auth: {
- events: {
- onConnectionSuccess(e) {
- console.log(e.user, e.provider);
- },
- onConnectionError(e) {
- console.error(e.error, e.provider);
- },
- },
- secret: env('ADMIN_JWT_SECRET', 'someSecretKey'),
- },
- url: env('PUBLIC_ADMIN_URL', '/dashboard'),
- autoOpen: false,
- watchIgnoreFiles: [
- './my-custom-folder', // Folder
- './scripts/someScript.sh', // File
- ],
- host: 'localhost', // Only used for --watch-admin
- port: 8003, // Only used for --watch-admin
- serveAdminPanel: env.bool('SERVE_ADMIN', true),
- forgotPassword: {
- from: 'no-reply@example.com',
- replyTo: 'no-reply@example.com',
- },
- },
-});
-```
+Nested keys are accessible with the [dot notation](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Property_accessors#dot_notation).
+:::note
+The filename is used as a prefix to access the configurations.
:::
-::::
-
-##### Available options
-
-| Property | Description | Type | Default |
-| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| `host` | Host name | string | `localhost` |
-| `port` | Port on which the server should be running. | integer | `1337` |
-| `socket` | Listens on a socket. Host and port are cosmetic when this option is provided and likewise use `url` to generate proper urls when using this option. This option is useful for running a server without exposing a port and using proxy servers on the same machine (e.g [Heroku nginx buildpack](https://github.com/heroku/heroku-buildpack-nginx#requirements-proxy-mode)) | string \| integer | `/tmp/nginx.socket` |
-| `emitErrors` | Enable errors to be emitted to `koa` when they happen in order to attach custom logic or use error reporting services. | boolean | `false` |
-| `url` | Public url of the server. Required for many different features (ex: reset password, third login providers etc.). Also enables proxy support such as Apache or Nginx, example: `https://mywebsite.com/api`. The url can be relative, if so, it is used with `http://${host}:${port}` as the base url. An absolute url is however **recommended**. | string | `''` |
-| `proxy` | Set the koa variable `app.proxy`. When `true`, proxy header fields will be trusted. | boolean | `false` |
-| `cron` | Cron configuration (powered by [`node-schedule`](https://github.com/node-schedule/node-schedule)) | Object | |
-| `cron.enabled` | Enable or disable CRON tasks to schedule jobs at specific dates. | boolean | `false` |
-| `admin` | Admin panel configuration | Object | |
-| `admin.auth` | Authentication configuration | Object | |
-| `admin.auth.secret` | Secret used to encode JWT tokens | string | `undefined` |
-| `admin.auth.events` | Record of all the events subscribers registered for the authentication | object | `{}` |
-| `admin.auth.events.onConnectionSuccess` | Function called when an admin user log in successfully to the administration panel | function | `undefined` |
-| `admin.auth.events.onConnectionError` | Function called when an admin user fails to log in to the administration panel | function | `undefined` |
-| `admin.url` | Url of your admin panel. Default value: `/admin`. Note: If the url is relative, it will be concatenated with `url`. | string | `/admin` |
-| `admin.autoOpen` | Enable or disabled administration opening on start. | boolean | `true` |
-| `admin.watchIgnoreFiles` | Add custom files that should not be watched during development. See more [here](https://github.com/paulmillr/chokidar#path-filtering) (property `ignored`). | Array(string) | `[]` |
-| `admin.host` | Use a different host for the admin panel. Only used along with `strapi develop --watch-admin` | string | `localhost` |
-| `admin.port` | Use a different port for the admin panel. Only used along with `strapi develop --watch-admin` | string | `8000` |
-| `admin.serveAdminPanel` | If false, the admin panel won't be served. Note: the `index.html` will still be served, see [defaultIndex option](/developer-docs/latest/setup-deployment-guides/configurations.md#global-middlewares) | boolean | `true` |
-| `admin.forgotPassword` | Settings to customize the forgot password email (see more here: [Forgot Password Email](/developer-docs/latest/development/admin-customization.md#forgot-password-email)) | Object | {} |
-| `admin.forgotPassword.emailTemplate` | Email template as defined in [email plugin](/developer-docs/latest/development/plugins/email.md#programmatic-usage) | Object | [Default template](https://github.com/strapi/strapi/tree/master/packages/strapi-admin/config/email-templates/forgot-password.js) |
-| `admin.forgotPassword.from` | Sender mail address | string | Default value defined in your [provider configuration](/developer-docs/latest/development/plugins/email.md#configure-the-plugin) |
-| `admin.forgotPassword.replyTo` | Default address or addresses the receiver is asked to reply to | string | Default value defined in your [provider configuration](/developer-docs/latest/development/plugins/email.md#configure-the-plugin) |
-
-### Formats
-
-You can either use `.js` or `.json` files to configure your application.
+Configuration files can either be `.js` or `.json` files.
-When using a `.js` you can either export an object:
+When using a `.js` file, the configuration can be exported:
-```js
-module.exports = {
- mySecret: 'someValue',
-};
-```
+- either as an object:
-or a function returning a configuration object (recommended usage). The function will get access to the [`env` utility](#casting-environment-variables).
-
-```js
-module.exports = ({ env }) => {
- return {
+ ```js
+ module.exports = {
mySecret: 'someValue',
};
-};
-```
-
-## Optional configurations
-
-### Environment
-
-In case you need specific static configurations for specific environments, and using environment variables becomes tedious, Strapi configurations can be created per environment in `./config/env/{env}/{filename}`.
-
-These configurations will be merged into the base configurations defined in the `./config` folder.
-The environment is based on the `NODE_ENV` environment variable (defaults to `development`).
-
-When starting Strapi with `NODE_ENV=production` it will load the configuration from `./config/*` and `./config/env/production/*`. Everything defined in the production config will override the default config.
-
-In combination with environment variables this pattern becomes really powerful.
-
-Examples:
-
-`./config/server.js`
-
-```js
-module.exports = {
- host: '127.0.0.1',
-};
-```
-
-`./config/env/production/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
-});
-```
-
-When starting your application:
-
-```bash
-yarn start
-# uses host 127.0.0.1
-```
-
-```bash
-NODE_ENV=production yarn start
-# uses host 0.0.0.0
-```
-
-```bash
-HOST=10.0.0.1 NODE_ENV=production yarn start
-# uses host 10.0.0.1
-```
-
-### Environment variables
-
-#### List of Strapi's environment variables
-
-Some settings can only be modified through environment variables. Here is a list of those settings are associated environment variable names:
-
-| name | description | type | default |
-| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | ------- | --------------- |
-| `STRAPI_DISABLE_UPDATE_NOTIFICATION` | Don't show the notification message about updating strapi in the terminal | boolean | `false` |
-| `STRAPI_HIDE_STARTUP_MESSAGE` | Don't show the startup message in the terminal | boolean | `false` |
-| `STRAPI_TELEMETRY_DISABLED` | Don't send telemetry usage data to Strapi | boolean | `false` |
-| `STRAPI_LOG_TIMESTAMP` | Add the timestamp info in logs | boolean | `false` |
-| `STRAPI_LOG_LEVEL` | Select the level of logs among `fatal`, `error`, `warn`, `info`, `debug`, `trace` | string | `'info'` |
-| `STRAPI_LOG_FORCE_COLOR` | Force colors to be displayed even in environments that are not supposed to have colors enabled (ex: outside of a TTY) | boolean | `true` |
-| `STRAPI_LOG_PRETTY_PRINT` | Log lines are displayed as text instead of as object | boolean | `true` |
-| `STRAPI_LICENSE` | The license key to activate the Enterprise Edition | string | `undefined` |
-| `NODE_ENV` | Type of environment where the app is running | string | `'development'` |
-| `BROWSER` | Open the admin panel in the browser after startup | boolean | `true` |
-| `ENV_PATH` | Path to the file that contains your environment variables | string | `'./.env'` |
-| `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE`| Initialization locale for the app, if [Internationalization (i18n) plugin](/developer-docs/latest/development/plugins/i18n.md) is installed and enabled on your content types (see [Configuration of i18n in production environments](/developer-docs/latest/development/plugins/i18n.md#configuration-in-production-environments)) | string | `'en'` |
-
-#### Configuration using environment variables
-
-In most use cases you will have different configurations between your environments. For example: your database credentials.
-
-Instead of writing those credentials into your configuration files, you can define those variables in a `.env` file at the root of your application.
-
-**Example:**
-
-**Path —** `.env`
-
-```
-DATABASE_PASSWORD=acme
-```
-
-If you want to customize the path of the `.env` file to load you can set an environment variable called `ENV_PATH` before starting your application:
-
-```sh
-$ ENV_PATH=/absolute/path/to/.env npm run start
-```
-
-Now you can access those variables in your configuration files and application. You can use `process.env.{varName}` to access those variables anywhere.
-
-In your configuration files you will have access to a `env` utility that allows defining defaults and casting values.
-
-**Path —** `./config/database.js`
-
-```js
-module.exports = ({ env }) => ({
- connections: {
- default: {
- settings: {
- password: env('DATABASE_PASSWORD'),
- },
- },
- },
-});
-```
-
-#### Casting environment variables
-
-```js
-// Returns the env if defined without casting it
-env('VAR', 'default');
-
-// Cast to int (using parseInt)
-env.int('VAR', 0);
-
-// Cast to float (using parseFloat)
-env.float('VAR', 3.14);
-
-// Cast to boolean (check if the value is equal to 'true')
-env.bool('VAR', true);
-
-// Cast to js object (using JSON.parse)
-env.json('VAR', { key: 'value' });
-
-// Cast to an array (syntax: ENV_VAR=[value1, value2, value3] | ENV_VAR=["value1", "value2", "value3"])
-env.array('VAR', [1, 2, 3]);
-
-// Case to date (using new Date(value))
-env.date('VAR', new Date());
-```
-
-### API
-
-**Path —** `./config/api.js`.
-
-```js
-module.exports = ({ env }) => ({
- responses: {
- privateAttributes: ['_v', 'id', 'created_at'],
- },
- rest: {
- defaultLimit: 100,
- maxLimit: 250,
- },
-});
-```
-
-#### Available options
-
-| Property | Description | Type | Default |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------- |
-| `responses` | Global API response configuration | Object | |
-| `responses.privateAttributes` | Set of globally defined attributes to be treated as private. E.g. `_v` when using MongoDb or timestamps like `created_at`, `updated_at` can be treated as private | String array | `[]` |
-| `rest` | REST API configuration | Object | |
-| `rest.defaultLimit` | Specifies default `_limit` parameter used in API calls | Integer | `100` |
-| `rest.maxLimit` | Specifies max allowed number that can be requested as `_limit`. Default to `null` which fetches all results | Integer | `null` |
-
-### Plugins
-
-A plugin is like a small independent sub-application. It has its own business logic with dedicated models, controllers, services, middlewares or hooks. It can also have its own UI integrated in the admin panel.
-
-::: tip
-Please refer to the [plugins documentation](/developer-docs/latest/development/local-plugins-customization.md) for more information.
-:::
-
-### Hooks
-
-The hooks are modules that add functionality to the core. They are loaded during the server boot.
-
-#### Structure
-
-##### File structure
-
-```js
-module.exports = strapi => {
- const hook = {
- /**
- * Default options
- */
-
- defaults: {
- // config object
- },
-
- /**
- * Initialize the hook
- */
-
- async initialize() {
- // await someAsyncCode()
- // const settings = {...this.defaults, ...strapi.config.hook.settings.**};
- },
- };
-
- return hook;
-};
-```
-
-- `defaults` (object): Contains the default configurations.
-- `initialize` (function): Called during the server boot.
-
-The [configurations](#configuration-and-activation) of the hook are accessible through `strapi.config.hook.settings.**`.
-
-The hooks are accessible through the `strapi.hook` variable.
-
-##### Node modules
-
-Every folder that follows this name pattern `strapi-hook-*` in your `./node_modules` folder will be loaded as a hook.
-
-A hook needs to follow the structure below:
-
-```
-/strapi-hook-[...]
-└─── lib
- - index.js
-- LICENSE.md
-- package.json
-- README.md
-```
-
-The `index.js` is the entry point to your hook. It should look like the example above.
-
-##### Custom local hooks
-
-The framework allows loading hooks from the project directly without having to install them from npm. It's a great way to take advantage of the features of the hooks system for code that doesn't need to be shared between apps. To achieve this, you have to create a `./hooks` folder at the root of your project and put the hooks into it.
-
-```
-/project
-└─── admin
-└─── api
-└─── config
-│ - hook.js
-└─── hooks
-│ └─── strapi-documentation
-│ - index.js
-│ └─── strapi-server-side-rendering
-│ - index.js
-└─── public
-- favicon.ico
-- package.json
-- server.js
-```
-
-#### Configuration and activation
-
-To activate and configure hooks with custom options, you need to add/edit your `./config/hook.js` file in your Strapi app. A hook specific timeout value will overwrite the global timeout value, the default `timeout` value is 1000 milliseconds.
-
-```js
-module.exports = {
- timeout: 2000,
- settings: {
- 'hook-name': {
- enabled: true,
- timeout: 3000,
- },
- },
-};
-```
-
-### Middlewares
-
-The middlewares are functions which are composed and executed in a stack-like manner upon request. If you are not familiar with the middleware stack in Koa, we highly recommend you to read the [Koa's documentation introduction](http://koajs.com/#introduction).
+ ```
-#### Structure
+- or as a function returning a configuration object (recommended usage). The function will get access to the [`env` utility](#casting-environment-variables):
-##### File structure
-
-```js
-module.exports = strapi => {
- return {
- // can also be async
- initialize() {
- strapi.app.use(async (ctx, next) => {
- // await someAsyncCode()
-
- await next();
-
- // await someAsyncCode()
- });
- },
+ ```js
+ module.exports = ({ env }) => {
+ return {
+ mySecret: 'someValue',
+ };
};
-};
-```
-
-- `initialize` (function): Called during the server boot.
-
-The middlewares are accessible through the `strapi.middleware` variable.
-
-##### Node modules
-
-Every folder that follows this name pattern `strapi-middleware-*` in your `./node_modules` folder will be loaded as a middleware.
-
-A middleware needs to follow the structure below:
-
-```
-/middleware
-└─── lib
- - index.js
-- LICENSE.md
-- package.json
-- README.md
-```
-
-The `index.js` is the entry point to your middleware. It should look like the example above.
-
-##### Custom middlewares
+ ```
-The framework allows the application to override the default middlewares and add new ones. You have to create a `./middlewares` folder at the root of your project and put the middlewares into it.
-
-```
-/project
-└─── api
-└─── config
-└─── middlewares
-│ └─── responseTime // It will override the core default responseTime middleware.
-│ - index.js
-│ └─── views // It will be added into the stack of middleware.
-│ - index.js
-└─── public
-- favicon.ico
-- package.json
-- server.js
-```
-
-Every middleware will be injected into the Koa stack. To manage the load order, please refer to the [Middleware order section](#load-order).
-
-#### Configuration and activation
-
-To configure the middlewares of your application, you need to create or edit the `./config/middleware.js` file in your Strapi app.
-
-By default this file doesn't exist, you will have to create it.
-
-**Available options**
-
-- `timeout` (integer): Defines the maximum allowed milliseconds to load a middleware.
-- `load` (Object): Configuration middleware loading. See details [here](#load-order)
-- `settings` (Object): Configuration of each middleware
- - `{middlewareName}` (Object): Configuration of one middleware
- - `enabled` (boolean): Tells Strapi to run the middleware or not
-
-##### Settings
-
-**Example**:
-
-**Path —** `./config/middleware.js`.
-
-```js
-module.exports = {
- //...
- settings: {
- cors: {
- origin: ['http://localhost', 'https://mysite.com', 'https://www.mysite.com'],
- },
- },
-};
-```
-
-##### Load order
-
-The middlewares are injected into the Koa stack asynchronously. Sometimes it happens that some of these middlewares need to be loaded in a specific order. To define a load order, create or edit the file `./config/middleware.js`.
-
-**Path —** `./config/middleware.js`.
-
-```js
-module.exports = {
- load: {
- before: ['responseTime', 'logger', 'cors', 'responses'],
- order: [
- "Define the middlewares' load order by putting their name in this array in the right order",
- ],
- after: ['parser', 'router'],
- },
-};
-```
-
-- `load`:
- - `before`: Array of middlewares that need to be loaded in the first place. The order of this array matters.
- - `order`: Array of middlewares that need to be loaded in a specific order.
- - `after`: Array of middlewares that need to be loaded at the end of the stack. The order of this array matters.
-
-#### Core middleware configurations
-
-The core of Strapi embraces a small list of middlewares for performances, security and great error handling.
-
-- boom
-- cors
-- cron
-- csp
-- favicon
-- gzip
-- hsts
-- ip
-- language
-- logger
-- p3p
-- parser
-- public
-- responses
-- responseTime
-- router
-- session
-- xframe
-- xss
+## Required configurations
-::: tip
-The following middlewares cannot be disabled: responses, router, logger and boom.
-:::
+Some parts of Strapi must be configured for the Strapi application to work properly:
-##### Global middlewares
+- the [database](/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md),
+- the [server](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md),
+- the [admin panel](/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md),
+- and the [middlewares](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md).
-- `favicon`
- - `path` (string): Path to the favicon file. Default value: `favicon.ico`.
- - `maxAge` (integer): Cache-control max-age directive in ms. Default value: `86400000`.
-- `public`
- - `path` (string): Path to the public folder. Default value: `./public`.
- - `maxAge` (integer): Cache-control max-age directive in ms. Default value: `60000`.
- - `defaultIndex` (boolean): Display default index page at `/` and `/index.html`. Default value: `true`.
+## Optional configurations
-##### Request middlewares
-
-- `session`
- - `enabled` (boolean): Enable or disable sessions. Default value: `false`.
-- `logger`
- - `level` (string): Default log level. Default value: `debug`.
- - `exposeInContext` (boolean): Expose logger in context so it can be used through `strapi.log.info(‘my log’)`. Default value: `true`.
- - `requests` (boolean): Enable or disable requests logs. Default value: `false`.
-- `parser` (See [koa-body](https://github.com/dlau/koa-body#options) for more information)
- - `enabled`(boolean): Enable or disable parser. Default value: `true`.
- - `multipart` (boolean): Enable or disable multipart bodies parsing. Default value: `true`.
- - `jsonLimit` (string|integer): The byte (if integer) limit of the JSON body. Default value: `1mb`.
- - `formLimit` (string|integer): The byte (if integer) limit of the form body. Default value: `56k`.
- - `queryStringParser` (see [qs](https://github.com/ljharb/qs) for a full list of options).
- - `arrayLimit` (integer): the maximum length of an array in the query string. Any array members with an index of greater than the limit will instead be converted to an object with the index as the key. Default value: `100`.
- - `depth` (integer): maximum parsing depth of nested query string objects. Default value: `20`.
-
-::: tip
-The session doesn't work with `mongo` as a client. The package that we should use is broken for now.
-:::
-
-##### Response middlewares
-
-- [`gzip`](https://en.wikipedia.org/wiki/Gzip)
- - `enabled` (boolean): Enable or not GZIP response compression.
- - `options` (Object): Allow passing of options from [koa-compress](https://github.com/koajs/compress#options).
-- `responseTime`
- - `enabled` (boolean): Enable or not `X-Response-Time header` to response. Default value: `false`.
-- `poweredBy`
- - `enabled` (boolean): Enable or not `X-Powered-By` header to response. Default value: `true`.
- - `value` (string): The value of the header. Default value: `Strapi `
-
-::: tip
-`gzip` compression via `koa-compress` uses [Brotli](https://en.wikipedia.org/wiki/Brotli) by default, but is not configured with sensible defaults for most cases. If you experience slow response times with `gzip` enabled, consider disabling Brotli by passing `{br: false}` as an option. You may also pass more sensible params with `{br: { params: { // YOUR PARAMS HERE } }}`
-:::
-
-##### Security middlewares
-
-- [`csp`](https://en.wikipedia.org/wiki/Content_Security_Policy)
- - `enabled` (boolean): Enable or disable CSP to avoid Cross Site Scripting (XSS) and data injection attacks.
- - `policy` (string): Configures the `Content-Security-Policy` header. If not specified uses default value. Default value: `undefined`.
-- [`p3p`](https://en.wikipedia.org/wiki/P3P)
- - `enabled` (boolean): Enable or disable p3p.
-- [`hsts`](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)
- - `enabled` (boolean): Enable or disable HSTS.
- - `maxAge` (integer): Number of seconds HSTS is in effect. Default value: `31536000`.
- - `includeSubDomains` (boolean): Applies HSTS to all subdomains of the host. Default value: `true`.
-- [`xframe`](https://en.wikipedia.org/wiki/Clickjacking)
- - `enabled` (boolean): Enable or disable `X-FRAME-OPTIONS` headers in response.
- - `value` (string): The value for the header, e.g. DENY, SAMEORIGIN or ALLOW-FROM uri. Default value: `SAMEORIGIN`.
-- [`xss`](https://en.wikipedia.org/wiki/Cross-site_scripting)
- - `enabled` (boolean): Enable or disable XSS to prevent Cross Site Scripting (XSS) attacks in older IE browsers (IE8).
-- [`cors`](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing)
- - `enabled` (boolean): Enable or disable CORS to prevent your server to be requested from another domain.
- - `origin` (string or array): Allowed URLs (`http://example1.com, http://example2.com`, `['http://www.example1.com', 'http://example1.com']` or allows everyone `*`). Default value: `*`.
- - `expose` (array): Configures the `Access-Control-Expose-Headers` CORS header. If not specified, no custom headers are exposed. Default value: `["WWW-Authenticate", "Server-Authorization"]`.
- - `maxAge` (integer): Configures the `Access-Control-Max-Age` CORS header. Default value: `31536000`.
- - `credentials` (boolean): Configures the `Access-Control-Allow-Credentials` CORS header. Default value: `true`.
- - `methods` (array)|String - Configures the `Access-Control-Allow-Methods` CORS header. Default value: `["GET", "POST", "PUT", "PATCH", "DELETE", "OPTIONS", "HEAD"]`.
- - `headers` (array): Configures the `Access-Control-Allow-Headers` CORS header. If not specified, defaults to reflecting the headers specified in the request's Access-Control-Request-Headers header. Default value: `["Content-Type", "Authorization", "X-Frame-Options"]`.
-- `ip`
- - `enabled` (boolean): Enable or disable IP blocker. Default value: `false`.
- - `whiteList` (array): Whitelisted IPs. Default value: `[]`.
- - `blackList` (array): Blacklisted IPs. Default value: `[]`.
-
-#### Example
-
-Create your custom middleware.
-
-**Path —** `./middlewares/timer/index.js`
-
-```js
-module.exports = strapi => {
- return {
- initialize() {
- strapi.app.use(async (ctx, next) => {
- const start = Date.now();
-
- await next();
-
- const delta = Math.ceil(Date.now() - start);
-
- ctx.set('X-Response-Time', delta + 'ms');
- });
- },
- };
-};
-```
-
-Enable the middleware in environments settings.
-
-Load a middleware at the very first place
-
-**Path —** `./config/middleware.js`
-
-```js
-module.exports = {
- load: {
- before: ['timer', 'responseTime', 'logger', 'cors', 'responses', 'gzip'],
- order: [
- "Define the middlewares' load order by putting their name in this array is the right order",
- ],
- after: ['parser', 'router'],
- },
- settings: {
- timer: {
- enabled: true,
- },
- },
-};
-```
-
-### Functions
-
-The `./config/functions/` folder contains a set of JavaScript files in order to add dynamic and logic based configurations.
-
-All functions that are exposed in this folder are accessible via `strapi.config.functions['fileName']();`
-
-
-
-#### Bootstrap
-
-**Path —** `./config/functions/bootstrap.js`.
-
-The `bootstrap` function is called at every server start. You can use it to add a specific logic at this moment of your server's lifecycle.
-
-Here are some use cases:
-
-- Create an admin user if there isn't one.
-- Fill the database with some necessary data.
-- Load some environment variables.
-
-The bootstrap function can be synchronous or asynchronous.
-
-**Synchronous**
-
-```js
-module.exports = () => {
- // some sync code
-};
-```
-
-**Return a promise**
-
-```js
-module.exports = () => {
- return new Promise(/* some code */);
-};
-```
-
-**Asynchronous**
-
-```js
-module.exports = async () => {
- await someSetup();
-};
-```
-
-#### CRON tasks
-
-CRON tasks allow you to schedule jobs (arbitrary functions) for execution at specific dates, with optional recurrence rules. It only uses a single timer at any given time (rather than reevaluating upcoming jobs every second/minute).
-
-This feature is powered by [`node-schedule`](https://www.npmjs.com/package/node-schedule) node modules. Check it for more information.
-
-::: warning
-Make sure the `enabled` cron config is set to `true` in `./config/server.js` file.
-:::
-
-The cron format consists of:
-
-```
-* * * * * *
-┬ ┬ ┬ ┬ ┬ ┬
-│ │ │ │ │ |
-│ │ │ │ │ └ day of week (0 - 7) (0 or 7 is Sun)
-│ │ │ │ └───── month (1 - 12)
-│ │ │ └────────── day of month (1 - 31)
-│ │ └─────────────── hour (0 - 23)
-│ └──────────────────── minute (0 - 59)
-└───────────────────────── second (0 - 59, OPTIONAL)
-```
-
-To define a CRON job, add your logic like below:
-
-**Path —** `./config/functions/cron.js`.
-
-```js
-module.exports = {
- /**
- * Simple example.
- * Every monday at 1am.
- */
-
- '0 0 1 * * 1': () => {
- // Add your own logic here (e.g. send a queue of email, create a database backup, etc.).
- },
-};
-```
-
-If your CRON task is required to run based on a specific timezone then you can configure the task like below:
-
-```js
-module.exports = {
- /**
- * CRON task with timezone example.
- * Every monday at 1am for Asia/Dhaka timezone.
- * List of valid timezones: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
- */
-
- '0 0 1 * * 1': {
- task: () => {
- // Add your own logic here (e.g. send a queue of email, create a database backup, etc.).
- },
- options: {
- tz: 'Asia/Dhaka',
- },
- },
-};
-```
-
-#### Database ORM customization
-
-When present, they are loaded to let you customize your database connection instance, for example for adding some plugin, customizing parameters, etc.
-
-You will need to install the plugin using the normal `npm install the-plugin-name` or any of the other supported package tools such as yarn then follow the below examples to load them.
-
-:::: tabs
-
-::: tab Mongoose
-
-As an example, for using the `mongoose-simple-random` plugin for MongoDB, you can register it like this:
-
-**Path —** `./config/functions/mongoose.js`.
-
-```js
-'use strict';
-
-const random = require('mongoose-simple-random');
-
-module.exports = (mongoose, connection) => {
- mongoose.plugin(random);
-};
-```
-
-:::
-
-::: tab Bookshelf
-
-Another example would be using the `bookshelf-uuid` plugin for MySQL, you can register it like this:
-
-**Path —** `./config/functions/bookshelf.js`.
-
-```js
-'use strict';
-
-module.exports = (bookshelf, connection) => {
- bookshelf.plugin('bookshelf-uuid');
-};
-```
-
-:::
-
-::::
-
-### Public assets
-
-Public assets are static files such as images, video, css, etc. that you want to make accessible to the outside world.
-
-Because an API may need to serve static assets, every new Strapi project includes by default, a folder named `/public`. Any file located in this directory is accessible if the request's path doesn't match any other defined route and if it matches a public file name.
-
-Example:
-
-An image named `company-logo.png` in `./public/` is accessible through `/company-logo.png` URL.
-
-::: tip
-`index.html` files are served if the request corresponds to a folder name (`/pictures` url will try to serve `public/pictures/index.html` file).
-:::
-
-::: warning
-The dotfiles are not exposed. It means that every file name that starts with `.`, such as `.htaccess` or `.gitignore`, are not served.
-:::
-
-### Single Sign On
-
-***
-
-Single-Sign-On on Strapi allows you to configure additional sign-in and sign-up methods for your administration panel.
-
-::: danger PREREQUISITES
-- A Strapi application running on version 3.5.0 or higher is required.
-- To configure SSO on your application, you will need an EE license with a Gold plan.
-- Make sure Strapi is part of the applications you can access with your provider. For example, with Microsoft (Azure) Active Directory, you must first ask someone with the right permissions to add Strapi to the list of allowed applications. Please refer to your provider(s) documentation to learn more about that.
-:::
-
-::: warning CAUTION
-It is currently not possible to associate a unique SSO provider to an email address used for a Strapi account, meaning that the access to a Strapi account cannot be restricted to only one SSO provider. For more information and workarounds to solve this issue, [please refer to the dedicated GitHub issue](https://github.com/strapi/strapi/issues/9466#issuecomment-783587648).
-:::
-
-#### Usage
-
-SSO configuration lives in the server configuration of your application found within `/config/server.js`.
-
-##### Accessing the configuration
-
-The providers' configuration should be written within the `admin.auth.providers` path of the server configuration.
-
-`admin.auth.providers` is an array of [provider configuration](#provider-configuration).
-
-```javascript
-module.exports = ({ env }) => ({
- // ...
- admin: {
- // ...
- auth: {
- providers: [], // The providers' configuration lives there
- },
- },
-});
-```
-
-##### Provider Configuration
-
-A provider's configuration is a Javascript object built with the following properties:
-
-| Name | Required | Type | Description |
-| ---------------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `uid` | true | string | The UID of the strategy. It must match the strategy's name |
-| `displayName` | true | string | The name that will be used on the login page to reference the provider |
-| `icon` | false | string | An image URL. If specified, it will replace the displayName on the login page |
-| `createStrategy` | true | function | A factory that will build and return a new passport strategy for your provider. Takes the strapi instance as parameter |
-
-::: tip
-The `uid` property is the unique identifier of each strategy and is generally found in the strategy's package. If you are not sure of what it refers to, please contact the maintainer of the strategy.
-:::
-
-###### The `createStrategy` Factory
-
-A passport strategy is usually built by instantiating it using 2 parameters: the configuration object, and the verify function.
-
-
-**Configuration Object**
-
-The configuration object depends on the strategy needs, but often asks for a callback URL to be redirected to once the connection has been made on the provider side.
-
-You can generate a specific callback URL for your provider using the `getStrategyCallbackURL` method. This URL also needs to be written on the provider side in order to allow redirection from it.
-
-The format of the callback URL is the following: `/admin/connect/`.
-
-::: tip
-`strapi.admin.services.passport.getStrategyCallbackURL` is a Strapi helper you can use to get a callback URL for a specific provider. It takes a provider name as a parameter and returns a URL.
-:::
-
-If needed, this is also where you will put your client ID and secret key for your OAuth2 application.
-
-**Verify Function**
-
-The verify function is used here as a middleware allowing the user to transform and make extra processing on the data returned from the provider API.
-
-This function always takes a `done` method as last parameter which is used to transfer needed data to the Strapi layer of SSO.
-
-Its signature is the following: `void done(error: any, data: object);` and it follows the following rules:
-
-- If `error` is not set to `null`, then the data sent is ignored, and the controller will throw an error.
-- If the SSO's auto-registration feature is disabled, then the `data` object only need to be composed of an `email` property.
-- If the SSO's auto-registration feature is enabled, then you will need to define (in addition to the `email`) either a `username` property or both `firstname` and `lastname` within the `data` oject.
-
-###### Adding a provider
-
-Adding a new provider means adding a new way for your administrators to log-in.
-
-To achieve a great flexibility and a large choice of provider, Strapi uses [Passport.js](http://www.passportjs.org/). Any valid passport strategy that doesn't need additional custom data should therefore work with Strapi.
-
-::: warning
-Strategies such as [ldapauth](https://github.com/vesse/passport-ldapauth) don't work out of the box since they require extra data to be sent from the admin panel.
-If you want to add an LDAP provider to your application, you will need to write a [custom strategy](http://www.passportjs.org/packages/passport-custom/).
-You can also use services such as Okta and Auth0 as bridge services.
-:::
-
-###### Configuring the provider
-
-To configure a provider, follow the procedure below:
-
-1. Make sure to import your strategy in your server configuration file, either from an installed package or a local file.
-2. You'll need to add a new item to the `admin.auth.providers` array in your server configuration that will match the [format given above](#provider-configuration)
-3. Restart your application, the provider should appear on your admin login page.
-
-##### Examples
-
-:::::: tabs
-
-::::: tab Google
-
-Using: [passport-google-oauth2](https://github.com/mstade/passport-google-oauth2)
-
-:::: tabs
-
-::: tab yarn
-
-```bash
-yarn add passport-google-oauth2
-```
-
-:::
-
-::: tab npm
-
-```bash
-npm install --save passport-google-oauth2
-```
-
-::::
-
-`/config/server.js`
-
-```jsx
-'use strict';
-
-const GoogleStrategy = require('passport-google-oauth2');
-
-module.exports = ({ env }) => ({
- // ...
- admin: {
- // ...
- auth: {
- /// ...
- providers: [
- {
- uid: 'google',
- displayName: 'Google',
- icon: 'https://cdn2.iconfinder.com/data/icons/social-icons-33/128/Google-512.png',
- createStrategy: strapi =>
- new GoogleStrategy(
- {
- clientID: env('GOOGLE_CLIENT_ID'),
- clientSecret: env('GOOGLE_CLIENT_SECRET'),
- scope: [
- 'https://www.googleapis.com/auth/userinfo.email',
- 'https://www.googleapis.com/auth/userinfo.profile',
- ],
- callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('google'),
- },
- (request, accessToken, refreshToken, profile, done) => {
- done(null, {
- email: profile.email,
- firstname: profile.given_name,
- lastname: profile.family_name,
- });
- }
- ),
- },
- ],
- },
- },
-});
-```
-
-:::::
-
-::::: tab Github
-
-Using: [passport-github](https://github.com/cfsghost/passport-github)
-
-:::: tabs
-
-::: tab yarn
-
-```bash
-yarn add passport-github2
-```
-
-:::
-
-::: tab npm
-
-```bash
-npm install --save passport-github2
-```
-
-:::
-
-::::
-
-`/config/server.js`
-
-```jsx
-'use strict';
-
-const GithubStrategy = require('passport-github2');
-
-module.exports = ({ env }) => ({
- // ...
- admin: {
- // ...
- auth: {
- // ...
- providers: [
- {
- uid: 'github',
- displayName: 'Github',
- icon: 'https://cdn1.iconfinder.com/data/icons/logotypes/32/github-512.png',
- createStrategy: strapi =>
- new GithubStrategy(
- {
- clientID: env('GITHUB_CLIENT_ID'),
- clientSecret: env('GITHUB_CLIENT_SECRET'),
- scope: ['user:email'],
- callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('github'),
- },
- (accessToken, refreshToken, profile, done) => {
- done(null, {
- email: profile.emails[0].value,
- username: profile.username,
- });
- }
- ),
- },
- ],
- },
- },
-});
-```
-
-:::::
-
-::::: tab Discord
-
-Using: [passport-discord](https://github.com/nicholastay/passport-discord#readme)
-
-:::: tabs
-
-::: tab yarn
-
-```bash
-yarn add passport-discord
-```
-
-:::
-
-::: tab npm
-
-```bash
-npm install --save passport-discord
-```
-
-:::
-
-::::
-
-`/config/server.js`
-
-```jsx
-'use strict';
-
-const DiscordStrategy = require('passport-discord');
-
-module.exports = ({ env }) => ({
- // ...
- admin: {
- // ...
- auth: {
- // ...
- providers: [
- {
- uid: 'discord',
- displayName: 'Discord',
- icon: 'https://cdn0.iconfinder.com/data/icons/free-social-media-set/24/discord-512.png',
- createStrategy: strapi =>
- new DiscordStrategy(
- {
- clientID: env('DISCORD_CLIENT_ID'),
- clientSecret: env('DISCORD_SECRET'),
- callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('discord'),
- scope: ['identify', 'email'],
- },
- (accessToken, refreshToken, profile, done) => {
- done(null, {
- email: profile.email,
- username: `${profile.username}#${profile.discriminator}`,
- });
- }
- ),
- },
- ],
- },
- },
-});
-```
-
-:::::
-::::: tab Microsoft
-
-Using: [passport-azure-ad-oauth2](https://github.com/auth0/passport-azure-ad-oauth2#readme)
-
-:::: tabs
-
-::: tab yarn
-
-```bash
-yarn add passport-azure-ad-oauth2 jsonwebtoken
-```
-
-:::
-
-::: tab npm
-
-```bash
-npm install --save passport-azure-ad-oauth2 jsonwebtoken
-```
-
-:::
-
-::::
-
-`/config/server.js`
-
-```jsx
-'use strict';
-
-const AzureAdOAuth2Strategy = require('passport-azure-ad-oauth2');
-const jwt = require('jsonwebtoken');
-
-module.exports = ({ env }) => ({
- // ...
- admin: {
- // ...
- auth: {
- // ...
- providers: [
- {
- uid: 'azure_ad_oauth2',
- displayName: 'Microsoft',
- icon:
- 'https://upload.wikimedia.org/wikipedia/commons/thumb/9/96/Microsoft_logo_%282012%29.svg/320px-Microsoft_logo_%282012%29.svg.png',
- createStrategy: strapi =>
- new AzureAdOAuth2Strategy(
- {
- clientID: env('MICROSOFT_CLIENT_ID', ''),
- clientSecret: env('MICROSOFT_CLIENT_SECRET', ''),
- scope: ['user:email'],
- tenant: env('MICROSOFT_TENANT_ID', ''),
- callbackURL: strapi.admin.services.passport.getStrategyCallbackURL(
- 'azure_ad_oauth2'
- ),
- },
- (accessToken, refreshToken, params, profile, done) => {
- var waadProfile = jwt.decode(params.id_token, '', true);
- done(null, {
- email: waadProfile.upn,
- username: waadProfile.upn,
- });
- }
- ),
- },
- ],
- },
- },
-});
-```
-
-:::::
-::::::
-
-##### Advanced Customization
-
-###### Admin Panel URL
-
-If your administration panel lives on a different host/port than your Strapi server, you will need to modify the admin URL.
-To do so, head to your `/config/server.js` configuration file and tweak the `admin.url` field.
-
-For example, if your admin application has been started on `https://api.example.com`, your configuration will look like the following:
-
-`/config/server.js`
-
-```javascript
-module.exports = () => ({
- // ...
- admin: {
- // ...
- url: 'https://api.example.com/admin',
- },
-});
-```
-
-###### Custom Logic
-
-In some scenarios, you will want to write additional logic for your connection workflow such as:
-
-- Restricting connection and registration for a specific domain
-- Triggering actions on connection attempt
-- Analytics
-
-The easiest way to do so is to plug into the verify function of your strategy and write some code.
-
-For example, if you want to allow only people with an official strapi.io email address, you can instantiate your strategy like this:
-
-```javascript
-const strategyInstance = new Strategy(configuration, ({ email, username }, done) => {
- // If the email ends with @strapi.io
- if (email.endsWith('@strapi.io')) {
- // Then we continue with the data given by the provider
- return done(null, { email, username });
- }
-
- // Otherwise, we continue by sending an error to the done function
- done(new Error('Forbidden email address'));
-});
-```
-
-###### Authentication Events
-
-The SSO feature adds a new [authentication event](/developer-docs/latest/setup-deployment-guides/configurations.md#available-options): `onSSOAutoRegistration`.
-
-This event is triggered whenever a user is created using the auto-register feature added by SSO.
-It contains the created user (`event.user`), and the provider used to make the registration (`event.provider`).
-
-Example:
-
-`/config/server.js`
-
-```javascript
-module.exports = () => ({
- // ...
- admin: {
- // ...
- auth: {
- // ...
- events: {
- onConnectionSuccess(e) {},
- onConnectionError(e) {},
- // ...
- onSSOAutoRegistration(e) {
- const { user, provider } = e;
-
- console.log(
- `A new user (${user.id}) has been automatically registered using ${provider}`
- );
- },
- },
- },
- },
-});
-```
-
-### Role-Based Access Control
-
-::: warning 🚧 This API is considered unstable for now.
-
-:::
-
-Role-Based Access Control (RBAC) is an approach to restricting access to some users. In a Strapi application, users of the admin panel are administrators. Their roles and permissions are [configured in the admin panel](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md). The Community Edition of Strapi offers 3 default roles (Author, Editor, and Super Admin). To go further, creating custom conditions for any type of permission is also possible. This requires an Enterprise Edition with at minimum a Bronze licence plan.
-
-#### Declaring new conditions
-
-Declare a single condition as an object, and multiple conditions as an array of objects. Each condition object can have 5 possible properties:
-
-- `displayName` (string): the condition name as shown in the admin panel,
-- `name` (string): the condition name, kebab-cased,
-- `category` (string, _optional_): conditions can be grouped into categories available [in the admin panel](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#setting-custom-conditions-for-permissions); if undefined, the condition will appear under the "Default" category,
-- `plugin` (string, _optional_): if the condition is created by a plugin, should be the plugin's name, kebab-cased (e.g `content-manager`),
-- `handler`: a function used to verify the condition (see [using the condition handler](#using-the-condition-handler))
-
-Declare and register conditions in your [`./config/functions/bootstrap.js`](/developer-docs/latest/setup-deployment-guides/configurations.md#bootstrap) file (see [Registering conditions](#registering-conditions)).
-
-:::tip NOTE
-The condition `name` property acts as a [unique id](https://github.com/strapi/strapi/blob/master/packages/strapi-admin/services/permission/condition-provider.js#L22) within its namespace, that is either the plugin if the `plugin` property is defined, or the root namespace.
-:::
-
-#### Using the condition handler
-
-A condition can be applied to any permission, and the condition `handler` is used to verify the condition. The `handler` is a function returning a query object or a boolean value.
-
-Query objects are useful to verify conditions on the entities you read, create, update, delete or publish. They use the [sift.js](https://github.com/crcn/sift.js) library, but only with the following supported operators:
-
-- `$or`
-- `$and`
-- `$eq`
-- `$ne`
-- `$in`
-- `$nin`
-- `$lt`
-- `$lte`
-- `$gt`
-- `$gte`
-- `$exists`
-- `$elemMatch`
-
-The condition `handler` can be a synchronous or asynchronous function that:
-
-* receives the authenticated user making the request,
-* and returns `true`, `false`, or a query object.
-
-Returning `true` or `false` is useful to verify an external condition or a condition on the authenticated user.
-For instance, a condition that allows access to a page in the admin panel only if server time is 5pm could use this handler:
-
-```js
- handler: () => new Date().getHours() === 17
-```
-
-The `handler` function receives the authenticated user, so it can verify conditions on the user:
-
-```js
-const condition = {
- displayName: "Email address from strapi.io",
- name: "email-strapi-dot-io",
- async handler(user) {
- return user.email.includes('@strapi.io');
- },
-};
-```
-
-For more granular control, the `handler` function can also return a query object:
-
-```js
- const condition = {
- displayName: "price greater than 50",
- name: "price-gt-50",
- async handler(user) {
- return { price: { $gt: 50 } };
- },
- };
-```
-
-
-#### Registering conditions
-
-To be available in the admin panel, conditions should be declared and registered in the [`./config/functions/bootstrap.js`](/developer-docs/latest/setup-deployment-guides/configurations.md#bootstrap) file. Register a single condition with the `conditionProvider.register()` method:
-
-```js
-module.exports = async () => {
- await strapi.admin.services.permission.conditionProvider.register({
- displayName: 'Billing amount under 10K',
- name: 'billing-amount-under-10k',
- plugin: 'admin',
- handler: { amount: { $lt: 10000 }},
- });
-};
-```
-
-To register multiple conditions, defined as an array of [condition objects](#declaring-new-conditions), use `conditionProvider.registerMany()`:
-
-```js
-const conditions = [
- {
- displayName: "Entity has same name as user",
- name: "same-name-as-user",
- plugin: "name of a plugin if created in a plugin"
- handler: (user) => {
- return { name: user.name };
- },
- },
- {
- displayName: "Email address from strapi.io",
- name: "email-strapi-dot-io",
- async handler(user) {
- return user.email.includes('@strapi.io');
- },
- }
-];
-
-module.exports = async () => {
- // do your boostrap
-
- await strapi.admin.services.permission.conditionProvider.registerMany(conditions);
-};
-```
+Strapi also offers the following optional configuration options for specific features:
+
+- [API tokens](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md)
+- [functions](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md)
+- [cron jobs](/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md)
+- [API calls](/developer-docs/latest/setup-deployment-guides/configurations/optional/api.md)
+- [plugins](/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md)
+- the [environment and its variables](/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md)
+- [public assets](/developer-docs/latest/setup-deployment-guides/configurations/optional/public-assets.md)
+- [Single Sign-On](/developer-docs/latest/setup-deployment-guides/configurations/optional/sso.md)
+- [Role-Based Access Control](/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.md)
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md
deleted file mode 100644
index 4dc21e0df4..0000000000
--- a/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md
+++ /dev/null
@@ -1,380 +0,0 @@
----
-title: MongoDB - Strapi Developer Documentation
-description: Learn how to install MongoDB on your computer and using it for your Strapi application.
----
-
-# MongoDB Installation
-
-::: warning WARNING
-Starting from the release of Strapi v4, MongoDB is not supported natively anymore and no connector is available. For more information, please refer to [the official communication on the topic](https://strapi.io/blog/mongo-db-support-in-strapi-past-present-and-future).
-:::
-
-## Install MongoDB locally
-
-### 1. Install MongoDB on your development environment
-
-If you already have MongoDB installed locally and running as a background service, you may skip to [Install Strapi locally with MongoDB](#_2-install-strapi-locally-with-mongodb). (If you have additional questions, please see the official [MongoDB documentation](https://docs.mongodb.com/manual/installation/#tutorial-installation). )
-
-Please complete the installation steps appropriate to your operating system.
-
-:::: tabs
-
-::: tab Windows 10
-
-### Install MongoDB on Windows 10
-
-Follow these steps to [install MongoDB onto your Windows 10](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-windows/) environment (The Windows Sub-System for Linux (WSL) is unsupported by MongoDB):
-
-1. Download the `MongoDB Community Edition Server` for Windows [here](https://www.mongodb.com/download-center/community?jmp=docs). Select `MongoDB Community Server` and verify the options that match your computer. Then `Download` the package and follow the installation instructions to complete the process.
-
-2. After successfully installing MongoDB, the MongoDB service is started. To begin using MongoDB, connect a mongo.exe shell to the running MongoDB instance.
-
-```bash
-"C:\Program Files\MongoDB\Server\4.0\bin\mongo.exe"
-```
-
-You can exit the MongoDB shell with `CTRL + C`.
-
-You have now installed MongoDB for _Windows 10_. You are now ready to [install Strapi with MongoDB locally](#_2-install-strapi-locally-with-mongodb).
-
-:::
-
-::: tab Mac
-
-### Install MongoDB on Mac
-
-Follow these steps to [install MongoDB onto your Mac](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/) developer environment:
-
-1. Use `brew` to tap the official MongoDB formula repository and add it to the formula list:
-
-```bash
-brew tap mongodb/brew
-```
-
-2. Now install MongoDB
-
-```bash
-brew install mongodb-community@4.4
-```
-
-3. Get the mongod process running in order to connect and use MongoDB:
-
-For macOS running on Intel processors:
-
-```bash
-mongod --config /usr/local/etc/mongod.conf
-```
-
-For macOS running on Apple M1 processors:
-
-```bash
-mongod --config /opt/homebrew/etc/mongod.conf
-```
-
-You have now installed MongoDB for macOS. You are now ready to [install Strapi with MongoDB locally](#_2-install-strapi-locally-with-mongodb).
-
-:::
-
-::: tab Ubuntu
-
-### Install MongoDB on Ubuntu
-
-Follow these steps to [install MongoDB onto your Ubuntu](https://docs.mongodb.com/manual/administration/install-on-linux/) environment:
-
-1. Import a public key to ensure your MongoDB is authentic:
-
-```bash
-sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 9DA31620334BD75D9DCB49F368818C72E52529D4
-```
-
-2. Next, add the repository for 18.04. Repositories for other versions of Ubuntu are found [here](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/).
-
-```bash
-echo "deb [ arch=amd64 ] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.0.list
-```
-
-3. Reload the local package database:
-
-```bash
-sudo apt-get update
-```
-
-4. Install the stable release MongoDB package
-
-```bash
-sudo apt-get install -y mongodb-org
-```
-
-5. Get the `mongod` process running in order to connect and use MongoDB:
-
-```bash
-sudo service mongod start
-```
-
-6. Confirm the MongoDB status:
-
-```bash
-service mongod status
-```
-
-7. The last step is to enable automatically starting MongoDB when your computer boots:
-
-```bash
-sudo systemctl enable mongod
-```
-
-You have now installed MongoDB for _Linux_. You are now ready to [install Strapi with MongoDB locally](#_2-install-strapi-locally-with-mongodb).
-
-:::
-
-::::
-
-### 2. Install Strapi locally with MongoDB
-
-Follow these steps to create a Strapi project locally using the MongoDB database.
-
-::: tip
-MongoDB must already be running in the background.
-:::
-
-1. Create a new Strapi project
-
-`Path: ./`
-
-:::: tabs
-
-::: tab yarn
-
-```
-yarn create strapi-app my-project
-```
-
-:::
-
-::: tab npx
-
-```
-npx create-strapi-app my-project
-```
-
-:::
-
-::::
-
-- Use your `down arrow` key and select `Custom (manual settings)` and press `enter`:
-
-```bash
-? Choose your installation type
- Quickstart (recommended)
-❯ Custom (manual settings)
-```
-
-- Select `MongoDB` and press `enter`:
-
-```bash
-? Choose your installation type Custom (manual settings)
-? Choose your main database:
- SQLite
-❯ MongoDB
- MySQL
- Postgres
-```
-
-- Press `enter` to select the remaining default options. It will look something like this:
-
-```bash
-
-? Choose your installation type Custom (manual settings)
-? Choose your main database: MongoDB
-? Database name: my-project
-? Host: 127.0.0.1
-? +srv connection: false
-? Port (It will be ignored if you enable +srv): 27017
-? Username:
-? Password:
-? Authentication database (Maybe "admin" or blank):
-? Enable SSL connection: false
-
-⏳ Testing database connection...
-The app has been connected to the database successfully!
-
-🏗 Application generation:
-✔ Copy dashboard
-✔ Installed dependencies.
-
-👌 Your new application my-project is ready at /Users/david/Desktop/Projects/my-project.
-
-⚡️ Change directory:
-$ cd my-project
-
-⚡️ Start application:
-$ strapi develop
-
-```
-
-You have successfully installed Strapi with MongoDB on your local development environment. You are now ready to [create your first user](/developer-docs/latest/getting-started/quick-start.md).
-
----
-
-## Install on Atlas: MongoDB Atlas
-
-Follow these steps to configure a local Strapi project to use a [MongoDB Atlas](https://www.mongodb.com/cloud/atlas) free 512 MB account in production. (Please see [MongoDB Atlas Documentation](https://docs.atlas.mongodb.com/getting-started/) if you have any questions.)
-
-- You must have already [created your Strapi project using MongoDB](/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md#_2-install-strapi-locally-with-mongodb).
-- You must have already created a [free MongoDB Atlas account](https://www.mongodb.com/cloud/atlas).
-
-### 1. Log in to your account to create a **Project** and a **Cluster**
-
-- First you need to `Create a new Project`.
-- Then click `Build a Cluster`, from the options page:
- - Choose **AWS** as your **Cloud Provider & Region**.
- - Select a **Region**. (Note: some **Regions** do not have a _free tier_.)
- - In **Cluster Tier**, select **Shared Sandbox**, _Tier_ `MO`.
- - In **Cluster Name**, name your cluster.
-- Click the green `Create Cluster` button. You will get a message that says, "_Your cluster is being created..._"
-
-### 2. Next, click on the `Database Access` in the left menu (under `Overview`):
-
-- Click the green `+ ADD NEW USER` button:
- - Enter a `username`.
- - Enter a `password`.
- - Under `User Privileges` ensure **`Read and write to any database`** is selected. Then click `Add User` to save.
-
-### 3. Then `whitelist` your IP address. Click into `Network Access`, under `Security` in the left menu:
-
-- Click the green `+ ADD IP ADDRESS`
-
- - Click `ADD CURRENT IP ADDRESS` or **manually** enter in an IP address to `whitelist`.
- - Leave a comment to label this IP Address. E.g. `Office`.
- - Then click the green `Confirm` button.
- - Delete the `0.0.0.0/0` configuration after testing the connection.
-
- ::: tip
- If for any reason you need to test the configuration or other aspect of your connection to the database, you may want to set back the `Allow Access from Anywhere`. Follow this steps:
- :::
-
- - Click the green `+ ADD IP ADDRESS`
- - Next add `0.0.0.0/0` in the `Whitelist Entry`. **Note:** In permanent projects you would configure this with the appropriate IP addresses.
- - Leave a comment to label this IP Address. E.g. `Anywhere`.
- - Click `Confirm`. Then wait until the status turns from `Pending` to `Active`.
-
- ::: tip
- If you are serving you Strapi project from a known IP Address then follow the following steps to `allow Network Access`.
- :::
-
- - **Manually** enter in an IP address to `whitelist`, for your Strapi server.
- - Leave a comment to label this IP Address. E.g. `Heroku Server`
- - Then click the green `Confirm` button.
-
-### 4. Retrieve database credentials
-
-MongoDB Atlas automatically exposes the database credentials into a single environment variable accessible by your app. To locate it, follow these steps:
-
-- Under `Atlas` in the left-hand, click on `Clusters`. This should take you to your `cluster`. Next, click `CONNECT` and then `Connect Your Application`.
-- Under `1. Choose your driver version`, select **DRIVER** as `Node.js` and **VERSION** as `3.6 or later`.
- ::: warning
- You **must** use `Version: 3.6 or later`.
- :::
-- This should show a **Connection String Only** similar to this:
-
-`mongodb+srv://username:@cluster0.blah.mongodb.net/myFirstDatabase?retryWrites=true&w=majority`
-
-
-
-
-::: warning
-Please note the `` after your `username`. In this example, after `mongodb+srv://username:`. You will need to replace the `` with the password you created earlier for this user in your **MongoDB Atlas** account.
-:::
-
-### 5. Update and replace your existing `/database.js` config file for the appropriate environment (development | production).
-
-Replace the contents of `/database.js` with the following and replace **< password >** with the password of the user of your database you created earlier:
-
-`Path: ./config/database.js`.
-
-:::: tabs
-
-::: tab Uri Method
-
-This method uses the URI string aqcuired from Atlas in step 4.
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {
- uri: env('DATABASE_URI'),
- srv: env.bool('DATABASE_SRV', true),
- port: env.int('DATABASE_PORT', 27017),
- database: env('DATABASE_NAME'),
- },
- options: {
- authenticationDatabase: env('AUTHENTICATION_DATABASE', null),
- ssl: env.bool('DATABASE_SSL', true),
- },
- },
- },
-})
-
-```
-
-`Path: .env`
-
-```
-DATABASE_URI=mongodb+srv://username:@cluster0.blah.mongodb.net/myFirstDatabase?retryWrites=true&w=majority
-DATABASE_NAME=myFirstDatabase
-```
-
-
-:::
-
-::: tab Combined Method
-
-This method connects via passing individual connection settings.
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {
- host: env('DATABASE_HOST'),
- srv: env.bool('DATABASE_SRV', true),
- port: env.int('DATABASE_PORT', 27017),
- database: env('DATABASE_NAME'),
- username: env('DATABASE_USERNAME'),
- password: env('DATABASE_PASSWORD'),
- },
- options: {
- authenticationDatabase: env('AUTHENTICATION_DATABASE', null),
- ssl: env.bool('DATABASE_SSL', true),
- },
- },
- },
-})
-
-```
-
-`Path: .env`
-
-```
-DATABASE_HOST=cluster0.blah.mongodb.net
-DATABASE_NAME=myFirstDatabase
-DATABASE_USERNAME=admin
-DATABASE_PASSWORD=yourpassword
-```
-
-
-:::
-
-::::
-
-::: danger WARNING
-We recommend replacing sensitive (eg. "URI string" above) information in your database configuration files before uploading your project to a public repository such as GitHub. For more information about using environment variables, please read [configurations](/developer-docs/latest/setup-deployment-guides/configurations.md).
-
-:::
-
-You are now ready use Strapi locally or to deploy your project to an external hosting provider and use MongoDB Atlas as your database server.
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/sqlite.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/sqlite.md
index e245171a41..cf7bd18d63 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/sqlite.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/databases/sqlite.md
@@ -1,6 +1,7 @@
---
-title: SQLite - Strapi Developer Documentation
+title: SQLite - Strapi Developer Docs
description: Learn how you can use SQLite for your Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/databases/sqlite.html
---
# SQLite Installation
@@ -11,35 +12,31 @@ SQLite is the default ([Quick Start](/developer-docs/latest/getting-started/quic
Simply use one of the following commands.
-:::: tabs
+
-::: tab yarn
-
-```bash
-yarn create strapi-app my-project --quickstart
+
+```sh
+npx create-strapi-app@latest my-project --quickstart
```
+
-:::
-
-::: tab npx
-
-```bash
-npx create-strapi-app my-project --quickstart
+
+```sh
+yarn create strapi-app my-project --quickstart
```
+
-:::
-
-::::
+
This will create a new project and launch it in the browser.
::: tip
-The [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md) is a complete step-by-step tutorial
+The [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md) is a complete step-by-step tutorial.
:::
## Other SQL Databases (PostgreSQL, MySQL)
-Refer to the [configuration section](/developer-docs/latest/setup-deployment-guides/configurations.md#database) for all supported options to setup Strapi with your SQL database.
+Refer to the [configuration section](/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md) for all supported options to setup Strapi with your SQL database.
::: tip
Most cloud service providers offer a managed SQL database service, which is a hassle-free way to get your database up and running. To get up and running locally, you might want to try using a Docker container.
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md
new file mode 100644
index 0000000000..0af61a8009
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md
@@ -0,0 +1,31 @@
+---
+title: API tokens - Strapi Developer Docs
+description:
+---
+
+# API tokens
+
+Authentication strategies in Strapi can either be based on the use of the [Users & Permissions plugin](/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.md) or on the built-in API token feature.
+
+Using API tokens allows executing a request on [REST API](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md) endpoints as an authenticated user.
+
+## Creation
+
+New API tokens are generated from the [admin panel](/user-docs/latest/settings/managing-global-settings.md#managing-api-tokens).
+
+## Usage
+
+When performing a request to Strapi's [REST API](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md), the API token should be added to the request's `Authorization` header with the following syntax: `bearer your-api-token`.
+
+## Configuration
+
+New API tokens are generated using a salt. This salt is automatically generated by Strapi and stored in `./config/admin.js` as `apiToken.salt`.
+
+The salt can be customized:
+
+- either by updating the string value for `apiToken.salt` in `./config/admin.js` (see [admin panel configuration documentation](/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md))
+- or by creating an `API_TOKEN_SALT` [environment variable](/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md#strapi-s-environment-variables) in the `.env` file of the project
+
+::: caution
+Changing the salt invalidates all the existing API tokens.
+:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/api.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/api.md
new file mode 100644
index 0000000000..b093705ab0
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/api.md
@@ -0,0 +1,33 @@
+---
+title: API configuration - Strapi Developer Docs
+description: Strapi's default API parameters can be configured.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/api.html
+---
+
+# API configuration
+
+General settings for API calls can be set in the `./config/api.js` file:
+
+| Property | Description | Type | Default |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------- |
+| `responses` | Global API response configuration | Object | - |
+| `responses.privateAttributes` | Set of globally defined attributes to be treated as private. | String array | `[]` |
+| `rest` | REST API configuration | Object | - |
+| `rest.defaultLimit` | Default `limit` parameter used in API calls (see [REST API documentation](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#pagination-by-offset)) | Integer | `25` |
+| `rest.maxLimit` | Maximum allowed number that can be requested as `limit` (see [REST API documentation](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#pagination-by-offset)).
Defaults to `null`, which fetches all results. | Integer | `100` |
+
+**Example:**
+
+```js
+// path: ./config/api.js
+
+module.exports = ({ env }) => ({
+ responses: {
+ privateAttributes: ['_v', 'id', 'created_at'],
+ },
+ rest: {
+ defaultLimit: 100,
+ maxLimit: 250,
+ },
+});
+```
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md
new file mode 100644
index 0000000000..877ccb4a8f
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md
@@ -0,0 +1,97 @@
+---
+title: Cron jobs - Strapi Developer Docs
+description: Strapi allows you to configure cron jobs for execution at specific dates and times, with optional reccurence rules.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.html
+---
+
+# Cron jobs
+
+:::prerequisites
+The `cron.enabled` configuration option should be set to `true` in [the `./config/server.js` file](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md).
+:::
+
+`cron` allows scheduling arbitrary functions for execution at specific dates, with optional recurrence rules. These functions are named cron jobs. `cron` only uses a single timer at any given time, rather than reevaluating upcoming jobs every second/minute.
+
+This feature is powered by the [`node-schedule`](https://www.npmjs.com/package/node-schedule) package.
+
+The `cron` format consists of:
+
+```
+
+* * * * * *
+┬ ┬ ┬ ┬ ┬ ┬
+│ │ │ │ │ |
+│ │ │ │ │ └ day of week (0 - 7) (0 or 7 is Sun)
+│ │ │ │ └───── month (1 - 12)
+│ │ │ └────────── day of month (1 - 31)
+│ │ └─────────────── hour (0 - 23)
+│ └──────────────────── minute (0 - 59)
+└───────────────────────── second (0 - 59, OPTIONAL)
+
+```
+
+To define cron jobs and have them run at the required times:
+
+1. [Create](#creating-a-cron-job) the appropriate file.
+2. [Enable](#enabling-cron-jobs) the cron jobs in the server configuration file.
+
+::: tip
+Optionally, cron jobs can be directly created in the `cron.tasks` key of the [server configuration file](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md).
+:::
+
+## Creating a cron job
+
+To define a cron job, create a file with the following structure:
+
+```js
+// path: ./config/cron-tasks.js
+
+module.exports = {
+ /**
+ * Simple example.
+ * Every monday at 1am.
+ */
+
+ '0 0 1 * * 1': ({ strapi }) => {
+ // Add your own logic here (e.g. send a queue of email, create a database backup, etc.).
+ },
+};
+```
+
+If the cron job is required to run based on a specific timezone, configure it like the following:
+
+```js
+module.exports = {
+ /**
+ * Cron job with timezone example.
+ * Every Monday at 1am for Asia/Dhaka timezone.
+ * List of valid timezones: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
+ */
+
+ '0 0 1 * * 1': {
+ task: ({ strapi }) => { /* Add your own logic here */ },
+ options: {
+ tz: 'Asia/Dhaka',
+ },
+ },
+};
+```
+
+## Enabling cron jobs
+
+To enable cron jobs, set `cron.enabled` to `true` in the [server configuration file](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md) and declare the jobs:
+
+```js
+// path: ./config/server.js
+
+const cronTasks = require("./cron-tasks");
+
+module.exports = ({ env }) => ({
+ host: env("HOST", "0.0.0.0"),
+ port: env.int("PORT", 1337),
+ cron: {
+ enabled: true,
+ tasks: cronTasks,
+ },
+});
+```
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md
new file mode 100644
index 0000000000..350a73b256
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md
@@ -0,0 +1,122 @@
+---
+title: Environment configuration and variables - Strapi Developer Docs
+description: In case you need specific static configurations for specific environments, configurations can be created per environment.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.html
+---
+
+# Environment configuration and variables
+
+Strapi provides environment variables that can be used in configuration files. An `env()` utility can be used to [retrieve the value of environment variables](#configuration-using-environment-variables) and [cast variables to different types](#casting-environment-variables), and specific [configurations for different environments](#environment-configurations) can be created.
+## Strapi's environment variables
+
+Strapi provides the following environment variables:
+
+| Setting | Description | Type | Default value |
+| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | --------------- |
+| `STRAPI_DISABLE_UPDATE_NOTIFICATION` | Don't show the notification message about updating strapi in the terminal | `Boolean` | `false` |
+| `STRAPI_HIDE_STARTUP_MESSAGE` | Don't show the startup message in the terminal | `Boolean` | `false` |
+| `STRAPI_TELEMETRY_DISABLED` | Don't send telemetry usage data to Strapi | `Boolean` | `false` |
+| `STRAPI_LICENSE` | The license key to activate the Enterprise Edition | `String` | `undefined` |
+| `NODE_ENV` | Type of environment where the app is running | `String` | `'development'` |
+| `BROWSER` | Open the admin panel in the browser after startup | `Boolean` | `true` |
+| `ENV_PATH` | Path to the file that contains your environment variables | `String` | `'./.env'` |
+| `STRAPI_PLUGIN_I18N_INIT_LOCALE_CODE`
_Optional_ | Initialization locale for the app, if the [Internationalization (i18n) plugin](/developer-docs/latest/plugins/i18n.md) is installed and enabled on Content-Types (see [Configuration of i18n in production environments](/developer-docs/latest/plugins/i18n.md#configuration-in-production-environments)) | `String` | `'en'` |
+| `API_TOKEN_SALT`
_Optional_ | Salt to use to generate [API tokens](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md) | `String` | - |
+
+## Configuration using environment variables
+
+In most use cases there will be different configurations between environments (e.g. database credentials).
+
+Instead of writing those credentials into configuration files, variables can be defined in a `.env` file at the root of the application:
+
+```sh
+# path: .env
+
+DATABASE_PASSWORD=acme
+```
+
+To customize the path of the `.env` file to load, set an environment variable called `ENV_PATH` before starting the application:
+
+```sh
+$ ENV_PATH=/absolute/path/to/.env npm run start
+```
+
+Variables defined in the `.env` file are accessible using `process.env.{variableName}` anywhere in configuration and application files.
+
+In configuration files, a `env()` utility allows defining defaults and [casting values](#casting-environment-variables):
+
+```js
+// path: ./config/database.js
+
+module.exports = ({ env }) => ({
+ connections: {
+ default: {
+ settings: {
+ password: env('DATABASE_PASSWORD'),
+ },
+ },
+ },
+});
+```
+
+### Casting environment variables
+
+The `env()` utility can be used to cast environment varibles to different types:
+
+```js
+// Returns the env if defined without casting it
+env('VAR', 'default');
+
+// Cast to integer (using parseInt)
+env.int('VAR', 0);
+
+// Cast to float (using parseFloat)
+env.float('VAR', 3.14);
+
+// Cast to boolean (check if the value is equal to 'true')
+env.bool('VAR', true);
+
+// Cast to JS object (using JSON.parse)
+env.json('VAR', { key: 'value' });
+
+// Cast to array (syntax: ENV_VAR=[value1, value2, value3] | ENV_VAR=["value1", "value2", "value3"])
+env.array('VAR', [1, 2, 3]);
+
+// Case to date (using new Date(value))
+env.date('VAR', new Date());
+```
+
+## Environment configurations
+
+Configurations can be created with the following naming and structure conventions: `./config/env/{environment}/{filename}`. This is useful when you need specific static configurations for specific environments and using environment variables is not the best solution.
+
+These configurations will be merged into the base configurations defined in the `./config` folder.
+The environment is based on the `NODE_ENV` environment variable, which defaults to `development`.
+
+When starting Strapi with `NODE_ENV=production` it will load the configuration from `./config/*` and `./config/env/production/*`. Everything defined in the production configuration will override the default configuration. In combination with environment variables this pattern becomes really powerful.
+
+For instance, using the following configuration files will give you various options to start the server:
+
+```js
+// path: ./config/server.js
+
+module.exports = {
+ host: '127.0.0.1',
+};
+
+
+// path: ./config/env/production/server.js
+
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+});
+```
+
+With these configuration files the server will start on various ports depending on the environment variables passed:
+
+```bash
+yarn start # uses host 127.0.0.1
+NODE_ENV=production yarn start # uses host 0.0.0.0
+HOST=10.0.0.1 NODE_ENV=production yarn start # uses host 10.0.0.1
+```
+
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md
new file mode 100644
index 0000000000..0969a68f24
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md
@@ -0,0 +1,64 @@
+---
+title: Functions - Strapi Developer Docs
+description: Strapi includes life cycle functions (e.g. register, bootstrap and destroy) that control the flow of your application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.html
+---
+
+# Functions
+
+The `./src/index.js` file includes global [register](#register), [bootstrap](#bootstrap) and [destroy](#destroy) functions that can be used to add dynamic and logic-based configurations.
+
+## Register
+
+The `register` found in `./src/index.js` lifecycle function is an asynchronous function that runs before the application is initialized.
+It can be used to:
+
+- [extend plugins](/developer-docs/latest/development/plugins-extension.md#extending-a-plugin-s-interface)
+- extend [content-types](/developer-docs/latest/development/backend-customization/models.md) programmatically
+- load some [environment variables](/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md).
+
+## Bootstrap
+
+The `bootstrap` lifecycle function found in `./src/index.js` is called at every server start.
+
+It can be used to:
+
+- create an admin user if there isn't one
+- fill the database with some necessary data
+- declare custom conditions for the [Role-Based Access Control (RBAC)](/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.md) feature
+
+The bootstrap function can be synchronous, asynchronous, or return a premise:
+
+**Synchronous function**
+
+```js
+module.exports = () => {
+ // some sync code
+};
+```
+
+**Asynchronous function**
+
+```js
+module.exports = async () => {
+ await someSetup();
+};
+```
+
+**Function returning a promise**
+
+```js
+module.exports = () => {
+ return new Promise(/* some code */);
+};
+```
+
+
+## Destroy
+
+The `destroy` function found in `./src/index.js` is an asynchronous function that runs before the application gets shut down.
+
+It can be used to gracefully:
+
+- stop [services](/developer-docs/latest/development/backend-customization/services.md) that are running
+- [clean up plugin actions](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#destroy) (e.g. close connections, remove listeners, etc.).
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md
new file mode 100644
index 0000000000..2a4c9ed308
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.md
@@ -0,0 +1,65 @@
+---
+title: Plugins configuration - Strapi Developer Docs
+description: Strapi plugins have a single entry point file to define their configurations.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/plugins.html
+---
+
+# Plugins configuration
+
+The configurations for all plugins are stored in `/config/plugins.js` (see [project structure](/developer-docs/latest/setup-deployment-guides/file-structure.md)). Each plugin can be configured with the following available parameters:
+
+| Parameter | Description | Type |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| `enabled` | Enable (`true`) or disable (`false`) an installed plugin | Boolean |
+| `config`
_Optional_ | Used to override default plugin configuration ([defined in strapi-server.js](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#configuration)) | Object |
+| `resolve`
_Optional_ | Path to the plugin's folder | String |
+
+```js
+// path: ./config/plugins.js
+
+module.exports = ({ env }) => ({
+ // enable a plugin that doesn't require any configuration
+ i18n: true,
+
+ // enable a custom plugin
+ myplugin: {
+ // my-plugin is going to be the internal name used for this plugin
+ enabled: true,
+ resolve: './src/plugins/my-local-plugin',
+ config: {
+ // user plugin config goes here
+ },
+ },
+
+ // disable a plugin
+ myotherplugin: {
+ enabled: false, // plugin installed but disabled
+ },
+});
+```
+
+:::tip
+If no specific configuration is required, a plugin can also be declared with the shorthand syntax `'plugin-name': true`.
+:::
+
+## GraphQL configuration
+
+The [GraphQL plugin](/developer-docs/latest/plugins/graphql.md) has the following specific configuration options:
+
+| Parameter | Description | Type |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ------------- |
+| `defaultLimit` | Default value for [the `pagination[limit]` parameter](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md#pagination-by-offset) used in API calls | `Integer` |
+| `maxLimit` | Maximum value for [the `pagination[limit]` parameter](/developer-docs/latest/developer-resources/database-apis-reference/graphql-api.md#pagination-by-offset) used in API calls | `Integer` |
+
+```js
+// path: ./config/plugins.js
+
+module.exports = () => ({
+ graphql: {
+ enabled: true,
+ config: {
+ defaultLimit: 10,
+ maxLimit: 20
+ }
+})
+```
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/public-assets.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/public-assets.md
new file mode 100644
index 0000000000..0615a5151b
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/public-assets.md
@@ -0,0 +1,19 @@
+---
+title: Public assets configuration - Strapi Developer Docs
+description: The public folder of Strapi is used for static files that you want to make accesible to the outside world.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/public-assets.html
+---
+
+# Public assets configuration
+
+Public assets are static files (e.g. images, video, CSS files, etc.) that you want to make accessible to the outside world.
+
+Because an API may need to serve static assets, every new Strapi project includes by default a folder named `/public`. Any file located in this directory is accessible if the request's path doesn't match any other defined route and if it matches a public file name (e.g. an image named `company-logo.png` in `./public/` is accessible through `/company-logo.png` URL).
+
+::: tip
+`index.html` files are served if the request corresponds to a folder name (`/pictures` url will try to serve `public/pictures/index.html` file).
+:::
+
+:::caution
+The dotfiles are not exposed. It means that every file name that starts with `.`, such as `.htaccess` or `.gitignore`, are not served.
+:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.md
new file mode 100644
index 0000000000..6ee3676b5c
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.md
@@ -0,0 +1,127 @@
+---
+title: Role-Based Access Control (RBAC) - Strapi Developer Docs
+description: In Strapi, RBAC is an approach to restricting access to some features of the admin panel to some users. The Community Edition of Strapi offers 3 default roles.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.html
+---
+
+# Role-Based Access Control
+
+:::caution 🚧 This API is considered unstable for now.
+
+:::
+
+Role-Based Access Control (RBAC) is an approach to restricting access to some users. In a Strapi application, users of the admin panel are administrators. Their roles and permissions are [configured in the admin panel](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md). The Community Edition of Strapi offers 3 default roles (Author, Editor, and Super Admin). To go further, creating custom conditions for any type of permission is also possible. This requires an Enterprise Edition with at minimum a Bronze licence plan.
+
+## Declaring new conditions
+
+Declare a single condition as an object, and multiple conditions as an array of objects. Each condition object can have 5 possible properties:
+
+- `displayName` (string): the condition name as shown in the admin panel,
+- `name` (string): the condition name, kebab-cased,
+- `category` (string, _optional_): conditions can be grouped into categories available [in the admin panel](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#setting-custom-conditions-for-permissions); if undefined, the condition will appear under the "Default" category,
+- `plugin` (string, _optional_): if the condition is created by a plugin, should be the plugin's name, kebab-cased (e.g `content-manager`),
+- `handler`: a function used to verify the condition (see [using the condition handler](#using-the-condition-handler))
+
+Declare and register conditions in the global [`bootstrap` function](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md#bootstrap) found in `./src/index.js` (see [Registering conditions](#registering-conditions)).
+
+:::note
+The condition `name` property acts as a [unique id](https://github.com/strapi/strapi/blob/master/packages/strapi-admin/services/permission/condition-provider.js#L22) within its namespace, that is either the plugin if the `plugin` property is defined, or the root namespace.
+:::
+
+## Using the condition handler
+
+A condition can be applied to any permission, and the condition `handler` is used to verify the condition. The `handler` is a function returning a query object or a boolean value.
+
+Query objects are useful to verify conditions on the entities you read, create, update, delete or publish. They use the [sift.js](https://github.com/crcn/sift.js) library, but only with the following supported operators:
+
+- `$or`
+- `$and`
+- `$eq`
+- `$ne`
+- `$in`
+- `$nin`
+- `$lt`
+- `$lte`
+- `$gt`
+- `$gte`
+- `$exists`
+- `$elemMatch`
+
+The condition `handler` can be a synchronous or asynchronous function that:
+
+- receives the authenticated user making the request,
+- and returns `true`, `false`, or a query object.
+
+Returning `true` or `false` is useful to verify an external condition or a condition on the authenticated user.
+For instance, a condition that allows access to a page in the admin panel only if server time is 5pm could use this handler:
+
+```js
+handler: () => new Date().getHours() === 17;
+```
+
+The `handler` function receives the authenticated user, so it can verify conditions on the user:
+
+```js
+const condition = {
+ displayName: 'Email address from strapi.io',
+ name: 'email-strapi-dot-io',
+ async handler(user) {
+ return user.email.includes('@strapi.io');
+ },
+};
+```
+
+For more granular control, the `handler` function can also return a query object:
+
+```js
+const condition = {
+ displayName: 'price greater than 50',
+ name: 'price-gt-50',
+ async handler(user) {
+ return { price: { $gt: 50 } };
+ },
+};
+```
+
+## Registering conditions
+
+To be available in the admin panel, conditions should be declared and registered in the global [`bootstrap` function](/developer-docs/latest/setup-deployment-guides/configurations/optional/functions.md#bootstrap) found in `./src/index.js`. Register a single condition with the `conditionProvider.register()` method:
+
+```js
+module.exports = async () => {
+ await strapi.admin.services.permission.conditionProvider.register({
+ displayName: 'Billing amount under 10K',
+ name: 'billing-amount-under-10k',
+ plugin: 'admin',
+ handler: { amount: { $lt: 10000 } },
+ });
+};
+```
+
+To register multiple conditions, defined as an array of [condition objects](#declaring-new-conditions), use `conditionProvider.registerMany()`:
+
+```js
+const conditions = [
+ {
+ displayName: "Entity has same name as user",
+ name: "same-name-as-user",
+ plugin: "name of a plugin if created in a plugin"
+ handler: (user) => {
+ return { name: user.name };
+ },
+ },
+ {
+ displayName: "Email address from strapi.io",
+ name: "email-strapi-dot-io",
+ async handler(user) {
+ return user.email.includes('@strapi.io');
+ },
+ }
+];
+
+module.exports = async () => {
+ // do your boostrap
+
+ await strapi.admin.services.permission.conditionProvider.registerMany(conditions);
+};
+```
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/sso.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/sso.md
new file mode 100644
index 0000000000..a2c1fd3480
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/optional/sso.md
@@ -0,0 +1,511 @@
+---
+title: Single Sign-On (SSO) - Strapi Developer Docs
+description: Strapi's SSO allows you to configure additional sign-in and sign-up methods for your administration panel. It requires an Entreprise Edition with a Gold plan.
+sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/optional/sso.html
+---
+
+# Single Sign-On
+
+Single Sign-On on Strapi allows you to configure additional sign-in and sign-up methods for your administration panel.
+
+::: prerequisites
+
+- A Strapi application running on version 3.5.0 or higher is required.
+- To configure SSO on your application, you will need an EE license with a [Gold plan](https://strapi.io/pricing-self-hosted).
+- Make sure Strapi is part of the applications you can access with your provider. For example, with Microsoft (Azure) Active Directory, you must first ask someone with the right permissions to add Strapi to the list of allowed applications. Please refer to your provider(s) documentation to learn more about that.
+ :::
+
+:::caution
+It is currently not possible to associate a unique SSO provider to an email address used for a Strapi account, meaning that the access to a Strapi account cannot be restricted to only one SSO provider. For more information and workarounds to solve this issue, [please refer to the dedicated GitHub issue](https://github.com/strapi/strapi/issues/9466#issuecomment-783587648).
+:::
+
+SSO configuration lives in the server configuration of the application, found at `./config/admin.js`.
+
+## Accessing the configuration
+
+The providers' configuration should be written within the `auth.providers` path of the admin panel configuration.
+
+`auth.providers` is an array of [provider configuration](#setting-up-provider-configuration).
+
+```javascript
+// path: ./config/admin.js
+
+module.exports = ({ env }) => ({
+ // ...
+ auth: {
+ providers: [], // The providers' configuration lives there
+ },
+});
+```
+
+## Setting up provider configuration
+
+A provider's configuration is a JavaScript object built with the following properties:
+
+| Name | Required | Type | Description |
+| ---------------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
+| `uid` | true | string | The UID of the strategy. It must match the strategy's name |
+| `displayName` | true | string | The name that will be used on the login page to reference the provider |
+| `icon` | false | string | An image URL. If specified, it will replace the displayName on the login page |
+| `createStrategy` | true | function | A factory that will build and return a new passport strategy for your provider. Takes the strapi instance as parameter |
+
+::: tip
+The `uid` property is the unique identifier of each strategy and is generally found in the strategy's package. If you are not sure of what it refers to, please contact the maintainer of the strategy.
+:::
+
+::: note
+By default, Strapi security policy does not allow loading images from external URLs, so provider logos will not show up on the [login screen](/user-docs/latest/getting-started/introduction.md#accessing-the-admin-panel) of the admin panel unless [a security exception is added](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md#security).
+:::
+
+### The `createStrategy` Factory
+
+A passport strategy is usually built by instantiating it using 2 parameters: the configuration object, and the verify function.
+
+#### Configuration Object
+
+The configuration object depends on the strategy needs, but often asks for a callback URL to be redirected to once the connection has been made on the provider side.
+
+A specific callback URL can be generated for your provider using the `getStrategyCallbackURL` method. This URL also needs to be written on the provider side in order to allow redirection from it.
+
+The format of the callback URL is the following: `/admin/connect/`.
+
+::: tip
+`strapi.admin.services.passport.getStrategyCallbackURL` is a Strapi helper you can use to get a callback URL for a specific provider. It takes a provider name as a parameter and returns a URL.
+:::
+
+If needed, this is also where you will put your client ID and secret key for your OAuth2 application.
+
+**Verify Function**
+
+The verify function is used here as a middleware allowing the user to transform and make extra processing on the data returned from the provider API.
+
+This function always takes a `done` method as last parameter which is used to transfer needed data to the Strapi layer of SSO.
+
+Its signature is the following: `void done(error: any, data: object);` and it follows the following rules:
+
+- If `error` is not set to `null`, then the data sent is ignored, and the controller will throw an error.
+- If the SSO's auto-registration feature is disabled, then the `data` object only need to be composed of an `email` property.
+- If the SSO's auto-registration feature is enabled, then you will need to define (in addition to the `email`) either a `username` property or both `firstname` and `lastname` within the `data` oject.
+
+### Adding a provider
+
+Adding a new provider means adding a new way for your administrators to log-in.
+
+To achieve a great flexibility and a large choice of provider, Strapi uses [Passport.js](http://www.passportjs.org/). Any valid passport strategy that doesn't need additional custom data should therefore work with Strapi.
+
+:::caution
+Strategies such as [ldapauth](https://github.com/vesse/passport-ldapauth) don't work out of the box since they require extra data to be sent from the admin panel.
+If you want to add an LDAP provider to your application, you will need to write a [custom strategy](http://www.passportjs.org/packages/passport-custom/).
+You can also use services such as Okta and Auth0 as bridge services.
+:::
+
+### Configuring the provider
+
+To configure a provider, follow the procedure below:
+
+1. Make sure to import your strategy in your server configuration file, either from an installed package or a local file.
+2. You'll need to add a new item to the `auth.providers` array in your admin panel configuration that will match the [format given above](#setting-up-provider-configuration)
+3. Restart your application, the provider should appear on your admin login page.
+
+### Configuration providers examples
+
+#### Google
+
+Using: [passport-google-oauth2](https://github.com/mstade/passport-google-oauth2)
+
+
+
+
+```sh
+npm install --save passport-google-oauth2
+```
+
+
+
+```sh
+yarn add passport-google-oauth2
+```
+
+
+
+
+::: details Configuration example for Google:
+
+```jsx
+// path: ./config/admin.js
+
+'use strict';
+
+const GoogleStrategy = require('passport-google-oauth2');
+
+module.exports = ({ env }) => ({
+ // ...
+ admin: {
+ // ...
+ auth: {
+ /// ...
+ providers: [
+ {
+ uid: 'google',
+ displayName: 'Google',
+ icon: 'https://cdn2.iconfinder.com/data/icons/social-icons-33/128/Google-512.png',
+ createStrategy: strapi =>
+ new GoogleStrategy(
+ {
+ clientID: env('GOOGLE_CLIENT_ID'),
+ clientSecret: env('GOOGLE_CLIENT_SECRET'),
+ scope: [
+ 'https://www.googleapis.com/auth/userinfo.email',
+ 'https://www.googleapis.com/auth/userinfo.profile',
+ ],
+ callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('google'),
+ },
+ (request, accessToken, refreshToken, profile, done) => {
+ done(null, {
+ email: profile.email,
+ firstname: profile.given_name,
+ lastname: profile.family_name,
+ });
+ }
+ ),
+ },
+ ],
+ },
+ },
+});
+```
+
+:::
+
+#### Github
+
+
+Using: [passport-github](https://github.com/cfsghost/passport-github)
+
+
+
+
+```sh
+npm install --save passport-github2
+```
+
+
+
+```sh
+yarn add passport-github2
+```
+
+
+
+
+::: details Configuration example for Github:
+
+```jsx
+// path: ./config/admin.js
+
+'use strict';
+
+const GithubStrategy = require('passport-github2');
+
+module.exports = ({ env }) => ({
+ // ...
+ admin: {
+ // ...
+ auth: {
+ // ...
+ providers: [
+ {
+ uid: 'github',
+ displayName: 'Github',
+ icon: 'https://cdn1.iconfinder.com/data/icons/logotypes/32/github-512.png',
+ createStrategy: strapi =>
+ new GithubStrategy(
+ {
+ clientID: env('GITHUB_CLIENT_ID'),
+ clientSecret: env('GITHUB_CLIENT_SECRET'),
+ scope: ['user:email'],
+ callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('github'),
+ },
+ (accessToken, refreshToken, profile, done) => {
+ done(null, {
+ email: profile.emails[0].value,
+ username: profile.username,
+ });
+ }
+ ),
+ },
+ ],
+ },
+ },
+});
+```
+
+:::
+
+#### Discord
+
+Using: [passport-discord](https://github.com/nicholastay/passport-discord#readme)
+
+
+
+
+```sh
+npm install --save passport-discord
+```
+
+
+
+```sh
+yarn add passport-discord
+```
+
+
+
+
+::: details Configuration example for Discord:
+
+```jsx
+// path: ./config/admin.js
+
+'use strict';
+
+const DiscordStrategy = require('passport-discord');
+
+module.exports = ({ env }) => ({
+ // ...
+ admin: {
+ // ...
+ auth: {
+ // ...
+ providers: [
+ {
+ uid: 'discord',
+ displayName: 'Discord',
+ icon: 'https://cdn0.iconfinder.com/data/icons/free-social-media-set/24/discord-512.png',
+ createStrategy: strapi =>
+ new DiscordStrategy(
+ {
+ clientID: env('DISCORD_CLIENT_ID'),
+ clientSecret: env('DISCORD_SECRET'),
+ callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('discord'),
+ scope: ['identify', 'email'],
+ },
+ (accessToken, refreshToken, profile, done) => {
+ done(null, {
+ email: profile.email,
+ username: `${profile.username}#${profile.discriminator}`,
+ });
+ }
+ ),
+ },
+ ],
+ },
+ },
+});
+```
+
+:::
+
+#### Microsoft
+
+Using: [passport-azure-ad-oauth2](https://github.com/auth0/passport-azure-ad-oauth2#readme)
+
+
+
+
+```sh
+npm install --save passport-azure-ad-oauth2 jsonwebtoken
+```
+
+
+
+```sh
+yarn add passport-azure-ad-oauth2 jsonwebtoken
+```
+
+
+
+
+::: details Configuration example for Microsoft:
+
+```jsx
+// path: ./config/admin.js
+
+'use strict';
+
+const AzureAdOAuth2Strategy = require('passport-azure-ad-oauth2');
+const jwt = require('jsonwebtoken');
+
+module.exports = ({ env }) => ({
+ // ...
+ admin: {
+ // ...
+ auth: {
+ // ...
+ providers: [
+ {
+ uid: 'azure_ad_oauth2',
+ displayName: 'Microsoft',
+ icon:
+ 'https://upload.wikimedia.org/wikipedia/commons/thumb/9/96/Microsoft_logo_%282012%29.svg/320px-Microsoft_logo_%282012%29.svg.png',
+ createStrategy: strapi =>
+ new AzureAdOAuth2Strategy(
+ {
+ clientID: env('MICROSOFT_CLIENT_ID', ''),
+ clientSecret: env('MICROSOFT_CLIENT_SECRET', ''),
+ scope: ['user:email'],
+ tenant: env('MICROSOFT_TENANT_ID', ''),
+ callbackURL: strapi.admin.services.passport.getStrategyCallbackURL(
+ 'azure_ad_oauth2'
+ ),
+ },
+ (accessToken, refreshToken, params, profile, done) => {
+ var waadProfile = jwt.decode(params.id_token, '', true);
+ done(null, {
+ email: waadProfile.upn,
+ username: waadProfile.upn,
+ });
+ }
+ ),
+ },
+ ],
+ },
+ },
+});
+```
+
+:::
+
+#### Okta
+
+Using: [passport-okta-oauth20](https://github.com/antoinejaussoin/passport-okta-oauth20/blob/main/README.md)
+
+
+
+
+```sh
+npm install --save passport-okta-oauth20
+```
+
+
+
+```sh
+yarn add passport-okta-oauth20
+```
+
+
+
+
+::: details Configuration example for Okta:
+
+```jsx
+// path: ./config/admin.js
+
+'use strict';
+
+const OktaOAuth2Strategy = require('passport-okta-oauth20').Strategy;
+
+module.exports = ({ env }) => ({
+ // ...
+ admin: {
+ // ...
+ auth: {
+ // ...
+ providers: [
+ {
+ uid: 'okta',
+ displayName: 'Okta',
+ icon:
+ 'https://www.okta.com/sites/default/files/Okta_Logo_BrightBlue_Medium-thumbnail.png',
+ createStrategy: strapi =>
+ new OktaOAuth2Strategy(
+ {
+ clientID: env('OKTA_CLIENT_ID'),
+ clientSecret: env('OKTA_CLIENT_SECRET'),
+ audience: env('OKTA_DOMAIN'),
+ scope: ['openid', 'email', 'profile'],
+ callbackURL: strapi.admin.services.passport.getStrategyCallbackURL('okta'),
+ },
+ (accessToken, refreshToken, profile, done) => {
+ done(null, {
+ email: profile.email,
+ username: profile.username,
+ });
+ }
+ ),
+ },
+ ],
+ },
+ },
+});
+```
+
+:::
+
+## Performing advanced customization
+
+### Admin panel URL
+
+If the administration panel lives on a host/port different from the Strapi server, the admin panel URL needs to be updated:
+update the `url` key in the `./config/admin.js` configuration file (see [admin panel customization documentation](/developer-docs/latest/development/admin-customization.md#access-url)).
+
+### Custom Logic
+
+In some scenarios, you will want to write additional logic for your connection workflow such as:
+
+- restricting connection and registration for a specific domain
+- triggering actions on connection attempt
+- adding analytics
+
+The easiest way to do so is to plug into the verify function of your strategy and write some code.
+
+For example, if you want to allow only people with an official strapi.io email address, you can instantiate your strategy like this:
+
+```javascript
+// path: ./config/admin.js
+
+const strategyInstance = new Strategy(configuration, ({ email, username }, done) => {
+ // If the email ends with @strapi.io
+ if (email.endsWith('@strapi.io')) {
+ // then we continue with the data given by the provider
+ return done(null, { email, username });
+ }
+
+ // Otherwise, we continue by sending an error to the done function
+ done(new Error('Forbidden email address'));
+});
+```
+
+### Authentication Events
+
+The SSO feature adds a new [authentication event](/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md#available-options): `onSSOAutoRegistration`.
+
+This event is triggered whenever a user is created using the auto-register feature added by SSO.
+It contains the created user (`event.user`), and the provider used to make the registration (`event.provider`).
+
+```javascript
+// path: ./config/admin.js
+
+module.exports = () => ({
+ // ...
+ admin: {
+ // ...
+ auth: {
+ // ...
+ events: {
+ onConnectionSuccess(e) {},
+ onConnectionError(e) {},
+ // ...
+ onSSOAutoRegistration(e) {
+ const { user, provider } = e;
+
+ console.log(
+ `A new user (${user.id}) has been automatically registered using ${provider}`
+ );
+ },
+ },
+ },
+ },
+});
+```
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md
new file mode 100644
index 0000000000..441ca07fd4
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md
@@ -0,0 +1,102 @@
+---
+title: Admin panel configuration - Strapi Developer Docs
+description: Strapi's admin panel offers a single entry point file for its configuration.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.html
+---
+
+# Admin panel configuration
+
+The `./config/admin.js` is used to define admin panel configuration for the Strapi application.
+
+## Available options
+
+ The `./config/admin.js` file can include the following parameters:
+
+| Parameter | Description | Type | Default |
+| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `apiToken.salt` | Salt used to generate [API tokens](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md) | String | (A random string
generated
by Strapi) |
+| `auth` | Authentication configuration | Object | - |
+| `auth.secret` | Secret used to encode JWT tokens | string | `undefined` |
+| `auth.events` | Record of all the events subscribers registered for the authentication | object | `{}` |
+| `auth.events.onConnectionSuccess` | Function called when an admin user log in successfully to the administration panel | function | `undefined` |
+| `auth.events.onConnectionError` | Function called when an admin user fails to log in to the administration panel | function | `undefined` |
+| `url` | Url of your admin panel. Default value: `/admin`. Note: If the url is relative, it will be concatenated with `url`. | string | `/admin` |
+| `autoOpen` | Enable or disabled administration opening on start. | boolean | `true` |
+| `watchIgnoreFiles` | Add custom files that should not be watched during development. See more [here](https://github.com/paulmillr/chokidar#path-filtering) (property `ignored`). | Array(string) | `[]` |
+| `host` | Use a different host for the admin panel. Only used along with `strapi develop --watch-admin` | string | `localhost` |
+| `port` | Use a different port for the admin panel. Only used along with `strapi develop --watch-admin` | string | `8000` |
+| `serveAdminPanel` | If false, the admin panel won't be served. Note: the `index.html` will still be served, see [defaultIndex option](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md) | boolean | `true` |
+| `forgotPassword` | Settings to customize the forgot password email (see more here: [Forgot Password Email](/developer-docs/latest/development/admin-customization.md#forgotten-password-email)) | Object | {} |
+| `forgotPassword.emailTemplate` | Email template as defined in [email plugin](/developer-docs/latest/plugins/email.md#programmatic-usage) | Object | [Default template](https://github.com/strapi/strapi/tree/master/packages/strapi-admin/config/email-templates/forgot-password.js) |
+| `forgotPassword.from` | Sender mail address | string | Default value defined in your [provider configuration](/developer-docs/latest/plugins/email.md#configure-the-plugin) |
+| `forgotPassword.replyTo` | Default address or addresses the receiver is asked to reply to | string | Default value defined in your [provider configuration](/developer-docs/latest/plugins/email.md#configure-the-plugin) |
+
+## Configurations
+
+The `./config/admin.js` file should at least include a minimal configuration with required parameters for authentication and [API tokens](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md). Additional parameters can be included for a full configuration.
+
+:::note
+[Environmental configurations](/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md) (i.e. using the `env()` helper) do not need to contain all the values so long as they exist in the default `./config/server.js`.
+:::
+
+:::: tabs card
+::: tab Minimal configuration
+
+The default configuration created with any new project should at least include the following:
+
+```js
+// path: ./config/admin.js
+
+module.exports = ({ env }) => ({
+ apiToken: {
+ salt: env('API_TOKEN_SALT', 'someRandomLongString'),
+ },
+ auth: {
+ secret: env('ADMIN_JWT_SECRET', 'someSecretKey'),
+ },
+})
+
+```
+
+:::
+
+::: tab Full configuration
+
+```js
+// path: ./config/admin.js
+
+module.exports = ({ env }) => ({
+ apiToken: {
+ salt: env('API_TOKEN_SALT', 'someRandomLongString'),
+ },
+ auth: {
+ events: {
+ onConnectionSuccess(e) {
+ console.log(e.user, e.provider);
+ },
+ onConnectionError(e) {
+ console.error(e.error, e.provider);
+ },
+ },
+ secret: env('ADMIN_JWT_SECRET', 'someSecretKey'),
+ },
+ url: env('PUBLIC_ADMIN_URL', '/dashboard'),
+ autoOpen: false,
+ watchIgnoreFiles: [
+ './my-custom-folder', // Folder
+ './scripts/someScript.sh', // File
+ ],
+ host: 'localhost', // Only used for --watch-admin
+ port: 8003, // Only used for --watch-admin
+ serveAdminPanel: env.bool('SERVE_ADMIN', true),
+ forgotPassword: {
+ from: 'no-reply@example.com',
+ replyTo: 'no-reply@example.com',
+ },
+})
+
+```
+
+:::
+::::
+
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md
new file mode 100644
index 0000000000..01c26bf932
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md
@@ -0,0 +1,236 @@
+---
+title: Database configuration - Strapi Developer Docs
+description: Strapi offers a single entry point file to configure its databases.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/required/databases.html
+---
+
+# Database configuration
+
+The `./config/database.js` file is used to define database connections that will be used to store the application content.
+
+:::strapi Supported databases
+The CLI installation guide details [supported database and versions](/developer-docs/latest/setup-deployment-guides/installation/cli.md#preparing-the-installation).
+:::
+
+## Configuration structure
+
+The `./config/database.js` accepts 2 main configuration objects:
+
+- [`connection`](#connection-configuration-object) for database configuration options passed to [Knex.js](https://github.com/knex/knex)
+- [`settings`](#settings-configuration-object) for Strapi-specific database settings
+
+### `connection` configuration object
+
+| Parameter | Description | Type |
+| ------------------------------------------------------------------ | ---------------------------------------------------------------------------- | --------- |
+| `client` | Database client to create the connection. `sqlite` or `postgres` or `mysql`. | `String` |
+| `connection` | Database [connection information](#connection-parameters) | `Object` |
+| `debug` | Show database exchanges and errors. | `Boolean` |
+| `useNullAsDefault`
_Optional, only for SQLite_ | Use `NULL` as a default value | `Boolean` |
+| `pool`
_Optional_ | [Database pooling options](#database-pooling-options) | `Object` |
+
+#### Connection parameters
+
+The `connection.connection` object found in `./config/database.js` is used to pass database connection information and accepts the following parameters:
+
+| Parameter | Description | Type |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------- | --------------------- |
+| `host` | Database host name. Default value: `localhost`. | `String` |
+| `port` | Database port | `Integer` |
+| `database` | Database name. | `String` |
+| `username` | Username used to establish the connection | `String` |
+| `password` | Password used to establish the connection | `String` |
+| `timezone` | Set the default behavior for local time. Default value: `utc` [Timezone options](https://www.php.net/manual/en/timezones.php) | `String` |
+| `schema` | Set the default database schema. **Used only for Postgres DB.** | `String` |
+| `ssl` | For SSL database connection.
Use an object to pass certificate files as strings. | `Boolean` or `Object` |
+
+#### Database pooling options
+
+The `connection.pool` object optionally found in `./config/database.js` is used to pass [Tarn.js](https://github.com/vincit/tarn.js) database pooling options and accepts the following parameters:
+
+| Parameter | Description | Type | Default |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ------- |
+| `min` | Minimum number of database connections to keepalive | `Integer` | `0` |
+| `max` | Maximum number of database connections to keepalive | `Integer` | `10` |
+| `acquireTimeoutMillis` | Time in ms before timing out a database connection attempt | `Integer` | - |
+| `createTimeoutMillis` | Time in ms before timing out a create query attempt | `Integer` | - |
+| `destroyTimeoutMillis` | Time in ms before timing out a destroy query attempt | `Integer` | - |
+| `idleTimeoutMillis` | Time in ms before free database connections are destroyed | `Integer` | - |
+| `reapIntervalMillis` | Time in ms to check for idle database connections to destroy | `Integer` | - |
+| `createRetryIntervalMillis` | Time in ms to idle before retrying failed create actions | `Integer` | - |
+| `afterCreate` | Callback function to execute custom logic when the pool acquires a new connection.
See the [Knex.js documentation](https://knexjs.org/#Installation-pooling) for more information | `Function` | - |
+
+### `settings` configuration object
+
+The `settings` object found in `./config/database.js` is used to configure Strapi-specific database settings and accepts the following parameter:
+
+| Parameter | Description | Type | Default |
+| ---------------- | ------------------------------------------------ | --------- | ------- |
+| `forceMigration` | Enable or disable the forced database migration. | `Boolean` | `true` |
+
+
+
+### Configuration examples
+
+::::: tabs card
+
+:::: tab PostgreSQL
+
+```js
+module.exports = ({ env }) => ({
+ connection: {
+ client: 'postgres',
+ connection: {
+ host: env('DATABASE_HOST', '127.0.0.1'),
+ port: env.int('DATABASE_PORT', 5432),
+ database: env('DATABASE_NAME', 'strapi'),
+ user: env('DATABASE_USERNAME', 'strapi'),
+ password: env('DATABASE_PASSWORD', 'strapi'),
+ schema: env('DATABASE_SCHEMA', 'public'), // Not required
+ ssl: {
+ rejectUnauthorized: env.bool('DATABASE_SSL_SELF', false), // For self-signed certificates
+ },
+ },
+ debug: false,
+ },
+});
+```
+
+:::caution
+Strapi is aware that there is an issue regarding **SSL support for the server**.
+In order to fix it, you have to set the `ssl:{}` object as a boolean in order to disable it. See below for example:
+
+```js
+module.exports = ({ env }) => ({
+ connection: {
+ client: "postgres",
+ connection: {
+ ...
+ ssl: env('DATABASE_SSL', false)
+ },
+ },
+});
+```
+
+:::
+
+Please note that if you need client side SSL CA verification you will need to use the `ssl:{}` object with the fs module to convert your CA certificate to a string. You can see an example below:
+
+```js
+const fs = require('fs');
+
+module.exports = ({ env }) => ({
+ connection: {
+ client: "postgres",
+ connection: {
+ ...
+ ssl: {
+ ca: fs.readFileSync(`${__dirname}/path/to/your/ca-certificate.crt`).toString(),
+ },
+ },
+ },
+});
+```
+
+::::
+
+:::: tab MySQL/MariaDB
+
+```js
+module.exports = ({ env }) => ({
+ connection: {
+ client: 'mysql',
+ connection: {
+ host: env('DATABASE_HOST', '127.0.0.1'),
+ port: env.int('DATABASE_PORT', 5432),
+ database: env('DATABASE_NAME', 'strapi'),
+ user: env('DATABASE_USERNAME', 'strapi'),
+ password: env('DATABASE_PASSWORD', 'strapi'),
+ ssl: {
+ rejectUnauthorized: env.bool('DATABASE_SSL_SELF', false), // For self-signed certificates
+ },
+ },
+ debug: false,
+ },
+});
+```
+
+::::
+
+:::: tab SQLite
+
+```js
+module.exports = ({ env }) => ({
+ connection: {
+ client: 'sqlite',
+ connection: {
+ filename: env('DATABASE_FILENAME', '.tmp/data.db'),
+ },
+ useNullAsDefault: true,
+ debug: false,
+ },
+});
+```
+
+::::
+
+:::::
+
+## Configuration in database
+
+Configuration files are not multi-server friendly. To update configurations in production you can use a data store to get and set settings.
+
+### Get settings
+
+- `environment` (string): Sets the environment you want to store the data in. By default it's current environment (can be an empty string if your configuration is environment agnostic).
+- `type` (string): Sets if your configuration is for an `api`, `plugin` or `core`. By default it's `core`.
+- `name` (string): You have to set the plugin or api name if `type` is `api` or `plugin`.
+- `key` (string, required): The name of the key you want to store.
+
+```js
+// strapi.store(object).get(object);
+
+// create reusable plugin store variable
+const pluginStore = strapi.store({
+ environment: strapi.config.environment,
+ type: 'plugin',
+ name: 'users-permissions',
+});
+
+await pluginStore.get({ key: 'grant' });
+```
+
+### Set settings
+
+- `value` (any, required): The value you want to store.
+
+```js
+// strapi.store(object).set(object);
+
+// create reusable plugin store variable
+const pluginStore = strapi.store({
+ environment: strapi.config.environment,
+ type: 'plugin',
+ name: 'users-permissions'
+});
+
+await pluginStore.set({
+ key: 'grant',
+ value: {
+ ...
+ }
+});
+```
+
+## Databases installation guides
+
+Strapi gives you the option to choose the most appropriate database for your project. It currently supports **PostgreSQL**, **SQLite**, **MySQL** and **MariaDB**.
+
+The following documentation covers how to install SQLite locally (for development purposes):
+
+
+
+
+:::caution
+Installation guides for other databases (MySQL, MariaDB) are being reworked. [Contributions](https://github.com/strapi/documentation/blob/main/CONTRIBUTING.md) are most welcome.
+:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md
new file mode 100644
index 0000000000..ea0da7e353
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md
@@ -0,0 +1,233 @@
+---
+title: Middlewares configuration - Strapi Developer Docs
+description: Strapi offers a single entry point file for its middlewares configurations.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.html
+---
+
+# Middlewares configuration
+
+::: strapi Different types of middlewares
+
+In Strapi, 2 middleware concepts coexist:
+
+- **Strapi middlewares** are configured and enabled as global middlewares for the entire Strapi server application. The present documentation describes how to configure Strapi middlewares.
Strapi also offers the ability to implement your own custom middlewares (see [middlewares customization documentation](/developer-docs/latest/development/backend-customization/middlewares.md)).
+
+- **Route middlewares** have a more limited scope and are configured and used as middlewares at the route level. They are described in the [route middlewares documentation](/developer-docs/latest/development/backend-customization/routes.md#middlewares).
+
+:::
+
+The `./config/middlewares.js` file is used to define all the Strapi middlewares that should be applied by the Strapi server.
+
+Only the middlewares present in `./config/middlewares.js` are applied. Loading middlewares happens in a specific [loading order](#loading-order), with some [naming conventions](#naming-conventions) and an [optional configuration](#optional-configuration) for each middleware.
+
+Strapi prepopulates the `./config/middlewares.js` file with built-in, internal middlewares that all have their own [configuration options](#internal-middlewares-configuration-reference).
+
+## Loading order
+
+The `./config/middlewares.js` file exports an array, where order matters and controls the execution order of the middleware stack:
+
+```js
+// path: ./config/middlewares.js
+
+module.exports = [
+ // The array is pre-populated with internal, built-in middlewares, prefixed by `strapi::`
+ 'strapi::cors',
+ 'strapi::body',
+ 'strapi::errors',
+ // ...
+ 'my-custom-node-module', // custom middleware that does not require any configuration
+ {
+ // custom resolve to find a package or a path
+ resolve: 'my-custom-node-module',
+ config: {
+ foo: 'bar',
+ },
+ },
+ {
+ // custom resolve to find a package or a path
+ resolve: '../some-dir/custom-middleware',
+ config: {
+ foo: 'bar',
+ },
+ },
+];
+```
+
+:::tip
+If you aren't sure where to place a middleware in the stack, add it to the end of the list.
+:::
+
+## Naming conventions
+
+Strapi middlewares can be classified into different types depending on their origin, which defines the following naming conventions:
+
+
+
+| Middleware type | Origin | Naming convention |
+| --------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| Internal | Built-in middlewares (i.e. included with Strapi), automatically loaded | `strapi::middleware-name` |
+| Application-level | Loaded from the `./src/middlewares` folder | `global::middleware-name` |
+| API-level | Loaded from the `./src/api/[api-name]/middlewares` folder | `api::api-name.middleware-name` |
+| Plugin | Exported from `strapi-server.js` in the [`middlewares` property of the plugin interface](/developer-docs/latest/developer-resources/plugin-api-reference/server.md#middlewares) | `plugin::plugin-name.middleware-name` |
+| External | Can be:- either node modules installed with [npm](https://www.npmjs.com/search?q=strapi-middleware)
- or local middlewares (i.e. custom middlewares created locally and configured in `./config/middlewares.js`.)
| -
As they are directly configured and resolved from the configuration file, they have no naming convention. |
+
+## Optional configuration
+
+Middlewares can have an optional configuration with the following parameters:
+
+| Parameter | Description | Type |
+| --------- | ----------------------------------------------------------------- | ------- |
+| `config` | Used to define or override the middleware configuration | Object |
+| `resolve` | Path to the middleware's folder (useful for external middlewares) | String |
+
+## Internal middlewares configuration reference
+
+Strapi's core includes the following internal middlewares, mostly used for performances, security and error handling:
+
+- [body](#body),
+- [compression](#compression),
+- [cors](#cors),
+- [errors](#errors),
+- [favicon](#favicon),
+- [ip](#ip),
+- [logger](#logger),
+- [poweredBy](#poweredby),
+- [query](#query),
+- [response-time](#response-time),
+- responses, which handle the [responses](/developer-docs/latest/development/backend-customization/requests-responses.md),
+- [security](#security),
+- [public](#public),
+
+::: caution
+The following built-in middlewares are automatically added by Strapi: `errors`, `security`, `cors`, `query`', `body`, `public`, `favicon`. They should not be removed as it will throw an error.
+:::
+
+### `body`
+
+The `body` middleware is based on [koa-body](https://github.com/koajs/koa-body) and uses these sensible defaults:
+
+| Option | Description | Type | Default |
+| ----------- | ----------------------------------------- | --------- | ------- |
+| `multipart` | Parse multipart bodies | `Boolean` | `true` |
+| `patchKoa` | Patch request body to Koa's `ctx.request` | `Boolean` | `true` |
+
+For a full list of available options, check the [koa-body documentation](https://github.com/koajs/koa-body#options).
+
+### `compression`
+
+The `compression` middleware is based on [koa-compress](https://github.com/koajs/compress) and offers the same [options](https://github.com/koajs/compress#options).
+
+### `cors`
+
+This security middleware is about cross-origin resource sharing (CORS) and is based on [@koa/cors](https://github.com/koajs/cors). It accepts the following options:
+
+
+| Option | Type | Description | Default value |
+| ---------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- |
+| `origin` | Allowed URLs.
The value(s) can be:- strings (e.g. `http://example1.com, http://example2.com`)
- an array of strings (e.g. `['http://www.example1.com', 'http://example1.com']`)
- or `*` to allow all URLs
| `String or Array` | `*` |
+| `maxAge` | Configure the `Access-Control-Max-Age` CORS header parameter, in seconds | `String or Number` | `31536000` | |
+| `credentials` | Configure the `Access-Control-Allow-Credentials` CORS header | `Boolean` | `true` |
+| `methods` | Configure the `Access-Control-Allow-Methods` CORS header | `Array` or `String` | `['GET', 'POST', 'PUT', 'PATCH', 'DELETE', 'HEAD', 'OPTIONS']` |
+| `headers` | Configure the `Access-Control-Allow-Headers` CORS header
If not specified, defaults to reflecting the headers specified in the request's `Access-Control-Request-Headers` header | `Array` or `String` | `['Content-Type', 'Authorization', 'Origin', 'Accept']` |
+| `keepHeaderOnError` | Add set headers to `err.header` if an error is thrown | `Boolean` | `false` | |
+
+### `errors`
+
+The errors middleware handles [errors](/developer-docs/latest/developer-resources/error-handling.md) thrown by the code. Based on the type of error it sets the appropriate HTTP status to the response. By default, any error not supposed to be exposed to the end-user will result in a 500 HTTP response.
+
+The middleware doesn't have any configuration option.
+
+### `favicon`
+
+The `favicon` middleware is used to serve the favicon. It's based on [koa-favicon](https://github.com/koajs/favicon) and has these sensible defaults:
+
+| Option | Description | Type | Default value |
+| -------- | ------------------------------------------------ | ------- | ------------- |
+| `path` | Path to the favicon file | String | `favicon.ico` |
+| `maxAge` | Cache-control max-age directive, in milliseconds | Integer | `86400000` |
+
+#### `ip`
+
+The `ip` middleware is an IP filter middleware based on [koa-ip](https://github.com/nswbmw/koa-ip) and accepts the following options:
+
+| Option | Description | Type | Default value |
+| ----------- | --------------- | ----- | ------------- |
+| `whitelist` | Whitelisted IPs | Array | `[]` |
+| `blacklist` | Blacklisted IPs | Array | `[]` |
+
+### `logger`
+
+The `logger` middleware is used to log requests.
+
+| Option | Description | Type | Default value |
+| --------- | -------------------- | ------- | ------------- |
+| `enabled` | Enable requests logs | Boolean | `false` |
+
+To define a custom configuration for the `logger` middleware, create a dedicated configuration file (`./config/logger.js`). It should export an object that must be a complete or partial [winstonjs](https://github.com/winstonjs/winston) logger configuration. The object will be merged with Strapi's default logger configuration on server start.
+
+::: details Example: Custom configuration for the logger middleware
+
+```js
+'use strict';
+
+const {
+ winston,
+ formats: { prettyPrint, levelFilter },
+} = require('@strapi/logger');
+
+module.exports = {
+ transports: [
+ new winston.transports.Console({
+ level: 'http',
+ format: winston.format.combine(
+ levelFilter('http'),
+ prettyPrint({ timestamps: 'YYYY-MM-DD hh:mm:ss.SSS' })
+ ),
+ }),
+ ],
+};
+```
+:::
+
+### `poweredBy`
+
+The `poweredBy` middleware adds a `X-Powered-By` parameter to the response header, with a default value of `Strapi `.
+
+### `query`
+
+The `query` middleware is a query parser based on [qs](https://github.com/ljharb/qs) and has the following sensible defaults:
+
+| Option | Description | Type | Default value |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------- | ------------- |
+| `strictNullHandling` | Distinguish between null values and empty strings (see [qs documentation](https://github.com/ljharb/qs#handling-of-null-values)) | Boolean | `true` |
+| `arrayLimit` | Maximum index limit when parsing arrays (see [qs documentation](https://github.com/ljharb/qs#parsing-arrays)) | Number | 100 |
+| `depth` | Maximum depth of nested objects when parsing objects (see [qs documentation](https://github.com/ljharb/qs#parsing-objects)) | Number | 20 |
+
+### `response-time`
+
+The `response-time` middleware enables the `X-Response-Time` (in milliseconds) for the response header.
+
+### `public`
+
+The `public` middleware is a static file serving middleware, based on [koa-static](https://github.com/koajs/static). It accepts the following options:
+
+| Option | Description | Type | Default value |
+| -------------- | --------------------------------------------------- | ------- | ------------- |
+| `path` | Path to the public folder | String | `./public` |
+| `maxAge` | Cache-control max-age directive, in milliseconds | Integer | `60000` |
+| `defaultIndex` | Display default index page at `/` and `/index.html` | Boolean | `true` |
+
+### `security`
+
+The security middleware is based on [koa-helmet](https://helmetjs.github.io/) and has the following sensible defaults:
+
+| Option | Description | Type | Default value |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | ---------------------------------------------------- |
+| `crossOriginEmbedderPolicy` | Set the `Cross-Origin-Embedder-Policy` header to `require-corp` | `Boolean` | `false` |
+| `crossOriginOpenerPolicy` | Set the `Cross-Origin-Opener-Policy` header | `Boolean` | `false` |
+| `crossOriginOpenerPolicy` | Set the `Cross-Origin-Resource-Policy` header | `Boolean` | `false` |
+| `originAgentCluster` | Set the `Origin-Agent-Cluster` header | `Boolean` | `false` |
+| `contentSecurityPolicy` | Set the `Content-Security-Policy` header | `Boolean` | `false` |
+| `xssFilter` | Disable browsers' cross-site scripting filter by setting the `X-XSS-Protection` header to `0` | `false` | |
+| `hsts` | Set options for the HTTP Strict Transport Security (HSTS) policy.
Accepts the following parameters:- `maxAge`: Number of seconds HSTS is in effect
- `includeSubDomains`: Applies HSTS to all subdomains of the host
| - `maxAge`: `Integer`
- `includeSubDomains`: `Boolean`
| - `maxAge`: `31536000`
- `includeSubDomains`: `true`
|
+| `frameguard` | Set `X-Frame-Options` header to help mitigate clickjacking attacks
Accepts the `action` parameter that specifies which directive to use. | `String` | `sameorigin` |
diff --git a/docs/developer-docs/latest/setup-deployment-guides/configurations/required/server.md b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/server.md
new file mode 100644
index 0000000000..7d5ba9e87e
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/configurations/required/server.md
@@ -0,0 +1,76 @@
+---
+title: Server configuration - Strapi Developer Docs
+description: Strapi offers a single entry point file for its server configuration.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/required/server.html
+---
+
+# Server configuration
+
+The `./config/server.js` is used to define server configuration for the Strapi application.
+
+## Available options
+
+The `./config/server.js` file can include the following parameters:
+
+
+
+| Parameter | Description | Type | Default |
+| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `host`
❗️ _Mandatory_ | Host name | string | `localhost` |
+| `port`
❗️ _Mandatory_ | Port on which the server should be running. | integer | `1337` |
+| `socket` | Listens on a socket. Host and port are cosmetic when this option is provided and likewise use `url` to generate proper urls when using this option. This option is useful for running a server without exposing a port and using proxy servers on the same machine (e.g [Heroku nginx buildpack](https://github.com/heroku/heroku-buildpack-nginx#requirements-proxy-mode)) | string \| integer | `/tmp/nginx.socket` |
+| `emitErrors` | Enable errors to be emitted to `koa` when they happen in order to attach custom logic or use error reporting services. | boolean | `false` |
+| `url` | Public url of the server. Required for many different features (ex: reset password, third login providers etc.). Also enables proxy support such as Apache or Nginx, example: `https://mywebsite.com/api`. The url can be relative, if so, it is used with `http://${host}:${port}` as the base url. An absolute url is however recommended. | string | `''` |
+| `proxy` | Set the koa variable `app.proxy`. When `true`, proxy header fields will be trusted. | boolean | `false` |
+| `cron` | Cron configuration (powered by [`node-schedule`](https://github.com/node-schedule/node-schedule)) | Object | |
+| `cron.enabled` | Enable or disable [CRON jobs](/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md) to schedule jobs at specific dates. | boolean | `false` |
+| `cron.tasks` | Declare [CRON jobs](/developer-docs/latest/setup-deployment-guides/configurations/optional/cronjobs.md) to be run at specific dates. | boolean | `false` |
+
+## Configurations
+
+The `./config/server.js` file should at least include a minimal configuration with the `host` and `port` parameters. Additional parameters can be included for a full configuration.
+
+:::note
+[Environmental configurations](/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md) (i.e. using the `env()` helper) do not need to contain all the values so long as they exist in the default `./config/server.js`.
+:::
+
+::::: tabs card
+
+:::: tab Minimal configuration
+
+The default configuration created with any new project should at least include the following:
+
+```js
+// path: ./config/server.js
+
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+});
+```
+
+::::
+
+:::: tab Full configuration
+
+The following is an example of a full configuration file. Not all of these keys are required (see [available options](#available-options)).
+
+```js
+// path: ./config/server.js
+
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+ socket: '/tmp/nginx.socket', // only use if absolutely required
+ emitErrors: false,
+ url: env('PUBLIC_URL', 'https://api.example.com'),
+ proxy: env.bool('IS_PROXIED', true),
+ cron: {
+ enabled: env.bool('CRON_ENABLED', false),
+ },
+});
+```
+
+::::
+
+:::::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment.md b/docs/developer-docs/latest/setup-deployment-guides/deployment.md
index 415418903d..b6614a60e0 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment.md
@@ -1,42 +1,20 @@
---
-title: Deployment - Strapi Developer Documentation
+title: Deployment - Strapi Developer Docs
description: Learn how to develop locally with Strapi and deploy Strapi with various hosting options.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment.html
---
-
# Deployment
Strapi gives you many possible deployment options for your project or application. Strapi can be deployed on traditional hosting servers or services such as 21YunBox, Render, Heroku, AWS, Azure and others. The following documentation covers how to develop locally with Strapi and deploy Strapi with various hosting options.
-::: tip
-Deploying **databases** along with Strapi is covered in the [Databases Guide](/developer-docs/latest/setup-deployment-guides/configurations.md#databases-installation-guides).
+::: strapi Database deployment
+Deploying databases along with Strapi is covered in the [databases guide](/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md#databases-installation-guides).
:::
## General guidelines
-::: danger PREREQUISITES
+::: prerequisites
To provide the best possible environment for Strapi there are a few requirements, these apply in both a development (local) as well as a staging and production workflow.
- Node LTS (v12 or V14) **Note that odd-number releases of Node will never be supported (e.g. v13, v15).**
@@ -50,7 +28,6 @@ To provide the best possible environment for Strapi there are a few requirements
- MariaDB >= 10.1
- PostgreSQL >= 10
- SQLite >= 3
- - MongoDB >= 3.6
- A supported operating system
- Ubuntu >= 18.04 (LTS-Only)
- Debian >= 9.x
@@ -84,14 +61,14 @@ NODE_PORT=1338
```
::: tip
-To learn more about configuration you can read the documentation [here](/developer-docs/latest/setup-deployment-guides/configurations.md)
+To learn more about configuration details, you can read the [configurations](/developer-docs/latest/setup-deployment-guides/configurations.md) documentation.
:::
#### 2. Launch the server
Before running your server in production you need to build your admin panel for production
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -118,7 +95,13 @@ npm install cross-env
Then in your `package.json` scripts section:
```bash
-"production": "cross-env NODE_ENV=production npm run build"
+"build:win": "cross-env NODE_ENV=production npm run build",
+```
+
+And run:
+
+```bash
+npm run build:win
```
:::
@@ -127,7 +110,7 @@ Then in your `package.json` scripts section:
Run the server with the `production` settings.
-:::: tabs
+:::: tabs card
::: tab yarn
@@ -154,14 +137,20 @@ npm install cross-env
Then in your `package.json` scripts section:
```bash
-"production": "cross-env NODE_ENV=production npm start"
+"start:win": "cross-env NODE_ENV=production npm start",
+```
+
+And run:
+
+```bash
+npm run start:win
```
:::
::::
-::: warning
+::: caution
We highly recommend using [pm2](https://github.com/Unitech/pm2/) to manage your process.
:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/21yunbox.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/21yunbox.md
index 990ce23d99..6719e9a2ec 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/21yunbox.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/21yunbox.md
@@ -1,34 +1,13 @@
---
-title: 21YunBox Deployment - Strapi Developer Documentation
+title: 21YunBox Deployment - Strapi Developer Docs
description: Learn in this guide how to update an existing Strapi project so it can be deployed on 21YunBox.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/21yunbox.html
---
-
-
# 21YunBox
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This guide explains how to update an existing Strapi project so it can be deployed on [21YunBox](https://www.21yunbox.com).
21YunBox provides a Chinese CDN, continuous deployment, one-click HTTPS and [other services such as managed databases and backend web services](https://www.21yunbox.com/docs/#/), allowing to launch web projects in China.
@@ -36,10 +15,10 @@ This guide explains how to update an existing Strapi project so it can be deploy
With persistent disks and managed PostgreSQL databases, 21YunBox gives you multiple different ways to store your content. 21YunBox services come with fully managed SSL, so it's no longer necessary to set up a proxy server to secure your Strapi app. Since 21YunBox services are automatically restarted if they become unresponsive, you don't need to use a process manager like `pm2` either.
::: tip
-For more information consult [21YunBox's Deploy Strapi guide](https://www.21yunbox.com/docs/#/deploy-strapi)
+For more information consult [21YunBox's Deploy Strapi guide](https://www.21yunbox.com/docs/#/deploy-strapi).
:::
-:::danger PREREQUISITES
+:::prerequisites
This guide assumes you already have a Strapi project to deploy. If you need a project, use the [Quick Start](/developer-docs/latest/getting-started/quick-start.md) to get started or fork 21YunBox's Strapi Examples:
- [Strapi with SQLite Starter](https://gitee.com/eryiyunbox-examples/hello-strapi-sqlite)
@@ -89,7 +68,3 @@ Now that 21YunBox is connected to your repo, it will automatically build and pub
## Custom domains
Add your own domains to your site easily using 21YunBox's [custom domains](https://www.21yunbox.com/docs/#/custom-domains) guide.
-
-::: tip NOTE
-If you need customized deployment with Strapi, please contact [21YunBox](https://www.21yunbox.com/docs/#/contact).
-:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/amazon-aws.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/amazon-aws.md
index 3e96678b58..2f2d72538b 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/amazon-aws.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/amazon-aws.md
@@ -1,10 +1,13 @@
---
-title: AWS Deployment - Strapi Developer Documentation
+title: AWS Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on AWS EC2, host your database on AWS RDS and upload your assets on AWS S3.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/amazon-aws.html
---
# Amazon AWS
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This is a step-by-step guide for deploying a Strapi project to [Amazon AWS EC2](https://aws.amazon.com/ec2/). This guide will connect to an [Amazon AWS RDS](https://aws.amazon.com/rds/) for managing and hosting the database. Optionally, this guide will show you how to connect host and serve images on [Amazon AWS S3](https://aws.amazon.com/s3/).
Prior to starting this guide, you should have created a [Strapi project](/developer-docs/latest/getting-started/quick-start.md), to use for deploying on AWS. And have read through the [configuration](/developer-docs/latest/setup-deployment-guides/deployment.md#application-configuration) section.
@@ -72,7 +75,7 @@ Amazon calls a virtual private server, a **virtual server** or **Amazon EC2 inst
In the top menu, near your IAM Account User name, select, from the dropdown, the most appropriate region to host your Strapi project. For example, `US East (N.Virginia)` or `Asia Pacific (Hong Kong)`. You will want to remember this region for configuring other services on AWS and serving these services from the same region.
-#### 3. Click on the blue `Launch Instance` button
+#### 3. Click on the orange `Launch Instance` button
- `Select` **Ubuntu Server 18.04 LTS (HVM), SSD Volume Type**
- Ensure `General purpose` + `t2.small` is `checked`.
@@ -100,7 +103,7 @@ In the top menu, near your IAM Account User name, select, from the dropdown, the
- Review the details, in the **Step 7: Review Instance Launch**, then click the blue `Launch` button. Now, you need to **select an existing key pair** or **create a new key pair**. To create a new key pair, do the following:
- Select the dropdown option `Create a new key pair`.
- Name your the key pair name, e.g. `ec2-strapi-key-pair`
- ::: warning
+ ::: caution
Download the **private key file** (.pem file). This file is needed, so note where it was downloaded.
:::
- After downloading the file, click the blue `Launch Instances` button.
@@ -109,7 +112,7 @@ Your instance is now running. Continue to the next steps.
### Install a PostgreSQL database on AWS RDS
-Amazon calls their database hosting services **RDS**. Multiple database options exist and are available. In this guide, **PostgreSQL** is used as the example, and the steps are similar for each of the other database that are supported by Strapi. (**MySQL**, **MongoDB**, **PostgreSQL**, **MariaDB**, **SQLite**). You will set-up an **RDS instance** to host your `postgresql` database.
+Amazon calls their database hosting services **RDS**. Multiple database options exist and are available. In this guide, **PostgreSQL** is used as the example, and the steps are similar for each of the other database that are supported by Strapi. (**MySQL**, **PostgreSQL**, **MariaDB**, **SQLite**). You will set-up an **RDS instance** to host your `postgresql` database.
::: tip
**Amazon RDS** does **NOT** have a completely free evaluation tier. After finishing this guide, if you are only testing, please remember to [delete the database](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DeleteInstance.html). Otherwise, you will incur charges.
@@ -354,7 +357,7 @@ module.exports = ({ env }) => ({
});
```
-Checkout the documentation about using an upload provider [here](/developer-docs/latest/development/plugins/upload.md#using-a-provider).
+Checkout the documentation about using an upload provider [here](/developer-docs/latest/plugins/upload.md#using-a-provider).
#### 4. Push your local changes to your project's GitHub repository.
@@ -628,8 +631,8 @@ sudo nano /etc/systemd/system/webhook.service
- In the `nano` editor, copy/paste the following script, but make sure to replace `ubuntu` **in two places** if you changed the default `ubuntu` user, and `paste the $PATH` from above.
-::: warning
-**DELETE THE #COMMENTS BEFORE SAVING**, then save and exit.
+:::caution
+Delete the #comments before saving, then save and exit.
:::
```bash
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/azure.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/azure.md
index f5ccc9bc5d..60110308de 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/azure.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/azure.md
@@ -1,10 +1,13 @@
---
-title: Azure Deployment - Strapi Developer Documentation
+title: Azure Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on Microsoft Azure.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/azure.html
---
# Azure
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This is a step-by-step guide for deploying a Strapi project to [Azure](https://azure.microsoft.com/en-us/). Databases can be on a [Azure Virtual Machine](https://azure.microsoft.com/en-us/services/virtual-machines/), hosted externally as a service, or via the [Azure Managed Databases](https://azure.microsoft.com/en-us/services/postgresql/). Prior to starting this guide, you should have created a [Strapi project](/developer-docs/latest/getting-started/quick-start.md). And have read through the [configuration](/developer-docs/latest/setup-deployment-guides/deployment.md#application-configuration) section.
### Azure Install Requirements
@@ -185,14 +188,12 @@ Strapi will need a database in order to save data to, you have multiple options
For Azure managed databases you can use the following:
-- Azure Cosmos DB (Not officially supported, but has an option for MongoDB based API)
- Azure Database for MySQL
- Azure Database for PostgreSQL
- Azure Database for MariaDB
Likewise you can use any of the following installed locally on the virtual machine:
-- MongoDB >= 3.6
- MySQL >= 5.6
- MariaDB >= 10.1
- PostgreSQL >= 10
@@ -467,4 +468,4 @@ There are many different types of proxy services you could use, anything from lo
#### 3. File upload providers
-There are many options for storing files outside of your virtual machine, Strapi have built a few and the community is constantly building new ones. See the [following guide](/developer-docs/latest/development/plugins/upload.md#create-providers) on searching for options as well as installing them.
+There are many options for storing files outside of your virtual machine, Strapi have built a few and the community is constantly building new ones. See the [following guide](/developer-docs/latest/plugins/upload.md#create-providers) on searching for options as well as installing them.
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean-app-platform.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean-app-platform.md
index 6f5f3fcbf0..2511c79b08 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean-app-platform.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean-app-platform.md
@@ -1,15 +1,14 @@
---
-title: DigitalOcean App Platform Deployment - Strapi Developer Documentation
+title: DigitalOcean App Platform Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on DigitalOcean App Platform.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean-app-platform.html
---
# DigitalOcean App Platform
-This is a step-by-step guide for deploying a Strapi project to [DigitalOcean's App Platform](https://digitalocean.com). App Platform is DigitalOcean's Platform as a Service (PaaS) that will handle deploying, networking, SSL, and more for your app. It is the easiest way to deploy Strapi to DigitalOcean.
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
-::: warning
-Please note that as of June 18th, 2021 we were made aware that there is a critical security issue when using DigitalOcean Managed databases with the DigitalOcean App platform. We do not currently recommend using this combination and if you require a managed database, you should use a DigitalOcean Droplet instead. More information can be found on the DigitalOcean [forum thread](https://www.digitalocean.com/community/questions/how-to-add-my-digitalocean-app-as-a-trusted-resource-for-my-managed-database) and [feature request](https://ideas.digitalocean.com/app-framework-services/p/allow-managed-databases-trusted-sources-to-be-used-with-app-platform) pages.
-:::
+This is a step-by-step guide for deploying a Strapi project to [DigitalOcean's App Platform](https://digitalocean.com). App Platform is DigitalOcean's Platform as a Service (PaaS) that will handle deploying, networking, SSL, and more for your app. It is the easiest way to deploy Strapi to DigitalOcean.
Databases can be created using DigitalOcean's [Managed Databases](https://www.digitalocean.com/products/managed-databases/).
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean.md
index dedb1d12cf..e1027760ff 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean.md
@@ -1,10 +1,13 @@
---
-title: DigitalOcean Droplet Deployment - Strapi Developer Documentation
+title: DigitalOcean Droplet Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on DigitalOcean Droplets.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean.html
---
# DigitalOcean Droplets
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This is a step-by-step guide for deploying a Strapi project to [DigitalOcean](https://www.digitalocean.com/) Droplet. If you want to deploy your Strapi project from GitHub, you can deploy to DigitalOcean's Platform as a Service (PaaS) called [App Platform](/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/digitalocean-app-platform.md).
Databases can be on a [DigitalOcean Droplet](https://www.digitalocean.com/docs/droplets/) or hosted externally as a service using [DigitalOcean Managed Databases](https://www.digitalocean.com/products/managed-databases/).
@@ -118,7 +121,7 @@ git --version
#### 2. **OPTIONAL:** Install Git.
-::: tip NOTE
+:::note
Only do this step if _not installed_, as above. Please follow these directions on [how to install Git on Ubuntu 18.04](https://www.digitalocean.com/community/tutorials/how-to-install-git-on-ubuntu-18-04).
:::
@@ -130,7 +133,7 @@ After installing and configuring Git on your Droplet. Please continue to the nex
DigitalOcean has excellent documentation regarding the installation and use of the major databases that work with Strapi. The previous steps above should all be completed prior to continuing. You can find links, and any further instructions, below:
-:::: tabs
+:::: tabs card
::: tab PostgreSQL
@@ -153,7 +156,7 @@ postgres=# \q
exit
```
-- **OPTIONAL:** If in **Development**, your Strapi project is uses **SQLite**, you will need to install a dependency package called `pg`:
+- **OPTIONAL:** If in **Development**, your Strapi project uses **SQLite**, you will need to install a dependency package called `pg`:
- On your **Development** computer:
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/google-app-engine.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/google-app-engine.md
index f9a5630f71..53924d2b63 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/google-app-engine.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/google-app-engine.md
@@ -1,10 +1,13 @@
---
-title: Google App Engine Deployment - Strapi Developer Documentation
+title: Google App Engine Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on Google App Engine and how to upload your assets on Google Cloud Storage.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/google-app-engine.html
---
# Google App Engine
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
In this guide we are going to:
- Create a new Strapi project
@@ -14,29 +17,21 @@ In this guide we are going to:
### New Strapi project
-:::: tabs
-
-::: tab yarn
+
-Use **yarn** to install the Strapi project (**recommended**). [Install yarn with these docs](https://yarnpkg.com/lang/en/docs/install/)
-
-```bash
-yarn create strapi-app my-project --quickstart
+
+```sh
+npx create-strapi-app@latest my-project --quickstart
```
+
-:::
-
-::: tab npx
-
-Use **npm/npx** to install the Strapi project
-
-```bash
-npx create-strapi-app my-project --quickstart
+
+```sh
+yarn create strapi-app my-project --quickstart
```
+
-:::
-
-::::
+
When the setup completes, register an admin user using the form which opens in the browser. This user will be only relevant in local development.
@@ -106,12 +101,12 @@ The `myapi-123456` part is the project identifier. (The number is automatically
The following is an example config for `Standard Environment` or `Flexible Environment`.
-:::: tabs
+:::: tabs card
::: tab Standard Environment
```yaml
-runtime: nodejs10
+runtime: nodejs14
instance_class: F2
@@ -177,7 +172,7 @@ yarn add pg
[Google App Engine requires](https://cloud.google.com/sql/docs/postgres/connect-app-engine) to connect to the database using the unix socket path, not an IP and port.
-Edit `database.js`, and use the socket path as `host`.
+Edit `database.js`, and use the socket path as `socketPath`.
`Path: ./config/env/production/database.js`.
@@ -189,7 +184,7 @@ module.exports = ({ env }) => ({
connector: 'bookshelf',
settings: {
client: 'postgres',
- host: `/cloudsql/${env('INSTANCE_CONNECTION_NAME')}`,
+ socketPath: `/cloudsql/${env('INSTANCE_CONNECTION_NAME')}`,
database: env('DATABASE_NAME'),
username: env('DATABASE_USERNAME'),
password: env('DATABASE_PASSWORD'),
@@ -250,7 +245,7 @@ Follow the [documentation of the plugin](https://github.com/Lith/strapi-provider
CORS is enabled by default, allowing `*` origin. You may want to limit the allowed origins.
-Read the documentation [here](/developer-docs/latest/setup-deployment-guides/configurations.md#middlewares).
+Read the documentation [here](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md).
**Changing the admin url**
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.md
index b9df424f7d..12ae138787 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.md
@@ -1,10 +1,13 @@
---
-title: Heroku Deployment - Strapi Developer Documentation
+title: Heroku Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on Heroku.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.html
---
# Heroku
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This is a step-by-step guide for deploying a Strapi project on [Heroku](https://www.heroku.com/). Databases that work well with Strapi and Heroku are provided instructions on how to get started.
### Heroku Install Requirements
@@ -18,7 +21,7 @@ If you already have the Heroku CLI installed locally on your computer. Skip to [
Download and install the `Heroku CLI` for your operating system:
-:::: tabs
+:::: tabs card
::: tab Ubuntu
Run the following from your terminal:
@@ -63,37 +66,23 @@ Follow the instructions and return to your command line.
Create a [new Strapi project](/developer-docs/latest/getting-started/quick-start.md) (if you want to deploy an existing project go to step 4).
-::: tip NOTE
-
-If you plan to use **MongoDB** with your project, [refer to the create a Strapi project with MongoDB section of the documentation](/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md#install-mongodb-locally) then, jump to step 4.
-
-:::
-
`Path: ./`
-:::: tabs
-
-::: tab yarn
-
-Use **yarn** to install the Strapi project (**recommended**). [Install yarn with these docs](https://yarnpkg.com/lang/en/docs/install/)
+
-```bash
-yarn create strapi-app my-project --quickstart
+
+```sh
+npx create-strapi-app@latest my-project --quickstart
```
+
-:::
-
-::: tab npx
-
-Use **npm/npx** to install the Strapi project
-
-```bash
-npx create-strapi-app my-project --quickstart
+
+```sh
+yarn create strapi-app my-project --quickstart
```
+
-:::
-
-::::
+
::: tip
When you use `--quickstart` to create a Strapi project locally, a **SQLite database** is used which is not compatible with Heroku. Therefore, another database option [must be chosen](#_7-heroku-database-set-up).
@@ -136,8 +125,8 @@ heroku create
You can use `heroku create custom-project-name`, to have Heroku create a `custom-project-name.heroku.com` URL. Otherwise, Heroku will automatically generate a random project name (and URL) for you.
-::: tip NOTE
-If you have a Heroku project app already created. You would use the following step to initialize your local project folder:
+:::tip
+If you have a Heroku project app already created, you would use the following step to initialize your local project folder:
`Path: ./my-project/`
@@ -151,11 +140,11 @@ Your local development environment is now set-up and configured to work with Her
#### 7. Heroku Database set-up
-Below you will find database options when working with Heroku. Please choose the correct database (e.g. PostgreSQL, MongoDB, etc.) and follow those instructions.
+Below you will find database options when working with Heroku. Please choose the correct database (e.g. PostgreSQL) and follow those instructions.
-:::: tabs
+:::::: tabs card
-::: tab PostgreSQL
+::::: tab PostgreSQL
### Heroku Postgres
@@ -191,21 +180,25 @@ Strapi expects a variable for each database connection configuration (host, user
Install the package:
-With npm:
+
-```bash
+
+```sh
npm install pg-connection-string --save
```
+
-With yarn:
-
-```bash
+
+```sh
yarn add pg-connection-string
```
+
+
+
#### 4. Create your Heroku database config file for production
-Create new subfolders in `./config` like so: `/env/production`, then create a new `database.js` in it (see [environment documentation](/developer-docs/latest/setup-deployment-guides/configurations.md#environment)). Your path should look like this: `./config/env/production/database.js`. When you run locally you should be using the `./config/database.js` which could be set to use SQLite, however it's recommended you use PostgreSQL locally also, for information on configuring your local database, please see the [database documentation](/developer-docs/latest/setup-deployment-guides/configurations.md#database).
+Create new subfolders in `./config` like so: `/env/production`, then create a new `database.js` in it (see [environment documentation](http://localhost:8080/documentation/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md)). Your path should look like this: `./config/env/production/database.js`. When you run locally you should be using the `./config/database.js` which could be set to use SQLite, however it's recommended you use PostgreSQL locally also, for information on configuring your local database, please see the [database documentation](/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md).
`Path: ./config/env/production/database.js`
@@ -245,7 +238,7 @@ heroku config:set NODE_ENV=production
#### 5. Create your Strapi server config for production
-Create a new `server.js` in a new [env](/developer-docs/latest/setup-deployment-guides/configurations.md#environment) folder. In this file you only need one key, the `url`, to notify Strapi what our public Heroku domain is. All other settings will automatically be pulled from the default `./config/server.js`.
+Create a new `server.js` in a new [env](http://localhost:8080/documentation/developer-docs/latest/setup-deployment-guides/configurations/optional/environment.md) folder. In this file you only need one key, the `url`, to notify Strapi what our public Heroku domain is. All other settings will automatically be pulled from the default `./config/server.js`.
`Path: ./config/env/production/server.js`
@@ -267,137 +260,25 @@ Unless you originally installed Strapi with PostgreSQL, you need to install the
`Path: ./my-project/`
+
-:::: tabs
-::: tab npm
-
-```bash
+
+```sh
npm install pg --save
```
-:::
+
-::: tab yarn
-```bash
+
+```sh
yarn add pg
```
-:::
-::::
-
-:::
-
-::: tab MongoDB
-
-### MongoDB Atlas
-
-(Using Strapi and MongoDB requires different set-up and different configuration steps. You cannot use `--quickstart` to develop a `MongoDB` Strapi project.)
-
-Please follow these steps the **deploy a Strapi app with MongoDB on Heroku**.
-
-You must have completed the [steps to use Strapi with MongoDB Atlas](/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md#install-on-atlas-mongodb-atlas) - through **4. Retrieve database credentials**.
-
-#### 1. Set environment variables
-
-When you [set-up your MongoDB Atlas database](/developer-docs/latest/setup-deployment-guides/configurations/databases/mongodb.md#install-on-atlas-mongodb-atlas) you noted a connection string. Similar to this:
-
-```bash
-mongodb://paulbocuse:@strapidatabase-shard-00-00-fxxx6c.mongodb.net:27017,strapidatabase-shard-00-01-fxxxc.mongodb.net:27017,strapidatabase-shard-00-02-fxxxc.mongodb.net:27017/test?ssl=true&replicaSet=strapidatabase-shard-0&authSource=admin&retryWrites=true&w=majority
-
-```
+
-So, from **MongoDB Atlas**, you have to set two environment variables in the Heroku config (for **DATABASE_URI** and **DATABASE_NAME**). Set the environment variables using the following commands:
+
-```bash
-heroku config:set DATABASE_URI="mongodb://paulbocuse:@strapidatabase-shard-00-00-fxxx6c.mongodb.net:27017,strapidatabase-shard-00-01-fxxxc.mongodb.net:27017,strapidatabase-shard-00-02-fxxxc.mongodb.net:27017/test?ssl=true&replicaSet=strapidatabase-shard-0&authSource=admin&retryWrites=true&w=majority"
-heroku config:set DATABASE_NAME="my-database-name"
-```
-
-Please replace the `` and `my-database-name` values with the your actual values.
-
-#### 2. Update your database config file
+:::::
-`Path: ./config/database.js`.
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {
- uri: env('DATABASE_URI'),
- },
- options: {
- ssl: true,
- },
- },
- },
-});
-```
-
-If you need to configure the connection differently (e.g using `host`,`port`...) you should set the default database config like so:
-
-`Path: ./config/database.js`.
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {},
- options: {},
- },
- },
-});
-```
-
-Then set the development and the production configurations separately:
-
-`Path: ./config/env/development/database.js`.
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {
- host: env('DATABASE_HOST'),
- port: env.int('DATABASE_PORT'),
- database: env('DATABASE_NAME'),
- username: env('DATABASE_USERNAME'),
- password: env('DATABASE_PASSWORD'),
- },
- options: {},
- },
- },
-});
-```
-
-and finally for the `production` env:
-
-`Path: ./config/env/production/database.js`.
-
-```js
-module.exports = ({ env }) => ({
- defaultConnection: 'default',
- connections: {
- default: {
- connector: 'mongoose',
- settings: {
- uri: env('DATABASE_URI'),
- },
- options: {
- ssl: true,
- },
- },
- },
-});
-```
-
-:::
-
-::::
+::::::
#### 8. Commit your changes
@@ -445,8 +326,8 @@ If you see the Strapi Welcome page, you have correctly set-up, configured and de
You can now continue with the [Quick Start Guide](/developer-docs/latest/getting-started/quick-start.md), if you have any questions on how to proceed.
-::: warning
-For security reasons, the Content-Types Builder plugin is disabled in production. To update content structure, please make your changes locally and deploy again.
+::: caution
+For security reasons, the Content-Type Builder plugin is disabled in production. To update content structure, please make your changes locally and deploy again.
:::
### Project updates
@@ -470,15 +351,15 @@ heroku open
Like with project updates on Heroku, the file system doesn't support local uploading of files as they will be wiped when Heroku "Cycles" the dyno. This type of file system is called [ephemeral](https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem), which means the file system only lasts until the dyno is restarted (with Heroku this happens any time you redeploy or during their regular restart which can happen every few hours or every day).
-Due to Heroku's filesystem you will need to use an upload provider such as AWS S3, Cloudinary, or Rackspace. You can view the documentation for installing providers [here](/developer-docs/latest/development/plugins/upload.md#create-providers) and you can see a list of providers from both Strapi and the community on [npmjs.com](https://www.npmjs.com/search?q=strapi-provider-upload-&page=0&perPage=20).
+Due to Heroku's filesystem you will need to use an upload provider such as AWS S3, Cloudinary, or Rackspace. You can view the documentation for installing providers [here](/developer-docs/latest/plugins/upload.md#create-providers) and you can see a list of providers from both Strapi and the community on [npmjs.com](https://www.npmjs.com/search?q=strapi-provider-upload-&page=0&perPage=20).
### Gzip
-As of version `3.2.1`, Strapi uses [`koa-compress`](https://github.com/koajs/compress) v5, which enables [Brotli](https://en.wikipedia.org/wiki/Brotli) compression by default. At the time of writing, the default configuration for Brotli results in poor performance, causing very slow response times and potentially response timeouts. If you plan on enabling the [gzip middleware](/developer-docs/latest/setup-deployment-guides/configurations.md#core-middleware-configurations), it is recommended that you disable Brotli or define better configuration params.
+As of version `3.2.1`, Strapi uses [`koa-compress`](https://github.com/koajs/compress) v5, which enables [Brotli](https://en.wikipedia.org/wiki/Brotli) compression by default. At the time of writing, the default configuration for Brotli results in poor performance, causing very slow response times and potentially response timeouts. If you plan on enabling the [gzip middleware](/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.md#internal-middlewares-configuration-reference), it is recommended that you disable Brotli or define better configuration params.
To disable Brotli, provide the following configuration in `config/middleware.js`.
-```jsonify
+```json
gzip: {
enabled: true,
options: {
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/qovery.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/qovery.md
index 24c21efdd3..ee8e9b8fa7 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/qovery.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/qovery.md
@@ -1,10 +1,13 @@
---
-title: Qovery Deployment - Strapi Developer Documentation
+title: Qovery Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on Qovery.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/qovery.html
---
# Qovery
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This is a step-by-step guide for deploying a Strapi project on [Qovery](https://www.qovery.com).
Qovery is a CaaS for developers to deploy their full-stack applications on AWS, GCP, Azure and Digital Ocean. Qovery provides access to managed PostgreSQL and free SSL.
@@ -21,9 +24,9 @@ Visit [the Qovery dashboard](https://start.qovery.com) to create an account if y
* Click on the **create a project** button and give a name to your project.
* Click on **next**.
- ::: tip NOTE
- One project can have multiple apps running. This is convenient to group your backend, frontend, database etc.
- :::
+::: note
+One project can have multiple apps running. This is convenient to group your backend, frontend, database etc.
+:::
### 3. Add your Strapi app
* Click on the **create an application** button and select your Github or Gitlab repository where your Strapi app is located.
@@ -77,11 +80,11 @@ routers:
- /*
```
-::: tip TIP
+::: tip
For more information about the `.qovery.yml` file, please refer to [the Qovery application documentation](https://docs.qovery.com/docs/using-qovery/configuration/applications).
:::
-::: tip NOTE
+:::note
Alternatively, you can deploy your Strapi application with a PostgreSQL database in the Qovery dashboard.
:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.md
index 9da3fb81c9..a8e3aa2f8a 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.md
@@ -1,16 +1,19 @@
---
-title: Render Deployment - Strapi Developer Documentation
+title: Render Deployment - Strapi Developer Docs
description: Learn in this guide how to deploy your Strapi application on Render.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/render.html
---
# Render
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md)!!!
+
This guide explains how to update an existing Strapi project so it can be deployed on [Render](https://render.com).
With persistent disks and managed PostgreSQL databases, Render gives you multiple different ways to store your content. Render services come with fully managed SSL, so it's no longer necessary to set up a proxy server to secure your Strapi app. Since Render services are automatically restarted if they become unresponsive, you don't need to use a process manager like `pm2` either.
::: tip
-For more information consult [Render's Deploy Strapi guide](https://render.com/docs/deploy-strapi)
+For more information consult [Render's Deploy Strapi guide](https://render.com/docs/deploy-strapi).
:::
### Step 1: Create a Render Account
@@ -31,7 +34,7 @@ Below are descriptions of 3 approaches that make different trade-offs between sc
Select the [render.yaml file](https://render.com/docs/yaml-spec) that matches your storage preferences and add it to the root of your Strapi project.
-:::: tabs
+:::: tabs card
::: tab strapi-sqlite
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy.md
index f42f826ed2..feb699f89f 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy.md
@@ -1,6 +1,7 @@
---
-title: Caddy Proxying - Strapi Developer Documentation
+title: Caddy Proxying - Strapi Developer Docs
description: Learn how you can use a proxy application like Caddy to secure your Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy.html
---
# Caddy Proxying
@@ -11,7 +12,9 @@ Caddy has some very easy to use options relating to Let's encrypt and automated
## Configuration
-The below configuration is based on "Caddy File" type, this is a single file config that Caddy will use to run the web server. There are multiple other options such as the Caddy REST API that this guide will not cover, you should review the [Caddy documentation](https://caddyserver.com/docs/) for further information on alternatives. You can also visit the [Caddy Community](https://caddy.community/) to speak with others relating to configuration questions.
+The below configuration is based on "Caddy File" type, this is a single file configuration that Caddy will use to run the web server. There are multiple other options such as the Caddy REST API that this guide will not cover, you should review the [Caddy documentation](https://caddyserver.com/docs/) for further information on alternatives. You can also visit the [Caddy Community](https://caddy.community/) to speak with others relating to configuration questions.
+
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/strapi-server.md)!!!
### Caddy file
@@ -21,25 +24,28 @@ In the below examples you will need to replace your domain, and should you wish
Below are 3 example Caddy configurations:
-- Sub-domain based such as `api.example.com`
-- Sub-folder based with both the API and Admin on the same sub-folder such as `example.com/api` and `example.com/api/admin`
-- Sub-folder based with split API and Admin such as `example.com/api` and `example.com/dashboard`
+- Subdomain-based such as `api.example.com`
+- Subfolder-based with both the API and Admin on the same subfolder (e.g. `example.com/test/api` and `example.com/test/admin`)
+- Subfolder-based with split API and admin panel (e.g. `example.com/api` and `example.com/dashboard`)
-::::: tabs
+::::: tabs card
-:::: tab Sub-Domain
+:::: tab Subdomain
-#### Sub-Domain
+#### Subdomain
-This config is using the sub-domain that is dedicated to Strapi only. It will bind to port 80 HTTP and proxies all requests (both api and admin) to the Strapi server running locally on the address specified. If you have configured Caddy properly to handle automated SSL you can remove the `http://` and Caddy will automatically convert all HTTP to HTTPS traffic.
+This configuration is using a subdomain dedicated to Strapi only. It will bind to port 80 HTTP and proxies all requests (both API and admin) to the Strapi server running locally on the address specified. If you have configured Caddy properly to handle automated SSL, you can remove the `http://` and Caddy will automatically convert all HTTP to HTTPS traffic.
---
-Example Domain: `api.example.com`
+- Example domain: `api.example.com`
+- Example admin panel: `api.example.com/admin`
+- Example API: `api.example.com/api`
+- Example uploaded Files (local provider): `api.example.com/uploads`
-**Path —** `/etc/caddy/Caddyfile`
+```sh
+# path: /etc/caddy/Caddyfile
-```
http://api.example.com {
reverse_proxy 127.0.0.1:1337
}
@@ -48,28 +54,31 @@ http://api.example.com {
::::
-:::: tab Sub-Folder-Unified
+:::: tab Subfolder unified
-#### Sub-Folder Unified
+#### Subfolder unified
-This config is using a sub-folder that is dedicated to Strapi only. It will bind to port 80 HTTP and hosts the "frontend" files on `/var/www` like a normal web server, but proxies all Strapi requests on the `example.com/api` sub-path.
+This configuration is using a subfolder dedicated to Strapi only. It will bind to port 80 HTTP and hosts the front-end files on `/var/www` like a normal web server, but proxies all Strapi requests on the `example.com/test` sub-path.
-::: warning
-Please note that this config is not focused on the frontend hosting, you will most likely need to adjust this to your frontend software requirements, it is only being shown here as an example.
+:::note
+This example configuration is not focused on the front end hosting and should be adjusted to your front-end software requirements.
:::
---
-Example Domain: `example.com/api`
+- Example domain: `example.com/test`
+- Example admin panel: `example.com/test/admin`
+- Example API: `example.com/test/api`
+- Example uploaded Files (local provider): `example.com/test/uploads`
-**Path —** `/etc/caddy/Caddyfile`
+```sh
+# path: /etc/caddy/Caddyfile
-```
-http://api.example.com {
+http://example.com {
root * /var/www
file_server
- route /api* {
- uri strip_prefix /api
+ route /test* {
+ uri strip_prefix /test
reverse_proxy 127.0.0.1:1337
}
}
@@ -77,37 +86,32 @@ http://api.example.com {
::::
-:::: tab Sub-Folder-Split
+:::: tab Subfolder split
-#### Sub-Folder Split
+#### Subfolder split
-This config is using two sub-folders that are dedicated to Strapi. It will bind to port 80 HTTP and hosts the "frontend" files on `/var/www` like a normal web server, but proxies all Strapi API requests on the `example.com/api` sub-path. Likewise it will proxy all admin requests on the `example.com/dashboard` sub-path.
+This configuration is using 2 subfolders dedicated to Strapi. It will bind to port 80 HTTP and hosts the front end files on `/var/www` like a normal web server, but proxies all Strapi API requests on the `example.com/api` subpath and all admin requests on the `example.com/dashboard` subpath.
-Alternatively for the admin, you can replace the proxy instead with serving the admin `build` folder directly from Caddy, such centralizing the admin but load balancing the backend APIs. The example for this is not shown, but it would likely be something you would build into your CI/CD platform.
+Alternatively, for the admin panel, you can replace the proxy instead with serving the admin `build` folder directly from Caddy, such centralizing the admin but load balancing the backend APIs. The example for this is not shown, but it would likely be something you would build into your CI/CD platform.
-::: warning
-Please note that this config is not focused on the frontend hosting, you will most likely need to adjust this to your frontend software requirements, it is only being shown here as an example.
+:::caution
+This example configuration is not focused on the front end hosting and should be adjusted to your front-end software requirements.
:::
---
-Example API Domain: `example.com/api`
-
-Example Admin Domain: `example.com/dashboard`
+- Example domain: `example.com`
+- Example admin: `example.com/dashboard`
+- Example API: `example.com/api`
+- Example uploaded Files (local provider): `example.com/uploads`
**Path —** `/etc/caddy/Caddyfile`
-```
-http://api.example.com {
- root * /var/www
- file_server
- route /api* {
- uri strip_prefix /api
- reverse_proxy 127.0.0.1:1337
- }
- route /dashboard* {
- reverse_proxy 127.0.0.1:1337
- }
+```sh
+# path: /etc/caddy/Caddyfile
+
+http://example.com {
+ reverse_proxy 127.0.0.1:1337
}
```
@@ -115,75 +119,4 @@ http://api.example.com {
:::::
-### Strapi Server
-
-In order to take full advantage of a proxied Strapi application you will need to configure Strapi to make it aware of the upstream proxy. Like with the above Caddy configurations there are 3 matching examples. To read more about this server configuration file please see the [server configuration](/developer-docs/latest/setup-deployment-guides/configurations.md#server) documentation.
-
-::::: tabs
-
-:::: tab Sub-Domain
-
-#### Sub-Domain Strapi config
-
----
-
-Example Domain: `api.example.com`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://api.example.com',
-});
-```
-
-::::
-
-:::: tab Sub-Folder-Unified
-
-#### Sub-Folder Unified Strapi config
-
----
-
-Example Domain: `example.com/api`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://example.com/api',
-});
-```
-
-::::
-
-:::: tab Sub-Folder-Split
-
-#### Sub-Folder Split Strapi config
-
----
-
-Example API Domain: `example.com/api`
-
-Example Admin Domain: `example.com/dashboard`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://example.com/api',
- admin: {
- url: 'https://example.com/dashboard',
- },
-});
-```
-
-::::
-
-:::::
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/admin-redirect.md)!!!
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy.md
index b6f3f57999..f60ba8a624 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy.md
@@ -1,6 +1,7 @@
---
-title: HAProxy Proxying - Strapi Developer Documentation
+title: HAProxy Proxying - Strapi Developer Docs
description: Learn how you can use a proxy application like HAProxy to secure your Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy.html
---
# HAProxy Proxying
@@ -9,33 +10,42 @@ As Strapi does not handle SSL directly and hosting a Node.js service on the "edg
## Configuration
-The below examples are more or less acting as an "SSL termination" proxy, meaning that HAProxy is only accepting the requests on SSL and proxying to other backend services such as Strapi or other web servers. **HAProxy cannot serve static content** and as such it is usually used to handle multi-server deployments in a failover or load-balance situation. The examples provided below are based around everything existing on the same server, but could easily be tweaked for multi-server deployments.
+The below examples are acting as an "SSL termination" proxy, meaning that HAProxy is only accepting the requests on SSL and proxying to other backend services such as Strapi or other web servers. HAProxy cannot serve static content and as such it is usually used to handle multi-server deployments in a failover or load-balance situation. The examples provided below are based around everything existing on the same server, but could easily be tweaked for multi-server deployments.
+
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/strapi-server.md)!!!
### HAProxy
-As mentioned previously the following examples are either proxying all requests directly to Strapi or are splitting requests between Strapi and some other backend web server such as Nginx, Apache, or others.
+The following examples are either proxying all requests directly to Strapi or are splitting requests between Strapi and some other backend web server such as Nginx, Apache, or others.
Below are 3 example HAProxy configurations:
- Sub-domain based such as `api.example.com`
-- Sub-folder based with both the API and Admin on the same sub-folder such as `example.com/api` and `example.com/api/admin`
-- Sub-folder based with split API and Admin such as `example.com/api` and `example.com/dashboard`
+- subfolder based with both the API and Admin on the same subfolder such as `example.com/test/api` and `example.com/test/admin`
+- subfolder based with split API and Admin such as `example.com/api` and `example.com/dashboard`
+
+:::caution HAProxy SSL Support
+If you are not familiar with HAProxy and using SSL certificates on the bind directive, you should combine your SSL cert, key, and any CA files into a single `.pem` package and use it's path in the bind directive. For more information see [HAProxy's bind documentation](https://www.haproxy.com/documentation/hapee/latest/onepage/#5.1). Most Let's Encrypt clients do not generate a file like this so you may need custom "after issue" scripts to do this for you.
+:::
-::::: tabs
+::::: tabs card
-:::: tab Sub-Domain
+:::: tab Subdomain
-#### Sub-Domain
+#### Subdomain
-This config is using the sub-domain that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies all requests (both api and admin) to the Strapi server running on the server.
+This configuration is using a subdomain dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies all requests (both API and admin) to the Strapi server running on the server.
---
-Example Domain: `api.example.com`
+- Example domain: `api.example.com`
+- Example admin panel: `api.example.com/admin`
+- Example API: `api.example.com/api`
+- Example uploaded Files (local provider): `api.example.com/uploads`
-**Path —** `/etc/haproxy/haproxy.cfg`
+```sh
+# path: /etc/haproxy/haproxy.cfg
-```
global
log /dev/log local0
log /dev/log local1 notice
@@ -75,7 +85,7 @@ defaults
frontend api.example.com
bind *:80
- bind *:443 ssl crt /path/to/your/cert
+ bind *:443 ssl crt /path/to/your/cert+key+ca.pem
http-request redirect scheme https unless { ssl_fc }
default_backend strapi-backend
@@ -85,23 +95,26 @@ backend strapi-backend
::::
-:::: tab Sub-Folder-Unified
+:::: tab Subfolder unified
-#### Sub-Folder Unified
+#### Subfolder unified
-This config is using a sub-folder that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies the "frontend" to `localhost:8080`, but proxies all Strapi requests on the `example.com/api` sub-path to the locally running Strapi application.
+This configuration is using a subfolder dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies the front end to `localhost:8080`, but proxies all Strapi requests on the `example.com/test` sub-path to the locally running Strapi application.
-::: warning
-HAProxy **cannot** serve static content, the below example is proxying frontend traffic to some other web server running on the localhost port 8080
+:::caution
+HAProxy cannot serve static content, the below example is proxying front-end traffic to some other web server running on the localhost port 8080.
:::
---
-Example Domain: `example.com/api`
+- Example domain: `example.com/test`
+- Example admin panel: `example.com/test/admin`
+- Example API: `example.com/test/api`
+- Example uploaded Files (local provider): `example.com/test/uploads`
-**Path —** `/etc/haproxy/haproxy.cfg`
+```sh
+# path: /etc/haproxy/haproxy.cfg
-```
global
log /dev/log local0
log /dev/log local1 notice
@@ -141,10 +154,10 @@ defaults
frontend example.com
bind *:80
- bind *:443 ssl crt /path/to/your/cert
+ bind *:443 ssl crt /path/to/your/cert+key+ca.pem
http-request redirect scheme https unless { ssl_fc }
- acl api path_beg /api
- use_backend strapi-backend if api
+ acl test path_beg /test
+ use_backend strapi-backend if test
default_backend default-backend
backend default-backend
@@ -153,32 +166,33 @@ backend default-backend
server somewebserver 127.0.0.1:8080
backend strapi-backend
- http-request set-path "%[path,regsub(^/api/?,/)]"
+ http-request set-path "%[path,regsub(^/test/?,/)]"
server local 127.0.0.1:1337
```
::::
-:::: tab Sub-Folder-Split
+:::: tab Subfolder split
-#### Sub-Folder Split
+#### Subfolder split
-This config is using a sub-folder that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies the "frontend" to `localhost:8080`, but proxies all strapi api requests on the `example.com/api` sub-path to the locally running Strapi application. Likewise it will proxy all admin requests on the `example.com/dashboard` sub-path.
+This config is using a subfolder dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies the front end to `localhost:8080`, but proxies all Strapi API requests on the `example.com/api` subpath to the locally running Strapi application and all admin requests on the `example.com/dashboard` subpath.
-::: warning
-Please note that this config is not focused on the frontend hosting, you will most likely need to adjust this to your frontend software requirements, it is only being shown here as an example.
+:::note
+This example configuration is not focused on the front end hosting and should be adjusted to your front-end software requirements.
:::
---
-Example API Domain: `example.com/api`
-
-Example Admin Domain: `example.com/dashboard`
+- Example domain: `example.com`
+- Example admin panel: `example.com/dashboard`
+- Example API: `example.com/api`
+- Example uploaded Files (local provider): `example.com/uploads`
-**Path —** `/etc/haproxy/haproxy.cfg`
+```sh
+# path: /etc/haproxy/haproxy.cfg
-```
global
log /dev/log local0
log /dev/log local1 notice
@@ -218,24 +232,11 @@ defaults
frontend example.com
bind *:80
- bind *:443 ssl crt /path/to/your/cert
+ bind *:443 ssl crt /path/to/your/cert+key+ca.pem
http-request redirect scheme https unless { ssl_fc }
- acl api path_beg /api
- acl dashboard path_beg /dashboard
- use_backend strapi-api-backend if api
- use_backend strapi-dashboard-backend if dashboard
- default_backend default-backend
-
-backend default-backend
- # HAProxy -cannot- serve static content on it's own
- # This example is relaying traffic to some other backend webserver
- server somewebserver 127.0.0.1:8080
-
-backend strapi-api-backend
- http-request set-path "%[path,regsub(^/api/?,/)]"
- server local 127.0.0.1:1337
+ default_backend strapi-backend
-backend strapi-dashboard-backend
+backend strapi-backend
server local 127.0.0.1:1337
```
@@ -243,75 +244,4 @@ backend strapi-dashboard-backend
:::::
-### Strapi Server
-
-In order to take full advantage of a proxied Strapi application you will need to configure Strapi to make it aware of the upstream proxy. Like with the above HAProxy configurations there are 3 matching examples. To read more about this server configuration file please see the [server configuration](/developer-docs/latest/setup-deployment-guides/configurations.md#server) documentation.
-
-::::: tabs
-
-:::: tab Sub-Domain
-
-#### Sub-Domain Strapi config
-
----
-
-Example Domain: `api.example.com`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://api.example.com',
-});
-```
-
-::::
-
-:::: tab Sub-Folder-Unified
-
-#### Sub-Folder Unified Strapi config
-
----
-
-Example Domain: `example.com/api`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://example.com/api',
-});
-```
-
-::::
-
-:::: tab Sub-Folder-Split
-
-#### Sub-Folder Split Strapi config
-
----
-
-Example API Domain: `example.com/api`
-
-Example Admin Domain: `example.com/dashboard`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://example.com/api',
- admin: {
- url: 'https://example.com/dashboard',
- },
-});
-```
-
-::::
-
-:::::
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/admin-redirect.md)!!!
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/nginx-proxy.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/nginx-proxy.md
index e0ab6f5784..724f9c2ed3 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/nginx-proxy.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/nginx-proxy.md
@@ -1,6 +1,7 @@
---
-title: Nginx Proxying - Strapi Developer Documentation
+title: Nginx Proxying - Strapi Developer Docs
description: Learn how you can use a proxy application like Nginx to secure your Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/deployment/optional-software/nginx-proxy.html
---
# Nginx Proxying
@@ -9,17 +10,19 @@ As Strapi does not handle SSL directly and hosting a Node.js service on the "edg
## Configuration
-The below configuration is based on Nginx virtual hosts, this means that you create configurations for each **domain** to allow serving multiple domains on the same port such as 80 (HTTP) or 443 (HTTPS). It also uses a central upstream file to store an alias to allow for easier management, load balancing, and failover in the case of clustering multiple Strapi deployments.
+The below configuration is based on Nginx virtual hosts, this means that you create configurations for each domain to allow serving multiple domains on the same port such as 80 (HTTP) or 443 (HTTPS). It also uses a central upstream file to store an alias to allow for easier management, load balancing, and failover in the case of clustering multiple Strapi deployments.
+
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/strapi-server.md)!!!
### Nginx Upstream
-Upstream blocks are used to map an alias such as `strapi` to a specific URL such as `localhost:1337`. While it would be useful to define these in each virtual host file, Nginx currently doesn't support loading these within the virtual host **if you have multiple virtual host files** and instead you should configure these within the `conf.d` directory as this is loaded before any virtual host files.
+Upstream blocks are used to map an alias such as `strapi` to a specific URL such as `localhost:1337`. While it would be useful to define these in each virtual host file, Nginx currently doesn't support loading these within the virtual host if you have multiple virtual host files. Instead, configure these within the `conf.d` directory as this is loaded before any virtual host files.
-In the below configuration we are mapping `localhost:1337` to the Nginx alias `strapi`.
+In the following configuration the `localhost:1337` is mapped to the Nginx alias `strapi`:
-**Path —** `/etc/nginx/conf.d/upstream.conf`
+```sh
+# path: /etc/nginx/conf.d/upstream.conf
-```
# Strapi server
upstream strapi {
server 127.0.0.1:1337;
@@ -28,31 +31,34 @@ upstream strapi {
### Nginx Virtual Host
-Virtual host files are what store the configuration for your specific app, service, or proxied service. For usage with Strapi this virtual host file is handling HTTPS connections and proxying them to Strapi running locally on the server. This configuration also redirects all HTTP requests to HTTPs using a 301 redirect.
+Virtual host files are what store the configuration for a specific app, service, or proxied service. For usage with Strapi this virtual host file is handling HTTPS connections and proxying them to Strapi running locally on the server. This configuration also redirects all HTTP requests to HTTPs using a 301 redirect.
In the below examples you will need to replace your domain and likewise your paths to SSL certificates will need to be changed based on where you place them or, if you are using Let's Encrypt, where your script places them. Please also note that while the path below shows `sites-available` you will need to symlink the file to `sites-enabled` in order for Nginx to enable the config.
Below are 3 example Nginx configurations:
-- Sub-domain based such as `api.example.com`
-- Sub-folder based with both the API and Admin on the same sub-folder such as `example.com/api` and `example.com/api/admin`
-- Sub-folder based with split API and Admin such as `example.com/api` and `example.com/dashboard`
+- subdomain based such as `api.example.com`
+- subfolder based with both the API and Admin on the same subfolder such as `example.com/test/api` and `example.com/test/admin`
+- subfolder based with split API and Admin such as `example.com/api` and `example.com/dashboard`
-::::: tabs
+::::: tabs card
-:::: tab Sub-Domain
+:::: tab Subdomain
-#### Sub-Domain
+#### Subdomain
-This config is using the sub-domain that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies all requests (both api and admin) to the Strapi server running on the upstream alias configured above.
+This configuration is using the subdomain that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and proxies all requests (both API and admin) to the Strapi server running on the upstream alias configured above.
---
-Example Domain: `api.example.com`
+- Example domain: `api.example.com`
+- Example admin panel: `api.example.com/admin`
+- Example API: `api.example.com/api`
+- Example uploaded Files (local provider): `api.example.com/uploads`
-**Path —** `/etc/nginx/sites-available/strapi.conf`
+```sh
+# path: /etc/nginx/sites-available/strapi.conf
-```
server {
# Listen HTTP
listen 80;
@@ -90,23 +96,26 @@ server {
::::
-:::: tab Sub-Folder-Unified
+:::: tab Subfolder unified
-#### Sub-Folder Unified
+#### Subfolder unified
-This config is using a sub-folder that is dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and hosts the "frontend" files on `/var/www/html` like a normal web server, but proxies all strapi requests on the `example.com/api` sub-path.
+This configuration is using a subfolder dedicated to Strapi only. It will redirect normal HTTP traffic over to SSL and hosts the front-end files on `/var/www/html` like a normal web server, but proxies all strapi requests on the `example.com/test` sub-path.
-::: warning
-Please note that this config is not focused on the frontend hosting, you will most likely need to adjust this to your frontend software requirements, it is only being shown here as an example.
+:::note
+This example configuration is not focused on the front end hosting and should be adjusted to your front-end software requirements.
:::
---
-Example Domain: `example.com/api`
+- Example domain: `example.com/test`
+- Example admin: `example.com/test/admin`
+- Example API: `example.com/test/api`
+- Example uploaded files (local provider): `example.com/test/uploads`
-**Path —** `/etc/nginx/sites-available/strapi.conf`
+```sh
+# path: /etc/nginx/sites-available/strapi.conf
-```
server {
# Listen HTTP
listen 80;
@@ -131,8 +140,8 @@ server {
}
# Strapi API and Admin
- location /api/ {
- rewrite ^/api/?(.*)$ /$1 break;
+ location /test/ {
+ rewrite ^/test/?(.*)$ /$1 break;
proxy_pass http://strapi;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-Host $host;
@@ -150,27 +159,28 @@ server {
::::
-:::: tab Sub-Folder-Split
+:::: tab Subfolder split
-#### Sub-Folder Split
+#### Subfolder split
-This config is using two sub-folders that are dedicated to Strapi. It will redirect normal HTTP traffic over to SSL and hosts the "frontend" files on `/var/www/html` like a normal web server, but proxies all strapi API requests on the `example.com/api` sub-path. Likewise it will proxy all admin requests on the `example.com/dashboard` sub-path.
+This configuration is using 2 subfolders dedicated to Strapi. It will redirect normal HTTP traffic over to SSL and hosts the front end files on `/var/www/html` like a normal web server, but proxies all strapi API requests on the `example.com/api` sub-path and all admin requests on the `example.com/dashboard` subpath.
Alternatively for the admin, you can replace the proxy instead with serving the admin `build` folder directly from Nginx, such centralizing the admin but load balancing the backend APIs. The example for this is not shown, but it would likely be something you would build into your CI/CD platform.
-::: warning
-Please note that this config is not focused on the frontend hosting, you will most likely need to adjust this to your frontend software requirements, it is only being shown here as an example.
+:::note
+This example configuration is not focused on the front end hosting and should be adjusted to your front-end software requirements.
:::
---
-Example API Domain: `example.com/api`
+- Example domain: `example.com`
+- Example admin: `example.com/dashboard`
+- Example API: `example.com/api`
+- Example uploaded files (local provider): `example.com/uploads`
-Example Admin Domain: `example.com/dashboard`
+```sh
+# path: /etc/nginx/sites-available/strapi.conf
-**Path —** `/etc/nginx/sites-available/strapi.conf`
-
-```
server {
# Listen HTTP
listen 80;
@@ -194,9 +204,8 @@ server {
root /var/www/html;
}
- # Strapi API
- location /api/ {
- rewrite ^/api/?(.*)$ /$1 break;
+ # Proxy Config
+ location / {
proxy_pass http://strapi;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-Host $host;
@@ -209,21 +218,6 @@ server {
proxy_set_header Connection "Upgrade";
proxy_pass_request_headers on;
}
-
- # Strapi Dashboard
- location /dashboard {
- proxy_pass http://strapi/dashboard;
- proxy_http_version 1.1;
- proxy_set_header X-Forwarded-Host $host;
- proxy_set_header X-Forwarded-Server $host;
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
- proxy_set_header X-Forwarded-Proto $scheme;
- proxy_set_header Host $http_host;
- proxy_set_header Upgrade $http_upgrade;
- proxy_set_header Connection "Upgrade";
- proxy_pass_request_headers on;
- }
}
```
@@ -231,75 +225,4 @@ server {
:::::
-### Strapi Server
-
-In order to take full advantage of a proxied Strapi application you will need to configure Strapi to make it aware of the upstream proxy. Like with the above Nginx configurations there are 3 matching examples. To read more about this server configuration file please see the [server configuration](/developer-docs/latest/setup-deployment-guides/configurations.md#server) documentation.
-
-::::: tabs
-
-:::: tab Sub-Domain
-
-#### Sub-Domain Strapi config
-
----
-
-Example Domain: `api.example.com`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://api.example.com',
-});
-```
-
-::::
-
-:::: tab Sub-Folder-Unified
-
-#### Sub-Folder Unified Strapi config
-
----
-
-Example Domain: `example.com/api`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://example.com/api',
-});
-```
-
-::::
-
-:::: tab Sub-Folder-Split
-
-#### Sub-Folder Split Strapi config
-
----
-
-Example API Domain: `example.com/api`
-
-Example Admin Domain: `example.com/dashboard`
-
-**Path —** `config/server.js`
-
-```js
-module.exports = ({ env }) => ({
- host: env('HOST', '0.0.0.0'),
- port: env.int('PORT', 1337),
- url: 'https://example.com/api',
- admin: {
- url: 'https://example.com/dashboard',
- },
-});
-```
-
-::::
-
-:::::
+!!!include(developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/admin-redirect.md)!!!
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/admin-redirect.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/admin-redirect.md
new file mode 100644
index 0000000000..a6b6f5ae9f
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/admin-redirect.md
@@ -0,0 +1,18 @@
+### Redirecting landing page to admin panel
+
+If you do not wish to have the default landing page mounted on `/` you can create a custom `./public/index.html` using the sample code below to automatically redirect to your admin panel.
+
+:::caution
+This sample configuration expects that the admin panel is accessible on `/admin`. If you used one of the above configurations to change this to `/dashboard` you will also need to adjust this sample configuration.
+:::
+
+**Path —** `./public/index.html`
+
+```html
+
+
+
+
+
+```
+
\ No newline at end of file
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/strapi-server.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/strapi-server.md
new file mode 100644
index 0000000000..c56970ccba
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/optional-software/snippets/strapi-server.md
@@ -0,0 +1,95 @@
+### Strapi server
+
+In order to take full advantage of a proxied Strapi application, Strapi should be configured so it's aware of the upstream proxy. Like with the below configurations there are 3 matching examples. Additional information can be found in the [server configuration](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md) and [admin configuration](/developer-docs/latest/setup-deployment-guides/configurations/required/admin-panel.md) documentations.
+
+:::note
+These examples use the default API Prefix of `/api`. This can be changed without the need to directly modify the Nginx configuration (see the [API prefix](/developer-docs/latest/setup-deployment-guides/configurations/optional/api.md) documentation).
+:::
+
+:::caution
+If the `url` key is changed in the `./config/admin.js` or `./config/server.js` files, the admin panel needs to be rebuilt with `yarn build` or `npm run build`.
+:::
+
+::::: tabs card
+
+:::: tab Subdomain
+
+#### Subdomain Strapi configuration
+
+---
+
+- Example domain: `api.example.com`
+- Example admin: `api.example.com/admin`
+- Example API: `api.example.com/api`
+- Example uploaded files (local provider): `api.example.com/uploads`
+
+```js
+// path: ./config/server.js
+
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+ url: 'https://api.example.com',
+});
+```
+
+::::
+
+:::: tab Subfolder unified
+
+#### Subfolder unified Strapi configuration
+
+---
+
+- Example domain: `example.com/test`
+- Example admin: `example.com/test/admin`
+- Example API: `example.com/test/api`
+- Example uploaded Files (local provider): `example.com/test/uploads`
+
+```js
+// path: ./config/server.js
+
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+ url: 'https://example.com/test',
+});
+```
+
+::::
+
+:::: tab Subfolder split
+
+#### Subfolder split Strapi configuration
+
+---
+
+- Example domain: `example.com`
+- Example admin: `example.com/dashboard`
+- Example API: `example.com/api`
+- Example uploaded files (local provider): `example.com/uploads`
+
+```js
+// path: ./config/server.js
+
+module.exports = ({ env }) => ({
+ host: env('HOST', '0.0.0.0'),
+ port: env.int('PORT', 1337),
+ url: 'https://example.com',
+});
+```
+
+```js
+// path: ./config/admin.js
+
+module.exports = ({ env }) => ({
+ auth: {
+ ...
+ }
+ url: 'https://example.com/dashboard',
+});
+```
+
+::::
+
+:::::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md b/docs/developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md
new file mode 100644
index 0000000000..d2fadc8b00
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/deployment/snippets/deployment-guide-not-updated.md
@@ -0,0 +1,3 @@
+::: caution
+This third-party deployment guide might not be up-to-date with Strapi v4. [Contributions](https://github.com/strapi/documentation/blob/main/CONTRIBUTING.md) are most welcome.
+:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/file-structure.md b/docs/developer-docs/latest/setup-deployment-guides/file-structure.md
index a8213a0ecc..3b4b0394c1 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/file-structure.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/file-structure.md
@@ -1,43 +1,101 @@
---
-title: Project Structure - Strapi Developer Documentation
+title: Project Structure - Strapi Developer Docs
description: Discover the project structure of any default Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/file-structure.html
---
+
+
# Project structure
-By default, the structure of your Strapi project looks as shown below:
-
-- `/.cache`: contains files used to build your admin panel.
-- [`/admin`](/developer-docs/latest/development/admin-customization.md): _(optional)_ contains your admin customization files.
-- `/api`: contains the business logic of your project split into sub-folders per API.
- - `**`
- - `/config`: contains the API's configurations ([`routes`](/developer-docs/latest/development/backend-customization.md#routing), [`policies`](/developer-docs/latest/development/backend-customization.md#policies), etc.).
- - [`/controllers`](/developer-docs/latest/development/backend-customization.md#controllers): contains the API's custom controllers.
- - [`/models`](/developer-docs/latest/development/backend-customization.md#models): contains the API's models.
- - [`/services`](/developer-docs/latest/development/backend-customization.md#services): contains the API's custom services.
-- `/build`: contains your admin panel UI build.
-- [`/config`](/developer-docs/latest/setup-deployment-guides/configurations.md)
- - [`/functions`](/developer-docs/latest/setup-deployment-guides/configurations.md#functions): contains lifecycle or generic functions of the project.
- - [`/responses`](/developer-docs/latest/development/backend-customization.md#requests-responses): contains custom responses.
- - `404.js`: contains a template for constructing your custom 404 message.
- - [`bootstrap.js`](/developer-docs/latest/setup-deployment-guides/configurations.md#bootstrap): contains the code executed at the application start.
- - [`cron.js`](/developer-docs/latest/setup-deployment-guides/configurations.md#cron-tasks): contains the cron tasks.
- - [`server.js`](/developer-docs/latest/setup-deployment-guides/configurations.md#server): contains the general configurations of the project.
- - [`database.js`](/developer-docs/latest/setup-deployment-guides/configurations.md#database): contains the database configurations of the project.
-- `/extensions`: contains the files to extend installed plugins.
-- [`/hooks`](/developer-docs/latest/setup-deployment-guides/configurations.md#hooks): contains the custom hooks of the project.
-- [`/middlewares`](/developer-docs/latest/setup-deployment-guides/configurations.md#middlewares): contains the custom middlewares of the project.
-- [`/plugins`](/developer-docs/latest/setup-deployment-guides/configurations.md#plugins): contains your local plugins.
-- [`/public`](/developer-docs/latest/setup-deployment-guides/configurations.md#public-assets): contains the files accessible to the outside world.
-- `/node_modules`: contains the npm packages used by the project.
-
-If your Strapi project was created with the [starter CLI](https://strapi.io/blog/announcing-the-strapi-starter-cli), the project structure looks like this:
+:::: note
+If the Strapi project was created with the [starter CLI](https://strapi.io/blog/announcing-the-strapi-starter-cli), its structure includes both a `frontend` and `backend` folder, where the `backend` folder has the default structure.
+
+::: details Structure of a project created with the starter CLI
```sh
my-project
- /frontend # starter folder
- /backend # template folder
- /node_modules
+├─── frontend # starter folder
+├─── backend # template folder, has the default structure of a project
+└─── node_modules
```
-and the `backend` folder has the default structure described above.
+:::
+::::
+
+The default structure of a Strapi project created without the starter CLI looks like the following:
+
+
+
+.
+├──── .cache
+├──── .tmp
+├──── build
+├──── config
+│ ├ api.js
+│ ├ admin.js
+│ ├ cron-tasks.js
+│ ├ database.js
+│ ├ middlewares.js
+│ ├ plugins.js
+│ └ server.js
+├──── database
+│ └──── migrations
+├──── node_modules
+├──── public
+│ └──── uploads
+├──── src
+│ ├──── admin
+│ │ ├ app.js
+│ │ └ webpack.config.js
+│ ├──── api
+│ │ └──── (api-name)
+│ │ ├──── content-types
+│ │ │ └──── (content-type-name)
+│ │ │ └ lifecyles.js
+│ │ │ └ schema.json
+│ │ ├──── controllers
+│ │ ├──── middlewares
+│ │ ├──── policies
+│ │ ├──── routes
+│ │ ├──── services
+│ │ └ index.js
+│ ├──── components
+│ │ └──── (category-name)
+│ │ ├ (componentA).json
+│ │ └ (componentB).json
+│ ├──── extensions
+│ │ └──── (plugin-to-be-extended)
+│ │ ├──── content-types
+│ │ │ └──── (content-type-name)
+│ │ │ └ schema.json
+│ │ └ strapi-server.js
+│ ├──── middlewares
+│ │ └──── (middleware-name)
+│ │ ├ defaults.json
+│ │ └ index.js
+│ ├──── plugins
+│ │ └──── (plugin-name)
+│ │ ├──── admin
+│ │ │ └──── src
+│ │ │ └ index.js
+│ │ ├──── server
+│ │ ├──── controllers
+│ │ ├──── policies
+│ │ ├ package.json
+│ │ ├ strapi-admin.js
+│ │ └ strapi-server.js
+│ ├─── policies
+│ └ index.js
+├ .env
+└ package.json
+
+
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation.md b/docs/developer-docs/latest/setup-deployment-guides/installation.md
index c1d443d2fd..cbc8c73861 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation.md
@@ -1,6 +1,7 @@
---
-title: Installation - Strapi Developer Documentation
+title: Installation - Strapi Developer Docs
description: Learn many different options to install Strapi and getting started on using it.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation.html
---
# Installation
@@ -45,9 +46,7 @@ Strapi projects and applications can be installed either locally on a computer,
## One-click installations
-::: warning WARNING
-One-click installation guides stop being updated by the Strapi documentation team starting at the release of Strapi v4. Community contributions to keep these guides updates are very welcome.
-:::
+!!!include(developer-docs/latest/setup-deployment-guides/snippets/one-click-install-not-updated.md)!!!
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/cli.md b/docs/developer-docs/latest/setup-deployment-guides/installation/cli.md
index eaeec71283..d02f6c22a9 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/cli.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/cli.md
@@ -1,48 +1,9 @@
---
-title: Installing from CLI - Strapi Developer Documentation
+title: Installing from CLI - Strapi Developer Docs
description: Fast-track local install for getting Strapi running on your computer in less than a minute.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/cli.html
---
-
-
# Installing from CLI
Strapi CLI (Command Line Interface) installation scripts are the fastest way to get Strapi running locally. The following guide is the installation option most recommended by Strapi.
@@ -51,52 +12,54 @@ Strapi CLI (Command Line Interface) installation scripts are the fastest way to
The CLI installation guide requires at least two software prerequisites to be already installed on your computer:
-- [Node.js](https://nodejs.org): only LTS versions are supported (version 12.x minimum). Other versions of Node.js may not be compatible with the latest release of Strapi. The 14.x version is most recommended by Strapi.
-- [npm](https://docs.npmjs.com/cli/v6/commands/npm-install) (version 6.x minimum) or [yarn](https://yarnpkg.com/getting-started/install) to run the CLI installation scripts.
+- [Node.js](https://nodejs.org): only LTS versions are supported (v12 and v14). Other versions of Node.js may not be compatible with the latest release of Strapi. The 14.x version is most recommended by Strapi.
+- [npm](https://docs.npmjs.com/cli/v6/commands/npm-install) (v6 only) or [yarn](https://yarnpkg.com/getting-started/install) to run the CLI installation scripts.
A database is also required for any Strapi project. Strapi currently supports the following databases:
-::: warning WARNING
-Starting from the release of Strapi v4, MongoDB is not supported natively anymore and no connector is available. For more information, please refer to [the official communication on the topic](https://strapi.io/blog/mongo-db-support-in-strapi-past-present-and-future).
-:::
-
| Database | Minimum version |
| ---------- | --------------- |
| SQLite | 3 |
| PostgreSQL | 10 |
| MySQL | 5.6 |
| MariaDB | 10.1 |
-| MongoDB | 3.6 |
## Creating a Strapi project
-::: danger 🤓 CLI installation options
+::: strapi CLI installation options
The following installation guide covers the most basic installation option using the CLI. There are however other options that can be used when creating a new Strapi project:
- Using the `--quickstart` flag at the end of the command to directly create the project in quickstart mode.
- Using the `--template` flag at the end of the command to create a project with pre-made Strapi configurations (see [Templates](templates.md)).
+- Using the `--no-run` flag will prevent Strapi from automatically starting the server (useful in combination with `--quickstart`)
+
+For more information on available flags, see our [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI).
Strapi also offers a starters CLI to create a project with a pre-made frontend application (see [our dedicated blog post](https://strapi.io/blog/announcing-the-strapi-starter-cli)).
:::
-
1. In a terminal, run the following command:
-:::: tabs card
-::: tab npm
- ```sh
- npx create-strapi-app my-project
- ```
-:::
-::: tab yarn
- ```sh
- yarn create strapi-app my-project
- ```
-:::
+
+
+
+```sh
+npx create-strapi-app@latest my-project
+```
+
+
+
+```sh
+yarn create strapi-app my-project
+```
+
+
+
2. Choose an installation type:
- * `Quickstart (recommended)`, which uses the default database (SQLite)
- * `Custom (manual settings)`, which allows to choose your preferred database
+
+ - `Quickstart (recommended)`, which uses the default database (SQLite)
+ - `Custom (manual settings)`, which allows to choose your preferred database
3. When terminal asks `Would you like to use a template?`, type `y` for yes or `n` for no then press Enter.
@@ -110,15 +73,18 @@ Strapi also offers a starters CLI to create a project with a pre-made frontend a
To start the Strapi application, run the following command in the project folder:
-:::: tabs card
-::: tab npm
+
+
+
```bash
npm run develop
```
-:::
+
-::: tab yarn
+
```sh
yarn develop
```
-:::
+
+
+
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-customization.md b/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-customization.md
index 9368868942..48588bd499 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-customization.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-customization.md
@@ -7,14 +7,15 @@ You can click below for more information about the installed software and the Ng
::: details Installed software
The Strapi application running on the droplet has the following softwares installed and configured:
-| Software | Version | Comments |
-|----------------|-----------------------|----------------|
-| Node.js | 12 | Installed via the offical [apt repository](https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions)) |
-| Yarn | latest stable version | Installed via the official [apt repository](https://classic.yarnpkg.com/en/docs/install/#debian-stable)) |
-| Nginx | latest version | Installed via Ubuntu default repository |
-| UFW (Uncomplicated Firewall) | latest stable version | Configured to only allow incoming ports 80 (HTTP), 443 (HTTPS), and 22 (SSH) |
-| PostgreSQL | latest version | Installed via Ubuntu default repository |
-| PM2 | latest version | Installed globally using Yarn |
+| Software | Version | Comments |
+| ---------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| Node.js | 12 | Installed via the offical [apt repository](https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions)) |
+| Yarn | latest stable version | Installed via the official [apt repository](https://classic.yarnpkg.com/en/docs/install/#debian-stable)) |
+| Nginx | latest version | Installed via Ubuntu default repository |
+| UFW (Uncomplicated Firewall) | latest stable version | Configured to only allow incoming ports 80 (HTTP), 443 (HTTPS), and 22 (SSH) |
+| PostgreSQL | latest version | Installed via Ubuntu default repository |
+| PM2 | latest version | Installed globally using Yarn |
+
:::
::::: details Nginx default configuration
@@ -81,13 +82,12 @@ The Strapi application runs in the `development` environment to allow for creati
To run the new `production` or `staging` environments you can refer to the [PM2 Documentation](https://pm2.keymetrics.io/docs/usage/quick-start/#managing-processes)
-
### Accessing the service account
To access your service account:
1. SSH into the `root` user. Depending on your Operating System or your SSH client, there may be multiple ways to do this. You should refer to your SSH client documentation for clarification on using SSH keys.
-2. Run the `sudo su strapi` command. This will take you to the `strapi` user's shell.
+2. Run the `sudo su strapi` command. This will take you to the `strapi` user's shell.
To go back to the `root` user, run `exit`.
@@ -99,17 +99,16 @@ Please note that by default the strapi user cannot run `sudo` commands. This is
While identified as the service user on the DigitalOcean virtual machine, [PM2](https://pm2.keymetrics.io/docs/usage/quick-start/#managing-processes) can be used to control the Strapi process and view logs with the following commands:
-* `pm2 list`: Show a list of all running processes. The default service is called "strapi-development" and should be running with an ID of 0.
-* `pm2 restart strapi-development`: Restart the Strapi process manually.
-* `pm2 stop strapi-development`: Stop the Strapi process.
-* `pm2 start strapi-development`: Start the Strapi process. Strapi will automatically start if the virtual machine is rebooted.
-* `pm2 logs strapi-development`: Show the logs in real time; to exit, use Ctrl+C.
+- `pm2 list`: Show a list of all running processes. The default service is called "strapi-development" and should be running with an ID of 0.
+- `pm2 restart strapi-development`: Restart the Strapi process manually.
+- `pm2 stop strapi-development`: Stop the Strapi process.
+- `pm2 start strapi-development`: Start the Strapi process. Strapi will automatically start if the virtual machine is rebooted.
+- `pm2 logs strapi-development`: Show the logs in real time; to exit, use Ctrl+C.
:::tip TIP
You can also manually view the log files under `/srv/strapi/.pm2/logs` if you encounter any errors during the bootup.
:::
-
## Strapi application access with ssh
To ssh into your Strapi application, run the following command:
@@ -129,12 +128,12 @@ To change the PostgreSQL password and update Strapi's config:
1. Log into the [`strapi`](#accessing-the-service-account) service user.
2. Run the `pm2 stop strapi-development` command to stop the current strapi process.
3. Run this command to change the password for the `strapi` database user:
+
```bash
psql -c "ALTER USER strapi with password '';"
```
+
where `` should be replaced by the password you want to use.
-
-
4. Update the `/srv/strapi/strapi-development/.env` file with the new password:
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-one-click.md b/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-one-click.md
index cbd6d907cd..ee42bb3f4f 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-one-click.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/digitalocean-one-click.md
@@ -1,62 +1,20 @@
---
-title: DigitalOcean One-click - Strapi Developer Documentation
+title: DigitalOcean One-click - Strapi Developer Docs
description: Quickly deploy a Strapi application on DigitalOcean by simply using their One-click button.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/digitalocean-one-click.html
---
-
-
# DigitalOcean One-click
-::: warning
- The one-click install droplet is currently missing from DigitalOcean's marketplace. We are actively working with them on this issue and recommend you to use another installation method in the meantime.
- :::
+::: caution
+The one-click install droplet is currently missing from DigitalOcean's marketplace. We are not planning to continue support for this installation method but if you want to configure it yourself you can use our [one-click repo](https://github.com/strapi/one-click-deploy) to build the image yourself.
+:::
-The following documentation will guide you through the one-click creation of a new Strapi project hosted on [DigitalOcean](https://www.digitalocean.com/).
+The following documentation will guide you through the one-click creation of a new Strapi project hosted on [DigitalOcean](https://www.digitalocean.com/)
DigitalOcean is a cloud platform that helps to deploy and scale applications by offering an Infrastructure as a Service (IaaS) platform for developers.
-:::tip PREREQUISITES
+::: prerequisites
A DigitalOcean account is necessary to follow this installation guide. Please visit the [DigitalOcean website](https://try.digitalocean.com/strapi/) to create an account if you don't already have one.
:::
@@ -85,6 +43,6 @@ To visit your Strapi application:
Visiting the Strapi application page for the first time will require to create the first administrator user.
-::: danger 🤓 Customization options for the DigitalOcean droplet
+::: strapi Customization options for the DigitalOcean droplet
The DigitalOcean droplet includes everything you need to run Strapi. However, should you need to access and customize the droplet environment and change some of its settings, you may want to refer to [our dedicated documentation](/developer-docs/latest/setup-deployment-guides/installation/digitalocean-customization.md). You can also find the image generation [source code](https://github.com/strapi/one-click-deploy/tree/master/digital-ocean) on Strapi's GitHub.
:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/docker.md b/docs/developer-docs/latest/setup-deployment-guides/installation/docker.md
index 268abe6ac7..8a969f99a3 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/docker.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/docker.md
@@ -1,6 +1,7 @@
---
-title: Install from Docker - Strapi Developer Documentation
+title: Install from Docker - Strapi Developer Docs
description: Quickly create a Strapi application using our official Strapi Docker images.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/docker.html
---
# Installing using Docker
@@ -9,7 +10,7 @@ The following documentation will guide you through the installation of a new Str
Docker is an open platform that allows to develop, ship and run applications by using containers (i.e. packages containing all the parts an application needs to function, such as libraries and dependencies).
-::: tip NOTE
+::: note
You can find the official Docker image for Strapi in the [Docker Hub](https://hub.docker.com/r/strapi/strapi).
:::
@@ -68,44 +69,6 @@ You can find the official Docker image for Strapi in the [Docker Hub](https://hu
::::
- :::: tab MongoDB
-
-
- ::: warning WARNING
- Starting from the release of Strapi v4, MongoDB is not supported natively anymore and no connector is available. For more information, please refer to [the official communication on the topic](https://strapi.io/blog/mongo-db-support-in-strapi-past-present-and-future).
- :::
-
- ```yaml
- version: '3'
- services:
- strapi:
- image: strapi/strapi
- environment:
- DATABASE_CLIENT: mongo
- DATABASE_NAME: strapi
- DATABASE_HOST: mongo
- DATABASE_PORT: 27017
- DATABASE_USERNAME: strapi
- DATABASE_PASSWORD: strapi
- volumes:
- - ./app:/srv/app
- ports:
- - '1337:1337'
- depends_on:
- - mongo
-
- mongo:
- image: mongo
- environment:
- MONGO_INITDB_DATABASE: strapi
- MONGO_INITDB_ROOT_USERNAME: strapi
- MONGO_INITDB_ROOT_PASSWORD: strapi
- volumes:
- - ./data:/data/db
- ```
-
- ::::
-
:::: tab MySQL
```yaml
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/platformsh.md b/docs/developer-docs/latest/setup-deployment-guides/installation/platformsh.md
index 8d5c8b889f..f5fe6a5470 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/platformsh.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/platformsh.md
@@ -1,40 +1,19 @@
---
-title: Install using Platform.sh - Strapi Developer Documentation
+title: Install using Platform.sh - Strapi Developer Docs
description: Quickly deploy a Strapi application using the official Platform.sh Strapi template.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/platformsh.html
sidebarDepth: 1
---
-
-
# Platform.sh One-Click
+!!!include(developer-docs/latest/setup-deployment-guides/snippets/one-click-install-not-updated.md)!!!
+
The following documentation will guide you through the one-click creation of a new Strapi project hosted on [Platform.sh](https://platform.sh/).
Platform.sh is a Platform as a Service (PaaS) that allows the management of multiple websites and applications. In particular, it allows to quickly install and deploy a Strapi application.
-::: warning PREREQUISITES
+::: prerequisites
A Platform.sh account is necessary to follow this installation guide. Please visit the [Platform.sh website](https://console.platform.sh/) to create an account if you don't already have one.
:::
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/render.md b/docs/developer-docs/latest/setup-deployment-guides/installation/render.md
index cdfec06b60..fa7d0f5824 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/render.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/render.md
@@ -1,39 +1,18 @@
---
-title: Render One-Click - Strapi Developer Documentation
+title: Render One-Click - Strapi Developer Docs
description: Quickly deploy a Strapi application on Render by simply using their One-click button.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/render.html
---
-
-
# Render One-Click
+!!!include(developer-docs/latest/setup-deployment-guides/snippets/one-click-install-not-updated.md)!!!
+
The following documentation will guide you through the one-click creation of a new Strapi project hosted on [Render](https://render.com).
Render is a cloud provider with persistent disks and managed PostgreSQL databases, that offers multiple different ways to store content.
-::: warning PREREQUISITES
+::: prerequisites
A Render account is necessary to follow this installation guide. Please visit [the Render dashboard](https://dashboard.render.com) to create an account if you do not already have one.
:::
@@ -51,13 +30,13 @@ Once the choice between the 3 repositories is made:
2. In the README file of your forked repository, click the **Deploy on Render** button.
3. Make sure you granted Render the permission to access your forked repository.
-::: tip NOTE
+::: note
When using Cloudinary, you will be prompted to enter your account credentials as environment variables. Render encrypts environment variables and stores them securely.
:::
## Running Strapi
-Your Strapi application on Render will be running in production mode, with `NODE_ENV=production`. However, to add or edit content-types via the admin panel (see [Content-Types Builder](https://strapi.io/documentation/user-docs/latest/content-types-builder/introduction-to-content-types-builder.html) documentation), Strapi must be running locally in development mode.
+Your Strapi application on Render will be running in production mode, with `NODE_ENV=production`. However, to add or edit content-types via the admin panel (see [Content-Type Builder](https://strapi.io/documentation/user-docs/latest/content-types-builder/introduction-to-content-types-builder.html) documentation), Strapi must be running locally in development mode.
To run Strapi locally:
diff --git a/docs/developer-docs/latest/setup-deployment-guides/installation/templates.md b/docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
index 22f92ca63f..642f6263c0 100644
--- a/docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
+++ b/docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
@@ -1,6 +1,7 @@
---
-title: Templates - Strapi Developer Documentation
+title: Templates - Strapi Developer Docs
description: Quickly create a pre-made Strapi application designed for a specific use case. It allows you to quickly bootstrap a custom Strapi app.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/templates.html
---
# Templates
@@ -13,7 +14,7 @@ Here are some things a template may configure for you:
- Components and dynamic zones
- Plugins to install, or custom plugins
-::: warning
+:::note
Templates and starters are not the same thing:
- A _template_ is a pre-made Strapi configuration. Note that it's only a configuration, not a configured application. That's because it cannot be run on its own, since it lacks many files, like database configs or the `package.json`. A template is only useful once applied on top of a default Strapi app via the CLI.
@@ -38,7 +39,7 @@ yarn create strapi-app my-project --template
::: tab npx
```bash
-npx create-strapi-app my-project --template
+npx create-strapi-app@latest my-project --template
```
:::
@@ -78,14 +79,14 @@ First, a template's only concern should be to adapt Strapi to a use case. It sho
Second, a template must follow the file structure detailed below.
-You can create this file structure by hand or generate it via the [CLI](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate-template).
+You can create this file structure by hand or generate it via the [CLI](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-templates-generate).
:::: tabs
::: tab yarn
```bash
-yarn strapi generate:template
+yarn strapi templates:generate
```
:::
@@ -93,7 +94,7 @@ yarn strapi generate:template
::: tab npx
```bash
-npx strapi generate:template
+npx strapi templates:generate
```
:::
@@ -155,7 +156,7 @@ After reading the above rules, follow these steps to create your template:
1. Create a standard Strapi app with `create-strapi-app`, using the `--quickstart` option.
2. Customize your app to match the needs of your use case.
-3. Generate your template using the [CLI](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-generate-template) by running `strapi generate:template `
+3. Generate your template using the [CLI](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-templates-generate) by running `strapi templates:generate `
4. Navigate to this path to see your generated template
5. If you have modified your app's `package.json`, include these changes (and _only_ these changes) in `template.json` in a `package` property. Otherwise, leave it as an empty object.
6. Publish the root template project on GitHub. Make sure that the repository is public, and that the code is on the `master` branch.
diff --git a/docs/developer-docs/latest/setup-deployment-guides/snippets/one-click-install-not-updated.md b/docs/developer-docs/latest/setup-deployment-guides/snippets/one-click-install-not-updated.md
new file mode 100644
index 0000000000..10b71ecae7
--- /dev/null
+++ b/docs/developer-docs/latest/setup-deployment-guides/snippets/one-click-install-not-updated.md
@@ -0,0 +1,3 @@
+::: caution
+One-click installation guides are not updated by the Strapi documentation team anymore. [Community contributions](https://github.com/strapi/documentation/blob/main/CONTRIBUTING.md) are most welcome.
+:::
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides.md b/docs/developer-docs/latest/update-migration-guides/migration-guides.md
index 8e1343df3c..5640dc0d76 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides.md
@@ -1,13 +1,14 @@
---
-title: Migrate Guides - Strapi Developer Documentation
+title: Migrate Guides - Strapi Developer Docs
description: All the migration guides for a Strapi application.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides.html
---
# Migrations guides
## Instructions
-When upgrading your application you will need to follow every migration guide between your current version and the one you are upgrading to.
+When upgrading your application you will need to follow every migration guide between your current version and the one you are upgrading to.
::: tip TIP
If there is no specific migration guide for your version step(s), you should follow the general [Update Strapi guide](update-version.md).
@@ -25,7 +26,11 @@ If you were to upgrade your version from `3.2.3` to `3.6.1`, you would have to f
4. Migration guide from 3.4.x to 3.4.4.
5. [Update Strapi guide.](update-version.md)
-## V3 guides
+## v4-Stable guides
+
+At the moment there are no migration guides from v3-Stable to v4-Stable. These will be coming soon!
+
+## V3-Stable guides
- [Migration guide from 3.4.x to 3.4.4](migration-guides/migration-guide-3.4.x-to-3.4.4.md)
- [Migration guide from 3.3.x to 3.4.0](migration-guides/migration-guide-3.3.x-to-3.4.0.md)
@@ -34,11 +39,12 @@ If you were to upgrade your version from `3.2.3` to `3.6.1`, you would have to f
- [Migration guide from 3.1.x to 3.2.3](migration-guides/migration-guide-3.1.x-to-3.2.x.md)
- [Migration guide from 3.0.x to 3.1.x](migration-guides/migration-guide-3.0.x-to-3.1.x.md)
-## Beta guides
+## v3-Beta guides
::: warning
The Strapi Beta version is no longer supported, you should upgrade to the V3 Stable.
+If you have issues upgrading, it's our general recommendation to create a new project.
:::
@@ -50,7 +56,7 @@ The Strapi Beta version is no longer supported, you should upgrade to the V3 Sta
- [Migration guide from beta.16+ to beta.17.4](migration-guides/migration-guide-beta.16-to-beta.17.4.md)
- [Migration guide from beta.15 to beta.16](migration-guides/migration-guide-beta.15-to-beta.16.md)
-## Alpha guides
+## v3-Alpha guides
::: warning
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-1-to-3.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-1-to-3.md
index 9f0a333871..aacaee3870 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-1-to-3.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-1-to-3.md
@@ -1,6 +1,7 @@
---
-title: Migrate from v1 to v3 - Strapi Developer Documentation
+title: Migrate from v1 to v3 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from v1 to v3.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-1-to-3.html
---
# Migrating from v1 to v3
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.0.x-to-3.1.x.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.0.x-to-3.1.x.md
index 8240c87579..ae298646d7 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.0.x-to-3.1.x.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.0.x-to-3.1.x.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.0.x to 3.1.x - Strapi Developer Documentation
+title: Migrate from 3.0.x to 3.1.x - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from 3.0.x to 3.1.x.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.0.x-to-3.1.x.html
---
# Migration guide from 3.0.x to 3.1.x
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.1.x-to-3.2.x.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.1.x-to-3.2.x.md
index 7e68999b71..f638612903 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.1.x-to-3.2.x.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.1.x-to-3.2.x.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.1.x to 3.2.3 - Strapi Developer Documentation
+title: Migrate from 3.1.x to 3.2.3 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from 3.1.x to 3.2.3.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.1.x-to-3.2.x.html
---
# Migration guide from 3.1.x to 3.2.3
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.3-to-3.2.4.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.3-to-3.2.4.md
index bfdd401a5c..e34598cdab 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.3-to-3.2.4.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.3-to-3.2.4.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.2.3 to 3.2.4 - Strapi Developer Documentation
+title: Migrate from 3.2.3 to 3.2.4 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from 3.2.3 to 3.2.4.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.3-to-3.2.4.html
---
# Migration guide from 3.2.3 to 3.2.4
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.5-to-3.3.0.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.5-to-3.3.0.md
index 5893423529..7f5816feaa 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.5-to-3.3.0.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.5-to-3.3.0.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.2.5 to 3.3.0 - Strapi Developer Documentation
+title: Migrate from 3.2.5 to 3.3.0 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from 3.2.5 to 3.3.0.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.2.5-to-3.3.0.html
---
# Migration guide from 3.2.5 to 3.3.0
@@ -63,6 +64,4 @@ _After_
strapi.notification.toggle(config);
```
-Here is a link to the [new notification API](/developer-docs/latest/development/local-plugins-customization.md#front-end-development).
-
That's it, now you can follow the basic [version update guide](/developer-docs/latest/update-migration-guides/update-version.md).
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.3.x-to-3.4.0.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.3.x-to-3.4.0.md
index 1b0ce99710..99b227debe 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.3.x-to-3.4.0.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.3.x-to-3.4.0.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.3.x to 3.4.0 - Strapi Developer Documentation
+title: Migrate from 3.3.x to 3.4.0 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from 3.3.x to 3.4.0.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.3.x-to-3.4.0.html
---
# Migration guide from 3.3.x to 3.4.0
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.4.x-to-3.4.4.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.4.x-to-3.4.4.md
index 967d79a6aa..47dc81fd78 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.4.x-to-3.4.4.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.4.x-to-3.4.4.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.4.x to 3.4.4 - Strapi Developer Documentation
+title: Migrate from 3.4.x to 3.4.4 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from 3.4.x to 3.4.4.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-3.4.x-to-3.4.4.html
---
# Migration guide from 3.4.x to 3.4.4
@@ -30,7 +31,7 @@ Recently Instagram shutdown their API in favor of a new one (see [https://www.in
- In your database, find the table `core_store`
- In that table, find the row with the key `plugin_users-permissions_grant`
- In that row, find the `value` column (it's JSON)
-- In this JSON, find the `instagram` attribute and edit it to add `"scope": ["user_profile"]` (⚠️ becareful to respect the JSON format)
+- In this JSON, find the `instagram` attribute and edit it to add `"scope": ["user_profile"]` (⚠️ make sure to respect the JSON format)
```diff
...
@@ -54,7 +55,7 @@ Recently Instagram shutdown their API in favor of a new one (see [https://www.in
- In your database, find the collection `core_store`
- In that collection, find the document with the key `plugin_users-permissions_grant`
- In that document, find the `value` field (it's JSON)
-- In this JSON, find the `instagram` attribute and edit it to add `"scope": ["user_profile"]` (⚠️ becareful to respect the JSON format)
+- In this JSON, find the `instagram` attribute and edit it to add `"scope": ["user_profile"]` (⚠️ make sure to respect the JSON format)
```diff
...
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.10-to-alpha.11.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.10-to-alpha.11.md
index a0d8ead089..6c9a99b599 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.10-to-alpha.11.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.10-to-alpha.11.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.10 to alpha.11 - Strapi Developer Documentation
+title: Migrate from alpha.10 to alpha.11 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.10 to alpha.11.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.10-to-alpha.11.html
---
# Migration guide from alpha.10 to alpha.11
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.11-to-alpha.12.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.11-to-alpha.12.md
index 517dd16d0e..0bcfca9ef6 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.11-to-alpha.12.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.11-to-alpha.12.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.11 to alpha.12 - Strapi Developer Documentation
+title: Migrate from alpha.11 to alpha.12 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.11 to alpha.12.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.11-to-alpha.12.html
---
# Migration guide from alpha.11 to alpha.12
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.1-to-alpha.12.2.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.1-to-alpha.12.2.md
index 5ce562c2c7..12afd75806 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.1-to-alpha.12.2.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.1-to-alpha.12.2.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.1 to alpha.12.2 - Strapi Developer Documentation
+title: Migrate from alpha.12.1 to alpha.12.2 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.1 to alpha.12.2.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.1-to-alpha.12.2.html
---
# Migration guide from alpha.12.1 to alpha.12.2
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.2-to-alpha.12.3.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.2-to-alpha.12.3.md
index 03a87fafd6..123744ed5d 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.2-to-alpha.12.3.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.2-to-alpha.12.3.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.2 to alpha.12.3 - Strapi Developer Documentation
+title: Migrate from alpha.12.2 to alpha.12.3 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.2 to alpha.12.3.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.2-to-alpha.12.3.html
---
# Migration guide from alpha.12.2 to alpha.12.3
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.3-to-alpha.12.4.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.3-to-alpha.12.4.md
index 66a0353157..599df7c198 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.3-to-alpha.12.4.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.3-to-alpha.12.4.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.3 to alpha.12.4 - Strapi Developer Documentation
+title: Migrate from alpha.12.3 to alpha.12.4 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.3 to alpha.12.4.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.3-to-alpha.12.4.html
---
# Migration guide from alpha.12.3 to alpha.12.4
@@ -9,7 +10,7 @@ description: Learn how you can migrate your Strapi application from alpha.12.3 t
- Add search to content manager
- Add bulk actions in content-manager
-- Add Enumeration type to Content-Types Builder
+- Add Enumeration type to Content-Type Builder
**Useful links:**
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.4-to-alpha.12.5.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.4-to-alpha.12.5.md
index 928fe001a3..435bfaff72 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.4-to-alpha.12.5.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.4-to-alpha.12.5.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.4 to alpha.12.5 - Strapi Developer Documentation
+title: Migrate from alpha.12.4 to alpha.12.5 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.4 to alpha.12.5.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.4-to-alpha.12.5.html
---
# Migration guide from alpha.12.4 to alpha.12.5
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.5-to-alpha.12.6.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.5-to-alpha.12.6.md
index ef15d58545..df74e03e2f 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.5-to-alpha.12.6.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.5-to-alpha.12.6.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.5 to alpha.12.6 - Strapi Developer Documentation
+title: Migrate from alpha.12.5 to alpha.12.6 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.5 to alpha.12.6.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.5-to-alpha.12.6.html
---
# Migration guide from alpha.12.5 to alpha.12.6
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.6-to-alpha.12.7.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.6-to-alpha.12.7.md
index f38ce4179c..6fd5a12dfa 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.6-to-alpha.12.7.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.6-to-alpha.12.7.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.6 to alpha.12.7 - Strapi Developer Documentation
+title: Migrate from alpha.12.6 to alpha.12.7 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.6 to alpha.12.7.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.6-to-alpha.12.7.html
---
# Migration guide from alpha.12.6 to alpha.12.7
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.7-to-alpha.13.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.7-to-alpha.13.md
index 329bc83e79..dafcc553ff 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.7-to-alpha.13.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.7-to-alpha.13.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.12.7 to alpha.13 - Strapi Developer Documentation
+title: Migrate from alpha.12.7 to alpha.13 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.12.7 to alpha.13.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.12.7-to-alpha.13.html
---
# Migration guide from alpha.12.7 to alpha.13
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13-to-alpha.13.1.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13-to-alpha.13.1.md
index b9376d8cce..a3cf8c3bf9 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13-to-alpha.13.1.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13-to-alpha.13.1.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.13 to alpha.13.1 - Strapi Developer Documentation
+title: Migrate from alpha.13 to alpha.13.1 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.13 to alpha.13.1.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13-to-alpha.13.1.html
---
# Migration guide from alpha.13 to alpha.13.1
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13.1-to-alpha.14.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13.1-to-alpha.14.md
index 8b46d9a1e5..29758db8cd 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13.1-to-alpha.14.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13.1-to-alpha.14.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.13.1 to alpha.14 - Strapi Developer Documentation
+title: Migrate from alpha.13.1 to alpha.14 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.13.1 to alpha.14.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.13.1-to-alpha.14.html
---
# Migration guide from alpha.13.1 to alpha.14
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14-to-alpha.14.1.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14-to-alpha.14.1.md
index 3bae0f31f9..ef37a9d174 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14-to-alpha.14.1.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14-to-alpha.14.1.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.14 to alpha.14.1 - Strapi Developer Documentation
+title: Migrate from alpha.14 to alpha.14.1 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.14 to alpha.14.1.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14-to-alpha.14.1.html
---
# Migration guide from alpha.14 to alpha.14.1
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.1-to-alpha.14.2.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.1-to-alpha.14.2.md
index 9ddb2a5c71..982bf9a17e 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.1-to-alpha.14.2.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.1-to-alpha.14.2.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.14.1 to alpha.14.2 - Strapi Developer Documentation
+title: Migrate from alpha.14.1 to alpha.14.2 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.14.1 to alpha.14.2.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.1-to-alpha.14.2.html
---
# Migration guide from alpha.14.1 to alpha.14.2
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.2-to-alpha.14.3.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.2-to-alpha.14.3.md
index 536e800b1f..7215976525 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.2-to-alpha.14.3.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.2-to-alpha.14.3.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.14.2 to alpha.14.3 - Strapi Developer Documentation
+title: Migrate from alpha.14.2 to alpha.14.3 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.14.2 to alpha.14.3.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.2-to-alpha.14.3.html
---
# Migration guide from alpha.14.2 to alpha.14.3
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.3-to-alpha.14.4.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.3-to-alpha.14.4.md
index d99dea76a5..260f20683a 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.3-to-alpha.14.4.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.3-to-alpha.14.4.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.14.3 to alpha.14.4 - Strapi Developer Documentation
+title: Migrate from alpha.14.3 to alpha.14.4 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.14.3 to alpha.14.4.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.3-to-alpha.14.4.html
---
# Migration guide from alpha.14.3 to alpha.14.4
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.4-to-alpha.14.5.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.4-to-alpha.14.5.md
index 09608b3f14..01e2b25d4c 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.4-to-alpha.14.5.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.4-to-alpha.14.5.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.14.4 to alpha.14.5 - Strapi Developer Documentation
+title: Migrate from alpha.14.4 to alpha.14.5 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.14.4 to alpha.14.5.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.4-to-alpha.14.5.html
---
# Migration guide from alpha.14.4 to alpha.14.5
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.5-to-alpha.15.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.5-to-alpha.15.md
index bbad6f9c5f..dbda3296ed 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.5-to-alpha.15.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.5-to-alpha.15.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.14.5 to alpha.15 - Strapi Developer Documentation
+title: Migrate from alpha.14.5 to alpha.15 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.14.5 to alpha.15.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.14.5-to-alpha.15.html
---
# Migration guide from alpha.14.5 to alpha.15
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.15-to-alpha.16.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.15-to-alpha.16.md
index 4c5bddd18e..6ef3e69228 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.15-to-alpha.16.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.15-to-alpha.16.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.15 to alpha.16 - Strapi Developer Documentation
+title: Migrate from alpha.15 to alpha.16 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.15 to alpha.16.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.15-to-alpha.16.html
---
# Migration guide from alpha.15 to alpha.16
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.16-to-alpha.17.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.16-to-alpha.17.md
index 610db0d879..8267426bca 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.16-to-alpha.17.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.16-to-alpha.17.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.16 to alpha.17 - Strapi Developer Documentation
+title: Migrate from alpha.16 to alpha.17 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.16 to alpha.17.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.16-to-alpha.17.html
---
# Migration guide from alpha.16 to alpha.17
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.17-to-alpha.18.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.17-to-alpha.18.md
index 74d67ffe92..b813ce23bc 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.17-to-alpha.18.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.17-to-alpha.18.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.17 to alpha.18 - Strapi Developer Documentation
+title: Migrate from alpha.17 to alpha.18 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.17 to alpha.18.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.17-to-alpha.18.html
---
# Migration guide from alpha.17 to alpha.18
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.18-to-alpha.19.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.18-to-alpha.19.md
index 4fcddd74f7..e3e113d4c1 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.18-to-alpha.19.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.18-to-alpha.19.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.18 to alpha.19 - Strapi Developer Documentation
+title: Migrate from alpha.18 to alpha.19 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.18 to alpha.19.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.18-to-alpha.19.html
---
# Migration guide from alpha.18 to alpha.19
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.19-to-alpha.20.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.19-to-alpha.20.md
index b709fe2683..dfd7edb269 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.19-to-alpha.20.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.19-to-alpha.20.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.19 to alpha.20 - Strapi Developer Documentation
+title: Migrate from alpha.19 to alpha.20 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.19 to alpha.20.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.19-to-alpha.20.html
---
# Migration guide from alpha.19 to alpha.20
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.20-to-alpha.21.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.20-to-alpha.21.md
index ad219f1f3a..3c53106b1c 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.20-to-alpha.21.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.20-to-alpha.21.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.20 to alpha.21 - Strapi Developer Documentation
+title: Migrate from alpha.20 to alpha.21 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.20 to alpha.21.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.20-to-alpha.21.html
---
# Migration guide from alpha.20 to alpha.21
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.21-to-alpha.22.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.21-to-alpha.22.md
index 27fe5e9d17..4c25625dee 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.21-to-alpha.22.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.21-to-alpha.22.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.21 to alpha.22 - Strapi Developer Documentation
+title: Migrate from alpha.21 to alpha.22 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.21 to alpha.22.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.21-to-alpha.22.html
---
# Migration guide from alpha.21 to alpha.22
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.22-to-alpha.23.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.22-to-alpha.23.md
index 6fc2825535..6ce93d081c 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.22-to-alpha.23.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.22-to-alpha.23.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.22 to alpha.23 - Strapi Developer Documentation
+title: Migrate from alpha.22 to alpha.23 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.22 to alpha.23.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.22-to-alpha.23.html
---
# Migration guide from alpha.22 to alpha.23
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.23-to-alpha.24.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.23-to-alpha.24.md
index 0cabebde2d..9bbfe6b92e 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.23-to-alpha.24.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.23-to-alpha.24.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.23 to alpha.24 - Strapi Developer Documentation
+title: Migrate from alpha.23 to alpha.24 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.23 to alpha.24.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.23-to-alpha.24.html
---
# Migration guide from alpha.23 to alpha.24
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.24-to-alpha.25.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.24-to-alpha.25.md
index 39953f86f0..3db05acc8f 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.24-to-alpha.25.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.24-to-alpha.25.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.24 to alpha.25.2 - Strapi Developer Documentation
-description: Learn how you can migrate your Strapi application from alpha.24 to alpha.25.2.
+title: Migrate from alpha.24 to alpha.25.2 - Strapi Developer Docs
+description: Learn how you can migrate your Strapi application from alpha.24 to alpha.25.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.24-to-alpha.25.html
---
# Migration guide from alpha.24 to alpha.25.2
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.25-to-alpha.26.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.25-to-alpha.26.md
index 48a53b5bfd..6f08a6c05d 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.25-to-alpha.26.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.25-to-alpha.26.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.25 to alpha.26.2s - Strapi Developer Documentation
-description: Learn how you can migrate your Strapi application from alpha.25 to alpha.26.2s.
+title: Migrate from alpha.25 to alpha.26.2s - Strapi Developer Docs
+description: Learn how you can migrate your Strapi application from alpha.25 to alpha.26.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.25-to-alpha.26.html
---
# Migration guide from alpha.25 to alpha.26.2
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.26-to-beta.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.26-to-beta.md
index aafe73bce8..7be8bef57f 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.26-to-beta.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.26-to-beta.md
@@ -1,6 +1,7 @@
---
-title: Migrate to v3.0.0-beta.x - Strapi Developer Documentation
-description: Learn how you can migrate your Strapi application to v3.0.0-beta.x.
+title: Migrate to v3.0.0-beta.x - Strapi Developer Docs
+description: Learn how you can migrate your Strapi application to from aplha.26 to beta.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.26-to-beta.html
---
# Migration Guide
@@ -545,7 +546,7 @@ The only difference is that the admin of a local plugin is ignored for the momen
In the `beta`, we are introducing the `Core API`, which is replacing the templates that were generated before.
Now when you create a new model your `controller` and `service` will be empty modules and will be used to override the default behaviors.
-Read more about [controllers](/developer-docs/latest/development/backend-customization.md#controllers) or [services](/developer-docs/latest/development/backend-customization.md#services)
+Read more about [controllers](/developer-docs/latest/development/backend-customization/controllers.md) or [services](/developer-docs/latest/development/backend-customization/services.md)
To migrate, you will only have to delete the methods you haven't modified or created from your `controllers` and `services`
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.7.4-to-alpha.8.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.7.4-to-alpha.8.md
index d606768ce6..26d40d7145 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.7.4-to-alpha.8.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.7.4-to-alpha.8.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.7.4 to alpha.8 - Strapi Developer Documentation
+title: Migrate from alpha.7.4 to alpha.8 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.7.4 to alpha.8.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.7.4-to-alpha.8.html
---
# Migration guide from alpha.7.4 to alpha.8
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.8-to-alpha.9.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.8-to-alpha.9.md
index fb1f668e9d..c9ebcccae7 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.8-to-alpha.9.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.8-to-alpha.9.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.8 to alpha.9 - Strapi Developer Documentation
+title: Migrate from alpha.8 to alpha.9 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.8 to alpha.9.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.8-to-alpha.9.html
---
# Migration guide from alpha.8 to alpha.9
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.9-to-alpha.10.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.9-to-alpha.10.md
index c159e5826c..df96465a28 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.9-to-alpha.10.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.9-to-alpha.10.md
@@ -1,6 +1,7 @@
---
-title: Migrate from alpha.9 to alpha.10 - Strapi Developer Documentation
+title: Migrate from alpha.9 to alpha.10 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from alpha.9 to alpha.10.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-alpha.9-to-alpha.10.html
---
# Migration guide from alpha.9 to alpha.10
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.15-to-beta.16.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.15-to-beta.16.md
index 73dd248287..a32fd7881b 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.15-to-beta.16.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.15-to-beta.16.md
@@ -1,6 +1,7 @@
---
-title: Migrate from beta.15 to beta.16 - Strapi Developer Documentation
+title: Migrate from beta.15 to beta.16 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from beta.15 to beta.16.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.15-to-beta.16.html
---
# Migration guide from beta.15 to beta.16
@@ -95,7 +96,7 @@ To make sure a Wysiwyg field stays the same when deploying, we introduced the `r
### Custom controllers and services
-If you are using [core services](/developer-docs/latest/development/backend-customization.md#services), you previously needed to call `result.toJSON()` or `result.toObject()` to get a plain javascript object. This is not the case anymore, you will now receive a simple object directly.
+If you are using [core services](/developer-docs/latest/development/backend-customization/services.md), you previously needed to call `result.toJSON()` or `result.toObject()` to get a plain javascript object. This is not the case anymore, you will now receive a simple object directly.
**Before**:
@@ -118,9 +119,9 @@ module.exports = {
};
```
-The same modification was made to `strapi.query()`. Read more about **Queries** [here](/developer-docs/latest/development/backend-customization.md#queries).
+The same modification was made to `strapi.query()`.
-Keep in mind that if you are running custom ORM queries with Bookshelf or Mongoose you will still have to call `toJSON` or `toObject`. Check out this section about [custom queries](/developer-docs/latest/development/backend-customization.md#api-reference).
+Keep in mind that if you are running custom ORM queries with Bookshelf or Mongoose you will still have to call `toJSON` or `toObject`.
### Bootstrap function
@@ -172,7 +173,7 @@ module.exports = () => {};
### Custom hooks
-If you have custom [hooks](/developer-docs/latest/setup-deployment-guides/configurations.md#hooks) in your project, the `initialize` function will not receive a callback anymore. You can either use an async function, return a promise or simply run a synchronous function.
+If you have custom hooks in your project, the `initialize` function will not receive a callback anymore. You can either use an async function, return a promise or simply run a synchronous function.
**Before**
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.16-to-beta.17.4.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.16-to-beta.17.4.md
index 8338b1a82d..f322b0bdb9 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.16-to-beta.17.4.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.16-to-beta.17.4.md
@@ -1,6 +1,7 @@
---
-title: Migrate to beta.17.4 - Strapi Developer Documentation
+title: Migrate to beta.17.4 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application to beta.17.4.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.16-to-beta.17.4.html
---
# Migration guide from beta.16.8 through beta.17.3 to beta.17.4
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.17-to-beta.18.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.17-to-beta.18.md
index b8d560d82e..bc9abc7c99 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.17-to-beta.18.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.17-to-beta.18.md
@@ -1,6 +1,7 @@
---
-title: Migrate to beta.18 - Strapi Developer Documentation
+title: Migrate to beta.18 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application to beta.18.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.17-to-beta.18.html
---
# Migration guide from beta.17.4 through beta.17.8 to beta.18
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.18-to-beta.19.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.18-to-beta.19.md
index 1faa25d8b3..de9c1fa325 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.18-to-beta.19.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.18-to-beta.19.md
@@ -1,6 +1,7 @@
---
-title: Migrate from beta.18.x to beta.19 - Strapi Developer Documentation
+title: Migrate from beta.18.x to beta.19 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from beta.18.x to beta.19.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.18-to-beta.19.html
---
# Migration guide from beta.18.x to beta.19
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.19.4.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.19.4.md
index b7a0e3d6b2..934cef259d 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.19.4.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.19.4.md
@@ -1,6 +1,7 @@
---
-title: Migrate from beta.19.x to beta.19.4 - Strapi Developer Documentation
+title: Migrate from beta.19.x to beta.19.4 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from beta.19.x to beta.19.4.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.19.4.html
---
# Migration guide from beta.19.x to beta.19.4
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.20.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.20.md
index 33e8462a15..a7ccee6b14 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.20.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.20.md
@@ -1,6 +1,7 @@
---
-title: Migrate from beta.19.x to beta.20 - Strapi Developer Documentation
+title: Migrate from beta.19.x to beta.20 - Strapi Developer Docs
description: Learn how you can migrate your Strapi application from beta.19.x to beta.20.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.19-to-beta.20.html
---
# Migration guide from beta.19.x to beta.20
@@ -49,7 +50,7 @@ You can now also disable this behavior with the `public.defaultIndex` option. Re
A lot of our users have been requesting that we move some back-end specific configurations to files. While implementing the media library feature, we decided to move the upload plugin settings to files.
-This means that you now have to configure your provider directly in the files. You can read the documentation [here](/developer-docs/latest/development/plugins/upload.md#using-a-provider) to update.
+This means that you now have to configure your provider directly in the files. You can read the documentation [here](/developer-docs/latest/plugins/upload.md#using-a-provider) to update.
## MongoDB Media relation changes
diff --git a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.20-to-3.0.0.md b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.20-to-3.0.0.md
index 3b19584694..6ac78cbca7 100644
--- a/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.20-to-3.0.0.md
+++ b/docs/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.20-to-3.0.0.md
@@ -1,6 +1,7 @@
---
-title: Migrate from 3.0.0-beta.20 to 3.0.0 - Strapi Developer Documentation
-description: Learn how you can migrate your Strapi application from 3.0.0-beta.20 to 3.0.0.
+title: Migrate from 3.0.0-beta.20 to 3.0.0 - Strapi Developer Docs
+description: Learn how you can migrate your Strapi application from beta.20 to 3.0.0.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/migration-guide-beta.20-to-3.0.0.html
---
# Migration guide from 3.0.0-beta.20 to 3.0.0
@@ -51,11 +52,11 @@ Before migrating, you should first read the new [configuration documentation](/d
#### Server
-Your server configuration should move from `./config/environments/{env}/server.json` to `./config/server.js` like shown [here](/developer-docs/latest/setup-deployment-guides/configurations.md#server).
+Your server configuration should move from `./config/environments/{env}/server.json` to `./config/server.js` like shown [here](/developer-docs/latest/setup-deployment-guides/configurations/required/server.md).
#### Database configuration
-Your database configuration should move from `./config/environments/{env}/database.json` to `./config/database.js` like shown [here](/developer-docs/latest/setup-deployment-guides/configurations.md#database).
+Your database configuration should move from `./config/environments/{env}/database.json` to `./config/database.js` like shown [here](/developer-docs/latest/setup-deployment-guides/configurations/required/databases.md).
#### Middlewares
@@ -94,9 +95,7 @@ module.exports = {
You can now move the middleware configurations from `application.json`, `language.json`, `security.json`, `request.json` and `response.json` files directly into the `settings` property.
-You can review all possible options in the [middleware documentation](/developer-docs/latest/setup-deployment-guides/configurations.md#configuration-and-activation-2).
-
-
+You can review all possible options in the [middleware documentation](/developer-docs/latest/setup-deployment-guides/deployment.md#application-configuration).
::: tip
If you never configured any middlewares you can delete this file all together. You can also only set the configurations you want to customize and leave the others out.
@@ -236,13 +235,13 @@ config
We have replaced the old lifecycles that had a lot of issues with a new simpler lifecycle layer.
-You can read more [here](/developer-docs/latest/development/backend-customization.md#lifecycle-hooks).
+You can read more [here](/developer-docs/latest/development/backend-customization/models.md#lifecycle-hooks).
## Email plugin settings
Email plugin settings have been moved to files. Now you can configure your email provider directly in files.
-You can read the documentation [here](/developer-docs/latest/development/plugins/email.md#configure-the-plugin) to update.
+You can read the documentation [here](/developer-docs/latest/plugins/email.md#configure-the-plugin) to update.
Once you have setup your configuration, you can cleanup your database by deleting in the `core_store` model the data with the `key` equal to `plugin_email_provider`.
diff --git a/docs/developer-docs/latest/update-migration-guides/update-version.md b/docs/developer-docs/latest/update-migration-guides/update-version.md
index 0d23a08d68..c2cd5d91ac 100644
--- a/docs/developer-docs/latest/update-migration-guides/update-version.md
+++ b/docs/developer-docs/latest/update-migration-guides/update-version.md
@@ -1,48 +1,43 @@
---
-title: Update Strapi version - Strapi Developer Documentation
+title: Update Strapi version - Strapi Developer Docs
description: The following documentation covers how to upgrade your application to the latest version of Strapi.
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/update-migration-guides/update-version.html
---
# Update Strapi version
In this guide you will learn how to upgrade your application to the latest version of Strapi.
-::: tip NOTE
+:::note
When a new version of Strapi is available, you will be notified both in your terminal, and in the admin panel.
-Also note that you can check the **Settings > Application** section of the admin panel to have more information on:
+Also note that you can check the **Settings > Global settings - Application** section of the admin panel to have more information on:
- The versions of Strapi and Node you are currently using.
- If relevant, the versions we recommend you to upgrade to.
:::
-::: warning CAUTION
+:::caution
Before you start, make sure your server is not running until the end of the guide!
:::
## Upgrade your dependencies
Start by upgrading all your Strapi packages in your `package.json`.
-For example upgrading from `3.4.4` to `3.6.1`:
+For example upgrading from `4.0.0` to `4.0.1`:
-:::: tabs
+:::: tabs card
-::: tab 3.4.4
+::: tab 4.0.0
```json
{
//...
"dependencies": {
- "strapi": "3.4.4",
- "strapi-admin": "3.4.4",
- "strapi-connector-bookshelf": "3.4.4",
- "strapi-plugin-content-manager": "3.4.4",
- "strapi-plugin-content-type-builder": "3.4.4",
- "strapi-plugin-email": "3.4.4",
- "strapi-plugin-graphql": "3.4.4",
- "strapi-plugin-upload": "3.4.4",
- "strapi-plugin-users-permissions": "3.4.4",
- "strapi-utils": "3.4.4"
+ "@strapi/plugin-documentation": "4.0.0",
+ "@strapi/plugin-i18n": "4.0.0",
+ "@strapi/plugin-users-permissions": "4.0.0",
+ "@strapi/strapi": "4.0.0"
//...
}
}
@@ -50,22 +45,16 @@ For example upgrading from `3.4.4` to `3.6.1`:
:::
-::: tab 3.6.1
+::: tab 4.0.1
```json
{
//...
"dependencies": {
- "strapi": "3.6.1",
- "strapi-admin": "3.6.1",
- "strapi-connector-bookshelf": "3.6.1",
- "strapi-plugin-content-manager": "3.6.1",
- "strapi-plugin-content-type-builder": "3.6.1",
- "strapi-plugin-email": "3.6.1",
- "strapi-plugin-graphql": "3.6.1",
- "strapi-plugin-upload": "3.6.1",
- "strapi-plugin-users-permissions": "3.6.1",
- "strapi-utils": "3.6.1"
+ "@strapi/plugin-documentation": "4.0.1",
+ "@strapi/plugin-i18n": "4.0.1",
+ "@strapi/plugin-users-permissions": "4.0.1",
+ "@strapi/strapi": "4.0.1"
//...
}
}
@@ -78,7 +67,7 @@ For example upgrading from `3.4.4` to `3.6.1`:
After editing the file run either `yarn install` or `npm install` to install the specified version.
::: tip
-If the operation doesn't work, try removing your `yarn.lock` or `package-lock.json`. If that doesn't help, remove the `node_modules` folder as well and try again..
+If the operation doesn't work, try removing your `yarn.lock` or `package-lock.json`. If that doesn't help, remove the `node_modules` folder as well and try again..
:::
## Rebuild your administration panel
@@ -86,15 +75,25 @@ If the operation doesn't work, try removing your `yarn.lock` or `package-lock.js
New releases can introduce changes to the administration panel that require a rebuild.
Rebuild the admin panel with one of the following commands:
-```bash
-yarn build --clean
-# or
+
+
+
+```sh
npm run build -- --clean
```
+
+
+
+```sh
+yarn build --clean
+```
+
+
+
## Extensions
-If you are using [extensions](/developer-docs/latest/development/plugin-customization.md) to create custom code or modify existing code, you will need to update your code and compare your version to the new changes on the repository. Not updating your extensions can **break your app** in unexpected ways we cannot predict.
+If you are using [extensions](/developer-docs/latest/development/plugins-extension.md) to create custom code or modify existing code, you will need to update your code and compare your version to the new changes on the repository. Not updating your extensions can **break your app** in unexpected ways we cannot predict.
## Migration guides
@@ -106,10 +105,20 @@ Just make sure when you update your version that a migration guide exists or not
If you have followed the information above, you can start your application with:
-```bash
-yarn develop
-# or
+
+
+
+```sh
npm run develop
```
+
+
+
+```sh
+yarn develop
+```
+
+
+
🎉 Congrats, your application has been migrated!
diff --git a/docs/package.json b/docs/package.json
index 8bc8a0f823..8e0f8191ea 100644
--- a/docs/package.json
+++ b/docs/package.json
@@ -10,8 +10,9 @@
},
"license": "SEE LICENSE IN LICENSE",
"dependencies": {
- "@vuepress/plugin-medium-zoom": "^1.7.1",
- "vuepress": "^1.7.1",
+ "@vuepress/plugin-medium-zoom": "^1.8.2",
+ "markdown-it-include": "^2.0.0",
+ "vuepress": "^1.8.2",
"vuepress-plugin-code-copy": "^1.0.6",
"vuepress-plugin-element-tabs": "^0.2.8",
"vuepress-plugin-font-awesome": "1.90.6",
@@ -19,7 +20,8 @@
},
"devDependencies": {
"@vuepress/plugin-back-to-top": "^1.8.2",
- "vuepress-plugin-check-md": "^0.0.2"
+ "vuepress-plugin-check-md": "^0.0.2",
+ "vuepress-plugin-container": "^2.1.5"
},
"author": {
"email": "hi@strapi.io",
diff --git a/docs/user-docs/latest/assets/content-manager/RF_multiple-choices.png b/docs/user-docs/latest/assets/content-manager/RF_multiple-choices.png
index 52f7252092..e806c05edf 100644
Binary files a/docs/user-docs/latest/assets/content-manager/RF_multiple-choices.png and b/docs/user-docs/latest/assets/content-manager/RF_multiple-choices.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/RF_one-choice.png b/docs/user-docs/latest/assets/content-manager/RF_one-choice.png
index de91b2772a..90f49a2e96 100644
Binary files a/docs/user-docs/latest/assets/content-manager/RF_one-choice.png and b/docs/user-docs/latest/assets/content-manager/RF_one-choice.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/content-manager_displayed-fields.png b/docs/user-docs/latest/assets/content-manager/content-manager_displayed-fields.png
index 289faf67d4..3336af1c20 100644
Binary files a/docs/user-docs/latest/assets/content-manager/content-manager_displayed-fields.png and b/docs/user-docs/latest/assets/content-manager/content-manager_displayed-fields.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/content-manager_filters.png b/docs/user-docs/latest/assets/content-manager/content-manager_filters.png
index 26a2445ccd..ac90a06ef3 100644
Binary files a/docs/user-docs/latest/assets/content-manager/content-manager_filters.png and b/docs/user-docs/latest/assets/content-manager/content-manager_filters.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/content-manager_list-view.png b/docs/user-docs/latest/assets/content-manager/content-manager_list-view.png
index 67f62e8526..66f0ac3082 100644
Binary files a/docs/user-docs/latest/assets/content-manager/content-manager_list-view.png and b/docs/user-docs/latest/assets/content-manager/content-manager_list-view.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/content-manager_settings-list-view.png b/docs/user-docs/latest/assets/content-manager/content-manager_settings-list-view.png
index b1d2ee6849..180aeff26c 100644
Binary files a/docs/user-docs/latest/assets/content-manager/content-manager_settings-list-view.png and b/docs/user-docs/latest/assets/content-manager/content-manager_settings-list-view.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/content-manager_single-type.png b/docs/user-docs/latest/assets/content-manager/content-manager_single-type.png
index 843efaa0e6..45c3738b39 100644
Binary files a/docs/user-docs/latest/assets/content-manager/content-manager_single-type.png and b/docs/user-docs/latest/assets/content-manager/content-manager_single-type.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/content-manager_translate.png b/docs/user-docs/latest/assets/content-manager/content-manager_translate.png
index d26d7952a7..a8953b0472 100644
Binary files a/docs/user-docs/latest/assets/content-manager/content-manager_translate.png and b/docs/user-docs/latest/assets/content-manager/content-manager_translate.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view-config.png b/docs/user-docs/latest/assets/content-manager/edit-view-config.png
index ddc1da3ce5..8121d5adc5 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view-config.png and b/docs/user-docs/latest/assets/content-manager/edit-view-config.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view.png b/docs/user-docs/latest/assets/content-manager/edit-view.png
index 677c980ed6..cba414faa3 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view.png and b/docs/user-docs/latest/assets/content-manager/edit-view.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view_component2.png b/docs/user-docs/latest/assets/content-manager/edit-view_component2.png
index 5f31cedc66..c5e4b2d7d3 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view_component2.png and b/docs/user-docs/latest/assets/content-manager/edit-view_component2.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view_component3.png b/docs/user-docs/latest/assets/content-manager/edit-view_component3.png
index db5207d27c..8bd8fe477d 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view_component3.png and b/docs/user-docs/latest/assets/content-manager/edit-view_component3.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view_component4.png b/docs/user-docs/latest/assets/content-manager/edit-view_component4.png
index 4777da5767..6d72ebd6d7 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view_component4.png and b/docs/user-docs/latest/assets/content-manager/edit-view_component4.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone1.png b/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone1.png
index 638d2f08fc..bbe6b46f1f 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone1.png and b/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone1.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone3.png b/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone3.png
index bee68a65c3..dcb9df73c3 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone3.png and b/docs/user-docs/latest/assets/content-manager/edit-view_dynamic-zone3.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/edit-view_relational-fields.png b/docs/user-docs/latest/assets/content-manager/edit-view_relational-fields.png
index 5099dea70d..bb81712ead 100644
Binary files a/docs/user-docs/latest/assets/content-manager/edit-view_relational-fields.png and b/docs/user-docs/latest/assets/content-manager/edit-view_relational-fields.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/editing_draft_version.png b/docs/user-docs/latest/assets/content-manager/editing_draft_version.png
index 93e95b864d..d7463d7cef 100644
Binary files a/docs/user-docs/latest/assets/content-manager/editing_draft_version.png and b/docs/user-docs/latest/assets/content-manager/editing_draft_version.png differ
diff --git a/docs/user-docs/latest/assets/content-manager/editing_published_version.png b/docs/user-docs/latest/assets/content-manager/editing_published_version.png
index 0e1308dfe2..cc130313f9 100644
Binary files a/docs/user-docs/latest/assets/content-manager/editing_published_version.png and b/docs/user-docs/latest/assets/content-manager/editing_published_version.png differ
diff --git a/docs/user-docs/latest/assets/content-types-builder/component-creation.png b/docs/user-docs/latest/assets/content-types-builder/component-creation.png
index e50c2e1d6a..5658b44cfa 100644
Binary files a/docs/user-docs/latest/assets/content-types-builder/component-creation.png and b/docs/user-docs/latest/assets/content-types-builder/component-creation.png differ
diff --git a/docs/user-docs/latest/assets/content-types-builder/content-type-creation.png b/docs/user-docs/latest/assets/content-types-builder/content-type-creation.png
index d9a677311a..5ea748cea3 100644
Binary files a/docs/user-docs/latest/assets/content-types-builder/content-type-creation.png and b/docs/user-docs/latest/assets/content-types-builder/content-type-creation.png differ
diff --git a/docs/user-docs/latest/assets/content-types-builder/content-types-builder.png b/docs/user-docs/latest/assets/content-types-builder/content-types-builder.png
index 5f6279dc3e..9ba8e05088 100644
Binary files a/docs/user-docs/latest/assets/content-types-builder/content-types-builder.png and b/docs/user-docs/latest/assets/content-types-builder/content-types-builder.png differ
diff --git a/docs/user-docs/latest/assets/content-types-builder/content-types-builder_edition.png b/docs/user-docs/latest/assets/content-types-builder/content-types-builder_edition.png
index a10cca7445..4f25e5dbaf 100644
Binary files a/docs/user-docs/latest/assets/content-types-builder/content-types-builder_edition.png and b/docs/user-docs/latest/assets/content-types-builder/content-types-builder_edition.png differ
diff --git a/docs/user-docs/latest/assets/content-types-builder/fields-selection.png b/docs/user-docs/latest/assets/content-types-builder/fields-selection.png
index 71fb768487..6d8b4ca52f 100644
Binary files a/docs/user-docs/latest/assets/content-types-builder/fields-selection.png and b/docs/user-docs/latest/assets/content-types-builder/fields-selection.png differ
diff --git a/docs/user-docs/latest/assets/getting-started/admin-panel-homepage.png b/docs/user-docs/latest/assets/getting-started/admin-panel-homepage.png
index 95b3ac7bba..9db137cded 100644
Binary files a/docs/user-docs/latest/assets/getting-started/admin-panel-homepage.png and b/docs/user-docs/latest/assets/getting-started/admin-panel-homepage.png differ
diff --git a/docs/user-docs/latest/assets/getting-started/login-page-sso.png b/docs/user-docs/latest/assets/getting-started/login-page-sso.png
index 8958e4026b..3b32c3eac2 100644
Binary files a/docs/user-docs/latest/assets/getting-started/login-page-sso.png and b/docs/user-docs/latest/assets/getting-started/login-page-sso.png differ
diff --git a/docs/user-docs/latest/assets/getting-started/user-information-profile.png b/docs/user-docs/latest/assets/getting-started/user-information-profile.png
index 3ffa7a296c..5c22de430b 100644
Binary files a/docs/user-docs/latest/assets/getting-started/user-information-profile.png and b/docs/user-docs/latest/assets/getting-started/user-information-profile.png differ
diff --git a/docs/user-docs/latest/assets/icons/add_circle.svg b/docs/user-docs/latest/assets/icons/add_circle.svg
new file mode 100644
index 0000000000..e7b5a4c3da
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/add_circle.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/add_icon.svg b/docs/user-docs/latest/assets/icons/add_icon.svg
new file mode 100644
index 0000000000..9c1ab02534
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/add_icon.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/after.svg b/docs/user-docs/latest/assets/icons/after.svg
new file mode 100644
index 0000000000..fcd6b418eb
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/after.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/api_tokens.svg b/docs/user-docs/latest/assets/icons/api_tokens.svg
new file mode 100644
index 0000000000..d414992f6c
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/api_tokens.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/application.svg b/docs/user-docs/latest/assets/icons/application.svg
new file mode 100644
index 0000000000..7232a42ff9
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/application.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/back.svg b/docs/user-docs/latest/assets/icons/back.svg
new file mode 100644
index 0000000000..d43d6b7174
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/back.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/carret.svg b/docs/user-docs/latest/assets/icons/carret.svg
new file mode 100644
index 0000000000..72da913973
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/carret.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/check_icon.svg b/docs/user-docs/latest/assets/icons/check_icon.svg
new file mode 100644
index 0000000000..5c105633b7
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/check_icon.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/clear.svg b/docs/user-docs/latest/assets/icons/clear.svg
new file mode 100644
index 0000000000..8b22e988f2
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/clear.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/close-icon.svg b/docs/user-docs/latest/assets/icons/close-icon.svg
new file mode 100644
index 0000000000..6c3850817d
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/close-icon.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/cog.svg b/docs/user-docs/latest/assets/icons/cog.svg
new file mode 100644
index 0000000000..7cb76d46b7
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/cog.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/content.svg b/docs/user-docs/latest/assets/icons/content.svg
new file mode 100644
index 0000000000..8a0a129bd2
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/content.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/content_manager.svg b/docs/user-docs/latest/assets/icons/content_manager.svg
new file mode 100644
index 0000000000..4a751c4fe3
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/content_manager.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/content_types_builder.svg b/docs/user-docs/latest/assets/icons/content_types_builder.svg
new file mode 100644
index 0000000000..dafef5a82f
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/content_types_builder.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/cross.svg b/docs/user-docs/latest/assets/icons/cross.svg
new file mode 100644
index 0000000000..efa48452fc
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/cross.svg
@@ -0,0 +1,10 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_boolean.svg b/docs/user-docs/latest/assets/icons/ctb_boolean.svg
new file mode 100644
index 0000000000..9b2db57a1c
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_boolean.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_component.svg b/docs/user-docs/latest/assets/icons/ctb_component.svg
new file mode 100644
index 0000000000..a37ee85d12
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_component.svg
@@ -0,0 +1,5 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_date.svg b/docs/user-docs/latest/assets/icons/ctb_date.svg
new file mode 100644
index 0000000000..5f2063dbc7
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_date.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_dz.svg b/docs/user-docs/latest/assets/icons/ctb_dz.svg
new file mode 100644
index 0000000000..727aea4fb8
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_dz.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_email.svg b/docs/user-docs/latest/assets/icons/ctb_email.svg
new file mode 100644
index 0000000000..397a7baa9e
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_email.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_enum.svg b/docs/user-docs/latest/assets/icons/ctb_enum.svg
new file mode 100644
index 0000000000..f8bee96767
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_enum.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_json.svg b/docs/user-docs/latest/assets/icons/ctb_json.svg
new file mode 100644
index 0000000000..245af20aff
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_json.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_media.svg b/docs/user-docs/latest/assets/icons/ctb_media.svg
new file mode 100644
index 0000000000..f9a85015bd
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_media.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_number.svg b/docs/user-docs/latest/assets/icons/ctb_number.svg
new file mode 100644
index 0000000000..7dd2500de0
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_number.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_password.svg b/docs/user-docs/latest/assets/icons/ctb_password.svg
new file mode 100644
index 0000000000..99fd806bb7
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_password.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation.svg b/docs/user-docs/latest/assets/icons/ctb_relation.svg
new file mode 100644
index 0000000000..bb361c4943
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation_1to1.svg b/docs/user-docs/latest/assets/icons/ctb_relation_1to1.svg
new file mode 100644
index 0000000000..751bd0755e
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation_1to1.svg
@@ -0,0 +1,5 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation_1tomany.svg b/docs/user-docs/latest/assets/icons/ctb_relation_1tomany.svg
new file mode 100644
index 0000000000..8d5ad7ae98
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation_1tomany.svg
@@ -0,0 +1,9 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation_manyto1.svg b/docs/user-docs/latest/assets/icons/ctb_relation_manyto1.svg
new file mode 100644
index 0000000000..82b12ae97f
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation_manyto1.svg
@@ -0,0 +1,9 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation_manytomany.svg b/docs/user-docs/latest/assets/icons/ctb_relation_manytomany.svg
new file mode 100644
index 0000000000..f6c3359f1f
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation_manytomany.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation_manyway.svg b/docs/user-docs/latest/assets/icons/ctb_relation_manyway.svg
new file mode 100644
index 0000000000..b78900c2a8
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation_manyway.svg
@@ -0,0 +1,9 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_relation_oneway.svg b/docs/user-docs/latest/assets/icons/ctb_relation_oneway.svg
new file mode 100644
index 0000000000..ac59fcfdf7
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_relation_oneway.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_richtext.svg b/docs/user-docs/latest/assets/icons/ctb_richtext.svg
new file mode 100644
index 0000000000..9ada8bc22a
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_richtext.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_text.svg b/docs/user-docs/latest/assets/icons/ctb_text.svg
new file mode 100644
index 0000000000..b3763d9839
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_text.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/ctb_uid.svg b/docs/user-docs/latest/assets/icons/ctb_uid.svg
new file mode 100644
index 0000000000..704601bf2f
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/ctb_uid.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/delete.svg b/docs/user-docs/latest/assets/icons/delete.svg
new file mode 100644
index 0000000000..3a72728102
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/delete.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/documentation.svg b/docs/user-docs/latest/assets/icons/documentation.svg
new file mode 100644
index 0000000000..7141d6ddf2
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/documentation.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/down.svg b/docs/user-docs/latest/assets/icons/down.svg
new file mode 100644
index 0000000000..5c86d71b22
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/down.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/down2.svg b/docs/user-docs/latest/assets/icons/down2.svg
new file mode 100644
index 0000000000..c0258602f5
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/down2.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/drag.svg b/docs/user-docs/latest/assets/icons/drag.svg
new file mode 100644
index 0000000000..6a242929df
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/drag.svg
@@ -0,0 +1,14 @@
+
diff --git a/docs/user-docs/latest/assets/icons/duplicate.svg b/docs/user-docs/latest/assets/icons/duplicate.svg
new file mode 100644
index 0000000000..9f6de21e02
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/duplicate.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/edit.svg b/docs/user-docs/latest/assets/icons/edit.svg
new file mode 100644
index 0000000000..0c5a93106a
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/edit.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/email_template.svg b/docs/user-docs/latest/assets/icons/email_template.svg
new file mode 100644
index 0000000000..4b04c60e66
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/email_template.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/external_link.svg b/docs/user-docs/latest/assets/icons/external_link.svg
new file mode 100644
index 0000000000..f1ecce968d
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/external_link.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/globe.svg b/docs/user-docs/latest/assets/icons/globe.svg
new file mode 100644
index 0000000000..0eda5dce15
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/globe.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/image.svg b/docs/user-docs/latest/assets/icons/image.svg
new file mode 100644
index 0000000000..e61c6fe72c
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/image.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/lock.svg b/docs/user-docs/latest/assets/icons/lock.svg
new file mode 100644
index 0000000000..83accc01c5
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/lock.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/marketplace.svg b/docs/user-docs/latest/assets/icons/marketplace.svg
new file mode 100644
index 0000000000..6bed4271c3
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/marketplace.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/media_library.svg b/docs/user-docs/latest/assets/icons/media_library.svg
new file mode 100644
index 0000000000..9d1d8a2361
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/media_library.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/minus.svg b/docs/user-docs/latest/assets/icons/minus.svg
new file mode 100644
index 0000000000..c12b5d00ab
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/minus.svg
@@ -0,0 +1,4 @@
+
diff --git a/docs/user-docs/latest/assets/icons/plugins.svg b/docs/user-docs/latest/assets/icons/plugins.svg
new file mode 100644
index 0000000000..a0cc58cb62
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/plugins.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/provider.svg b/docs/user-docs/latest/assets/icons/provider.svg
new file mode 100644
index 0000000000..f433962399
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/provider.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/roles.svg b/docs/user-docs/latest/assets/icons/roles.svg
new file mode 100644
index 0000000000..0f28293cdb
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/roles.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/roles_permissions.svg b/docs/user-docs/latest/assets/icons/roles_permissions.svg
new file mode 100644
index 0000000000..d3be232726
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/roles_permissions.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/search.svg b/docs/user-docs/latest/assets/icons/search.svg
new file mode 100644
index 0000000000..6853306f9e
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/search.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/settings.svg b/docs/user-docs/latest/assets/icons/settings.svg
new file mode 100644
index 0000000000..cb76e89f86
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/settings.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/up.svg b/docs/user-docs/latest/assets/icons/up.svg
new file mode 100644
index 0000000000..9cf952ad85
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/up.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/up2.svg b/docs/user-docs/latest/assets/icons/up2.svg
new file mode 100644
index 0000000000..c00010aaf4
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/up2.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/users.svg b/docs/user-docs/latest/assets/icons/users.svg
new file mode 100644
index 0000000000..57e9d7bf69
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/users.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/webhooks.svg b/docs/user-docs/latest/assets/icons/webhooks.svg
new file mode 100644
index 0000000000..f535b271c0
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/webhooks.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/user-docs/latest/assets/icons/world.svg b/docs/user-docs/latest/assets/icons/world.svg
new file mode 100644
index 0000000000..6b81d63010
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/world.svg
@@ -0,0 +1,9 @@
+
diff --git a/docs/user-docs/latest/assets/icons/world_striked.svg b/docs/user-docs/latest/assets/icons/world_striked.svg
new file mode 100644
index 0000000000..20a574307b
--- /dev/null
+++ b/docs/user-docs/latest/assets/icons/world_striked.svg
@@ -0,0 +1,10 @@
+
diff --git a/docs/user-docs/latest/assets/plugins/plugins-settings.png b/docs/user-docs/latest/assets/plugins/plugins-settings.png
index a85059926d..ad64ed21fa 100644
Binary files a/docs/user-docs/latest/assets/plugins/plugins-settings.png and b/docs/user-docs/latest/assets/plugins/plugins-settings.png differ
diff --git a/docs/user-docs/latest/assets/settings/settings-i18n.png b/docs/user-docs/latest/assets/settings/settings-i18n.png
index d6d5362fcb..185bbd22ea 100644
Binary files a/docs/user-docs/latest/assets/settings/settings-i18n.png and b/docs/user-docs/latest/assets/settings/settings-i18n.png differ
diff --git a/docs/user-docs/latest/assets/settings/settings-sso.png b/docs/user-docs/latest/assets/settings/settings-sso.png
index c12eb9c816..9dc6583f68 100644
Binary files a/docs/user-docs/latest/assets/settings/settings-sso.png and b/docs/user-docs/latest/assets/settings/settings-sso.png differ
diff --git a/docs/user-docs/latest/assets/settings/settings_api-token.png b/docs/user-docs/latest/assets/settings/settings_api-token.png
new file mode 100644
index 0000000000..a74991caa5
Binary files /dev/null and b/docs/user-docs/latest/assets/settings/settings_api-token.png differ
diff --git a/docs/user-docs/latest/assets/settings/up_email-templates.png b/docs/user-docs/latest/assets/settings/up_email-templates.png
index 612d0affd0..9d5306303a 100644
Binary files a/docs/user-docs/latest/assets/settings/up_email-templates.png and b/docs/user-docs/latest/assets/settings/up_email-templates.png differ
diff --git a/docs/user-docs/latest/assets/settings/up_providers.png b/docs/user-docs/latest/assets/settings/up_providers.png
index fe20c64dbf..25a756bdb7 100644
Binary files a/docs/user-docs/latest/assets/settings/up_providers.png and b/docs/user-docs/latest/assets/settings/up_providers.png differ
diff --git a/docs/user-docs/latest/assets/settings/up_settings.png b/docs/user-docs/latest/assets/settings/up_settings.png
index 9c281400fd..c225b96d6a 100644
Binary files a/docs/user-docs/latest/assets/settings/up_settings.png and b/docs/user-docs/latest/assets/settings/up_settings.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/administrator_custom-conditions.png b/docs/user-docs/latest/assets/users-permissions/administrator_custom-conditions.png
index 942690694d..93af8f0e2a 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/administrator_custom-conditions.png and b/docs/user-docs/latest/assets/users-permissions/administrator_custom-conditions.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/administrator_edit-info.png b/docs/user-docs/latest/assets/users-permissions/administrator_edit-info.png
index 6afc0f15e6..bb7fedabf9 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/administrator_edit-info.png and b/docs/user-docs/latest/assets/users-permissions/administrator_edit-info.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/administrator_list-view.png b/docs/user-docs/latest/assets/users-permissions/administrator_list-view.png
index dc7cff73b3..f41753c66d 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/administrator_list-view.png and b/docs/user-docs/latest/assets/users-permissions/administrator_list-view.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/administrator_roles-edition.png b/docs/user-docs/latest/assets/users-permissions/administrator_roles-edition.png
index 4850a06f5f..66810de174 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/administrator_roles-edition.png and b/docs/user-docs/latest/assets/users-permissions/administrator_roles-edition.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/administrator_roles.png b/docs/user-docs/latest/assets/users-permissions/administrator_roles.png
index 5cbb0f5e51..285e632d48 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/administrator_roles.png and b/docs/user-docs/latest/assets/users-permissions/administrator_roles.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/end-user_content-manager.png b/docs/user-docs/latest/assets/users-permissions/end-user_content-manager.png
index 5ea5856f02..09ce0fd743 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/end-user_content-manager.png and b/docs/user-docs/latest/assets/users-permissions/end-user_content-manager.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/end-user_roles-config.png b/docs/user-docs/latest/assets/users-permissions/end-user_roles-config.png
index 4954ca1dd5..304f37a5ba 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/end-user_roles-config.png and b/docs/user-docs/latest/assets/users-permissions/end-user_roles-config.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/end-user_roles.png b/docs/user-docs/latest/assets/users-permissions/end-user_roles.png
index f83146d16b..291e60303b 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/end-user_roles.png and b/docs/user-docs/latest/assets/users-permissions/end-user_roles.png differ
diff --git a/docs/user-docs/latest/assets/users-permissions/users-roles-permissions-settings.png b/docs/user-docs/latest/assets/users-permissions/users-roles-permissions-settings.png
index 93a75da65f..00230f1804 100644
Binary files a/docs/user-docs/latest/assets/users-permissions/users-roles-permissions-settings.png and b/docs/user-docs/latest/assets/users-permissions/users-roles-permissions-settings.png differ
diff --git a/docs/user-docs/latest/content-manager/configuring-view-of-content-type.md b/docs/user-docs/latest/content-manager/configuring-view-of-content-type.md
index 73cbc748ee..019d6ee11c 100644
--- a/docs/user-docs/latest/content-manager/configuring-view-of-content-type.md
+++ b/docs/user-docs/latest/content-manager/configuring-view-of-content-type.md
@@ -1,6 +1,7 @@
---
title: Configuring views of a content type - Strapi User Guide
description: Instructions to configure the edit view and list view of a content type in a Strapi application.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-manager/configuring-view-of-content-type.html
---
# Configuring the views of a content type
@@ -9,9 +10,9 @@ Depending on their type, content types can be divided into 2 interfaces: the lis
## Configuring the list view
-On the right side of the list view interface, right above the table, a settings button is displayed. It allows to access the configurations that can be set for the list view of your collection type, and to choose which fields to display in the table.
+On the right side of the list view interface, right above the table, a settings button  is displayed. It allows to access the configurations that can be set for the list view of your collection type, and to choose which fields to display in the table.
-::: tip NOTE
+::: note
The configurations only apply to the list view of the collection type from which the settings are accessed (i.e. disabling the filters or search options for a collection type will not automatically also disable these same options for all other collection types).
Note also that the explanations below explain how to permanently configure which fields are displayed in the table of the list view of your collection type. It is also possible to configure the displayed fields temporarily (see [Introduction to content manager](../content-manager/introduction-to-content-manager.md)).
@@ -21,9 +22,8 @@ Note also that the explanations below explain how to permanently configure which
### List view settings
-1. In the list view of your collection type, click on the settings button .
-2. Click on the **Configure the view** button.
-3. In the Settings area, define your chosen new settings:
+1. In the list view of your collection type, click on the settings button  to be redirected to the list view configuration interface.
+2. In the Settings area, define your chosen new settings:
| Setting name | Instructions |
| ---------------------- | -------------------------------------------------------------------------------------------------- |
@@ -31,28 +31,28 @@ Note also that the explanations below explain how to permanently configure which
| Enable filters | Click on **ON** or **OFF** to able or disable filters. |
| Enable bulk actions | Click on **ON** or **OFF** to able or disable the multiple selection boxes in the list view table. |
| Entries per page | Choose among the drop-down list the number of entries per page. |
-| Default sort attribute | Choose the sorting field and type that will be applied by default. |
+| Default sort attribute | Choose the sorting field that will be used by default. |
+| Default sort order | Choose the sorting type that will be applied by default. |
-4. Click on the **Save** button.
+3. Click on the **Save** button.
### List view display
-1. In the list view of your collection type, click on the settings button .
-2. Click on the **Configure the view** button.
-3. In the View area, define what fields to display in the list view table, and in what order:
- - Click the add button  to add a new field.
- - Click the delete button  to remove a field.
- - Click the reorder button  and drag and drop it to the place you want it to be displayed among the other fields.
-4. Click the name of the field to access its available own settings:
+1. In the list view of your collection type, click on the settings button  to be redirected to the list view configuration interface.
+2. In the View area, define what fields to display in the list view table, and in what order:
+ - Click the add button  to add a new field.
+ - Click the delete button  to remove a field.
+ - Click the reorder button  and drag and drop it to the place you want it to be displayed among the other fields.
+3. Click the edit button  to access its available own settings:
| Setting name | Instructions |
| ------------------------- | ------------------------------------------------------------------------- |
-| Label | Write the label to should be used for the field in the list view table. |
+| Label | Write the label to be used for the field in the list view table. |
| Enable sort on this field | Click on **ON** or **OFF** to able or disable the sort on the field. |
-5. Click on the **Save** button.
+4. Click on the **Save** button.
-::: tip NOTE
+::: note
Relational fields can also be displayed in the list view. There are however some specificities to keep in mind:
- Only one field can be displayed per relational field.
@@ -86,10 +86,10 @@ In the edit view of a content type, in the right side of the interface, a **Conf
1. In the edit view of your content type, click on the **Configure the view** button.
2. In the View area, define what fields to display in the list view table, and in what order:
- - Click the add button  to add a new field.
- - Click the delete button  to remove a field.
- - Click the reorder button  and drag and drop it to the place you want it to be displayed among the other fields.
-3. Click the name of a field to access its available own settings:
+ - Click the add button  to add a new field.
+ - Click the delete button  to remove a field.
+ - Click the reorder button  and drag and drop it to the place you want it to be displayed among the other fields.
+3. Click the edit button  to access its available own settings:
| Setting name | Instructions |
| --------------- | ----------------------------------------------------------------------------------------- |
@@ -100,7 +100,7 @@ In the edit view of a content type, in the right side of the interface, a **Conf
4. Click on the **Save** button.
-::: warning IMPORTANT
+::: caution
The settings and display of a component's fields cannot be managed and reordered through the entry's edit view configuration page. Click on the **Set the component's layout** button of a component to access the component's own configuration page. You will find the exact same settings and display options as for the entry, but that will specifically apply to your component.
Note also that the settings are defined for the component itself, which means that the settings will automatically be applied for every other content type where the component is used.
@@ -113,7 +113,7 @@ On the right side of the View area is displayed a Relational fields part. As in
To define what relational fields of an entry should be available in the edit view, the following options are available:
- the **Insert another relational field** button, to add another relational field to your entry. If the button remains unclickable, it means that no other relational field can be added.
-- the delete button , to remove a relational field.
-- the reorder button , to drag and drop to the place you want your relational field to be displayed among the others.
+- the delete button , to remove a relational field.
+- the reorder button , to drag and drop to the place you want your relational field to be displayed among the others.
As for regular fields, it is possible to access the available settings of the relational fields by clicking on their name. Most settings are the same as for regular fields (see [Edit view display](./configuring-view-of-content-type.md#edit-view-display)) except for "Entry title" which is only available for relational fields. It is recommended to choose well the entry title of relational fields as the more comprehensive it is, the easier it will be for administrators to manage the content of relational fields from the edit view.
diff --git a/docs/user-docs/latest/content-manager/introduction-to-content-manager.md b/docs/user-docs/latest/content-manager/introduction-to-content-manager.md
index a392c3e0eb..5e48488522 100644
--- a/docs/user-docs/latest/content-manager/introduction-to-content-manager.md
+++ b/docs/user-docs/latest/content-manager/introduction-to-content-manager.md
@@ -1,21 +1,22 @@
---
title: Content Manager - Strapi User Guide
description: Introduction to the Content Manager which allows to write content for collection types and single types.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-manager/introduction-to-content-manager.html
---
# Introduction to the Content Manager
-The Content Manager is a core plugin of Strapi. It is a feature that is always activated by default and cannot be deleted. It is accessible both when the application is in a development and production environment.
+The Content Manager is a core plugin of Strapi. It is a feature that is always activated by default and cannot be deactivated. It is accessible both when the application is in a development and production environment.
-The Content Manager is divided into 2 categories, both displayed in the main navigation: _Collection types_ and _Single types_. Each category contains the available collection and single content-types, which were created beforehand using the Content-Types Builder. From these 2 categories, administrators can create, manage, and publish content.
+The Content Manager is accessible from  *Content Manager* in the main navigation, which opens a subnavigation displaying 2 categories: _Collection types_ and _Single types_. Each category contains the available collection and single content-types which were created beforehand using the [Content-Type Builder](/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md). From these 2 categories, administrators can create, manage, and publish content.
-::: tip 💡 TIP
-Click the search icon in the main navigation to use a text search and find one of your content types more quickly!
+::: tip
+Click the search icon  in the subnavigation to use a text search and find one of your content-types more quickly!
:::
## Collection types
-The _Collection types_ category of the Content Manager displays the list of available collection types which are directly accessible from the main navigation of the admin panel.
+The _Collection types_ category of the Content Manager displays the list of available collection types which are accessible from the  Content Manager subnavigation.
For each available collection type multiple entries can be created which is why each collection type is divided into 2 interfaces: the list view and the edit view (see [Writing content](writing-content.md)).
@@ -25,13 +26,13 @@ The list view of a collection type displays all entries created for that collect
From the list view, it is possible to:
-- make a textual search (1) or set filters (2) to find specific entries,
-- create a new entry (3),
+- create a new entry (1),
+- make a textual search (2) or set filters (3) to find specific entries,
- if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed, filter by locale to display only the entries translated in a chosen locale (4),
- configure the fields displayed in the table of the list view (5),
-- duplicate , edit (see [Writing content](../content-manager/writing-content.md)) or delete (see [Deleting content](../content-manager/saving-and-publishing-content.md#deleting-content)) an entry.
+- edit  (see [Writing content](../content-manager/writing-content.md)), duplicate , or delete  (see [Deleting content](../content-manager/saving-and-publishing-content.md#deleting-content)) an entry.
-::: tip 💡 TIP
+::: tip
Sorting can be enabled for most fields displayed in the list view table (see [Configuring the views of a content type](../content-manager/configuring-view-of-content-type.md)). Click on a field name, in the header of the table, to sort on that field.
:::
@@ -46,48 +47,46 @@ To set a new filter:
1. Click on the **Filters** button.
2. Click on the 1st drop-down list to choose the field on which the condition will be applied.
3. Click on the 2nd drop-down list to choose the type of condition to apply.
-4. Enter the value of the condition in the 3rd box.
-5. (optional) Click on the add button  to add another condition-based filter.
-6. Click on the **Apply** button.
+4. Enter the value(s) of the condition in the remaining textbox.
+6. Click on the **Add filter** button.
-::: tip NOTE
-When active, filters are displayed next to the **Filters** button. They can be removed by clicking on the delete icon .
+::: note
+When active, filters are displayed next to the **Filters** button. They can be removed by clicking on the delete icon .
:::
### Creating a new entry
-On the top right side of the list view interface, an **Add New [collection type name]** button is displayed. It allows to create a new entry for your collection type.
+On the top right side of the list view interface, an **Add new entry** button is displayed. It allows to create a new entry for your collection type.
Clicking on the new entry button will redirect you to the edit view, where you will be able to write the content of the new entry (see [Writing content](writing-content.md)).
-::: warning IMPORTANT
+::: note
New entries are only considered created once some of their content has been written and saved once. Only then will the new entry be listed in the list view.
:::
### Configuring the table fields
-Right above the list view table, on the right side of the interface, a settings button is displayed. It allows to access the configurations that can be set for the list view of your collection type (see [Configuring the views of a content type](../content-manager/configuring-view-of-content-type.md)), and to choose which fields to display in the table.
+Above the list view table, on the right, a "... currently selected" drop-down menu is displayed. It allows to choose which fields to display in the table.
-::: tip NOTE
-Configuring the displayed field of the table in the way detailed below is only temporary: the configurations will be reset as soon as the page is refreshed or when navigating the admin panel outside the Content Manager. For permanent configurations, please refer to [Configuring the views of a content type](../content-manager/configuring-view-of-content-type.md).
+::: note
+Configuring the displayed field of the table in the way detailed below is only temporary: the configurations will be reset as soon as the page is refreshed or when navigating the admin panel outside the Content Manager. For permanent configurations, go to the list view configuration interface by clicking on the settings button  (see [Configuring the views of a content type](../content-manager/configuring-view-of-content-type.md)).
:::
To temporarily configure the fields displayed in the table:
-1. Click on the settings button .
-2. In the Displayed Fields section, tick the boxes associated with the field you want to be displayed in the table.
+1. Click on the "... currently selected" drop-down menu.
+2. Tick the boxes associated with the field you want to be displayed in the table.
3. Untick the boxes associated with the fields you do not want to be displayed in the table.
-::: tip NOTE
+::: tip
Relational fields can also be displayed in the list view. Please refer to [Configuring the views of a content type](../content-manager/configuring-view-of-content-type.md) for more information on their specificities.
-
:::
## Single types
-The _Single types_ category of the Content Manager displays the list of available single types, which are directly accessible from the main navigation of the admin panel.
+The _Single types_ category of the Content Manager displays the list of available single types, which are accessible from the  Content Manager subnavigation.
Unlike collection types which have multiple entries, single types are not created for multiple uses. In other words, there can only be one default entry per available single type. There is therefore no list view in the Single types category.
diff --git a/docs/user-docs/latest/content-manager/managing-relational-fields.md b/docs/user-docs/latest/content-manager/managing-relational-fields.md
index 3e332423b8..12bb2bf6db 100644
--- a/docs/user-docs/latest/content-manager/managing-relational-fields.md
+++ b/docs/user-docs/latest/content-manager/managing-relational-fields.md
@@ -1,11 +1,12 @@
---
title: Managing Relational Fields - Strapi User Guide
description: Instructions to manage relation-type fields, called "relational fields", which establish a relation between two content-types.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-manager/managing-relational-fields.html
---
# Managing relational fields
-Relation-type fields added to a content-type from the Content-Types Builder allow to establish a relation with another content-type -mandatorily a collection type. These fields are called "relational fields".
+Relation-type fields added to a content-type from the Content-Type Builder allow to establish a relation with another content-type -mandatorily a collection type. These fields are called "relational fields".
Relational fields are before all else regular fields, meaning that their content is written from the edit view of the content-type they belong to (see [Writing content](writing-content.md)).
@@ -22,21 +23,21 @@ I want to assign a category to each of my restaurants, therefore I have establis
In the Content Manager, from the edit view of my Restaurant entries, I can manage the Category relational field, and choose which entry of Category is relevant for my restaurant.
:::
-
+
-The relational fields of a content-type are managed from the Relational fields box, located in the right side of the edit view interface. It lists the names of the relational fields. Under each relational field name is displayed a drop-down list containing all available entry titles.
+The relational fields of a content-type are managed from the Relations box, located in the right side of the edit view interface. It lists the names of the relational fields. Under each relational field name is displayed a drop-down list containing all available entry titles.
-The Relational fields box allows to choose which entries the relational fields should point to. You can either choose one or several entries depending on the type of relation that was established.
+The Relations box allows to choose which entries the relational fields should point to. You can either choose one or several entries depending on the type of relation that was established.
-::: tip 💡 TIP
-Instead of choosing an entry by scrolling the list, you can click any drop-down list from the Relational fields box and type to search a specific entry.
+::: tip
+Instead of choosing an entry by scrolling the list, you can click any drop-down list from the Relations box and type to search a specific entry.
:::
-::: tip NOTE
+::: note
If the Draft & Publish feature (see [Saving, publishing and deleting content](saving-and-publishing-content.md)) is activated for the content-type the relational field belongs to, you will notice blue or green dots next to the entries names in the drop-down list. They indicate the status of the entry, respectively draft or published content.
:::
-::: warning IMPORTANT
+::: caution
If the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed, the list of entries may be limited or differ from one locale to another. Only relevant entries that can possibly be chosen for a relational field will be listed.
:::
@@ -44,33 +45,33 @@ If the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md
Many-to-one, one-to-one, and one-way types of relation only allow to choose one entry per relational field.
-
+
To select the only relevant relational field's entry:
-1. In the Relational fields box of your content-type's edit view, click on the drop-down list of the relational field.
+1. In the Relations box of your content-type's edit view, click on the drop-down list of the relational field.
2. Among the list of entries, choose one.
-::: tip 💡 TIP
+::: tip
Click on **Details** to be redirected to the edit view of the content-type the relational field originally belongs to. Make sure you save your page first, to avoid losing your last modifications.
:::
-To remove the entry selected in the drop-down list, click on the  button.
+To remove the entry selected in the drop-down list, click on the delete button .
## Managing multiple-choices relational fields
Many-to-many, one-to-many, and many-ways types of relation allow to choose several entries per relational field.
-
+
To select the relevant relational field's entries:
-1. In the Relational fields box of your content-type's edit view, click on the drop-down list of the relational field.
+1. In the Relations box of your content-type's edit view, click on the drop-down list of the relational field.
2. Among the list of entries, choose one.
3. Repeat step 2 until all relevant entries have been chosen.
-::: tip 💡 TIP
+::: tip
All selected entries are listed right below the drop-down list. Click on the name of an entry to be redirected to the edit view of the content-type the relational field originally belongs to.
:::
-To remove an entry, click on the  button in the selected entries list.
+To remove an entry, click on the remove button  in the selected entries list.
diff --git a/docs/user-docs/latest/content-manager/saving-and-publishing-content.md b/docs/user-docs/latest/content-manager/saving-and-publishing-content.md
index 9e04eebf20..a34ffc9075 100644
--- a/docs/user-docs/latest/content-manager/saving-and-publishing-content.md
+++ b/docs/user-docs/latest/content-manager/saving-and-publishing-content.md
@@ -1,6 +1,7 @@
---
title: Saving & Publishishing content - Strapi User Guide
description: Instructions to manage content throughout its whole lifecycle, from the draft version to the deletion of the obsolete content.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-manager/saving-and-publishing-content.html
---
# Saving, publishing and deleting content
@@ -9,11 +10,11 @@ Strapi allows you to manage your content throughout its whole lifecycle, whether
## Saving & publishing content
-::: warning IMPORTANT
-The possibility to manage drafts for contents comes from the Draft & Publish feature. This feature is activated by default, but it can be deactivated for any content type from the Content-Types Builder. If you disabled the Draft & Publish feature, saving your content means saving and publishing at the same time.
+::: caution
+The possibility to manage drafts for contents comes from the Draft & Publish feature. This feature is activated by default, but it can be deactivated for any content type from the Content-Type Builder. If you disabled the Draft & Publish feature, saving your content means saving and publishing at the same time.
:::
-Your contents can have 2 statuses: draft or published. You can see the current status indicated on the right of the interface, below the Information box.
+Your contents can have 2 statuses: draft or published. You can see the current status indicated on the right of the interface, above the Information box.
@@ -23,11 +24,11 @@ By default, each newly created content is a draft. Drafts can be modified and sa
To publish a draft, click on the **Publish** button in the top right corner of the content editor.
-::: warning CAUTION
+::: caution
Before publishing a draft, make sure it doesn't have relations with other non-published content, otherwise some of the content may not be available through the API.
:::
-When a content is not a draft anymore, but has been published, it is indicated on the right of the interface, below the Information box.
+When a content is not a draft anymore, but has been published, it is indicated on the right of the interface, above the Information box.
@@ -42,12 +43,12 @@ To unpublish content, click on the **Unpublish** button in the top right corner
You can delete content by deleting any entry of a collection type, or the default entry of a single type.
1. In the edit view of the entry, click on the **Delete this entry** button, located at the bottom of the right side of the interface.
-2. In the window that pops up, click on the **Yes, confirm** button to confirm the deletion.
+2. In the window that pops up, click on the **Confirm** button to confirm the deletion.
-::: tip 💡 TIP
-You can delete entries from the list view of a collection type, by clicking on the trash button  on the right side of the entry's record in the table.
You also have the possibility to delete multiple entries at the same time. To do so, select your entries to delete by ticking the box on the left side of the entries' record. Then, click on **Delete selected**  located right below the header of the table.
+::: tip
+You can delete entries from the list view of a collection type, by clicking on the delete button  on the right side of the entry's record in the table.
You also have the possibility to delete multiple entries at the same time. To do so, select your entries to delete by ticking the box on the left side of the entries' record. Then, click on the **Delete** button located above the header of the table.
:::
-::: warning IMPORTANT
+::: caution
If the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed, entries can only be deleted one locale at the time.
:::
\ No newline at end of file
diff --git a/docs/user-docs/latest/content-manager/translating-content.md b/docs/user-docs/latest/content-manager/translating-content.md
index a76bd1fce1..2e57c58b03 100644
--- a/docs/user-docs/latest/content-manager/translating-content.md
+++ b/docs/user-docs/latest/content-manager/translating-content.md
@@ -1,6 +1,7 @@
---
title: Translating content - Strapi User Guide
-description: Instructions to translate content in various locales with i18n plugin
+description: Instructions to translate content in various locales with i18n plugin.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-manager/translating-content.html
---
# Translating content
@@ -13,12 +14,12 @@ In the Content Manager, when the Internationalization plugin is installed, some
- an Internationalization box, displayed in the right side of the interface, from where it is possible to switch locales
- icons displayed next to every field to indicate whether the field can be translated or not:
- - 
indicates that the field can be translated,
- - 
indicates that the field cannot be translated: its content is the same for every locale (i.e. changing the value of a non-localizable field changes it for all other locales).
+ -  indicates that the field can be translated,
+ -  indicates that the field cannot be translated: its content is the same for every locale (i.e. changing the value of a non-localizable field changes it for all other locales).
The Internationalization plugin also allows dynamic zones and components to differ from one locale to another. Depending on the locale, dynamic zones can indeed have different structures depending on the locale, and repeatable components can have different entries and be organised differently as well.
-::: warning IMPORTANT
+::: caution
Content can only be managed one locale at the time. It is not possible to edit or publish content for several locales at the same time (e.g. Clicking on the **Publish** button will only publish the content for the locale you are currently working on).
:::
@@ -29,6 +30,6 @@ To translate content in another locale:
3. Choose the locale in which you want to translate your content.
4. Translate your content by filling up your content-type's fields (see [Writing content](writing-content.md)).
-::: tip 💡 TIP
-Click on the **Fill in form** button in the Internationalization box for all non relational fields to be filled up with the values of another chosen locale. It can be useful if you do not remember what was the exact content in another locale.
+::: tip
+Click on the **Fill in from another locale** button in the Internationalization box for all non relational fields to be filled up with the values of another chosen locale. It can be useful if you do not remember what was the exact content in another locale.
:::
\ No newline at end of file
diff --git a/docs/user-docs/latest/content-manager/writing-content.md b/docs/user-docs/latest/content-manager/writing-content.md
index cffa4f55d1..e7acecec0e 100644
--- a/docs/user-docs/latest/content-manager/writing-content.md
+++ b/docs/user-docs/latest/content-manager/writing-content.md
@@ -1,11 +1,12 @@
---
title: Writing Content - Strapi User Guide
description: Instructions to write content by filling up fields that are meant to contain specific content (e.g. text, numbers, media etc.).
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-manager/writing-content.html
---
# Writing content
-In Strapi, writing content consists in filling up fields, which are meant to contain specific content (e.g. text, numbers, media etc.). These fields were configured for the collection or single type beforehand, through the Content-Types Builder.
+In Strapi, writing content consists in filling up fields, which are meant to contain specific content (e.g. text, numbers, media etc.). These fields were configured for the collection or single type beforehand, through the [Content-Type Builder](/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md).
@@ -18,8 +19,8 @@ To write or edit content:
| Field name | Instructions |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Text | Write your content in the textbox.
💡 For long texts, the box can be expanded. |
-| Rich text | Write your content, in MarkDown, in the textbox. Formatting options are available in the top bar of the textbox, as well as a **Switch to preview** button to see the result of your content.
💡 The box can be expanded by clicking on **Expand** in the bottom bar. It displays side by side, at the same time, the textbox that you can edit and the preview. |
+| Text | Write your content in the textbox. |
+| Rich text | Write your content in the textbox. Formatting options are available in the top bar of the textbox, as well as a **Preview mode/Markdown mode** button to switch between modes.
💡 The box can be expanded by clicking on **Expand** in the bottom bar. It displays side by side, at the same time, the textbox that you can edit and the preview. |
| Number | Write your number in the textbox. Up and down arrows, displayed on the right of the box, allow to increase or decrease the current number indicated in the textbox. |
| Date | 1. Click the date and/or time box.
2. Choose a date using the calendar and/or a time among the list. |
| Boolean | Click on **OFF** or **ON**. |
@@ -38,35 +39,36 @@ There are 2 types of components: non-repeatable and repeatable components.
#### Non-repeatable components
-
-
+
+
Non-repeatable components are a combination of fields which can be used only once.
By default, the combination of fields are not directly displayed in the edit view:
-1. Click on the  button to add the component.
+1. Click on the add button  to add the component.
2. Fill in the fields of the component.
-To delete the non-repeatable component, click on the trash button , located on the top right corner of the component area.
+To delete the non-repeatable component, click on the delete button , located on the top right corner of the component area.
#### Repeatable components
-
+
Repeatable components are also a combination of fields, but they allow to create multiple component entries, all following the same combination of fields.
To add a new entry and display its combination of fields:
-1. Click on the  **Add new entry** button.
+1. Click on the add button  to add the component.
2. Fill in the fields of the component.
+3. (optional) Click on the **Add new entry** button and fill in the fields again.
The repeatable component entries can be reordered or deleted directly in the edit view, using buttons displayed on the right of the entry area.
-- Use the drag & drop button  to reorder entries of your repeatable component.
-- Use the trash button  to delete an entry from your repeatable component.
+- Use the drag & drop button  to reorder entries of your repeatable component.
+- Use the delete button  to delete an entry from your repeatable component.
-::: tip NOTE
+::: note
Unlike regular fields, the order of the entries of a repeatable component is important. It should correspond exactly to how end-users will read/see the content.
:::
@@ -74,19 +76,19 @@ Unlike regular fields, the order of the entries of a repeatable component is imp
Dynamic zones are a combination of components, which themselves are composed of several fields. Writing the content of a dynamic zone requires additional steps in order to access the fields.
-
-
+
+
-1. Click on the  **Add to content** button.
+1. Click on the  **Add a component to [dynamic zone name]** button.
2. Choose a component available for the dynamic zone.
3. Fill in the fields of the component.
Dynamic zones' components can also be reordered or deleted directly in the edit view, using buttons displayed in the top right corner of the component area.
-- Use the arrow button  to reorder components in your dynamic zone.
-- Use the trash button  to delete a component from your dynamic zone.
+- Use the arrow buttons   to reorder components in your dynamic zone.
+- Use the delete button  to delete a component from your dynamic zone.
-::: tip NOTE
+::: note
Unlike regular fields, the order of the fields and components inside a dynamic field is important. It should correspond exactly to how end-users will read/see the content.
:::
diff --git a/docs/user-docs/latest/content-types-builder/configuring-fields-content-type.md b/docs/user-docs/latest/content-types-builder/configuring-fields-content-type.md
index 837c47b3eb..6fa9761e64 100644
--- a/docs/user-docs/latest/content-types-builder/configuring-fields-content-type.md
+++ b/docs/user-docs/latest/content-types-builder/configuring-fields-content-type.md
@@ -1,32 +1,33 @@
---
title: Fields for Content Types - Strapi User Guide
-description: Instructions to configure in the Content-Types Builder the fields that compose each content-type.
+description: Instructions to configure in the Content-Type Builder the fields that compose each content-type.
sidebarDepth: 3
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-types-builder/configuring-fields-content-type.html
---
# Configuring fields for content types
-::: warning The Content-Types Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.
+::: callout The Content-Type Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.
:::
Content-types are composed of one or several fields. Each field is designed to contain specific kind of data, filled up in the Content Manager (see [Writing content](/user-docs/latest/content-manager/writing-content.md)).
-In the Content-Types Builder, fields can be added at the creation of a new content-type or component, or afterward when a content-type or component is edited or updated. The following documentation lists all existing regular fields but also tackles the specificities of components and dynamic zones. For each, you will find a definition, explanation of the form they take once in the Content Manager, and instructions to configure them.
+In the Content-Type Builder, fields can be added at the creation of a new content-type or component, or afterward when a content-type or component is edited or updated. The following documentation lists all existing regular fields but also tackles the specificities of components and dynamic zones. For each, you will find a definition, explanation of the form they take once in the Content Manager, and instructions to configure them.
-::: tip NOTE
+::: note
Depending on what content-type or component is being created or edited, not all fields -including components and dynamic zones- are always available.
:::
-
+
## Regular fields
-### 
Text
+### 
Text
The Text field displays a textbox that can contain small text. This field can be used for titles, descriptions, etc.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -55,11 +56,11 @@ The Text field displays a textbox that can contain small text. This field can be
::::
-### 
Rich Text
+### 
Rich Text
The Rich Text field displays an editor with formatting options to manage rich text. This field can be used for long written content.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -77,6 +78,7 @@ The Rich Text field displays an editor with formatting options to manage rich te
| Private field | Tick to make the field private and prevent it from being found via the API. |
| Enable localization for this field | (if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed and localization is enabled for the content-type) Allow the field to have a different value per locale. |
| Required field | Tick to prevent creating or saving an entry if the field is not filled in. |
+| Unique field | Tick to prevent another field to be identical to this one. |
| Maximum length | Tick to define a maximum number of characters allowed. |
| Minimum length | Tick to define a minimum number of characters allowed. |
@@ -84,11 +86,11 @@ The Rich Text field displays an editor with formatting options to manage rich te
::::
-### 
Number
+### 
Number
The Number field displays a field for any kind of number: integer, decimal and float.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -115,11 +117,11 @@ The Number field displays a field for any kind of number: integer, decimal and f
::::
-### 
Date
+### 
Date
The Date field can display a date (year, month, day), time (hour, minute, second) or datetime (year, month, day, hour, minute, and second) picker.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -144,11 +146,11 @@ The Date field can display a date (year, month, day), time (hour, minute, second
::::
-### 
Boolean
+### 
Boolean
The Boolean field displays a toggle button to manage boolean values (e.g. Yes or No, 1 or 0, True or False).
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -162,7 +164,7 @@ The Boolean field displays a toggle button to manage boolean values (e.g. Yes or
| Setting name | Instructions |
|----------------|-----------------------------------------------------------------------------|
-| Default value | Write the default value of the Boolean field. |
+| Default value | Choose the default value of the Boolean field: *true*, *null* or *false*. |
| Private field | Tick to make the field private and prevent it from being found via the API. |
| Enable localization for this field | (if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed and localization is enabled for the content-type) Allow the field to have a different value per locale. |
| Required field | Tick to prevent creating or saving an entry if the field is not filled in. |
@@ -172,20 +174,20 @@ The Boolean field displays a toggle button to manage boolean values (e.g. Yes or
::::
-### 
Relation
+### 
Relation
The Relation field allows to establish a relation with another content-type, that must be a collection type.
There are 6 different types of relations:
-- 
One way: Content-type A *has one* Content-type B
-- 
One-to-one: Content-type A *has and belong to one* Content-type B
-- 
One-to-many: Content-type A *belongs to many* Content-type B
-- 
Many-to-one: Content-type B *has many* Content-type A
-- 
Many-to-many: Content-type A *has and belongs to many* Content-type B
-- 
Many way: Content-type A *has many* Content-type B
+- 
One way: Content-type A *has one* Content-type B
+- 
One-to-one: Content-type A *has and belong to one* Content-type B
+- 
One-to-many: Content-type A *belongs to many* Content-type B
+- 
Many-to-one: Content-type B *has many* Content-type A
+- 
Many-to-many: Content-type A *has and belongs to many* Content-type B
+- 
Many way: Content-type A *has many* Content-type B
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -203,18 +205,16 @@ Configuring the base settings of the Relation field consists in choosing with wh
| Setting name | Instructions |
|----------------|-----------------------------------------------------------------------------|
| Private field | Tick to make the field private and prevent it from being found via the API. |
-| Unique field | Tick to prevent another field to be identical to this one. |
-| Custom column names | Rename the columns corresponding to the relational fields to make it more comprehensive in the database. |
:::
::::
-### 
Email
+### 
Email
The Email field displays an email address field with format validation to ensure the email address is valid.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -240,11 +240,11 @@ The Email field displays an email address field with format validation to ensure
::::
-### 
Password
+### 
Password
The Password field displays a password field that is encrypted.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -270,13 +270,13 @@ The Password field displays a password field that is encrypted.
::::
-### 
Enumeration
+### 
Enumeration
The Enumeration field allows to configure a list of values displayed in a drop-down list.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -291,7 +291,7 @@ The Enumeration field allows to configure a list of values displayed in a drop-d
| Setting name | Instructions |
|----------------|-----------------------------------------------------------------------------|
-| Default value | Write the default value of the Enumeration field. |
+| Default value | Choose the default value of the Enumeration field. |
| Name override for GraphQL | Write a custom GraphQL schema type to override the default one for the field. |
| Private field | Tick to make the field private and prevent it from being found via the API. |
| Enable localization for this field | (if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed and localization is enabled for the content-type) Allow the field to have a different value per locale. |
@@ -302,11 +302,11 @@ The Enumeration field allows to configure a list of values displayed in a drop-d
::::
-### 
Media
+### 
Media
The Media field allows to choose one or more media files (e.g. image, video) from those uploaded in the Media Library of the application.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -331,11 +331,11 @@ The Media field allows to choose one or more media files (e.g. image, video) fro
::::
-### 
JSON
+### 
JSON
The JSON field allows to configure data in a JSON format, to store JSON objects or arrays.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -353,18 +353,16 @@ The JSON field allows to configure data in a JSON format, to store JSON objects
| Enable localization for this field | (if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed and localization is enabled for the content-type) Allow the field to have a different value per locale. |
| Required field | Tick to prevent creating or saving an entry if the field is not filled in. |
| Unique field | Tick to prevent another field to be identical to this one. |
-| Maximum length | Tick to define a maximum number of characters allowed. |
-| Minimum length | Tick to define a minimum number of characters allowed. |
:::
::::
-### 
UID
+### 
UID
The UID field displays a field that sets a unique identifier, optionally based on an existing other field from the same content-type.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -389,16 +387,16 @@ The UID field displays a field that sets a unique identifier, optionally based o
::::
-## 
Components
+## 
Components
Components are a combination of several fields. Components allow to create reusable sets of fields, that can be quickly added to content-types, dynamic zones but also nested into other components.
-When configuring a component through the Content-Types Builder, it is possible to either:
+When configuring a component through the Content-Type Builder, it is possible to either:
- create a new component by clicking on *Create a new component* (see [Creating a new component](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-component)),
- or use an existing one by clicking on *Use an existing component*.
-:::: tabs
+:::: tabs card
::: tab Base settings
@@ -415,6 +413,7 @@ When configuring a component through the Content-Types Builder, it is possible t
| Setting name | Instructions |
|----------------|-----------------------------------------------------------------------------------------|
| Required field | Tick to prevent creating or saving an entry if the field is not filled in. |
+| Private field | Tick to make the field private and prevent it from being found via the API. |
| Maximum value | For repeatable components only - Tick to define a maximum number of characters allowed. |
| Minimum value | For repeatable components only - Tick to define a minimum number of characters allowed. |
| Enable localization for this field | (if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed and localization is enabled for the content-type) Allow the component to be translated per available locale. |
@@ -423,11 +422,11 @@ When configuring a component through the Content-Types Builder, it is possible t
::::
-## 
Dynamic zones
+## 
Dynamic zones
Dynamic zones are a combination of components that can be added to content-types. They allow a flexible content structure as once in the Content Manager, administrators have the choice of composing and rearranging the components of the dynamic zone how they want.
-:::: tabs
+:::: tabs card
::: tab Base settings
diff --git a/docs/user-docs/latest/content-types-builder/creating-new-content-type.md b/docs/user-docs/latest/content-types-builder/creating-new-content-type.md
index efa8d48b84..ef97fccff5 100644
--- a/docs/user-docs/latest/content-types-builder/creating-new-content-type.md
+++ b/docs/user-docs/latest/content-types-builder/creating-new-content-type.md
@@ -1,52 +1,53 @@
---
title: Creating Content-Types - Strapi User Guide
-description: The Content-Types Builder allows to create new content-types (single and collection types).
+description: The Content-Type Builder allows to create new content-types (single and collection types).
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-types-builder/creating-new-content-type.html
---
# Creating content-types
-::: warning The Content-Types Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.
+::: callout The Content-Type Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.
:::
-The Content-Types Builder allows to create new content-types: single and collection types. Although they are not proper content-types as they cannot exist independently, components can also be created through the Content-Types Builder, in the same way as collection and single types.
+The Content-Type Builder allows to create new content-types: single and collection types. Although they are not proper content-types as they cannot exist independently, components can also be created through the Content-Type Builder, in the same way as collection and single types.
## Creating a new content-type
-Content types are created from the Collection types and Single types categories of the Content-Types Builder.
+Content types are created from the Content-Type Builder's Collection types and Single types categories, both displayed in the Content-Type Builder subnavigation.
To create a new content-type:
1. Choose whether you want to create a collection type or a single type.
-2. Click on the **Create a new collection/single type** button in the category of the content-type you want to create.
-3. In the content-type creation window, write the name of the new content-type in the *Display name* textbox. When creating a collection type, opt for a singular name, as collection type names are automatically pluralised when displayed in the Content Manager.
-4. (optional) In the Advanced Settings tab, configure the available settings for the new content-type:
+2. In the category of the content-type you want to create, click on **Create a new collection/single type**.
+3. In the content-type creation window, write the name of the new content-type in the *Display name* textbox.
+4. Check the *API UID* to make sure the automatically pre-filled values are correct. Collection type names are indeed automatically pluralised when displayed in the Content Manager. It is recommended to opt for singular names, but the *API UID* field allows to fix any pluralisation mistake.
+5. (optional) In the Advanced Settings tab, configure the available settings for the new content-type:
| Setting name | Instructions |
|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| Draft & Publish | Click on **ON** to activate the Draft & Publish feature for your content-type (see [Saving & publishing content](/user-docs/latest/content-manager/saving-and-publishing-content.md#saving-publishing-content)). Click on **OFF** to deactivate the feature. |
-| Collection name | Write a database collection/table name that will be used for your content-type. |
| Enable localization for this Content-Type | (if the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed) Tick the box to allow the content-type to be managed in various locales. |
-5. Click on the **Continue** button.
-6. Add and configure chosen fields for your content-type (see [Configuring fields for content-types](/user-docs/latest/content-types-builder/configuring-fields-content-type.md)).
-7. Click on the **Save** button.
+6. Click on the **Continue** button.
+7. Add and configure chosen fields for your content-type (see [Configuring fields for content-types](/user-docs/latest/content-types-builder/configuring-fields-content-type.md)).
+8. Click on the **Save** button.
-::: warning IMPORTANT
-New content-types are only considered created once they have been saved. Saving is only possible if at least one field has been added and properly configured. If these steps have not been done, a content-type cannot be created, listed in its category in the Content-Types Builder, and cannot be used in the Content Manager.
+::: caution
+New content-types are only considered created once they have been saved. Saving is only possible if at least one field has been added and properly configured. If these steps have not been done, a content-type cannot be created, listed in its category in the Content-Type Builder, and cannot be used in the Content Manager.
:::
## Creating a new component
-Components are created from the same-named category of the Content-Types Builder.
+Components are created from the same-named category of the Content-Type Builder's subnavigation.
To create a new component:
-1. Click on the **Create a new component** button.
+1. In the Components category of the Content-Type Builder subnavigation, click on **Create a new component**.
2. In the component creation window, configure the base settings of the new component:
- Write the name of the component in the *Name* textbox.
- Select an available category, or enter in the textbox a new category name to create one.
diff --git a/docs/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md b/docs/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md
index f38b0fc419..998d114a79 100644
--- a/docs/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md
+++ b/docs/user-docs/latest/content-types-builder/introduction-to-content-types-builder.md
@@ -1,29 +1,30 @@
---
-title: Content-Types Builder - Strapi User Guide
-description: From the Content-Types Builder, administrators can create and manage content-types (collection types and single types but also components).
+title: Content-Type Builder - Strapi User Guide
+description: From the Content-Type Builder, administrators can create and manage content-types (collection types and single types but also components).
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-types-builder/introduction-to-content-types-builder.html
---
-# Introduction to the Content-Types Builder
+# Introduction to the Content-Type Builder
-The Content-Types Builder is a core plugin of Strapi. It is a feature that is always activated by default and cannot be deleted. The Content-Types Builder is however only accessible when the application is in a development environment.
+The Content-Type Builder is a core plugin of Strapi. It is a feature that is always activated by default and cannot be deactivated. The Content-Type Builder is however only accessible when the application is in a development environment.
-Administrators can access the Content-Types Builder from _Plugins > Content-Types Builder_ in the main navigation of the admin panel.
+Administrators can access the Content-Type Builder from  _Content-Type Builder_ in the main navigation of the admin panel.
-
+
-From the Content-Types Builder, administrators can create and manage content-types: collection types and single types but also components.
+From the Content-Type Builder, administrators can create and manage content-types: collection types and single types but also components.
- Collection types are content-types that can manage several entries.
- Single types are content-types that can only manage one entry.
- Components are a data structure that can be used in multiple collection types and single types.
-All 3 are displayed as categories in the left side of the Content-Types Builder interface. In each category are listed all content-types and components that have already been created.
+All 3 are displayed as categories in the subnavigation of the Content-Type Builder. In each category are listed all content-types and components that have already been created.
-From each category of the Content-Types Builder, it is possible to:
+From each category of the Content-Type Builder subnavigation, it is possible to:
- click on an existing content-type or component to access it and edit it (see [Managing content-types](/user-docs/latest/content-types-builder/managing-content-types.md)),
- or create a new content-type or component (see [Creating content-types](/user-docs/latest/content-types-builder/creating-new-content-type.md)).
-::: tip 💡 TIP
-Click the search icon of any category to find a specific collection type, single type, or component.
+::: tip
+Click the search icon  in the Content-Type Builder subnavigation to find a specific collection type, single type, or component.
:::
diff --git a/docs/user-docs/latest/content-types-builder/managing-content-types.md b/docs/user-docs/latest/content-types-builder/managing-content-types.md
index 0b74ad3043..c3a0d6e063 100644
--- a/docs/user-docs/latest/content-types-builder/managing-content-types.md
+++ b/docs/user-docs/latest/content-types-builder/managing-content-types.md
@@ -1,48 +1,49 @@
---
title: Managing Content-types - Strapi User Guide
-description: The Content-Types Builder allows to manage any existing content-type or component, even if it is already being used in the Content Manager. They can only be managed one at a time.
+description: The Content-Type Builder allows to manage any existing content-type or component, even if it is already being used in the Content Manager. They can only be managed one at a time.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/content-types-builder/managing-content-types.html
---
# Managing content-types
-::: warning The Content-Types Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.
+::: callout The Content-Type Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.
:::
-The Content-Types Builder allows to manage any existing content-type or component, even if it is already being used in the Content Manager. They can only be managed one at a time.
+The Content-Type Builder allows to manage any existing content-type or component, even if it is already being used in the Content Manager. They can only be managed one at a time.
To manage a content-type or a component, click on its name in the Collection Types, Single Types or Components category.
## Editing content-types
-Managing a content-type or component can include editing the general settings and the fields, but also deleting the whole content-type or component. For any chosen content-type of component, the right side of the Content-Types Builder interface displays all available editing options.
+Managing a content-type or component can include editing the general settings and the fields, but also deleting the whole content-type or component. For any chosen content-type of component, the right side of the Content-Type Builder interface displays all available editing options.
-
+
-- Next to the name and optional description of the content-type or component, an edit button (1) allows to access the general settings of the content-type or component.
-- In the top right corner, **Cancel** and **Save** buttons (2) allow to respectively cancel or save any ongoing modification.
+- Next to the name and optional description of the content-type or component, an  **Edit** button (1) allows to access the general settings of the content-type or component.
+- In the top right corner:
+ - the **Add new field** and **Save** buttons (2) allow to respectively add another field to the content-type or component (see [Configuring fields for content-types](/user-docs/latest/content-types-builder/configuring-fields-content-type.md)), or save any ongoing modification.
+ - the **Configure the view** button allows to access the view configuration interface (see [Configuring the edit view](/user-docs/latest/content-manager/configuring-view-of-content-type.md#configuring-the-edit-view))
- Below the previous editing options, a table (3) lists all the fields created and configured for the content-type or component. From the fields table, it is possible to:
- - Click on the edit button to edit a field
- - Click on the trash button to delete a field
- - Click on the **Add another field** button to add another field to the content-type or component (see [Configuring fields for content-types](/user-docs/latest/content-types-builder/configuring-fields-content-type.md))
- - Click on the **Configure the view** button to access the view configuration interface (see [Configuring the edit view](/user-docs/latest/content-manager/configuring-view-of-content-type.md#configuring-the-edit-view))
+ - Click on the edit button  to edit a field
+ - Click on the delete button  to delete a field
-::: warning IMPORTANT
+::: caution
Editing a field allows renaming it. However, keep in mind that regarding the database, renaming a field means creating a whole new field and deleting the former one. Although nothing is deleted from the database, the data that was associated with the former field name will not be accessible from the admin panel of your application anymore.
:::
## Deleting content-types
-Content types and components can be deleted through the Content-Types Builder. Deleting a content-type automatically deletes all entries from the Content Manager that were based on that content-type. The same goes for the deletion of a component, which is automatically deleted from every content-type or entry where it was used.
+Content types and components can be deleted through the Content-Type Builder. Deleting a content-type automatically deletes all entries from the Content Manager that were based on that content-type. The same goes for the deletion of a component, which is automatically deleted from every content-type or entry where it was used.
To delete a content-type or component:
-1. In the Content-Types Builder navigation, click on the name of the content-type or component to delete.
-2. In the edition interface of the chosen content-type or component, click on the edit button on the right side of the content-type's or component's name.
+1. In the Content-Type Builder subnavigation, click on the name of the content-type or component to delete.
+2. In the edition interface of the chosen content-type or component, click on the  **Edit** button on the right side of the content-type's or component's name.
3. In the edition window, click on the **Delete** button.
4. In the confirmation window, confirm the deletion.
-::: warning IMPORTANT
-Deleting a content-type only deletes what was created and available from the Content-Types Builder, and by extent from the admin panel of your Strapi application. All the data that was created based on that content-type is however kept in the database. For more information, please refer to the related [GitHub issue](https://github.com/strapi/strapi/issues/1114).
+::: caution
+Deleting a content-type only deletes what was created and available from the Content-Type Builder, and by extent from the admin panel of your Strapi application. All the data that was created based on that content-type is however kept in the database. For more information, please refer to the related [GitHub issue](https://github.com/strapi/strapi/issues/1114).
:::
diff --git a/docs/user-docs/latest/getting-started/introduction.md b/docs/user-docs/latest/getting-started/introduction.md
index 35aa6d0227..1f9d7c05f5 100644
--- a/docs/user-docs/latest/getting-started/introduction.md
+++ b/docs/user-docs/latest/getting-started/introduction.md
@@ -1,6 +1,8 @@
---
title: Strapi User Guide
description: This user guide contains the functional documentation related to all features available in the admin panel of your Strapi application.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/getting-started/introduction.html
+sidebarDepth: 3
---
# Welcome to the Strapi user guide!
@@ -11,9 +13,9 @@ This user guide contains the functional documentation related to all features av
Before going any further into this user guide, we recommend you to acknowledge the main concepts below. They will help you to understand how Strapi works, and ensure a smooth Strapi experience.
-- **Development, Staging or Production Environment**
When you start working on your application, it is in a development environment, which is the status for the content structure and application configuration. After deploying your application, it is in production or staging environment. This status change impacts how you can use your Strapi application, as some features are only available in development environment, such as the Content-Types Builder. In this user guide the availability or not of a feature, depending on the application status, is always mentioned in the feature's introduction.
+- **Development, Staging or Production Environment**
When you start working on your application, it is in a development environment, which is the status for the content structure and application configuration. After deploying your application, it is in production or staging environment. This status change impacts how you can use your Strapi application, as some features are only available in development environment, such as the Content-Type Builder. In this user guide the availability or not of a feature, depending on the application status, is always mentioned in the feature's introduction.
-- **Versions**
Strapi is constantly evolving and growing. This implies that new releases are quite frequent, to improve what is already available but also to add new features to Strapi. For every new Strapi version, we communicate through our main channels and by sending notifications both on your terminal (when launching your Strapi application), and on your application's admin panel. We always recommend to use the latest version, especially since our documentation including this user guide, are only aligned with the latest version. If you are on an older version of Strapi, some information in this documentation may not apply to your application.
+- **Versions**
Strapi is constantly evolving and growing. This implies that new releases are quite frequent, to improve what is already available but also to add new features to Strapi. For every new Strapi version, we communicate through our main channels and by sending notifications both on your terminal (when launching your Strapi application), and on your application's admin panel. We always recommend to use the latest version. However, we always keep live both the documentation of the current Strapi version, and the documention of the previous one - the latter being officially and actively maintained for 6 months after the release of the newest Strapi version.
- **License and Pricing Plans**
As a Strapi user you have the choice between using the Community Edition, which is entirely free, or one of the 3 paid plans of the Enterprise Edition: Bronze, Silver, and Gold (see [Pricing and Plans](https://strapi.io/pricing-self-hosted)). In this user guide if a feature is only available for the Enterprise Edition, a badge is displayed beside the section's title to indicate which plans allow access to that feature (e.g. ).
@@ -25,8 +27,8 @@ With all this in mind, you should be ready to start your Strapi experience!
The admin panel is the back office of your Strapi application. From the admin panel, you will be able to manage content types, and write their actual content. It is also from the admin panel that you will manage users, both administrators and end-users of your Strapi application.
-::: warning IMPORTANT
-In order to access the admin panel, your Strapi application must be launched, and you must be aware of the URL to its admin panel (e.g. `api.example.com/admin`).
+::: caution
+In order to access the admin panel, your Strapi application must be launched, and you must be aware of the URL to its admin panel (e.g. `api.example.com/admin`).
:::
@@ -35,7 +37,7 @@ To access the admin panel:
1. Go to the URL of your Strapi application's admin panel.
2. Enter your credentials to log in.
-3. Click on the **Log in** button. You should be redirected to the homepage of the admin panel.
+3. Click on the **Login** button. You should be redirected to the homepage of the admin panel.
### Using SSO for authentication
@@ -45,31 +47,46 @@ To do so, in the login page of your Strapi application, click on a chosen provid
## Setting up your administrator profile
-If you are a new administrator, we recommend making sure your profile is all set, before diving into your Strapi application. From your administrator profile, you are able to modify your user information, such as name, username, email or password.
+If you are a new administrator, we recommend making sure your profile is all set, before diving into your Strapi application. From your administrator profile, you are able to modify your user information, such as name, username, email or password. You can also choose the language of the interface for your Strapi application.
To modify your user information:
-1. Click on your user name in the top right hand corner of the admin panel.
+1. Click on your account name or initials in the bottom left hand corner of the main navigation of your Strapi application.
2. In the drop-down menu, click on **Profile**.
3. Modify the information of your choice:
-| User information | Instructions |
+| Profile & Experience | Instructions |
| --------------------- | ------------------------------------------------------------------------------------------------------- |
| First name | Write your first name in the textbox. |
| Last name | Write your last name in the textbox. |
| Email | Write your complete email address in the textbox. |
| Username | (optional) Write a username in the textbox. |
-| Password | Write a new password in the textbox. You can click on the eye icon for the password to be shown. |
-| Confirmation password | Write the same new password in the textbox. You can click on the eye icon for the password to be shown. |
+| Interface language | Among the drop-down list, choose a language for your Strapi application interface. |
4. Click on the **Save** button.
+### Changing your password
+
+To change the password of your account:
+
+1. Go to your administrator profile.
+2. Fill in the password-related options:
+
+| Password modification | |
+| --------------------- | ------------------------------------------------------------------------------------------------------- |
+| Current password | Write your current password in the textbox.
💡 You can click on the eye icon for the password to be shown. |
+| Password | Write the new password in the textbox.
💡 You can click on the eye icon for the password to be shown. |
+| Password confirmation | Write the same new password in the textbox.
💡 You can click on the eye icon for the password to be shown. |
+
+3. Click on the **Save** button.
+
+
---
Congratulations on being a new Strapi user! You're now ready to discover all the features and options that Strapi has to offer!
-::: tip 💡 TIP
+::: strapi Welcome to the Strapi community!
If you have any trouble with your Strapi experience, you can reach us through [GitHub](https://github.com/strapi/) or our [forum](https://forum.strapi.io/)! The Strapi Community and Strapi team are always available to answer your questions or help you with anything!
:::
diff --git a/docs/user-docs/latest/plugins/installing-plugins-via-marketplace.md b/docs/user-docs/latest/plugins/installing-plugins-via-marketplace.md
index 0bcef6820b..9953190633 100644
--- a/docs/user-docs/latest/plugins/installing-plugins-via-marketplace.md
+++ b/docs/user-docs/latest/plugins/installing-plugins-via-marketplace.md
@@ -1,13 +1,20 @@
---
title: Installing plugins via the Marketplace - Strapi User Guide
-description: Instructions to install new plugins in a Strapi application via the Marketplace
+description: Instructions to install new plugins in a Strapi application via the Marketplace.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/plugins/installing-plugins-via-marketplace.html
---
# Installing plugins via the Marketplace
-The Marketplace is a section of the admin panel that lists all plugins that can be installed in a Strapi application. The Marketplace is accessible from _General > Marketplace_ in the main navigation of the admin panel.
+::: callout 🚧 The Marketplace is currently not available for v4. It will be back soon, stay tuned!
+In the meantime, plugins can be installed via the Command Line Interface (see [Developer Documentation](/developer-docs/latest/developer-resources/cli/CLI.md#strapi-install)).
+:::
+
+The Marketplace is a section of the admin panel that lists all plugins that can be installed in a Strapi application. The Marketplace is accessible from  _Marketplace_ in the main navigation of the admin panel.
-::: warning IMPORTANT
+
\ No newline at end of file
diff --git a/docs/user-docs/latest/plugins/introduction-to-plugins.md b/docs/user-docs/latest/plugins/introduction-to-plugins.md
index e06cfab9e2..c6b867f64f 100644
--- a/docs/user-docs/latest/plugins/introduction-to-plugins.md
+++ b/docs/user-docs/latest/plugins/introduction-to-plugins.md
@@ -1,16 +1,17 @@
---
title: Plugins - Strapi User Guide
description: Reference guide to all Strapi plugins and instructions to use these plugins.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/plugins/introduction-to-plugins.html
---
# Introduction to plugins
Strapi is built around plugins of different kinds. There are the core plugins which are essential for your Strapi application to function, and therefore cannot be deactivated. But there are also other plugins, that can either be installed by default or not, to add more options and possibilities to your Strapi application.
-::: tip NOTE
-Core plugins which include the Content Manager and the Content-Types Builder are documented in their own sections of the user guide as they are quite specific (see [Introduction to the Content Manager](../content-manager/introduction-to-content-manager.md) and [Introduction to the Content-Types Builder](../content-types-builder/introduction-to-content-types-builder.md)). This Plugins section focuses on how to manage plugins in general and provides documentation for the others, non-core plugins.
+::: note
+Core plugins which include the Content Manager and the Content-Type Builder are documented in their own sections of the user guide as they are quite specific (see [Introduction to the Content Manager](../content-manager/introduction-to-content-manager.md) and [Introduction to the Content-Type Builder](../content-types-builder/introduction-to-content-types-builder.md)). This Plugins section focuses on how to manage plugins in general and provides documentation for the others, non-core plugins.
:::
-Plugins are managed from _General > Marketplace_ and _General > Plugins_ in the main navigation of the admin panel, for anything related to installation and deletion. Once installed, your plugins are available in _Plugins_, also accessible from the main navigation of the admin panel.
+Plugins are managed, for anything related to installation and deletion, from  _Marketplace_ and  _Plugins_, both available in the main navigation of the admin panel. Once installed, your plugins are added to the main navigation of the admin panel, from where they are directly accessible.
diff --git a/docs/user-docs/latest/plugins/strapi-plugins.md b/docs/user-docs/latest/plugins/strapi-plugins.md
index 4be45da275..4f6ea41050 100644
--- a/docs/user-docs/latest/plugins/strapi-plugins.md
+++ b/docs/user-docs/latest/plugins/strapi-plugins.md
@@ -1,13 +1,16 @@
---
title: List of Strapi plugins - Strapi User Guide
-description: Reference guide to Strapi plugins explaining how they work and how they expand a Strapi application
+description: Reference guide to Strapi plugins explaining how they work and how they expand a Strapi application.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/plugins/strapi-plugins.html
---
# List of Strapi plugins
-::: warning 🚧 This section of the user guide is a work in progress. Stay tuned!
+
No matter if they are installed by default, or additional, Strapi plugins allow to expand your application by adding more options and possibilities. All options are documented in their right places throughout the user guide. However, you can use the following documentation as a reference guide to know which Strapi plugins are available, how they work and which options they add to your Strapi application.
@@ -15,7 +18,7 @@ No matter if they are installed by default, or additional, Strapi plugins allow
### 
Internationalization plugin
-The Internationalization plugin is installed by default on all Strapi applications running on version 3.6.0 or higher. For lower versions, a migration is needed (see [Update Strapi version](https://strapi.io/documentation/developer-docs/latest/update-migration-guides/update-version.html) in the developer documentation), as well as a manual installation of the plugin (see [Installing plugins via the Marketplace](installing-plugins-via-marketplace.md)).
+The Internationalization plugin is installed by default on all v4 Strapi applications, but can be deactivated.
This plugin allows to manage content in different languages, called "locales". With the Internationalization plugin, it is possible to:
@@ -27,14 +30,14 @@ The Internationalization plugin impacts several parts of the admin panel. The ta
| Section impacted | Options and settings |
|------------------|---------------------------------------------------------------------------------------------------------|
-| Settings | - Addition of a new "Internationalization" setting sub-section, from which to add, edit or delete locales available for the application (see [Configuring Internationalization locales](../settings/managing-global-settings.md#configuring-internationalization-locales)).
👉 Path reminder: *General > Settings > Global Settings > Internationalization*
- Addition of new permissions for administator roles: access to content-types, as well as possible actions on the content-types, can be defined depending on the locale (see [Configuring role's permissions](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#configuring-role-s-permissions)).
👉 Path reminder: *General > Settings > Administration panel*
|
-| Content-Types Builder | - Addition of a new setting at content-type level, to allow or not localisation/translation of the content-type (see [Creating a new content-type](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-content-type)).
- Addition of a new setting at field level, to allow or not localisation/translation of the content-type (see [Configuring fields for content types](/user-docs/latest/content-types-builder/configuring-fields-content-type.md#regular-fields)).
|
+| Settings | - Addition of a new "Internationalization" setting sub-section, from which to add, edit or delete locales available for the application (see [Configuring Internationalization locales](../settings/managing-global-settings.md#configuring-internationalization-locales)).
👉 Path reminder:  *Settings > Global Settings > Internationalization*
- Addition of new permissions for administator roles: access to content-types, as well as possible actions on the content-types, can be defined depending on the locale (see [Configuring role's permissions](/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md#configuring-role-s-permissions)).
👉 Path reminder:  *Settings > Administration panel*
|
+| Content-Type Builder | - Addition of a new setting at content-type level, to allow or not localisation/translation of the content-type (see [Creating a new content-type](/user-docs/latest/content-types-builder/creating-new-content-type.md#creating-a-new-content-type)).
- Addition of a new setting at field level, to allow or not localisation/translation of the content-type (see [Configuring fields for content types](/user-docs/latest/content-types-builder/configuring-fields-content-type.md#regular-fields)).
|
| Content Manager | - Addition of new *Locales* filter in collection types list view, to manage entries per locale (see [Introduction to the Content Manager](/user-docs/latest/content-manager/introduction-to-content-manager.md#collection-types)).
- Addition of new options in content-types edit view, to translate content and manage it per locale (see [Translating content](/user-docs/latest/content-manager/translating-content.md)).
|
### 
Users & Permissions plugin
-The Users & Permissions plugin is installed by default on all Strapi applications.
+The Users & Permissions plugin is installed by default on all v4 Strapi applications, but can be deactivated.
This plugin allows to manage end-users, who consume the content that is created and managed with a Strapi application and displayed on a front-end application (e.g. website, mobile application, connected device etc.). With the Users & Permissions plugin, it is possible to:
@@ -47,6 +50,6 @@ The Users & Permissions plugin impacts several parts of the admin panel. The tab
| Section impacted | Options and settings |
|------------------|---------------------------------------------------------------------------------------------------------|
-| Settings | Addition of a "Users & Permissions plugin" setting section, which contains 4 sub-sections: Roles (see [Configuring end-users roles](../users-roles-permissions/configuring-end-users-roles.md)), Providers, Email Templates, and Advanced Settings (see [Configuring Users & Permissions plugin](../settings/configuring-users-permissions-plugin-settings.md)).
👉 Path reminder: *General > Settings > Users & Permissions plugin*
|
-| Content-Types Builder | Creation of 3 default collection types: "User", "Role" and "Permission". They respectively allow to manage the end-users, the end-users roles and their permissions. These collection types cannot be deleted and their composing fields cannot be edited, but addition of new fields is possible. Out of the 3, only the "User" collection type is then available via the Content Manager.
|
+| Settings | Addition of a "Users & Permissions plugin" setting section, which contains 4 sub-sections: Roles (see [Configuring end-users roles](../users-roles-permissions/configuring-end-users-roles.md)), Providers, Email Templates, and Advanced Settings (see [Configuring Users & Permissions plugin](../settings/configuring-users-permissions-plugin-settings.md)).
👉 Path reminder:  *Settings > Users & Permissions plugin*
|
+| Content-Type Builder | Creation of 3 default collection types: "User", "Role" and "Permission". They respectively allow to manage the end-users, the end-users roles and their permissions. These collection types cannot be deleted and their composing fields cannot be edited, but addition of new fields is possible. Out of the 3, only the "User" collection type is then available via the Content Manager.
|
| Content Manager | Addition of the default "User" collection type that allows to manage end-user accounts (see [Managing end-users accounts](../users-roles-permissions/managing-end-users.md)). - By default, the following fields are available: Username, Email, Password, as well as Confirmed and Blocked as boolean fields.
- The "User" collection type has a relation established with the "Role" collection type. All end-user accounts must indeed be attributed a role: by default, the end-user is attributed the end-user role set as default, but that role can be changed via the end-users entries directly in the Content Manager.
|
\ No newline at end of file
diff --git a/docs/user-docs/latest/settings/configuring-users-permissions-plugin-settings.md b/docs/user-docs/latest/settings/configuring-users-permissions-plugin-settings.md
index 8d8ad96db6..9ed4c698e1 100644
--- a/docs/user-docs/latest/settings/configuring-users-permissions-plugin-settings.md
+++ b/docs/user-docs/latest/settings/configuring-users-permissions-plugin-settings.md
@@ -1,11 +1,12 @@
---
title: Users & Permissions plugin settings - Strapi User Guide
description: Instructions to configure the Users & Permissions plugin
+canonicalUrl: https://docs.strapi.io/user-docs/latest/settings/configuring-users-permissions-plugin-settings.html
---
# Configuring Users & Permissions plugin settings
-The Users & Permissions plugin is managed from the *Users & Permissions plugin* settings section, accessible from *General > Settings* in the main navigation of the admin panel. This settings section allows to configure the available providers, email templates and the advanced settings of the plugin. It also allows to define the end-users roles and their related permissions (see [Configuring end-users roles](../users-roles-permissions/configuring-end-users-roles.md)).
+The Users & Permissions plugin is managed from the *Users & Permissions plugin* settings section, accessible from  *Settings* in the main navigation of the admin panel. This settings section allows to configure the available providers, email templates and the advanced settings of the plugin. It also allows to define the end-users roles and their related permissions (see [Configuring end-users roles](../users-roles-permissions/configuring-end-users-roles.md)).
## Configuring providers
@@ -21,10 +22,16 @@ To enable and configure a provider:
4. Fill in the provider's configurations. Each provider has its own specific set of configurations, detailed in our developer documentation (see [Setting up the provider](https://strapi.io/documentation/developer-docs/latest/development/plugins/users-permissions.html#setting-up-the-provider-examples)).
5. Click on the **Save** button.
-::: tip NOTE
+::: note
Other providers that are not proposed by default by Strapi can be added manually through the code of your Strapi application (see [Developer documentation](https://strapi.io/documentation/developer-docs/latest/development/plugins/users-permissions.html#adding-a-new-provider-to-your-project)).
:::
+
+
## Configuring email templates
The Users & Permissions plugin uses 2 email templates, "Email address confirmation" and "Reset password", that are sent to end-users:
@@ -66,4 +73,6 @@ All settings related to the Users & Permissions plugin are managed from the *Adv
| Enable sign-ups | Click on the **ON** button to enable end-users sign-ups. Click on **OFF** to prevent end-users registration to your front-end application(s). |
| Reset password page | Indicate the URL of the reset password page for your front-end application(s). |
| Enable email confirmation | Click on the **ON** button to enable end-users account confirmation by sending them a confirmation email. Click on **OFF** to disable account confirmation. |
-| Redirection url | Indicate the URL of the page where end-users should be redirected after confirming their Strapi account. |
\ No newline at end of file
+| Redirection url | Indicate the URL of the page where end-users should be redirected after confirming their Strapi account. |
+
+3. Click the **Save** button.
\ No newline at end of file
diff --git a/docs/user-docs/latest/settings/managing-global-settings.md b/docs/user-docs/latest/settings/managing-global-settings.md
index 16b5ec7fdc..fe6f963e7c 100644
--- a/docs/user-docs/latest/settings/managing-global-settings.md
+++ b/docs/user-docs/latest/settings/managing-global-settings.md
@@ -1,11 +1,12 @@
---
title: Global Settings - Strapi User Guide
description: Instructions to manage the global settings of a Strapi application in the admin panel.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/settings/manageing-global-settings.html
---
# Managing global settings
-Global settings for plugins and features are managed from *General > Settings* in the main navigation of the admin panel.
+Global settings for plugins and features are managed from  *Settings* in the main navigation of the admin panel.
## Configuring Single Sign-On
@@ -23,6 +24,8 @@ To configure the SSO feature settings:
| Auto-registration | Click on **ON** to allow the automatic creation of a new Strapi administrator when an SSO login does not match an existing Strapi administrator account. If this setting is set on **OFF**, new Strapi administrators accounts must be created manually beforehand. |
| Default role | Choose among the drop-down list the role to attribute by default to auto-registrated Strapi administrators through SSO login. |
+3. Click the **Save** button.
+
## Configuring Internationalization locales
The [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) allows to manage content in different languages, called "locales". Once the Internationalization plugin is installed in a Strapi application (see [Installing plugins via the Marketplace](../plugins/installing-plugins-via-marketplace.md)), administrators can manage locales from the *Global settings > Internationalization* sub-section of the settings interface.
@@ -33,15 +36,15 @@ The *Internationalization* settings sub-section displays a table listing all loc
For each locale, the table displays the default ISO code of the locale, its optional display name and indicates if the locale is set as the default one. From the table, administrators can also:
-- Click on the edit button to edit a locale
-- Click on the trash button to delete a locale
+- Click on the edit button  to edit a locale
+- Click on the delete button  to delete a locale
### Adding a new locale
Administrators can add and manage as many locales as they want. There can however only be one locale set as the default one for the whole Strapi application.
-::: tip NOTE
-It is not possible to create custom locales. Locales can only be created based on [the 500+ pre-created list of locales](https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-i18n/constants/iso-locales.json) set by Strapi.
+::: note
+It is not possible to create custom locales. Locales can only be created based on [the 500+ pre-created list of locales](https://github.com/strapi/strapi/blob/releases/v4/packages/plugins/i18n/server/constants/iso-locales.json) set by Strapi.
:::
To add a new locale:
@@ -50,4 +53,39 @@ To add a new locale:
2. In the locale addition window, choose your new locale among the *Locales* drop-down list. The latter lists alphabetically all locales, displayed as their ISO code, that can be added to your Strapi application.
3. (optional) In the *Locale display name* textbox, write a new display name for your new locale.
4. (optional) In the Advanced settings tab, tick the *Set as default locale* setting to make your new locale the default one for your Strapi application.
-5. Click on the **Add locale** button to confirm the addition of your new locale.
\ No newline at end of file
+5. Click on the **Save** button to confirm the addition of your new locale.
+
+## Managing API tokens
+
+API tokens allow users to authenticate their Content API queries (see [Developer Documentation](/developer-docs/latest/setup-deployment-guides/configurations/optional/api-tokens.md)). Administrators can manage API tokens through the *Global settings > API Tokens* sub-section of the settings interface.
+
+
+
+The *API Tokens* settings sub-section displays a table listing all created API tokens.
+
+For each API token, the table displays its name, description, type and date of creation. From the table, administrators can also:
+
+- Click on the edit button to edit an API token's name, description or type
+- Click on the delete button to delete an API token
+
+### Creating a new API token
+
+All API tokens created by administrators of the Strapi application are permanent tokens that cannot be regenerated.
+
+To create a new API token:
+
+1. Click on the **Add new entry** button.
+2. In the API token edition interface, configure the new API token:
+
+| Setting name | Instructions |
+|--------------|-----------------------------------------------------------|
+| Name | Write the name of the API token. |
+| Description | (optional) Write a description for the API token. |
+| Token type | Choose a token type: either *Read-only* or *Full access*. |
+
+3. Click on the **Save** button. The new API token will be displayed at the top of the interface, along with a copy button .
+
+::: caution
+For security reasons, API tokens are only shown right after they have been created. When refreshing the page or navigating elsewhere in the admin panel, the newly created API token will be hidden and will not be displayed again.
+:::
+
diff --git a/docs/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md b/docs/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md
index 35a3277a4b..bc237852c6 100644
--- a/docs/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md
+++ b/docs/user-docs/latest/users-roles-permissions/configuring-administrator-roles.md
@@ -1,11 +1,12 @@
---
title: Configure Administrator Roles - Strapi User Guide
description: Instructions to configure the administrator roles of a Strapi application with the Role-Based Access Control (RBAC) feature.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/users-roles-permissions/configuring-administrator-roles.html
---
# Configuring administrator roles
-Administrators are the users of an admin panel of a Strapi application. Administrator accounts and roles are managed with the Role-Based Access Control (RBAC) feature. It is available in the *Administration panel* section of the Settings interface, accessible from *General > Settings* in the main navigation of the admin panel.
+Administrators are the users of an admin panel of a Strapi application. Administrator accounts and roles are managed with the Role-Based Access Control (RBAC) feature. It is available in the *Administration panel* section of the  _Settings_ subnavigation.
The *Administration panel* section is divided into 2 sub-sections: *Roles* and *Users* (see [Managing administrators](managing-administrators.md)).
@@ -25,7 +26,7 @@ By default, 3 administrator roles are defined for any Strapi application:
- Editor: to be able to create content, and manage and publish any content.
- Super Admin: to be able to access all features and settings. This is the role attributed by default to the first administrator at the creation of the Strapi application.
-::: warning IMPORTANT
+::: caution
If you use your Strapi application with the Community Edition (see [Pricing and Plans](https://strapi.io/pricing-self-hosted)), your use of the RBAC feature will be limited. Only the 3 default roles are available, as you cannot create more roles and cannot delete the default ones. It is however possible to edit them, but to an extent:
- You can only configure permissions for the content-types, but not for the plugins and settings of the Strapi application.
@@ -41,8 +42,8 @@ On the top right side of the *Administration panel > Roles* interface, an **Add
To create a new role, click on the **Add new role** button.
Clicking on the **Add new role** button will redirect you to the roles edition interface, where you will be able to edit the role's details and configure its permissions (see [Editing a role](#editing-role-s-details)).
-::: tip 💡 TIP
-In the *Roles* interface, from the table, you can click on the duplicate button to create a new role by duplicating an existing one.
+::: tip
+In the *Roles* interface, from the table, you can click on the duplicate button  to create a new role by duplicating an existing one.
:::
## Deleting a role
@@ -51,20 +52,16 @@ Administrator roles can be deleted from the *Administration panel > Roles* inter
To delete a role:
-1. Click on the trash button on the right side of the role's record.
+1. Click on the delete button  on the right side of the role's record.
2. In the deletion window, click on the **Yes, confirm** button to confirm the deletion.
-::: tip 💡 TIP
-You also have the possibility to delete multiple roles at the same time. To do so, select the roles by ticking the box on the left side of the roles' record. Then, click on the **Delete** button in the top right corner of the table.
-:::
-
## Editing a role
-The role edition interface allows to edit the details of an administrator role as well as configure in detail the permissions to all sections of your Strapi application. It is accessible from *Administration panel > Roles* either after clicking on the edit button on the right side of a role's record, or after clicking on the **Add new role** button (see [Creating a new role](#creating-a-new-role)).
+The role edition interface allows to edit the details of an administrator role as well as configure in detail the permissions to all sections of your Strapi application. It is accessible from *Administration panel > Roles* either after clicking on the edit button  on the right side of a role's record, or after clicking on the **Add new role** button (see [Creating a new role](#creating-a-new-role)).
-::: warning IMPORTANT
+::: caution
It isn't possible to edit the permissions of the Super Admin role. All configurations are in read-only mode.
:::
@@ -72,7 +69,7 @@ It isn't possible to edit the permissions of the Super Admin role. All configura
The details area of an administrator role editing interface allow to define the name of the role, and to give it a description that should help other administrators understand what the role gives access to.
-::: tip 💡 TIP
+::: tip
In the top right corner, you can see a counter indicating how many administrators have been attributed the role.
:::
@@ -85,15 +82,15 @@ To edit a role's details, follow the instructions from the table below:
### Configuring role's permissions
-The permissions area of an administrator role editing interface allows to configure in detail what actions an administrator can do for any part of the Strapi application. It is displayed as a table, split into 4 categories: Collection Types, Single Types, Plugins and Settings.
+The permissions area of an administrator role editing interface allows to configure in detail what actions an administrator can do for any part of the Strapi application. It is displayed as a table, split into 4 categories: Collection types, Single types, Plugins and Settings.
-#### Collection and Single Types
+#### Collection and Single types
-The Collection Types and Single Types categories respectively list all available collection and single types for the Strapi application. For each content type, the administrators can have the permission to perform the following actions: create, read, update, delete and publish.
+The Collection types and Single types categories respectively list all available collection and single types for the Strapi application. For each content type, the administrators can have the permission to perform the following actions: create, read, update, delete and publish.
-To configure Collection or Single Types permissions for a role:
+To configure Collection or Single types permissions for a role:
-1. Go to the Collection Types or Single Types category of the permissions table.
+1. Go to the Collection types or Single types category of the permissions table.
2. Tick the box on the left of the name of the content type to give access to. By default, all actions can be performed for all fields of the content type.
3. (optional - Enterprise Edition only) Untick the action-related boxes to prevent actions of your choice.
4. (optional) Click the name of the content type to display its full list of fields. Untick the field and action-related boxes to prevent access and/or action for the fields of your choice. If the [Internationalization plugin](/user-docs/latest/plugins/strapi-plugins.md#internationalization-plugin) is installed, define also what permissions should be granted for each available locale.
@@ -110,7 +107,7 @@ To configure plugins or settings permissions for a role:
2. Click on the name of the sub-category which permissions to configure, to display all available permissions.
3. Tick the boxes of the permissions the role should give access to. You can refer to the table below for more information and instructions.
-:::: tabs
+:::: tabs card
::: tab Plugins
@@ -118,9 +115,9 @@ By default, plugins permissions can be configured for the Content-Type Builder,
| Plugin name | Permissions |
| -------------------- | ----------- |
-| Content-Type-Builder | - General
- "Read" - gives access to the Content-Types Builder plugin in read-only mode
|
-| Upload
*(Media Library)* | - General
- "Access the Media Library" - gives access to the Media Library plugin
- Assets
- "Create (upload)" - allows to upload media files
- "Update (crop, details, replace) + delete" - allows to edit uploaded media files
- "Download" - allows to download uploaded media files
- "Copy link" - allows to copy the link of an uploaded media file
|
| Content-Manager | - Single types
- "Configure view" - allows to configure the edit view of a single type
- Collection types
- "Configure view" - allows to configure the edit view of a collection type
- Components
- "Configure Layout" - allows to configure the layout of a component
|
+| Content-Type-Builder | - General
- "Read" - gives access to the Content-Type Builder plugin in read-only mode
|
+| Upload
*(Media Library)* | - General
- "Access the Media Library" - gives access to the Media Library plugin
- Assets
- "Create (upload)" - allows to upload media files
- "Update (crop, details, replace) + delete" - allows to edit uploaded media files
- "Download" - allows to download uploaded media files
- "Copy link" - allows to copy the link of an uploaded media file
|
| Users-Permissions | - Roles
- "Create" - allows to create end-user roles
- "Read" - allows to see created end-user roles
- "Update" - allows to edit end-user roles
- "Delete" - allows to delete end-user roles
- Providers
- "Read" - allows to see providers
- "Edit" - allows to edit providers
- Email Templates
- "Read" - allows to access the email templates
- "Edit" - allows to edit email templates
- Advanced settings
- "Read" - allows to access the advanced settings of the Users & Permissions plugin
- "Edit" - allows to edit advanced settings
👉 Path reminder to the Users & Permissions plugin:
*General > Settings > Users & Permissions plugin* |
:::
@@ -132,6 +129,8 @@ Settings permissions can be configured for all settings accessible from *General
| Setting name | Permissions |
| ----------------------- | ----------- |
| Media Library | - General
- "Access the Media Library settings page" - gives access to Media Library settings
👉 Path reminder to Media Library settings:
*General > Settings > Global Settings - Media Library* |
+| Internationalization | - Locales
- "Create" - allows to create new locales
- "Read" - allows to see available locales
- "Update" - allows to edit available locales
- "Delete" - allows to delete locales
👉 Path reminder to the Internationalization settings:
*General > Settings > Global Settings - Internationalization* |
+| Single sign on | - Options
- "Read" - allows to access the SSO settings
- "Update" - allows to edit the SSO settings
👉 Path reminder to the SSO settings:
*General > Settings > Global Settings - Single Sign-On* |
| Plugins and Marketplace | - Marketplace
- "Access the Marketplace" - gives access to the Marketplace
- Plugins
- "Install (only for dev env)" - allows to install new plugins when in a development environment
- "Uninstall (only for dev env)" - allows to uninstall plugins when in a development environment
|
| Webhooks | - General
- "Create" - allows to create webhooks
- "Read" - allows to see created webhooks
- "Update" - allows to edit webhooks
- "Delete" - allows to delete webhooks
👉 Path reminder to Webhook settings:
*General > Settings > Global Settings - Webhook* |
| Users and Roles | - Users
- "Create (invite)" - allows to create administrator accounts
- "Read" - allows to see existing administrator accounts
- "Update" - allows to edit administrator accounts
- "Delete" - allows to delete administrator accounts
- Roles
- "Create" - allows to create administrator roles
- "Read" - allows to see created administrator roles
- "Update" - allows to edit administrator roles
- "Delete" - allows to delete administrator roles
👉 Path reminder to the RBAC feature:
*General > Settings > Administration Panel* |
@@ -149,11 +148,11 @@ For each permission of each category, a **Settings** button is displayed. It all
- the administrator must be the creator,
- the administrator must have the same role as the creator.
-::: tip NOTE
-Other custom conditions can be available if they have been created beforehand for your Strapi application (see [Role-Based Access Control](/developer-docs/latest/setup-deployment-guides/configurations.md#role-based-access-control)).
+::: note
+Other custom conditions can be available if they have been created beforehand for your Strapi application (see [Role-Based Access Control](/developer-docs/latest/setup-deployment-guides/configurations/optional/rbac.md).
:::
-
+
To set custom conditions:
@@ -161,9 +160,13 @@ To set custom conditions:
2. In the *Define conditions* window, each available permission can be customised with a specific condition. Click on the drop-down list related to the permission you want to customise.
3. Define the custom condition for the chosen permission. You can either:
- Tick the Default option for all available additional conditions to be applied.
- - Click on the arrow button  to see the available additional conditions and tick only the chosen one(s).
+ - Click on the arrow button  to see the available additional conditions and tick only the chosen one(s).
4. Click on the **Apply** button.
-::: warning IMPORTANT
+::: tip
+Once a custom condition is set for a permission, a dot is displayed next to the permission's name and the **Settings** button.
+:::
+
+::: caution
Custom conditions can only be set for permissions that have been ticked to be granted for the role. If not, when clicking the **Settings** button, the window that opens will remain empty, as no custom condition option will be available.
:::
diff --git a/docs/user-docs/latest/users-roles-permissions/configuring-end-users-roles.md b/docs/user-docs/latest/users-roles-permissions/configuring-end-users-roles.md
index 53e81f96e8..10e981c121 100644
--- a/docs/user-docs/latest/users-roles-permissions/configuring-end-users-roles.md
+++ b/docs/user-docs/latest/users-roles-permissions/configuring-end-users-roles.md
@@ -1,13 +1,16 @@
---
title: Configure End-users Roles - Strapi User Guide
description: Instructions to configure the end-users roles for a front-end application using the Users & Permissions plugin
+canonicalUrl: https://docs.strapi.io/user-docs/latest/users-roles-permissions/configuring-end-users-roles.html
---
# Configuring end-users roles
-End-users are the users who consume the content that is created and managed with a Strapi application and displayed on front-end applications (e.g. websites, mobile applications, connected devices etc.). Unlike the administrators, they do not have access to the admin panel. End-users are managed with the Users & Permissions plugin (see [Users & Permissions plugin](../plugins/strapi-plugins.md#users-permissions-plugin)). This plugin is however not entirely managed and configured from one same place of the admin panel: end-users accounts are managed from the Content Manager (see [Managing end-user accounts](../users-roles-permissions/managing-end-users.md)) but end-users roles and permissions are managed in the Settings interface.
+End-users are the users who consume the content that is created and managed with a Strapi application and displayed on front-end applications (e.g. websites, mobile applications, connected devices etc.). Unlike the administrators, they do not have access to the admin panel.
-The configurations of the end-users roles and permissions are available in the *Users & Permissions plugin* section of the Settings interface, accessible from *General > Settings* in the main navigation of the admin panel.
+With the [Users & Permissions plugin](../plugins/strapi-plugins.md#users-permissions-plugin) activated, it is possible to manage end-users. This plugin is however not entirely managed and configured from one same place of the admin panel: end-users accounts are managed from the Content Manager (see [Managing end-user accounts](../users-roles-permissions/managing-end-users.md)) but end-users roles and permissions are managed in the Settings interface.
+
+The configurations of the end-users roles and permissions are available in the *Users & Permissions plugin* section of the  _Settings_ subnavigation.
@@ -19,12 +22,16 @@ From this interface, it is possible to:
- delete an end-user role (see [Deleting a role](#deleting-a-role)),
- or access information regarding an end-user role, and edit it (see [Editing a role](#editing-a-role)).
+::: tip
+Click the search button  above the table to use a text search and find one of your administrator roles more quickly!
+:::
+
By default, 2 end-user roles are defined for any Strapi application:
- Authenticated: for end-users to access content only if they are logged in to a front-end application.
- Public: for end-users to access content without being logged in to a front-end application.
-::: tip NOTE
+::: note
The end-user role attributed by default to all new end-users can be defined in the *Advanced settings* sub-section of *Users & Permissions plugin* (see [Configuring advanced settings](../settings/configuring-users-permissions-plugin-settings.md#configuring-advanced-settings)).
:::
@@ -41,14 +48,14 @@ Although the 2 default end-users roles cannot be deleted, the other ones can, as
To delete a role:
-1. Click on the trash button on the right side of the role's record.
-2. In the deletion window, click on the **Yes, confirm** button to confirm the deletion.
+1. Click on the delete button  on the right side of the role's record.
+2. In the deletion window, click on the  **Confirm** button to confirm the deletion.
## Editing a role
-The role edition interface allows to edit the details of an end-user role as well as to configure in detail the permissions to access the content of a front-end application. It is accessible from *Users & Permissions plugin > Roles* either after clicking on the edit button on the right side of a role's record, or after clicking on the **Add new role** button (see [Creating a new role](#creating-a-new-role)).
+The role edition interface allows to edit the details of an end-user role as well as to configure in detail the permissions to access the content of a front-end application. It is accessible from *Users & Permissions plugin > Roles* either after clicking on the edit button  on the right side of a role's record, or after clicking on the **Add new role** button (see [Creating a new role](#creating-a-new-role)).
### Editing role's details
@@ -71,6 +78,6 @@ To configure permissions for an end-user role:
2. Tick the boxes of the actions and permissions to grant for the role.
3. Click on the **Save** button.
-::: tip 💡 TIP
+::: tip
When ticking an action or permission box, related bound routes of the API are displayed in the right side of the interface.
:::
\ No newline at end of file
diff --git a/docs/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.md b/docs/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.md
index 018352a31a..bc2d8bce2a 100644
--- a/docs/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.md
+++ b/docs/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.md
@@ -1,12 +1,13 @@
---
title: Users, Roles & Permissions - Strapi User Guide
description: Introduction to the system of permissions of Strapi which gives access to features of the admin panel.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/users-roles-permissions/introduction-to-users-roles-permissions.html
---
# Introduction to users, roles & permissions
Some features of the admin panel, as well as the content managed with Strapi itself, are ruled by a system of permissions. These permissions can be assigned to roles, which are associated with the users who have access to the admin panel, the administrators. But it is also possible to grant permissions more publicly, to give access to content to the end-users of your Strapi application.
-Depending on what users and their roles and permissions you want to manage, you should either use the Role Based Access Control (RBAC) feature, or the Users & Permissions plugin. Both are accessible from _General > Settings_ in the main navigation of the admin panel.
+Depending on what users and their roles and permissions you want to manage, you should either use the Role Based Access Control (RBAC) feature, or the Users & Permissions plugin. Both are managed from  _Settings_, accessible from the main navigation of the admin panel.
diff --git a/docs/user-docs/latest/users-roles-permissions/managing-administrators.md b/docs/user-docs/latest/users-roles-permissions/managing-administrators.md
index f704837f19..5f697adc64 100644
--- a/docs/user-docs/latest/users-roles-permissions/managing-administrators.md
+++ b/docs/user-docs/latest/users-roles-permissions/managing-administrators.md
@@ -1,11 +1,12 @@
---
title: Managing Administrators - Strapi User Guide
description: Instructions to manage the administrators of a Strapi application with the Role-Based Access Control (RBAC) feature.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/users-roles-permissions/managing-administrators.html
---
# Managing administrator accounts
-Administrators are the users of an admin panel of a Strapi application. Administrator accounts and roles are managed with the Role-Based Access Control (RBAC) feature. It is available in the *Administration panel* section of the Settings interface, accessible from *General > Settings* in the main navigation of the admin panel.
+Administrators are the users of an admin panel of a Strapi application. Administrator accounts and roles are managed with the Role-Based Access Control (RBAC) feature. It is available in the *Administration panel* section of the section of the  _Settings_ subnavigation.
The *Administration panel* section is divided into 2 sub-sections: *Roles* (see [Configuring administrator roles](configuring-administrator-roles.md)) and *Users*.
@@ -16,35 +17,42 @@ The *Users* sub-section of *Administration panel* displays a table listing all t
From this interface, it is possible to:
- make a textual search (1) to find specific administrators,
-- sort the administrator accounts (2) to make it easier to view the list of administrator accounts,
- set filters (2) to find specific administrators,
-- create a new administrator account (see [Creating a new account](#creating-a-new-account)),
+- create a new administrator account (see [Creating a new account](#creating-a-new-account)) (3),
- delete an administrator account (see [Deleting an account](#deleting-an-account)),
- or access information regarding an administrator account, and edit it (see [Editing an account](#editing-an-account)).
For each administrator listed in the table, their main account information are displayed, including name, email and attributed role. The status of their account is also indicated: active or inactive, depending on whether the administrator has already logged in to activate the account or not.
+::: tip
+Sorting can be enabled for most fields displayed in the table. Click on a field name, in the header of the table, to sort on that field.
+:::
+
## Creating a new account
-On the top right side of the *Administration panel > Users* interface, a **Create new User** button is displayed. It allows to create a new administrator account for your Strapi application.
+On the top right side of the *Administration panel > Users* interface, a **Create new user** button is displayed. It allows to create a new administrator account for your Strapi application.
To create a new administrator account:
-1. Click on the **Create new User** button.
-2. In the *Add new user* window, fill in the following information about the new administrator:
+1. Click on the **Create new user** button.
+2. In the *Create new user* window, fill in the Details information about the new administrator:
| User information | Instructions |
| ----------------- | ------------------------------------------------------------------------------------------------------- |
| First name | (mandatory) Write the administrator's first name in the textbox. |
| Last name | (mandatory) Write the administrator's last name in the textbox. |
| Email | (mandatory) Write the administrator's complete email address in the textbox. |
-| User's role | (mandatory) Choose from the drop-down list the role to attribute to the new administrator. |
-3. Click on the **Create user** button in the bottom right corner of the *Add new user* window.
-4. A URL appears at the top of the window: it is the URL to send the new administrator for them to log in for the first time to your Strapi application. Click the copy button to copy the URL.
-5. Click on the **Continue** button in the bottom right corner to finish the new administrator account creation. The new administrator should now be listed in the table.
+3. Fill in the Login settings about the new administrator:
+
+| User's roles | (mandatory) Choose from the drop-down list the role to attribute to the new administrator. |
+| Connect with SSO | (optional - Enterprise Edition only) Click **ON** or **OFF** to connect the new administrator account with SSO. |
-::: tip NOTE
+4. Click on the **Create user** button in the bottom right corner of the *Add new user* window.
+5. A URL appears at the top of the window: it is the URL to send the new administrator for them to log in for the first time to your Strapi application. Click the copy button  to copy the URL.
+6. Click on the **Finish** button in the bottom right corner to finish the new administrator account creation. The new administrator should now be listed in the table.
+
+::: note
The administrator invitation URL is accessible from the administrator's account until it has been activated.
:::
@@ -54,7 +62,7 @@ Administrator accounts can be deleted from the *Administration panel > Users* in
To delete an administrator:
-1. Click on the trash button on the right side of the account's record, or select one or more accounts by ticking the boxes on the left side of the accounts' records then click on the **Delete** button in the top right corner.
+1. Click on the delete button  on the right side of the account's record, or select one or more accounts by ticking the boxes on the left side of the accounts' records then click on the  **Delete** button above the table.
2. In the deletion window, click on the **Yes, confirm** button to confirm the deletion.
## Editing an account
@@ -75,16 +83,13 @@ To edit an administrator account:
| Email | Write the administrator's complete email address in the textbox. |
| Username | Write the administrator's username in the textbox. |
| Password | Write the new administrator account's password in the textbox. |
-| Confirmation password | Write the new password in the textbox for confirmation. |
+| Password confirmation | Write the new password in the textbox for confirmation. |
| Active | Click on **ON** to activate the administrator's account. |
-3. (optional) In the *Attributed roles* area, edit the role of the administrator:
+3. (optional) In the *Login settings* area, edit the role of the administrator:
- Click on the drop-down list to choose a new role, and/or add it to the already attributed one.
- - Click on the  to delete an already attributed role.
+ - Click on the delete button  to delete an already attributed role.
4. Click on the **Save** button in the top right corner.
-::: tip 💡 TIP
-You can go back to the original configurations of the account by clicking on the **Reset** button in the top right corner of the interface.
-:::
diff --git a/docs/user-docs/latest/users-roles-permissions/managing-end-users.md b/docs/user-docs/latest/users-roles-permissions/managing-end-users.md
index 306bc3b2fb..f99d83b7ac 100644
--- a/docs/user-docs/latest/users-roles-permissions/managing-end-users.md
+++ b/docs/user-docs/latest/users-roles-permissions/managing-end-users.md
@@ -1,11 +1,14 @@
---
title: Managing End-Users Accounts - Strapi User Guide
-description: Instructions to manage the end-users of a front-end application with the Users & Permissions plugin
+description: Instructions to manage the end-users of a front-end application with the Users & Permissions plugin.
+canonicalUrl: https://docs.strapi.io/user-docs/latest/users-roles-permissions/managing-end-users.html
---
# Managing end-users accounts
-End-users are the users who consume the content that is created and managed with a Strapi application and displayed on front-end applications (e.g. websites, mobile applications, connected devices etc.). Unlike the administrators, they do not have access to the admin panel. End-users are managed with the Users & Permissions plugin (see [Users & Permissions plugin](../plugins/strapi-plugins.md#users-permissions-plugin)). This plugin is however not entirely managed and configured from one same place of the admin panel: end-users roles and permissions are managed in the Settings interface (see [Configuring end-users roles](../users-roles-permissions/configuring-end-users-roles.md)), but end-users accounts are managed from the Content Manager.
+End-users are the users who consume the content that is created and managed with a Strapi application and displayed on front-end applications (e.g. websites, mobile applications, connected devices etc.). Unlike the administrators, they do not have access to the admin panel.
+
+With the [Users & Permissions plugin](../plugins/strapi-plugins.md#users-permissions-plugin) activated, it is possible to manage end-users. This plugin is however not entirely managed and configured from one same place of the admin panel: end-users roles and permissions are managed in the  _Settings_ interface (see [Configuring end-users roles](../users-roles-permissions/configuring-end-users-roles.md)), but end-users accounts are managed from the  _Content Manager_.
With the Users & Permissions plugin, the end-users and their account information are managed as a content-type. When the plugin is installed on a Strapi application, 3 collection types are automatically created (see [Users & Permissions plugin](../plugins/strapi-plugins.md#users-permissions-plugin)), including "User" which is the only one available directly in the Content Manager.
@@ -13,14 +16,14 @@ With the Users & Permissions plugin, the end-users and their account information
Registering new end-users in a front-end application with the Users & Permissions plugin consists in adding a new entry to the User collection-type (see [Introduction to the Content Mananger](../content-manager/introduction-to-content-manager.md) for more information about the Content Manager).
-::: tip IMPORTANT
+::: note
If end-users can register themselves on your front-end application (see [Managing Users & Permissions plugin settings](../settings/configuring-users-permissions-plugin-settings.md)), a new entry will automatically be created and the fields of that entry will be filled up with the information indicated by the end-user. All fields can however be edited by an administrator of the Strapi application.
:::
To create a new end-user account:
1. Go to the User collection type in the Content Manager.
-2. Click on the **Add New user** button in the top right corner.
+2. Click on the **Add new entry** button in the top right corner.
3. Fill in the default fields of the entry. Additional fields added specifically for your Strapi application by your administrators may be displayed as well.
| Field | Instructions |
diff --git a/docs/yarn.lock b/docs/yarn.lock
index dc8ba6e09e..0616e7ecc1 100644
--- a/docs/yarn.lock
+++ b/docs/yarn.lock
@@ -2,363 +2,407 @@
# yarn lockfile v1
-"@babel/code-frame@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.12.13.tgz#dcfc826beef65e75c50e21d3837d7d95798dd658"
- integrity sha512-HV1Cm0Q3ZrpCR93tkWOYiuYIgLxZXZFVG2VgK+MBWjUqZTundupbfx2aXarXuw5Ko5aMcjtJgbSs4vUGBS5v6g==
+"@babel/code-frame@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.14.5.tgz#23b08d740e83f49c5e59945fbf1b43e80bbf4edb"
+ integrity sha512-9pzDqyc6OLDaqe+zbACgFkb6fKMNG6CObKpnYXChRsvYGyEdc7CA2BaqeOM+vOtCS5ndmJicPJhKAwYRI6UfFw==
dependencies:
- "@babel/highlight" "^7.12.13"
+ "@babel/highlight" "^7.14.5"
-"@babel/compat-data@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.12.13.tgz#27e19e0ed3726ccf54067ced4109501765e7e2e8"
- integrity sha512-U/hshG5R+SIoW7HVWIdmy1cB7s3ki+r3FpyEZiCgpi4tFgPnX/vynY80ZGSASOIrUM6O7VxOgCZgdt7h97bUGg==
+"@babel/compat-data@^7.13.11", "@babel/compat-data@^7.15.0":
+ version "7.15.0"
+ resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.15.0.tgz#2dbaf8b85334796cafbb0f5793a90a2fc010b176"
+ integrity sha512-0NqAC1IJE0S0+lL1SWFMxMkz1pKCNCjI4tr2Zx4LJSXxCLAdr6KyArnY+sno5m3yH9g737ygOyPABDsnXkpxiA==
"@babel/core@^7.11.0", "@babel/core@^7.8.4":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.12.13.tgz#b73a87a3a3e7d142a66248bf6ad88b9ceb093425"
- integrity sha512-BQKE9kXkPlXHPeqissfxo0lySWJcYdEP0hdtJOH/iJfDdhOCcgtNCjftCJg3qqauB4h+lz2N6ixM++b9DN1Tcw==
- dependencies:
- "@babel/code-frame" "^7.12.13"
- "@babel/generator" "^7.12.13"
- "@babel/helper-module-transforms" "^7.12.13"
- "@babel/helpers" "^7.12.13"
- "@babel/parser" "^7.12.13"
- "@babel/template" "^7.12.13"
- "@babel/traverse" "^7.12.13"
- "@babel/types" "^7.12.13"
+ version "7.15.5"
+ resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.15.5.tgz#f8ed9ace730722544609f90c9bb49162dc3bf5b9"
+ integrity sha512-pYgXxiwAgQpgM1bNkZsDEq85f0ggXMA5L7c+o3tskGMh2BunCI9QUwB9Z4jpvXUOuMdyGKiGKQiRe11VS6Jzvg==
+ dependencies:
+ "@babel/code-frame" "^7.14.5"
+ "@babel/generator" "^7.15.4"
+ "@babel/helper-compilation-targets" "^7.15.4"
+ "@babel/helper-module-transforms" "^7.15.4"
+ "@babel/helpers" "^7.15.4"
+ "@babel/parser" "^7.15.5"
+ "@babel/template" "^7.15.4"
+ "@babel/traverse" "^7.15.4"
+ "@babel/types" "^7.15.4"
convert-source-map "^1.7.0"
debug "^4.1.0"
- gensync "^1.0.0-beta.1"
+ gensync "^1.0.0-beta.2"
json5 "^2.1.2"
- lodash "^4.17.19"
- semver "^5.4.1"
+ semver "^6.3.0"
source-map "^0.5.0"
-"@babel/generator@^7.12.13":
- version "7.12.15"
- resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.12.15.tgz#4617b5d0b25cc572474cc1aafee1edeaf9b5368f"
- integrity sha512-6F2xHxBiFXWNSGb7vyCUTBF8RCLY66rS0zEPcP8t/nQyXjha5EuK4z7H5o7fWG8B4M7y6mqVWq1J+1PuwRhecQ==
+"@babel/generator@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.15.4.tgz#85acb159a267ca6324f9793986991ee2022a05b0"
+ integrity sha512-d3itta0tu+UayjEORPNz6e1T3FtvWlP5N4V5M+lhp/CxT4oAA7/NcScnpRyspUMLK6tu9MNHmQHxRykuN2R7hw==
dependencies:
- "@babel/types" "^7.12.13"
+ "@babel/types" "^7.15.4"
jsesc "^2.5.1"
source-map "^0.5.0"
-"@babel/helper-annotate-as-pure@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.12.13.tgz#0f58e86dfc4bb3b1fcd7db806570e177d439b6ab"
- integrity sha512-7YXfX5wQ5aYM/BOlbSccHDbuXXFPxeoUmfWtz8le2yTkTZc+BxsiEnENFoi2SlmA8ewDkG2LgIMIVzzn2h8kfw==
+"@babel/helper-annotate-as-pure@^7.14.5", "@babel/helper-annotate-as-pure@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.15.4.tgz#3d0e43b00c5e49fdb6c57e421601a7a658d5f835"
+ integrity sha512-QwrtdNvUNsPCj2lfNQacsGSQvGX8ee1ttrBrcozUP2Sv/jylewBP/8QFe6ZkBsC8T/GYWonNAWJV4aRR9AL2DA==
dependencies:
- "@babel/types" "^7.12.13"
+ "@babel/types" "^7.15.4"
-"@babel/helper-builder-binary-assignment-operator-visitor@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.12.13.tgz#6bc20361c88b0a74d05137a65cac8d3cbf6f61fc"
- integrity sha512-CZOv9tGphhDRlVjVkAgm8Nhklm9RzSmWpX2my+t7Ua/KT616pEzXsQCjinzvkRvHWJ9itO4f296efroX23XCMA==
+"@babel/helper-builder-binary-assignment-operator-visitor@^7.14.5":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.15.4.tgz#21ad815f609b84ee0e3058676c33cf6d1670525f"
+ integrity sha512-P8o7JP2Mzi0SdC6eWr1zF+AEYvrsZa7GSY1lTayjF5XJhVH0kjLYUZPvTMflP7tBgZoe9gIhTa60QwFpqh/E0Q==
dependencies:
- "@babel/helper-explode-assignable-expression" "^7.12.13"
- "@babel/types" "^7.12.13"
+ "@babel/helper-explode-assignable-expression" "^7.15.4"
+ "@babel/types" "^7.15.4"
-"@babel/helper-compilation-targets@^7.12.13", "@babel/helper-compilation-targets@^7.9.6":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.12.13.tgz#d689cdef88810aa74e15a7a94186f26a3d773c98"
- integrity sha512-dXof20y/6wB5HnLOGyLh/gobsMvDNoekcC+8MCV2iaTd5JemhFkPD73QB+tK3iFC9P0xJC73B6MvKkyUfS9cCw==
+"@babel/helper-compilation-targets@^7.13.0", "@babel/helper-compilation-targets@^7.15.4", "@babel/helper-compilation-targets@^7.9.6":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.15.4.tgz#cf6d94f30fbefc139123e27dd6b02f65aeedb7b9"
+ integrity sha512-rMWPCirulnPSe4d+gwdWXLfAXTTBj8M3guAf5xFQJ0nvFY7tfNAFnWdqaHegHlgDZOCT4qvhF3BYlSJag8yhqQ==
dependencies:
- "@babel/compat-data" "^7.12.13"
- "@babel/helper-validator-option" "^7.12.11"
- browserslist "^4.14.5"
- semver "^5.5.0"
+ "@babel/compat-data" "^7.15.0"
+ "@babel/helper-validator-option" "^7.14.5"
+ browserslist "^4.16.6"
+ semver "^6.3.0"
-"@babel/helper-create-class-features-plugin@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.12.13.tgz#0f1707c2eec1a4604f2a22a6fb209854ef2a399a"
- integrity sha512-Vs/e9wv7rakKYeywsmEBSRC9KtmE7Px+YBlESekLeJOF0zbGUicGfXSNi3o+tfXSNS48U/7K9mIOOCR79Cl3+Q==
+"@babel/helper-create-class-features-plugin@^7.14.5", "@babel/helper-create-class-features-plugin@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.15.4.tgz#7f977c17bd12a5fba363cb19bea090394bf37d2e"
+ integrity sha512-7ZmzFi+DwJx6A7mHRwbuucEYpyBwmh2Ca0RvI6z2+WLZYCqV0JOaLb+u0zbtmDicebgKBZgqbYfLaKNqSgv5Pw==
dependencies:
- "@babel/helper-function-name" "^7.12.13"
- "@babel/helper-member-expression-to-functions" "^7.12.13"
- "@babel/helper-optimise-call-expression" "^7.12.13"
- "@babel/helper-replace-supers" "^7.12.13"
- "@babel/helper-split-export-declaration" "^7.12.13"
+ "@babel/helper-annotate-as-pure" "^7.15.4"
+ "@babel/helper-function-name" "^7.15.4"
+ "@babel/helper-member-expression-to-functions" "^7.15.4"
+ "@babel/helper-optimise-call-expression" "^7.15.4"
+ "@babel/helper-replace-supers" "^7.15.4"
+ "@babel/helper-split-export-declaration" "^7.15.4"
-"@babel/helper-create-regexp-features-plugin@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.12.13.tgz#0996d370a92896c612ae41a4215544bd152579c0"
- integrity sha512-XC+kiA0J3at6E85dL5UnCYfVOcIZ834QcAY0TIpgUVnz0zDzg+0TtvZTnJ4g9L1dPRGe30Qi03XCIS4tYCLtqw==
+"@babel/helper-create-regexp-features-plugin@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.14.5.tgz#c7d5ac5e9cf621c26057722fb7a8a4c5889358c4"
+ integrity sha512-TLawwqpOErY2HhWbGJ2nZT5wSkR192QpN+nBg1THfBfftrlvOh+WbhrxXCH4q4xJ9Gl16BGPR/48JA+Ryiho/A==
dependencies:
- "@babel/helper-annotate-as-pure" "^7.12.13"
+ "@babel/helper-annotate-as-pure" "^7.14.5"
regexpu-core "^4.7.1"
-"@babel/helper-explode-assignable-expression@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.12.13.tgz#0e46990da9e271502f77507efa4c9918d3d8634a"
- integrity sha512-5loeRNvMo9mx1dA/d6yNi+YiKziJZFylZnCo1nmFF4qPU4yJ14abhWESuSMQSlQxWdxdOFzxXjk/PpfudTtYyw==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-function-name@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.12.13.tgz#93ad656db3c3c2232559fd7b2c3dbdcbe0eb377a"
- integrity sha512-TZvmPn0UOqmvi5G4vvw0qZTpVptGkB1GL61R6lKvrSdIxGm5Pky7Q3fpKiIkQCAtRCBUwB0PaThlx9vebCDSwA==
- dependencies:
- "@babel/helper-get-function-arity" "^7.12.13"
- "@babel/template" "^7.12.13"
- "@babel/types" "^7.12.13"
-
-"@babel/helper-get-function-arity@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-get-function-arity/-/helper-get-function-arity-7.12.13.tgz#bc63451d403a3b3082b97e1d8b3fe5bd4091e583"
- integrity sha512-DjEVzQNz5LICkzN0REdpD5prGoidvbdYk1BVgRUOINaWJP2t6avB27X1guXK1kXNrX0WMfsrm1A/ZBthYuIMQg==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-hoist-variables@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.12.13.tgz#13aba58b7480b502362316ea02f52cca0e9796cd"
- integrity sha512-KSC5XSj5HreRhYQtZ3cnSnQwDzgnbdUDEFsxkN0m6Q3WrCRt72xrnZ8+h+pX7YxM7hr87zIO3a/v5p/H3TrnVw==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-member-expression-to-functions@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.12.13.tgz#c5715695b4f8bab32660dbdcdc2341dec7e3df40"
- integrity sha512-B+7nN0gIL8FZ8SvMcF+EPyB21KnCcZHQZFczCxbiNGV/O0rsrSBlWGLzmtBJ3GMjSVMIm4lpFhR+VdVBuIsUcQ==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-module-imports@^7.0.0", "@babel/helper-module-imports@^7.12.13", "@babel/helper-module-imports@^7.8.3":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.12.13.tgz#ec67e4404f41750463e455cc3203f6a32e93fcb0"
- integrity sha512-NGmfvRp9Rqxy0uHSSVP+SRIW1q31a7Ji10cLBcqSDUngGentY4FRiHOFZFE1CLU5eiL0oE8reH7Tg1y99TDM/g==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-module-transforms@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.12.13.tgz#01afb052dcad2044289b7b20beb3fa8bd0265bea"
- integrity sha512-acKF7EjqOR67ASIlDTupwkKM1eUisNAjaSduo5Cz+793ikfnpe7p4Q7B7EWU2PCoSTPWsQkR7hRUWEIZPiVLGA==
+"@babel/helper-define-polyfill-provider@^0.2.2":
+ version "0.2.3"
+ resolved "https://registry.yarnpkg.com/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.2.3.tgz#0525edec5094653a282688d34d846e4c75e9c0b6"
+ integrity sha512-RH3QDAfRMzj7+0Nqu5oqgO5q9mFtQEVvCRsi8qCEfzLR9p2BHfn5FzhSB2oj1fF7I2+DcTORkYaQ6aTR9Cofew==
dependencies:
+ "@babel/helper-compilation-targets" "^7.13.0"
"@babel/helper-module-imports" "^7.12.13"
- "@babel/helper-replace-supers" "^7.12.13"
- "@babel/helper-simple-access" "^7.12.13"
- "@babel/helper-split-export-declaration" "^7.12.13"
- "@babel/helper-validator-identifier" "^7.12.11"
- "@babel/template" "^7.12.13"
- "@babel/traverse" "^7.12.13"
- "@babel/types" "^7.12.13"
- lodash "^4.17.19"
-
-"@babel/helper-optimise-call-expression@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.12.13.tgz#5c02d171b4c8615b1e7163f888c1c81c30a2aaea"
- integrity sha512-BdWQhoVJkp6nVjB7nkFWcn43dkprYauqtk++Py2eaf/GRDFm5BxRqEIZCiHlZUGAVmtwKcsVL1dC68WmzeFmiA==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-plugin-utils@^7.0.0", "@babel/helper-plugin-utils@^7.10.4", "@babel/helper-plugin-utils@^7.12.13", "@babel/helper-plugin-utils@^7.8.0", "@babel/helper-plugin-utils@^7.8.3":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.12.13.tgz#174254d0f2424d8aefb4dd48057511247b0a9eeb"
- integrity sha512-C+10MXCXJLiR6IeG9+Wiejt9jmtFpxUc3MQqCmPY8hfCjyUGl9kT+B2okzEZrtykiwrc4dbCPdDoz0A/HQbDaA==
-
-"@babel/helper-remap-async-to-generator@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.12.13.tgz#170365f4140e2d20e5c88f8ba23c24468c296878"
- integrity sha512-Qa6PU9vNcj1NZacZZI1Mvwt+gXDH6CTfgAkSjeRMLE8HxtDK76+YDId6NQR+z7Rgd5arhD2cIbS74r0SxD6PDA==
- dependencies:
- "@babel/helper-annotate-as-pure" "^7.12.13"
- "@babel/helper-wrap-function" "^7.12.13"
- "@babel/types" "^7.12.13"
-
-"@babel/helper-replace-supers@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.12.13.tgz#00ec4fb6862546bd3d0aff9aac56074277173121"
- integrity sha512-pctAOIAMVStI2TMLhozPKbf5yTEXc0OJa0eENheb4w09SrgOWEs+P4nTOZYJQCqs8JlErGLDPDJTiGIp3ygbLg==
- dependencies:
- "@babel/helper-member-expression-to-functions" "^7.12.13"
- "@babel/helper-optimise-call-expression" "^7.12.13"
- "@babel/traverse" "^7.12.13"
- "@babel/types" "^7.12.13"
-
-"@babel/helper-simple-access@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-simple-access/-/helper-simple-access-7.12.13.tgz#8478bcc5cacf6aa1672b251c1d2dde5ccd61a6c4"
- integrity sha512-0ski5dyYIHEfwpWGx5GPWhH35j342JaflmCeQmsPWcrOQDtCN6C1zKAVRFVbK53lPW2c9TsuLLSUDf0tIGJ5hA==
- dependencies:
- "@babel/types" "^7.12.13"
-
-"@babel/helper-skip-transparent-expression-wrappers@^7.12.1":
- version "7.12.1"
- resolved "https://registry.yarnpkg.com/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.12.1.tgz#462dc63a7e435ade8468385c63d2b84cce4b3cbf"
- integrity sha512-Mf5AUuhG1/OCChOJ/HcADmvcHM42WJockombn8ATJG3OnyiSxBK/Mm5x78BQWvmtXZKHgbjdGL2kin/HOLlZGA==
- dependencies:
- "@babel/types" "^7.12.1"
-
-"@babel/helper-split-export-declaration@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.12.13.tgz#e9430be00baf3e88b0e13e6f9d4eaf2136372b05"
- integrity sha512-tCJDltF83htUtXx5NLcaDqRmknv652ZWCHyoTETf1CXYJdPC7nohZohjUgieXhv0hTJdRf2FjDueFehdNucpzg==
+ "@babel/helper-plugin-utils" "^7.13.0"
+ "@babel/traverse" "^7.13.0"
+ debug "^4.1.1"
+ lodash.debounce "^4.0.8"
+ resolve "^1.14.2"
+ semver "^6.1.2"
+
+"@babel/helper-explode-assignable-expression@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.15.4.tgz#f9aec9d219f271eaf92b9f561598ca6b2682600c"
+ integrity sha512-J14f/vq8+hdC2KoWLIQSsGrC9EFBKE4NFts8pfMpymfApds+fPqR30AOUWc4tyr56h9l/GA1Sxv2q3dLZWbQ/g==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-function-name@^7.14.5", "@babel/helper-function-name@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.15.4.tgz#845744dafc4381a4a5fb6afa6c3d36f98a787ebc"
+ integrity sha512-Z91cOMM4DseLIGOnog+Z8OI6YseR9bua+HpvLAQ2XayUGU+neTtX+97caALaLdyu53I/fjhbeCnWnRH1O3jFOw==
dependencies:
- "@babel/types" "^7.12.13"
+ "@babel/helper-get-function-arity" "^7.15.4"
+ "@babel/template" "^7.15.4"
+ "@babel/types" "^7.15.4"
-"@babel/helper-validator-identifier@^7.12.11":
- version "7.12.11"
- resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.12.11.tgz#c9a1f021917dcb5ccf0d4e453e399022981fc9ed"
- integrity sha512-np/lG3uARFybkoHokJUmf1QfEvRVCPbmQeUQpKow5cQ3xWrV9i3rUHodKDJPQfTVX61qKi+UdYk8kik84n7XOw==
+"@babel/helper-get-function-arity@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-get-function-arity/-/helper-get-function-arity-7.15.4.tgz#098818934a137fce78b536a3e015864be1e2879b"
+ integrity sha512-1/AlxSF92CmGZzHnC515hm4SirTxtpDnLEJ0UyEMgTMZN+6bxXKg04dKhiRx5Enel+SUA1G1t5Ed/yQia0efrA==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-hoist-variables@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.15.4.tgz#09993a3259c0e918f99d104261dfdfc033f178df"
+ integrity sha512-VTy085egb3jUGVK9ycIxQiPbquesq0HUQ+tPO0uv5mPEBZipk+5FkRKiWq5apuyTE9FUrjENB0rCf8y+n+UuhA==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-member-expression-to-functions@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.15.4.tgz#bfd34dc9bba9824a4658b0317ec2fd571a51e6ef"
+ integrity sha512-cokOMkxC/BTyNP1AlY25HuBWM32iCEsLPI4BHDpJCHHm1FU2E7dKWWIXJgQgSFiu4lp8q3bL1BIKwqkSUviqtA==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-module-imports@^7.0.0", "@babel/helper-module-imports@^7.12.13", "@babel/helper-module-imports@^7.14.5", "@babel/helper-module-imports@^7.15.4", "@babel/helper-module-imports@^7.8.3":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.15.4.tgz#e18007d230632dea19b47853b984476e7b4e103f"
+ integrity sha512-jeAHZbzUwdW/xHgHQ3QmWR4Jg6j15q4w/gCfwZvtqOxoo5DKtLHk8Bsf4c5RZRC7NmLEs+ohkdq8jFefuvIxAA==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-module-transforms@^7.14.5", "@babel/helper-module-transforms@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.15.4.tgz#962cc629a7f7f9a082dd62d0307fa75fe8788d7c"
+ integrity sha512-9fHHSGE9zTC++KuXLZcB5FKgvlV83Ox+NLUmQTawovwlJ85+QMhk1CnVk406CQVj97LaWod6KVjl2Sfgw9Aktw==
+ dependencies:
+ "@babel/helper-module-imports" "^7.15.4"
+ "@babel/helper-replace-supers" "^7.15.4"
+ "@babel/helper-simple-access" "^7.15.4"
+ "@babel/helper-split-export-declaration" "^7.15.4"
+ "@babel/helper-validator-identifier" "^7.14.9"
+ "@babel/template" "^7.15.4"
+ "@babel/traverse" "^7.15.4"
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-optimise-call-expression@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.15.4.tgz#f310a5121a3b9cc52d9ab19122bd729822dee171"
+ integrity sha512-E/z9rfbAOt1vDW1DR7k4SzhzotVV5+qMciWV6LaG1g4jeFrkDlJedjtV4h0i4Q/ITnUu+Pk08M7fczsB9GXBDw==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-plugin-utils@^7.0.0", "@babel/helper-plugin-utils@^7.10.4", "@babel/helper-plugin-utils@^7.12.13", "@babel/helper-plugin-utils@^7.13.0", "@babel/helper-plugin-utils@^7.14.5", "@babel/helper-plugin-utils@^7.8.0", "@babel/helper-plugin-utils@^7.8.3":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.14.5.tgz#5ac822ce97eec46741ab70a517971e443a70c5a9"
+ integrity sha512-/37qQCE3K0vvZKwoK4XU/irIJQdIfCJuhU5eKnNxpFDsOkgFaUAwbv+RYw6eYgsC0E4hS7r5KqGULUogqui0fQ==
+
+"@babel/helper-remap-async-to-generator@^7.14.5", "@babel/helper-remap-async-to-generator@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.15.4.tgz#2637c0731e4c90fbf58ac58b50b2b5a192fc970f"
+ integrity sha512-v53MxgvMK/HCwckJ1bZrq6dNKlmwlyRNYM6ypaRTdXWGOE2c1/SCa6dL/HimhPulGhZKw9W0QhREM583F/t0vQ==
+ dependencies:
+ "@babel/helper-annotate-as-pure" "^7.15.4"
+ "@babel/helper-wrap-function" "^7.15.4"
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-replace-supers@^7.14.5", "@babel/helper-replace-supers@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.15.4.tgz#52a8ab26ba918c7f6dee28628b07071ac7b7347a"
+ integrity sha512-/ztT6khaXF37MS47fufrKvIsiQkx1LBRvSJNzRqmbyeZnTwU9qBxXYLaaT/6KaxfKhjs2Wy8kG8ZdsFUuWBjzw==
+ dependencies:
+ "@babel/helper-member-expression-to-functions" "^7.15.4"
+ "@babel/helper-optimise-call-expression" "^7.15.4"
+ "@babel/traverse" "^7.15.4"
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-simple-access@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-simple-access/-/helper-simple-access-7.15.4.tgz#ac368905abf1de8e9781434b635d8f8674bcc13b"
+ integrity sha512-UzazrDoIVOZZcTeHHEPYrr1MvTR/K+wgLg6MY6e1CJyaRhbibftF6fR2KU2sFRtI/nERUZR9fBd6aKgBlIBaPg==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-skip-transparent-expression-wrappers@^7.14.5", "@babel/helper-skip-transparent-expression-wrappers@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.15.4.tgz#707dbdba1f4ad0fa34f9114fc8197aec7d5da2eb"
+ integrity sha512-BMRLsdh+D1/aap19TycS4eD1qELGrCBJwzaY9IE8LrpJtJb+H7rQkPIdsfgnMtLBA6DJls7X9z93Z4U8h7xw0A==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-split-export-declaration@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.15.4.tgz#aecab92dcdbef6a10aa3b62ab204b085f776e257"
+ integrity sha512-HsFqhLDZ08DxCpBdEVtKmywj6PQbwnF6HHybur0MAnkAKnlS6uHkwnmRIkElB2Owpfb4xL4NwDmDLFubueDXsw==
+ dependencies:
+ "@babel/types" "^7.15.4"
+
+"@babel/helper-validator-identifier@^7.14.5", "@babel/helper-validator-identifier@^7.14.9":
+ version "7.14.9"
+ resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.14.9.tgz#6654d171b2024f6d8ee151bf2509699919131d48"
+ integrity sha512-pQYxPY0UP6IHISRitNe8bsijHex4TWZXi2HwKVsjPiltzlhse2znVcm9Ace510VT1kxIHjGJCZZQBX2gJDbo0g==
+
+"@babel/helper-validator-option@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/helper-validator-option/-/helper-validator-option-7.14.5.tgz#6e72a1fff18d5dfcb878e1e62f1a021c4b72d5a3"
+ integrity sha512-OX8D5eeX4XwcroVW45NMvoYaIuFI+GQpA2a8Gi+X/U/cDUIRsV37qQfF905F0htTRCREQIB4KqPeaveRJUl3Ow==
+
+"@babel/helper-wrap-function@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-wrap-function/-/helper-wrap-function-7.15.4.tgz#6f754b2446cfaf3d612523e6ab8d79c27c3a3de7"
+ integrity sha512-Y2o+H/hRV5W8QhIfTpRIBwl57y8PrZt6JM3V8FOo5qarjshHItyH5lXlpMfBfmBefOqSCpKZs/6Dxqp0E/U+uw==
+ dependencies:
+ "@babel/helper-function-name" "^7.15.4"
+ "@babel/template" "^7.15.4"
+ "@babel/traverse" "^7.15.4"
+ "@babel/types" "^7.15.4"
+
+"@babel/helpers@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.15.4.tgz#5f40f02050a3027121a3cf48d497c05c555eaf43"
+ integrity sha512-V45u6dqEJ3w2rlryYYXf6i9rQ5YMNu4FLS6ngs8ikblhu2VdR1AqAd6aJjBzmf2Qzh6KOLqKHxEN9+TFbAkAVQ==
+ dependencies:
+ "@babel/template" "^7.15.4"
+ "@babel/traverse" "^7.15.4"
+ "@babel/types" "^7.15.4"
+
+"@babel/highlight@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.14.5.tgz#6861a52f03966405001f6aa534a01a24d99e8cd9"
+ integrity sha512-qf9u2WFWVV0MppaL877j2dBtQIDgmidgjGk5VIMw3OadXvYaXn66U1BFlH2t4+t3i+8PhedppRv+i40ABzd+gg==
+ dependencies:
+ "@babel/helper-validator-identifier" "^7.14.5"
+ chalk "^2.0.0"
+ js-tokens "^4.0.0"
-"@babel/helper-validator-option@^7.12.11":
- version "7.12.11"
- resolved "https://registry.yarnpkg.com/@babel/helper-validator-option/-/helper-validator-option-7.12.11.tgz#d66cb8b7a3e7fe4c6962b32020a131ecf0847f4f"
- integrity sha512-TBFCyj939mFSdeX7U7DDj32WtzYY7fDcalgq8v3fBZMNOJQNn7nOYzMaUCiPxPYfCup69mtIpqlKgMZLvQ8Xhw==
+"@babel/parser@^7.15.4", "@babel/parser@^7.15.5":
+ version "7.15.6"
+ resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.15.6.tgz#043b9aa3c303c0722e5377fef9197f4cf1796549"
+ integrity sha512-S/TSCcsRuCkmpUuoWijua0Snt+f3ewU/8spLo+4AXJCZfT0bVCzLD5MuOKdrx0mlAptbKzn5AdgEIIKXxXkz9Q==
-"@babel/helper-wrap-function@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helper-wrap-function/-/helper-wrap-function-7.12.13.tgz#e3ea8cb3ee0a16911f9c1b50d9e99fe8fe30f9ff"
- integrity sha512-t0aZFEmBJ1LojdtJnhOaQEVejnzYhyjWHSsNSNo8vOYRbAJNh6r6GQF7pd36SqG7OKGbn+AewVQ/0IfYfIuGdw==
+"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.15.4.tgz#dbdeabb1e80f622d9f0b583efb2999605e0a567e"
+ integrity sha512-eBnpsl9tlhPhpI10kU06JHnrYXwg3+V6CaP2idsCXNef0aeslpqyITXQ74Vfk5uHgY7IG7XP0yIH8b42KSzHog==
dependencies:
- "@babel/helper-function-name" "^7.12.13"
- "@babel/template" "^7.12.13"
- "@babel/traverse" "^7.12.13"
- "@babel/types" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-skip-transparent-expression-wrappers" "^7.15.4"
+ "@babel/plugin-proposal-optional-chaining" "^7.14.5"
-"@babel/helpers@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.12.13.tgz#3c75e993632e4dadc0274eae219c73eb7645ba47"
- integrity sha512-oohVzLRZ3GQEk4Cjhfs9YkJA4TdIDTObdBEZGrd6F/T0GPSnuV6l22eMcxlvcvzVIPH3VTtxbseudM1zIE+rPQ==
+"@babel/plugin-proposal-async-generator-functions@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.15.4.tgz#f82aabe96c135d2ceaa917feb9f5fca31635277e"
+ integrity sha512-2zt2g5vTXpMC3OmK6uyjvdXptbhBXfA77XGrd3gh93zwG8lZYBLOBImiGBEG0RANu3JqKEACCz5CGk73OJROBw==
dependencies:
- "@babel/template" "^7.12.13"
- "@babel/traverse" "^7.12.13"
- "@babel/types" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-remap-async-to-generator" "^7.15.4"
+ "@babel/plugin-syntax-async-generators" "^7.8.4"
-"@babel/highlight@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.12.13.tgz#8ab538393e00370b26271b01fa08f7f27f2e795c"
- integrity sha512-kocDQvIbgMKlWxXe9fof3TQ+gkIPOUSEYhJjqUjvKMez3krV7vbzYCDq39Oj11UAVK7JqPVGQPlgE85dPNlQww==
+"@babel/plugin-proposal-class-properties@^7.14.5", "@babel/plugin-proposal-class-properties@^7.8.3":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.14.5.tgz#40d1ee140c5b1e31a350f4f5eed945096559b42e"
+ integrity sha512-q/PLpv5Ko4dVc1LYMpCY7RVAAO4uk55qPwrIuJ5QJ8c6cVuAmhu7I/49JOppXL6gXf7ZHzpRVEUZdYoPLM04Gg==
dependencies:
- "@babel/helper-validator-identifier" "^7.12.11"
- chalk "^2.0.0"
- js-tokens "^4.0.0"
+ "@babel/helper-create-class-features-plugin" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/parser@^7.12.13":
- version "7.12.15"
- resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.12.15.tgz#2b20de7f0b4b332d9b119dd9c33409c538b8aacf"
- integrity sha512-AQBOU2Z9kWwSZMd6lNjCX0GUgFonL1wAM1db8L8PMk9UDaGsRCArBkU4Sc+UCM3AE4hjbXx+h58Lb3QT4oRmrA==
-
-"@babel/plugin-proposal-async-generator-functions@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.12.13.tgz#d1c6d841802ffb88c64a2413e311f7345b9e66b5"
- integrity sha512-1KH46Hx4WqP77f978+5Ye/VUbuwQld2hph70yaw2hXS2v7ER2f3nlpNMu909HO2rbvP0NKLlMVDPh9KXklVMhA==
+"@babel/plugin-proposal-class-static-block@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-class-static-block/-/plugin-proposal-class-static-block-7.15.4.tgz#3e7ca6128453c089e8b477a99f970c63fc1cb8d7"
+ integrity sha512-M682XWrrLNk3chXCjoPUQWOyYsB93B9z3mRyjtqqYJWDf2mfCdIYgDrA11cgNVhAQieaq6F2fn2f3wI0U4aTjA==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-remap-async-to-generator" "^7.12.13"
- "@babel/plugin-syntax-async-generators" "^7.8.0"
-
-"@babel/plugin-proposal-class-properties@^7.12.13", "@babel/plugin-proposal-class-properties@^7.8.3":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.12.13.tgz#3d2ce350367058033c93c098e348161d6dc0d8c8"
- integrity sha512-8SCJ0Ddrpwv4T7Gwb33EmW1V9PY5lggTO+A8WjyIwxrSHDUyBw4MtF96ifn1n8H806YlxbVCoKXbbmzD6RD+cA==
- dependencies:
- "@babel/helper-create-class-features-plugin" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-create-class-features-plugin" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-class-static-block" "^7.14.5"
"@babel/plugin-proposal-decorators@^7.8.3":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-decorators/-/plugin-proposal-decorators-7.12.13.tgz#d4c89b40c2b7a526b0d394de4f4def36191e413e"
- integrity sha512-x2aOr5w4ARJoYHFKoG2iEUL/Xe99JAJXjAasHijXp3/KgaetJXGE62SmHgsW3Tia/XUT5AxF2YC0F+JyhPY/0Q==
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-decorators/-/plugin-proposal-decorators-7.15.4.tgz#fb55442bc83ab4d45dda76b91949706bf22881d2"
+ integrity sha512-WNER+YLs7avvRukEddhu5PSfSaMMimX2xBFgLQS7Bw16yrUxJGWidO9nQp+yLy9MVybg5Ba3BlhAw+BkdhpDmg==
dependencies:
- "@babel/helper-create-class-features-plugin" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/plugin-syntax-decorators" "^7.12.13"
+ "@babel/helper-create-class-features-plugin" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-decorators" "^7.14.5"
-"@babel/plugin-proposal-dynamic-import@^7.12.1":
- version "7.12.1"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.12.1.tgz#43eb5c2a3487ecd98c5c8ea8b5fdb69a2749b2dc"
- integrity sha512-a4rhUSZFuq5W8/OO8H7BL5zspjnc1FLd9hlOxIK/f7qG4a0qsqk8uvF/ywgBA8/OmjsapjpvaEOYItfGG1qIvQ==
+"@babel/plugin-proposal-dynamic-import@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.14.5.tgz#0c6617df461c0c1f8fff3b47cd59772360101d2c"
+ integrity sha512-ExjiNYc3HDN5PXJx+bwC50GIx/KKanX2HiggnIUAYedbARdImiCU4RhhHfdf0Kd7JNXGpsBBBCOm+bBVy3Gb0g==
dependencies:
- "@babel/helper-plugin-utils" "^7.10.4"
- "@babel/plugin-syntax-dynamic-import" "^7.8.0"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-dynamic-import" "^7.8.3"
-"@babel/plugin-proposal-export-namespace-from@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-export-namespace-from/-/plugin-proposal-export-namespace-from-7.12.13.tgz#393be47a4acd03fa2af6e3cde9b06e33de1b446d"
- integrity sha512-INAgtFo4OnLN3Y/j0VwAgw3HDXcDtX+C/erMvWzuV9v71r7urb6iyMXu7eM9IgLr1ElLlOkaHjJ0SbCmdOQ3Iw==
+"@babel/plugin-proposal-export-namespace-from@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-export-namespace-from/-/plugin-proposal-export-namespace-from-7.14.5.tgz#dbad244310ce6ccd083072167d8cea83a52faf76"
+ integrity sha512-g5POA32bXPMmSBu5Dx/iZGLGnKmKPc5AiY7qfZgurzrCYgIztDlHFbznSNCoQuv57YQLnQfaDi7dxCtLDIdXdA==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
"@babel/plugin-syntax-export-namespace-from" "^7.8.3"
-"@babel/plugin-proposal-json-strings@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.12.13.tgz#ced7888a2db92a3d520a2e35eb421fdb7fcc9b5d"
- integrity sha512-v9eEi4GiORDg8x+Dmi5r8ibOe0VXoKDeNPYcTTxdGN4eOWikrJfDJCJrr1l5gKGvsNyGJbrfMftC2dTL6oz7pg==
+"@babel/plugin-proposal-json-strings@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.14.5.tgz#38de60db362e83a3d8c944ac858ddf9f0c2239eb"
+ integrity sha512-NSq2fczJYKVRIsUJyNxrVUMhB27zb7N7pOFGQOhBKJrChbGcgEAqyZrmZswkPk18VMurEeJAaICbfm57vUeTbQ==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/plugin-syntax-json-strings" "^7.8.0"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-json-strings" "^7.8.3"
-"@babel/plugin-proposal-logical-assignment-operators@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-logical-assignment-operators/-/plugin-proposal-logical-assignment-operators-7.12.13.tgz#575b5d9a08d8299eeb4db6430da6e16e5cf14350"
- integrity sha512-fqmiD3Lz7jVdK6kabeSr1PZlWSUVqSitmHEe3Z00dtGTKieWnX9beafvavc32kjORa5Bai4QNHgFDwWJP+WtSQ==
+"@babel/plugin-proposal-logical-assignment-operators@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-logical-assignment-operators/-/plugin-proposal-logical-assignment-operators-7.14.5.tgz#6e6229c2a99b02ab2915f82571e0cc646a40c738"
+ integrity sha512-YGn2AvZAo9TwyhlLvCCWxD90Xq8xJ4aSgaX3G5D/8DW94L8aaT+dS5cSP+Z06+rCJERGSr9GxMBZ601xoc2taw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
"@babel/plugin-syntax-logical-assignment-operators" "^7.10.4"
-"@babel/plugin-proposal-nullish-coalescing-operator@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.12.13.tgz#24867307285cee4e1031170efd8a7ac807deefde"
- integrity sha512-Qoxpy+OxhDBI5kRqliJFAl4uWXk3Bn24WeFstPH0iLymFehSAUR8MHpqU7njyXv/qbo7oN6yTy5bfCmXdKpo1Q==
+"@babel/plugin-proposal-nullish-coalescing-operator@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.14.5.tgz#ee38589ce00e2cc59b299ec3ea406fcd3a0fdaf6"
+ integrity sha512-gun/SOnMqjSb98Nkaq2rTKMwervfdAoz6NphdY0vTfuzMfryj+tDGb2n6UkDKwez+Y8PZDhE3D143v6Gepp4Hg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.0"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3"
-"@babel/plugin-proposal-numeric-separator@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-numeric-separator/-/plugin-proposal-numeric-separator-7.12.13.tgz#bd9da3188e787b5120b4f9d465a8261ce67ed1db"
- integrity sha512-O1jFia9R8BUCl3ZGB7eitaAPu62TXJRHn7rh+ojNERCFyqRwJMTmhz+tJ+k0CwI6CLjX/ee4qW74FSqlq9I35w==
+"@babel/plugin-proposal-numeric-separator@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-numeric-separator/-/plugin-proposal-numeric-separator-7.14.5.tgz#83631bf33d9a51df184c2102a069ac0c58c05f18"
+ integrity sha512-yiclALKe0vyZRZE0pS6RXgjUOt87GWv6FYa5zqj15PvhOGFO69R5DusPlgK/1K5dVnCtegTiWu9UaBSrLLJJBg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
"@babel/plugin-syntax-numeric-separator" "^7.10.4"
-"@babel/plugin-proposal-object-rest-spread@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.12.13.tgz#f93f3116381ff94bc676fdcb29d71045cd1ec011"
- integrity sha512-WvA1okB/0OS/N3Ldb3sziSrXg6sRphsBgqiccfcQq7woEn5wQLNX82Oc4PlaFcdwcWHuQXAtb8ftbS8Fbsg/sg==
- dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/plugin-syntax-object-rest-spread" "^7.8.0"
- "@babel/plugin-transform-parameters" "^7.12.13"
-
-"@babel/plugin-proposal-optional-catch-binding@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.12.13.tgz#4640520afe57728af14b4d1574ba844f263bcae5"
- integrity sha512-9+MIm6msl9sHWg58NvqpNpLtuFbmpFYk37x8kgnGzAHvX35E1FyAwSUt5hIkSoWJFSAH+iwU8bJ4fcD1zKXOzg==
- dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/plugin-syntax-optional-catch-binding" "^7.8.0"
-
-"@babel/plugin-proposal-optional-chaining@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.12.13.tgz#63a7d805bc8ce626f3234ee5421a2a7fb23f66d9"
- integrity sha512-0ZwjGfTcnZqyV3y9DSD1Yk3ebp+sIUpT2YDqP8hovzaNZnQq2Kd7PEqa6iOIUDBXBt7Jl3P7YAcEIL5Pz8u09Q==
- dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-skip-transparent-expression-wrappers" "^7.12.1"
- "@babel/plugin-syntax-optional-chaining" "^7.8.0"
-
-"@babel/plugin-proposal-private-methods@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-private-methods/-/plugin-proposal-private-methods-7.12.13.tgz#ea78a12554d784ecf7fc55950b752d469d9c4a71"
- integrity sha512-sV0V57uUwpauixvR7s2o75LmwJI6JECwm5oPUY5beZB1nBl2i37hc7CJGqB5G+58fur5Y6ugvl3LRONk5x34rg==
- dependencies:
- "@babel/helper-create-class-features-plugin" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
-
-"@babel/plugin-proposal-unicode-property-regex@^7.12.13", "@babel/plugin-proposal-unicode-property-regex@^7.4.4":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.12.13.tgz#bebde51339be829c17aaaaced18641deb62b39ba"
- integrity sha512-XyJmZidNfofEkqFV5VC/bLabGmO5QzenPO/YOfGuEbgU+2sSwMmio3YLb4WtBgcmmdwZHyVyv8on77IUjQ5Gvg==
- dependencies:
- "@babel/helper-create-regexp-features-plugin" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
-
-"@babel/plugin-syntax-async-generators@^7.8.0":
+"@babel/plugin-proposal-object-rest-spread@^7.15.6":
+ version "7.15.6"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.15.6.tgz#ef68050c8703d07b25af402cb96cf7f34a68ed11"
+ integrity sha512-qtOHo7A1Vt+O23qEAX+GdBpqaIuD3i9VRrWgCJeq7WO6H2d14EK3q11urj5Te2MAeK97nMiIdRpwd/ST4JFbNg==
+ dependencies:
+ "@babel/compat-data" "^7.15.0"
+ "@babel/helper-compilation-targets" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-object-rest-spread" "^7.8.3"
+ "@babel/plugin-transform-parameters" "^7.15.4"
+
+"@babel/plugin-proposal-optional-catch-binding@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.14.5.tgz#939dd6eddeff3a67fdf7b3f044b5347262598c3c"
+ integrity sha512-3Oyiixm0ur7bzO5ybNcZFlmVsygSIQgdOa7cTfOYCMY+wEPAYhZAJxi3mixKFCTCKUhQXuCTtQ1MzrpL3WT8ZQ==
+ dependencies:
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-optional-catch-binding" "^7.8.3"
+
+"@babel/plugin-proposal-optional-chaining@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.14.5.tgz#fa83651e60a360e3f13797eef00b8d519695b603"
+ integrity sha512-ycz+VOzo2UbWNI1rQXxIuMOzrDdHGrI23fRiz/Si2R4kv2XZQ1BK8ccdHwehMKBlcH/joGW/tzrUmo67gbJHlQ==
+ dependencies:
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-skip-transparent-expression-wrappers" "^7.14.5"
+ "@babel/plugin-syntax-optional-chaining" "^7.8.3"
+
+"@babel/plugin-proposal-private-methods@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-private-methods/-/plugin-proposal-private-methods-7.14.5.tgz#37446495996b2945f30f5be5b60d5e2aa4f5792d"
+ integrity sha512-838DkdUA1u+QTCplatfq4B7+1lnDa/+QMI89x5WZHBcnNv+47N8QEj2k9I2MUU9xIv8XJ4XvPCviM/Dj7Uwt9g==
+ dependencies:
+ "@babel/helper-create-class-features-plugin" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
+
+"@babel/plugin-proposal-private-property-in-object@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.15.4.tgz#55c5e3b4d0261fd44fe637e3f624cfb0f484e3e5"
+ integrity sha512-X0UTixkLf0PCCffxgu5/1RQyGGbgZuKoI+vXP4iSbJSYwPb7hu06omsFGBvQ9lJEvwgrxHdS8B5nbfcd8GyUNA==
+ dependencies:
+ "@babel/helper-annotate-as-pure" "^7.15.4"
+ "@babel/helper-create-class-features-plugin" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/plugin-syntax-private-property-in-object" "^7.14.5"
+
+"@babel/plugin-proposal-unicode-property-regex@^7.14.5", "@babel/plugin-proposal-unicode-property-regex@^7.4.4":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.14.5.tgz#0f95ee0e757a5d647f378daa0eca7e93faa8bbe8"
+ integrity sha512-6axIeOU5LnY471KenAB9vI8I5j7NQ2d652hIYwVyRfgaZT5UpiqFKCuVXCDMSrU+3VFafnu2c5m3lrWIlr6A5Q==
+ dependencies:
+ "@babel/helper-create-regexp-features-plugin" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
+
+"@babel/plugin-syntax-async-generators@^7.8.4":
version "7.8.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz#a983fb1aeb2ec3f6ed042a210f640e90e786fe0d"
integrity sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==
@@ -372,14 +416,21 @@
dependencies:
"@babel/helper-plugin-utils" "^7.12.13"
-"@babel/plugin-syntax-decorators@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-decorators/-/plugin-syntax-decorators-7.12.13.tgz#fac829bf3c7ef4a1bc916257b403e58c6bdaf648"
- integrity sha512-Rw6aIXGuqDLr6/LoBBYE57nKOzQpz/aDkKlMqEwH+Vp0MXbG6H/TfRjaY343LKxzAKAMXIHsQ8JzaZKuDZ9MwA==
+"@babel/plugin-syntax-class-static-block@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-class-static-block/-/plugin-syntax-class-static-block-7.14.5.tgz#195df89b146b4b78b3bf897fd7a257c84659d406"
+ integrity sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
+
+"@babel/plugin-syntax-decorators@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-decorators/-/plugin-syntax-decorators-7.14.5.tgz#eafb9c0cbe09c8afeb964ba3a7bbd63945a72f20"
+ integrity sha512-c4sZMRWL4GSvP1EXy0woIP7m4jkVcEuG8R1TOZxPBPtp4FSM/kiPZub9UIs/Jrb5ZAOzvTUSGYrWsrSu1JvoPw==
+ dependencies:
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-syntax-dynamic-import@^7.8.0", "@babel/plugin-syntax-dynamic-import@^7.8.3":
+"@babel/plugin-syntax-dynamic-import@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz#62bf98b2da3cd21d626154fc96ee5b3cb68eacb3"
integrity sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==
@@ -393,7 +444,7 @@
dependencies:
"@babel/helper-plugin-utils" "^7.8.3"
-"@babel/plugin-syntax-json-strings@^7.8.0":
+"@babel/plugin-syntax-json-strings@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz#01ca21b668cd8218c9e640cb6dd88c5412b2c96a"
integrity sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==
@@ -401,11 +452,11 @@
"@babel/helper-plugin-utils" "^7.8.0"
"@babel/plugin-syntax-jsx@^7.0.0", "@babel/plugin-syntax-jsx@^7.2.0", "@babel/plugin-syntax-jsx@^7.8.3":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.12.13.tgz#044fb81ebad6698fe62c478875575bcbb9b70f15"
- integrity sha512-d4HM23Q1K7oq/SLNmG6mRt85l2csmQ0cHRaxRXjKW0YFdEXqlZ5kzFQKH5Uc3rDJECgu+yCRgPkG04Mm98R/1g==
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.14.5.tgz#000e2e25d8673cce49300517a3eda44c263e4201"
+ integrity sha512-ohuFIsOMXJnbOMRfX7/w7LocdR6R7whhuRD4ax8IipLcLPlZGJKkBxgHp++U4N/vKyU16/YDQr2f5seajD3jIw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
"@babel/plugin-syntax-logical-assignment-operators@^7.10.4":
version "7.10.4"
@@ -414,7 +465,7 @@
dependencies:
"@babel/helper-plugin-utils" "^7.10.4"
-"@babel/plugin-syntax-nullish-coalescing-operator@^7.8.0":
+"@babel/plugin-syntax-nullish-coalescing-operator@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz#167ed70368886081f74b5c36c65a88c03b66d1a9"
integrity sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==
@@ -428,364 +479,381 @@
dependencies:
"@babel/helper-plugin-utils" "^7.10.4"
-"@babel/plugin-syntax-object-rest-spread@^7.8.0":
+"@babel/plugin-syntax-object-rest-spread@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz#60e225edcbd98a640332a2e72dd3e66f1af55871"
integrity sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
-"@babel/plugin-syntax-optional-catch-binding@^7.8.0":
+"@babel/plugin-syntax-optional-catch-binding@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz#6111a265bcfb020eb9efd0fdfd7d26402b9ed6c1"
integrity sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
-"@babel/plugin-syntax-optional-chaining@^7.8.0":
+"@babel/plugin-syntax-optional-chaining@^7.8.3":
version "7.8.3"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz#4f69c2ab95167e0180cd5336613f8c5788f7d48a"
integrity sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==
dependencies:
"@babel/helper-plugin-utils" "^7.8.0"
-"@babel/plugin-syntax-top-level-await@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.12.13.tgz#c5f0fa6e249f5b739727f923540cf7a806130178"
- integrity sha512-A81F9pDwyS7yM//KwbCSDqy3Uj4NMIurtplxphWxoYtNPov7cJsDkAFNNyVlIZ3jwGycVsurZ+LtOA8gZ376iQ==
+"@babel/plugin-syntax-private-property-in-object@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-private-property-in-object/-/plugin-syntax-private-property-in-object-7.14.5.tgz#0dc6671ec0ea22b6e94a1114f857970cd39de1ad"
+ integrity sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-arrow-functions@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.12.13.tgz#eda5670b282952100c229f8a3bd49e0f6a72e9fe"
- integrity sha512-tBtuN6qtCTd+iHzVZVOMNp+L04iIJBpqkdY42tWbmjIT5wvR2kx7gxMBsyhQtFzHwBbyGi9h8J8r9HgnOpQHxg==
+"@babel/plugin-syntax-top-level-await@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.14.5.tgz#c1cfdadc35a646240001f06138247b741c34d94c"
+ integrity sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-async-to-generator@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.12.13.tgz#fed8c69eebf187a535bfa4ee97a614009b24f7ae"
- integrity sha512-psM9QHcHaDr+HZpRuJcE1PXESuGWSCcbiGFFhhwfzdbTxaGDVzuVtdNYliAwcRo3GFg0Bc8MmI+AvIGYIJG04A==
+"@babel/plugin-transform-arrow-functions@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.14.5.tgz#f7187d9588a768dd080bf4c9ffe117ea62f7862a"
+ integrity sha512-KOnO0l4+tD5IfOdi4x8C1XmEIRWUjNRV8wc6K2vz/3e8yAOoZZvsRXRRIF/yo/MAOFb4QjtAw9xSxMXbSMRy8A==
dependencies:
- "@babel/helper-module-imports" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-remap-async-to-generator" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-block-scoped-functions@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.12.13.tgz#a9bf1836f2a39b4eb6cf09967739de29ea4bf4c4"
- integrity sha512-zNyFqbc3kI/fVpqwfqkg6RvBgFpC4J18aKKMmv7KdQ/1GgREapSJAykLMVNwfRGO3BtHj3YQZl8kxCXPcVMVeg==
+"@babel/plugin-transform-async-to-generator@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.14.5.tgz#72c789084d8f2094acb945633943ef8443d39e67"
+ integrity sha512-szkbzQ0mNk0rpu76fzDdqSyPu0MuvpXgC+6rz5rpMb5OIRxdmHfQxrktL8CYolL2d8luMCZTR0DpIMIdL27IjA==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-module-imports" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-remap-async-to-generator" "^7.14.5"
-"@babel/plugin-transform-block-scoping@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.12.13.tgz#f36e55076d06f41dfd78557ea039c1b581642e61"
- integrity sha512-Pxwe0iqWJX4fOOM2kEZeUuAxHMWb9nK+9oh5d11bsLoB0xMg+mkDpt0eYuDZB7ETrY9bbcVlKUGTOGWy7BHsMQ==
+"@babel/plugin-transform-block-scoped-functions@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.14.5.tgz#e48641d999d4bc157a67ef336aeb54bc44fd3ad4"
+ integrity sha512-dtqWqdWZ5NqBX3KzsVCWfQI3A53Ft5pWFCT2eCVUftWZgjc5DpDponbIF1+c+7cSGk2wN0YK7HGL/ezfRbpKBQ==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-classes@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.12.13.tgz#9728edc1838b5d62fc93ad830bd523b1fcb0e1f6"
- integrity sha512-cqZlMlhCC1rVnxE5ZGMtIb896ijL90xppMiuWXcwcOAuFczynpd3KYemb91XFFPi3wJSe/OcrX9lXoowatkkxA==
+"@babel/plugin-transform-block-scoping@^7.15.3":
+ version "7.15.3"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.15.3.tgz#94c81a6e2fc230bcce6ef537ac96a1e4d2b3afaf"
+ integrity sha512-nBAzfZwZb4DkaGtOes1Up1nOAp9TDRRFw4XBzBBSG9QK7KVFmYzgj9o9sbPv7TX5ofL4Auq4wZnxCoPnI/lz2Q==
dependencies:
- "@babel/helper-annotate-as-pure" "^7.12.13"
- "@babel/helper-function-name" "^7.12.13"
- "@babel/helper-optimise-call-expression" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-replace-supers" "^7.12.13"
- "@babel/helper-split-export-declaration" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
+
+"@babel/plugin-transform-classes@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.15.4.tgz#50aee17aaf7f332ae44e3bce4c2e10534d5d3bf1"
+ integrity sha512-Yjvhex8GzBmmPQUvpXRPWQ9WnxXgAFuZSrqOK/eJlOGIXwvv8H3UEdUigl1gb/bnjTrln+e8bkZUYCBt/xYlBg==
+ dependencies:
+ "@babel/helper-annotate-as-pure" "^7.15.4"
+ "@babel/helper-function-name" "^7.15.4"
+ "@babel/helper-optimise-call-expression" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-replace-supers" "^7.15.4"
+ "@babel/helper-split-export-declaration" "^7.15.4"
globals "^11.1.0"
-"@babel/plugin-transform-computed-properties@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.12.13.tgz#6a210647a3d67f21f699cfd2a01333803b27339d"
- integrity sha512-dDfuROUPGK1mTtLKyDPUavmj2b6kFu82SmgpztBFEO974KMjJT+Ytj3/oWsTUMBmgPcp9J5Pc1SlcAYRpJ2hRA==
+"@babel/plugin-transform-computed-properties@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.14.5.tgz#1b9d78987420d11223d41195461cc43b974b204f"
+ integrity sha512-pWM+E4283UxaVzLb8UBXv4EIxMovU4zxT1OPnpHJcmnvyY9QbPPTKZfEj31EUvG3/EQRbYAGaYEUZ4yWOBC2xg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-destructuring@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.12.13.tgz#fc56c5176940c5b41735c677124d1d20cecc9aeb"
- integrity sha512-Dn83KykIFzjhA3FDPA1z4N+yfF3btDGhjnJwxIj0T43tP0flCujnU8fKgEkf0C1biIpSv9NZegPBQ1J6jYkwvQ==
+"@babel/plugin-transform-destructuring@^7.14.7":
+ version "7.14.7"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.14.7.tgz#0ad58ed37e23e22084d109f185260835e5557576"
+ integrity sha512-0mDE99nK+kVh3xlc5vKwB6wnP9ecuSj+zQCa/n0voENtP/zymdT4HH6QEb65wjjcbqr1Jb/7z9Qp7TF5FtwYGw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-dotall-regex@^7.12.13", "@babel/plugin-transform-dotall-regex@^7.4.4":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.12.13.tgz#3f1601cc29905bfcb67f53910f197aeafebb25ad"
- integrity sha512-foDrozE65ZFdUC2OfgeOCrEPTxdB3yjqxpXh8CH+ipd9CHd4s/iq81kcUpyH8ACGNEPdFqbtzfgzbT/ZGlbDeQ==
+"@babel/plugin-transform-dotall-regex@^7.14.5", "@babel/plugin-transform-dotall-regex@^7.4.4":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.14.5.tgz#2f6bf76e46bdf8043b4e7e16cf24532629ba0c7a"
+ integrity sha512-loGlnBdj02MDsFaHhAIJzh7euK89lBrGIdM9EAtHFo6xKygCUGuuWe07o1oZVk287amtW1n0808sQM99aZt3gw==
dependencies:
- "@babel/helper-create-regexp-features-plugin" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-create-regexp-features-plugin" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-duplicate-keys@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.12.13.tgz#6f06b87a8b803fd928e54b81c258f0a0033904de"
- integrity sha512-NfADJiiHdhLBW3pulJlJI2NB0t4cci4WTZ8FtdIuNc2+8pslXdPtRRAEWqUY+m9kNOk2eRYbTAOipAxlrOcwwQ==
+"@babel/plugin-transform-duplicate-keys@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.14.5.tgz#365a4844881bdf1501e3a9f0270e7f0f91177954"
+ integrity sha512-iJjbI53huKbPDAsJ8EmVmvCKeeq21bAze4fu9GBQtSLqfvzj2oRuHVx4ZkDwEhg1htQ+5OBZh/Ab0XDf5iBZ7A==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-exponentiation-operator@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.12.13.tgz#4d52390b9a273e651e4aba6aee49ef40e80cd0a1"
- integrity sha512-fbUelkM1apvqez/yYx1/oICVnGo2KM5s63mhGylrmXUxK/IAXSIf87QIxVfZldWf4QsOafY6vV3bX8aMHSvNrA==
+"@babel/plugin-transform-exponentiation-operator@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.14.5.tgz#5154b8dd6a3dfe6d90923d61724bd3deeb90b493"
+ integrity sha512-jFazJhMBc9D27o9jDnIE5ZErI0R0m7PbKXVq77FFvqFbzvTMuv8jaAwLZ5PviOLSFttqKIW0/wxNSDbjLk0tYA==
dependencies:
- "@babel/helper-builder-binary-assignment-operator-visitor" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-builder-binary-assignment-operator-visitor" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-for-of@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.12.13.tgz#561ff6d74d9e1c8879cb12dbaf4a14cd29d15cf6"
- integrity sha512-xCbdgSzXYmHGyVX3+BsQjcd4hv4vA/FDy7Kc8eOpzKmBBPEOTurt0w5fCRQaGl+GSBORKgJdstQ1rHl4jbNseQ==
+"@babel/plugin-transform-for-of@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.15.4.tgz#25c62cce2718cfb29715f416e75d5263fb36a8c2"
+ integrity sha512-DRTY9fA751AFBDh2oxydvVm4SYevs5ILTWLs6xKXps4Re/KG5nfUkr+TdHCrRWB8C69TlzVgA9b3RmGWmgN9LA==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-function-name@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.12.13.tgz#bb024452f9aaed861d374c8e7a24252ce3a50051"
- integrity sha512-6K7gZycG0cmIwwF7uMK/ZqeCikCGVBdyP2J5SKNCXO5EOHcqi+z7Jwf8AmyDNcBgxET8DrEtCt/mPKPyAzXyqQ==
+"@babel/plugin-transform-function-name@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.14.5.tgz#e81c65ecb900746d7f31802f6bed1f52d915d6f2"
+ integrity sha512-vbO6kv0fIzZ1GpmGQuvbwwm+O4Cbm2NrPzwlup9+/3fdkuzo1YqOZcXw26+YUJB84Ja7j9yURWposEHLYwxUfQ==
dependencies:
- "@babel/helper-function-name" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-function-name" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-literals@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-literals/-/plugin-transform-literals-7.12.13.tgz#2ca45bafe4a820197cf315794a4d26560fe4bdb9"
- integrity sha512-FW+WPjSR7hiUxMcKqyNjP05tQ2kmBCdpEpZHY1ARm96tGQCCBvXKnpjILtDplUnJ/eHZ0lALLM+d2lMFSpYJrQ==
+"@babel/plugin-transform-literals@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-literals/-/plugin-transform-literals-7.14.5.tgz#41d06c7ff5d4d09e3cf4587bd3ecf3930c730f78"
+ integrity sha512-ql33+epql2F49bi8aHXxvLURHkxJbSmMKl9J5yHqg4PLtdE6Uc48CH1GS6TQvZ86eoB/ApZXwm7jlA+B3kra7A==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-member-expression-literals@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.12.13.tgz#5ffa66cd59b9e191314c9f1f803b938e8c081e40"
- integrity sha512-kxLkOsg8yir4YeEPHLuO2tXP9R/gTjpuTOjshqSpELUN3ZAg2jfDnKUvzzJxObun38sw3wm4Uu69sX/zA7iRvg==
+"@babel/plugin-transform-member-expression-literals@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.14.5.tgz#b39cd5212a2bf235a617d320ec2b48bcc091b8a7"
+ integrity sha512-WkNXxH1VXVTKarWFqmso83xl+2V3Eo28YY5utIkbsmXoItO8Q3aZxN4BTS2k0hz9dGUloHK26mJMyQEYfkn/+Q==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-modules-amd@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.12.13.tgz#43db16249b274ee2e551e2422090aa1c47692d56"
- integrity sha512-JHLOU0o81m5UqG0Ulz/fPC68/v+UTuGTWaZBUwpEk1fYQ1D9LfKV6MPn4ttJKqRo5Lm460fkzjLTL4EHvCprvA==
+"@babel/plugin-transform-modules-amd@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.14.5.tgz#4fd9ce7e3411cb8b83848480b7041d83004858f7"
+ integrity sha512-3lpOU8Vxmp3roC4vzFpSdEpGUWSMsHFreTWOMMLzel2gNGfHE5UWIh/LN6ghHs2xurUp4jRFYMUIZhuFbody1g==
dependencies:
- "@babel/helper-module-transforms" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-module-transforms" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
babel-plugin-dynamic-import-node "^2.3.3"
-"@babel/plugin-transform-modules-commonjs@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.12.13.tgz#5043b870a784a8421fa1fd9136a24f294da13e50"
- integrity sha512-OGQoeVXVi1259HjuoDnsQMlMkT9UkZT9TpXAsqWplS/M0N1g3TJAn/ByOCeQu7mfjc5WpSsRU+jV1Hd89ts0kQ==
+"@babel/plugin-transform-modules-commonjs@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.15.4.tgz#8201101240eabb5a76c08ef61b2954f767b6b4c1"
+ integrity sha512-qg4DPhwG8hKp4BbVDvX1s8cohM8a6Bvptu4l6Iingq5rW+yRUAhe/YRup/YcW2zCOlrysEWVhftIcKzrEZv3sA==
dependencies:
- "@babel/helper-module-transforms" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-simple-access" "^7.12.13"
+ "@babel/helper-module-transforms" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-simple-access" "^7.15.4"
babel-plugin-dynamic-import-node "^2.3.3"
-"@babel/plugin-transform-modules-systemjs@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.12.13.tgz#351937f392c7f07493fc79b2118201d50404a3c5"
- integrity sha512-aHfVjhZ8QekaNF/5aNdStCGzwTbU7SI5hUybBKlMzqIMC7w7Ho8hx5a4R/DkTHfRfLwHGGxSpFt9BfxKCoXKoA==
+"@babel/plugin-transform-modules-systemjs@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.15.4.tgz#b42890c7349a78c827719f1d2d0cd38c7d268132"
+ integrity sha512-fJUnlQrl/mezMneR72CKCgtOoahqGJNVKpompKwzv3BrEXdlPspTcyxrZ1XmDTIr9PpULrgEQo3qNKp6dW7ssw==
dependencies:
- "@babel/helper-hoist-variables" "^7.12.13"
- "@babel/helper-module-transforms" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-validator-identifier" "^7.12.11"
+ "@babel/helper-hoist-variables" "^7.15.4"
+ "@babel/helper-module-transforms" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-validator-identifier" "^7.14.9"
babel-plugin-dynamic-import-node "^2.3.3"
-"@babel/plugin-transform-modules-umd@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.12.13.tgz#26c66f161d3456674e344b4b1255de4d530cfb37"
- integrity sha512-BgZndyABRML4z6ibpi7Z98m4EVLFI9tVsZDADC14AElFaNHHBcJIovflJ6wtCqFxwy2YJ1tJhGRsr0yLPKoN+w==
+"@babel/plugin-transform-modules-umd@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.14.5.tgz#fb662dfee697cce274a7cda525190a79096aa6e0"
+ integrity sha512-RfPGoagSngC06LsGUYyM9QWSXZ8MysEjDJTAea1lqRjNECE3y0qIJF/qbvJxc4oA4s99HumIMdXOrd+TdKaAAA==
dependencies:
- "@babel/helper-module-transforms" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-module-transforms" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-named-capturing-groups-regex@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.12.13.tgz#2213725a5f5bbbe364b50c3ba5998c9599c5c9d9"
- integrity sha512-Xsm8P2hr5hAxyYblrfACXpQKdQbx4m2df9/ZZSQ8MAhsadw06+jW7s9zsSw6he+mJZXRlVMyEnVktJo4zjk1WA==
+"@babel/plugin-transform-named-capturing-groups-regex@^7.14.9":
+ version "7.14.9"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.14.9.tgz#c68f5c5d12d2ebaba3762e57c2c4f6347a46e7b2"
+ integrity sha512-l666wCVYO75mlAtGFfyFwnWmIXQm3kSH0C3IRnJqWcZbWkoihyAdDhFm2ZWaxWTqvBvhVFfJjMRQ0ez4oN1yYA==
dependencies:
- "@babel/helper-create-regexp-features-plugin" "^7.12.13"
+ "@babel/helper-create-regexp-features-plugin" "^7.14.5"
-"@babel/plugin-transform-new-target@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.12.13.tgz#e22d8c3af24b150dd528cbd6e685e799bf1c351c"
- integrity sha512-/KY2hbLxrG5GTQ9zzZSc3xWiOy379pIETEhbtzwZcw9rvuaVV4Fqy7BYGYOWZnaoXIQYbbJ0ziXLa/sKcGCYEQ==
+"@babel/plugin-transform-new-target@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.14.5.tgz#31bdae8b925dc84076ebfcd2a9940143aed7dbf8"
+ integrity sha512-Nx054zovz6IIRWEB49RDRuXGI4Gy0GMgqG0cII9L3MxqgXz/+rgII+RU58qpo4g7tNEx1jG7rRVH4ihZoP4esQ==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-object-super@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.12.13.tgz#b4416a2d63b8f7be314f3d349bd55a9c1b5171f7"
- integrity sha512-JzYIcj3XtYspZDV8j9ulnoMPZZnF/Cj0LUxPOjR89BdBVx+zYJI9MdMIlUZjbXDX+6YVeS6I3e8op+qQ3BYBoQ==
+"@babel/plugin-transform-object-super@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.14.5.tgz#d0b5faeac9e98597a161a9cf78c527ed934cdc45"
+ integrity sha512-MKfOBWzK0pZIrav9z/hkRqIk/2bTv9qvxHzPQc12RcVkMOzpIKnFCNYJip00ssKWYkd8Sf5g0Wr7pqJ+cmtuFg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-replace-supers" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-replace-supers" "^7.14.5"
-"@babel/plugin-transform-parameters@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.12.13.tgz#461e76dfb63c2dfd327b8a008a9e802818ce9853"
- integrity sha512-e7QqwZalNiBRHCpJg/P8s/VJeSRYgmtWySs1JwvfwPqhBbiWfOcHDKdeAi6oAyIimoKWBlwc8oTgbZHdhCoVZA==
+"@babel/plugin-transform-parameters@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.15.4.tgz#5f2285cc3160bf48c8502432716b48504d29ed62"
+ integrity sha512-9WB/GUTO6lvJU3XQsSr6J/WKvBC2hcs4Pew8YxZagi6GkTdniyqp8On5kqdK8MN0LMeu0mGbhPN+O049NV/9FQ==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-property-literals@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.12.13.tgz#4e6a9e37864d8f1b3bc0e2dce7bf8857db8b1a81"
- integrity sha512-nqVigwVan+lR+g8Fj8Exl0UQX2kymtjcWfMOYM1vTYEKujeyv2SkMgazf2qNcK7l4SDiKyTA/nHCPqL4e2zo1A==
+"@babel/plugin-transform-property-literals@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.14.5.tgz#0ddbaa1f83db3606f1cdf4846fa1dfb473458b34"
+ integrity sha512-r1uilDthkgXW8Z1vJz2dKYLV1tuw2xsbrp3MrZmD99Wh9vsfKoob+JTgri5VUb/JqyKRXotlOtwgu4stIYCmnw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-regenerator@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.12.13.tgz#b628bcc9c85260ac1aeb05b45bde25210194a2f5"
- integrity sha512-lxb2ZAvSLyJ2PEe47hoGWPmW22v7CtSl9jW8mingV4H2sEX/JOcrAj2nPuGWi56ERUm2bUpjKzONAuT6HCn2EA==
+"@babel/plugin-transform-regenerator@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.14.5.tgz#9676fd5707ed28f522727c5b3c0aa8544440b04f"
+ integrity sha512-NVIY1W3ITDP5xQl50NgTKlZ0GrotKtLna08/uGY6ErQt6VEQZXla86x/CTddm5gZdcr+5GSsvMeTmWA5Ii6pkg==
dependencies:
regenerator-transform "^0.14.2"
-"@babel/plugin-transform-reserved-words@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.12.13.tgz#7d9988d4f06e0fe697ea1d9803188aa18b472695"
- integrity sha512-xhUPzDXxZN1QfiOy/I5tyye+TRz6lA7z6xaT4CLOjPRMVg1ldRf0LHw0TDBpYL4vG78556WuHdyO9oi5UmzZBg==
+"@babel/plugin-transform-reserved-words@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.14.5.tgz#c44589b661cfdbef8d4300dcc7469dffa92f8304"
+ integrity sha512-cv4F2rv1nD4qdexOGsRQXJrOcyb5CrgjUH9PKrrtyhSDBNWGxd0UIitjyJiWagS+EbUGjG++22mGH1Pub8D6Vg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
"@babel/plugin-transform-runtime@^7.11.0":
- version "7.12.15"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.12.15.tgz#4337b2507288007c2b197059301aa0af8d90c085"
- integrity sha512-OwptMSRnRWJo+tJ9v9wgAf72ydXWfYSXWhnQjZing8nGZSDFqU1MBleKM3+DriKkcbv7RagA8gVeB0A1PNlNow==
- dependencies:
- "@babel/helper-module-imports" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- semver "^5.5.1"
+ version "7.15.0"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.15.0.tgz#d3aa650d11678ca76ce294071fda53d7804183b3"
+ integrity sha512-sfHYkLGjhzWTq6xsuQ01oEsUYjkHRux9fW1iUA68dC7Qd8BS1Unq4aZ8itmQp95zUzIcyR2EbNMTzAicFj+guw==
+ dependencies:
+ "@babel/helper-module-imports" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ babel-plugin-polyfill-corejs2 "^0.2.2"
+ babel-plugin-polyfill-corejs3 "^0.2.2"
+ babel-plugin-polyfill-regenerator "^0.2.2"
+ semver "^6.3.0"
-"@babel/plugin-transform-shorthand-properties@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.12.13.tgz#db755732b70c539d504c6390d9ce90fe64aff7ad"
- integrity sha512-xpL49pqPnLtf0tVluuqvzWIgLEhuPpZzvs2yabUHSKRNlN7ScYU7aMlmavOeyXJZKgZKQRBlh8rHbKiJDraTSw==
+"@babel/plugin-transform-shorthand-properties@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.14.5.tgz#97f13855f1409338d8cadcbaca670ad79e091a58"
+ integrity sha512-xLucks6T1VmGsTB+GWK5Pl9Jl5+nRXD1uoFdA5TSO6xtiNjtXTjKkmPdFXVLGlK5A2/or/wQMKfmQ2Y0XJfn5g==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-spread@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-spread/-/plugin-transform-spread-7.12.13.tgz#ca0d5645abbd560719c354451b849f14df4a7949"
- integrity sha512-dUCrqPIowjqk5pXsx1zPftSq4sT0aCeZVAxhdgs3AMgyaDmoUT0G+5h3Dzja27t76aUEIJWlFgPJqJ/d4dbTtg==
+"@babel/plugin-transform-spread@^7.14.6":
+ version "7.14.6"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-spread/-/plugin-transform-spread-7.14.6.tgz#6bd40e57fe7de94aa904851963b5616652f73144"
+ integrity sha512-Zr0x0YroFJku7n7+/HH3A2eIrGMjbmAIbJSVv0IZ+t3U2WUQUA64S/oeied2e+MaGSjmt4alzBCsK9E8gh+fag==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-skip-transparent-expression-wrappers" "^7.12.1"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-skip-transparent-expression-wrappers" "^7.14.5"
-"@babel/plugin-transform-sticky-regex@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.12.13.tgz#760ffd936face73f860ae646fb86ee82f3d06d1f"
- integrity sha512-Jc3JSaaWT8+fr7GRvQP02fKDsYk4K/lYwWq38r/UGfaxo89ajud321NH28KRQ7xy1Ybc0VUE5Pz8psjNNDUglg==
+"@babel/plugin-transform-sticky-regex@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.14.5.tgz#5b617542675e8b7761294381f3c28c633f40aeb9"
+ integrity sha512-Z7F7GyvEMzIIbwnziAZmnSNpdijdr4dWt+FJNBnBLz5mwDFkqIXU9wmBcWWad3QeJF5hMTkRe4dAq2sUZiG+8A==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-template-literals@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.12.13.tgz#655037b07ebbddaf3b7752f55d15c2fd6f5aa865"
- integrity sha512-arIKlWYUgmNsF28EyfmiQHJLJFlAJNYkuQO10jL46ggjBpeb2re1P9K9YGxNJB45BqTbaslVysXDYm/g3sN/Qg==
+"@babel/plugin-transform-template-literals@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.14.5.tgz#a5f2bc233937d8453885dc736bdd8d9ffabf3d93"
+ integrity sha512-22btZeURqiepOfuy/VkFr+zStqlujWaarpMErvay7goJS6BWwdd6BY9zQyDLDa4x2S3VugxFb162IZ4m/S/+Gg==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-typeof-symbol@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.12.13.tgz#785dd67a1f2ea579d9c2be722de8c84cb85f5a7f"
- integrity sha512-eKv/LmUJpMnu4npgfvs3LiHhJua5fo/CysENxa45YCQXZwKnGCQKAg87bvoqSW1fFT+HA32l03Qxsm8ouTY3ZQ==
+"@babel/plugin-transform-typeof-symbol@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.14.5.tgz#39af2739e989a2bd291bf6b53f16981423d457d4"
+ integrity sha512-lXzLD30ffCWseTbMQzrvDWqljvZlHkXU+CnseMhkMNqU1sASnCsz3tSzAaH3vCUXb9PHeUb90ZT1BdFTm1xxJw==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-unicode-escapes@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.12.13.tgz#840ced3b816d3b5127dd1d12dcedc5dead1a5e74"
- integrity sha512-0bHEkdwJ/sN/ikBHfSmOXPypN/beiGqjo+o4/5K+vxEFNPRPdImhviPakMKG4x96l85emoa0Z6cDflsdBusZbw==
+"@babel/plugin-transform-unicode-escapes@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.14.5.tgz#9d4bd2a681e3c5d7acf4f57fa9e51175d91d0c6b"
+ integrity sha512-crTo4jATEOjxj7bt9lbYXcBAM3LZaUrbP2uUdxb6WIorLmjNKSpHfIybgY4B8SRpbf8tEVIWH3Vtm7ayCrKocA==
dependencies:
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-plugin-utils" "^7.14.5"
-"@babel/plugin-transform-unicode-regex@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.12.13.tgz#b52521685804e155b1202e83fc188d34bb70f5ac"
- integrity sha512-mDRzSNY7/zopwisPZ5kM9XKCfhchqIYwAKRERtEnhYscZB79VRekuRSoYbN0+KVe3y8+q1h6A4svXtP7N+UoCA==
+"@babel/plugin-transform-unicode-regex@^7.14.5":
+ version "7.14.5"
+ resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.14.5.tgz#4cd09b6c8425dd81255c7ceb3fb1836e7414382e"
+ integrity sha512-UygduJpC5kHeCiRw/xDVzC+wj8VaYSoKl5JNVmbP7MadpNinAm3SvZCxZ42H37KZBKztz46YC73i9yV34d0Tzw==
dependencies:
- "@babel/helper-create-regexp-features-plugin" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
+ "@babel/helper-create-regexp-features-plugin" "^7.14.5"
+ "@babel/helper-plugin-utils" "^7.14.5"
"@babel/preset-env@^7.11.0":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.12.13.tgz#3aa2d09cf7d255177538dff292ac9af29ad46525"
- integrity sha512-JUVlizG8SoFTz4LmVUL8++aVwzwxcvey3N0j1tRbMAXVEy95uQ/cnEkmEKHN00Bwq4voAV3imQGnQvpkLAxsrw==
- dependencies:
- "@babel/compat-data" "^7.12.13"
- "@babel/helper-compilation-targets" "^7.12.13"
- "@babel/helper-module-imports" "^7.12.13"
- "@babel/helper-plugin-utils" "^7.12.13"
- "@babel/helper-validator-option" "^7.12.11"
- "@babel/plugin-proposal-async-generator-functions" "^7.12.13"
- "@babel/plugin-proposal-class-properties" "^7.12.13"
- "@babel/plugin-proposal-dynamic-import" "^7.12.1"
- "@babel/plugin-proposal-export-namespace-from" "^7.12.13"
- "@babel/plugin-proposal-json-strings" "^7.12.13"
- "@babel/plugin-proposal-logical-assignment-operators" "^7.12.13"
- "@babel/plugin-proposal-nullish-coalescing-operator" "^7.12.13"
- "@babel/plugin-proposal-numeric-separator" "^7.12.13"
- "@babel/plugin-proposal-object-rest-spread" "^7.12.13"
- "@babel/plugin-proposal-optional-catch-binding" "^7.12.13"
- "@babel/plugin-proposal-optional-chaining" "^7.12.13"
- "@babel/plugin-proposal-private-methods" "^7.12.13"
- "@babel/plugin-proposal-unicode-property-regex" "^7.12.13"
- "@babel/plugin-syntax-async-generators" "^7.8.0"
+ version "7.15.6"
+ resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.15.6.tgz#0f3898db9d63d320f21b17380d8462779de57659"
+ integrity sha512-L+6jcGn7EWu7zqaO2uoTDjjMBW+88FXzV8KvrBl2z6MtRNxlsmUNRlZPaNNPUTgqhyC5DHNFk/2Jmra+ublZWw==
+ dependencies:
+ "@babel/compat-data" "^7.15.0"
+ "@babel/helper-compilation-targets" "^7.15.4"
+ "@babel/helper-plugin-utils" "^7.14.5"
+ "@babel/helper-validator-option" "^7.14.5"
+ "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining" "^7.15.4"
+ "@babel/plugin-proposal-async-generator-functions" "^7.15.4"
+ "@babel/plugin-proposal-class-properties" "^7.14.5"
+ "@babel/plugin-proposal-class-static-block" "^7.15.4"
+ "@babel/plugin-proposal-dynamic-import" "^7.14.5"
+ "@babel/plugin-proposal-export-namespace-from" "^7.14.5"
+ "@babel/plugin-proposal-json-strings" "^7.14.5"
+ "@babel/plugin-proposal-logical-assignment-operators" "^7.14.5"
+ "@babel/plugin-proposal-nullish-coalescing-operator" "^7.14.5"
+ "@babel/plugin-proposal-numeric-separator" "^7.14.5"
+ "@babel/plugin-proposal-object-rest-spread" "^7.15.6"
+ "@babel/plugin-proposal-optional-catch-binding" "^7.14.5"
+ "@babel/plugin-proposal-optional-chaining" "^7.14.5"
+ "@babel/plugin-proposal-private-methods" "^7.14.5"
+ "@babel/plugin-proposal-private-property-in-object" "^7.15.4"
+ "@babel/plugin-proposal-unicode-property-regex" "^7.14.5"
+ "@babel/plugin-syntax-async-generators" "^7.8.4"
"@babel/plugin-syntax-class-properties" "^7.12.13"
- "@babel/plugin-syntax-dynamic-import" "^7.8.0"
+ "@babel/plugin-syntax-class-static-block" "^7.14.5"
+ "@babel/plugin-syntax-dynamic-import" "^7.8.3"
"@babel/plugin-syntax-export-namespace-from" "^7.8.3"
- "@babel/plugin-syntax-json-strings" "^7.8.0"
+ "@babel/plugin-syntax-json-strings" "^7.8.3"
"@babel/plugin-syntax-logical-assignment-operators" "^7.10.4"
- "@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.0"
+ "@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3"
"@babel/plugin-syntax-numeric-separator" "^7.10.4"
- "@babel/plugin-syntax-object-rest-spread" "^7.8.0"
- "@babel/plugin-syntax-optional-catch-binding" "^7.8.0"
- "@babel/plugin-syntax-optional-chaining" "^7.8.0"
- "@babel/plugin-syntax-top-level-await" "^7.12.13"
- "@babel/plugin-transform-arrow-functions" "^7.12.13"
- "@babel/plugin-transform-async-to-generator" "^7.12.13"
- "@babel/plugin-transform-block-scoped-functions" "^7.12.13"
- "@babel/plugin-transform-block-scoping" "^7.12.13"
- "@babel/plugin-transform-classes" "^7.12.13"
- "@babel/plugin-transform-computed-properties" "^7.12.13"
- "@babel/plugin-transform-destructuring" "^7.12.13"
- "@babel/plugin-transform-dotall-regex" "^7.12.13"
- "@babel/plugin-transform-duplicate-keys" "^7.12.13"
- "@babel/plugin-transform-exponentiation-operator" "^7.12.13"
- "@babel/plugin-transform-for-of" "^7.12.13"
- "@babel/plugin-transform-function-name" "^7.12.13"
- "@babel/plugin-transform-literals" "^7.12.13"
- "@babel/plugin-transform-member-expression-literals" "^7.12.13"
- "@babel/plugin-transform-modules-amd" "^7.12.13"
- "@babel/plugin-transform-modules-commonjs" "^7.12.13"
- "@babel/plugin-transform-modules-systemjs" "^7.12.13"
- "@babel/plugin-transform-modules-umd" "^7.12.13"
- "@babel/plugin-transform-named-capturing-groups-regex" "^7.12.13"
- "@babel/plugin-transform-new-target" "^7.12.13"
- "@babel/plugin-transform-object-super" "^7.12.13"
- "@babel/plugin-transform-parameters" "^7.12.13"
- "@babel/plugin-transform-property-literals" "^7.12.13"
- "@babel/plugin-transform-regenerator" "^7.12.13"
- "@babel/plugin-transform-reserved-words" "^7.12.13"
- "@babel/plugin-transform-shorthand-properties" "^7.12.13"
- "@babel/plugin-transform-spread" "^7.12.13"
- "@babel/plugin-transform-sticky-regex" "^7.12.13"
- "@babel/plugin-transform-template-literals" "^7.12.13"
- "@babel/plugin-transform-typeof-symbol" "^7.12.13"
- "@babel/plugin-transform-unicode-escapes" "^7.12.13"
- "@babel/plugin-transform-unicode-regex" "^7.12.13"
- "@babel/preset-modules" "^0.1.3"
- "@babel/types" "^7.12.13"
- core-js-compat "^3.8.0"
- semver "^5.5.0"
+ "@babel/plugin-syntax-object-rest-spread" "^7.8.3"
+ "@babel/plugin-syntax-optional-catch-binding" "^7.8.3"
+ "@babel/plugin-syntax-optional-chaining" "^7.8.3"
+ "@babel/plugin-syntax-private-property-in-object" "^7.14.5"
+ "@babel/plugin-syntax-top-level-await" "^7.14.5"
+ "@babel/plugin-transform-arrow-functions" "^7.14.5"
+ "@babel/plugin-transform-async-to-generator" "^7.14.5"
+ "@babel/plugin-transform-block-scoped-functions" "^7.14.5"
+ "@babel/plugin-transform-block-scoping" "^7.15.3"
+ "@babel/plugin-transform-classes" "^7.15.4"
+ "@babel/plugin-transform-computed-properties" "^7.14.5"
+ "@babel/plugin-transform-destructuring" "^7.14.7"
+ "@babel/plugin-transform-dotall-regex" "^7.14.5"
+ "@babel/plugin-transform-duplicate-keys" "^7.14.5"
+ "@babel/plugin-transform-exponentiation-operator" "^7.14.5"
+ "@babel/plugin-transform-for-of" "^7.15.4"
+ "@babel/plugin-transform-function-name" "^7.14.5"
+ "@babel/plugin-transform-literals" "^7.14.5"
+ "@babel/plugin-transform-member-expression-literals" "^7.14.5"
+ "@babel/plugin-transform-modules-amd" "^7.14.5"
+ "@babel/plugin-transform-modules-commonjs" "^7.15.4"
+ "@babel/plugin-transform-modules-systemjs" "^7.15.4"
+ "@babel/plugin-transform-modules-umd" "^7.14.5"
+ "@babel/plugin-transform-named-capturing-groups-regex" "^7.14.9"
+ "@babel/plugin-transform-new-target" "^7.14.5"
+ "@babel/plugin-transform-object-super" "^7.14.5"
+ "@babel/plugin-transform-parameters" "^7.15.4"
+ "@babel/plugin-transform-property-literals" "^7.14.5"
+ "@babel/plugin-transform-regenerator" "^7.14.5"
+ "@babel/plugin-transform-reserved-words" "^7.14.5"
+ "@babel/plugin-transform-shorthand-properties" "^7.14.5"
+ "@babel/plugin-transform-spread" "^7.14.6"
+ "@babel/plugin-transform-sticky-regex" "^7.14.5"
+ "@babel/plugin-transform-template-literals" "^7.14.5"
+ "@babel/plugin-transform-typeof-symbol" "^7.14.5"
+ "@babel/plugin-transform-unicode-escapes" "^7.14.5"
+ "@babel/plugin-transform-unicode-regex" "^7.14.5"
+ "@babel/preset-modules" "^0.1.4"
+ "@babel/types" "^7.15.6"
+ babel-plugin-polyfill-corejs2 "^0.2.2"
+ babel-plugin-polyfill-corejs3 "^0.2.2"
+ babel-plugin-polyfill-regenerator "^0.2.2"
+ core-js-compat "^3.16.0"
+ semver "^6.3.0"
-"@babel/preset-modules@^0.1.3":
+"@babel/preset-modules@^0.1.4":
version "0.1.4"
resolved "https://registry.yarnpkg.com/@babel/preset-modules/-/preset-modules-0.1.4.tgz#362f2b68c662842970fdb5e254ffc8fc1c2e415e"
integrity sha512-J36NhwnfdzpmH41M1DrnkkgAqhZaqr/NBdPfQ677mLzlaXo+oDiv1deyCDtgAhz8p328otdob0Du7+xgHGZbKg==
@@ -797,63 +865,62 @@
esutils "^2.0.2"
"@babel/runtime@^7.11.0", "@babel/runtime@^7.8.4":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.12.13.tgz#0a21452352b02542db0ffb928ac2d3ca7cb6d66d"
- integrity sha512-8+3UMPBrjFa/6TtKi/7sehPKqfAm4g6K+YQjyyFOLUTxzOngcRZTlAVY8sc2CORJYqdHQY8gRPHmn+qo15rCBw==
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.15.4.tgz#fd17d16bfdf878e6dd02d19753a39fa8a8d9c84a"
+ integrity sha512-99catp6bHCaxr4sJ/DbTGgHS4+Rs2RVd2g7iOap6SLGPDknRK9ztKNsE/Fg6QhSeh1FGE5f6gHGQmvvn3I3xhw==
dependencies:
regenerator-runtime "^0.13.4"
-"@babel/template@^7.0.0", "@babel/template@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.12.13.tgz#530265be8a2589dbb37523844c5bcb55947fb327"
- integrity sha512-/7xxiGA57xMo/P2GVvdEumr8ONhFOhfgq2ihK3h1e6THqzTAkHbkXgB0xI9yeTfIUoH3+oAeHhqm/I43OTbbjA==
- dependencies:
- "@babel/code-frame" "^7.12.13"
- "@babel/parser" "^7.12.13"
- "@babel/types" "^7.12.13"
-
-"@babel/traverse@^7.0.0", "@babel/traverse@^7.12.13":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.12.13.tgz#689f0e4b4c08587ad26622832632735fb8c4e0c0"
- integrity sha512-3Zb4w7eE/OslI0fTp8c7b286/cQps3+vdLW3UcwC8VSJC6GbKn55aeVVu2QJNuCDoeKyptLOFrPq8WqZZBodyA==
- dependencies:
- "@babel/code-frame" "^7.12.13"
- "@babel/generator" "^7.12.13"
- "@babel/helper-function-name" "^7.12.13"
- "@babel/helper-split-export-declaration" "^7.12.13"
- "@babel/parser" "^7.12.13"
- "@babel/types" "^7.12.13"
+"@babel/template@^7.0.0", "@babel/template@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.15.4.tgz#51898d35dcf3faa670c4ee6afcfd517ee139f194"
+ integrity sha512-UgBAfEa1oGuYgDIPM2G+aHa4Nlo9Lh6mGD2bDBGMTbYnc38vulXPuC1MGjYILIEmlwl6Rd+BPR9ee3gm20CBtg==
+ dependencies:
+ "@babel/code-frame" "^7.14.5"
+ "@babel/parser" "^7.15.4"
+ "@babel/types" "^7.15.4"
+
+"@babel/traverse@^7.0.0", "@babel/traverse@^7.13.0", "@babel/traverse@^7.15.4":
+ version "7.15.4"
+ resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.15.4.tgz#ff8510367a144bfbff552d9e18e28f3e2889c22d"
+ integrity sha512-W6lQD8l4rUbQR/vYgSuCAE75ADyyQvOpFVsvPPdkhf6lATXAsQIG9YdtOcu8BB1dZ0LKu+Zo3c1wEcbKeuhdlA==
+ dependencies:
+ "@babel/code-frame" "^7.14.5"
+ "@babel/generator" "^7.15.4"
+ "@babel/helper-function-name" "^7.15.4"
+ "@babel/helper-hoist-variables" "^7.15.4"
+ "@babel/helper-split-export-declaration" "^7.15.4"
+ "@babel/parser" "^7.15.4"
+ "@babel/types" "^7.15.4"
debug "^4.1.0"
globals "^11.1.0"
- lodash "^4.17.19"
-"@babel/types@^7.0.0", "@babel/types@^7.12.1", "@babel/types@^7.12.13", "@babel/types@^7.4.4":
- version "7.12.13"
- resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.12.13.tgz#8be1aa8f2c876da11a9cf650c0ecf656913ad611"
- integrity sha512-oKrdZTld2im1z8bDwTOQvUbxKwE+854zc16qWZQlcTqMN00pWxHQ4ZeOq0yDMnisOpRykH2/5Qqcrk/OlbAjiQ==
+"@babel/types@^7.0.0", "@babel/types@^7.15.4", "@babel/types@^7.15.6", "@babel/types@^7.4.4":
+ version "7.15.6"
+ resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.15.6.tgz#99abdc48218b2881c058dd0a7ab05b99c9be758f"
+ integrity sha512-BPU+7QhqNjmWyDO0/vitH/CuhpV8ZmK1wpKva8nuyNF5MJfuRNWMc+hc14+u9xT93kvykMdncrJT19h74uB1Ig==
dependencies:
- "@babel/helper-validator-identifier" "^7.12.11"
- lodash "^4.17.19"
+ "@babel/helper-validator-identifier" "^7.14.9"
to-fast-properties "^2.0.0"
-"@fortawesome/fontawesome-common-types@^0.2.34":
- version "0.2.34"
- resolved "https://registry.yarnpkg.com/@fortawesome/fontawesome-common-types/-/fontawesome-common-types-0.2.34.tgz#0a8c348bb23b7b760030f5b1d912e582be4ec915"
- integrity sha512-XcIn3iYbTEzGIxD0/dY5+4f019jIcEIWBiHc3KrmK/ROahwxmZ/s+tdj97p/5K0klz4zZUiMfUlYP0ajhSJjmA==
+"@fortawesome/fontawesome-common-types@^0.2.36":
+ version "0.2.36"
+ resolved "https://registry.yarnpkg.com/@fortawesome/fontawesome-common-types/-/fontawesome-common-types-0.2.36.tgz#b44e52db3b6b20523e0c57ef8c42d315532cb903"
+ integrity sha512-a/7BiSgobHAgBWeN7N0w+lAhInrGxksn13uK7231n2m8EDPE3BMCl9NZLTGrj9ZXfCmC6LM0QLqXidIizVQ6yg==
"@fortawesome/fontawesome-svg-core@^1.2.19":
- version "1.2.34"
- resolved "https://registry.yarnpkg.com/@fortawesome/fontawesome-svg-core/-/fontawesome-svg-core-1.2.34.tgz#1d1a7c92537cbc2b8a83eef6b6d824b4b5b46b26"
- integrity sha512-0KNN0nc5eIzaJxlv43QcDmTkDY1CqeN6J7OCGSs+fwGPdtv0yOQqRjieopBCmw+yd7uD3N2HeNL3Zm5isDleLg==
+ version "1.2.36"
+ resolved "https://registry.yarnpkg.com/@fortawesome/fontawesome-svg-core/-/fontawesome-svg-core-1.2.36.tgz#4f2ea6f778298e0c47c6524ce2e7fd58eb6930e3"
+ integrity sha512-YUcsLQKYb6DmaJjIHdDWpBIGCcyE/W+p/LMGvjQem55Mm2XWVAP5kWTMKWLv9lwpCVjpLxPyOMOyUocP1GxrtA==
dependencies:
- "@fortawesome/fontawesome-common-types" "^0.2.34"
+ "@fortawesome/fontawesome-common-types" "^0.2.36"
"@fortawesome/free-solid-svg-icons@^5.9.0":
- version "5.15.2"
- resolved "https://registry.yarnpkg.com/@fortawesome/free-solid-svg-icons/-/free-solid-svg-icons-5.15.2.tgz#25bb035de57cf85aee8072965732368ccc8e8943"
- integrity sha512-ZfCU+QjaFsdNZmOGmfqEWhzI3JOe37x5dF4kz9GeXvKn/sTxhqMtZ7mh3lBf76SvcYY5/GKFuyG7p1r4iWMQqw==
+ version "5.15.4"
+ resolved "https://registry.yarnpkg.com/@fortawesome/free-solid-svg-icons/-/free-solid-svg-icons-5.15.4.tgz#2a68f3fc3ddda12e52645654142b9e4e8fbb6cc5"
+ integrity sha512-JLmQfz6tdtwxoihXLg6lT78BorrFyCf59SAwBM6qV/0zXyVeDygJVb3fk+j5Qat+Yvcxp1buLTY5iDh1ZSAQ8w==
dependencies:
- "@fortawesome/fontawesome-common-types" "^0.2.34"
+ "@fortawesome/fontawesome-common-types" "^0.2.36"
"@fortawesome/vue-fontawesome@^0.1.6":
version "0.1.10"
@@ -894,32 +961,32 @@
defer-to-connect "^1.0.1"
"@types/glob@^7.1.1":
- version "7.1.3"
- resolved "https://registry.yarnpkg.com/@types/glob/-/glob-7.1.3.tgz#e6ba80f36b7daad2c685acd9266382e68985c183"
- integrity sha512-SEYeGAIQIQX8NN6LDKprLjbrd5dARM5EXsd8GI/A5l0apYI1fGMWgPHSe4ZKL4eozlAyI+doUE9XbYS4xCkQ1w==
+ version "7.1.4"
+ resolved "https://registry.yarnpkg.com/@types/glob/-/glob-7.1.4.tgz#ea59e21d2ee5c517914cb4bc8e4153b99e566672"
+ integrity sha512-w+LsMxKyYQm347Otw+IfBXOv9UWVjpHpCDdbBMt8Kz/xbvCYNjP+0qPh91Km3iKfSRLBB0P7fAMf0KHrPu+MyA==
dependencies:
"@types/minimatch" "*"
"@types/node" "*"
"@types/json-schema@^7.0.5":
- version "7.0.7"
- resolved "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.7.tgz#98a993516c859eb0d5c4c8f098317a9ea68db9ad"
- integrity sha512-cxWFQVseBm6O9Gbw1IWb8r6OS4OhSt3hPZLkFApLjM8TEXROBuQGLAH2i2gZpcXdLBIrpXuTDhH7Vbm1iXmNGA==
+ version "7.0.9"
+ resolved "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.9.tgz#97edc9037ea0c38585320b28964dde3b39e4660d"
+ integrity sha512-qcUXuemtEu+E5wZSJHNxUXeCZhAfXKQ41D+duX+VYPde7xyEVZci+/oXKJL13tnRs9lR2pr4fod59GT6/X1/yQ==
"@types/minimatch@*":
- version "3.0.3"
- resolved "https://registry.yarnpkg.com/@types/minimatch/-/minimatch-3.0.3.tgz#3dca0e3f33b200fc7d1139c0cd96c1268cadfd9d"
- integrity sha512-tHq6qdbT9U1IRSGf14CL0pUlULksvY9OZ+5eEgl1N7t+OA3tGvNpxJCzuKQlsNgCVwbAs670L1vcVQi8j9HjnA==
+ version "3.0.5"
+ resolved "https://registry.yarnpkg.com/@types/minimatch/-/minimatch-3.0.5.tgz#1001cc5e6a3704b83c236027e77f2f58ea010f40"
+ integrity sha512-Klz949h02Gz2uZCMGwDUSDS1YBlTdDDgbWHi+81l29tQALUtvz4rAYi5uoVhE5Lagoq6DeqAUlbrHvW/mXDgdQ==
"@types/node@*":
- version "14.14.25"
- resolved "https://registry.yarnpkg.com/@types/node/-/node-14.14.25.tgz#15967a7b577ff81383f9b888aa6705d43fbbae93"
- integrity sha512-EPpXLOVqDvisVxtlbvzfyqSsFeQxltFbluZNRndIb8tr9KiBnYNLzrc1N3pyKUCww2RNrfHDViqDWWE1LCJQtQ==
+ version "16.9.1"
+ resolved "https://registry.yarnpkg.com/@types/node/-/node-16.9.1.tgz#0611b37db4246c937feef529ddcc018cf8e35708"
+ integrity sha512-QpLcX9ZSsq3YYUUnD3nFDY8H7wctAhQj/TFKL8Ya8v5fMm3CFXxo8zStsLAl780ltoYoo1WvKUVGBQK+1ifr7g==
"@types/q@^1.5.1":
- version "1.5.4"
- resolved "https://registry.yarnpkg.com/@types/q/-/q-1.5.4.tgz#15925414e0ad2cd765bfef58842f7e26a7accb24"
- integrity sha512-1HcDas8SEj4z1Wc696tH56G8OlRaH/sqZOynNNB+HF0WOeXPaxTtbYzJY2oEfiUxjSKjhCKr+MvR7dCHcEelug==
+ version "1.5.5"
+ resolved "https://registry.yarnpkg.com/@types/q/-/q-1.5.5.tgz#75a2a8e7d8ab4b230414505d92335d1dcb53a6df"
+ integrity sha512-L28j2FcJfSZOnL1WBjDYp2vUHCeIFlyYI/53EwD/rKUBQ7MtUUfbQWiyKJGpcnv4/WgrhWsFKrcPstcAt/J0tQ==
"@vue/babel-helper-vue-jsx-merge-props@^1.2.1":
version "1.2.1"
@@ -931,10 +998,10 @@
resolved "https://registry.yarnpkg.com/@vue/babel-helper-vue-transform-on/-/babel-helper-vue-transform-on-1.0.2.tgz#9b9c691cd06fc855221a2475c3cc831d774bc7dc"
integrity sha512-hz4R8tS5jMn8lDq6iD+yWL6XNB699pGIVLk7WSJnn1dbpjaazsjZQkieJoRX6gW5zpYSCFqQ7jUquPNY65tQYA==
-"@vue/babel-plugin-jsx@^1.0.0-0":
- version "1.0.3"
- resolved "https://registry.yarnpkg.com/@vue/babel-plugin-jsx/-/babel-plugin-jsx-1.0.3.tgz#ad5ee86ebc9fc40900add9914534e223c719eace"
- integrity sha512-+52ZQFmrM0yh61dQlgwQlfHZXmYbswbQEL25SOSt9QkjegAdfIGu87oELw0l8H6cuJYazZCiNjPR9eU++ZIbxg==
+"@vue/babel-plugin-jsx@^1.0.3":
+ version "1.0.7"
+ resolved "https://registry.yarnpkg.com/@vue/babel-plugin-jsx/-/babel-plugin-jsx-1.0.7.tgz#22d6c84ef8db5ac13db971476a55cc5215902168"
+ integrity sha512-B5ctmlVk+vfyIV6PuvQkRB512c6LX2BUvJdNP9gOcllnpg9yrls9bDi7b3+tkAdT8+w1OoWsuJHHEV0Ntd67KQ==
dependencies:
"@babel/helper-module-imports" "^7.0.0"
"@babel/plugin-syntax-jsx" "^7.0.0"
@@ -959,9 +1026,9 @@
svg-tags "^1.0.0"
"@vue/babel-preset-app@^4.1.2":
- version "4.5.11"
- resolved "https://registry.yarnpkg.com/@vue/babel-preset-app/-/babel-preset-app-4.5.11.tgz#f677bc10472e418f71f61f10dde5a79976a215b8"
- integrity sha512-9VoFlm/9vhynKNGM+HA7qBsoQSUEnuG5i5kcFI9vTLLrh8A0fxrwUyVLLppO6T1sAZ6vrKdQFnEkjL+RkRAwWQ==
+ version "4.5.13"
+ resolved "https://registry.yarnpkg.com/@vue/babel-preset-app/-/babel-preset-app-4.5.13.tgz#cb475321e4c73f7f110dac29a48c2a9cb80afeb6"
+ integrity sha512-pM7CR3yXB6L8Gfn6EmX7FLNE3+V/15I3o33GkSNsWvgsMp6HVGXKkXgojrcfUUauyL1LZOdvTmu4enU2RePGHw==
dependencies:
"@babel/core" "^7.11.0"
"@babel/helper-compilation-targets" "^7.9.6"
@@ -973,14 +1040,14 @@
"@babel/plugin-transform-runtime" "^7.11.0"
"@babel/preset-env" "^7.11.0"
"@babel/runtime" "^7.11.0"
- "@vue/babel-plugin-jsx" "^1.0.0-0"
- "@vue/babel-preset-jsx" "^1.1.2"
+ "@vue/babel-plugin-jsx" "^1.0.3"
+ "@vue/babel-preset-jsx" "^1.2.4"
babel-plugin-dynamic-import-node "^2.3.3"
core-js "^3.6.5"
core-js-compat "^3.6.5"
semver "^6.1.0"
-"@vue/babel-preset-jsx@^1.1.2":
+"@vue/babel-preset-jsx@^1.2.4":
version "1.2.4"
resolved "https://registry.yarnpkg.com/@vue/babel-preset-jsx/-/babel-preset-jsx-1.2.4.tgz#92fea79db6f13b01e80d3a0099e2924bdcbe4e87"
integrity sha512-oRVnmN2a77bYDJzeGSt92AuHXbkIxbf/XXSE3klINnh9AXBmVS1DGa1f0d+dDYpLfsAKElMnqKTQfKn7obcL4w==
@@ -1044,33 +1111,33 @@
camelcase "^5.0.0"
"@vue/component-compiler-utils@^3.1.0":
- version "3.2.0"
- resolved "https://registry.yarnpkg.com/@vue/component-compiler-utils/-/component-compiler-utils-3.2.0.tgz#8f85182ceed28e9b3c75313de669f83166d11e5d"
- integrity sha512-lejBLa7xAMsfiZfNp7Kv51zOzifnb29FwdnMLa96z26kXErPFioSf9BMcePVIQ6/Gc6/mC0UrPpxAWIHyae0vw==
+ version "3.2.2"
+ resolved "https://registry.yarnpkg.com/@vue/component-compiler-utils/-/component-compiler-utils-3.2.2.tgz#2f7ed5feed82ff7f0284acc11d525ee7eff22460"
+ integrity sha512-rAYMLmgMuqJFWAOb3Awjqqv5X3Q3hVr4jH/kgrFJpiU0j3a90tnNBplqbj+snzrgZhC9W128z+dtgMifOiMfJg==
dependencies:
consolidate "^0.15.1"
hash-sum "^1.0.2"
lru-cache "^4.1.2"
merge-source-map "^1.1.0"
- postcss "^7.0.14"
+ postcss "^7.0.36"
postcss-selector-parser "^6.0.2"
source-map "~0.6.1"
vue-template-es2015-compiler "^1.9.0"
optionalDependencies:
prettier "^1.18.2"
-"@vuepress/core@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/core/-/core-1.8.0.tgz#b5450cdd33d7fc1e1d21a1590806d429c92d0dc9"
- integrity sha512-DrHx3gXa5rUDdvjcUHhmZg1DccMwc3kiYpgtbKCuJpHksz9eAVuOxbcy/b6TGRbbY4Q5EA2Fs3kI9hvPjYdCrQ==
+"@vuepress/core@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/core/-/core-1.8.2.tgz#4f5bafc894691bfea4146294a582a129483daf2a"
+ integrity sha512-lh9BLC06k9s0wxTuWtCkiNj49fkbW87enp0XSrFZHEoyDGSGndQjZmMMErcHc5Hx7nrW1nzc33sPH1NNtJl0hw==
dependencies:
"@babel/core" "^7.8.4"
"@vue/babel-preset-app" "^4.1.2"
- "@vuepress/markdown" "1.8.0"
- "@vuepress/markdown-loader" "1.8.0"
- "@vuepress/plugin-last-updated" "1.8.0"
- "@vuepress/plugin-register-components" "1.8.0"
- "@vuepress/shared-utils" "1.8.0"
+ "@vuepress/markdown" "1.8.2"
+ "@vuepress/markdown-loader" "1.8.2"
+ "@vuepress/plugin-last-updated" "1.8.2"
+ "@vuepress/plugin-register-components" "1.8.2"
+ "@vuepress/shared-utils" "1.8.2"
autoprefixer "^9.5.1"
babel-loader "^8.0.4"
cache-loader "^3.0.0"
@@ -1103,21 +1170,21 @@
webpack-merge "^4.1.2"
webpackbar "3.2.0"
-"@vuepress/markdown-loader@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/markdown-loader/-/markdown-loader-1.8.0.tgz#0d7493995869f974953b1aa47c7a791943d1d835"
- integrity sha512-ykYTNe4mC/0CxyEfyM9+oYJqFvOMZWw5qiNZVfg2t+Ip8nVR2pFhQ6fJe07Pbtc59eT4awKSEd8/kcjhTpfeZA==
+"@vuepress/markdown-loader@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/markdown-loader/-/markdown-loader-1.8.2.tgz#b2a58291a967f2bbe0af6e58f9542f5911879233"
+ integrity sha512-mWzFXikCUcAN/chpKkqZpRYKdo0312hMv8cBea2hvrJYV6y4ODB066XKvXN8JwOcxuCjxWYJkhWGr+pXq1oTtw==
dependencies:
- "@vuepress/markdown" "1.8.0"
+ "@vuepress/markdown" "1.8.2"
loader-utils "^1.1.0"
lru-cache "^5.1.1"
-"@vuepress/markdown@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/markdown/-/markdown-1.8.0.tgz#2fb0a9f6011d2543a4dc7d6a2ae976b9f49873ef"
- integrity sha512-f2yhoIHTD6gaPeLLidkxuytKGQCT6Gopm0fpyKZwfFZaWWz5+RPPGevq5UTmTb+5vvO2Li44HJc1EV7QONOw9Q==
+"@vuepress/markdown@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/markdown/-/markdown-1.8.2.tgz#50ea5a1962591a436b26d1aa2b111df37eb9ea8a"
+ integrity sha512-zznBHVqW+iBkznF/BO/GY9RFu53khyl0Ey0PnGqvwCJpRLNan6y5EXgYumtjw2GSYn5nDTTALYxtyNBdz64PKg==
dependencies:
- "@vuepress/shared-utils" "1.8.0"
+ "@vuepress/shared-utils" "1.8.2"
markdown-it "^8.4.1"
markdown-it-anchor "^5.0.2"
markdown-it-chain "^1.3.0"
@@ -1125,10 +1192,10 @@
markdown-it-table-of-contents "^0.4.0"
prismjs "^1.13.0"
-"@vuepress/plugin-active-header-links@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/plugin-active-header-links/-/plugin-active-header-links-1.8.0.tgz#1e3f9c1057a58f3bc849d0eebbcd492975f63a88"
- integrity sha512-0SqdkJLJSQqhPTgGccu/ev5zRCfeKKMkyPnUMJYsQe4zGhSosmwLcfB7LDo/VLqLhRipipzBnONESr12OgI4SQ==
+"@vuepress/plugin-active-header-links@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/plugin-active-header-links/-/plugin-active-header-links-1.8.2.tgz#0cb9b29c826dd97d35357a9b09c962ef782cb793"
+ integrity sha512-JmXAQg8D7J8mcKe2Ue3BZ9dOCzJMJXP4Cnkkc/IrqfDg0ET0l96gYWZohCqlvRIWt4f0VPiFAO4FLYrW+hko+g==
dependencies:
lodash.debounce "^4.0.8"
@@ -1139,43 +1206,43 @@
dependencies:
lodash.debounce "^4.0.8"
-"@vuepress/plugin-last-updated@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/plugin-last-updated/-/plugin-last-updated-1.8.0.tgz#a0fcd2906a4dcae107634013f7c49ddd05e0de87"
- integrity sha512-fBwtlffAabpTTalUMPSaJy/5fp3WpIA1FdWOfFcQ12X6179tupZB8fnueNsVJGBvGcdw8fbyzh5C9yKAq9lR/w==
+"@vuepress/plugin-last-updated@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/plugin-last-updated/-/plugin-last-updated-1.8.2.tgz#7ce689f8d5050cf0213949bc2e5aa879c09ff4b1"
+ integrity sha512-pYIRZi52huO9b6HY3JQNPKNERCLzMHejjBRt9ekdnJ1xhLs4MmRvt37BoXjI/qzvXkYtr7nmGgnKThNBVRTZuA==
dependencies:
cross-spawn "^6.0.5"
-"@vuepress/plugin-medium-zoom@^1.7.1":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/plugin-medium-zoom/-/plugin-medium-zoom-1.8.0.tgz#e7bff4dd0af58929c16d3feaa8f47dfa6cedac34"
- integrity sha512-mx+abkOVm/+hBFsE26xzcfHSB1EknUr7UJx1UKgHm2368odFhz5HMB68gFfslMKjwfKjfgNgP/Bm/zwWcbQXmw==
+"@vuepress/plugin-medium-zoom@^1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/plugin-medium-zoom/-/plugin-medium-zoom-1.8.2.tgz#0243dd27edf0c710f9a41a234d253d76ab51e625"
+ integrity sha512-Mljso/8E6IbNmIKmwKeC6FDfnhKY3fsOUSs5kEGzz3RQwd54eshqHAMRVwW4LZkYZHhwQXF8+qk7YqoMZB7jjg==
dependencies:
medium-zoom "^1.0.4"
-"@vuepress/plugin-nprogress@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/plugin-nprogress/-/plugin-nprogress-1.8.0.tgz#8fd3d5415d4c8326ca569118e935b875e5fd7bb5"
- integrity sha512-JmjeJKKWhbF/8z+EnY8BCWHoHKhUWfqXjXOfV+xifITl6BJlf53I/jLFpX7Sij8Whe+SKjH7kNvc+hioUdwJQw==
+"@vuepress/plugin-nprogress@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/plugin-nprogress/-/plugin-nprogress-1.8.2.tgz#dc6c082925420c8c59ecb7fc2d4a9401f6d4664a"
+ integrity sha512-3TOBee2NM3WLr1tdjDTGfrAMggjN+OlEPyKyv8FqThsVkDYhw48O3HwqlThp9KX7UbL3ExxIFBwWRFLC+kYrdw==
dependencies:
nprogress "^0.2.0"
-"@vuepress/plugin-register-components@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/plugin-register-components/-/plugin-register-components-1.8.0.tgz#cb23c8b54865926f16e81fdf5fa6ccf0dec17c0e"
- integrity sha512-ztafaAxn7XFS4F8z51d+QQB6DNAUG54wBSdfKydfnHbAYgtxoALzPlJW7FKQdxvZKxqGrJa9e4rkoZsat13KRQ==
+"@vuepress/plugin-register-components@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/plugin-register-components/-/plugin-register-components-1.8.2.tgz#2fb45a68b0a1efb8822670d95c3b231a2d0eb74d"
+ integrity sha512-6SUq3nHFMEh9qKFnjA8QnrNxj0kLs7+Gspq1OBU8vtu0NQmSvLFZVaMV7pzT/9zN2nO5Pld5qhsUJv1g71MrEA==
dependencies:
- "@vuepress/shared-utils" "1.8.0"
+ "@vuepress/shared-utils" "1.8.2"
-"@vuepress/plugin-search@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/plugin-search/-/plugin-search-1.8.0.tgz#d10cc04cff7467829b2e2e896b7e72a5ebc27ce1"
- integrity sha512-LlOCPg7JJ3I9WEpiBU8vCEFp6I5sa3OBu6SFHk+uK9iyKHwJYdRs4VK9x+igG40Rt/OIDRDo3c9SbLX/E/kqeA==
+"@vuepress/plugin-search@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/plugin-search/-/plugin-search-1.8.2.tgz#74b92f663acf6b4560e15dc0442a84c4e874e206"
+ integrity sha512-JrSJr9o0Kar14lVtZ4wfw39pplxvvMh8vDBD9oW09a+6Zi/4bySPGdcdaqdqGW+OHSiZNvG+6uyfKSBBBqF6PA==
-"@vuepress/shared-utils@1.8.0", "@vuepress/shared-utils@^1.2.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/shared-utils/-/shared-utils-1.8.0.tgz#b1187c764f4c2dee018b83f3560a14067d931240"
- integrity sha512-CVNMiYBntQyb4CuyS4KzmglDqsuBpj8V4QMzL9gCSoMv0VmwKx05fZedu+r0G5OcxYN4qjnu99yl9G6zWhOU9w==
+"@vuepress/shared-utils@1.8.2", "@vuepress/shared-utils@^1.2.0":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/shared-utils/-/shared-utils-1.8.2.tgz#5ec1601f2196aca34ad82eed7c9be2d7948f705b"
+ integrity sha512-6kGubc7iBDWruEBUU7yR+sQ++SOhMuvKWvWeTZJKRZedthycdzYz7QVpua0FaZSAJm5/dIt8ymU4WQvxTtZgTQ==
dependencies:
chalk "^2.3.2"
escape-html "^1.0.3"
@@ -1187,14 +1254,14 @@
toml "^3.0.0"
upath "^1.1.0"
-"@vuepress/theme-default@1.8.0":
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/@vuepress/theme-default/-/theme-default-1.8.0.tgz#5bcca542bc61099498f5d99a9928f0ff66e6e382"
- integrity sha512-CueCaANfICFbLnEL78YxSjgCHXL7mkgQI/cfyEHBgxlr247cYJQ+9IFDQIS0fJNuzHdLRy9UFUvVrCu6go8PUg==
+"@vuepress/theme-default@1.8.2":
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/@vuepress/theme-default/-/theme-default-1.8.2.tgz#7f474036c752c1f9801b83f68f5c70c092b182b4"
+ integrity sha512-rE7M1rs3n2xp4a/GrweO8EGwqFn3EA5gnFWdVmVIHyr7C1nix+EqjpPQF1SVWNnIrDdQuCw38PqS+oND1K2vYw==
dependencies:
- "@vuepress/plugin-active-header-links" "1.8.0"
- "@vuepress/plugin-nprogress" "1.8.0"
- "@vuepress/plugin-search" "1.8.0"
+ "@vuepress/plugin-active-header-links" "1.8.2"
+ "@vuepress/plugin-nprogress" "1.8.2"
+ "@vuepress/plugin-search" "1.8.2"
docsearch.js "^2.5.2"
lodash "^4.17.15"
stylus "^0.54.8"
@@ -1444,11 +1511,11 @@ ansi-colors@^3.0.0:
integrity sha512-hHUXGagefjN2iRrID63xckIvotOXOojhQKWIPUZ4mNUZ9nLZW+7FMNoE1lOkEhNWYsx/7ysGIuJYCiMAA9FnrA==
ansi-escapes@^4.1.0:
- version "4.3.1"
- resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-4.3.1.tgz#a5c47cc43181f1f38ffd7076837700d395522a61"
- integrity sha512-JWF7ocqNrp8u9oqpgV+wH5ftbt+cfvv+PTjOvKLT3AdYly/LmORARfEVT1iyjwN+4MqE5UmVKoAdIBqeoCHgLA==
+ version "4.3.2"
+ resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-4.3.2.tgz#6b2291d1db7d98b6521d5f1efa42d0f3a9feb65e"
+ integrity sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==
dependencies:
- type-fest "^0.11.0"
+ type-fest "^0.21.3"
ansi-html@0.0.7:
version "0.0.7"
@@ -1471,9 +1538,9 @@ ansi-regex@^4.1.0:
integrity sha512-1apePfXM1UOSqw0o9IiFAovVz9M5S1Dg+4TrDwfMewQ6p/rmMueb7tWZjQ1rx4Loy1ArBggoqGpfqqdI4rondg==
ansi-regex@^5.0.0:
- version "5.0.0"
- resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.0.tgz#388539f55179bf39339c81af30a654d69f87cb75"
- integrity sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==
+ version "5.0.1"
+ resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.1.tgz#082cb2c89c9fe8659a311a53bd6a4dc5301db304"
+ integrity sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==
ansi-styles@^2.2.1:
version "2.2.1"
@@ -1502,10 +1569,10 @@ anymatch@^2.0.0:
micromatch "^3.1.4"
normalize-path "^2.1.1"
-anymatch@~3.1.1:
- version "3.1.1"
- resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-3.1.1.tgz#c55ecf02185e2469259399310c173ce31233b142"
- integrity sha512-mM8522psRCqzV+6LhomX5wgp25YVibjh8Wj23I5RPkPppSVSjyKD2A2mBJmWGa+KN7f2D6LNh9jkBCeyLktzjg==
+anymatch@~3.1.2:
+ version "3.1.2"
+ resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-3.1.2.tgz#c0557c096af32f106198f4f4e2a383537e378716"
+ integrity sha512-P43ePfOAIupkguHUycrc4qJ9kz8ZiuOUijaETwX7THt0Y/GNK7v0aa8rY816xWjZ7rJdA5XdMcpVFTKMq+RvWg==
dependencies:
normalize-path "^3.0.0"
picomatch "^2.0.4"
@@ -1516,9 +1583,9 @@ aproba@^1.0.3, aproba@^1.1.1:
integrity sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==
are-we-there-yet@~1.1.2:
- version "1.1.5"
- resolved "https://registry.yarnpkg.com/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz#4b35c2944f062a8bfcda66410760350fe9ddfc21"
- integrity sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==
+ version "1.1.7"
+ resolved "https://registry.yarnpkg.com/are-we-there-yet/-/are-we-there-yet-1.1.7.tgz#b15474a932adab4ff8a50d9adfa7e4e926f21146"
+ integrity sha512-nxwy40TuMiUGqMyRHgCSWZ9FM4VAoRP4xUYSTv5ImRog+h9yISPbVH7H8fASCIzYn9wlEv4zvFL7uKDMCFQm3g==
dependencies:
delegates "^1.0.0"
readable-stream "^2.0.6"
@@ -1691,10 +1758,34 @@ babel-plugin-dynamic-import-node@^2.3.3:
dependencies:
object.assign "^4.1.0"
+babel-plugin-polyfill-corejs2@^0.2.2:
+ version "0.2.2"
+ resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.2.2.tgz#e9124785e6fd94f94b618a7954e5693053bf5327"
+ integrity sha512-kISrENsJ0z5dNPq5eRvcctITNHYXWOA4DUZRFYCz3jYCcvTb/A546LIddmoGNMVYg2U38OyFeNosQwI9ENTqIQ==
+ dependencies:
+ "@babel/compat-data" "^7.13.11"
+ "@babel/helper-define-polyfill-provider" "^0.2.2"
+ semver "^6.1.1"
+
+babel-plugin-polyfill-corejs3@^0.2.2:
+ version "0.2.4"
+ resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.2.4.tgz#68cb81316b0e8d9d721a92e0009ec6ecd4cd2ca9"
+ integrity sha512-z3HnJE5TY/j4EFEa/qpQMSbcUJZ5JQi+3UFjXzn6pQCmIKc5Ug5j98SuYyH+m4xQnvKlMDIW4plLfgyVnd0IcQ==
+ dependencies:
+ "@babel/helper-define-polyfill-provider" "^0.2.2"
+ core-js-compat "^3.14.0"
+
+babel-plugin-polyfill-regenerator@^0.2.2:
+ version "0.2.2"
+ resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.2.2.tgz#b310c8d642acada348c1fa3b3e6ce0e851bee077"
+ integrity sha512-Goy5ghsc21HgPDFtzRkSirpZVW35meGoTmTOb2bxqdl60ghub4xOidgNTHaZfQ2FaxQsKmwvXtOAkcIS4SMBWg==
+ dependencies:
+ "@babel/helper-define-polyfill-provider" "^0.2.2"
+
balanced-match@^1.0.0:
- version "1.0.0"
- resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.0.tgz#89b4d199ab2bee49de164ea02b89ce462d71b767"
- integrity sha1-ibTRmasr7kneFk6gK4nORi1xt2c=
+ version "1.0.2"
+ resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.2.tgz#e83e3a7e3f300b34cb9d87f615fa0cbf357690ee"
+ integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==
base64-js@^1.0.2:
version "1.5.1"
@@ -1766,14 +1857,14 @@ bluebird@^3.1.1, bluebird@^3.5.5:
integrity sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==
bn.js@^4.0.0, bn.js@^4.1.0, bn.js@^4.11.9:
- version "4.11.9"
- resolved "https://registry.yarnpkg.com/bn.js/-/bn.js-4.11.9.tgz#26d556829458f9d1e81fc48952493d0ba3507828"
- integrity sha512-E6QoYqCKZfgatHTdHzs1RRKP7ip4vvm+EyRUeE2RF0NblwVvb0p6jSVeNTOFxPn26QXN2o6SMfNxKp6kU8zQaw==
+ version "4.12.0"
+ resolved "https://registry.yarnpkg.com/bn.js/-/bn.js-4.12.0.tgz#775b3f278efbb9718eec7361f483fb36fbbfea88"
+ integrity sha512-c98Bf3tPniI+scsdk237ku1Dc3ujXQTSgyiPUDEOe7tRkhrqridvh8klBv0HCEso1OLOYcHuCv/cS6DNxKH+ZA==
bn.js@^5.0.0, bn.js@^5.1.1:
- version "5.1.3"
- resolved "https://registry.yarnpkg.com/bn.js/-/bn.js-5.1.3.tgz#beca005408f642ebebea80b042b4d18d2ac0ee6b"
- integrity sha512-GkTiFpjFtUzU9CbMeJ5iazkCzGL3jrhzerzZIuqLABjbwRaFt33I9tUdSNryIptM+RxDet6OKm2WnLXzW51KsQ==
+ version "5.2.0"
+ resolved "https://registry.yarnpkg.com/bn.js/-/bn.js-5.2.0.tgz#358860674396c6997771a9d051fcc1b57d4ae002"
+ integrity sha512-D7iWRBvnZE8ecXiLj/9wbxH7Tk79fAh8IHaTNq1RWRixsS02W+5qS+iE9yq6RYl0asXx5tw0bLhmT5pIfbSquw==
body-parser@1.19.0:
version "1.19.0"
@@ -1919,21 +2010,21 @@ browserify-zlib@^0.2.0:
dependencies:
pako "~1.0.5"
-browserslist@^4.0.0, browserslist@^4.12.0, browserslist@^4.14.5, browserslist@^4.16.1:
- version "4.16.3"
- resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.16.3.tgz#340aa46940d7db878748567c5dea24a48ddf3717"
- integrity sha512-vIyhWmIkULaq04Gt93txdh+j02yX/JzlyhLYbV3YQCn/zvES3JnY7TifHHvvr1w5hTDluNKMkV05cs4vy8Q7sw==
+browserslist@^4.0.0, browserslist@^4.12.0, browserslist@^4.16.6, browserslist@^4.17.0:
+ version "4.17.0"
+ resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.17.0.tgz#1fcd81ec75b41d6d4994fb0831b92ac18c01649c"
+ integrity sha512-g2BJ2a0nEYvEFQC208q8mVAhfNwpZ5Mu8BwgtCdZKO3qx98HChmeg448fPdUzld8aFmfLgVh7yymqV+q1lJZ5g==
dependencies:
- caniuse-lite "^1.0.30001181"
- colorette "^1.2.1"
- electron-to-chromium "^1.3.649"
+ caniuse-lite "^1.0.30001254"
+ colorette "^1.3.0"
+ electron-to-chromium "^1.3.830"
escalade "^3.1.1"
- node-releases "^1.1.70"
+ node-releases "^1.1.75"
buffer-from@^1.0.0:
- version "1.1.1"
- resolved "https://registry.yarnpkg.com/buffer-from/-/buffer-from-1.1.1.tgz#32713bc028f75c02fdb710d7c7bcec1f2c6070ef"
- integrity sha512-MQcXEUbCKtEo7bhqEs6560Hyd4XaovZlO/k9V3hjVUF/zwW7KBVdSK4gIt/bzwS9MbR5qob+F5jusZsb0YQK2A==
+ version "1.1.2"
+ resolved "https://registry.yarnpkg.com/buffer-from/-/buffer-from-1.1.2.tgz#2b146a6fd72e80b4f55d255f35ed59a3a9a41bd5"
+ integrity sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==
buffer-indexof@^1.0.0:
version "1.1.1"
@@ -1975,9 +2066,9 @@ bytes@3.1.0:
integrity sha512-zauLjrfCG+xvoyaqLoV8bLVXXNGC4JqlxFCutSDWA6fJrTo2ZuvLYTqZ7aHBLZSMOopbzwv8f+wZcVzfVTI2Dg==
cac@^6.5.6:
- version "6.7.1"
- resolved "https://registry.yarnpkg.com/cac/-/cac-6.7.1.tgz#0609d28a31d887746de4b66a15e3914f106f880c"
- integrity sha512-LfGt47+ugCY65W4yUEyxnZKd/tJSBJD/gUAxQGiQjH7yqdhbaX2XN0Rli4+0W0DJiDONmYeh0TlJxMtXGZspIg==
+ version "6.7.3"
+ resolved "https://registry.yarnpkg.com/cac/-/cac-6.7.3.tgz#10410b8611677990cc2e3c8b576d471c1d71b768"
+ integrity sha512-ECVqVZh74qgSuZG9YOt2OJPI3wGcf+EwwuF/XIOYqZBD0KZYLtgPWqFPxmDPQ6joxI1nOlvVgRV6VT53Ooyocg==
cacache@^12.0.2, cacache@^12.0.3:
version "12.0.4"
@@ -2113,10 +2204,10 @@ caniuse-api@^3.0.0:
lodash.memoize "^4.1.2"
lodash.uniq "^4.5.0"
-caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001109, caniuse-lite@^1.0.30001181:
- version "1.0.30001185"
- resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001185.tgz#3482a407d261da04393e2f0d61eefbc53be43b95"
- integrity sha512-Fpi4kVNtNvJ15H0F6vwmXtb3tukv3Zg3qhKkOGUq7KJ1J6b9kf4dnNgtEAFXhRsJo0gNj9W60+wBvn0JcTvdTg==
+caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001109, caniuse-lite@^1.0.30001254:
+ version "1.0.30001257"
+ resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001257.tgz#150aaf649a48bee531104cfeda57f92ce587f6e5"
+ integrity sha512-JN49KplOgHSXpIsVSF+LUyhD8PUp6xPpAXeRrrcBh4KBeP7W864jHn6RvzJgDlrReyeVjMFJL3PLpPvKIxlIHA==
caseless@~0.12.0:
version "0.12.0"
@@ -2182,19 +2273,19 @@ chokidar@^2.0.3, chokidar@^2.1.8:
fsevents "^1.2.7"
chokidar@^3.4.1:
- version "3.5.1"
- resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.5.1.tgz#ee9ce7bbebd2b79f49f304799d5468e31e14e68a"
- integrity sha512-9+s+Od+W0VJJzawDma/gvBNQqkTiqYTWLuZoyAsivsI4AaWTCzHG06/TMjsf1cYe9Cb97UCEhjz7HvnPk2p/tw==
+ version "3.5.2"
+ resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.5.2.tgz#dba3976fcadb016f66fd365021d91600d01c1e75"
+ integrity sha512-ekGhOnNVPgT77r4K/U3GDhu+FQ2S8TnK/s2KbIGXi0SZWuwkZ2QNyfWdZW+TVfn84DpEP7rLeCt2UI6bJ8GwbQ==
dependencies:
- anymatch "~3.1.1"
+ anymatch "~3.1.2"
braces "~3.0.2"
- glob-parent "~5.1.0"
+ glob-parent "~5.1.2"
is-binary-path "~2.1.0"
is-glob "~4.0.1"
normalize-path "~3.0.0"
- readdirp "~3.5.0"
+ readdirp "~3.6.0"
optionalDependencies:
- fsevents "~2.3.1"
+ fsevents "~2.3.2"
chownr@^1.1.1:
version "1.1.4"
@@ -2202,22 +2293,20 @@ chownr@^1.1.1:
integrity sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==
chrome-trace-event@^1.0.2:
- version "1.0.2"
- resolved "https://registry.yarnpkg.com/chrome-trace-event/-/chrome-trace-event-1.0.2.tgz#234090ee97c7d4ad1a2c4beae27505deffc608a4"
- integrity sha512-9e/zx1jw7B4CO+c/RXoCsfg/x1AfUBioy4owYH0bJprEYAx5hRFLRhWBqHAG57D0ZM4H7vxbP7bPe0VwhQRYDQ==
- dependencies:
- tslib "^1.9.0"
-
-ci-info@^1.6.0:
- version "1.6.0"
- resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-1.6.0.tgz#2ca20dbb9ceb32d4524a683303313f0304b1e497"
- integrity sha512-vsGdkwSCDpWmP80ncATX7iea5DWQemg1UgCW5J8tqjU3lYw4FBYuj89J0CTVomA7BEfvSZd84GmHko+MxFQU2A==
+ version "1.0.3"
+ resolved "https://registry.yarnpkg.com/chrome-trace-event/-/chrome-trace-event-1.0.3.tgz#1015eced4741e15d06664a957dbbf50d041e26ac"
+ integrity sha512-p3KULyQg4S7NIHixdwbGX+nFHkoBiA4YQmyWtjb8XngSKV124nJmRysgAeujbUVb15vh+RvFUfCPqU7rXk+hZg==
ci-info@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-2.0.0.tgz#67a9e964be31a51e15e5010d58e6f12834002f46"
integrity sha512-5tK7EtrZ0N+OLFMthtqOj4fI2Jeb88C4CAZPu25LDVUgXJ0A3Js4PMGqrn0JU1W0Mh1/Z8wZzYPxqUrXeBboCQ==
+ci-info@^3.0.0:
+ version "3.2.0"
+ resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-3.2.0.tgz#2876cb948a498797b5236f0095bc057d0dca38b6"
+ integrity sha512-dVqRX7fLUm8J6FgHJ418XuIgDLZDkYcDFTeL6TA2gt5WlIZUQrrH6EZrNClwT/H0FateUsZkGIOPRrLbP+PR9A==
+
cipher-base@^1.0.0, cipher-base@^1.0.1, cipher-base@^1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/cipher-base/-/cipher-base-1.0.4.tgz#8760e4ecc272f4c363532f926d874aae2c1397de"
@@ -2248,15 +2337,6 @@ cli-boxes@^2.2.0:
resolved "https://registry.yarnpkg.com/cli-boxes/-/cli-boxes-2.2.1.tgz#ddd5035d25094fce220e9cab40a45840a440318f"
integrity sha512-y4coMcylgSCdVinjiDBuR8PCC2bLjyGTwEmPb9NHR/QaNU6EUOXcTY/s6VjGMD6ENSEaeQYHCY0GNGS5jfMwPw==
-clipboard@^2.0.0:
- version "2.0.6"
- resolved "https://registry.yarnpkg.com/clipboard/-/clipboard-2.0.6.tgz#52921296eec0fdf77ead1749421b21c968647376"
- integrity sha512-g5zbiixBRk/wyKakSwCKd7vQXDjFnAMGHoEyBogG/bw9kTD9GvdAvaoRR1ALcEzt3pVKxZR0pViekPMIS0QyGg==
- dependencies:
- good-listener "^1.2.2"
- select "^1.1.2"
- tiny-emitter "^2.0.0"
-
cliui@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-5.0.0.tgz#deefcfdb2e800784aa34f46fa08e06851c7bbbc5"
@@ -2304,7 +2384,7 @@ collection-visit@^1.0.0:
map-visit "^1.0.0"
object-visit "^1.0.0"
-color-convert@^1.9.0, color-convert@^1.9.1:
+color-convert@^1.9.0, color-convert@^1.9.3:
version "1.9.3"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8"
integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
@@ -2328,26 +2408,26 @@ color-name@^1.0.0, color-name@~1.1.4:
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.4.tgz#c2a09a87acbde69543de6f63fa3995c826c536a2"
integrity sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==
-color-string@^1.5.4:
- version "1.5.4"
- resolved "https://registry.yarnpkg.com/color-string/-/color-string-1.5.4.tgz#dd51cd25cfee953d138fe4002372cc3d0e504cb6"
- integrity sha512-57yF5yt8Xa3czSEW1jfQDE79Idk0+AkN/4KWad6tbdxUmAs3MvjxlWSWD4deYytcRfoZ9nhKyFl1kj5tBvidbw==
+color-string@^1.6.0:
+ version "1.6.0"
+ resolved "https://registry.yarnpkg.com/color-string/-/color-string-1.6.0.tgz#c3915f61fe267672cb7e1e064c9d692219f6c312"
+ integrity sha512-c/hGS+kRWJutUBEngKKmk4iH3sD59MBkoxVapS/0wgpCz2u7XsNloxknyvBhzwEs1IbV36D9PwqLPJ2DTu3vMA==
dependencies:
color-name "^1.0.0"
simple-swizzle "^0.2.2"
color@^3.0.0:
- version "3.1.3"
- resolved "https://registry.yarnpkg.com/color/-/color-3.1.3.tgz#ca67fb4e7b97d611dcde39eceed422067d91596e"
- integrity sha512-xgXAcTHa2HeFCGLE9Xs/R82hujGtu9Jd9x4NW3T34+OMs7VoPsjwzRczKHvTAHeJwWFwX5j15+MgAppE8ztObQ==
+ version "3.2.1"
+ resolved "https://registry.yarnpkg.com/color/-/color-3.2.1.tgz#3544dc198caf4490c3ecc9a790b54fe9ff45e164"
+ integrity sha512-aBl7dZI9ENN6fUGC7mWpMTPNHmWUSNan9tuWN6ahh5ZLNk9baLJOnSMlrQkHcrfFgz2/RigjUVAjdx36VcemKA==
dependencies:
- color-convert "^1.9.1"
- color-string "^1.5.4"
+ color-convert "^1.9.3"
+ color-string "^1.6.0"
-colorette@^1.2.1:
- version "1.2.1"
- resolved "https://registry.yarnpkg.com/colorette/-/colorette-1.2.1.tgz#4d0b921325c14faf92633086a536db6e89564b1b"
- integrity sha512-puCDz0CzydiSYOrnXpz/PKd69zRrribezjtE9yd4zvytoRc8+RY/KJPvtPFKZS3E3wP6neGyMe0vOTlHO5L3Pw==
+colorette@^1.2.1, colorette@^1.3.0:
+ version "1.4.0"
+ resolved "https://registry.yarnpkg.com/colorette/-/colorette-1.4.0.tgz#5190fbb87276259a86ad700bff2c6d6faa3fca40"
+ integrity sha512-Y2oEozpomLn7Q3HFP7dpww7AtMJplbM9lGZP6RDfHqmbeRjiwRg4n6VM6j4KLmRke85uWEI7JqF17f3pqdRA0g==
combined-stream@^1.0.6, combined-stream@~1.0.6:
version "1.0.8"
@@ -2473,9 +2553,9 @@ content-type@~1.0.4:
integrity sha512-hIP3EEPs8tB9AT1L+NUqtwOAps4mk2Zob89MWXMHjHWg9milF/j4osnnQLXBCBFBk/tvIG/tUc9mOUJiPBhPXA==
convert-source-map@^1.7.0:
- version "1.7.0"
- resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-1.7.0.tgz#17a2cb882d7f77d3490585e2ce6c524424a3a442"
- integrity sha512-4FJkXzKXEDB1snCFZlLP4gpC3JILicCpGbzG9f9G7tGqGCzETQ2hWPrcinA9oU4wtf2biUaEH5065UnMeR33oA==
+ version "1.8.0"
+ resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-1.8.0.tgz#f3373c32d21b4d780dd8004514684fb791ca4369"
+ integrity sha512-+OQdjP49zViI/6i7nIJpA8rAl4sV/JdPfU9nZs3VqOwGIgizICvuN2ru6fMd+4llL0tar18UYJXfZ/TWtmhUjA==
dependencies:
safe-buffer "~5.1.1"
@@ -2524,24 +2604,29 @@ copy-webpack-plugin@^5.0.2:
serialize-javascript "^4.0.0"
webpack-log "^2.0.0"
-core-js-compat@^3.6.5, core-js-compat@^3.8.0:
- version "3.8.3"
- resolved "https://registry.yarnpkg.com/core-js-compat/-/core-js-compat-3.8.3.tgz#9123fb6b9cad30f0651332dc77deba48ef9b0b3f"
- integrity sha512-1sCb0wBXnBIL16pfFG1Gkvei6UzvKyTNYpiC41yrdjEv0UoJoq9E/abTMzyYJ6JpTkAj15dLjbqifIzEBDVvog==
+core-js-compat@^3.14.0, core-js-compat@^3.16.0, core-js-compat@^3.6.5:
+ version "3.17.3"
+ resolved "https://registry.yarnpkg.com/core-js-compat/-/core-js-compat-3.17.3.tgz#b39c8e4dec71ecdc735c653ce5233466e561324e"
+ integrity sha512-+in61CKYs4hQERiADCJsdgewpdl/X0GhEX77pjKgbeibXviIt2oxEjTc8O2fqHX8mDdBrDvX8MYD/RYsBv4OiA==
dependencies:
- browserslist "^4.16.1"
+ browserslist "^4.17.0"
semver "7.0.0"
core-js@^3.6.4, core-js@^3.6.5:
- version "3.8.3"
- resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.8.3.tgz#c21906e1f14f3689f93abcc6e26883550dd92dd0"
- integrity sha512-KPYXeVZYemC2TkNEkX/01I+7yd+nX3KddKwZ1Ww7SKWdI2wQprSgLmrTddT8nw92AjEklTsPBoSdQBhbI1bQ6Q==
+ version "3.17.3"
+ resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.17.3.tgz#8e8bd20e91df9951e903cabe91f9af4a0895bc1e"
+ integrity sha512-lyvajs+wd8N1hXfzob1LdOCCHFU4bGMbqqmLn1Q4QlCpDqWPpGf+p0nj+LNrvDDG33j0hZXw2nsvvVpHysxyNw==
-core-util-is@1.0.2, core-util-is@~1.0.0:
+core-util-is@1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.2.tgz#b5fd54220aa2bc5ab57aab7140c940754503c1a7"
integrity sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=
+core-util-is@~1.0.0:
+ version "1.0.3"
+ resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.3.tgz#a6042d3634c2b27e9328f837b965fac83808db85"
+ integrity sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==
+
cosmiconfig@^5.0.0:
version "5.2.1"
resolved "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-5.2.1.tgz#040f726809c591e77a17c0a3626ca45b4f168b1a"
@@ -2666,7 +2751,7 @@ css-select-base-adapter@^0.1.1:
resolved "https://registry.yarnpkg.com/css-select-base-adapter/-/css-select-base-adapter-0.1.1.tgz#3b2ff4972cc362ab88561507a95408a1432135d7"
integrity sha512-jQVeeRG70QI08vSTwf1jHxp74JoZsr2XSgETae8/xC8ovSnL2WF87GTLO86Sbwdt2lK4Umg4HnnwMO4YF3Ce7w==
-css-select@^2.0.0, css-select@^2.0.2:
+css-select@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/css-select/-/css-select-2.1.0.tgz#6a34653356635934a81baca68d0255432105dbef"
integrity sha512-Dqk7LQKpwLoH3VovzZnkzegqNSuAziQyNZUcrdDM401iY+R5NkGBXGmtO05/yaXQziALuPogeG0b7UAgjnTJTQ==
@@ -2676,6 +2761,17 @@ css-select@^2.0.0, css-select@^2.0.2:
domutils "^1.7.0"
nth-check "^1.0.2"
+css-select@^4.1.3:
+ version "4.1.3"
+ resolved "https://registry.yarnpkg.com/css-select/-/css-select-4.1.3.tgz#a70440f70317f2669118ad74ff105e65849c7067"
+ integrity sha512-gT3wBNd9Nj49rAbmtFHj1cljIAOLYSX1nZ8CB7TBO3INYckygm5B7LISU/szY//YmdiSLbJvDLOx9VnMVpMBxA==
+ dependencies:
+ boolbase "^1.0.0"
+ css-what "^5.0.0"
+ domhandler "^4.2.0"
+ domutils "^2.6.0"
+ nth-check "^2.0.0"
+
css-tree@1.0.0-alpha.37:
version "1.0.0-alpha.37"
resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-1.0.0-alpha.37.tgz#98bebd62c4c1d9f960ec340cf9f7522e30709a22"
@@ -2685,9 +2781,9 @@ css-tree@1.0.0-alpha.37:
source-map "^0.6.1"
css-tree@^1.1.2:
- version "1.1.2"
- resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-1.1.2.tgz#9ae393b5dafd7dae8a622475caec78d3d8fbd7b5"
- integrity sha512-wCoWush5Aeo48GLhfHPbmvZs59Z+M7k5+B1xDnXbdWNcEF423DoFdqSWE0PM5aNk5nI5cp1q7ms36zGApY/sKQ==
+ version "1.1.3"
+ resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-1.1.3.tgz#eb4870fb6fd7707327ec95c2ff2ab09b5e8db91d"
+ integrity sha512-tRpdppF7TRazZrjJ6v3stzv93qxRcSsFmW6cX0Zm2NVKpxE1WV1HblnghVv9TreireHkqI/VDEsfolRF1p6y7Q==
dependencies:
mdn-data "2.0.14"
source-map "^0.6.1"
@@ -2697,6 +2793,11 @@ css-what@^3.2.1:
resolved "https://registry.yarnpkg.com/css-what/-/css-what-3.4.2.tgz#ea7026fcb01777edbde52124e21f327e7ae950e4"
integrity sha512-ACUm3L0/jiZTqfzRM3Hi9Q8eZqd6IK37mMWPLz9PJxkLWllYeRf+EHUSHYEtFop2Eqytaq1FizFVh7XfBnXCDQ==
+css-what@^5.0.0:
+ version "5.0.1"
+ resolved "https://registry.yarnpkg.com/css-what/-/css-what-5.0.1.tgz#3efa820131f4669a8ac2408f9c32e7c7de9f4cad"
+ integrity sha512-FYDTSHb/7KXsWICVsxdmiExPjCfRC4qRFBdVwv7Ax9hMnvMmEjP9RfxTEZ3qPZGmADDn2vAKSo9UcN1jKVYscg==
+
css@^2.0.0:
version "2.2.4"
resolved "https://registry.yarnpkg.com/css/-/css-2.2.4.tgz#c646755c73971f2bba6a601e2cf2fd71b1298929"
@@ -2712,10 +2813,10 @@ cssesc@^3.0.0:
resolved "https://registry.yarnpkg.com/cssesc/-/cssesc-3.0.0.tgz#37741919903b868565e1c09ea747445cd18983ee"
integrity sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==
-cssnano-preset-default@^4.0.7:
- version "4.0.7"
- resolved "https://registry.yarnpkg.com/cssnano-preset-default/-/cssnano-preset-default-4.0.7.tgz#51ec662ccfca0f88b396dcd9679cdb931be17f76"
- integrity sha512-x0YHHx2h6p0fCl1zY9L9roD7rnlltugGu7zXSKQx6k2rYw0Hi3IqxcoAGF7u9Q5w1nt7vK0ulxV8Lo+EvllGsA==
+cssnano-preset-default@^4.0.8:
+ version "4.0.8"
+ resolved "https://registry.yarnpkg.com/cssnano-preset-default/-/cssnano-preset-default-4.0.8.tgz#920622b1fc1e95a34e8838203f1397a504f2d3ff"
+ integrity sha512-LdAyHuq+VRyeVREFmuxUZR1TXjQm8QQU/ktoo/x7bz+SdOge1YKc5eMN6pRW7YWBmyq59CqYba1dJ5cUukEjLQ==
dependencies:
css-declaration-sorter "^4.0.1"
cssnano-util-raw-cache "^4.0.1"
@@ -2745,7 +2846,7 @@ cssnano-preset-default@^4.0.7:
postcss-ordered-values "^4.1.2"
postcss-reduce-initial "^4.0.3"
postcss-reduce-transforms "^4.0.2"
- postcss-svgo "^4.0.2"
+ postcss-svgo "^4.0.3"
postcss-unique-selectors "^4.0.1"
cssnano-util-get-arguments@^4.0.0:
@@ -2771,12 +2872,12 @@ cssnano-util-same-parent@^4.0.0:
integrity sha512-WcKx5OY+KoSIAxBW6UBBRay1U6vkYheCdjyVNDm85zt5K9mHoGOfsOsqIszfAqrQQFIIKgjh2+FDgIj/zsl21Q==
cssnano@^4.1.10:
- version "4.1.10"
- resolved "https://registry.yarnpkg.com/cssnano/-/cssnano-4.1.10.tgz#0ac41f0b13d13d465487e111b778d42da631b8b2"
- integrity sha512-5wny+F6H4/8RgNlaqab4ktc3e0/blKutmq8yNlBFXA//nSFFAqAngjNVRzUvCgYROULmZZUoosL/KSoZo5aUaQ==
+ version "4.1.11"
+ resolved "https://registry.yarnpkg.com/cssnano/-/cssnano-4.1.11.tgz#c7b5f5b81da269cb1fd982cb960c1200910c9a99"
+ integrity sha512-6gZm2htn7xIPJOHY824ERgj8cNPgPxyCSnkXc4v7YvNW+TdVfzgngHcEhy/8D11kUWRUMbke+tC+AUcUsnMz2g==
dependencies:
cosmiconfig "^5.0.0"
- cssnano-preset-default "^4.0.7"
+ cssnano-preset-default "^4.0.8"
is-resolvable "^1.0.0"
postcss "^7.0.0"
@@ -2826,9 +2927,9 @@ debug@^3.1.1, debug@^3.2.6:
ms "^2.1.1"
debug@^4.1.0, debug@^4.1.1:
- version "4.3.1"
- resolved "https://registry.yarnpkg.com/debug/-/debug-4.3.1.tgz#f0d229c505e0c6d8c49ac553d1b13dc183f6b2ee"
- integrity sha512-doEwdvm4PCeK4K3RQN2ZC2BYUBaxwLARCqZmMjtF8a51J2Rb0xpVloFRnCODwqjpwnAoao4pelN8l3RJdv3gRQ==
+ version "4.3.2"
+ resolved "https://registry.yarnpkg.com/debug/-/debug-4.3.2.tgz#f0a49c18ac8779e31d4a0c6029dfb76873c7428b"
+ integrity sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==
dependencies:
ms "2.1.2"
@@ -2938,11 +3039,6 @@ delayed-stream@~1.0.0:
resolved "https://registry.yarnpkg.com/delayed-stream/-/delayed-stream-1.0.0.tgz#df3ae199acadfb7d440aaae0b29e2272b24ec619"
integrity sha1-3zrhmayt+31ECqrgsp4icrJOxhk=
-delegate@^3.1.2:
- version "3.2.0"
- resolved "https://registry.yarnpkg.com/delegate/-/delegate-3.2.0.tgz#b66b71c3158522e8ab5744f720d8ca0c2af59166"
- integrity sha512-IofjkYBZaZivn0V8nnsMJGBr4jVLxHDheKSW88PyxS5QC4Vo9ZbZVvhzlSxY87fVq3STR6r+4cGepyHkcWOQSw==
-
delegates@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/delegates/-/delegates-1.0.0.tgz#84c6e159b81904fdca59a0ef44cd870d31250f9a"
@@ -2967,9 +3063,9 @@ destroy@~1.0.4:
integrity sha1-l4hXRCxEdJ5CBmE+N5RiBYJqvYA=
detect-node@^2.0.4:
- version "2.0.4"
- resolved "https://registry.yarnpkg.com/detect-node/-/detect-node-2.0.4.tgz#014ee8f8f669c5c58023da64b8179c083a28c46c"
- integrity sha512-ZIzRpLJrOj7jjP2miAtgqIfmzbxa4ZOr5jJc601zklsfEx9oTzmmj2nVpIPRpNlRTIh8lc1kyViIY7BWSGNmKw==
+ version "2.1.0"
+ resolved "https://registry.yarnpkg.com/detect-node/-/detect-node-2.1.0.tgz#c9c70775a49c3d03bc2c06d9a73be550f978f8b1"
+ integrity sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==
diacritics@^1.3.0:
version "1.3.0"
@@ -2998,9 +3094,9 @@ dns-equal@^1.0.0:
integrity sha1-s55/HabrCnW6nBcySzR1PEfgZU0=
dns-packet@^1.3.1:
- version "1.3.1"
- resolved "https://registry.yarnpkg.com/dns-packet/-/dns-packet-1.3.1.tgz#12aa426981075be500b910eedcd0b47dd7deda5a"
- integrity sha512-0UxfQkMhYAUaZI+xrNZOz/as5KgDU0M/fQ9b6SpkyLbk3GEswDi6PADJVaYJradtRVsRIlF1zLyOodbcTCDzUg==
+ version "1.3.4"
+ resolved "https://registry.yarnpkg.com/dns-packet/-/dns-packet-1.3.4.tgz#e3455065824a2507ba886c55a89963bb107dec6f"
+ integrity sha512-BQ6F4vycLXBvdrJZ6S3gZewt6rcrks9KBgM9vrhW+knGRqc8uEdT7fuCwloc7nny5xNoMJ17HGH0R/6fpo8ECA==
dependencies:
ip "^1.1.0"
safe-buffer "^5.0.1"
@@ -3025,7 +3121,7 @@ docsearch.js@^2.5.2:
to-factory "^1.0.0"
zepto "^1.2.0"
-dom-converter@^0.2:
+dom-converter@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/dom-converter/-/dom-converter-0.2.0.tgz#6721a9daee2e293682955b6afe416771627bb768"
integrity sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA==
@@ -3040,6 +3136,15 @@ dom-serializer@0:
domelementtype "^2.0.1"
entities "^2.0.0"
+dom-serializer@^1.0.1:
+ version "1.3.2"
+ resolved "https://registry.yarnpkg.com/dom-serializer/-/dom-serializer-1.3.2.tgz#6206437d32ceefaec7161803230c7a20bc1b4d91"
+ integrity sha512-5c54Bk5Dw4qAxNOI1pFEizPSjVsx5+bpJKmL2kPn8JhBUq2q09tTCa3mjijun2NfK78NMouDYNMBkOrPZiS+ig==
+ dependencies:
+ domelementtype "^2.0.1"
+ domhandler "^4.2.0"
+ entities "^2.0.0"
+
dom-walk@^0.1.0:
version "0.1.2"
resolved "https://registry.yarnpkg.com/dom-walk/-/dom-walk-0.1.2.tgz#0c548bef048f4d1f2a97249002236060daa3fd84"
@@ -3050,24 +3155,24 @@ domain-browser@^1.1.1:
resolved "https://registry.yarnpkg.com/domain-browser/-/domain-browser-1.2.0.tgz#3d31f50191a6749dd1375a7f522e823d42e54eda"
integrity sha512-jnjyiM6eRyZl2H+W8Q/zLMA481hzi0eszAaBUzIVnmYVDBbnLxVNnfu1HgEBvCbL+71FrxMl3E6lpKH7Ge3OXA==
-domelementtype@1, domelementtype@^1.3.1:
+domelementtype@1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-1.3.1.tgz#d048c44b37b0d10a7f2a3d5fee3f4333d790481f"
integrity sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==
-domelementtype@^2.0.1:
- version "2.1.0"
- resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-2.1.0.tgz#a851c080a6d1c3d94344aed151d99f669edf585e"
- integrity sha512-LsTgx/L5VpD+Q8lmsXSHW2WpA+eBlZ9HPf3erD1IoPF00/3JKHZ3BknUVA2QGDNu69ZNmyFmCWBSO45XjYKC5w==
+domelementtype@^2.0.1, domelementtype@^2.2.0:
+ version "2.2.0"
+ resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-2.2.0.tgz#9a0b6c2782ed6a1c7323d42267183df9bd8b1d57"
+ integrity sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==
-domhandler@^2.3.0:
- version "2.4.2"
- resolved "https://registry.yarnpkg.com/domhandler/-/domhandler-2.4.2.tgz#8805097e933d65e85546f726d60f5eb88b44f803"
- integrity sha512-JiK04h0Ht5u/80fdLMCEmV4zkNh2BcoMFBmZ/91WtYZ8qVXSKjiw7fXMgFPnHcSZgOo3XdinHvmnDUeMf5R4wA==
+domhandler@^4.0.0, domhandler@^4.2.0:
+ version "4.2.2"
+ resolved "https://registry.yarnpkg.com/domhandler/-/domhandler-4.2.2.tgz#e825d721d19a86b8c201a35264e226c678ee755f"
+ integrity sha512-PzE9aBMsdZO8TK4BnuJwH0QT41wgMbRzuZrHUcpYncEjmQazq8QEaBWgLG7ZyC/DAZKEgglpIA6j4Qn/HmxS3w==
dependencies:
- domelementtype "1"
+ domelementtype "^2.2.0"
-domutils@^1.5.1, domutils@^1.7.0:
+domutils@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/domutils/-/domutils-1.7.0.tgz#56ea341e834e06e6748af7a1cb25da67ea9f8c2a"
integrity sha512-Lgd2XcJ/NjEw+7tFvfKxOzCYKZsdct5lczQ2ZaQY8Djz7pfAD3Gbp8ySJWtreII/vDlMVmxwa6pHmdxIYgttDg==
@@ -3075,6 +3180,15 @@ domutils@^1.5.1, domutils@^1.7.0:
dom-serializer "0"
domelementtype "1"
+domutils@^2.5.2, domutils@^2.6.0:
+ version "2.8.0"
+ resolved "https://registry.yarnpkg.com/domutils/-/domutils-2.8.0.tgz#4437def5db6e2d1f5d6ee859bd95ca7d02048135"
+ integrity sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==
+ dependencies:
+ dom-serializer "^1.0.1"
+ domelementtype "^2.2.0"
+ domhandler "^4.2.0"
+
dot-prop@^5.2.0:
version "5.3.0"
resolved "https://registry.yarnpkg.com/dot-prop/-/dot-prop-5.3.0.tgz#90ccce708cd9cd82cc4dc8c3ddd9abdd55b20e88"
@@ -3110,10 +3224,10 @@ ee-first@1.1.1:
resolved "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz#590c61156b0ae2f4f0255732a158b266bc56b21d"
integrity sha1-WQxhFWsK4vTwJVcyoViyZrxWsh0=
-electron-to-chromium@^1.3.649:
- version "1.3.661"
- resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.661.tgz#8603ec971b3e3b3d83389ac2bb64b9b07d7bb40a"
- integrity sha512-INNzKoL9ceOpPCpF5J+Fp9AOHY1RegwKViohAyTzV3XbkuRUx04r4v8edsDbevsog8UuL0GvD/Qerr2HwVTlSA==
+electron-to-chromium@^1.3.830:
+ version "1.3.840"
+ resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.840.tgz#3f2a1df97015d9b1db5d86a4c6bd4cdb920adcbb"
+ integrity sha512-yRoUmTLDJnkIJx23xLY7GbSvnmDCq++NSuxHDQ0jiyDJ9YZBUGJcrdUqm+ZwZFzMbCciVzfem2N2AWiHJcWlbw==
elliptic@^6.5.3:
version "6.5.4"
@@ -3169,16 +3283,16 @@ enhanced-resolve@^4.5.0:
memory-fs "^0.5.0"
tapable "^1.0.0"
-entities@^1.1.1, entities@~1.1.1:
- version "1.1.2"
- resolved "https://registry.yarnpkg.com/entities/-/entities-1.1.2.tgz#bdfa735299664dfafd34529ed4f8522a275fea56"
- integrity sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==
-
entities@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/entities/-/entities-2.2.0.tgz#098dc90ebb83d8dffa089d55256b351d34c4da55"
integrity sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==
+entities@~1.1.1:
+ version "1.1.2"
+ resolved "https://registry.yarnpkg.com/entities/-/entities-1.1.2.tgz#bdfa735299664dfafd34529ed4f8522a275fea56"
+ integrity sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==
+
envify@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/envify/-/envify-4.1.0.tgz#f39ad3db9d6801b4e6b478b61028d3f0b6819f7e"
@@ -3188,9 +3302,9 @@ envify@^4.0.0:
through "~2.3.4"
envinfo@^7.2.0:
- version "7.7.4"
- resolved "https://registry.yarnpkg.com/envinfo/-/envinfo-7.7.4.tgz#c6311cdd38a0e86808c1c9343f667e4267c4a320"
- integrity sha512-TQXTYFVVwwluWSFis6K2XKxgrD22jEv0FTuLCQI+OjH7rn93+iY0fSSFM5lrSxFY+H1+B0/cvvlamr3UsBivdQ==
+ version "7.8.1"
+ resolved "https://registry.yarnpkg.com/envinfo/-/envinfo-7.8.1.tgz#06377e3e5f4d379fea7ac592d5ad8927e0c4d475"
+ integrity sha512-/o+BXHmB7ocbHEAs6F2EnG0ogybVVUdkRunTT2glZU9XAaGmhqskrvKwqXuDfNjEO0LZKWdejEEpnq8aM0tOaw==
errno@^0.1.3, errno@~0.1.7:
version "0.1.8"
@@ -3206,42 +3320,29 @@ error-ex@^1.2.0, error-ex@^1.3.1:
dependencies:
is-arrayish "^0.2.1"
-es-abstract@^1.17.2:
- version "1.17.7"
- resolved "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.17.7.tgz#a4de61b2f66989fc7421676c1cb9787573ace54c"
- integrity sha512-VBl/gnfcJ7OercKA9MVaegWsBHFjV492syMudcnQZvt/Dw8ezpcOHYZXa/J96O8vx+g4x65YKhxOwDUh63aS5g==
- dependencies:
- es-to-primitive "^1.2.1"
- function-bind "^1.1.1"
- has "^1.0.3"
- has-symbols "^1.0.1"
- is-callable "^1.2.2"
- is-regex "^1.1.1"
- object-inspect "^1.8.0"
- object-keys "^1.1.1"
- object.assign "^4.1.1"
- string.prototype.trimend "^1.0.1"
- string.prototype.trimstart "^1.0.1"
-
-es-abstract@^1.18.0-next.1:
- version "1.18.0-next.2"
- resolved "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.18.0-next.2.tgz#088101a55f0541f595e7e057199e27ddc8f3a5c2"
- integrity sha512-Ih4ZMFHEtZupnUh6497zEL4y2+w8+1ljnCyaTa+adcoafI1GOvMwFlDjBLfWR7y9VLfrjRJe9ocuHY1PSR9jjw==
+es-abstract@^1.17.2, es-abstract@^1.18.0-next.2, es-abstract@^1.18.2:
+ version "1.18.6"
+ resolved "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.18.6.tgz#2c44e3ea7a6255039164d26559777a6d978cb456"
+ integrity sha512-kAeIT4cku5eNLNuUKhlmtuk1/TRZvQoYccn6TO0cSVdf1kzB0T7+dYuVK9MWM7l+/53W2Q8M7N2c6MQvhXFcUQ==
dependencies:
call-bind "^1.0.2"
es-to-primitive "^1.2.1"
function-bind "^1.1.1"
- get-intrinsic "^1.0.2"
+ get-intrinsic "^1.1.1"
+ get-symbol-description "^1.0.0"
has "^1.0.3"
- has-symbols "^1.0.1"
- is-callable "^1.2.2"
+ has-symbols "^1.0.2"
+ internal-slot "^1.0.3"
+ is-callable "^1.2.4"
is-negative-zero "^2.0.1"
- is-regex "^1.1.1"
- object-inspect "^1.9.0"
+ is-regex "^1.1.4"
+ is-string "^1.0.7"
+ object-inspect "^1.11.0"
object-keys "^1.1.1"
object.assign "^4.1.2"
- string.prototype.trimend "^1.0.3"
- string.prototype.trimstart "^1.0.3"
+ string.prototype.trimend "^1.0.4"
+ string.prototype.trimstart "^1.0.4"
+ unbox-primitive "^1.0.1"
es-to-primitive@^1.2.1:
version "1.2.1"
@@ -3333,14 +3434,14 @@ events@^1.1.0:
integrity sha1-nr23Y1rQmccNzEwqH1AEKI6L2SQ=
events@^3.0.0:
- version "3.2.0"
- resolved "https://registry.yarnpkg.com/events/-/events-3.2.0.tgz#93b87c18f8efcd4202a461aec4dfc0556b639379"
- integrity sha512-/46HWwbfCX2xTawVfkKLGxMifJYQBWMwY1mjywRtb4c9x8l5NP3KoJtnIOiL1hfdRkIuYhETxQlo62IF8tcnlg==
+ version "3.3.0"
+ resolved "https://registry.yarnpkg.com/events/-/events-3.3.0.tgz#31a95ad0a924e2d2c419a813aeb2c4e878ea7400"
+ integrity sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==
eventsource@^1.0.7:
- version "1.0.7"
- resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-1.0.7.tgz#8fbc72c93fcd34088090bc0a4e64f4b5cee6d8d0"
- integrity sha512-4Ln17+vVT0k8aWq+t/bF5arcS3EpT9gYtW66EPacdj/mAFevznsnyoHLPy2BA8gbIQeIHoPsvwmfBftfcG//BQ==
+ version "1.1.0"
+ resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-1.1.0.tgz#00e8ca7c92109e94b0ddf32dac677d841028cfaf"
+ integrity sha512-VSJjT5oCNrFvCS6igjzPAt5hBzQ2qPBFIbJ03zLI9SE0mxwZpMw6BfJrbFHm1a141AavMEB8JHmBhWAd66PfCg==
dependencies:
original "^1.0.0"
@@ -3481,9 +3582,9 @@ fast-json-stable-stringify@^2.0.0:
integrity sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==
faye-websocket@^0.11.3:
- version "0.11.3"
- resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.3.tgz#5c0e9a8968e8912c286639fde977a8b209f2508e"
- integrity sha512-D2y4bovYpzziGgbHYtGCMjlJM36vAl/y+xUyn1C+FVx8szd1E+86KwVw6XvYSzOP8iMpm1X0I4xJD+QtUb36OA==
+ version "0.11.4"
+ resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.4.tgz#7f0d9275cfdd86a1c963dc8b65fcc451edcbb1da"
+ integrity sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g==
dependencies:
websocket-driver ">=0.5.1"
@@ -3552,9 +3653,9 @@ find-cache-dir@^2.1.0:
pkg-dir "^3.0.0"
find-cache-dir@^3.3.1:
- version "3.3.1"
- resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-3.3.1.tgz#89b33fad4a4670daa94f855f7fbe31d6d84fe880"
- integrity sha512-t2GDMt3oGC/v+BMwzmllWDuJF/xcDtE5j/fCGbqDD7OLuJkj0cfh1YSA5VKPvwMeLFLNDBkwOKZ2X85jGLVftQ==
+ version "3.3.2"
+ resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-3.3.2.tgz#b30c5b6eff0730731aea9bbd9dbecbd80256d64b"
+ integrity sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig==
dependencies:
commondir "^1.0.1"
make-dir "^3.0.2"
@@ -3592,9 +3693,9 @@ flush-write-stream@^1.0.0:
readable-stream "^2.3.6"
follow-redirects@^1.0.0:
- version "1.13.2"
- resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.13.2.tgz#dd73c8effc12728ba5cf4259d760ea5fb83e3147"
- integrity sha512-6mPTgLxYm3r6Bkkg0vNM0HTjfGrOEtsfbhagQvbxDEsEkpNhw582upBaoRZylzen6krEmxXJgt9Ju6HiI4O7BA==
+ version "1.14.4"
+ resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.14.4.tgz#838fdf48a8bbdd79e52ee51fb1c94e3ed98b9379"
+ integrity sha512-zwGkiSXC1MUJG/qmeIFH2HBJx9u0V46QGUe3YR1fXG8bXQxq7fLj0RjLZQ5nubr9qNJUZrH+xUcwXEoXNpfS+g==
for-in@^1.0.2:
version "1.0.2"
@@ -3620,10 +3721,10 @@ form-data@~2.3.2:
combined-stream "^1.0.6"
mime-types "^2.1.12"
-forwarded@~0.1.2:
- version "0.1.2"
- resolved "https://registry.yarnpkg.com/forwarded/-/forwarded-0.1.2.tgz#98c23dab1175657b8c0573e8ceccd91b0ff18c84"
- integrity sha1-mMI9qxF1ZXuMBXPozszZGw/xjIQ=
+forwarded@0.2.0:
+ version "0.2.0"
+ resolved "https://registry.yarnpkg.com/forwarded/-/forwarded-0.2.0.tgz#2269936428aad4c15c7ebe9779a84bf0b2a81811"
+ integrity sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==
fragment-cache@^0.2.1:
version "0.2.1"
@@ -3677,7 +3778,7 @@ fsevents@^1.2.7:
bindings "^1.5.0"
nan "^2.12.1"
-fsevents@~2.3.1:
+fsevents@~2.3.2:
version "2.3.2"
resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.3.2.tgz#8a526f78b8fdf4623b709e0b975c52c24c02fd1a"
integrity sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==
@@ -3718,7 +3819,7 @@ gaze@^1.0.0:
dependencies:
globule "^1.0.0"
-gensync@^1.0.0-beta.1:
+gensync@^1.0.0-beta.2:
version "1.0.0-beta.2"
resolved "https://registry.yarnpkg.com/gensync/-/gensync-1.0.0-beta.2.tgz#32a6ee76c3d7f52d46b2b1ae5d93fea8580a25e0"
integrity sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==
@@ -3728,7 +3829,7 @@ get-caller-file@^2.0.1:
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e"
integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
-get-intrinsic@^1.0.2:
+get-intrinsic@^1.0.2, get-intrinsic@^1.1.0, get-intrinsic@^1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/get-intrinsic/-/get-intrinsic-1.1.1.tgz#15f59f376f855c446963948f0d24cd3637b4abc6"
integrity sha512-kWZrnVM42QCiEA2Ig1bG8zjoIMOgxWwYCEeNdwY6Tv/cOSeGpcoX4pXHfKUxNKVoArnrEr2e9srnAxxGIraS9Q==
@@ -3756,6 +3857,14 @@ get-stream@^5.1.0:
dependencies:
pump "^3.0.0"
+get-symbol-description@^1.0.0:
+ version "1.0.0"
+ resolved "https://registry.yarnpkg.com/get-symbol-description/-/get-symbol-description-1.0.0.tgz#7fdb81c900101fbd564dd5f1a30af5aadc1e58d6"
+ integrity sha512-2EmdH1YvIQiZpltCNgkuiUnyukzxM/R6NDJX31Ke3BG1Nq5b0S2PhX59UKi9vZpPDQVdqn+1IcaAwnzTT5vCjw==
+ dependencies:
+ call-bind "^1.0.2"
+ get-intrinsic "^1.1.1"
+
get-value@^2.0.3, get-value@^2.0.6:
version "2.0.6"
resolved "https://registry.yarnpkg.com/get-value/-/get-value-2.0.6.tgz#dc15ca1c672387ca76bd37ac0a395ba2042a2c28"
@@ -3776,10 +3885,10 @@ glob-parent@^3.1.0:
is-glob "^3.1.0"
path-dirname "^1.0.0"
-glob-parent@~5.1.0:
- version "5.1.1"
- resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-5.1.1.tgz#b6c1ef417c4e5663ea498f1c45afac6916bbc229"
- integrity sha512-FnI+VGOpnlGHWZxthPGR+QhR78fuiK0sNLkHQv+bL9fQi57lNNdquIbna/WrfROrolq8GK5Ek6BiMwqL/voRYQ==
+glob-parent@~5.1.2:
+ version "5.1.2"
+ resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-5.1.2.tgz#869832c58034fe68a4093c17dc15e8340d8401c4"
+ integrity sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==
dependencies:
is-glob "^4.0.1"
@@ -3789,9 +3898,9 @@ glob-to-regexp@^0.3.0:
integrity sha1-jFoUlNIGbFcMw7/kSWF1rMTVAqs=
glob@^7.0.0, glob@^7.0.3, glob@^7.1.2, glob@^7.1.3, glob@^7.1.4, glob@^7.1.6, glob@~7.1.1:
- version "7.1.6"
- resolved "https://registry.yarnpkg.com/glob/-/glob-7.1.6.tgz#141f33b81a7c2492e125594307480c46679278a6"
- integrity sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==
+ version "7.1.7"
+ resolved "https://registry.yarnpkg.com/glob/-/glob-7.1.7.tgz#3b193e9233f01d42d0b3f78294bbeeb418f94a90"
+ integrity sha512-OvD9ENzPLbegENnYP5UUfJIirTg4+XwMWGaQfQTY0JenxNvvIKP3U3/tAQSPIu/lHxXYSZmpXlUHeqAIdKzBLQ==
dependencies:
fs.realpath "^1.0.0"
inflight "^1.0.4"
@@ -3858,21 +3967,14 @@ globby@^9.1.0, globby@^9.2.0:
slash "^2.0.0"
globule@^1.0.0:
- version "1.3.2"
- resolved "https://registry.yarnpkg.com/globule/-/globule-1.3.2.tgz#d8bdd9e9e4eef8f96e245999a5dee7eb5d8529c4"
- integrity sha512-7IDTQTIu2xzXkT+6mlluidnWo+BypnbSoEVVQCGfzqnl5Ik8d3e1d4wycb8Rj9tWW+Z39uPWsdlquqiqPCd/pA==
+ version "1.3.3"
+ resolved "https://registry.yarnpkg.com/globule/-/globule-1.3.3.tgz#811919eeac1ab7344e905f2e3be80a13447973c2"
+ integrity sha512-mb1aYtDbIjTu4ShMB85m3UzjX9BVKe9WCzsnfMSZk+K5GpIbBOexgg4PPCt5eHDEG5/ZQAUX2Kct02zfiPLsKg==
dependencies:
glob "~7.1.1"
lodash "~4.17.10"
minimatch "~3.0.2"
-good-listener@^1.2.2:
- version "1.2.2"
- resolved "https://registry.yarnpkg.com/good-listener/-/good-listener-1.2.2.tgz#d53b30cdf9313dffb7dc9a0d477096aa6d145c50"
- integrity sha1-1TswzfkxPf+33JoNR3CWqm0UXFA=
- dependencies:
- delegate "^3.1.2"
-
got@^9.6.0:
version "9.6.0"
resolved "https://registry.yarnpkg.com/got/-/got-9.6.0.tgz#edf45e7d67f99545705de1f7bbeeeb121765ed85"
@@ -3891,16 +3993,16 @@ got@^9.6.0:
url-parse-lax "^3.0.0"
graceful-fs@^4.1.11, graceful-fs@^4.1.15, graceful-fs@^4.1.2, graceful-fs@^4.1.6:
- version "4.2.6"
- resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.6.tgz#ff040b2b0853b23c3d31027523706f1885d76bee"
- integrity sha512-nTnJ528pbqxYanhpDYsi4Rd8MAeaBA67+RZ10CM1m3bTAVFEDcd5AuA4a6W5YkGZ1iNXHzZz8T6TBKLeBuNriQ==
+ version "4.2.8"
+ resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.8.tgz#e412b8d33f5e006593cbd3cee6df9f2cebbe802a"
+ integrity sha512-qkIilPUYcNhJpd33n0GBXTB1MMPp14TxEsEs0pTrsSVucApsYzW5V+Q8Qxhik6KU3evy+qkAAowTByymK0avdg==
gray-matter@^4.0.1:
- version "4.0.2"
- resolved "https://registry.yarnpkg.com/gray-matter/-/gray-matter-4.0.2.tgz#9aa379e3acaf421193fce7d2a28cebd4518ac454"
- integrity sha512-7hB/+LxrOjq/dd8APlK0r24uL/67w7SkYnfwhNFwg/VDIGWGmduTDYf3WNstLW2fbbmRwrDGCVSJ2isuf2+4Hw==
+ version "4.0.3"
+ resolved "https://registry.yarnpkg.com/gray-matter/-/gray-matter-4.0.3.tgz#e893c064825de73ea1f5f7d88c7a9f7274288798"
+ integrity sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==
dependencies:
- js-yaml "^3.11.0"
+ js-yaml "^3.13.1"
kind-of "^6.0.2"
section-matter "^1.0.0"
strip-bom-string "^1.0.0"
@@ -3930,6 +4032,11 @@ has-ansi@^2.0.0:
dependencies:
ansi-regex "^2.0.0"
+has-bigints@^1.0.1:
+ version "1.0.1"
+ resolved "https://registry.yarnpkg.com/has-bigints/-/has-bigints-1.0.1.tgz#64fe6acb020673e3b78db035a5af69aa9d07b113"
+ integrity sha512-LSBS2LjbNBTf6287JEbEzvJgftkF5qFkmCo9hDRpAzKhUOlJ+hx8dd4USs00SgsUNwc4617J9ki5YtEClM2ffA==
+
has-flag@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd"
@@ -3940,10 +4047,17 @@ has-flag@^4.0.0:
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-4.0.0.tgz#944771fd9c81c81265c4d6941860da06bb59479b"
integrity sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==
-has-symbols@^1.0.1:
- version "1.0.1"
- resolved "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.1.tgz#9f5214758a44196c406d9bd76cebf81ec2dd31e8"
- integrity sha512-PLcsoqu++dmEIZB+6totNFKq/7Do+Z0u4oT0zKOJNl3lYK6vGwwu2hjHs+68OEZbTjiUE9bgOABXbP/GvrS0Kg==
+has-symbols@^1.0.1, has-symbols@^1.0.2:
+ version "1.0.2"
+ resolved "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.2.tgz#165d3070c00309752a1236a479331e3ac56f1423"
+ integrity sha512-chXa79rL/UC2KlX17jo3vRGz0azaWEx5tGqZg5pO3NUyEJVB17dMruQlzCCOfUvElghKcm5194+BCRvi2Rv/Gw==
+
+has-tostringtag@^1.0.0:
+ version "1.0.0"
+ resolved "https://registry.yarnpkg.com/has-tostringtag/-/has-tostringtag-1.0.0.tgz#7e133818a7d394734f941e73c3d3f9291e658b25"
+ integrity sha512-kFjcSNhnlGV1kyoGk7OXKSawH5JOb/LzUc5w9B02hOTO0dfFRjbHQKvg1d6cf3HbeUmtU9VbbV3qzZ2Teh97WQ==
+ dependencies:
+ has-symbols "^1.0.2"
has-unicode@^2.0.0:
version "2.0.1"
@@ -4043,9 +4157,9 @@ hogan.js@^3.0.2:
nopt "1.0.10"
hosted-git-info@^2.1.4:
- version "2.8.8"
- resolved "https://registry.yarnpkg.com/hosted-git-info/-/hosted-git-info-2.8.8.tgz#7539bd4bc1e0e0a895815a2e0262420b12858488"
- integrity sha512-f/wzC2QaWBs7t9IYqB4T3sR1xviIViXJRJTWBlx2Gf3g0Xi5vI7Yy4koXQ1c9OYDGHN9sBy1DQ2AB8fqZBWhUg==
+ version "2.8.9"
+ resolved "https://registry.yarnpkg.com/hosted-git-info/-/hosted-git-info-2.8.9.tgz#dffc0bf9a21c02209090f2aa69429e1414daf3f9"
+ integrity sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==
hpack.js@^2.1.6:
version "2.1.6"
@@ -4067,11 +4181,6 @@ hsla-regex@^1.0.0:
resolved "https://registry.yarnpkg.com/hsla-regex/-/hsla-regex-1.0.0.tgz#c1ce7a3168c8c6614033a4b5f7877f3b225f9c38"
integrity sha1-wc56MWjIxmFAM6S194d/OyJfnDg=
-html-comment-regex@^1.1.0:
- version "1.1.2"
- resolved "https://registry.yarnpkg.com/html-comment-regex/-/html-comment-regex-1.1.2.tgz#97d4688aeb5c81886a364faa0cad1dda14d433a7"
- integrity sha512-P+M65QY2JQ5Y0G9KKdlDpo0zK+/OHptU5AaBwUfAIDJZk1MYf32Frm84EcOytfJE0t5JvkAnKlmjsXDnWzCJmQ==
-
html-entities@^1.3.1:
version "1.4.0"
resolved "https://registry.yarnpkg.com/html-entities/-/html-entities-1.4.0.tgz#cfbd1b01d2afaf9adca1b10ae7dffab98c71d2dc"
@@ -4100,17 +4209,15 @@ html-tags@^3.1.0:
resolved "https://registry.yarnpkg.com/html-tags/-/html-tags-3.1.0.tgz#7b5e6f7e665e9fb41f30007ed9e0d41e97fb2140"
integrity sha512-1qYz89hW3lFDEazhjW0yVAV87lw8lVkrJocr72XmBkMKsoSVJCQx3W8BXsC7hO2qAt8BoVjYjtAcZ9perqGnNg==
-htmlparser2@^3.10.1:
- version "3.10.1"
- resolved "https://registry.yarnpkg.com/htmlparser2/-/htmlparser2-3.10.1.tgz#bd679dc3f59897b6a34bb10749c855bb53a9392f"
- integrity sha512-IgieNijUMbkDovyoKObU1DUhm1iwNYE/fuifEoEHfd1oZKZDaONBSkal7Y01shxsM49R4XaMdGez3WnF9UfiCQ==
+htmlparser2@^6.1.0:
+ version "6.1.0"
+ resolved "https://registry.yarnpkg.com/htmlparser2/-/htmlparser2-6.1.0.tgz#c4d762b6c3371a05dbe65e94ae43a9f845fb8fb7"
+ integrity sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==
dependencies:
- domelementtype "^1.3.1"
- domhandler "^2.3.0"
- domutils "^1.5.1"
- entities "^1.1.1"
- inherits "^2.0.1"
- readable-stream "^3.1.1"
+ domelementtype "^2.0.1"
+ domhandler "^4.0.0"
+ domutils "^2.5.2"
+ entities "^2.0.0"
http-cache-semantics@^4.0.0:
version "4.1.0"
@@ -4339,6 +4446,15 @@ internal-ip@^4.3.0:
default-gateway "^4.2.0"
ipaddr.js "^1.9.0"
+internal-slot@^1.0.3:
+ version "1.0.3"
+ resolved "https://registry.yarnpkg.com/internal-slot/-/internal-slot-1.0.3.tgz#7347e307deeea2faac2ac6205d4bc7d34967f59c"
+ integrity sha512-O0DB1JC/sPyZl7cIo78n5dR7eUSwwpYPiXRhTzNxZVAMUuB8vlnRFyLxdrVToks6XPLVnFfbzaVd5WLjhgg+vA==
+ dependencies:
+ get-intrinsic "^1.1.0"
+ has "^1.0.3"
+ side-channel "^1.0.4"
+
ip-regex@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/ip-regex/-/ip-regex-2.1.0.tgz#fa78bf5d2e6913c911ce9f819ee5146bb6d844e9"
@@ -4379,11 +4495,12 @@ is-accessor-descriptor@^1.0.0:
kind-of "^6.0.0"
is-arguments@^1.0.4:
- version "1.1.0"
- resolved "https://registry.yarnpkg.com/is-arguments/-/is-arguments-1.1.0.tgz#62353031dfbee07ceb34656a6bde59efecae8dd9"
- integrity sha512-1Ij4lOMPl/xB5kBDn7I+b2ttPMKa8szhEIrXDuXQD/oe3HJLTLhqhgGspwgyGd6MOywBUqVvYicF72lkgDnIHg==
+ version "1.1.1"
+ resolved "https://registry.yarnpkg.com/is-arguments/-/is-arguments-1.1.1.tgz#15b3f88fda01f2a97fec84ca761a560f123efa9b"
+ integrity sha512-8Q7EARjzEnKpt/PCD7e1cgUS0a6X8u5tdSiMqXhojOdoV9TsMsiO+9VLC5vAmO8N7/GmXn7yjR8qnA6bVAEzfA==
dependencies:
- call-bind "^1.0.0"
+ call-bind "^1.0.2"
+ has-tostringtag "^1.0.0"
is-arrayish@^0.2.1:
version "0.2.1"
@@ -4395,6 +4512,13 @@ is-arrayish@^0.3.1:
resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.3.2.tgz#4574a2ae56f7ab206896fb431eaeed066fdf8f03"
integrity sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==
+is-bigint@^1.0.1:
+ version "1.0.4"
+ resolved "https://registry.yarnpkg.com/is-bigint/-/is-bigint-1.0.4.tgz#08147a1875bc2b32005d41ccd8291dffc6691df3"
+ integrity sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==
+ dependencies:
+ has-bigints "^1.0.1"
+
is-binary-path@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-1.0.1.tgz#75f16642b480f187a711c814161fd3a4a7655898"
@@ -4409,15 +4533,23 @@ is-binary-path@~2.1.0:
dependencies:
binary-extensions "^2.0.0"
+is-boolean-object@^1.1.0:
+ version "1.1.2"
+ resolved "https://registry.yarnpkg.com/is-boolean-object/-/is-boolean-object-1.1.2.tgz#5c6dc200246dd9321ae4b885a114bb1f75f63719"
+ integrity sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==
+ dependencies:
+ call-bind "^1.0.2"
+ has-tostringtag "^1.0.0"
+
is-buffer@^1.1.5:
version "1.1.6"
resolved "https://registry.yarnpkg.com/is-buffer/-/is-buffer-1.1.6.tgz#efaa2ea9daa0d7ab2ea13a97b2b8ad51fefbe8be"
integrity sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==
-is-callable@^1.1.4, is-callable@^1.2.2:
- version "1.2.3"
- resolved "https://registry.yarnpkg.com/is-callable/-/is-callable-1.2.3.tgz#8b1e0500b73a1d76c70487636f368e519de8db8e"
- integrity sha512-J1DcMe8UYTBSrKezuIUTUwjXsho29693unXM2YhJUTR2txK/eG47bvNa/wipPFmZFgr/N6f1GA66dv0mEyTIyQ==
+is-callable@^1.1.4, is-callable@^1.2.4:
+ version "1.2.4"
+ resolved "https://registry.yarnpkg.com/is-callable/-/is-callable-1.2.4.tgz#47301d58dd0259407865547853df6d61fe471945"
+ integrity sha512-nsuwtxZfMX67Oryl9LCQ+upnC0Z0BgpwntpS89m1H/TLF0zNfzfLMV/9Wa/6MZsj0acpEjAO0KF1xT6ZdLl95w==
is-ci@^2.0.0:
version "2.0.0"
@@ -4438,10 +4570,10 @@ is-color-stop@^1.0.0:
rgb-regex "^1.0.1"
rgba-regex "^1.0.0"
-is-core-module@^2.1.0:
- version "2.2.0"
- resolved "https://registry.yarnpkg.com/is-core-module/-/is-core-module-2.2.0.tgz#97037ef3d52224d85163f5597b2b63d9afed981a"
- integrity sha512-XRAfAdyyY5F5cOXn7hYQDqh2Xmii+DEfIcQGxK/uNwMHhIkPWO0g8msXcbzLe+MpGoR951MlqM/2iIlU4vKDdQ==
+is-core-module@^2.2.0:
+ version "2.6.0"
+ resolved "https://registry.yarnpkg.com/is-core-module/-/is-core-module-2.6.0.tgz#d7553b2526fe59b92ba3e40c8df757ec8a709e19"
+ integrity sha512-wShG8vs60jKfPWpF2KZRaAtvt3a20OAn7+IJ6hLPECpSABLcKtFKTTI4ZtH5QcBruBHlq+WsdHWyz0BCZW7svQ==
dependencies:
has "^1.0.3"
@@ -4460,9 +4592,11 @@ is-data-descriptor@^1.0.0:
kind-of "^6.0.0"
is-date-object@^1.0.1:
- version "1.0.2"
- resolved "https://registry.yarnpkg.com/is-date-object/-/is-date-object-1.0.2.tgz#bda736f2cd8fd06d32844e7743bfa7494c3bfd7e"
- integrity sha512-USlDT524woQ08aoZFzh3/Z6ch9Y/EWXEHQ/AaRN0SkKq4t2Jw2R2339tSXmwuVoY7LLlBCbOIlx2myP/L5zk0g==
+ version "1.0.5"
+ resolved "https://registry.yarnpkg.com/is-date-object/-/is-date-object-1.0.5.tgz#0841d5536e724c25597bf6ea62e1bd38298df31f"
+ integrity sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==
+ dependencies:
+ has-tostringtag "^1.0.0"
is-descriptor@^0.1.0:
version "0.1.6"
@@ -4558,6 +4692,13 @@ is-npm@^4.0.0:
resolved "https://registry.yarnpkg.com/is-npm/-/is-npm-4.0.0.tgz#c90dd8380696df87a7a6d823c20d0b12bbe3c84d"
integrity sha512-96ECIfh9xtDDlPylNPXhzjsykHsMJZ18ASpaWzQyBr4YRTcVjUvzaHayDAES2oU/3KpljhHUjtSRNiDwi0F0ig==
+is-number-object@^1.0.4:
+ version "1.0.6"
+ resolved "https://registry.yarnpkg.com/is-number-object/-/is-number-object-1.0.6.tgz#6a7aaf838c7f0686a50b4553f7e54a96494e89f0"
+ integrity sha512-bEVOqiRcvo3zO1+G2lVMy+gkkEm9Yh7cDMRusKKu5ZJKPUYSJwICTKZrNKHA2EbSP0Tu0+6B/emsYNHZyn6K8g==
+ dependencies:
+ has-tostringtag "^1.0.0"
+
is-number@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-3.0.0.tgz#24fd6201a4782cf50561c810276afc7d12d71195"
@@ -4595,9 +4736,9 @@ is-path-inside@^2.1.0:
path-is-inside "^1.0.2"
is-path-inside@^3.0.1:
- version "3.0.2"
- resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-3.0.2.tgz#f5220fc82a3e233757291dddc9c5877f2a1f3017"
- integrity sha512-/2UGPSgmtqwo1ktx8NDHjuPwZWmHhO+gj0f93EkhLB5RgW9RZevWYYlIkS6zePc6U2WpOdQYIwHe9YC4DWEBVg==
+ version "3.0.3"
+ resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-3.0.3.tgz#d231362e53a07ff2b0e0ea7fed049161ffd16283"
+ integrity sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==
is-plain-obj@^1.0.0:
version "1.1.0"
@@ -4611,13 +4752,13 @@ is-plain-object@^2.0.3, is-plain-object@^2.0.4:
dependencies:
isobject "^3.0.1"
-is-regex@^1.0.4, is-regex@^1.1.1:
- version "1.1.2"
- resolved "https://registry.yarnpkg.com/is-regex/-/is-regex-1.1.2.tgz#81c8ebde4db142f2cf1c53fc86d6a45788266251"
- integrity sha512-axvdhb5pdhEVThqJzYXwMlVuZwC+FF2DpcOhTS+y/8jVq4trxyPgfcwIxIKiyeuLlSQYKkmUaPQJ8ZE4yNKXDg==
+is-regex@^1.0.4, is-regex@^1.1.4:
+ version "1.1.4"
+ resolved "https://registry.yarnpkg.com/is-regex/-/is-regex-1.1.4.tgz#eef5663cd59fa4c0ae339505323df6854bb15958"
+ integrity sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==
dependencies:
call-bind "^1.0.2"
- has-symbols "^1.0.1"
+ has-tostringtag "^1.0.0"
is-resolvable@^1.0.0:
version "1.1.0"
@@ -4629,19 +4770,19 @@ is-stream@^1.1.0:
resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-1.1.0.tgz#12d4a3dd4e68e0b79ceb8dbc84173ae80d91ca44"
integrity sha1-EtSj3U5o4Lec6428hBc66A2RykQ=
-is-svg@^3.0.0:
- version "3.0.0"
- resolved "https://registry.yarnpkg.com/is-svg/-/is-svg-3.0.0.tgz#9321dbd29c212e5ca99c4fa9794c714bcafa2f75"
- integrity sha512-gi4iHK53LR2ujhLVVj+37Ykh9GLqYHX6JOVXbLAucaG/Cqw9xwdFOjDM2qeifLs1sF1npXXFvDu0r5HNgCMrzQ==
+is-string@^1.0.5, is-string@^1.0.7:
+ version "1.0.7"
+ resolved "https://registry.yarnpkg.com/is-string/-/is-string-1.0.7.tgz#0dd12bf2006f255bb58f695110eff7491eebc0fd"
+ integrity sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==
dependencies:
- html-comment-regex "^1.1.0"
+ has-tostringtag "^1.0.0"
-is-symbol@^1.0.2:
- version "1.0.3"
- resolved "https://registry.yarnpkg.com/is-symbol/-/is-symbol-1.0.3.tgz#38e1014b9e6329be0de9d24a414fd7441ec61937"
- integrity sha512-OwijhaRSgqvhm/0ZdAcXNZt9lYdKFpcRDT5ULUuYXPoT794UNOdU+gpT6Rzo7b4V2HUl/op6GqY894AZwv9faQ==
+is-symbol@^1.0.2, is-symbol@^1.0.3:
+ version "1.0.4"
+ resolved "https://registry.yarnpkg.com/is-symbol/-/is-symbol-1.0.4.tgz#a6dac93b635b063ca6872236de88910a57af139c"
+ integrity sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==
dependencies:
- has-symbols "^1.0.1"
+ has-symbols "^1.0.2"
is-typedarray@^1.0.0, is-typedarray@~1.0.0:
version "1.0.0"
@@ -4706,9 +4847,9 @@ javascript-stringify@^1.6.0:
integrity sha1-FC0RHzpuPa6PSpr9d9RYVbWpzOM=
javascript-stringify@^2.0.1:
- version "2.0.1"
- resolved "https://registry.yarnpkg.com/javascript-stringify/-/javascript-stringify-2.0.1.tgz#6ef358035310e35d667c675ed63d3eb7c1aa19e5"
- integrity sha512-yV+gqbd5vaOYjqlbk16EG89xB5udgjqQF3C5FAORDg4f/IS1Yc5ERCv5e/57yBcfJYw05V5JyIXabhwb75Xxow==
+ version "2.1.0"
+ resolved "https://registry.yarnpkg.com/javascript-stringify/-/javascript-stringify-2.1.0.tgz#27c76539be14d8bd128219a2d731b09337904e79"
+ integrity sha512-JVAfqNPTvNq3sB/VHQJAFxN/sPgKnsKrCwyRt15zwNCdrMMJDdcEOdubuy+DuJYYdm0ox1J4uzEuYKkN+9yhVg==
js-base64@^2.1.8:
version "2.6.4"
@@ -4720,7 +4861,7 @@ js-tokens@^4.0.0:
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499"
integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
-js-yaml@^3.11.0, js-yaml@^3.13.1:
+js-yaml@^3.13.1:
version "3.14.1"
resolved "https://registry.yarnpkg.com/js-yaml/-/js-yaml-3.14.1.tgz#dae812fdb3825fa306609a8717383c50c36a0537"
integrity sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==
@@ -4972,10 +5113,10 @@ lodash.uniq@^4.5.0:
resolved "https://registry.yarnpkg.com/lodash.uniq/-/lodash.uniq-4.5.0.tgz#d0225373aeb652adc1bc82e4945339a842754773"
integrity sha1-0CJTc662Uq3BvILklFM5qEJ1R3M=
-lodash@^4.0.0, lodash@^4.17.11, lodash@^4.17.14, lodash@^4.17.15, lodash@^4.17.19, lodash@^4.17.20, lodash@^4.17.3, lodash@^4.17.5, lodash@~4.17.10:
- version "4.17.20"
- resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.20.tgz#b44a9b6297bcb698f1c51a3545a2b3b368d59c52"
- integrity sha512-PlhdFcillOINfeV7Ni6oF1TAEayyZBoZ8bcshTHqOYJYlrqzRK5hagpagky5o4HfCzzd1TRkXPMFq6cKk9rGmA==
+lodash@^4.0.0, lodash@^4.17.11, lodash@^4.17.14, lodash@^4.17.15, lodash@^4.17.20, lodash@^4.17.21, lodash@^4.17.3, lodash@^4.17.5, lodash@~4.17.10:
+ version "4.17.21"
+ resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.21.tgz#679591c564c3bffaae8454cf0b3df370c3d6911c"
+ integrity sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==
loglevel@^1.6.8:
version "1.7.1"
@@ -5074,6 +5215,11 @@ markdown-it-emoji@^1.4.0:
resolved "https://registry.yarnpkg.com/markdown-it-emoji/-/markdown-it-emoji-1.4.0.tgz#9bee0e9a990a963ba96df6980c4fddb05dfb4dcc"
integrity sha1-m+4OmpkKljupbfaYDE/dsF37Tcw=
+markdown-it-include@^2.0.0:
+ version "2.0.0"
+ resolved "https://registry.yarnpkg.com/markdown-it-include/-/markdown-it-include-2.0.0.tgz#e86e3b3c68c8f0e0437e179ba919ffd28443127a"
+ integrity sha512-wfgIX92ZEYahYWiCk6Jx36XmHvAimeHN420csOWgfyZjpf171Y0xREqZWcm/Rwjzyd0RLYryY+cbNmrkYW2MDw==
+
markdown-it-table-of-contents@^0.4.0:
version "0.4.4"
resolved "https://registry.yarnpkg.com/markdown-it-table-of-contents/-/markdown-it-table-of-contents-0.4.4.tgz#3dc7ce8b8fc17e5981c77cc398d1782319f37fbc"
@@ -5205,17 +5351,22 @@ miller-rabin@^4.0.0:
bn.js "^4.0.0"
brorand "^1.0.1"
-mime-db@1.45.0, "mime-db@>= 1.43.0 < 2":
- version "1.45.0"
- resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.45.0.tgz#cceeda21ccd7c3a745eba2decd55d4b73e7879ea"
- integrity sha512-CkqLUxUk15hofLoLyljJSrukZi8mAtgd+yE5uO4tqRZsdsAJKv0O+rFMhVDRJgozy+yG6md5KwuXhD4ocIoP+w==
+mime-db@1.49.0:
+ version "1.49.0"
+ resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.49.0.tgz#f3dfde60c99e9cf3bc9701d687778f537001cbed"
+ integrity sha512-CIc8j9URtOVApSFCQIF+VBkX1RwXp/oMMOrqdyXSBXq5RWNEsRfyj1kiRnQgmNXmHxPoFIxOroKA3zcU9P+nAA==
+
+"mime-db@>= 1.43.0 < 2":
+ version "1.50.0"
+ resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.50.0.tgz#abd4ac94e98d3c0e185016c67ab45d5fde40c11f"
+ integrity sha512-9tMZCDlYHqeERXEHO9f/hKfNXhre5dK2eE/krIvUjZbS2KPcqGDfNShIWS1uW9XOTKQKqK6qbeOci18rbfW77A==
mime-types@^2.1.12, mime-types@~2.1.17, mime-types@~2.1.19, mime-types@~2.1.24:
- version "2.1.28"
- resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.28.tgz#1160c4757eab2c5363888e005273ecf79d2a0ecd"
- integrity sha512-0TO2yJ5YHYr7M2zzT7gDU1tbwHxEUWBCLt0lscSNpcdAfFyJOVEpRYNS7EXVcTLNj/25QO8gulHC5JtTzSE2UQ==
+ version "2.1.32"
+ resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.32.tgz#1d00e89e7de7fe02008db61001d9e02852670fd5"
+ integrity sha512-hJGaVS4G4c9TSMYh2n6SQAGrC4RnfU+daP8G7cSCmaqNjiOoUY0VHCMS42pxnQmVF1GWwFhbHWn3RIxCqTmZ9A==
dependencies:
- mime-db "1.45.0"
+ mime-db "1.49.0"
mime@1.6.0:
version "1.6.0"
@@ -5223,9 +5374,9 @@ mime@1.6.0:
integrity sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==
mime@^2.0.3, mime@^2.4.4:
- version "2.5.0"
- resolved "https://registry.yarnpkg.com/mime/-/mime-2.5.0.tgz#2b4af934401779806ee98026bb42e8c1ae1876b1"
- integrity sha512-ft3WayFSFUVBuJj7BMLKAQcSlItKtfjsKDDsii3rqFDAZ7t11zRe8ASw/GlmivGwVUYtwkQrxiGGpL6gFvB0ag==
+ version "2.5.2"
+ resolved "https://registry.yarnpkg.com/mime/-/mime-2.5.2.tgz#6e3dc6cc2b9510643830e5f19d5cb753da5eeabe"
+ integrity sha512-tqkh47FzKeCPD2PUiPB6pkbMzsCasjxAfC62/Wap5qrUWcb+sFasXUC5I3gYM5iBM8v/Qpn4UK0x+j0iHyFPDg==
mimic-response@^1.0.0, mimic-response@^1.0.1:
version "1.0.1"
@@ -5358,9 +5509,9 @@ multicast-dns@^6.0.1:
thunky "^1.0.2"
nan@^2.12.1, nan@^2.13.2:
- version "2.14.2"
- resolved "https://registry.yarnpkg.com/nan/-/nan-2.14.2.tgz#f5376400695168f4cc694ac9393d0c9585eeea19"
- integrity sha512-M2ufzIiINKCuDfBSAUr1vWQ+vuVcA9kqx8JJUsbQi6yf1uGRyb7HfpdfUr5qLXf3B/t8dPvcjhKMmlfnP47EzQ==
+ version "2.15.0"
+ resolved "https://registry.yarnpkg.com/nan/-/nan-2.15.0.tgz#3f34a473ff18e15c1b5626b62903b5ad6e665fee"
+ integrity sha512-8ZtvEnA2c5aYCZYd1cvgdnU6cqwixRoYg70xPLWUws5ORTa/lnw+u4amixRS/Ac5U5mQVgp9pnlSUnbNWFaWZQ==
nanomatch@^1.2.9:
version "1.2.13"
@@ -5453,10 +5604,10 @@ node-libs-browser@^2.2.1:
util "^0.11.0"
vm-browserify "^1.0.1"
-node-releases@^1.1.70:
- version "1.1.70"
- resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.70.tgz#66e0ed0273aa65666d7fe78febe7634875426a08"
- integrity sha512-Slf2s69+2/uAD79pVVQo8uSiC34+g8GWY8UH2Qtqv34ZfhYrxpYpfzs9Js9d6O0mbDmALuxaTlplnBTnSELcrw==
+node-releases@^1.1.75:
+ version "1.1.75"
+ resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.75.tgz#6dd8c876b9897a1b8e5a02de26afa79bb54ebbfe"
+ integrity sha512-Qe5OUajvqrqDSy6wrWFmMwfJ0jVgwiw4T3KqmbTcZ62qW0gQkheXYhcFM1+lOVcGUoRxcEcfyvFMAnDgaF1VWw==
node-sass@^4.11.0:
version "4.14.1"
@@ -5537,9 +5688,9 @@ normalize-url@^3.0.0:
integrity sha512-U+JJi7duF1o+u2pynbp2zXDW2/PADgC30f0GsHZtRh+HOcXHnw137TrNlyxxRvWW5fjKd3bcLHPxofWuCjaeZg==
normalize-url@^4.1.0:
- version "4.5.0"
- resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-4.5.0.tgz#453354087e6ca96957bd8f5baf753f5982142129"
- integrity sha512-2s47yzUxdexf1OhyRi4Em83iQk0aPvwTddtFz4hnSSw9dCEsLEGf6SwIO8ss/19S9iBb5sJaOuTvTGDeZI00BQ==
+ version "4.5.1"
+ resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-4.5.1.tgz#0dd90cf1288ee1d1313b87081c9a5932ee48518a"
+ integrity sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA==
npm-run-path@^2.0.0:
version "2.0.2"
@@ -5570,6 +5721,13 @@ nth-check@^1.0.2:
dependencies:
boolbase "~1.0.0"
+nth-check@^2.0.0:
+ version "2.0.0"
+ resolved "https://registry.yarnpkg.com/nth-check/-/nth-check-2.0.0.tgz#1bb4f6dac70072fc313e8c9cd1417b5074c0a125"
+ integrity sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==
+ dependencies:
+ boolbase "^1.0.0"
+
num2fraction@^1.2.2:
version "1.2.2"
resolved "https://registry.yarnpkg.com/num2fraction/-/num2fraction-1.2.2.tgz#6f682b6a027a4e9ddfa4564cd2589d1d4e669ede"
@@ -5599,17 +5757,17 @@ object-copy@^0.1.0:
define-property "^0.2.5"
kind-of "^3.0.3"
-object-inspect@^1.8.0, object-inspect@^1.9.0:
- version "1.9.0"
- resolved "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.9.0.tgz#c90521d74e1127b67266ded3394ad6116986533a"
- integrity sha512-i3Bp9iTqwhaLZBxGkRfo5ZbE07BQRT7MGu8+nNgwW9ItGp1TzCTw2DLEoWwjClxBjOFI/hWljTAmYGCEwmtnOw==
+object-inspect@^1.11.0, object-inspect@^1.9.0:
+ version "1.11.0"
+ resolved "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.11.0.tgz#9dceb146cedd4148a0d9e51ab88d34cf509922b1"
+ integrity sha512-jp7ikS6Sd3GxQfZJPyH3cjcbJF6GZPClgdV+EFygjFLQ5FmW/dRUnTd9PQ9k0JhoNDabWFbpF1yCdSWCC6gexg==
object-is@^1.0.1:
- version "1.1.4"
- resolved "https://registry.yarnpkg.com/object-is/-/object-is-1.1.4.tgz#63d6c83c00a43f4cbc9434eb9757c8a5b8565068"
- integrity sha512-1ZvAZ4wlF7IyPVOcE1Omikt7UpaFlOQq0HlSti+ZvDH3UiD2brwGMwDbyV43jao2bKJ+4+WdPJHSd7kgzKYVqg==
+ version "1.1.5"
+ resolved "https://registry.yarnpkg.com/object-is/-/object-is-1.1.5.tgz#b9deeaa5fc7f1846a0faecdceec138e5778f53ac"
+ integrity sha512-3cyDsyHgtmi7I7DfSSI2LDp6SK2lwvtbg0p0R1e0RvTqF5ceGx+K2dfSjm1bKDMVCFEDAQvy+o8c6a7VujOddw==
dependencies:
- call-bind "^1.0.0"
+ call-bind "^1.0.2"
define-properties "^1.1.3"
object-keys@^1.0.11, object-keys@^1.0.12, object-keys@^1.1.0, object-keys@^1.1.1:
@@ -5624,7 +5782,7 @@ object-visit@^1.0.0:
dependencies:
isobject "^3.0.0"
-object.assign@^4.1.0, object.assign@^4.1.1, object.assign@^4.1.2:
+object.assign@^4.1.0, object.assign@^4.1.2:
version "4.1.2"
resolved "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.2.tgz#0ed54a342eceb37b38ff76eb831a0e788cb63940"
integrity sha512-ixT2L5THXsApyiUPYKmW+2EHpXXe5Ii3M+f4e+aJFAHao5amFRW6J0OO6c/LU8Be47utCx2GL89hxGB6XSmKuQ==
@@ -5635,13 +5793,13 @@ object.assign@^4.1.0, object.assign@^4.1.1, object.assign@^4.1.2:
object-keys "^1.1.1"
object.getownpropertydescriptors@^2.0.3, object.getownpropertydescriptors@^2.1.0:
- version "2.1.1"
- resolved "https://registry.yarnpkg.com/object.getownpropertydescriptors/-/object.getownpropertydescriptors-2.1.1.tgz#0dfda8d108074d9c563e80490c883b6661091544"
- integrity sha512-6DtXgZ/lIZ9hqx4GtZETobXLR/ZLaa0aqV0kzbn80Rf8Z2e/XFnhA0I7p07N2wH8bBBltr2xQPi6sbKWAY2Eng==
+ version "2.1.2"
+ resolved "https://registry.yarnpkg.com/object.getownpropertydescriptors/-/object.getownpropertydescriptors-2.1.2.tgz#1bd63aeacf0d5d2d2f31b5e393b03a7c601a23f7"
+ integrity sha512-WtxeKSzfBjlzL+F9b7M7hewDzMwy+C8NRssHd1YrNlzHzIDrXcXiNOMrezdAEM4UXixgV+vvnyBeN7Rygl2ttQ==
dependencies:
- call-bind "^1.0.0"
+ call-bind "^1.0.2"
define-properties "^1.1.3"
- es-abstract "^1.18.0-next.1"
+ es-abstract "^1.18.0-next.2"
object.pick@^1.3.0:
version "1.3.0"
@@ -5651,14 +5809,13 @@ object.pick@^1.3.0:
isobject "^3.0.1"
object.values@^1.1.0:
- version "1.1.2"
- resolved "https://registry.yarnpkg.com/object.values/-/object.values-1.1.2.tgz#7a2015e06fcb0f546bd652486ce8583a4731c731"
- integrity sha512-MYC0jvJopr8EK6dPBiO8Nb9mvjdypOachO5REGk6MXzujbBrAisKo3HmdEI6kZDL6fC31Mwee/5YbtMebixeag==
+ version "1.1.4"
+ resolved "https://registry.yarnpkg.com/object.values/-/object.values-1.1.4.tgz#0d273762833e816b693a637d30073e7051535b30"
+ integrity sha512-TnGo7j4XSnKQoK3MfvkzqKCi0nVe/D9I9IjwTNYdb/fxYHpjrluHVOgw0AF6jrRFGMPHdfuidR09tIDiIvnaSg==
dependencies:
- call-bind "^1.0.0"
+ call-bind "^1.0.2"
define-properties "^1.1.3"
- es-abstract "^1.18.0-next.1"
- has "^1.0.3"
+ es-abstract "^1.18.2"
obuf@^1.0.0, obuf@^1.1.2:
version "1.1.2"
@@ -5697,9 +5854,9 @@ opn@^5.5.0:
is-wsl "^1.1.0"
optimize-css-assets-webpack-plugin@^5.0.1:
- version "5.0.4"
- resolved "https://registry.yarnpkg.com/optimize-css-assets-webpack-plugin/-/optimize-css-assets-webpack-plugin-5.0.4.tgz#85883c6528aaa02e30bbad9908c92926bb52dc90"
- integrity sha512-wqd6FdI2a5/FdoiCNNkEvLeA//lHHfG24Ln2Xm2qqdIk4aOlsR18jwpyOihqQ8849W3qu2DX8fOYxpvTMj+93A==
+ version "5.0.8"
+ resolved "https://registry.yarnpkg.com/optimize-css-assets-webpack-plugin/-/optimize-css-assets-webpack-plugin-5.0.8.tgz#cbccdcf5a6ef61d4f8cc78cf083a67446e5f402a"
+ integrity sha512-mgFS1JdOtEGzD8l+EuISqL57cKO+We9GcoiQEmdCWRqqck+FGNmYJtx9qfAPzEz+lRrlThWMuGDaRkI/yWNx/Q==
dependencies:
cssnano "^4.1.10"
last-call-webpack-plugin "^3.0.0"
@@ -5892,9 +6049,9 @@ path-key@^2.0.0, path-key@^2.0.1:
integrity sha1-QRyttXTFoUDTpLGRDUDYDMn0C0A=
path-parse@^1.0.6:
- version "1.0.6"
- resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.6.tgz#d62dbb5679405d72c4737ec58600e9ddcf06d24c"
- integrity sha512-GSmOT2EbHrINBf9SR7CDELwlJ8AENk3Qn7OikK4nFYAu3Ote2+JYNVvkpAEQm3/TLNEJFD/xZJjzyxg3KBWOzw==
+ version "1.0.7"
+ resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.7.tgz#fbc114b60ca42b30d9daf5858e4bd68bbedb6735"
+ integrity sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==
path-to-regexp@0.1.7:
version "0.1.7"
@@ -5918,9 +6075,9 @@ path-type@^3.0.0:
pify "^3.0.0"
pbkdf2@^3.0.3:
- version "3.1.1"
- resolved "https://registry.yarnpkg.com/pbkdf2/-/pbkdf2-3.1.1.tgz#cb8724b0fada984596856d1a6ebafd3584654b94"
- integrity sha512-4Ejy1OPxi9f2tt1rRV7Go7zmfDQ+ZectEQz3VGUQhgq62HtIRPDyG/JtnwIxs6x3uNMwo2V7q1fMvKjb+Tnpqg==
+ version "3.1.2"
+ resolved "https://registry.yarnpkg.com/pbkdf2/-/pbkdf2-3.1.2.tgz#dd822aa0887580e52f1a039dc3eda108efae3075"
+ integrity sha512-iuh7L6jA7JEGu2WxDwtQP1ddOpaJNC4KlDEFfdQajSGgGPNi4OyDc2R7QnbY2bR9QjBVGwgvTdNJZoE7RaxUMA==
dependencies:
create-hash "^1.1.2"
create-hmac "^1.1.4"
@@ -5934,9 +6091,9 @@ performance-now@^2.1.0:
integrity sha1-Ywn04OX6kT7BxpMHrjZLSzd8nns=
picomatch@^2.0.4, picomatch@^2.2.1:
- version "2.2.2"
- resolved "https://registry.yarnpkg.com/picomatch/-/picomatch-2.2.2.tgz#21f333e9b6b8eaff02468f5146ea406d345f4dad"
- integrity sha512-q0M/9eZHzmr0AulXyPwNfZjtwZ/RBZlbN3K3CErVrk50T2ASYI7Bye0EvekFY3IP1Nt2DHu0re+V2ZHIpMkuWg==
+ version "2.3.0"
+ resolved "https://registry.yarnpkg.com/picomatch/-/picomatch-2.3.0.tgz#f1f061de8f6a4bf022892e2d128234fb98302972"
+ integrity sha512-lY1Q/PiJGC2zOv/z391WOTD+Z02bCgsFfvxoXXf6h7kv9o+WmsmzYqrAwY63sNgOxE4xEdq0WyUnXfKeBrSvYw==
pify@^2.0.0:
version "2.3.0"
@@ -6288,21 +6445,18 @@ postcss-selector-parser@^3.0.0:
uniq "^1.0.1"
postcss-selector-parser@^6.0.0, postcss-selector-parser@^6.0.2:
- version "6.0.4"
- resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-6.0.4.tgz#56075a1380a04604c38b063ea7767a129af5c2b3"
- integrity sha512-gjMeXBempyInaBqpp8gODmwZ52WaYsVOsfr4L4lDQ7n3ncD6mEyySiDtgzCT+NYC0mmeOLvtsF8iaEf0YT6dBw==
+ version "6.0.6"
+ resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-6.0.6.tgz#2c5bba8174ac2f6981ab631a42ab0ee54af332ea"
+ integrity sha512-9LXrvaaX3+mcv5xkg5kFwqSzSH1JIObIx51PrndZwlmznwXRfxMddDvo9gve3gVR8ZTKgoFDdWkbRFmEhT4PMg==
dependencies:
cssesc "^3.0.0"
- indexes-of "^1.0.1"
- uniq "^1.0.1"
util-deprecate "^1.0.2"
-postcss-svgo@^4.0.2:
- version "4.0.2"
- resolved "https://registry.yarnpkg.com/postcss-svgo/-/postcss-svgo-4.0.2.tgz#17b997bc711b333bab143aaed3b8d3d6e3d38258"
- integrity sha512-C6wyjo3VwFm0QgBy+Fu7gCYOkCmgmClghO+pjcxvrcBKtiKt0uCF+hvbMO1fyv5BMImRK90SMb+dwUnfbGd+jw==
+postcss-svgo@^4.0.3:
+ version "4.0.3"
+ resolved "https://registry.yarnpkg.com/postcss-svgo/-/postcss-svgo-4.0.3.tgz#343a2cdbac9505d416243d496f724f38894c941e"
+ integrity sha512-NoRbrcMWTtUghzuKSoIm6XV+sJdvZ7GZSc3wdBN0W19FTtp2ko8NqLsgoh/m9CzNhU3KLPvQmjIwtaNFkaFTvw==
dependencies:
- is-svg "^3.0.0"
postcss "^7.0.0"
postcss-value-parser "^3.0.0"
svgo "^1.0.0"
@@ -6326,10 +6480,10 @@ postcss-value-parser@^4.0.2, postcss-value-parser@^4.1.0:
resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-4.1.0.tgz#443f6a20ced6481a2bda4fa8532a6e55d789a2cb"
integrity sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ==
-postcss@^7.0.0, postcss@^7.0.1, postcss@^7.0.14, postcss@^7.0.26, postcss@^7.0.27, postcss@^7.0.32, postcss@^7.0.5, postcss@^7.0.6:
- version "7.0.35"
- resolved "https://registry.yarnpkg.com/postcss/-/postcss-7.0.35.tgz#d2be00b998f7f211d8a276974079f2e92b970e24"
- integrity sha512-3QT8bBJeX/S5zKTTjTCIjRF3If4avAT6kqxcASlTWEtAFCb9NH0OUxNDfgZSWdP5fJnBYCMEWkIFfWeugjzYMg==
+postcss@^7.0.0, postcss@^7.0.1, postcss@^7.0.14, postcss@^7.0.26, postcss@^7.0.27, postcss@^7.0.32, postcss@^7.0.36, postcss@^7.0.5, postcss@^7.0.6:
+ version "7.0.36"
+ resolved "https://registry.yarnpkg.com/postcss/-/postcss-7.0.36.tgz#056f8cffa939662a8f5905950c07d5285644dfcb"
+ integrity sha512-BebJSIUMwJHRH0HAQoxN4u1CN86glsrwsW0q7T+/m44eXOUAxSNdHRkNZPYz5vVUbg17hFgOQDE7fZk7li3pZw==
dependencies:
chalk "^2.4.2"
source-map "^0.6.1"
@@ -6359,11 +6513,9 @@ pretty-time@^1.1.0:
integrity sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA==
prismjs@^1.13.0:
- version "1.23.0"
- resolved "https://registry.yarnpkg.com/prismjs/-/prismjs-1.23.0.tgz#d3b3967f7d72440690497652a9d40ff046067f33"
- integrity sha512-c29LVsqOaLbBHuIbsTxaKENh1N2EQBOHaWv7gkHN4dgRbxSREqDnDbtFJYdpPauS4YCplMSNCABQ6Eeor69bAA==
- optionalDependencies:
- clipboard "^2.0.0"
+ version "1.24.1"
+ resolved "https://registry.yarnpkg.com/prismjs/-/prismjs-1.24.1.tgz#c4d7895c4d6500289482fa8936d9cdd192684036"
+ integrity sha512-mNPsedLuk90RVJioIky8ANZEwYm5w9LcvCXrxHlwf4fNVSn8jEipMybMkWUyyF0JhnC+C4VcOVSBuHRKs1L5Ow==
process-nextick-args@~2.0.0:
version "2.0.1"
@@ -6381,11 +6533,11 @@ promise-inflight@^1.0.1:
integrity sha1-mEcocL8igTL8vdhoEputEsPAKeM=
proxy-addr@~2.0.5:
- version "2.0.6"
- resolved "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.6.tgz#fdc2336505447d3f2f2c638ed272caf614bbb2bf"
- integrity sha512-dh/frvCBVmSsDYzw6n926jv974gddhkFPfiN8hPOi30Wax25QZyZEGveluCgliBnqmuM+UJmBErbAUFIoDbjOw==
+ version "2.0.7"
+ resolved "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.7.tgz#f19fe69ceab311eeb94b42e70e8c2070f9ba1025"
+ integrity sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==
dependencies:
- forwarded "~0.1.2"
+ forwarded "0.2.0"
ipaddr.js "1.9.1"
prr@~1.0.1:
@@ -6571,7 +6723,7 @@ read-pkg@^1.0.0:
string_decoder "~1.1.1"
util-deprecate "~1.0.1"
-readable-stream@^3.0.6, readable-stream@^3.1.1, readable-stream@^3.6.0:
+readable-stream@^3.0.6, readable-stream@^3.6.0:
version "3.6.0"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.6.0.tgz#337bbda3adc0706bd3e024426a286d4b4b2c9198"
integrity sha512-BViHy7LKeTz4oNnkcLJ+lVSL6vpiFeX6/d3oSH8zCW7UxP2onchk+vTGB143xuFjHS3deTgkKoXXymXqymiIdA==
@@ -6589,10 +6741,10 @@ readdirp@^2.2.1:
micromatch "^3.1.10"
readable-stream "^2.0.2"
-readdirp@~3.5.0:
- version "3.5.0"
- resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-3.5.0.tgz#9ba74c019b15d365278d2e91bb8c48d7b4d42c9e"
- integrity sha512-cMhu7c/8rdhkHXWsY+osBhfSy0JikwpHK/5+imo+LpeasTF8ouErHrlYkwT0++njiyuDvc7OFY5T3ukvZ8qmFQ==
+readdirp@~3.6.0:
+ version "3.6.0"
+ resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-3.6.0.tgz#74a370bd857116e245b29cc97340cd431a02a6c7"
+ integrity sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==
dependencies:
picomatch "^2.2.1"
@@ -6611,22 +6763,22 @@ reduce@^1.0.1:
dependencies:
object-keys "^1.1.0"
-regenerate-unicode-properties@^8.2.0:
- version "8.2.0"
- resolved "https://registry.yarnpkg.com/regenerate-unicode-properties/-/regenerate-unicode-properties-8.2.0.tgz#e5de7111d655e7ba60c057dbe9ff37c87e65cdec"
- integrity sha512-F9DjY1vKLo/tPePDycuH3dn9H1OTPIkVD9Kz4LODu+F2C75mgjAJ7x/gwy6ZcSNRAAkhNlJSOHRe8k3p+K9WhA==
+regenerate-unicode-properties@^9.0.0:
+ version "9.0.0"
+ resolved "https://registry.yarnpkg.com/regenerate-unicode-properties/-/regenerate-unicode-properties-9.0.0.tgz#54d09c7115e1f53dc2314a974b32c1c344efe326"
+ integrity sha512-3E12UeNSPfjrgwjkR81m5J7Aw/T55Tu7nUyZVQYCKEOs+2dkxEY+DpPtZzO4YruuiPb7NkYLVcyJC4+zCbk5pA==
dependencies:
- regenerate "^1.4.0"
+ regenerate "^1.4.2"
-regenerate@^1.4.0:
+regenerate@^1.4.2:
version "1.4.2"
resolved "https://registry.yarnpkg.com/regenerate/-/regenerate-1.4.2.tgz#b9346d8827e8f5a32f7ba29637d398b69014848a"
integrity sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==
regenerator-runtime@^0.13.4:
- version "0.13.7"
- resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.13.7.tgz#cac2dacc8a1ea675feaabaeb8ae833898ae46f55"
- integrity sha512-a54FxoJDIr27pgf7IgeQGxmqUNYrcV338lf/6gH456HZ/PhX+5BcwHXG9ajESmwe6WRO0tAzRUrRmNONWgkrew==
+ version "0.13.9"
+ resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.13.9.tgz#8925742a98ffd90814988d7566ad30ca3b263b52"
+ integrity sha512-p3VT+cOEgxFsRRA9X4lkI1E+k2/CtnKtU4gcxyaCUreilL/vqI6CdZ3wxVUx3UOUg+gnUOQQcRI7BmSI656MYA==
regenerator-transform@^0.14.2:
version "0.14.5"
@@ -6652,16 +6804,16 @@ regexp.prototype.flags@^1.2.0:
define-properties "^1.1.3"
regexpu-core@^4.7.1:
- version "4.7.1"
- resolved "https://registry.yarnpkg.com/regexpu-core/-/regexpu-core-4.7.1.tgz#2dea5a9a07233298fbf0db91fa9abc4c6e0f8ad6"
- integrity sha512-ywH2VUraA44DZQuRKzARmw6S66mr48pQVva4LBeRhcOltJ6hExvWly5ZjFLYo67xbIxb6W1q4bAGtgfEl20zfQ==
+ version "4.8.0"
+ resolved "https://registry.yarnpkg.com/regexpu-core/-/regexpu-core-4.8.0.tgz#e5605ba361b67b1718478501327502f4479a98f0"
+ integrity sha512-1F6bYsoYiz6is+oz70NWur2Vlh9KWtswuRuzJOfeYUrfPX2o8n74AnUVaOGDbUqVGO9fNHu48/pjJO4sNVwsOg==
dependencies:
- regenerate "^1.4.0"
- regenerate-unicode-properties "^8.2.0"
- regjsgen "^0.5.1"
- regjsparser "^0.6.4"
- unicode-match-property-ecmascript "^1.0.4"
- unicode-match-property-value-ecmascript "^1.2.0"
+ regenerate "^1.4.2"
+ regenerate-unicode-properties "^9.0.0"
+ regjsgen "^0.5.2"
+ regjsparser "^0.7.0"
+ unicode-match-property-ecmascript "^2.0.0"
+ unicode-match-property-value-ecmascript "^2.0.0"
registry-auth-token@^4.0.0:
version "4.2.1"
@@ -6677,15 +6829,15 @@ registry-url@^5.0.0:
dependencies:
rc "^1.2.8"
-regjsgen@^0.5.1:
+regjsgen@^0.5.2:
version "0.5.2"
resolved "https://registry.yarnpkg.com/regjsgen/-/regjsgen-0.5.2.tgz#92ff295fb1deecbf6ecdab2543d207e91aa33733"
integrity sha512-OFFT3MfrH90xIW8OOSyUrk6QHD5E9JOTeGodiJeBS3J6IwlgzJMNE/1bZklWz5oTg+9dCMyEetclvCVXOPoN3A==
-regjsparser@^0.6.4:
- version "0.6.7"
- resolved "https://registry.yarnpkg.com/regjsparser/-/regjsparser-0.6.7.tgz#c00164e1e6713c2e3ee641f1701c4b7aa0a7f86c"
- integrity sha512-ib77G0uxsA2ovgiYbCVGx4Pv3PSttAx2vIwidqQzbL2U5S4Q+j00HdSAneSBuyVcMvEnTXMjiGgB+DlXozVhpQ==
+regjsparser@^0.7.0:
+ version "0.7.0"
+ resolved "https://registry.yarnpkg.com/regjsparser/-/regjsparser-0.7.0.tgz#a6b667b54c885e18b52554cb4960ef71187e9968"
+ integrity sha512-A4pcaORqmNMDVwUjWoTzuhwMGpP+NykpfqAsEgI1FSH/EzC7lrN5TMd+kN8YCovX+jMpu8eaqXgXPCa0g8FQNQ==
dependencies:
jsesc "~0.5.0"
@@ -6700,20 +6852,20 @@ remove-trailing-separator@^1.0.1:
integrity sha1-wkvOKig62tW8P1jg1IJJuSN52O8=
renderkid@^2.0.4:
- version "2.0.5"
- resolved "https://registry.yarnpkg.com/renderkid/-/renderkid-2.0.5.tgz#483b1ac59c6601ab30a7a596a5965cabccfdd0a5"
- integrity sha512-ccqoLg+HLOHq1vdfYNm4TBeaCDIi1FLt3wGojTDSvdewUv65oTmI3cnT2E4hRjl1gzKZIPK+KZrXzlUYKnR+vQ==
- dependencies:
- css-select "^2.0.2"
- dom-converter "^0.2"
- htmlparser2 "^3.10.1"
- lodash "^4.17.20"
- strip-ansi "^3.0.0"
+ version "2.0.7"
+ resolved "https://registry.yarnpkg.com/renderkid/-/renderkid-2.0.7.tgz#464f276a6bdcee606f4a15993f9b29fc74ca8609"
+ integrity sha512-oCcFyxaMrKsKcTY59qnCAtmDVSLfPbrv6A3tVbPdFMMrv5jaK10V6m40cKsoPNhAqN6rmHW9sswW4o3ruSrwUQ==
+ dependencies:
+ css-select "^4.1.3"
+ dom-converter "^0.2.0"
+ htmlparser2 "^6.1.0"
+ lodash "^4.17.21"
+ strip-ansi "^3.0.1"
repeat-element@^1.1.2:
- version "1.1.3"
- resolved "https://registry.yarnpkg.com/repeat-element/-/repeat-element-1.1.3.tgz#782e0d825c0c5a3bb39731f84efee6b742e6b1ce"
- integrity sha512-ahGq0ZnV5m5XtZLMb+vP76kcAM5nkLqk0lpqAuojSKGgQtn4eRi4ZZGm2olo2zKFH+sMsWaqOCW1dqAnOru72g==
+ version "1.1.4"
+ resolved "https://registry.yarnpkg.com/repeat-element/-/repeat-element-1.1.4.tgz#be681520847ab58c7568ac75fbfad28ed42d39e9"
+ integrity sha512-LFiNfRcSu7KK3evMyYOuCzv3L10TW7yC1G2/+StMjK8Y6Vqd2MG7r/Qjw4ghtuCOjFvlnms/iMmLqpvW/ES/WQ==
repeat-string@^1.6.1:
version "1.6.1"
@@ -6790,12 +6942,12 @@ resolve-url@^0.2.1:
resolved "https://registry.yarnpkg.com/resolve-url/-/resolve-url-0.2.1.tgz#2c637fe77c893afd2a663fe21aa9080068e2052a"
integrity sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo=
-resolve@^1.10.0, resolve@^1.2.0:
- version "1.19.0"
- resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.19.0.tgz#1af5bf630409734a067cae29318aac7fa29a267c"
- integrity sha512-rArEXAgsBG4UgRGcynxWIWKFvh/XZCcS8UJdHhwy91zwAvCZIbcs+vAbflgBnNjYMs/i/i+/Ux6IZhML1yPvxg==
+resolve@^1.10.0, resolve@^1.14.2, resolve@^1.2.0:
+ version "1.20.0"
+ resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.20.0.tgz#629a013fb3f70755d6f0b7935cc1c2c5378b1975"
+ integrity sha512-wENBPt4ySzg4ybFQW2TT1zMQucPK95HSh/nq2CFTZVOGut2+pQvSsgtda4d26YrYcr067wjbmzOG8byDPBX63A==
dependencies:
- is-core-module "^2.1.0"
+ is-core-module "^2.2.0"
path-parse "^1.0.6"
responselike@^1.0.2:
@@ -6934,15 +7086,10 @@ select-hose@^2.0.0:
resolved "https://registry.yarnpkg.com/select-hose/-/select-hose-2.0.0.tgz#625d8658f865af43ec962bfc376a37359a4994ca"
integrity sha1-Yl2GWPhlr0Psliv8N2o3NZpJlMo=
-select@^1.1.2:
- version "1.1.2"
- resolved "https://registry.yarnpkg.com/select/-/select-1.1.2.tgz#0e7350acdec80b1108528786ec1d4418d11b396d"
- integrity sha1-DnNQrN7ICxEIUoeG7B1EGNEbOW0=
-
selfsigned@^1.10.8:
- version "1.10.8"
- resolved "https://registry.yarnpkg.com/selfsigned/-/selfsigned-1.10.8.tgz#0d17208b7d12c33f8eac85c41835f27fc3d81a30"
- integrity sha512-2P4PtieJeEwVgTU9QEcwIRDQ/mXJLX8/+I3ur+Pg16nS8oNbrGxEso9NyYWy8NAmXiNl4dlAp5MwoNeCWzON4w==
+ version "1.10.11"
+ resolved "https://registry.yarnpkg.com/selfsigned/-/selfsigned-1.10.11.tgz#24929cd906fe0f44b6d01fb23999a739537acbe9"
+ integrity sha512-aVmbPOfViZqOZPgRBT0+3u4yZFHpmnIghLMlAcb5/xhp5ZtB/RVnKhz5vl2M32CLXAqR4kha9zfhNg0Lf/sxKA==
dependencies:
node-forge "^0.10.0"
@@ -6953,7 +7100,7 @@ semver-diff@^3.1.1:
dependencies:
semver "^6.3.0"
-"semver@2 || 3 || 4 || 5", semver@^5.1.0, semver@^5.4.1, semver@^5.5.0, semver@^5.5.1, semver@^5.6.0:
+"semver@2 || 3 || 4 || 5", semver@^5.1.0, semver@^5.5.0, semver@^5.6.0:
version "5.7.1"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.7.1.tgz#a954f931aeba508d307bbf069eff0c01c96116f7"
integrity sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==
@@ -6963,7 +7110,7 @@ semver@7.0.0:
resolved "https://registry.yarnpkg.com/semver/-/semver-7.0.0.tgz#5f3ca35761e47e05b206c6daff2cf814f0316b8e"
integrity sha512-+GB6zVA9LWh6zovYQLALHwv5rb2PHGlJi3lfiqIHxR0uuwCgefcOJc59v9fv1w8GbStwxuuqqAjI9NMAOOgq1A==
-semver@^6.0.0, semver@^6.1.0, semver@^6.2.0, semver@^6.3.0:
+semver@^6.0.0, semver@^6.1.0, semver@^6.1.1, semver@^6.1.2, semver@^6.2.0, semver@^6.3.0:
version "6.3.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-6.3.0.tgz#ee0a64c8af5e8ceea67687b133761e1becbd1d3d"
integrity sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==
@@ -7086,10 +7233,19 @@ shebang-regex@^1.0.0:
resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-1.0.0.tgz#da42f49740c0b42db2ca9728571cb190c98efea3"
integrity sha1-2kL0l0DAtC2yypcoVxyxkMmO/qM=
+side-channel@^1.0.4:
+ version "1.0.4"
+ resolved "https://registry.yarnpkg.com/side-channel/-/side-channel-1.0.4.tgz#efce5c8fdc104ee751b25c58d4290011fa5ea2cf"
+ integrity sha512-q5XPytqFEIKHkGdiMIrY10mvLRvnQh42/+GoBlFW3b2LXLE2xxJpZFdm94we0BaoV3RwJyGqg5wS7epxTv0Zvw==
+ dependencies:
+ call-bind "^1.0.0"
+ get-intrinsic "^1.0.2"
+ object-inspect "^1.9.0"
+
signal-exit@^3.0.0, signal-exit@^3.0.2:
- version "3.0.3"
- resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.3.tgz#a1410c2edd8f077b08b4e253c8eacfcaf057461c"
- integrity sha512-VUJ49FC8U1OxwZLxIbTTrDvLnf/6TDgxZcK8wxR8zs13xpx7xbG60ndBlhNrFi2EMuFRoeDoJO7wthSLq42EjA==
+ version "3.0.4"
+ resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.4.tgz#366a4684d175b9cab2081e3681fda3747b6c51d7"
+ integrity sha512-rqYhcAnZ6d/vTPGghdrw7iumdcbXpsk1b8IG/rz+VWV51DM0p7XCtMoJ3qhPLIbp3tvyt3pKRbaaEMZYpHto8Q==
simple-swizzle@^0.2.2:
version "0.2.2"
@@ -7144,16 +7300,16 @@ snapdragon@^0.8.1:
use "^3.1.0"
sockjs-client@^1.5.0:
- version "1.5.0"
- resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.5.0.tgz#2f8ff5d4b659e0d092f7aba0b7c386bd2aa20add"
- integrity sha512-8Dt3BDi4FYNrCFGTL/HtwVzkARrENdwOUf1ZoW/9p3M8lZdFT35jVdrHza+qgxuG9H3/shR4cuX/X9umUrjP8Q==
+ version "1.5.2"
+ resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.5.2.tgz#4bc48c2da9ce4769f19dc723396b50f5c12330a3"
+ integrity sha512-ZzRxPBISQE7RpzlH4tKJMQbHM9pabHluk0WBaxAQ+wm/UieeBVBou0p4wVnSQGN9QmpAZygQ0cDIypWuqOFmFQ==
dependencies:
debug "^3.2.6"
eventsource "^1.0.7"
faye-websocket "^0.11.3"
inherits "^2.0.4"
json3 "^3.3.3"
- url-parse "^1.4.7"
+ url-parse "^1.5.3"
sockjs@^0.3.21:
version "0.3.21"
@@ -7188,9 +7344,9 @@ source-map-resolve@^0.5.0, source-map-resolve@^0.5.2:
urix "^0.1.0"
source-map-support@~0.5.12:
- version "0.5.19"
- resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.19.tgz#a98b62f86dcaf4f67399648c085291ab9e8fed61"
- integrity sha512-Wonm7zOCIJzBGQdB+thsPar0kYuCIzYvxZwlBa87yi/Mdjv7Tip2cyVbLj5o0cFPN4EVkuTwb3GDDyUx2DGnGw==
+ version "0.5.20"
+ resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.20.tgz#12166089f8f5e5e8c56926b377633392dd2cb6c9"
+ integrity sha512-n1lZZ8Ve4ksRqizaBQgxXDgKwttHDhyfQjA6YZZn8+AroHbsIz+JjwxQDxbp+7y5OYCI8t1Yk7etjD9CRd2hIw==
dependencies:
buffer-from "^1.0.0"
source-map "^0.6.0"
@@ -7249,9 +7405,9 @@ spdx-expression-parse@^3.0.0:
spdx-license-ids "^3.0.0"
spdx-license-ids@^3.0.0:
- version "3.0.7"
- resolved "https://registry.yarnpkg.com/spdx-license-ids/-/spdx-license-ids-3.0.7.tgz#e9c18a410e5ed7e12442a549fbd8afa767038d65"
- integrity sha512-U+MTEOO0AiDzxwFvoa4JVnMV6mZlJKk2sBLt90s7G0Gd0Mlknc7kxEn3nuDPNZRta7O2uy8oLcZLVT+4sqNZHQ==
+ version "3.0.10"
+ resolved "https://registry.yarnpkg.com/spdx-license-ids/-/spdx-license-ids-3.0.10.tgz#0d9becccde7003d6c658d487dd48a32f0bf3014b"
+ integrity sha512-oie3/+gKf7QtpitB0LYLETe+k8SifzsX4KixvpOsbI6S0kRiRQ5MKOio8eMSAKQ17N06+wdEOXRiId+zOxo0hA==
spdy-transport@^3.0.0:
version "3.0.0"
@@ -7304,9 +7460,9 @@ sshpk@^1.7.0:
tweetnacl "~0.14.0"
ssri@^6.0.1:
- version "6.0.1"
- resolved "https://registry.yarnpkg.com/ssri/-/ssri-6.0.1.tgz#2a3c41b28dd45b62b63676ecb74001265ae9edd8"
- integrity sha512-3Wge10hNcT1Kur4PDFwEieXSCMCJs/7WvSACcrMYrNp+b8kDL1/0wJch5Ni2WrtwEa2IO8OsVfeKIciKCDx/QA==
+ version "6.0.2"
+ resolved "https://registry.yarnpkg.com/ssri/-/ssri-6.0.2.tgz#157939134f20464e7301ddba3e90ffa8f7728ac5"
+ integrity sha512-cepbSq/neFK7xB6A50KHN0xHDotYzq58wWCa5LeWqnPrHG8GzfEjO/4O8kpmcGW+oaxkvhEJCWgbgNk4/ZV93Q==
dependencies:
figgy-pudding "^3.5.1"
@@ -7316,9 +7472,9 @@ stable@^0.1.8:
integrity sha512-ji9qxRnOVfcuLDySj9qzhGSEFVobyt1kIOSkj1qZzYLzq7Tos/oUUWvotUPQLlrsidqsK6tBH89Bc9kL5zHA6w==
stack-utils@^1.0.1:
- version "1.0.4"
- resolved "https://registry.yarnpkg.com/stack-utils/-/stack-utils-1.0.4.tgz#4b600971dcfc6aed0cbdf2a8268177cc916c87c8"
- integrity sha512-IPDJfugEGbfizBwBZRZ3xpccMdRyP5lqsBWXGQWimVjua/ccLCeMOAVjlc1R7LxFjo5sEDhyNIXd8mo/AiDS9w==
+ version "1.0.5"
+ resolved "https://registry.yarnpkg.com/stack-utils/-/stack-utils-1.0.5.tgz#a19b0b01947e0029c8e451d5d61a498f5bb1471b"
+ integrity sha512-KZiTzuV3CnSnSvgMRrARVCj+Ht7rMbauGDK0LdVFRGyenwdylpajAp4Q0i6SX8rEmbTpMMf6ryq2gb8pPq2WgQ==
dependencies:
escape-string-regexp "^2.0.0"
@@ -7336,11 +7492,11 @@ static-extend@^0.1.1:
integrity sha1-Fhx9rBd2Wf2YEfQ3cfqZOBR4Yow=
std-env@^2.2.1:
- version "2.2.1"
- resolved "https://registry.yarnpkg.com/std-env/-/std-env-2.2.1.tgz#2ffa0fdc9e2263e0004c1211966e960948a40f6b"
- integrity sha512-IjYQUinA3lg5re/YMlwlfhqNRTzMZMqE+pezevdcTaHceqx8ngEi1alX9nNCk9Sc81fy1fLDeQoaCzeiW1yBOQ==
+ version "2.3.0"
+ resolved "https://registry.yarnpkg.com/std-env/-/std-env-2.3.0.tgz#66d4a4a4d5224242ed8e43f5d65cfa9095216eee"
+ integrity sha512-4qT5B45+Kjef2Z6pE0BkskzsH0GO7GrND0wGlTM1ioUe3v0dGYx9ZJH0Aro/YyA8fqQ5EyIKDRjZojJYMFTflw==
dependencies:
- ci-info "^1.6.0"
+ ci-info "^3.0.0"
stdout-stream@^1.4.0:
version "1.4.1"
@@ -7413,28 +7569,28 @@ string-width@^3.0.0, string-width@^3.1.0:
strip-ansi "^5.1.0"
string-width@^4.0.0, string-width@^4.1.0:
- version "4.2.0"
- resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.0.tgz#952182c46cc7b2c313d1596e623992bd163b72b5"
- integrity sha512-zUz5JD+tgqtuDjMhwIg5uFVV3dtqZ9yQJlZVfq4I01/K5Paj5UHj7VyrQOJvzawSVlKpObApbfD0Ed6yJc+1eg==
+ version "4.2.2"
+ resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.2.tgz#dafd4f9559a7585cfba529c6a0a4f73488ebd4c5"
+ integrity sha512-XBJbT3N4JhVumXE0eoLU9DCjcaF92KLNqTmFCnG1pf8duUxFGwtP6AD6nkjw9a3IdiRtL3E2w3JDiE/xi3vOeA==
dependencies:
emoji-regex "^8.0.0"
is-fullwidth-code-point "^3.0.0"
strip-ansi "^6.0.0"
-string.prototype.trimend@^1.0.1, string.prototype.trimend@^1.0.3:
- version "1.0.3"
- resolved "https://registry.yarnpkg.com/string.prototype.trimend/-/string.prototype.trimend-1.0.3.tgz#a22bd53cca5c7cf44d7c9d5c732118873d6cd18b"
- integrity sha512-ayH0pB+uf0U28CtjlLvL7NaohvR1amUvVZk+y3DYb0Ey2PUV5zPkkKy9+U1ndVEIXO8hNg18eIv9Jntbii+dKw==
+string.prototype.trimend@^1.0.4:
+ version "1.0.4"
+ resolved "https://registry.yarnpkg.com/string.prototype.trimend/-/string.prototype.trimend-1.0.4.tgz#e75ae90c2942c63504686c18b287b4a0b1a45f80"
+ integrity sha512-y9xCjw1P23Awk8EvTpcyL2NIr1j7wJ39f+k6lvRnSMz+mz9CGz9NYPelDk42kOz6+ql8xjfK8oYzy3jAP5QU5A==
dependencies:
- call-bind "^1.0.0"
+ call-bind "^1.0.2"
define-properties "^1.1.3"
-string.prototype.trimstart@^1.0.1, string.prototype.trimstart@^1.0.3:
- version "1.0.3"
- resolved "https://registry.yarnpkg.com/string.prototype.trimstart/-/string.prototype.trimstart-1.0.3.tgz#9b4cb590e123bb36564401d59824298de50fd5aa"
- integrity sha512-oBIBUy5lea5tt0ovtOFiEQaBkoBBkyJhZXzJYrSmDo5IUUqbOPvVezuRs/agBIdZ2p2Eo1FD6bD9USyBLfl3xg==
+string.prototype.trimstart@^1.0.4:
+ version "1.0.4"
+ resolved "https://registry.yarnpkg.com/string.prototype.trimstart/-/string.prototype.trimstart-1.0.4.tgz#b36399af4ab2999b4c9c648bd7a3fb2bb26feeed"
+ integrity sha512-jh6e984OBfvxS50tdY2nRZnoC5/mLFKOREQfw8t5yytkoUsJRNxvI/E39qu1sD0OtWI3OC0XgKSmcWwziwYuZw==
dependencies:
- call-bind "^1.0.0"
+ call-bind "^1.0.2"
define-properties "^1.1.3"
string_decoder@^1.0.0, string_decoder@^1.1.1:
@@ -7668,11 +7824,6 @@ timsort@^0.3.0:
resolved "https://registry.yarnpkg.com/timsort/-/timsort-0.3.0.tgz#405411a8e7e6339fe64db9a234de11dc31e02bd4"
integrity sha1-QFQRqOfmM5/mTbmiNN4R3DHgK9Q=
-tiny-emitter@^2.0.0:
- version "2.1.0"
- resolved "https://registry.yarnpkg.com/tiny-emitter/-/tiny-emitter-2.1.0.tgz#1d1a56edfc51c43e863cbb5382a72330e3555423"
- integrity sha512-NB6Dk1A9xgQPMoGqC5CVXn123gWyte215ONT5Pp5a0yt4nlEoO1ZWeCwpncaekPHXO60i47ihFnZPiRPjRMq4Q==
-
to-arraybuffer@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/to-arraybuffer/-/to-arraybuffer-1.0.1.tgz#7d229b1fcc637e466ca081180836a7aabff83f43"
@@ -7760,11 +7911,6 @@ trim-newlines@^1.0.0:
dependencies:
glob "^7.1.2"
-tslib@^1.9.0:
- version "1.14.1"
- resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.14.1.tgz#cf2d38bdc34a134bcaf1091c41f6619e2f672d00"
- integrity sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==
-
tty-browserify@0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/tty-browserify/-/tty-browserify-0.0.0.tgz#a157ba402da24e9bf957f9aa69d524eed42901a6"
@@ -7782,10 +7928,10 @@ tweetnacl@^0.14.3, tweetnacl@~0.14.0:
resolved "https://registry.yarnpkg.com/tweetnacl/-/tweetnacl-0.14.5.tgz#5ae68177f192d4456269d108afa93ff8743f4f64"
integrity sha1-WuaBd/GS1EViadEIr6k/+HQ/T2Q=
-type-fest@^0.11.0:
- version "0.11.0"
- resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.11.0.tgz#97abf0872310fed88a5c466b25681576145e33f1"
- integrity sha512-OdjXJxnCN1AvyLSzeKIgXTXxV+99ZuXl3Hpo9XpJAv9MBcHrrJOQ5kV7ypXOuQie+AmWG25hLbiKdwYTifzcfQ==
+type-fest@^0.21.3:
+ version "0.21.3"
+ resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.21.3.tgz#d260a24b0198436e133fa26a524a6d65fa3b2e37"
+ integrity sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w==
type-fest@^0.8.1:
version "0.8.1"
@@ -7825,28 +7971,38 @@ uglify-js@3.4.x:
commander "~2.19.0"
source-map "~0.6.1"
-unicode-canonical-property-names-ecmascript@^1.0.4:
- version "1.0.4"
- resolved "https://registry.yarnpkg.com/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-1.0.4.tgz#2619800c4c825800efdd8343af7dd9933cbe2818"
- integrity sha512-jDrNnXWHd4oHiTZnx/ZG7gtUTVp+gCcTTKr8L0HjlwphROEW3+Him+IpvC+xcJEFegapiMZyZe02CyuOnRmbnQ==
+unbox-primitive@^1.0.1:
+ version "1.0.1"
+ resolved "https://registry.yarnpkg.com/unbox-primitive/-/unbox-primitive-1.0.1.tgz#085e215625ec3162574dc8859abee78a59b14471"
+ integrity sha512-tZU/3NqK3dA5gpE1KtyiJUrEB0lxnGkMFHptJ7q6ewdZ8s12QrODwNbhIJStmJkd1QDXa1NRA8aF2A1zk/Ypyw==
+ dependencies:
+ function-bind "^1.1.1"
+ has-bigints "^1.0.1"
+ has-symbols "^1.0.2"
+ which-boxed-primitive "^1.0.2"
-unicode-match-property-ecmascript@^1.0.4:
- version "1.0.4"
- resolved "https://registry.yarnpkg.com/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-1.0.4.tgz#8ed2a32569961bce9227d09cd3ffbb8fed5f020c"
- integrity sha512-L4Qoh15vTfntsn4P1zqnHulG0LdXgjSO035fEpdtp6YxXhMT51Q6vgM5lYdG/5X3MjS+k/Y9Xw4SFCY9IkR0rg==
+unicode-canonical-property-names-ecmascript@^2.0.0:
+ version "2.0.0"
+ resolved "https://registry.yarnpkg.com/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-2.0.0.tgz#301acdc525631670d39f6146e0e77ff6bbdebddc"
+ integrity sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ==
+
+unicode-match-property-ecmascript@^2.0.0:
+ version "2.0.0"
+ resolved "https://registry.yarnpkg.com/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-2.0.0.tgz#54fd16e0ecb167cf04cf1f756bdcc92eba7976c3"
+ integrity sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==
dependencies:
- unicode-canonical-property-names-ecmascript "^1.0.4"
- unicode-property-aliases-ecmascript "^1.0.4"
+ unicode-canonical-property-names-ecmascript "^2.0.0"
+ unicode-property-aliases-ecmascript "^2.0.0"
-unicode-match-property-value-ecmascript@^1.2.0:
- version "1.2.0"
- resolved "https://registry.yarnpkg.com/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-1.2.0.tgz#0d91f600eeeb3096aa962b1d6fc88876e64ea531"
- integrity sha512-wjuQHGQVofmSJv1uVISKLE5zO2rNGzM/KCYZch/QQvez7C1hUhBIuZ701fYXExuufJFMPhv2SyL8CyoIfMLbIQ==
+unicode-match-property-value-ecmascript@^2.0.0:
+ version "2.0.0"
+ resolved "https://registry.yarnpkg.com/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-2.0.0.tgz#1a01aa57247c14c568b89775a54938788189a714"
+ integrity sha512-7Yhkc0Ye+t4PNYzOGKedDhXbYIBe1XEQYQxOPyhcXNMJ0WCABqqj6ckydd6pWRZTHV4GuCPKdBAUiMc60tsKVw==
-unicode-property-aliases-ecmascript@^1.0.4:
- version "1.1.0"
- resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-1.1.0.tgz#dd57a99f6207bedff4628abefb94c50db941c8f4"
- integrity sha512-PqSoPh/pWetQ2phoj5RLiaqIk4kCNwoV3CI+LfGmWLKI3rE3kl1h59XpX2BjgDrmbxD9ARtQobPGU1SguCYuQg==
+unicode-property-aliases-ecmascript@^2.0.0:
+ version "2.0.0"
+ resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.0.0.tgz#0a36cb9a585c4f6abd51ad1deddb285c165297c8"
+ integrity sha512-5Zfuy9q/DFr4tfO7ZPeVXb1aPoeQSdeFMLpYuFebehDAhbuevLs5yxSZmIFN1tP5F9Wl4IpJrYojg85/zgyZHQ==
union-value@^1.0.0:
version "1.0.1"
@@ -7969,10 +8125,10 @@ url-parse-lax@^3.0.0:
dependencies:
prepend-http "^2.0.0"
-url-parse@^1.4.3, url-parse@^1.4.7:
- version "1.4.7"
- resolved "https://registry.yarnpkg.com/url-parse/-/url-parse-1.4.7.tgz#a8a83535e8c00a316e403a5db4ac1b9b853ae278"
- integrity sha512-d3uaVyzDB9tQoSXFvuSUNFibTd9zxd2bkVrDRvF5TmvWWQwqE4lgYJ5m+x1DbecWkw+LK4RNl2CU1hHuOKPVlg==
+url-parse@^1.4.3, url-parse@^1.5.3:
+ version "1.5.3"
+ resolved "https://registry.yarnpkg.com/url-parse/-/url-parse-1.5.3.tgz#71c1303d38fb6639ade183c2992c8cc0686df862"
+ integrity sha512-IIORyIQD9rvj0A4CLWsHkBBJuNqWpFQe224b6j9t/ABmquIS0qDU2pY6kl6AuOrL5OkCXHMCFNe1jBcuAggjvQ==
dependencies:
querystringify "^2.1.1"
requires-port "^1.0.0"
@@ -8080,9 +8236,9 @@ vue-hot-reload-api@^2.3.0:
integrity sha512-BXq3jwIagosjgNVae6tkHzzIk6a8MHFtzAdwhnV5VlvPTFxDCvIttgSiHWjdGoTJvXtmRu5HacExfdarRcFhog==
vue-loader@^15.7.1:
- version "15.9.6"
- resolved "https://registry.yarnpkg.com/vue-loader/-/vue-loader-15.9.6.tgz#f4bb9ae20c3a8370af3ecf09b8126d38ffdb6b8b"
- integrity sha512-j0cqiLzwbeImIC6nVIby2o/ABAWhlppyL/m5oJ67R5MloP0hj/DtFgb0Zmq3J9CG7AJ+AXIvHVnJAPBvrLyuDg==
+ version "15.9.8"
+ resolved "https://registry.yarnpkg.com/vue-loader/-/vue-loader-15.9.8.tgz#4b0f602afaf66a996be1e534fb9609dc4ab10e61"
+ integrity sha512-GwSkxPrihfLR69/dSV3+5CdMQ0D+jXg8Ma1S4nQXKJAznYFX14vHdc/NetQc34Dw+rBbIJyP7JOuVb9Fhprvog==
dependencies:
"@vue/component-compiler-utils" "^3.1.0"
hash-sum "^1.0.2"
@@ -8091,14 +8247,14 @@ vue-loader@^15.7.1:
vue-style-loader "^4.1.0"
vue-router@^3.4.5:
- version "3.5.1"
- resolved "https://registry.yarnpkg.com/vue-router/-/vue-router-3.5.1.tgz#edf3cf4907952d1e0583e079237220c5ff6eb6c9"
- integrity sha512-RRQNLT8Mzr8z7eL4p7BtKvRaTSGdCbTy2+Mm5HTJvLGYSSeG9gDzNasJPP/yOYKLy+/cLG/ftrqq5fvkFwBJEw==
+ version "3.5.2"
+ resolved "https://registry.yarnpkg.com/vue-router/-/vue-router-3.5.2.tgz#5f55e3f251970e36c3e8d88a7cd2d67a350ade5c"
+ integrity sha512-807gn82hTnjCYGrnF3eNmIw/dk7/GE4B5h69BlyCK9KHASwSloD1Sjcn06zg9fVG4fYH2DrsNBZkpLtb25WtaQ==
vue-server-renderer@^2.6.10:
- version "2.6.12"
- resolved "https://registry.yarnpkg.com/vue-server-renderer/-/vue-server-renderer-2.6.12.tgz#a8cb9c49439ef205293cb41c35d0d2b0541653a5"
- integrity sha512-3LODaOsnQx7iMFTBLjki8xSyOxhCtbZ+nQie0wWY4iOVeEtTg1a3YQAjd82WvKxrWHHTshjvLb7OXMc2/dYuxw==
+ version "2.6.14"
+ resolved "https://registry.yarnpkg.com/vue-server-renderer/-/vue-server-renderer-2.6.14.tgz#c8bffff152df6b47b858818ef8d524d2fc351654"
+ integrity sha512-HifYRa/LW7cKywg9gd4ZtvtRuBlstQBao5ZCWlg40fyB4OPoGfEXAzxb0emSLv4pBDOHYx0UjpqvxpiQFEuoLA==
dependencies:
chalk "^1.1.3"
hash-sum "^1.0.2"
@@ -8110,17 +8266,17 @@ vue-server-renderer@^2.6.10:
source-map "0.5.6"
vue-style-loader@^4.1.0:
- version "4.1.2"
- resolved "https://registry.yarnpkg.com/vue-style-loader/-/vue-style-loader-4.1.2.tgz#dedf349806f25ceb4e64f3ad7c0a44fba735fcf8"
- integrity sha512-0ip8ge6Gzz/Bk0iHovU9XAUQaFt/G2B61bnWa2tCcqqdgfHs1lF9xXorFbE55Gmy92okFT+8bfmySuUOu13vxQ==
+ version "4.1.3"
+ resolved "https://registry.yarnpkg.com/vue-style-loader/-/vue-style-loader-4.1.3.tgz#6d55863a51fa757ab24e89d9371465072aa7bc35"
+ integrity sha512-sFuh0xfbtpRlKfm39ss/ikqs9AbKCoXZBpHeVZ8Tx650o0k0q/YCM7FRvigtxpACezfq6af+a7JeqVTWvncqDg==
dependencies:
hash-sum "^1.0.2"
loader-utils "^1.0.2"
vue-template-compiler@^2.6.10:
- version "2.6.12"
- resolved "https://registry.yarnpkg.com/vue-template-compiler/-/vue-template-compiler-2.6.12.tgz#947ed7196744c8a5285ebe1233fe960437fcc57e"
- integrity sha512-OzzZ52zS41YUbkCBfdXShQTe69j1gQDZ9HIX8miuC9C3rBCk9wIRjLiZZLrmX9V+Ftq/YEyv1JaVr5Y/hNtByg==
+ version "2.6.14"
+ resolved "https://registry.yarnpkg.com/vue-template-compiler/-/vue-template-compiler-2.6.14.tgz#a2f0e7d985670d42c9c9ee0d044fed7690f4f763"
+ integrity sha512-ODQS1SyMbjKoO1JBJZojSw6FE4qnh9rIpUZn2EUT86FKizx9uH5z6uXiIrm4/Nb/gwxTi/o17ZDEGWAXHvtC7g==
dependencies:
de-indent "^1.0.2"
he "^1.1.0"
@@ -8131,9 +8287,9 @@ vue-template-es2015-compiler@^1.9.0:
integrity sha512-4gDntzrifFnCEvyoO8PqyJDmguXgVPxKiIxrBKjIowvL9l+N66196+72XVYR8BBf1Uv1Fgt3bGevJ+sEmxfZzw==
vue@^2.6.10:
- version "2.6.12"
- resolved "https://registry.yarnpkg.com/vue/-/vue-2.6.12.tgz#f5ebd4fa6bd2869403e29a896aed4904456c9123"
- integrity sha512-uhmLFETqPPNyuLLbsKz6ioJ4q7AZHzD8ZVFNATNyICSZouqP2Sz0rotWQC8UNBF6VGSCs5abnKJoStA6JbCbfg==
+ version "2.6.14"
+ resolved "https://registry.yarnpkg.com/vue/-/vue-2.6.14.tgz#e51aa5250250d569a3fbad3a8a5a687d6036e235"
+ integrity sha512-x2284lgYvjOMj3Za7kqzRcUSxBboHqtgRE2zlos1qWaOye5yUmHn42LB1250NJBLRwEcdrB0JRwyPTEPhfQjiQ==
vuepress-html-webpack-plugin@^3.2.0:
version "3.2.0"
@@ -8160,7 +8316,7 @@ vuepress-plugin-code-copy@^1.0.6:
resolved "https://registry.yarnpkg.com/vuepress-plugin-code-copy/-/vuepress-plugin-code-copy-1.0.6.tgz#6431dab764b48b5b203e4936d98b1943651ce4ad"
integrity sha512-FiqwMtlb4rEsOI56O6sSkekcd3SlESxbkR2IaTIQxsMOMoalKfW5R9WlR1Pjm10v6jmU661Ex8MR11k9IzrNUg==
-vuepress-plugin-container@^2.0.2:
+vuepress-plugin-container@^2.0.2, vuepress-plugin-container@^2.1.5:
version "2.1.5"
resolved "https://registry.yarnpkg.com/vuepress-plugin-container/-/vuepress-plugin-container-2.1.5.tgz#37fff05662fedbd63ffd3a5463b2592c7a7f3133"
integrity sha512-TQrDX/v+WHOihj3jpilVnjXu9RcTm6m8tzljNJwYhxnJUW0WWQ0hFLcDTqTBwgKIFdEiSxVOmYE+bJX/sq46MA==
@@ -8199,13 +8355,13 @@ vuepress-plugin-smooth-scroll@^0.0.3:
dependencies:
smoothscroll-polyfill "^0.4.3"
-vuepress@^1.7.1:
- version "1.8.0"
- resolved "https://registry.yarnpkg.com/vuepress/-/vuepress-1.8.0.tgz#0139d466b33fbfdb628abb76d555368b85cf9772"
- integrity sha512-YvNitvoEc+JSJRv1W+IoRnvOTFyTWyUMuGuF2kTIbiSwIHb1hNinc3lqNSeBQJy7IBqyEzK5fnTq1mlynh4gwA==
+vuepress@^1.8.2:
+ version "1.8.2"
+ resolved "https://registry.yarnpkg.com/vuepress/-/vuepress-1.8.2.tgz#97e8bf979630611fc7b621fc4cc35b798ee5e847"
+ integrity sha512-BU1lUDwsA3ghf7a9ga4dsf0iTc++Z/l7BR1kUagHWVBHw7HNRgRDfAZBDDQXhllMILVToIxaTifpne9mSi94OA==
dependencies:
- "@vuepress/core" "1.8.0"
- "@vuepress/theme-default" "1.8.0"
+ "@vuepress/core" "1.8.2"
+ "@vuepress/theme-default" "1.8.2"
cac "^6.5.6"
envinfo "^7.2.0"
opencollective-postinstall "^2.0.2"
@@ -8387,6 +8543,17 @@ when@~3.6.x:
resolved "https://registry.yarnpkg.com/when/-/when-3.6.4.tgz#473b517ec159e2b85005497a13983f095412e34e"
integrity sha1-RztRfsFZ4rhQBUl6E5g/CVQS404=
+which-boxed-primitive@^1.0.2:
+ version "1.0.2"
+ resolved "https://registry.yarnpkg.com/which-boxed-primitive/-/which-boxed-primitive-1.0.2.tgz#13757bc89b209b049fe5d86430e21cf40a89a8e6"
+ integrity sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==
+ dependencies:
+ is-bigint "^1.0.1"
+ is-boolean-object "^1.1.0"
+ is-number-object "^1.0.4"
+ is-string "^1.0.5"
+ is-symbol "^1.0.3"
+
which-module@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/which-module/-/which-module-2.0.0.tgz#d9ef07dce77b9902b8a3a8fa4b31c3e3f7e6e87a"
@@ -8445,9 +8612,9 @@ write-file-atomic@^3.0.0:
typedarray-to-buffer "^3.1.5"
ws@^6.2.1:
- version "6.2.1"
- resolved "https://registry.yarnpkg.com/ws/-/ws-6.2.1.tgz#442fdf0a47ed64f59b6a5d8ff130f4748ed524fb"
- integrity sha512-GIyAXC2cB7LjvpgMt9EKS2ldqr0MTrORaleiOno6TweZ6r3TKtoFQWay/2PceJ3RuBasOHzXNn5Lrw1X0bEjqA==
+ version "6.2.2"
+ resolved "https://registry.yarnpkg.com/ws/-/ws-6.2.2.tgz#dd5cdbd57a9979916097652d78f1cc5faea0c32e"
+ integrity sha512-zmhltoSR8u1cnDsD43TX59mzoMZsLKqUweyYBAIvTngR3shc0W6aOZylZmq/7hqyVxPdi+5Ud2QInblgyE72fw==
dependencies:
async-limiter "~1.0.0"
@@ -8462,9 +8629,9 @@ xtend@^4.0.0, xtend@~4.0.1:
integrity sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==
y18n@^4.0.0:
- version "4.0.1"
- resolved "https://registry.yarnpkg.com/y18n/-/y18n-4.0.1.tgz#8db2b83c31c5d75099bb890b23f3094891e247d4"
- integrity sha512-wNcy4NvjMYL8gogWWYAO7ZFWFfHcbdbE57tZO8e4cbpj8tfUcwrwqSl3ad8HxpYWCdXcJUCeKKZS62Av1affwQ==
+ version "4.0.3"
+ resolved "https://registry.yarnpkg.com/y18n/-/y18n-4.0.3.tgz#b5f259c82cd6e336921efd7bfd8bf560de9eeedf"
+ integrity sha512-JKhqTOwSrqNA1NY5lSztJ1GrBiUodLMmIZuLiDaMRJ+itFd+ABVE8XBjOvIWL+rSqNDC74LCSFmlb/U4UZ4hJQ==
yallist@^2.1.2:
version "2.1.2"
diff --git a/qsg-handson-part2-04-roles.png b/qsg-handson-part2-04-roles.png
deleted file mode 100644
index 2a43f7f21f..0000000000
Binary files a/qsg-handson-part2-04-roles.png and /dev/null differ