A react component that transforms a Contentful rich text structure to html

Usage no npm install needed!

<script type="module">
  import moxyReactContentfulRichText from 'https://cdn.skypack.dev/@moxy/react-contentful-rich-text';



NPM version Downloads Build Status Coverage Status Dependency status Dev Dependency status

A react component that transforms a contentful rich text structure to HTML.


$ npm install @moxy/react-contentful-rich-text

This library is written in modern JavaScript and is published in both CommonJS and ES module transpiled variants. If you target older browsers please make sure to transpile accordingly.


Content Management Systems (CMS) usually provide a custom text field that lets users define headings, font styles, lists, quotes, links, assets and many more.

Each CMS provides this rich text in a specific format, usually a data structure in json, to be interpreted. Contentful is one of those content management systems.

In common use cases, rich text data must be represented as HTML. Based on this use cases, there should be an easier way to render Contentful rich text as HTML.


import React from 'react';
import RichText from '@moxy/react-contentful-rich-text';

const ContentType1 = ({ inline, data }) => (
        <h2>{ data.fields.title }</h2>
        <p>{ data.fields.description }</p>

const entryMap = {
    myContentType1: ContentType1,

const MyComponent = ({ richTextField }) => (
    <div className="container">
        <RichText data={ richTextField } entryMap={ entryMap }/>

export default MyComponent;

Import the styleguide base styles in the app's entry CSS file:

@import "@moxy/react-contentful-rich-text/dist/index.css";

..or in your entry JavaScript file:

import '@moxy/react-contentful-rich-text/dist/index.css';


Each HTML element will be rendered with a data attribute data-type to provide an easier way to style them.

.myReactContentfulRichText {
    & [data-type="paragraph"] {
        margin: 1em 0;

    & [data-type="text"] {
        font-size: 14px;

    & [data-type="heading-1"] { ... }
    & [data-type="heading-2"] { ... }
    & [data-type="heading-3"] { ... }
    & [data-type="heading-4"] { ... }
    & [data-type="heading-5"] { ... }
    & [data-type="heading-6"] { ... }
    & [data-type="bold"] { ... }
    & [data-type="italic"] { ... }
    & [data-type="underline"] { ... }
    & [data-type="code"] { ... }
    & [data-type="multi-code"] { ... }
    & [data-type="unordered-list"] { ... }
    & [data-type="ordered-list"] { ... }
    & [data-type="list-item"] { ... }
    & [data-type="hyperlink"] { ... }
    & [data-type="asset-hyperlink"] { ... }
    & [data-type="email-hyperlink"] { ... }
    & [data-type="blockquote"] { ... }
    & [data-type="thematic-break"] { ... }
    & [data-type="image"] { ... }
    & [data-type="video"] { ... }


The following props are available for the RichText component.


Type: object | Required: false

Rich text field value.


    "nodeType": "document",
    "data": {},
    "content": [...],


Type: object | Required: false

Map of Contentful content types to react components. Required to render embedded entries.


    myContentType1: ContentType1
    myContentType2: ContentType2

Where myContentType# is the id of a content type and ContentType# is a react component that will receive the data from an entry of that content type.

The react component will also receive a boolean inline prop that details if an embedded entry should be rendered inline.


Type: string | Required: false

A className to apply to the component.


$ npm test
$ npm test -- --watch # during development


A demo Next.js project is available in the /demo folder so you can try out this component.

First, build the react-contentful-rich-text project with:

$ npm run build

To run the demo, do the following inside the demo's folder:

$ npm i
$ npm run dev

Note: Everytime a change is made to the package a rebuild is required to reflect those changes on the demo.


I can't override the component's CSS, what's happening?

There is an ongoing next.js issue about the loading order of modules and global CSS in development mode. This has been fixed in v9.3.6-canary.0, so you can either update next.js to a version higher than v9.3.5, or simply increase the CSS specificity when overriding component's classes, as we did in the demo, e.g. having the page or section CSS wrap the component's one.


Released under the MIT License.