Skip to main content
Community Plugin
View plugin on GitHub
See starters using this

gatsby-source-prismic

Source plugin for pulling data into Gatsby from prismic.io repositories.

Table of Contents

Features

  • Supports Rich Text fields, slices, and content relation fields
  • Supports gatsby-image using Imgix or gatsby-transformer-sharp for image fields
  • Utilizes prismic-dom to provide HTML and link values so you don’t have to use prismic-dom directly
  • Supports Prismic previews and automatically adds the Prismic Toolbar

Install

npm install --save gatsby-source-prismic

Migration Guide

Read the migration guide to learn why and how to upgrade from v2 to v3. Then read the previews guide to learn how to setup previews.

How to use

// In your gatsby-config.js
plugins: [
  /*
   * Gatsby's data processing layer begins with “source”
   * plugins. Here the site sources its data from prismic.io.
   */
  {
    resolve: 'gatsby-source-prismic',
    options: {
      // The name of your prismic.io repository. This is required.
      // Example: 'gatsby-source-prismic-test-site' if your prismic.io address
      // is 'gatsby-source-prismic-test-site.prismic.io'.
      repositoryName: 'gatsby-source-prismic-test-site',

      // An API access token to your prismic.io repository. This is optional.
      // You can generate an access token in the "API & Security" section of
      // your repository settings. Setting a "Callback URL" is not necessary.
      // The token will be listed under "Permanent access tokens".
      accessToken: 'example-wou7evoh0eexuf6chooz2jai2qui9pae4tieph1sei4deiboj',

      // If you provide a release ID, the plugin will fetch data from Prismic
      // for a specific release. A Prismic release is a way to gather a
      // collection of changes for a future version of your website. Note that
      // if you add changes to a release, you'll need to rebuild your website
      // to see them.
      // See: https://user-guides.prismic.io/en/collections/22653-releases-scheduling#the-basics-of-a-release
      releaseID: 'example-eiyaingiefahyi7z',

      // Set a link resolver function used to process links in your content.
      // Fields with rich text formatting or links to internal content use this
      // function to generate the correct link URL.
      // The document node, field key (i.e. API ID), and field value are
      // provided to the function, as seen below. This allows you to use
      // different link resolver logic for each field if necessary.
      // See: https://prismic.io/docs/javascript/query-the-api/link-resolving
      linkResolver: ({ node, key, value }) => (doc) => {
        // Your link resolver
      },

      // Set a list of links to fetch and be made available in your link
      // resolver function.
      // See: https://prismic.io/docs/javascript/query-the-api/fetch-linked-document-fields
      fetchLinks: [
        // Your list of links
      ],

      // Set an HTML serializer function used to process formatted content.
      // Fields with rich text formatting use this function to generate the
      // correct HTML.
      // The document node, field key (i.e. API ID), and field value are
      // provided to the function, as seen below. This allows you to use
      // different HTML serializer logic for each field if necessary.
      // See: https://prismic.io/docs/nodejs/beyond-the-api/html-serializer
      htmlSerializer: ({ node, key, value }) => (
        type,
        element,
        content,
        children,
      ) => {
        // Your HTML serializer
      },

      // Provide an object of Prismic custom type JSON schemas to load into
      // Gatsby. This is required.
      schemas: {
        // Your custom types mapped to schemas
      },

      // Set a default language when fetching documents. The default value is
      // '*' which will fetch all languages.
      // See: https://prismic.io/docs/javascript/query-the-api/query-by-language
      lang: '*',

      // Add the Prismic Toolbar script to the site. Defaults to false.
      // Set to "legacy" if your repository requires the older toolbar script.
      // See: https://prismic.io/docs/rest-api/beyond-the-api/the-preview-feature
      prismicToolbar: true,

      // Set a function to determine if images are downloaded locally and made
      // available for gatsby-transformer-sharp for use with gatsby-image.
      // The document node, field key (i.e. API ID), and field value are
      // provided to the function, as seen below. This allows you to use
      // different logic for each field if necessary.
      // This defaults to always return false.
      shouldDownloadImage: ({ node, key, value }) => {
        // Return true to download the image or false to skip.
      },

      // Provide a default set of Imgix image transformations applied to
      // Imgix-backed gatsby-image fields. These options will override the
      // defaults set by Prismic.
      // See: https://docs.imgix.com/apis/url
      imageImgixParams: {
        auto: 'compress,format',
        fit: 'max',
        q: 50,
      },

      // Provide a default set of Imgix image transformations applied to
      // the placeholder images of Imgix-backed gatsby-image fields. These
      // parameters will be applied over those provided in the above
      // `imageImgixParams` option.
      // See: https://docs.imgix.com/apis/url
      imagePlaceholderImgixParams: {
        w: 100,
        blur: 15,
        q: 50,
      },

      // Set the prefix for the filename where type paths for your schemas are
      // stored. The filename will include the MD5 hash of your schemas after
      // the prefix.
      // This defaults to 'prismic-typepaths---${repositoryName}'.
      typePathsFilenamePrefix:
        'prismic-typepaths---gatsby-source-prismic-test-site',
    },
  },
]

Providing JSON schemas

In order for Gatsby to know about your Prismic custom types, you must provide the full JSON schema of each custom type. This is done via the plugin’s schemas option in gatsby-config.js.

The recommended approach is to create a schemas directory in your project and import them into your gatsby-config.js file.

// In your gatsby-config.js
plugins: [
  {
    resolve: 'gatsby-source-prismic',
    options: {
      // ...
      schemas: {
        page: require('./src/schemas/page.json'),
        blog_post: require('./src/schemas/blog_post.json'),
      },
      // ...
    },
  },
]

Each schema file should be populated with the contents of the “JSON editor” tab in the Prismic Custom Type editor.

Note: The names of your schemas in the schemas object should be exactly the same as your custom type’s API ID. For example, if your API ID is ”blog-post”, your key should be ”blog-post”, not ”blog_post“.

See the official docs for more details on version controlling your custom types: How to version custom types.

How to query

You can query nodes created from Prismic using GraphQL like the following:

Note: Learn to use the GraphQL tool and Ctrl+Spacebar at http://localhost:8000/___graphql to discover the types and properties of your GraphQL model.

{
  allPrismicPage {
    edges {
      node {
        id
        uid
        first_publication_date
        last_publication_date
        data {
          title {
            text
          }
          content {
            html
          }
        }
      }
    }
  }
}

All documents are pulled from your repository and created as prismic${contentTypeName} and allPrismic${contentTypeName}, where ${contentTypeName} is the API ID of your document’s content type.

For example, if you have Product as one of your content types, you will be able to query it like the following:

{
  allPrismicProduct {
    edges {
      node {
        id
        data {
          name
          price
          description {
            html
          }
        }
      }
    }
  }
}

Query Rich Text fields

Data from fields with rich text formatting (e.g. headings, bold, italic) is transformed to provide HTML and text versions. This uses the official prismic-dom library and the linkResolver and htmlSerializer functions from your site’s gatsby-node.js to create the HTML and text fields.

Note: If you need to access the raw data, the original data is accessible using the raw field, though use of this field is discouraged.

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          title {
            text
          }
          content {
            html
          }
        }
      }
    }
  }
}

Link fields are processed using the official prismic-dom library and the linkResolver function from your site’s gatsby-config.js. The resolved URL is provided at the url field.

If the link type is a web link (i.e. a URL external from your site), the URL is provided without additional processing.

All other URL fields, such as target, lang, and isBroken, are provided on the field, as well.

The target field defaults to an empty string. This allows you to always query the target field even if it is not set in Prismic.

Note: If you need to access the raw data, the original data is accessible using the raw field, though use of this field is discouraged.

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          featured_post {
            url
            target
          }
        }
      }
    }
  }
}

Query Image fields

Prismic allows setting multiple images for a single image field with optional constraints. This is useful when different versions of an image are required based on its surrouding context. One such example could be a responsive image where a different image may be necessary on smaller or larger screens.

Image thumbnails are available on the thumbnail field of all image fields.

See the official docs for more details on configuring thumbnails on your custom types: How to set up responsive images.

See the Image processing section to learn how to enable Gatsby Image support.

{
  allPrismicPage {
    edges {
      nodes {
        data {
          image_field {
            url
            thumbnails {
              thumbnail_name {
                url
              }
            }
          }
        }
      }
    }
  }
}

Query Content Relation fields

Content Relation fields relate a field to another document. Since fields from within the related document is often needed, the document data is provided at the document field. The resolved URL to the document using the official prismic-dom library and the linkResolver function from your site’s gatsby-node.js is also provided at the url field.

Querying data on the document field is handled the same as querying slices. Please read the Query slices section for details.

Note: If you need to access the raw data, the original data is accessible using the raw field, though use of this field is discouraged.

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          featured_post {
            url
            document {
              __typename
              ... on PrismicPost {
                data {
                  title {
                    text
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

Query slices

Prismic slices allow you to build a flexible series of content blocks. Since the content structure is dynamic, querying the content is handled differently than other fields.

To access slice fields, you need to use GraphQL inline fragments. This requires you to know types of nodes. The easiest way to get the type of nodes is to use the /___graphql debugger and run the below query (adjust the document type and field name).

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          body {
            __typename
          }
        }
      }
    }
  }
}

When you have node type names, you can use them to create inline fragments.

Full example:

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          body {
            __typename
            ... on PrismicPageBodyRichText {
              text {
                html
              }
            }
            ... on PrismicPageBodyQuote {
              quote {
                html
              }
              credit {
                text
              }
            }
            ... on PrismicPageBodyFootnote {
              content {
                html
              }
            }
          }
        }
      }
    }
  }
}

Query direct API data as a fallback

If you find you cannot query the data you need through the GraphQL interface, you can get the raw response from the prismic-javascript API using the dataString field.

This field contains the whole node’s original data before processing as a string generated using JSON.stringify.

This is absolutely discouraged as it defeats the purpose of Gatsby’s GraphQL data interface, but it is available if necessary

{
  allPrismicPage {
    edges {
      node {
        id
        dataString
      }
    }
  }
}

Image processing

You can process images using one of the following methods:

  • Recommended: On-the-fly transformed using Imgix: Images are not downloaded to your computer or server and instead are transformed using Prismic’s Imgix integration to resize images on-the-fly.
  • Locally transformed at build-time: Images are downloaded to your computer or server which resizes images at build-time.

You can apply image processing to any image field and its thumbnails on a document. Image processing of inline images added to Rich Text fields is currently not supported.

Using Imgix transformed images

Using this method, images are manipulated on Imgix’s servers at request time, eliminating the need to download and resize images on your computer or server.

To access image processing in your queries, you need to use this pattern, where ...ImageFragment is one of the following fragments:

  • GatsbyPrismicImageFixed
  • GatsbyPrismicImageFixed_noBase64
  • GatsbyPrismicImageFluid
  • GatsbyPrismicImageFluid_noBase64

Learn about the different types of responsive images and fragments from gatsby-image’s official docs.

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          imageFieldName {
            fluid {
              ...ImageFragment
            }
          }
        }
      }
    }
  }
}

Full example:

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          imageFieldName {
            fluid(maxWidth: 1000, maxHeight: 800) {
              ...GatsbyPrismicImageFluid
            }
          }
        }
      }
    }
  }
}

Using locally transformed images

To use local image processing, you need gatsby-transformer-sharp, gatsby-plugin-sharp, and their dependencies gatsby-image and gatsby-source-filesystem in your gatsby-config.js.

Note that this will incur additional build time as image processing is time-consuming.

In your gatsby-config.js file, set the shouldDownloadImage plugin option to a function that returns true for images requiring local transformations.

// In your gatsby-config.js
plugins: [
  {
    resolve: 'gatsby-source-prismic',
    options: {
      // Along with your other options...

      // Set a function to determine if images are downloaded locally and made
      // available for gatsby-transformer-sharp for use with gatsby-image.
      // The document node, field key (i.e. API ID), and field value are
      // provided to the function, as seen below. This allows you to use
      // different logic for each field if necessary.
      // This defaults to always return false.
      shouldDownloadImage: ({ node, key, value }) => {
        // Return true to download the image or false to skip.
        return true
      },
    },
  },
]

To access image processing in your queries, you need to use this pattern, where ...ImageFragment is one of the gatsby-transformer-sharp fragments:

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          imageFieldName {
            localFile {
              childImageSharp {
                ...ImageFragment
              }
            }
          }
        }
      }
    }
  }
}

Full example:

{
  allPrismicPage {
    edges {
      node {
        id
        data {
          imageFieldName {
            localFile {
              childImageSharp {
                fixed(width: 500, height: 300) {
                  ...GatsbyImageSharpFixed_withWebp
                }
              }
            }
          }
        }
      }
    }
  }
}

To learn more about local image processing, check the documentation of gatsby-plugin-sharp.

Previews

gatsby-source-prismic provides a way to preview document changes directly from Prismic without rebuilding your site. By rendering previews client-side, we can retain the benefits of Gatsby’s HTML pre-rendering while still provding the dynamic and rich content editing experience of a traditional server setup.

For an in-depth guide on using previews, please refer to this guide.

Releases

You can provide a releaseID option to build a release version of your website. See the How to use section for a description of the option. To learn more about Prismic releases, see Prismic’s official documentation here: The basics of a release.

You can get a release ID by using the Prismic REST API:

curl https://my-repository-name.prismic.io/api/v2
# =>
#   {
#     "refs": [
#       {
#         "id": "master",
#         "ref": "XoS0aRAAAB8AmarD",
#         "label": "Master",
#         "isMasterRef": true
#       },
#       {
#         "id": "Xny9FRAAAB4AdbNo",
#         "ref": "Xr024BEAAFNM2PNM~XoS0aRAAAB8AmarD",
#         "label": "My release"
#       }
#       ...
#     ],
#   }

In the refs array of the response, the id property of the refs object is a release ID. The label identifies the release’s purpose. Master, for example, is the latest published version of all your documents. Your other Prismic Releases will be listed here with their names.

Note that a release build is totally compatible with the preview system explained in the preview guide. Using a releaseID is a way to view at once another version of your website, but under the hood it works the same way as the default build. So you can preview a draft of one document of your release just like you would do with the master version.

Limitations

GraphQL-valid field names

All field names must adhere to GraphQL’s field name requirements:

  • a-z: Any lowercase letter.
  • A-Z: Any uppercase letter.
  • 0-9: Any number. Name must not start with a number.
  • _: Underscores

Note that this does not allow fields containing the following:

  • Starting with a number (e.g. 0_my_field)
  • Dashes (e.g. my-field)
  • Symbols (e.g. !@#$%^&*())

Site’s gatsby-node.js example

const path = require('path')

exports.createPages = async ({ graphql, actions }) => {
  const { createPage } = actions

  // Query all Pages with their IDs and template data.
  const pages = await graphql(`
    {
      allPrismicPage {
        nodes {
          id
          uid
          data {
            template
          }
        }
      }
    }
  `)

  const pageTemplates = {
    Light: path.resolve(__dirname, 'src/templates/light.js'),
    Dark: path.resolve(__dirname, 'src/templates/dark.js'),
  }

  // Create pages for each Page in Prismic using the selected template.
  pages.data.allPrismicPage.nodes.forEach((node) => {
    createPage({
      path: `/${node.uid}`,
      component: pageTemplates[node.template],
      context: {
        id: node.id,
      },
    })
  })
}