Template Content

On this page, you'll learn how to template content from the Prismic API in your Express application.

Content from Prismic comes in different types. Some are simple fields, like numbers or booleans. Others are structured fields, like titles, rich texts, and links.

Simple field types can be injected directly into your application:

@prismicio/client includes special utilities for rendering structured fields. To render the rich text field, for instance, use prismic.asHTML():

To get started, let's look at the structure of the API response.

When you use Prismic's query methods, you will see three different types of API responses:

• paginated responses, which return a response object
• get-all responses, which return a results array
• get-single responses, which return a document object

In fact, these are all part of the same structure: the response object contains the results array, in which each item is a document object.

Here's more detail about what that each looks like:

When you make a query by get() to the Prismic API, you will get a JSON object containing pagination information and an array of query results. Here is a truncated example of an API response containing some simple fields:

If you store the response in a variable called response you might access a single data point like this:

In Express with, EJS templating, like this:

The most important property on the response object is the results array.

When you make a query using a get-all method, such as getAllByType(), you will get a results array containing all matching results.

The getAll*() methods, such as getAllByType(), will directly return a results array.

Here is a truncated example of an API response using getAllByType() :

If you store the response in a variable called results you might access a single data point like this:

In Express.js with, EJS templating, like this:

Each item in the results array is a document object.

The helper functions getSingle(), getByUID(), and getByID() will return a document object, which contains the data for an individual document directly.

Here's a truncated example of the response for those queries:

With a single document query, you might access your data like this:

The content for each Prismic field is delivered as either a simple primitive value or an object. The simple fields can be injected directly into your app since their value is either a string, a number, or a boolean. Here are the simple fields:

• Color
• Key text
• Number
• Select
• Boolean
• Date
• Timestamp

Here's an example of how to template the number field value from its API ID. You can template the other simple fields the same way.

Retrieving the color field is similar. Here we can see how to do inline styling in Express:

The date and timestamp fields from Prismic are strings. The raw response for each of these fields has the following formats:

• Date: YYYY-MM-DD
• Timestamp: YYYY-MM-DDTHH:MM:SS+0000

prismic.asDate()  takes a date or timestamp field from Prismic and converts it to a JavaScript date object. To learn more about JavaScript Date objects, see the MDN Date documentation or this tutorial by Tania Rascia.

The geopoint field is served as an object with two properties: latitude and longitude. Here is an example API response:

Here is an example of how to retrieve the latitude & longitude coordinates for a geopoint field.

The embed field will let content authors paste an oEmbed supported service resource URL (YouTube, Vimeo, Soundcloud, etc.), and add the embedded content to your website. This is the API response of the embed field:

Here’s an example of how to integrate the embed field into your templates.

The image field returns an object with data about the image, including a URL for your image (hosted on Prismic's servers) and alt text.

You can template an image using the asImageSrc() function and an <img> element:

Images can be transformed using Prismic’s built-in Imgix integration and asImageSrc(). This allows you to resize, crop, recolor, and more. See Imgix’s URL API Reference for a full list of available information.

The following example converts the image to grayscale with sat: -100:

Image fields can have responsive views. Retrieve their URLs by passing each view to asImageWidthSrcSet().

The asImageWidthSrcSet() and asImagePixelDensitySrcSet() functions build responsive srcset attribute values that can be passed to <img> or <source> elements:

Rich text and titles are delivered in an array that contains information about the text structure. Here's an example of the API response of the rich text field (title fields follow the same format).

To render the rich text and title fields, use the prismic.asHTML() method to convert your rich text field to HTML.

The prismic.asText() method will output the rich text or title field as a string. Here is an example of how to get plain text from a rich text or title field:

The link field allows you to link to an external webpage, an internal Prismic document, or an item in your Media Library (like a PDF). The content relationship field allows you to link specifically to an internal Prismic document.

Here's what a content relationship field looks like from the API (a link field takes a similar format). This field has an API ID example_content_relationship, and it links to another document that has the UID another-document and the type page.

There are two things that you might want to do with a link:

• Link to another page or media item, internally or externally
• Pull in content from another document

Here's how to do those things.

To render a link to the web, you can use the asLink() method from @prismicio/client. asLink() accepts a link or content relationship field and returns an absolute or relative URL as a string. You can inject that string into an <a> tag, like so:

To pull content from a linked document, you must fetch that content in your API Query using the graphQuery or fetchLinks API options. You can learn more about both options in the Rest API Technical Reference. Here, we'll explain more about fetchLinks.

The fetchLinks option allows you to retrieve a specific content field from a linked document and add it to the document response object. In your query options, use fetchLinks as the key, with the value formatted like so:

• first, the API ID of the custom type referenced in your content relationship field
• then, the API ID of the field that you want to retrieve

For instance, if you have a custom type called blog that includes a content relationship field called example_content_relationship linked to a custom type called author where you want to retrieve a field that has an API ID is author_name, you would format the option like so:

Once you have adjusted your API query, the linked content will appear in a data object nested in the link or content relationship field:

You can then template that content normally:

A group field renders an array of content fields. Here's what the API response looks like for a hypothetical group field modeling a nav menu.

To integrate a repeatable group field into your template, loop through each item in the group as shown below using the map() method:

Slices are repeatable, rearrangeable content sections. Learn more about slices in What is a Slice?

On the document object, slices are stored in the body array, like so:

To learn how to render slices, see the Render Slices article.