docs: Update of the Project Management section

src/content/docs/crowdin/project-management/creating-project.mdx

@@ -3,7 +3,7 @@ title: Creating a Project
 slug: creating-project
 ---
 
-import { Steps, Aside, CardGrid, Card } from '@astrojs/starlight/components';
+import { Steps, Aside, CardGrid, LinkCard, Card } from '@astrojs/starlight/components';
 import { Icon } from 'astro-icon/components';
 import { Image } from 'astro:assets';
 import createProject from '!/crowdin/project-management/create_project.png';
@@ -47,14 +47,15 @@ To create a project, follow these steps:
   3. Name your project.
   4. Customize your project address if needed.
   5. Select the preferred project visibility. You can choose between a **Public project** (visible to anyone) or a **Private project** (visible only to the invited project members). For a public project, you can enable **Moderated project joining** in your project **Settings** tab and restrict the possibility of translating for users until you confirm their join requests. Private projects can't be found via search engines and Crowdin search. <Image src={projectVisibility} alt="Project Visibility" />
-  6. Select **String-based project** if you want to manage your translatable content as individual strings. Otherwise, keep this option cleared to manage your translatable content as source files.
-  7. Select the source and target languages of your project. The source language is the language you’re translating from, and the target languages are the ones you’re translating into.
-     <Aside type="tip">You can select target languages manually or via **Pre-fill** by [copying target languages](/project-settings/languages#copying-target-languages) from another project under your account or using the top 30 languages. If you’d like to translate your project into target languages not officially supported, you can still add them as [custom languages](/project-settings/languages#adding-custom-languages).</Aside>
-  8. Click **Create Project**.
+  6. Select **String-based project** if you want to manage your translatable content as individual strings. Otherwise, keep this option cleared to manage your translatable content as source files. <Aside type="caution">The project address and type cannot be changed once the project is created.</Aside>
+  7. Select the source and target languages of your project. The source language is the language you’re translating from, and the target languages are the ones you’re translating into.     
+  8. Select the existing TM and glossary for your new project to be used as defaults. Alternatively, to create your new project with clean resources, leave the **Create new translation memory** and **Create new glossary** options selected.     
+  9. Click **Create Project**.
 </Steps>
 
-<Aside type="caution">
-  The project address and type cannot be changed once the project is created.
+<Aside type="tip" title="Tips">
+  - You can select target languages manually or via **Pre-fill** by [copying target languages](/project-settings/languages#copying-target-languages) from another project under your account or using the top 30 languages. If you’d like to translate your project into target languages not officially supported, you can still add them as [custom languages](/project-settings/languages#adding-custom-languages).
+  - After the project creation, you can change the [default TM](/project-settings/translation-memories/#changing-default-tm) and [default glossary](/project-settings/glossaries/#changing-default-glossary) in the project's **Settings**.
 </Aside>
 
 ## See Also

src/content/docs/crowdin/project-management/project-settings/general.mdx

@@ -19,6 +19,14 @@ In the **Name** section, you can change the project name and add a public descri
 
 <Image src={naming} alt="Naming" />
 
+## Project Language Page View
+
+This section allows you to choose how translators interact with the content on your project's language page.
+
+- **Show files only** &ndash; this option is useful if your project focuses on file-based translation without the need for visual context. It's an easy setup for projects where the text is self-explanatory or where screenshots aren't necessary.
+- **Show files and tagged screenshots** &ndash; displaying both files and tagged screenshots allows translators to reference visual context alongside the text. This option is useful for projects where the meaning of the text can be influenced by its visual environment, improving translation accuracy.
+- **Show screenshots only** &ndash; select this option if every string in your project is associated with a screenshot. By providing visual context for all text, you can significantly improve the quality of translations. This method is considered best practice, especially for projects with complex interfaces or where visual elements are crucial for understanding. However, it requires effort to maintain the accuracy and relevance of the screenshots.
+
 ## Branding
 
 In the **Branding** section, you can customize the appearance of your project by setting up a custom domain and project logo.

src/content/docs/enterprise/project-management/creating-project.mdx

@@ -82,10 +82,11 @@ This type of project setup suits larger or more complex localization projects wh
 To create a project, follow these steps:
 
 <Steps>
-  1. Open your organization's **Workspace**, hover over the <Icon name="mdi:plus" class="inline-icon" /> button at the bottom right, and select **Create a project**. <Image src={createProject} alt="Start to create a project" />
+  1. Open your organization's **Workspace**, hover over the <Icon name="mdi:plus" class="inline-icon" />**Create** button at the lower-right corner, and select **Create a project**. <Image src={createProject} alt="Start to create a project" />
   1. Enter the project name. <Image src={provideProjectName} alt="Provide the project name" class="width-lg" />
   1. Select the source language and target languages. The source language is the language you’re translating from, and the target languages are the ones you’re translating into. <Image src={chooseLanguages} alt="Choose the languages" class="width-lg" />
   1. Select **String-based** if you want to manage your translatable content as individual strings. Otherwise, keep **File-based** selected to manage your translatable content as source files. <Aside type="caution">The project type cannot be changed once the project is created.</Aside>
+  1. Select the existing TM and glossary for your new project to be used as defaults. Alternatively, to create your new project with clean resources, leave the **Create new translation memory** and **Create new glossary** options selected.
   1. *(Optional)* Assign a workflow or [create a new one](/enterprise/workflows).
 
       For projects with an assigned workflow, you can enable the **Delay workflow start** during the project creation. This will allow you to upload existing translations and resources (TM, Glossary) before the project becomes available for translation. Once ready to start with the translation, open your project and click **Start workflow** in the **Dashboard**.
@@ -96,6 +97,7 @@ To create a project, follow these steps:
 
 <Aside type="tip" title="Tips">
   - You can select target languages manually or via **Pre-fill** by using the top 30 languages. If you’d like to translate your project into target languages not officially supported, you can still add them as [custom languages](/enterprise/project-settings/languages#adding-custom-languages).
+  - After the project creation, you can change the [default TM](/enterprise/project-settings/translation-memories/#changing-default-tm) and [default glossary](/enterprise/project-settings/glossaries/#changing-default-glossary) in the project's **Settings**.
   - If you click **Remember selection** at the bottom right, the selected settings will be used as a template the next time you create a project. You can edit the settings afterward.
   - Use [Fields](/enterprise/fields/) to add custom properties to your project.
 </Aside>

src/content/docs/enterprise/project-management/project-settings/general.mdx

@@ -17,6 +17,14 @@ In the **Details** section, you can upload the project logo, change the project
 
 <Image src={details} alt="Project details" />
 
+## Project Language Page View
+
+This section allows you to choose how translators interact with the content on your project's language page.
+
+- **Show files only** &ndash; this option is useful if your project focuses on file-based translation without the need for visual context. It's an easy setup for projects where the text is self-explanatory or where screenshots aren't necessary.
+- **Show files and tagged screenshots** &ndash; displaying both files and tagged screenshots allows translators to reference visual context alongside the text. This option is useful for projects where the meaning of the text can be influenced by its visual environment, improving translation accuracy.
+- **Show screenshots only** &ndash; select this option if every string in your project is associated with a screenshot. By providing visual context for all text, you can significantly improve the quality of translations. This method is considered best practice, especially for projects with complex interfaces or where visual elements are crucial for understanding. However, it requires effort to maintain the accuracy and relevance of the screenshots.
+
 ## Transfer Ownership
 
 Originally, you own any project you create in Crowdin Enterprise. You can transfer your project ownership to any other user in the Organization you belong to.