DOC Remove references to old Addons website (#389)

en/00_Getting_Started/00_Server_Requirements.md

@@ -27,10 +27,10 @@ You also need to install [Composer 2](https://getcomposer.org/).
 ## Database
 
 * MySQL >=5.6 (built-in, [commercially supported](/project_governance/supported_modules/))
-* PostgreSQL ([third party module](https://addons.silverstripe.org/add-ons/silverstripe/postgresql), community
+* PostgreSQL ([third party module](https://github.com/silverstripe/silverstripe-postgresql), community
   supported)
-* SQL Server ([third party module](https://addons.silverstripe.org/add-ons/silverstripe/mssql), community supported)
-* SQLite ([third party module](https://addons.silverstripe.org/add-ons/silverstripe/sqlite3), community supported)
+* SQL Server ([third party module](https://github.com/silverstripe/silverstripe-mssql), community supported)
+* SQLite ([third party module](https://github.com/silverstripe/silverstripe-sqlite3), community supported)
 
 ### Default MySQL Collation
 
@@ -239,7 +239,7 @@ instances, this can become a capacity issue over time - see
 ### Error pages
 
 The default installation
-includes [silverstripe/errorpage](https://addons.silverstripe.org/add-ons/silverstripe/errorpage), which generates
+includes [silverstripe/errorpage](https://github.com/silverstripe/silverstripe-errorpage/), which generates
 static error pages that bypass PHP execution when those pages are published in the CMS. Once published, the static files
 are located in `public/assets/error-404.html` and `public/assets/error-500.html`. The default `public/.htaccess` file is
 configured to have Apache serve those pages based on their HTTP status code.

en/00_Getting_Started/02_Composer.md

@@ -72,7 +72,7 @@ see [Using development versions](#using-development-versions).
 
 Composer isn't only used to download Silverstripe CMS, it is also used to manage all Silverstripe CMS modules
 and any other PHP dependencies you may have.
-You can find thousands of modules on [https://addons.silverstripe.org](https://addons.silverstripe.org).
+You can find thousands of Silverstripe CMS modules on [Packagist](https://packagist.org/search/?type=silverstripe-vendormodule).
 Installing a module can be done with [the require command](https://getcomposer.org/doc/03-cli.md#require-r):
 
 ```bash

en/02_Developer_Guides/01_Templates/06_Themes.md

@@ -11,7 +11,7 @@ application can provide multiple unique themes (i.e.a mobile theme).
 
 ## Downloading
 
-Head to the [themes section of the addons site](https://addons.silverstripe.org/add-ons?search=&type=theme) to check out the range of themes the 
+Head to the [Packagist](https://packagist.org/search/?type=silverstripe-theme) to check out the range of themes the 
 community has built. Themes are published and downloaded using Composer,
 just like any other [Silverstripe module](/developer_guides/extending/modules).
 
@@ -97,9 +97,9 @@ A `theme` within Silverstripe CMS is simply a collection of templates and other
 
 To define extra themes simply add extra entries to the `SilverStripe\View\SSViewer.themes` configuration array. You will probably always want to ensure that you include `'$default'` in your list of themes to ensure that the base templates are used when required.
 
-## Submitting your theme to addons
+## Submitting your theme
 
-If you want to submit your theme to the Silverstripe CMS addons directory then check:
+If you want to submit your theme to Packagist for others to use, then check:
 
 * You should ensure your templates are well structured, modular and commented so it's easy for other people to customise 
 * Templates should not contain text inside images and all images provided must be open source and not break any 
@@ -109,11 +109,11 @@ copyright or license laws. This includes any icons your template uses.
 
 Once you've created your module and set up your Composer configuration, create a new repository and push your theme to a Git host such as [GitHub.com](https://github.com). 
 
-The final step is to [submit your theme to Packagist](https://packagist.org/about#how-to-submit-packages) (the central Composer package repository). Once your theme is listed in Packagist, and has `"type": "silverstripe-theme"` in its configuration, it will automatically be pulled into our addons listing site.
+The final step is to [submit your theme to Packagist](https://packagist.org/about#how-to-submit-packages) (the central Composer package repository).
 
 ## Links
 
- * [Themes Listing on silverstripe.org](https://addons.silverstripe.org/add-ons?search=&type=theme)
+ * [Silverstripe CMS themes on Packagist](https://packagist.org/search/?type=silverstripe-theme)
 
 ## Related Lessons
 * [Creating your first project](https://www.silverstripe.org/learn/lessons/v4/creating-your-first-project)

en/02_Developer_Guides/05_Extending/00_Modules.md

@@ -21,7 +21,6 @@ within your module when you next flush your cache.
 
 ## Finding Modules
 
-* [Official module list on silverstripe.org](https://addons.silverstripe.org/)
 * [Packagist.org "silverstripe" tag](https://packagist.org/search/?tags=silverstripe)
 * [GitHub.com "silverstripe" search](https://github.com/search?q=silverstripe)
 

en/02_Developer_Guides/05_Extending/How_Tos/01_Publish_a_Module.md

@@ -60,9 +60,7 @@ For more information about what your `composer.json` file should include, consul
 
 
 Once your module is published online with a service like github.com or bitbucket.com, submit the repository to 
-[Packagist](https://packagist.org/) to have the module accessible to developers. It'll automatically get picked
-up by [addons.silverstripe.org](https://addons.silverstripe.org/) website due to the `silverstripe-vendormodule`
-type in the file.
+[Packagist](https://packagist.org/) to have the module accessible to developers.
 
 Note that Silverstripe CMS modules have the following distinct characteristics: