Sorry, no results found for "".

In this page

Setup

Migrating HTML content

Converting image tags into blocks

Migrating Markdown content

Migrating Modular Content fields

Wrapping up

Working with Structured Text > Migrating content to Structured Text

Migrating content to Structured Text

The goal of this guide is to teach you how to migrate an existing DatoCMS project to Structured Text fields. To illustrate the process, we'll use an example project that you can clone on your account to follow each step.

In a hurry? Download the final result!

If you prefer to skip the tutorial and just take a look at the final code, head over to this GitHub repo.

Setup

First of all, to follow this guide, make sure to clone this example project into your own DatoCMS account.

Done? Great! Now's open the terminal, create a new directory for the migration project, and install the DatoCMS CLI:

mkdir structured-text-migrations
cd structured-text-migrations
npm init --yes
npm i --save-dev typescript @datocms/cli
tsc --init
mkdir -p migrations/utils

Now let's setup a profile for the CLI:

1
$ datocms profile:set
2

3
Config file not present in "datocms.config.json", will be created from scratch
4
Requested to configure profile "default"
5

6
* Level of logging to use for the profile (NONE, BASIC, BODY, BODY_AND_HEADERS) [NONE]:
7
* Directory where script migrations will be stored [./migrations]:
8
* API key of the DatoCMS model used to store migration data [schema_migration]:
9
* Path of the file to use as migration script template (optional):
10

11
Writing "datocms.config.json"... done

We're also creating a local .env file containing the full-access API token to the project, so that the datocms CLI can communicate with it (make sure you don't commit it to your repo!):

echo 'DATOCMS_API_TOKEN=<YOUR_READWRITE-TOKEN>' > .env

High-level strategy & Project skeleton

This is the content schema of the cloned project:

The fields we want to convert into Structured Text are the following:

HTML Article > Content (HTML multi-paragraph text);
Markdown Article > Content (Markdown multi-paragraph text);
Modular Content Article > Content (Modular content);

To do that, we're going to write three migration scripts (one for each model) and test the result inside a sandbox environment.

For every field, the high-level plan will be the same:

Create a new Structured Text field for the model;
For every article, take the old content, convert it to Structured Text and save it in the new field;
Destroy the old field.

Inside the migrations/utils directory, we're adding some functions that we're going to use for all three migrations:

createStructuredTextFieldFrom creates a new Structured Text field with the same label and API key as an existing field, but prefixed with structured_text_ (basically, step 1 of our plan);
getAllRecords fetches all the records of a specific model using the nested option, so that for modular content fields we get the full payload of the inner block records instead of just their ID (that's the first bit of step 2);
swapFields destroys the old field, and renames the new Structured Text field as the old one (that's step 3 of our plan);

Lastly, since:

some API calls expect the model ID and not the model API key, and
model IDs are different on each environment, and
we want our migrations to work on any environment

we can avoid hardcoding model IDs writing a getModelIdsByApiKey function that returns an object mapping API keys to model IDs:

1
import { Client, SimpleSchemaTypes } from '@datocms/cli/lib/cma-client-node';
2

3
export default async function createStructuredTextFieldFrom(
4
  client: Client,
5
  modelApiKey: string,
6
  fieldApiKey: string,
7
  modelBlockIds: SimpleSchemaTypes.ItemTypeIdentity[],
8
): Promise<SimpleSchemaTypes.Field> {
9
  const legacyField = await client.fields.find(
10
    `${modelApiKey}::${fieldApiKey}`,
11
  );
12

13
  const newApiKey = `structured_text_${fieldApiKey}`;
14
  const label = `${legacyField.label} (Structured-text)`;
15

16
  console.log(`Creating ${modelApiKey}::${newApiKey}`);
17

18
  return client.fields.create(modelApiKey, {
19
    label,
20
    api_key: newApiKey,
21
    field_type: 'structured_text',
22
    fieldset: legacyField.fieldset,
23
    validators: {
24
      structured_text_blocks: {
25
        item_types: modelBlockIds,
26
      },
27
      structured_text_links: { item_types: [] },
28
    },
29
  });
30
}
31

32
// ./migrations/utils/getAllRecords.ts
33
import { Client } from '@datocms/cli/lib/cma-client-node';
34

35
export default async function getAllRecords(
36
  client: Client,
37
  modelApiKey: string,
38
) {
39
  const records = await client.items.list({
40
    filter: { type: modelApiKey },
41
    nested: true,
42
  });
43
  console.log(`Found ${records.length} records!`);
44
  return records;
45
}
46

47
// ./migrations/utils/swapFields.ts
48
import { Client } from '@datocms/cli/lib/cma-client-node';
49

50
export default async function swapFields(
51
  client: Client,
52
  modelApiKey: string,
53
  fieldApiKey: string,
54
) {
55
  const oldField = await client.fields.find(`${modelApiKey}::${fieldApiKey}`);
56
  const newField = await client.fields.find(
57
    `${modelApiKey}::structured_text_${fieldApiKey}`,
58
  );
59
  // destroy the old field
60
  await client.fields.destroy(oldField.id);
61
  // rename the new field
62
  await client.fields.update(newField.id, {
63
    api_key: fieldApiKey,
64
    label: oldField.label,
65
    position: oldField.position,
66
  });
67
}
68

69
// ./migrations/utils/getModelIdsByApiKey.ts
70
import { Client } from '@datocms/cli/lib/cma-client-node';
71
import { ItemType } from '@datocms/cma-client/dist/types/generated/SimpleSchemaTypes';
72

73
export default async function getModelIdsByApiKey(
74
  client: Client,
75
): Promise<Record<string, ItemType>> {
76
  const models = await client.itemTypes.list();
77
  return models.reduce(
78
    (acc, itemType) => ({
79
      ...acc,
80
      [itemType.api_key]: itemType,
81
    }),
82
    {},
83
  );
84
}
85

86
// migrations/utils/findOrCreateUploadWithUrl.ts
87
import { Client } from '@datocms/cli/lib/cma-client-node';
88
import path from 'path';
89

90
export default async function findOrCreateUploadWithUrl(
91
  client: Client,
92
  url: string,
93
) {
94
  let upload;
95

96
  if (url.startsWith('https://www.datocms-assets.com')) {
97
    const pattern = path.basename(url).replace(/^[0-9]+\-/, '');
98

99
    const matchingUploads = await client.uploads.list({
100
      filter: {
101
        fields: {
102
          filename: {
103
            matches: {
104
              pattern,
105
              case_sensitive: false,
106
              regexp: false,
107
            },
108
          },
109
        },
110
      },
111
    });
112

113
    upload = matchingUploads.find((u) => {
114
      return u.url === url;
115
    });
116
  }
117

118
  if (!upload) {
119
    upload = await client.uploads.createFromUrl({ url });
120
  }
121

122
  return upload;
123
}

Migrating HTML content

Let's create the first migration script:

> datocms migrations:new convertHtmlArticles
Created migrations/1612281851_convertHtmlArticles.ts

Replace the content of the file with the following skeleton, which uses the utilities we just created:

1
import getModelIdsByApiKey from './utils/getModelIdsByApiKey';
2
import createStructuredTextFieldFrom from './utils/createStructuredTextFieldFrom';
3
import htmlToStructuredText from './utils/htmlToStructuredText';
4
import getAllRecords from './utils/getAllRecords';
5
import swapFields from './utils/swapFields';
6
import convertImgsToBlocks from './utils/convertImgsToBlocks';
7
import { Client, SimpleSchemaTypes } from '@datocms/cli/lib/cma-client-node';
8

9
type HtmlArticleType = SimpleSchemaTypes.Item & {
10
  title: string;
11
  content: string;
12
};
13

14
export default async function convertHtmlArticles(client: Client) {
15
  const modelIds = await getModelIdsByApiKey(client);
16

17
  await createStructuredTextFieldFrom(client, 'html_article', 'content', [
18
    modelIds.image_block.id,
19
  ]);
20

21
  const records = (await getAllRecords(
22
    client,
23
    'html_article',
24
  )) as HtmlArticleType[];
25

26
  for (const record of records) {
27
    const structuredTextContent = await htmlToStructuredText(
28
      record.content,
29
      convertImgsToBlocks(client, modelIds),
30
    );
31
    await client.items.update(record.id, {
32
      structured_text_content: structuredTextContent,
33
    });
34
    if (record.meta.status !== 'draft') {
35
      await client.items.publish(record.id);
36
    }
37
  }
38

39
  await swapFields(client, 'html_article', 'content');
40
}

A couple of notes:

Inside the HTML field there might be image tags (<img />). Structured Text does not have a specific node to handle images because it offers block nodes, which is a more powerful primitive. This means that, during the transformation process, we'll need to convert those <img /> tags into block records of type "Image" (that's the same block currently used by the Modular Content field). For this reason, in line 19 we pass the image_block model ID to configure the newly created Structured Text field to accept such type of blocks;
In the highlighted lines we're going to perform the actual records update and make sure we republish updated records (unless they were in draft).

So what is left to do is to implement the htmlToStructuredText() function.

The datocms-html-to-structured-text package offers a parse5ToStructuredText function that is meant to be used in NodeJS environments to perform the conversion from HTML to Structured Text (parse5 is a popular HTML parser for NodeJS).

Internally, the parse5ToStructuredText will take the parse5 Document, convert it into a hast tree, and then convert the hast tree into a dast tree (that's the format of our Structured Text document). All these conversions might seem an overkill, but we will see later how having hast as an intermediate representation will come in handy.

Let's install some dependencies:

npm install --save-dev parse5 \
            datocms-html-to-structured-text \
            datocms-structured-text-utils \
            unist-utils-core@1.0.5

Now we have everything we need to build our htmlToStructuredText function:

1
import { parse } from 'parse5';
2
import {
3
  parse5ToStructuredText,
4
  Options,
5
} from 'datocms-html-to-structured-text';
6
import { validate } from 'datocms-structured-text-utils';
7

8
export default async function htmlToStructuredText(
9
  html: string,
10
  settings: Options,
11
) {
12
  if (!html) {
13
    return null;
14
  }
15

16
  const result = await parse5ToStructuredText(
17
    parse(html, {
18
      sourceCodeLocationInfo: true,
19
    }),
20
    settings,
21
  );
22

23
  const validationResult = validate(result);
24

25
  if (!validationResult.valid) {
26
    throw new Error(validationResult.message);
27
  }
28

29
  return result;
30
}

Please note that in the highlighted line we use the validate function from the datocms-structured-text-utils package to make sure that the final result is valid Structured Text.

Converting image tags into blocks

The code above will convert 99% of the HTML correctly, but images present in the content will be skipped.

As we already noted before, that's because Structured Text does not have a specific node to handle images. Instead, it offers block nodes, which can handle images and much more. We have to pass some additional settings to the parse5ToStructuredText function to tell it how to convert <img /> tags to block nodes:

1
import {
2
  buildBlockRecord,
3
  Client,
4
  SimpleSchemaTypes,
5
} from '@datocms/cli/lib/cma-client-node';
6
import { visit, find } from 'unist-utils-core';
7
import {
8
  HastNode,
9
  HastElementNode,
10
  CreateNodeFunction,
11
  Context,
12
} from 'datocms-html-to-structured-text';
13
import { Options } from 'datocms-html-to-structured-text';
14
import findOrCreateUploadWithUrl from './findOrCreateUploadWithUrl';
15

16
export default function convertImgsToBlocks(
17
  client: Client,
18
  modelIds: Record<string, SimpleSchemaTypes.ItemType>,
19
): Options {
20
  return {
21
    preprocess: (tree: HastNode) => {
22
      const liftedImages = new WeakSet();
23

24
      const body = find(
25
        tree,
26
        (node: HastNode) =>
27
          (node.type === 'element' && node.tagName === 'body') ||
28
          node.type === 'root',
29
      );
30

31
      visit<HastNode, HastElementNode & { children: HastNode[] }>(
32
        body,
33
        (node, index, parents) => {
34
          if (
35
            node.type !== 'element' ||
36
            node.tagName !== 'img' ||
37
            liftedImages.has(node) ||
38
            parents.length === 1
39
          ) {
40
            return;
41
          }
42

43
          const imgParent = parents[parents.length - 1];
44
          imgParent.children.splice(index, 1);
45

46
          let i = parents.length;
47
          let splitChildrenIndex = index;
48
          let childrenAfterSplitPoint: HastNode[] = [];
49

50
          while (--i > 0) {
51
            const parent = parents[i];
52
            const parentsParent = parents[i - 1];
53

54
            childrenAfterSplitPoint =
55
              parent.children.splice(splitChildrenIndex);
56
            splitChildrenIndex = parentsParent.children.indexOf(parent);
57

58
            let nodeInserted = false;
59

60
            if (i === 1) {
61
              splitChildrenIndex += 1;
62
              parentsParent.children.splice(splitChildrenIndex, 0, node);
63
              liftedImages.add(node);
64

65
              nodeInserted = true;
66
            }
67

68
            splitChildrenIndex += 1;
69

70
            if (childrenAfterSplitPoint.length > 0) {
71
              parentsParent.children.splice(splitChildrenIndex, 0, {
72
                ...parent,
73
                children: childrenAfterSplitPoint,
74
              });
75
            }
76

77
            if (parent.children.length === 0) {
78
              splitChildrenIndex -= 1;
79
              parentsParent.children.splice(
80
                nodeInserted ? splitChildrenIndex - 1 : splitChildrenIndex,
81
                1,
82
              );
83
            }
84
          }
85
        },
86
      );
87
    },
88
    // now that images are top-level, convert them into `block` dast nodes
89
    handlers: {
90
      img: async (
91
        createNode: CreateNodeFunction,
92
        node: HastNode,
93
        _context: Context,
94
      ) => {
95
        if (node.type !== 'element' || !node.properties) {
96
          return;
97
        }
98

99
        const { src: url } = node.properties;
100
        const upload = await findOrCreateUploadWithUrl(client, url);
101

102
        return createNode('block', {
103
          item: buildBlockRecord({
104
            item_type: { id: modelIds.image_block.id, type: 'item_type' },
105
            image: {
106
              upload_id: upload.id,
107
            },
108
          }),
109
        });
110
      },
111
    },
112
  };
113
}

A couple notes:

We use the handlers option to specify how to convert the <img /> hast nodes tags to dast block nodes (the default behavior, as we saw, is to simply skip them);
The block node should contain a block record of type Image (that's the same block currently used by the Modular Content field), which in turn has a single-asset image field. In line 79 we create a new asset starting from the src tag of the image, to feed it to the image field. Luckily, the handlers are async functions, so we can easily perform an asyncronous operation inside of it.
Since in the dast format, a block node can only be at root level, we use the preprocess option to tweak the hast tree and lift every image node up to the root (in case they're inside paragraphs or other tags).

We can test the migration with the following command from the Terminal, which will clone the primary environment into a sandbox, and run the migration:

datocms migrations:run --destination=with-structured-text
✔ Running 1612281851_convertHtmlArticles.ts...
Done!

Success! The article content is correctly converted to structured text.

Migrating Markdown content

Once we know how to perform the HTML-to-Structured-Text conversion, we only have to do some minor changes to make it work also for Markdown content.

As we just saw, the datocms-html-to-structured-text package knows how to convert an hast tree (HTML) to a dast tree (Structured Text), so if we can convert a Markdown string to hast, then the rest of the code will be basically the same.

Luckily, hast is part of the unified ecosystem, which also includes:

an analogue specification for representing Markdown in a syntax tree called mdast;
a tool to convert Markdown strings to mdast;
a tool to convert mdast trees to hast.

Let's install all the packages we need:

npm install --save-dev unified@9 remark-parse@9 mdast-util-to-hast@10

We can now create a function similar to htmlToStructuredText called markdownToStructuredText that connects all the dots:

1
import unified from 'unified';
2
import toHast from 'mdast-util-to-hast';
3
import parse from 'remark-parse';
4
import {
5
  hastToStructuredText,
6
  Options,
7
  HastRootNode,
8
} from 'datocms-html-to-structured-text';
9
import { validate } from 'datocms-structured-text-utils';
10

11
export default async function markdownToStructuredText(
12
  markdown: string,
13
  options: Options,
14
) {
15
  if (!markdown) {
16
    return null;
17
  }
18

19
  const mdastTree = unified().use(parse).parse(markdown);
20
  const hastTree = toHast(mdastTree) as HastRootNode;
21
  const result = await hastToStructuredText(hastTree, options);
22

23
  const validationResult = validate(result);
24

25
  if (!validationResult.valid) {
26
    throw new Error(validationResult.message);
27
  }
28

29
  return result;
30
}

We can now create a new migration script:

> datocms migrations:new convertMarkdownArticles
Created migrations/1612340785_convertMarkdownArticles.ts

And basically copy the previous migration, just replacing the name of the model (from html_article to markdown_article), and the call to htmlToStructuredText with a call to markdownToStructuredText:

1
import getModelIdsByApiKey from './utils/getModelIdsByApiKey';
2
import createStructuredTextFieldFrom from './utils/createStructuredTextFieldFrom';
3
import markdownToStructuredText from './utils/markdownToStructuredText';
4
import convertImgsToBlocks from './utils/convertImgsToBlocks';
5
import getAllRecords from './utils/getAllRecords';
6
import swapFields from './utils/swapFields';
7
import { Client, SimpleSchemaTypes } from '@datocms/cli/lib/cma-client-node';
8

9
type MdArticleType = SimpleSchemaTypes.Item & {
10
  title: string;
11
  content: string;
12
};
13
export default async function (client: Client) {
14
  const modelIds = await getModelIdsByApiKey(client);
15

16
  await createStructuredTextFieldFrom(client, 'markdown_article', 'content', [
17
    modelIds.image_block.id,
18
  ]);
19

20
  const records = (await getAllRecords(
21
    client,
22
    'markdown_article',
23
  )) as MdArticleType[];
24

25
  for (const record of records) {
26
    const structuredTextContent = await markdownToStructuredText(
27
      record.content,
28
      convertImgsToBlocks(client, modelIds),
29
    );
30
    await client.items.update(record.id, {
31
      structured_text_content: structuredTextContent,
32
    });
33
    if (record.meta.status !== 'draft') {
34
      await client.items.publish(record.id);
35
    }
36
  }
37

38
  await swapFields(client, 'markdown_article', 'content');
39
}

We can now run the new migration inside the sandbox environment we already created for the first migration:

> datocms migrations:run --source=with-structured-text --in-place
✔ Running 1612340785_convertMarkdownArticles.ts...
Done!

Migrating Modular Content fields

To migrate Modular Content fields into Structured Text fields, we must acknowledge the fact that both fields allow nested record blocks: the difference between the two is that Modular Content is basically an array of record blocks, while in Structed Text record blocks are inside the dast tree in nodes of type block. In other words, our task here is, for every modular content, to transform an array of block records into a single dast document. It's up to us to decide how to convert each block we encounter into one/many nodes into our dast document.

Let's take a look at the project schema again:

The existing Modular Content field supports three block types:

Text (which in turn contains a text Markdown field);
Code (which has two fields, one that contains the actual code and another that stores the language);
Image (which, as we already know, it contains a single-asset field called image).

Here's the code for our migration:

1
import { Document, Node, validate } from 'datocms-structured-text-utils';
2
import getModelIdsByApiKey from './utils/getModelIdsByApiKey';
3
import createStructuredTextFieldFrom from './utils/createStructuredTextFieldFrom';
4
import getAllRecords from './utils/getAllRecords';
5
import swapFields from './utils/swapFields';
6
import markdownToStructuredText from './utils/markdownToStructuredText';
7
import convertImgsToBlocks from './utils/convertImgsToBlocks';
8
import { Client, SimpleSchemaTypes } from '@datocms/cli/lib/cma-client-node';
9

10
type ModularArticleType = SimpleSchemaTypes.Item & {
11
  title: string;
12
  content: any;
13
};
14

15
export default async function (client: Client) {
16
  const modelIds = await getModelIdsByApiKey(client);
17

18
  await createStructuredTextFieldFrom(
19
    client,
20
    'modular_content_article',
21
    'content',
22
    [modelIds.image_block.id, modelIds.text_block.id, modelIds.code_block.id],
23
  );
24

25
  const records = (await getAllRecords(
26
    client,
27
    'modular_content_article',
28
  )) as ModularArticleType[];
29

30
  for (const record of records) {
31
    const rootNode = {
32
      type: 'root',
33
      children: [] as Node[],
34
    };
35

36
    for (const block of record.content) {
37
      switch (block.relationships.item_type.id) {
38
        case modelIds.text_block.id: {
39
          const markdownSt = await markdownToStructuredText(
40
            block.text,
41
            convertImgsToBlocks(client, modelIds),
42
          );
43

44
          if (markdownSt) {
45
            rootNode.children = [
46
              ...rootNode.children,
47
              ...markdownSt.document.children,
48
            ];
49
          }
50
          break;
51
        }
52

53
        case modelIds.code_block.id: {
54
          rootNode.children.push({
55
            type: 'code',
56
            language: block.language,
57
            code: block.code,
58
          });
59
          break;
60
        }
61
        default: {
62
          delete block.id;
63
          delete block.meta;
64
          delete block.createdAt;
65
          delete block.updatedAt;
66

67
          rootNode.children.push({
68
            type: 'block',
69
            item: block,
70
          });
71
          break;
72
        }
73
      }
74
    }
75

76
    const result = {
77
      schema: 'dast',
78
      document: rootNode,
79
    } as Document;
80

81
    const validationResult = validate(result);
82

83
    if (!validationResult.valid) {
84
      throw new Error(validationResult.message);
85
    }
86

87
    await client.items.update(record.id, {
88
      structured_text_content: result,
89
    });
90

91
    if (record.meta.status !== 'draft') {
92
      await client.items.publish(record.id);
93
    }
94
  }
95

96
  await swapFields(client, 'modular_content_article', 'content');
97
}

Every time we need to convert a Modular Content field, we start by creating an empty Dast root node (that is, one with no children, line 33).

Then, for every block contained in the modular content (line 38), we're going to accumulate children inside the root node:

If it is a Text block (line 40), we use the markdownToStructuredText function to convert its Markdown content into a Dast tree, then take the children of the resulting root node and add them to our accumulator;
Since Dast supports nodes of type code, if we encounter a Code block (line 55), we simply convert it to code node, and add it to the accumulator;
If we find an Image block (line 63), we'll wrap the block into a Dast block node, and add it to the accumulator as it is.

Wrapping up

Once you get to know the Structured Text format, it becomes quite straightforward converting from/to its Dast tree representation of nodes, and the DatoCMS API, coupled with migrations/sandbox environments, makes it easy to perform any kind of treatment to your content.

You can download the final code from this GitHub repo.

Did this doc help you?

Need help?

Explore our forum, contact support, or connect with our sales team . You can also chat live with other users in our Slack channel.