Updated articles based on feedback from DXP team

10/umbraco-cms/extending/packages/README.md

@@ -30,7 +30,7 @@ Packages provide a wide variety of functionality, and can often span multiple ca
 
 #### Schema Extensions
 
-A package that can be categorized as a Schema Extension will extend the default Umbraco Schema. Schema in this sense refers to things like Data Types, Property Editors, Document Types and Media Types. By extending Umbraco with packages such as [Our.Umbraco.GMaps](https://marketplace.umbraco.com/package/our.umbraco.gmaps) editors are given greater capabilities when they are populating their content pages.
+A package that can be categorized as a Schema Extension will extend the default Umbraco Schema. Schema in this sense refers to things like Data Types, Property Editors, Document Types and Media Types. By extending Umbraco with packages such as [Umbraco Commerce](https://docs.umbraco.com/umbraco-commerce) editors are given greater capabilities when they are populating their content pages.
 
 #### Management Extensions
 

12/umbraco-cms/extending/packages/README.md

@@ -44,7 +44,7 @@ Content apps are almost like dashboards for content nodes that are intended to d
 
 #### Integration extensions
 
-This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [UCommerce](https://marketplace.umbraco.com/package/ucommerce.umbraco8), that includes an entire webshop module for Umbraco.
+This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [Umbraco Commerce](https://docs.umbraco.com/umbraco-commerce), that includes an entire webshop module for Umbraco.
 
 ## [Types of Packages](types-of-packages.md)
 

12/umbraco-cms/extending/packages/installing-and-uninstalling-packages.md

@@ -21,10 +21,6 @@ In the Umbraco Backoffice, you will find a **Packages** section that displays th
 
 ![Backoffice - Packages section](images/backoffice-packages-section.png)
 
-{% hint style="warning" %}
-For Umbraco CMS version 8 and earlier versions, the Packages section displays the [Packages site on Our](https://our.umbraco.com/packages/).
-{% endhint %}
-
 {% tabs %}
 {% tab title="NuGet package" %}
 Navigating to a specific package in the section will present you with an overview of the package, as well as an install snippet for NuGet CLI.

13/umbraco-cms/extending/packages/README.md

@@ -44,7 +44,7 @@ Content apps are almost like dashboards for content nodes that are intended to d
 
 #### Integration extensions
 
-This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [UCommerce](https://marketplace.umbraco.com/package/ucommerce.umbraco8), that includes an entire webshop module for Umbraco.
+This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [Umbraco Commerce](https://docs.umbraco.com/umbraco-commerce), that includes an entire webshop module for Umbraco.
 
 ## [Types of Packages](types-of-packages.md)
 

13/umbraco-cms/extending/packages/installing-and-uninstalling-packages.md

@@ -21,10 +21,6 @@ In the Umbraco Backoffice, you will find a **Packages** section that displays th
 
 ![Backoffice - Packages section](images/backoffice-packages-section.png)
 
-{% hint style="warning" %}
-For Umbraco CMS version 8 and earlier versions, the Packages section displays the [Packages site on Our](https://our.umbraco.com/packages/).
-{% endhint %}
-
 {% tabs %}
 {% tab title="NuGet package" %}
 Navigating to a specific package in the section will present you with an overview of the package, as well as an install snippet for NuGet CLI.

14/umbraco-cms/extending/packages/README.md

@@ -47,7 +47,7 @@ Content apps are almost like dashboards for content nodes that are intended to d
 
 #### Integration extensions
 
-This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [UCommerce](https://marketplace.umbraco.com/package/ucommerce.umbraco8), that includes an entire webshop module for Umbraco.
+This type of package can be a lot of things, and can include a number of the other package types. They are generally integrating a larger system into Umbraco. A good example could be an e-commerce package such as [Umbraco Commerce](https://docs.umbraco.com/umbraco-commerce), that includes an entire webshop module for Umbraco.
 
 ## [Types of Packages](types-of-packages.md)
 

14/umbraco-cms/extending/packages/good-practice-and-defaults.md

@@ -8,7 +8,9 @@ This document provides guides and notes on package development. It includes good
 
 ## Backoffice assets (JS/CSS/HTML)
 
-To extend the Umbraco backoffice, a package can provide files such as a `package.manifest` and AngularJS views/controllers that should be stored within the `App_Plugins` folder. It's recommended to put all files in a subfolder with a unique name, preferably using the package name, like `App_Plugins\MyPackage`.
+To extend the Umbraco backoffice, a package can provide files such as `umbraco-package.json` and TypeScript/JavaScript files that should be stored within the `App_Plugins` folder. It's recommended to put all files in a subfolder with a unique name, preferably using the package name, like `App_Plugins\MyPackage`.
+
+For more information on how to extend the Umbraco backoffice, have a look at the [customizing the backoffice documentation](../customize-backoffice/README.md)
 
 Files in the `App_Plugins` folder will be publicly available on the website even though they are not in the `wwwroot` folder. You should not store sensitive information in the `App_Plugins` folder.
 

14/umbraco-cms/extending/packages/installing-and-uninstalling-packages.md

@@ -21,10 +21,6 @@ In the Umbraco Backoffice, you will find a **Packages** section that displays th
 
 ![Backoffice - Packages section](images/backoffice-packages-section.png)
 
-{% hint style="warning" %}
-For Umbraco CMS version 8 and earlier versions, the Packages section displays the [Packages site on Our](https://our.umbraco.com/packages/).
-{% endhint %}
-
 {% tabs %}
 {% tab title="NuGet package" %}
 Navigating to a specific package in the section will present you with an overview of the package, as well as an install snippet for NuGet CLI.

14/umbraco-cms/extending/packages/language-files-for-packages.md

@@ -2,39 +2,29 @@
 description: "Information on how to use language files to make your Umbraco package UI support multiple languages"
 ---
 
-# Language file for packages
-
-Umbraco Core includes language files, but package authors must provide their own for multi-lingual UI.
-
-## Including new language keys
-
-For each language your package supports, you include an .xml file in the same format as the core language files, named with its language code. The language files must be located in a `Lang` folder inside your package folder in `App_Plugins`. If your package assets are in `/App_Plugins/mypackage` all language files must be placed in the following locations:
-
-- English keys: `/App_Plugins/mypackage/Lang/en-US.xml`
-- Danish keys: `/App_Plugins/mypackage/Lang/da-DK.xml`
-
-{% hint style="info" %}
-The `App_Plugins` version of the `Lang` directory is case sensitive on Linux systems, so make sure that it start with a capital `L`.
-{% endhint %}
-
-## Language file format
-
-Each language file can include one or more area. Each area contains a collection of language keys with the translation.
-
-For reference on the language file format see the core [language files on GitHub](https://github.com/umbraco/Umbraco-CMS/tree/v9/dev/src/Umbraco.Web.UI/umbraco/config/lang)
-
-### Sample structure
-
-```xml
-<?xml version="1.0" encoding="utf-8" standalone="yes"?>
-<language alias="da" intName="Danish" localName="dansk" lcid="6" culture="da-DK">
-    <creator>
-        <name>The Umbraco community</name>
-        <link>http://mydomain.com</link>
-    </creator>
-    <area alias="dialog">
-        <key alias="myKey">Min nøgle</key>
-        <key alias="otherKey">Min anden nøgle</key>
-    </area>
-</language>
+# Languages for packages
+
+If you want your package to be available in different languages, you can use the existing localizations from Umbraco or register your own localizations. The localizations are written as a key-value pair pattern.
+
+To register localizations to a language, you must add a new manifest to the Extension API. The manifest can be added through the `umbraco-package.json` file like this:
+
+{% code title="umbraco-package.json" lineNumbers="true" %}
+
+```json
+{
+  ...
+  "name": "MyPackage",
+  "extensions": [
+    {
+      "type": "localization",
+      "alias": "MyPackage.Localize.EnUS",
+      "name": "English (United States)",
+      "meta": {
+        "culture": "en-us"
+      },
+      "js": "/App_Plugins/MyPackage/Localization/en-us.js"
+    }
+  ]
+}
 ```
+Read the [UI Localization documentation](../language-files/ui-localization.md) to learn in-depth on how you can use languages in your packages and Umbraco in general.