Preview configuration

Preview your latest content via API

Start by teaching your app how to fetch the latest versions of your content. This means making requests to Delivery Preview API. Every request to the API must be authenticated with a Delivery API key. Remember that server-side technology is required to keep your API keys secret.

• Preview content with Delivery REST API
• Preview content with Delivery GraphQL API.

To create Delivery API keys for previewing content, you need to be a Project manager. Here’s an example of how you can get the latest version of a My article content item:

Prepare your app for preview

When your app can display the content it gets from a Kontent.ai project, the next step is to prepare your app for previewing unpublished content. We recommend using Delivery SDKs to make all this easier. To follow the best practices and avoid using your production app for fetching non-production data (preview), you need two separate instances of your app:

• Production instance: Fetches published content via Delivery API. This instance serves content via example.org URL, for example.
• Preview instance: Fetches the latest version of your content, even if it's not published yet, via Delivery Preview API. This instance serves content via preview.example.org URL, for example.

You can distinguish the instances by providing or omitting the Preview API key. If the key’s present, your app will run the preview instance, if it’s not, that’s a sign to run the production instance. 

Set up multiple previews with spaces

Check out how to set up multiple previews in your project.

Define preview URLs for content types

To preview your content, you need to set up preview URLs for your content types. The URLs may be different for each combination of space and content type.

1. In Environment settings > Preview URLs > Preview URLs for content types, click Set up preview for a content type.
2. Select a content type.
3. In Used in spaces, select a space you’re setting the URL for.
   • If you don’t use spaces, select All spaces. Similarly, use All spaces for a preview URL that’s universal across all your spaces.
4. Type in the preview URL.

The preview URLs must be:

• Absolute paths in the format https://domain/path
• Shorter than 1024 characters

Dynamic preview URLs with macros

If you’re setting up URLs that need to be dynamic, there are a few macros you can use:

• {Space}: space domain
• {URLslug}: content item’s URL slug element value
• {Lang}: codename of the selected language
• {Codename}: content item’s codename
• {ItemId}: content item’s internal ID
• {Collection}: content item’s collection codename
  • This macro is available if you have collections enabled for your subscription.

You can create SEO-friendly URLs using the URL slug element with the {URLslug} macro: https://preview.example.org/articles/{URLslug}. Alternatively, you can use the {Codename} or {ItemId} macros to identify the content items in your preview URLs. In multi-regional projects, use the {Lang} macro to get the currently selected language codename, such as en-us or ja-jp. You can combine the macros. A preview URL https://preview.example.org/{Lang}/articles/{URLslug} would resolve to https://preview.example.org/en-ca/articles/previewing-content-items, for example.

Static preview URLs

Your home page, for instance, doesn’t need a dynamic preview URL, because it's static (it's unique and in one location). For example, a home page’s preview URL for an app running at https://preview.example.org would be https://preview.example.org or https://{Space}.

Set up a preview for Web Spotlight

When setting up Web Spotlight, you set up a preview just like you would without Web Spotlight.

Web Spotlight and spaces

Web Spotlight uses a content item of the Web Spotlight root content type as its top-level (root) content item. The rest of the tree is under this item. Setting up a preview for Web Spotlight with multiple spaces is no different from setting it up for Web Spotlight in a project with only a single space. You set up the preview for the Web Spotlight root content type and for all the other types under it. Specify different preview URLs for different combinations of spaces and content types.

Set up edit buttons in your preview

Once you have a preview working in both your app and Kontent.ai project, it’s a good idea to add edit buttons to your application. They can look like what you see below. For content creators, this small addition means they can go straight to editing in Kontent.ai just by clicking the button. This will help them in case they need to fix minor errors or typos right after they spot them when previewing their content. If your editors have problems opening items through the edit links, verify their user roles.