Merge pull request #2801 from MicrosoftDocs/portals-ICM186064810-1812284

Portals ICM 186064810 - 1812284

Author: tapanm-MSFT

powerapps-docs/maker/portals/configure/enable-multiple-language-support.md

@@ -6,7 +6,7 @@ manager: kvivek
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 11/04/2019
+ms.date: 04/30/2020
 ms.author: tapanm
 ms.reviewer:
 ---
@@ -18,7 +18,7 @@ Business is not confined to a single region or a language. A single portal can d
 
 To enable multiple languages for a portal, follow these steps:
 
-1. [Enable languages in a Common Data Service environment.](https://technet.microsoft.com/library/dn832148.aspx)  
+1. [Enable languages in a Common Data Service environment.](https://docs.microsoft.com/power-platform/admin/enable-languages)  
 2. Go to **Portals** > **Website** > **Websites**.
 3. Select the website to add language support to.
 4. In the **Supported Languages** section under the **General** tab, select **New Website Language**.

powerapps-docs/maker/portals/configure/websites.md

@@ -6,20 +6,20 @@ manager: kvivek
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 11/14/2019
+ms.date: 04/30/2020
 ms.author: tapanm
 ms.reviewer:
 ---
 
 # Manage websites
 
-A website is the core entity of portals application. A portal application selects a single Website record, and this determines what portal entities – [web pages](web-page.md), [web files](web-files.md), [web roles](create-web-roles.md), [content snippets](customize-content-snippets.md), etc. – are applicable to this application.
+A website is the core entity of portals application. A portal application selects a single Website record, and this determines what portal entities such as [web pages](web-page.md), [web files](web-files.md), [web roles](create-web-roles.md), and [content snippets](customize-content-snippets.md) are applicable to this application.
 
 With a website providing an application scope, multiple distinct portal applications can be connected to a single organization.
 
 > [!NOTE]
 > Determination of which website record a given portal application is bound to is usually by the website's name, specified in the configuration of the portal deployment.
-However, it is also possible to control this by URL path prefix (see the descriptions of Parent Website and Partial URL under [website attributes](#website-attributes)), or by ___domain, using website bindings.
+However, it is also possible to control this by ___domain name or website bindings.
 
 ## Manage websites
 
@@ -41,12 +41,15 @@ Websites are created when you create a new portal. However, advanced website man
 ### Website attributes
 
 |Name|Description|
-|-----|----------|
+|-|-|
 |Name|The descriptive name of the website. This field is required.|
+| Default Language | Default language for the selected portal. Before you change the default language, you must: <br> - [Add the language in Common Data Service environment](https://docs.microsoft.com/power-platform/admin/enable-languages). <br> - [Add the language in Supported Languages](enable-multiple-language-support.md) section for Websites record.
+| Owner | The owner contact record for the selected Websites record.
 |Primary Domain Name|The primary ___domain name of the portal to which this website record will be added.|
-|Parent Website|The parent website of the website. This field can generally be ignored, except in certain advanced portal configurations in which a single portal application is bound to one master website at the application root path, with one or more child websites available at specific sub-paths.|
-|Partial URL|The root URL path segment for all URLs generated for portal entities related to this website.<br>For example, if a portal application is deployed to be available at the root of the ___domain example.com, and this attribute has no value, a request to `http://example.com/` will render the Home web page of the application website (as the Home web page is required to have its Partial URL set to "/").<br>If this attribute is set to the value "my-website", the Home Web Page will instead have a URL of `http://example.com/my-website/`, and all pages in the website will have the same "/my-website/" path prefix.<br>In most portal configurations, this field can be ignored and left blank.<br>Partial URL values are used as URL path segments. As such, they should not contain illegal URL path characters, such as "?", "#", "!", "%". Since portal URLs are generated by joining together Partial URL values with slashes ("/"), they should also not generally contain slashes.<br>Recommended practice would be to restrict Partial URL values to letters, numbers, and hyphens or underscores. For example: "press-releases", "Users_Guide", "product1".|
-|||
+|Parent Website\*|The parent website of the website. This field can generally be ignored, except in certain advanced portal configurations in which a single portal application is bound to one master website at the application root path, with one or more child websites available at specific sub-paths. <br>\* Only for backward compatibility, not to be used for new or existing portals. |
+| Header and Footer Templates | The [Web templates for headers and footers](../liquid/store-content-web-templates.md#web-templates-as-page-templates) overriding global headers and footers.
+| Supported Languages | The [supported languages](enable-multiple-language-support.md) for the selected Websites record.
 
 ### See also
+
 [Website bindings](website-bindings.md)