Changes for 9.4.0 release

Author: estruyf

.frontmatter/database/mediaDb.json

@@ -1,6 +1,6 @@
 # Change Log
 
-## [9.4.0] - 2023-xx-xx
+## [9.4.0] - 2023-xx-xx - [Release notes](https://beta.frontmatter.codes/updates/v9.4.0)
 
 ### ✨ New features
 

content/changelog/CHANGELOG.md

@@ -2,7 +2,7 @@
 title: Version 9.4.0 release notes
 description: ""
 date: 2023-12-07T15:05:16.280Z
-lastmod: 2023-12-07T16:40:53.318Z
+lastmod: 2023-12-08T09:17:28.790Z
 slug: ""
 type: changelog
 ---
@@ -68,12 +68,26 @@ const width = answers.width;
 
 > **Info**: More information can be found in the [asking questions to users](/docs/custom-actions#asking-questions-to-users) documentation.
 
-### Scheduled content
+## Scheduled content
 
 You can now filter and group the content dashboard by scheduled content. This allows you to see which content is scheduled to be published in the future.
 
 ![Scheduled content](/releases/v9.4.0/scheduled-content.png)
 
+## Creating sub-content
+
+When creating sub-content, you can now select the parent folder. This allows you to create you content in any folder you want.
+
+You can enable this feature on the content type by setting the `allowAsSubContent` or `isSubContent` property to `true`.
+
+> **Info**: More information can be found in the [creating sub-content](/docs/content-creation/content-types#creating-sub-content) documentation.
+
+## Content type name shown in the panel
+
+A small enhancement which we added in this release to the editor panel is the content type name in the metadata section. Now you can easily see which content type your content is using.
+
+![Content type name](/releases/v9.4.0/content-type-name.png)
+
 ## Related issues/enhancements
 
 ### ✨ New features

content/changelog/v9.4.0.md

@@ -3,7 +3,7 @@ title: Content types
 slug: content-creation/content-types
 description: null
 date: 2022-03-14T08:43:17.483Z
-lastmod: 2023-09-11T07:47:18.146Z
+lastmod: 2023-12-08T09:13:41.283Z
 weight: 200.1
 ---
 
@@ -128,6 +128,8 @@ For the content type you can configure the following properties:
 | `postScript`      | `string`                                 | An optional post script that can be used after new content creation. In order to use this, you will have to set the value to the ID of your [content script][04]   | `null`        |
 | `previewPath`     | `string`                                 | Defines a custom preview path for the content type. When the preview path is not set, the value from the [`frontMatter.preview.pathName`][03] setting will be used | `null`        |
 | `template`        | `string`                                 | Specify a path to a template file that will be used when creating new content with the content type                                                                | `null`        |
+| `allowAsSubContent` | `boolean`                              | Allow the content type to be used as sub-content                                                                                                                   | `false`       |
+| `isSubContent`    | `boolean`                                | Defines the content type as sub-content                                                                                                                            | `false`       |
 
 ## Define your own type
 
@@ -180,6 +182,61 @@ type: documentation
 
 > **Fields**: Check out the [fields][05] section to learn which fields are supported.
 
+## Creating sub-content
+
+By default, when you create new content, it will always be created in one of your defined folders
+in the `frontMatter.content.pageFolders` setting.
+
+In some cases, you want to create a hierarchy of content. For example, you want to create a
+documentation site, where each topic has its own folder. The starting point is a page bundle which
+contains the `index.md` file and all the related topics are created as separate files in the same
+folder.
+
+To support this, you can now make use of the `allowAsSubContent` and `isSubContent` properties on
+your content type.
+
+### Allow as sub-content
+
+The `allowAsSubContent` property is intended to be used for content types with a page bundle
+(`pageBundle: true`). When you set this property to `true`, during the content creation, you will be
+able to choose if you want to create content as parent or sub-content.
+
+```json {{ "title": "Using the allowAsSubContent property" }}
+{
+  "frontMatter.taxonomy.contentTypes": [
+    {
+      "name": "parent",
+      "pageBundle": true,
+      "allowAsSubContent": true,
+      "fields": [
+        ...
+      ]
+    }
+  ]
+}
+```
+
+### Is sub-content
+
+The `isSubContent` property is intended to be used for content types which will always be created as
+sub-content. When you set this property to `true`, during the content creation, you be able to
+select the parent folder.
+
+```json {{ "title": "Using the isSubContent property" }}
+{
+  "frontMatter.taxonomy.contentTypes": [
+    {
+      "name": "child",
+      "pageBundle": true,
+      "isSubContent": true,
+      "fields": [
+        ...
+      ]
+    }
+  ]
+}
+```
+
 ## Using a template with the content type
 
 When creating content that requires a pre-defined structure, you can use the `template` property.

content/docs/content-creation/content-type.md

@@ -3,7 +3,7 @@ title: Fields
 slug: content-creation/fields
 description: null
 date: 2022-03-14T08:42:21.626Z
-lastmod: 2023-12-01T09:24:51.920Z
+lastmod: 2023-12-08T08:57:08.344Z
 weight: 200.2
 ---
 
@@ -447,6 +447,8 @@ When the tag is created, you will be able to re-use it for other content.
 
 - `taxonomyLimit`: Defines the maximum number of items that can be selected. By default set to `0`
   which allows unlimited items to be selected.
+- `singleValueAsString`: When set to `true`, a single value will be added as a string value instead
+of an array.
 
 > **Info**: When a limit is defined, this will get reflected in the UI as well:
 
@@ -479,6 +481,8 @@ The `categories` field is similar to the [tags][09] field. Categories are also s
 
 - `taxonomyLimit`: Defines the maximum number of items that can be selected. By default set to `0`
   which allows unlimited items to be selected.
+- `singleValueAsString`: When set to `true`, a single value will be added as a string value instead
+of an array.
 
 ```json {{ "title": "Usage" }}
 {
@@ -506,6 +510,8 @@ taxonomy values and structure.
   which allows unlimited items to be selected.
 - `taxonomyId`: Set the id of your custom taxonomy definition defined in the
   `frontMatter.taxonomy.customTaxonomy` setting.
+- `singleValueAsString`: When set to `true`, a single value will be added as a string value instead
+of an array.
 
 ### Custom taxonomy
 

content/docs/content-creation/fields.md

@@ -3,7 +3,7 @@ title: Settings overview
 slug: settings/overview
 description: null
 date: 2023-02-13T16:44:09.618Z
-lastmod: 2023-10-27T07:02:42.637Z
+lastmod: 2023-12-08T09:03:00.096Z
 weight: 1100.2
 ---
 
@@ -771,6 +771,13 @@ Specifies the tags which can be used in the Front Matter.
 > (`.frontmatter/database/taxonomyDb.json`). The setting can still be used to predefine the tags.
 > Once the project gets initialized, the tags will be moved to the database file.
 
+### frontMatter.taxonomy.quoteStringValues
+
+Specify if you always want to wrap string values in quotes.
+
+- Type: `boolean`
+- Default: `false`
+
 ### frontMatter.telemetry.disable
 
 Specify if you want to disable the telemetry.