Ver 17

docusaurus.config.js

@@ -30,10 +30,10 @@ const config = {
           editUrl: "https://github.com/Jumoo/jumoo-docs/edit/master",
           versions: {
             current: {
-              label: "v16.x - Umbraco 16",
+              label: "v17.x - Umbraco 17",
             },
-            "15.x": {
-              label: "v15.x - Umbraco 15",
+            "16.x": {
+              label: "v16.x - Umbraco 16",
               banner: "unmaintained",
             },
             "13.x": {
@@ -68,10 +68,10 @@ const config = {
         lastVersion: "current",
         versions: {
           current: {
-            label: "v16.x - Umbraco 16",
+            label: "v17.x - Umbraco 17",
           },
-          "15.x": {
-            label: "v15.x - Umbraco 15",
+          "16.x": {
+            label: "v16.x - Umbraco 16",
             banner: "unmaintained",
           },
           "13.x": {

i18n/en/docusaurus-plugin-content-docs-tm/current.json

@@ -1,6 +1,6 @@
 {
   "version.label": {
-    "message": "v16.x - Umbraco 16",
+    "message": "v17.x - Umbraco 17",
     "description": "The label for version current"
   },
   "sidebar.documentationSidebar.category.get-started-tm": {

i18n/en/docusaurus-plugin-content-docs/current.json

@@ -1,6 +1,6 @@
 {
   "version.label": {
-    "message": "v16.x - Umbraco 16",
+    "message": "v17.x - Umbraco 17",
     "description": "The label for version current"
   },
   "sidebar.documentationSidebar.category.uSync": {

src/pages/SupportLifecycles.md

@@ -21,13 +21,12 @@ From release, to the end of standard support, we will fix any bugs, and issue up
 | Version | Release Date | Type | End of Standard Support | End-of-Life
 |--|--|--|--|--|
 13 | 14th December 2023 | LTS | 14th December 2025 | 14th December 2026
-15 |	14th November 2024 |	STS |  12th June 2025 | 14th November 2025
 16 |	12th June 2025 |	STS |	27th November 2025 |	12th June 2026
+17 |	27th November 2025 |	LTS |	27th November 2027 |	27th November 2028
 
 ### Upcoming Releases
 | Version | Release Date | Type | End of Standard Support | End-of-Life
 |--|--|--|--|--|
-17 |	27th November 2025 |	LTS |	27th November 2027 |	27th November 2028
 18 | 25th June 2026 | STS | 10th December 2026 | 25th June 2027
 19 | 10th December 2026 | STS | 24th June 2027 | 10th December 2027
 20 | 24th June 2027 | STS | 9th December 2027 | 24th June 2028
@@ -42,6 +41,7 @@ From release, to the end of standard support, we will fix any bugs, and issue up
 11 |	12th December 2022 |	STS |	1st September 2023 |	1st December 2023
 12 |	29th June 2023 |	STS |	29th March 2024 |	29th June 2024
 14 |	30th May 2024 | STS | 2nd March 2025 | 30th May 2025
+15 |	14th November 2024 |	STS |  12th June 2025 | 14th November 2025
 
 ### Short Term Support (STS) Releases
 

tm/01.install.mdx

@@ -5,7 +5,7 @@ title: Installation
 To install Translation Manager you will first need to have [installed Umbraco.](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install)
 
 :::note
-Translation Manager v16 runs on Umbraco v16
+Translation Manager v17 runs on Umbraco v17
 ::: 
 
 ## Install via .NET CLI
@@ -25,7 +25,7 @@ import TabItem from '@theme/TabItem';
 <TabItem value="pm">
 
 ```cli
-<PackageReference Include="Jumoo.TranslationManager" Version="16.*" />
+<PackageReference Include="Jumoo.TranslationManager" Version="17.*" />
 ```
 
 </TabItem>
@@ -40,5 +40,5 @@ dotnet add package Jumoo.TranslationManager
 
 
 ## Install as Package 
-On Umbraco v16 you can't install packages via the backoffice, it must be installed via NuGet.
+On Umbraco v17 you can't install packages via the backoffice, it must be installed via NuGet.
 

tm/03.userGuide/15.bulk.md

@@ -2,7 +2,7 @@
 title: Bulk Translations
 ---
 :::warning Not Yet Implemented
-This option is not yet available in version 16.
+This option is not yet available in version 17.
 :::
 
 Bulk Translations allow you to easily build bundles of content from the same translation set and send them for translation. You can pick your translation set from anywhere within a site. 

tm_versioned_docs/version-16.x/00.intro.md

@@ -0,0 +1,19 @@
+---
+title: Introduction
+slug: /
+---
+
+
+Translation Manager is an end to end translation management solution for Umbraco. 
+
+## Overview
+Translation Manager provides editors and website managers with a clean and easy
+way to manage translations for their Umbraco based website. 
+
+Through the use of extended menu options and the Translation Manager Dashboard,
+users can submit, track, and approve content translations without ever having
+to leave Umbraco. 
+
+for more information see the [full Translation Manager site](https://jumoo.co.uk/translate)
+
+<iframe width="684" height="385" src="https://www.youtube.com/embed/pvzcy2V6BVU?si=KptopoRw3QLoIPgK" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

tm_versioned_docs/version-16.x/01.install.mdx

@@ -0,0 +1,44 @@
+---
+title: Installation
+---
+
+To install Translation Manager you will first need to have [installed Umbraco.](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install)
+
+:::note
+Translation Manager v16 runs on Umbraco v16
+::: 
+
+## Install via .NET CLI
+If you have [installed your Umbraco site using .NET CLI](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install/install-umbraco-with-templates), you can also install Translation Manager from within Visual Studio by running the following command in the command-line.
+
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<Tabs
+  defaultValue="core"
+  values={[
+    { label: 'Dotnet', value: 'core', },
+    { label: 'Package Reference', value: 'pm', },
+  ]
+}>
+<TabItem value="pm">
+
+```cli
+<PackageReference Include="Jumoo.TranslationManager" Version="16.*" />
+```
+
+</TabItem>
+<TabItem value="core">
+
+```cli
+dotnet add package Jumoo.TranslationManager
+```
+
+</TabItem>
+</Tabs>
+
+
+## Install as Package 
+On Umbraco v16 you can't install packages via the backoffice, it must be installed via NuGet.
+

tm_versioned_docs/version-16.x/02.getStarted/02.setup.md

@@ -0,0 +1,31 @@
+---
+title: Multi-Language Setups
+---
+
+There are two ways of setting up Umbraco for multiple languages. You can either:
+
+- have a content tree for each language, or
+- run all of your languages through a single tree and use the Umbraco [Variants](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/variants) feature.
+
+## Multiple Tree Setup.
+If you want to have separate content for each language on your site you can do this by maintaining separate content trees within Umbraco, one for each language: 
+
+![multiple languages](multitree.png)
+
+
+## Single Node 
+When using variants, all of your languages live under one content tree.
+
+![single tree](single.png)
+
+and your languages are managed via the dropdown at the top of the content node
+
+![dropdown](dropdown.png)
+
+
+## Which Setup is Right? 
+Which of these setups you choose will depend on how you want to manage your content. If **all** of your content is identical for each language on your site, then the variant method may work best as you can keep your content in sync easily. 
+
+If you have some content that only appears for one or some of your languages then you may wish to maintain a separate tree for each language. 
+
+Translation Manager works with both multilingual setups and has built in tools to help you maintain your site and its structure. 

tm_versioned_docs/version-16.x/02.getStarted/03.Configure.md

@@ -0,0 +1,28 @@
+---
+title: Configure Translations
+--- 
+
+Before you can perform any translations with Translation Manager you will need to configure it so it knows where your primary language content is and where you want the translated content to go. 
+
+You do this by creating a [Translation Set.](../reference/fundementals/set)
+
+## 1. Create a Translation Set: 
+
+1. Go to the settings section of Umbraco
+2. Expand the *Translation Manager* node in the settings tree
+3. Go to the *Sets* node
+4. Click on the *Create new set* button.
+![The create new set button.](createSet.png)
+
+## 2. Configure Your Translation Set
+
+ 1. Give your set a name.
+ 2. Select your master content node.
+    - This is the place where your source content is going to come from 
+ 3. Select the locations you want the translated content to go.
+
+You can have multiple locations on for each language your want to translate.
+
+ You don't need to change any other settings but you can follow our [create a Translation Set guide](../userGuide/create) for more info.
+
+

tm_versioned_docs/version-16.x/02.getStarted/04.send.md

@@ -0,0 +1,31 @@
+---
+title: Send to Translate
+---
+
+Once your set is created you can send your content for translation.
+
+In your source language site:
+
+- Right click on the node you want to have translated.
+- Select "Send to translation" from the menu.
+
+## Send to Translation Dialog
+
+![Translation Menu](sendtotranslate.png)
+
+- Choose which languages you want the content to be translated into.
+- Select whether or not you want to include child content.
+- Choose what you want to do with translated items. 
+- Click send. 
+
+### Choose a provider
+
+Depending on your setup, you will now see the choose a Connector option. Select [XLIFF Connector.](../extending/connectors/XLIFF/xliff)
+
+:::note
+The XLIFF connector has no options you can change. Other connectors might give you options here that allow you to change how a job is sent to a translation service
+:::
+
+- Click *Send* 
+
+Translation Manager will now create a translation job for your translated content. 

tm_versioned_docs/version-16.x/02.getStarted/05.job.md

@@ -0,0 +1,27 @@
+---
+title: The Translation Job
+---
+
+#### Viewing the Job
+
+![Submitted for translation](viewjob.png)
+
+Once a job has been created you can click the *View Job Button*.
+
+This will take you to the translated job. 
+
+![Translated job page](translatedjob.png)
+
+#### Processing the Translation (XLIFF)
+
+With the XLIFF connector, you can download the XLIFF file that has been produced and send it to your translator.
+
+When the translator has finished translating your content, they will return an XLIFF file to you, which you can then upload to the translation job, so Translation Manager will load in the translated content. 
+
+#### Approving the Job 
+Once you have your translated content back into the Translation Manager job, you can approve it and it will be pushed back in your Umbraco site. 
+
+- *Approve & Publish* will put the content back into your site and publish the pages.
+- *Approve & Save* will put the content back but will not publish the pages, so it won't be live.
+
+

tm_versioned_docs/version-16.x/02.getStarted/10.licence.md

@@ -0,0 +1,33 @@
+---
+title: Purchase a Licence
+---
+
+
+## Licence Limits
+Without a licence you can have one [translation set](../reference/fundementals/set) and translate between two languages, such as from English to French, but you cannot add other languages. 
+
+On your local machine, where the domain ends in either .localhost or .local, you can have as many languages or translation sets as you want. However, when you move to a production server, the licence limits will apply.
+
+## Purchase a Licence
+
+Go to the website https://jumoo.co.uk/translate/purchase
+
+
+## Add Licence Key to the Site 
+![Licence page](licencelocation.png)
+
+You can find the licence key box in the backoffice in Settings -> Translation Manager -> licence.
+
+The licence is stored in `umbraco/Licence/translationManager.licence`. This file can be copied between servers.
+
+You can also enter the licence key in config:
+
+```json
+"Translation": {
+  "License" : {
+        "Key": "[LICENCE-KEY]",
+        "Domains": "[LICENCE-DOMAIN]"
+    }
+}
+```
+This way if the translationManager.licence file is deleted, your translation key won't go with it. 

tm_versioned_docs/version-16.x/02.getStarted/15.upgrade.mdx

@@ -0,0 +1,40 @@
+---
+title: Upgrading Translation Manager
+---
+
+
+You can upgrade Translation Manager via the commandline or editing your project (.csproj) file directly.
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<Tabs
+  defaultValue="core"
+  values={[
+    { label: 'Dotnet', value: 'core', },
+    { label: 'Package Reference', value: 'pm', },
+  ]
+}>
+<TabItem value="pm">
+
+```cli
+<PackageReference Include="Jumoo.TranslationManager" Version="14.*" />
+```
+
+</TabItem>
+<TabItem value="core">
+
+```cli
+dotnet add package Jumoo.TranslationManager
+```
+
+</TabItem>
+</Tabs>
+
+### Finishing Jobs
+
+We don't reccomend that you upgrade Translation Manager with jobs in their submitted state. 
+
+Usually, upgrades don't change internal data, but occasionally they do, so it is much safer not to have open jobs when you upgrade.
+
+

tm_versioned_docs/version-16.x/02.getStarted/_category_.json

@@ -0,0 +1,10 @@
+{
+    "label": "Get Started",
+    "key": "get-started-tm",
+    "link": {
+        "type": "generated-index",
+        "title": "Get Started with Translation Manager",
+        "description": "Your guide to installing Translation Manager and getting started."
+    }
+}
+