Merge pull request #104 from humanmade/backport-103-to-v3-branch

[Backport v3-branch] Add pre-approved plugins doc

other-docs/getting-started/third-party-plugins.md

@@ -56,3 +56,8 @@ composer require wpackagist-plugin/akismet
 Third-party plugins should be placed inside the `content/plugins/` directory. Each plugin should be contained in its own directory within the plugins directory, with one file containing a [comment header](https://developer.wordpress.org/plugins/plugin-basics/#getting-started).
 
 Generally speaking, we recommend using Git submodules if you're installing modules manually. This reduces the amount of code necessary in your repository, and makes managing updates much easier.
+
+
+## Pre-Approved Plugins
+
+We maintain a list of trusted 3rd party plugins that you can refer to for recommendations, [read more about our pre-approved plugins here](docs://guides/pre-approved-plugins.md).

other-docs/guides/pre-approved-plugins.md

@@ -0,0 +1,11 @@
+# Pre-Approved Plugins
+
+There is a wealth of 3rd party plugins that add complex features to Altis from events management to ecommerce.
+
+Typically all 3rd party code should be reviewed and approved by a software engineer on your team before it is deployed to ensure that your application running on Altis stays fast and secure. [You can read more about how to add 3rd party plugins to your application here](docs://getting-started/third-party-plugins.md).
+
+To help reduce the overhead for delivery teams we keep a list of trusted plugins produced and maintained by industry leaders that you can refer to. These plugins do not require an in-depth review prior to installing.
+
+[You can view the list of all pre-approved plugins here](https://www.altis-dxp.com/resources/pre-approved-plugins/).
+
+**Note:** Pre-approved plugins should only be viewed as recommendations and are not directly supported by Altis.