Multilingual support

Author: estruyf

.frontmatter/database/mediaDb.json

@@ -3,22 +3,24 @@ title: Content folders
 slug: content-creation/content-folders
 description: null
 date: 2024-02-21T09:10:16.640Z
-lastmod: 2024-02-21T09:43:59.593Z
+lastmod: 2024-02-21T14:56:03.901Z
 weight: 200.11
 ---
 
 # Content Folders
 
 Content folders are a way to organize your pages/files. Most of the time,
-this location is defined by the Static Site Generator (SSG) you are using.
+the static site generator (SSG) you are using defines the location where
+you store your content.
 
-To make sure that Front Matter CMS can find your content, and create the
+To make sure that Front Matter CMS can find your content and create the
 content in the correct place, you need to register the content/page folders.
 
 ## Registering content folders
 
-The registration of the page folders is normally done during the setup of
-the CMS: [Step 3: Register content folder(s)][01].
+The registration of the page folders is typically performed during the setup of
+the CMS: [Step 3: Register content folder(s)][01],
+but you can perform changes at any time.
 
 Content folders are stored in the [frontMatter.content.pageFolders][02] setting.
 
@@ -73,7 +75,27 @@ Content folders are stored in the [frontMatter.content.pageFolders][02] setting.
 }
 ```
 
-Once the content folders are registered, you can start creating content with Front Matter CMS.
+Once the content folders are registered, you can create content with Front Matter CMS.
+
+## Register a new content folder
+
+### Settings view
+
+You can make use of the settings view to easily add a new content folder.
+
+To open the settings view, click on the gear icon in the top right corner in any of our dashboards.
+
+1. Click on the "Content folders" tab.
+1. Click on the folders which you want to add as a content folder.
+
+![Add a new content folder](/releases/v9.3.0/content-folders.png)
+
+### Explorer view
+
+You can also add a new content folder by right-clicking on a folder in the explorer view
+and clicking on `Register folder` under the Front Matter CMS context menu.
+
+![Register a new content folder](/releases/v9.3.0/register-folder.png)
 
 ## Properties
 

content/docs/content-creation/content-folders.md

@@ -3,8 +3,148 @@ title: Multilingual
 slug: content-creation/multilingual
 description: null
 date: 2024-02-21T09:10:16.640Z
-lastmod: 2024-02-21T09:43:53.819Z
+lastmod: 2024-02-21T15:47:40.601Z
 weight: 200.71
 ---
 
 # Multilingual content
+
+Front Matter CMS supports multilingual content. This means that you can create
+content in multiple languages and manage them in the same workspace.
+
+![Multilingual content](/releases/v10.0.0/multilingual-content.png)
+
+## Configuration
+
+To enable multilingual content, you need to define the default locale per content folder
+and define which locales which you want to support.
+
+### Define the default locale per content folder
+
+To define the default locale per content folder, you need to use the `defaultLocale`
+property on the `frontMatter.content.pageFolders` setting.
+
+```json {{ "title": "Example of the default locale configuration" }}
+{
+  "frontMatter.content.pageFolders": [
+    {
+      "title": "Multilingual",
+      "path": "[[workspace]]/docs/en",
+      "filePrefix": "",
+      "defaultLocale": "en" // This value needs to map to the locale defined in the i18n setting
+    }
+  ]
+}
+```
+
+### Define the locales
+
+You can define the locales on two levels:
+
+- **Global level**: When using the `frontMatter.content.i18n` setting, you define
+  the locales for the entire workspace. This means that any content folder which
+  is multilingual enabled, it will use the locales defined in the global setting.
+- **Content folder level**: When using the `locales` property on the
+  `frontMatter.content.pageFolders` setting, you can define the locales for a
+  specific content folder.
+
+#### Global level
+
+To define the locales on the global level, you need to use the `frontMatter.content.i18n`
+setting.
+
+```json {{ "title": "Example of the global i18n configuration" }}
+{
+  "frontMatter.content.i18n": [
+    {
+      "title": "English",
+      "locale": "en"
+    },
+    {
+      "title": "German",
+      "locale": "de",
+      "path": "../de"
+    },
+    {
+      "title": "Nederlands",
+      "locale": "nl",
+      "path": "../nl"
+    }
+  ]
+}
+```
+
+> **Important**: The default locale (like the **English** locale) does not
+> require to define a `path` as it is defined by the content folder configuration.
+
+#### Content folder level
+
+You can also define the locales on the content folder level. This allows you to
+override the global locales for a specific content folder.
+
+```json {{ "title": "Example of the content folder i18n configuration" }}
+{
+  "frontMatter.content.pageFolders": [
+    {
+      "title": "Multilingual",
+      "path": "[[workspace]]/docs/en",
+      "filePrefix": "",
+      "defaultLocale": "en",
+      "locales": [
+        {
+          "title": "English",
+          "locale": "en"
+        },
+        {
+          "title": "Nederlands",
+          "locale": "nl",
+          "path": "../nl"
+        }
+      ]
+    }
+  ]
+}
+```
+
+## Create a translation
+
+Once the multilingual settings are configured, you can create content in multiple
+languages with Front Matter CMS.
+
+You can create content translations by starting from the default locale content and
+then you can use any of the following methods to create a new translation:
+
+- Use the `Front Matter: Create new translation` command from the command palette
+- Use the `Create new translation` button in the content editor toolbar
+
+![Create translation action](/releases/v10.0.0/create-translation.png)
+
+- On the content dashboard, you can use the `create translation` action from the
+  content item menu
+
+![Create translation on content card](/releases/v10.0.0/card-create-translation-action.png)
+
+## Automatic language translation
+
+By default, the multilingual feature does not include automatic language translation of
+content. However, you can make use of [DeepL](https://www.deepl.com/) for automatic
+language translation.
+
+To enable automatic language translation, you need to provide your authentication key
+from DeepL.
+
+### Configure DeepL
+
+Follow the next steps in order to configure the DeepL authentication key:
+
+- Go to the [DeepL Account Summary](https://www.deepl.com/your-account/summary) page
+- Copy the `Authentication Key for DeepL API`
+- Back in Visual Studio Code, open the Front Matter CMS dashboard
+- Click on the gear icon in the top right corner to open the settings view
+- Click on the `Integration` tab
+- Paste the `Authentication Key for DeepL API` in the `Authentication key` field
+
+![DeepL Authentication Key](/releases/v10.0.0/deepl-authentication-key.png)
+
+Once you provided the authentication key, when you create a new translation, the
+content will be automatically translated to the target language.

content/docs/content-creation/multilingual.md

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/content.pagefolders.schema.json",
   "description": "Defines the settings for Front Matter page folder",
-  "lastModified": "2024-02-21T09:52:54.398Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - page folder",
   "properties": {

public/config/content.pagefolders.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/content.placeholders.schema.json",
   "description": "Defines the settings for Front Matter placeholder",
-  "lastModified": "2024-02-21T09:52:54.399Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - placeholder",
   "properties": {

public/config/content.placeholders.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/content.snippets.schema.json",
   "description": "Defines the settings for Front Matter snippet",
-  "lastModified": "2024-02-21T09:52:54.399Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - snippet",
   "required": [

public/config/content.snippets.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/custom.scripts.schema.json",
   "description": "Defines the settings for Front Matter custom script",
-  "lastModified": "2024-02-21T09:52:54.398Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - custom script",
   "properties": {

public/config/custom.scripts.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/data.files.schema.json",
   "description": "Defines the settings for Front Matter data file",
-  "lastModified": "2024-02-21T09:52:54.399Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - data file",
   "properties": {

public/config/data.files.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/data.folders.schema.json",
   "description": "Defines the settings for Front Matter data folder",
-  "lastModified": "2024-02-21T09:52:54.399Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - data folder",
   "properties": {

public/config/data.folders.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema",
   "$id": "https://beta.frontmatter.codes/config/data.types.schema.json",
   "description": "Defines the settings for Front Matter data type",
-  "lastModified": "2024-02-21T09:52:54.399Z",
+  "lastModified": "2024-02-21T15:28:35.428Z",
   "type": "object",
   "title": "Front Matter - data type",
   "properties": {