Fix some 404s in v4 docs

docs/.vuepress/config.js

@@ -112,7 +112,7 @@ const sidebar = {
         },
         {
           title: 'Deployment',
-          path: '/developer-docs/latest/setup-deployment-guides/deployment',
+          path: '/developer-docs/latest/setup-deployment-guides/deployment.html',
           collapsable: true,
           initialOpenGroupIndex: -1, // make sure that no subgroup is open by default — if set to 0, 'Hosting Provider Guides' is expanded
           children: [
@@ -195,7 +195,7 @@ const sidebar = {
         {
           title: 'Back-end customization',
           collapsable: true,
-          path: '/developer-docs/latest/development/backend-customization',
+          path: '/developer-docs/latest/development/backend-customization.html',
           children: [
             ['/developer-docs/latest/development/backend-customization/routes.md', 'Routes'],
             ['/developer-docs/latest/development/backend-customization/policies.md', 'Policies'],
@@ -301,7 +301,7 @@ const sidebar = {
             {
               title: 'Entity Service API',
               path:
-                '/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api',
+                '/developer-docs/latest/developer-resources/database-apis-reference/entity-service-api.html',
               collapsable: true,
               children: [
                 [
@@ -816,21 +816,21 @@ module.exports = {
                 text: 'Setup & Deployment',
                 link: '/developer-docs/latest/setup-deployment-guides/installation.html',
               },
-              {
-                text: 'Plugins',
-                link: '/developer-docs/latest/plugins/plugins-intro.html',
-              },
               {
                 text: 'Development',
                 link: '/developer-docs/latest/development/backend-customization.html',
               },
               {
-                text: 'Update & Migration',
-                link: '/developer-docs/latest/update-migration-guides/update-version.html',
+                text: 'Developer Resources',
+                link: '/developer-docs/latest/developer-resources/database-apis-reference/rest-api.html',
               },
               {
-                text: 'Developer Resources',
-                link: '/developer-docs/latest/developer-resources/content-api/content-api.html',
+                text: 'Plugins',
+                link: '/developer-docs/latest/plugins/plugins-intro.html',
+              },
+              {
+                text: 'Update & Migration',
+                link: '/developer-docs/latest/update-migration-guides/update-version.html',
               },
             ],
           },
@@ -868,7 +868,7 @@ module.exports = {
         ],
       },
       {
-        text: 'v3 documentation',
+        text: 'v3 Documentation',
         link: 'https://docs-v3.strapi.io'
       },
       {

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

@@ -67,15 +67,15 @@ For all these reasons, and others, we think it'll be a mistake and might confuse
 
 ## How do I customize a plugin?
 
-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`.
+Strapi uses a system called [extensions](/developer-docs/latest/development/plugins-extension.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`.
 
 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.
 
 <!-- TODO: Confirm with Frontend team if this FAQ is accurate -->
 
 ## Can I add my own 3rd party auth provider?
 
-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.
+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/plugins/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.
 
@@ -95,7 +95,7 @@ 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](/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.
+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.md), [Caddy](/developer-docs/latest/setup-deployment-guides/deployment/optional-software/caddy-proxy.md), [HAProxy](/developer-docs/latest/setup-deployment-guides/deployment/optional-software/haproxy-proxy.md), 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?
 

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

@@ -33,7 +33,7 @@ The following installation guide covers the most basic installation option using
 - 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).
+For more information on available flags, see our [CLI documentation](/developer-docs/latest/developer-resources/cli/CLI.md).
 
 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)).
 :::