IIS Issue 516

content/features/content-management/index.md

@@ -11,4 +11,8 @@ Following is an list of content management features within **DNN Platform**.
 ## [Sites](xref:sites)
 Learn the features of sites within **DNN Platform**.
 
+## [Localization](xref:localization)
+Learn about localization within **DNN Platform**.
+
+
 Please click the **Improve this Doc** button above to help us improve this page.

content/features/content-management/localization/index.md

@@ -0,0 +1,54 @@
+---
+uid: localization
+locale: en
+title: About Localization
+dnnversion: 09.02.00
+---
+
+# About Localization
+
+DNN comes with a built in framework for localizing your content, The overall process involves you designating a default language and then adding additional languages. For each additional language you can perform translation tasks like creating new resources and marking pages for translation.
+
+### Setting Up Your Site for Localization
+
+Step 1: Add a Language of Your Choosing
+  * You can access the add language dialog under `Settings` - `Site Settings` - `Languages`. Click the `+ Add New Language` button.
+
+![Step1-add-language](/images/Step1-add-language.jpg)
+
+Step 2: Verify the New Language is Enabled 
+  * This is marked with a check mark. If not, use the cog icon to enable the language.
+
+![Step2-enable-language](/images/Step2-enable-language.jpg)
+
+Step 3: Enable Content Localization
+  * It is recommended to flip the radio button `Make All Pages Translatable` on because this will make unique copies of each page that represent the translation of that page.
+
+> [!Warning]
+> The default language can not be changed afterwards.
+
+![Step3-enable-content-localization](/images/Step3-enable-content-localization.jpg)
+
+
+  * You can now visit your pages and start localizing content. As an admin, you'll find the language switcher most of the time (depending on the theme) at the right top of your screen.
+
+Step 4: Translate a Page
+  * Now that you have translatable versions of each page, a new `Localization` tab has been added under `Content` - `Pages` for each page.
+  * Once you have finished translating the page via the language specific version, mark your translated page as 'translated' and give it a go (if you desire) to be published.
+
+
+![Step4-localize-content](/images/Step4-localize-content.jpg)
+
+ Step 5: Activate Your Language
+  * The last step is to activate your language. Go to `Settings` - `Site Settings` - `Languages` and click the icon that stands for multi language.
+
+
+![Step5a-activate-content](/images/Step5a-activate-content.jpg)
+
+  * In the new window, flip the `Activate Pages In This Language` on to activate your pages.
+
+![Step5b-activate-content](/images/Step5b-activate-content.jpg)
+
+* This last step allows you as a content manager to prepare all the work for a new language and publish after everyone involved has approved. 
+
+If this still does not show your translated content, verify if you are using a module that needs language activation as well.

content/features/toc.md

@@ -6,6 +6,7 @@
 # [Content Management](xref:content-management)
 ## [Sites](xref:sites)
 ### [Import/Export](xref:import-export)
+## [Localization](xref:localization)
 # [Extensibility](xref:extensibility)
 ## [Event System](xref:event-system)
 ## [Extensions](xref:extensions)

content/tutorials/server/setup/set-up-iis/index.md

@@ -37,7 +37,7 @@ links: ["[DNN Wiki: Setting up Your Module Development Environment](https://www.
 
 
 
-        ![IIS options to turn on](/images/scr-InstallIIS-6.png)
+        ![IISUpdated](/images/IISUpdated.png)
 
 
 
@@ -99,4 +99,8 @@ You can create a new website or set up an existing one for use with DNN. Choose
 
     The account **IIS AppPool\\AppPoolName** is automatically created by IIS.
 
+    > [!Note]
+    > For security best practices, you should use either an App Pool Identity or an individual machine/AD account (often used by Control Panels) - not a Network Service.
+    > An **App Pool** represents a way to separate web applications from one another and prevents them from harming each other or their environments. Thus, you should generally only assign one worker process to one App Pool.
+
     See [Set Up DNN Folder and the User Account](xref:set-up-dnn-folder).