Issue: Only 1 dimension allowed in contentTypes

Describe the bug In case a Frontmatter subentry has to be taken as name of a custom contentType, it won’t work. For example:

FrontMatter

---
title: xxx
subtitle: yyy
photo:
  file: my-photo.jpg
  name: My Photo
---

Setting

"frontMatter.taxonomy.contentTypes": [
	"name": "default",
    "previewPath": "/static/photos/",
	"fields": [
		...
        {
          "title": "Article preview",
          "name": "photo.file",
          "type": "image"
        }
	]
]

Expected behavior Subentries should be noted if they are separated by a period.

[zivbk1]

This is excellent!

[estruyf]

The first integration of the multi-dimensional content-type field support has been added.

In the content type, you can now define it as follows:

{
  "frontMatter.taxonomy.contentTypes": [
    {
      "name": "multi-dimensional",
      "pageBundle": false,
      "fields": [
        ...
        {
          "title": "Photo",
          "type": "fields",
          "name": "photo",
          "fields": [
            {
              "title": "Title",
              "name": "title",
              "type": "string",
              "default": "default title"
            },
            {
              "title": "URL",
              "name": "url",
              "type": "string"
            }
          ]
        }
      ]
    }
  ]
}

When creating the content, it will automatically include the defined fields. From the metadata section in the Front Matter panel, you can perform changes to your article its front matter.

Feel free to test it out in the latest beta version.