Jumoo · daisy-jump · Jun 12, 2025 · Jun 6, 2025 · Jun 6, 2025 · Jun 9, 2025
diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -31,7 +31,11 @@ const config = {
           editUrl: "https://github.com/Jumoo/jumoo-docs/edit/master",
           versions: {
             current: {
+              label: "v16.x - Umbraco 16",
+            },
+            "15.x": {
               label: "v15.x - Umbraco 15",
+              banner: "unmaintained",
             },
             "13.x": {
               label: "v13.x - Umbraco 13",
@@ -65,7 +69,11 @@ const config = {
         lastVersion: "current",
         versions: {
           current: {
+            label: "v16.x - Umbraco 16",
+          },
+          "15.x": {
             label: "v15.x - Umbraco 15",
+            banner: "unmaintained",
           },
           "13.x": {
             label: "v13.x - Umbraco 13",

diff --git a/i18n/en/docusaurus-plugin-content-docs-tm/current.json b/i18n/en/docusaurus-plugin-content-docs-tm/current.json
@@ -1,6 +1,6 @@
 {
   "version.label": {
-    "message": "v15.x - Umbraco 15",
+    "message": "v16.x - Umbraco 16",
     "description": "The label for version current"
   },
   "sidebar.documentationSidebar.category.Get Started": {

diff --git a/i18n/en/docusaurus-plugin-content-docs/current.json b/i18n/en/docusaurus-plugin-content-docs/current.json
@@ -1,6 +1,6 @@
 {
   "version.label": {
-    "message": "v15.x - Umbraco 15",
+    "message": "v16.x - Umbraco 16",
     "description": "The label for version current"
   },
   "sidebar.documentationSidebar.category.uSync": {

diff --git a/src/pages/SupportLifecycles.md b/src/pages/SupportLifecycles.md
@@ -22,12 +22,12 @@ From release, to the end of standard support, we will fix any bugs, and issue up
 |--|--|--|--|--|
 10 |	16th June 2022 |	LTS |	16th June 2024 |	16th June 2025
 13 | 14th December 2023 | LTS | 14th December 2025 | 14th December 2026
-15 |	14th November 2024 |	STS |  14th August  2025 | 14th November 2025
+15 |	14th November 2024 |	STS |  12th June 2025 | 14th November 2025
+16 |	12th June 2025 |	STS |	12th March 2026 |	12th June 2026
 
 ### Upcoming Releases
 | Version | Release Date | Type | End of Standard Support | End-of-Life
 |--|--|--|--|--|
-16 |	12th June 2025 |	STS |	12th March 2026 |	12th June 2026
 17 |	27th November 2025 |	LTS |	27th November 2027 |	27th November 2028
 
 ### End-of-Life
@@ -39,6 +39,12 @@ From release, to the end of standard support, we will fix any bugs, and issue up
 12 |	29th June 2023 |	STS |	29th March 2024 |	29th June 2024
 14 |	30th May 2024 | STS | 2nd March 2025 | 30th May 2025
 
+### Short Term Support (STS) Releases
+
+Starting with version 15, we will only develop and patch an STS version while it is the latest Umbraco version. Once a new version of Umbraco is released, all our support patches and bug fixes will move to the new version.
+
+We will still patch any securty issues until the end-of-life date for any version. All bug fixes will only be applied to the latest STS release and any long-term support versions that have not reached end-of-life.
+
 ### More Info
 
 For more info on Umbraco updates, visit their [long-term support and end-of-life page](https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/). 
diff --git a/tm/01.install.mdx b/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 v15 runs on Umbraco v15
+Translation Manager v16 runs on Umbraco v16
 ::: 
 
 ## Install via NuGet Package Manager 
@@ -25,7 +25,7 @@ import TabItem from '@theme/TabItem';
 <TabItem value="pm">
 
 ```cli
-<PackageReference Include="Jumoo.TranslationManager" Version="15.*" />
+<PackageReference Include="Jumoo.TranslationManager" Version="16.*" />
 ```
 
 </TabItem>
@@ -40,5 +40,5 @@ dotnet add package Jumoo.TranslationManager
 
 
 ## Install as Package 
-On Umbraco v15 you can't install packages via the backoffice, it must be installed via NuGet.
+On Umbraco v16 you can't install packages via the backoffice, it must be installed via NuGet.
 
diff --git a/tm/03.userGuide/15.bulk.md b/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 15.
+This option is not yet available in version 16.
 :::
 
 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. 

diff --git a/tm/04.Extending/01.connectors/05.Microsoft.md b/tm/04.Extending/01.connectors/05.Microsoft.md
@@ -18,7 +18,7 @@ As of v15.0.3 you can change to a custom Endpoint for [Azure AI Custom Translato
 ## Region
 Select the region for your translation service. 
 
-As of V15.0.3 the Region options have a box under the the region drop down for if your region doesn't exist, or if you have a custom region with [Azure AI Custom Translator](https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/concepts/customization). To customise, click on the padlock symbol and type your custom region.
+As of v15.0.3 the Region options have a box under the the region drop down for if your region doesn't exist, or if you have a custom region with [Azure AI Custom Translator](https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/concepts/customization). To customise, click on the padlock symbol and type your custom region.
 
 ## Throttle
 Set the number of milliseconds between tasks sent to Microsoft Translator, this will prevent the system from being overwhelmed.

diff --git a/tm/05.reference/01.global.mdx b/tm/05.reference/01.global.mdx
@@ -30,8 +30,8 @@ overriding the default setting.
 {
     "Translation": {
         "backgroundCheck": true,
+        "backgroundApproval": false,
         "scheduleCheckPeriod": 180,
-        "autoTranslate": true,
         "includeEmpty": false,
         "batchSize": 25,
         "history": true,
@@ -42,6 +42,7 @@ overriding the default setting.
         "CheckLinksOnLoopback": false,
         "autoTranslate": true, 
         "autoTranslatePublishOnly": false,
+        "hideLicenceTab": false,
         "links": {
             "inline": true,
             "pickers": false, 
@@ -70,50 +71,140 @@ overriding the default setting.
 ```
 
 
-### Background Check
+### backgroundCheck
 Periodically checks the status of submitted [Jobs](fundementals/job) automatically.
+```json
+ "Translation": {
+    "backgroundCheck": true,
+  }
+```
+
+### BackgroundApproval
+Allows the approval process to run in the background (so you don't have to sit around and watch it happen). 
+```json
+ "Translation": {
+    "backgroundApproval": false
+  }
+```
 
-### Check Period 
+### scheduleCheckPeriod 
 The number specifies how often the background check occurs.
+```json
+"Translation": {
+    "scheduleCheckPeriod": 180,
+  }
+```
 
-### Include Empty Nodes 
+### includeEmpty
 Include nodes with no translatable text in jobs.
+```json
+"Translation": {
+    "includeEmpty": false,
+  }
+```
 
-### Batch Size 
+### batchSize 
 Number of items to process in a batch (if you are experiencing timeouts, try lowering this number).
+```json
+"Translation": {
+    "batchSize": 25,
+  }
+```
 
 ### history
 Shows the history tab on a job. This allows you to see events. This setting is on by default
+```json
+"Translation": {
+    "history": true,
+  }
+```
+
+### fixup
+Turns on debugging in interface by default, so you can delete the things you can't usually delete. You can turn this on per request by adding `&tm=debug` to the url.
+```json
+"Translation": {
+    "fixup": false,
+  }
+```
 
 ### returnToPending
 Put translated content back into the pending queue if a job is cancelled. May cause conflicts. This setting is off by default.
+```json
+"Translation": {
+    "returnToPending": false,
+  }
+```
 
 ### relationType
 Default Umbraco relation used to link pages across languages. 
+```json
+"Translation": {
+    "relationType": "relateDocumentOnCopy",
+  }
+```
 
 ### UniqueNestedIds
 Ensures that block and nested items get unique internal IDs when tranlated into other languages. By default these IDS are seperate, but depending on your set up you may want them to remain the same. 
+```json
+"Translation": {
+    "UniqueNestedIds": true,
+  }
+```
 
 ### CheckLinksOnLoopback
 Toggle whether or not links within content are checked on translations that are using variants. By default, links are only checked on translations between two different sitenodes. 
+```json
+"Translation": {
+    "CheckLinksOnLoopback": false,
+  }
+```
 
 ### autoTranslate
 Saves the changes that have been made in *Pending*.
+```json
+"Translation": {
+     "autoTranslate": true, 
+  }
+```
 
 ### autoTranslatePublishOnly
 Only published items are put into the pending queue
+```json
+"Translation": {
+    "autoTranslatePublishOnly": false,
+  }
+```
 
 ### hideLicenceTab
 Hide the licence tab from the UI. This setting is useful if you dont want anyone to see the licence key.
-
-### fixup
-Turns on debugging in interface by default, so you can delete the things you can't usually delete. You can turn this on per request by adding `&tm=debug` to the url.
+```json
+"Translation": {
+    "hideLicenceTab": false,
+  }
+```
 
 ### notify
 The email adresses that notifs will be sent to when jobs reach a certain stage.
+```json
+"Translation": {
+    "notify": {
+            "pending": "",
+            "approved": "",
+            "submitted": "",
+            "received": ""
+            "disabled": false,
+            "subject": "Translations : [{job}] - {eventName}",
+        },
+  }
+```
 
-### subject
+#### notify:subject
 The template for the subject is ID, source, and target, ID. The ID is the job ID, the source is the source language, and the target is the target language. The options for eventname are pending, approved, submitted, and recieved
+```json
+"notify": {
+    "subject": "Translations : [{job}] - {eventName}",
+ },
+```
 
 ### mappers
 Mappers are explained on the [Property Mapping page](../extending/mapping/index). 
diff --git a/tm_versioned_docs/version-15.x/00.intro.md b/tm_versioned_docs/version-15.x/00.intro.md
@@ -0,0 +1,18 @@
+---
+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)
+
diff --git a/tm_versioned_docs/version-15.x/01.install.mdx b/tm_versioned_docs/version-15.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 v15 runs on Umbraco v15
+::: 
+
+## Install via NuGet Package Manager 
+If you have [installed your Umbraco site via NuGet](https://our.umbraco.com/documentation/Fundamentals/Setup/Install/install-umbraco-with-nuget) then you can also install Translation Manager from within Visual Studio by running the following command in the [Package Manager Console.](https://docs.microsoft.com/en-us/nuget/consume-packages/install-use-packages-powershell)
+
+
+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="15.*" />
+```
+
+</TabItem>
+<TabItem value="core">
+
+```cli
+dotnet add package Jumoo.TranslationManager
+```
+
+</TabItem>
+</Tabs>
+
+
+## Install as Package 
+On Umbraco v15 you can't install packages via the backoffice, it must be installed via NuGet.
+
diff --git a/tm_versioned_docs/version-15.x/02.getStarted/02.setup.md b/tm_versioned_docs/version-15.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://our.umbraco.com/documentation/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.