Creating Custom Previews

The Static CMS exposes a window.CMS global object that you can use to register custom previews for an entire collection (or file within a file collection) via registerPreviewTemplate.

React Components Inline

The registerPreviewTemplate requires you to provide a React component. If you have a build process in place for your project, it is possible to integrate with this build process.

However, although possible, it may be cumbersome or even impractical to add a React build phase. For this reason, Static CMS exposes some constructs globally to allow you to create components inline: h (alias for React.createElement) as well some basic hooks (useState, useMemo, useEffect, useCallback).

NOTE: createClass is still provided, allowing for the creation of react class components. However it has now been deprecated and will be removed in v2.0.0.

Params

The following parameters will be passed to your react_component during render:

Example

const PostPreview = ({ widgetFor, getAsset, entry, collection, field }) => {
  const imageUrl = useMediaAsset(entry.data.image, collection, field, entry);

  return h(
    'div',
    {},
    h('h1', {}, entry.data.title),
    h('img', { src: imageUrl }),
    h('div', { className: 'text' }, widgetFor('body')),
  );
};

CMS.registerPreviewTemplate('posts', PostPreview);

Lists and Objects

The API for accessing the individual fields of list- and object-type entries is similar to the API for accessing fields in standard entries, but there are a few key differences. Access to these nested fields is facilitated through the widgetsFor function, which is passed to the preview template component during render.

List Template Example

For list fields, the widgetFor function returns an array of objects that you can map over in your template. If your field is a list of authors containing two entries, with fields name and description, the return value of widgetsFor would look like this:

[{
  data: { title: 'Mathias', description: 'Co-Founder'},
  widgets: { title: <WidgetComponent>, description: <WidgetComponent>}
},
{
  data: { title: 'Chris', description: 'Co-Founder'},
  widgets: { title: <WidgetComponent>, description: <WidgetComponent>}
}]

const AuthorsPreview = ({ widgetsFor }) => {
  return h(
    'div',
    {},

    // This is a static header that would only be rendered once for the entire list
    h('h1', {}, 'Authors'),

    // Here we provide a simple mapping function that will be applied to each
    // object in the array of authors
    widgetsFor('authors').map(function (author, index) {
      return h(
        'div',
        { key: index },
        h('hr', {}),
        h('strong', {}, author.data.name),
        author.widgets.description,
      );
    }),
  );
};

CMS.registerPreviewTemplate('authors', AuthorsPreview);

Object Example

Object fields are simpler than lists - instead of widgetsFor returning an array of objects, it returns a single object. Accessing the shape of that object is the same as the shape of objects returned for list fields:

{
  data: { front_limit: 0, author: 'Chris' },
  widgets: { front_limit: <WidgetComponent>, author: <WidgetComponent>}
}

const GeneralPreview = ({ entry, widgetsFor }) => {
  const title = entry.data.site_title;
  const posts = entry.data.posts;

  return h(
    'div',
    {},
    h('h1', {}, title),
    h(
      'dl',
      {},
      h('dt', {}, 'Posts on Frontpage'),
      h('dd', {}, widgetsFor('posts').widgets.front_limit || 0),

      h('dt', {}, 'Default Author'),
      h('dd', {}, widgetsFor('posts').data.author || 'None'),
    ),
  );
};

CMS.registerPreviewTemplate('general', GeneralPreview);