npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@moxy/react-contentful-rich-text

v1.0.0

Published

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

Downloads

17

Readme

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.

Installation

$ 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.

Motivation

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.

Usage

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

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

const entryMap = {
    myContentType1: ContentType1,
};

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

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';

Styling

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"] { ... }
}

API

The following props are available for the RichText component.

data

Type: object | Required: false

Rich text field value.

Example:

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

entryMap

Type: object | Required: false

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

Example:

{
    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.

className

Type: string | Required: false

A className to apply to the component.

Tests

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

Demo

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.

FAQ

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.

License

Released under the MIT License.