Next.js > Structured Text fields

    Structured Text fields

    Rich text in DatoCMS is stored in Structured Text fields, which lets us use it in many different contexts, from HTML in the browser to speech fulfillments in voice interfaces, if that's what you want.

    There's a lot to be said about Structured Text and the extensibility of it, but for now let's just say that it returns content in a particular JSON format called dast which will resemble this example:

    {
    "schema": "dast",
    "document": {
    "type": "root",
    "children": [
    {
    "type": "heading",
    "level": 1,
    "children": [
    {
    "type": "span",
    "marks": [],
    "value": "Hello world!"
    }
    ]
    }
    ]
    }
    }

    To make it easy to convert this format in HTML inside your Next.js projects, we released a package called react-datocms that exposes a <StructuredText /> component that does all the tedious work for you.

    To take advantage of it, install the react-datocms package if you haven't already:

    yarn add react-datocms

    Then, inside your page, make a GraphQL query to fetch a Structured Text field, and feed the result to the data prop of a <StructuredText /> component:

    import { request } from "../lib/datocms";
    import { StructuredText } from "react-datocms";
    const HOMEPAGE_QUERY = `query HomePage($limit: IntType) {
    allBlogPosts(first: $limit) {
    id
    title
    content {
    value
    }
    }
    }`;
    export async function getStaticProps() {
    const data = await request({
    query: HOMEPAGE_QUERY,
    variables: { limit: 10 }
    });
    return {
    props: {
    data
    }
    };
    }
    export default function Home({ data }) {
    return (
    <div>
    {data.allBlogPosts.map(blogPost => (
    <article key={blogPost.id}>
    <h6>{blogPost.title}</h6>
    <StructuredText data={blogPost.content} />
    </article>
    ))}
    </div>
    );
    }

    Rendering special nodes

    Other than "regular" formatting nodes (paragraphs, lists, etc.), Structured Text documents can contain three special types of node:

    • itemLink nodes are just like regular HTML hyperlinks, but point to other records instead of URLs;

    • inlineItem nodes lets you directly embed a reference to a record in-between regular text;

    • block nodes lets you embed a DatoCMS block record in-between regular paragraphs;

    If a Structured Text document contains one of these nodes, then we need to change the GraphQL query, so that we also fetch all the records and blocks it references. As an example, if the field can link to other Blog posts, and can embed blocks of type "Image block", then the query should change like this:

    const HOMEPAGE_QUERY = `query HomePage($limit: IntType) {
    allBlogPosts(first: $limit) {
    id
    title
    content {
    value
    blocks {
    __typename
    ... on ImageBlockRecord {
    id
    image { url alt }
    }
    }
    links {
    __typename
    ... on BlogPostRecord {
    id
    slug
    title
    }
    }
    }
    }
    }`;

    We also need to tell <StructuredText /> how you want such nodes to be rendered:

    return (
    <StructuredText
    data={blogPost.content}
    renderInlineRecord={({ record }) => {
    switch (record.__typename) {
    case "BlogPostRecord":
    return <a href={`/blog/${record.slug}`}>{record.title}</a>;
    default:
    return null;
    }
    }}
    renderLinkToRecord={({ record, children }) => {
    switch (record.__typename) {
    case "BlogPostRecord":
    return <a href={`/blog/${record.slug}`}>{children}</a>;
    default:
    return null;
    }
    }}
    renderBlock={({ record }) => {
    switch (record.__typename) {
    case "ImageBlockRecord":
    return <img src={record.image.url} alt={record.image.alt} />;
    default:
    return null;
    }
    }}
    />
    );