Skip to main content
Version: 2.x

Embed Fields

Embed fields allows you to add a valid oEmbed URL, like YouTube, Vimeo, or Spotify, to generate embedded HTML content, or add your own custom embed content. This guide explains how the default implementation work and how to customize it.

In Front-Commerce we expose the embed fields in two ways;

In this section we will cover how to implement both of these methods, and how to implement your own custom embed fields.


you can read more about the oEmbed format and view a list of supported providers on the oEmbed website.

Standalone Embed Fields

You can learn how to configure an embed field in the prismic documentation.

For this example let's say we want to create an album cover from an embed field.

Adding an Embed Field in your server-side

First add an embed field in your schema using the oEmbedContent type, for example:

type MyAlbum {
title: String
cover: oEmbedContent

Then you can add the EmbedTransformer to your album definition which will parse the embed response from Prismic as a rich oEmbedContent type.

- const { TitleTransformer } = loaders.Prismic.transformers;
+ const { TitleTransformer, EmbedTransformer } = loaders.Prismic.transformers;

loaders.Prismic.defineContentTransformers("album", {
fieldTransformers: {
title: new TitleTransformer()
+ cover: new EmbedTransformer(),

Adding an Embed Field in your client-side

We have added a PrismicEmbed component to handle the embed response in you client side.

To simplify the usage between the component and the backend data we created a PrismicEmbedFragment which contains the minimum required data for the component, for example:

#import "theme/modules/Prismic/PrismicEmbed/PrismicEmbedFragment.gql"

fragment AlbumFragment on Album {
cover {

The fragment will expose several fields from the oEmbedContent type.

import PrismicEmbed from "theme/modules/prismic/PrismicEmbed";

const Album = (props) => {
return (
<PrismicEmbed content={props.cover} />

You can override the default components for each embed type in your own theme


As mentioned above, the fragment only exposes the minimum required fields for the PrismicEmbed component, if you would like to create your own custom embed component you can refer to all the available fields on the oEmbedContent type.

Wysiwyg Embed Fields


To benefit from this API, you first need to Configure the PrismicWysiwyg.

Example with PrismicWysiwyg

Update your schema to use the PrismicWysiwyg type instead of the DefaultWysiwyg.

type MyAlbum {
title: String
cover: oEmbedContent
- content: DefaultWysiwyg
+ content: PrismicWysiwyg

Then use the RichtextToWysiwygTransformer which will transform the Prismic Richtext to the Wysiwyg format.

- const { TitleTransformer } = loaders.Prismic.transformers;
+ const { TitleTransformer, RichtextToWysiwygTransformer } = loaders.Prismic.transformers;

loaders.Prismic.defineContentTransformers("album", {
fieldTransformers: {
title: new TitleTransformer()
+ content: new RichtextToWysiwygTransformer(loaders.Wysiwyg),

You can then follow the same steps form <WysiwygV2 /> usage to implement the Wysiwyg in your client-side.

Adding additional Embed loading scripts

We have added loader functions for the following embed scripts:

  • Twitter
  • Facebook
  • Instagram

You can update these loading functions or add your own by overriding the theme/modules/WysiwygV2/PrismicWysiwyg/Components/EmbedScript/appEmbeds.js file.

  • This file accepts a record with the key as the embed provider (case sensitive).
  • The value contains a load function and optionally an src if you would like to use a custom script.
const appEmbeds = {
// Add you custom embed script here eg:
Facebook: {
// this will override the `Facebook` script included by Front-Commerce
src: "", // optional src (it's not recommended to change this)
load: (ref) => {
// this is only triggered once the script load event is fired
if (typeof window !== "undefined" && window.FB) {

export default appEmbeds;

Custom or raw HTML embeds in Wysiwyg

To add custom or raw HTML as for EmbedFields you would need to make some customization to the PrismicWysiwyg.

First setup your Prismic Rich Text field to allow the pre Tag

Enable pre tags in Rich Text

Then you can create a custom component for the pre tag, which will be used to inject the html into the dom.

import React from "react";

const Pre = (props) => {
const html = props.children[0].props.children || "";
return html ? <div dangerouslySetInnerHTML={{ __html: html }} /> : null;

export default Pre;

Then you will need to register this component by overriding the theme/modules/WysiwygV2/PrismicWysiwyg/appComponentsMap.js file.

import Pre from "./Components/Pre";

const appComponentsMap = {
pre: Pre,

export default appComponentsMap;

To improve the loading of scripts you can implement your own useEffect to lazy load the specific script by detecting the provider in the HTML raw text, you might also be interested in implementing a helper like dangerously-set-html-content which can better handle to loading of injected scripts.


This can also be done in slices, see the Add Custom Embed or HTML code article for more information.