Production hotfix (sidebar) + various updates ahead of 4.4.4

CODE_OF_CONDUCT.md

@@ -2,45 +2,82 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment include:
+Examples of behavior that contributes to a positive environment for our community include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
 
-Examples of unacceptable behavior by participants include:
+Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
-## Our Responsibilities
+## Enforcement Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hi@strapi.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at hi@strapi.io. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

docs/.vuepress/config-backup.js

@@ -351,6 +351,7 @@ const sidebar = {
         },
         ['/developer-docs/latest/developer-resources/cli/CLI', 'Command Line Interface'],
         ['/developer-docs/latest/developer-resources/error-handling.md', 'Error handling'],
+        ['/developer-docs/latest/developer-resources/database-migrations.md', 'Database migrations'],
         {
           title: 'Integrations',
           path: '/developer-docs/latest/developer-resources/content-api/integrations.html',

docs/.vuepress/config/sidebar-developer.js

@@ -316,6 +316,7 @@ const developer = [
       },
       ['/developer-docs/latest/developer-resources/cli/CLI', 'Command Line Interface'],
       ['/developer-docs/latest/developer-resources/error-handling.md', 'Error handling'],
+      ['/developer-docs/latest/developer-resources/database-migrations.md', 'Database migrations'],
       {
         title: 'Integrations',
         path: '/developer-docs/latest/developer-resources/content-api/integrations.html',

docs/.vuepress/theme/components/Sidebar.vue

@@ -59,7 +59,7 @@ export default {
   a
     display inline-block
   .nav-links
-    position: absolute
+    position: relative
     left: 0
     top: 0
     display none

docs/developer-docs/latest/developer-resources/database-migrations.md

@@ -0,0 +1,73 @@
+---
+title: Database migrations - Strapi Developer Docs
+description: Strapi database migrations are ways to modify the database
+canonicalUrl: https://docs.strapi.io/developer-docs/latest/development/backend-customization/database-migrations.html
+---
+
+# Database migrations
+
+Database migrations exist to run one-time queries against the database, typically to modify the tables structure or the data when upgrading the Strapi application. These migrations are run automatically when the application starts and are executed before the automated schema migrations that Strapi also performs on boot.
+
+::: callout 🚧  Experimental feature
+Database migrations are experimental. This feature is still a work in progress and will continue to be updated and improved. In the meantime, feel free to ask for help on the [forum](https://forum.strapi.io/) or on the community [Discord](https://discord.strapi.io).
+:::
+
+## Understanding database migration files
+
+Migrations are run using JavaScript migration files stored in `./database/migrations`.
+
+Strapi automatically detects migration files and run them once at the next startup in alphabetical order. Every new file is executed once. Migrations are run before the database tables are synced with the content-types schemas.
+
+::: warning
+Currently Strapi does not support down migrations. This means that if you need to revert a migration, you will have to do it manually. It is planned to implement down migrations in the future but no timeline is currently available.
+:::
+
+Migration files should export the function `up()`, which is used when upgrading (e.g. adding a new table `my_new_table`).
+
+The `up()` function runs in a database transaction which means if a query fails during the migration, the whole migration is cancelled, and no changes are applied to the database. If another transaction is created within the migration function, it will act as a nested transaction.
+
+::: note
+There is no CLI to manually execute the database migrations.
+:::
+
+## Creating a migration file
+
+To create a migration file:
+
+1. In the `./database/migrations` folder, create a new file named after the date and the name of the migration (e.g. `2022.05.10T00.00.00.name-of-my-migration.js`). Make sure that the file name follows this naming pattern, because the alphabetical order of the files defines the order in which the migrations have to run.
+
+2. Copy and paste the following template in the previously created file:
+
+```jsx
+'use strict'
+
+async function up(knex) {}
+
+module.exports = { up };
+```
+
+3. Fill in the template by adding actual migration code inside the `up()` function.
+`up()` receives a [Knex instance](https://knexjs.org/), already in a transaction state, that can be used to run the database queries.
+
+::: details Example of migration file
+
+```jsx
+// path: ./database/migrations/2022.05.10T00.00.00.name-of-my-migration.js
+
+module.exports = {
+  async up(knex) {
+    // You have full access to the Knex.js API with an already initialized connection to the database
+
+    // EXAMPLE: renaming a table
+    await knex.schema.renameTable('oldName', 'newName');
+
+    // EXAMPLE: renaming a column
+    await knex.schema.table('someTable', table => {
+      table.renameColumn('oldName', 'newName');
+    });
+
+    // EXAMPLE: updating data
+    await knex.from('someTable').update({ columnName: 'newValue' }).where({ columnName: 'oldValue' });
+  },
+};
+```

docs/developer-docs/latest/development/backend-customization/services.md

@@ -396,5 +396,3 @@ strapi.service('plugin::pluginName.serviceName');
 ::: tip
 To list all the available services, run `yarn strapi services:list`.
 :::
-
-:::

docs/developer-docs/latest/getting-started/troubleshooting.md

@@ -49,7 +49,7 @@ We are evaluating if we will natively add support for this in the future. We wil
 
 ## 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.
+If you used `--quickstart` to create your Strapi project, by default this uses the SQLite database. PaaS systems (Heroku, DigitalOcean Apps, Google App Engine, etc.) 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. For file uploads, you will need to use one of the 3rd party providers such as Cloudinary or AWS S3.
 

docs/developer-docs/latest/setup-deployment-guides/deployment.md

@@ -11,7 +11,7 @@ Strapi provides many deployment options for your project or application. Your St
 The following documentation covers how to develop locally with Strapi and deploy Strapi with several common hosting options.
 
 ::: callout ☁️ Strapi Cloud
-Don't want to deploy Strapi by yourself? <a href="https://strapi.io/cloud" target="_blank" id="deployment-section-cloud-link">Join the cloud waitlist</a> to soon get access to a platform to easily deploy and host your project.
+Don't want to deploy Strapi by yourself? <a href="https://strp.cc/3rywrsu" target="_blank" id="deployment-section-cloud-link">Join the cloud waitlist</a> to soon get access to a platform to easily deploy and host your project.
 :::
 
 ::: strapi Community Guides

docs/developer-docs/latest/setup-deployment-guides/installation/cli.md

@@ -14,12 +14,12 @@ Strapi CLI (Command Line Interface) installation scripts are the fastest way to
 
 A database is also required for any Strapi project. Strapi currently supports the following databases:
 
-| Database   | Minimum version |
-| ---------- | --------------- |
-| SQLite     | 3               |
-| PostgreSQL | 10              |
-| MySQL      | 5.7.8           |
-| MariaDB    | 10.2.7          |
+| Database   | Minimum | Recommended |
+|------------|---------|-------------|
+| MySQL      | 5.7.8   | 8.0         |
+| MariaDB    | 10.3    | 10.6        |
+| PostgreSQL | 11.0    | 14.0        |
+| SQLite     | 3       | 3           |
 
 ::: caution
 Strapi v4 does not support MongoDB.

docs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "strapi-docs",
-  "version": "4.4.0",
+  "version": "4.4.2",
   "main": "index.js",
   "scripts": {
     "dev": "yarn create:config-file && vuepress dev",