Skip to content
CoverKit CoverKit

How to configure use cases

Configure use cases on each template in the CoverKit template editor. Settings apply only to that template’s assignments.

Before you start

Section titled “Before you start”
  1. Create or open a template (Media → CoverKit).
  2. Design at least the layers you plan to map (headline text, logo image, and so on). See Template editor.
  3. Publish or update the template when finished so assignments persist.

Step-by-step

Section titled “Step-by-step”

1. Open use cases

Section titled “1. Open use cases”
  1. Edit the template.
  2. Open the CoverKit sidebar.
  3. Go to Use cases.

2. Enable a use case

Section titled “2. Enable a use case”
  1. Select a use case (for example Open Graph image).
  2. Turn it on for this template.
  3. Review settings for that use case—post types, front page, archives, alt text, and similar options vary by use case. See the dedicated page:
Section titled “3. Check dimensions (recommended)”

Many use cases recommend an output size (for example 1200×630 for Open Graph). If your template canvas proportions do not match, the panel may show a warning. Use Apply dimensions to canvas to resize the template canvas to match, then adjust your layout.

Output is still scaled and cropped to the use case’s required size when they differ; matching proportions avoids surprise cropping.

4. Map fields to layers

Section titled “4. Map fields to layers”

Mapping uses a field-first flow:

  1. Under Required or Recommended, find a field (for example Post title).
  2. Click Select layer (or the equivalent control on that row).
  3. The editor enters layer picker mode—compatible layers are highlighted.
  4. Click a layer on the canvas or in the list view.
  5. Confirm with Confirm selection / Use this layer.
  6. The row shows which layer and attribute are mapped (for example Post title → Headline · text). Use Change to remap.

Required fields should be mapped before you rely on output; the UI may warn if they are missing.

Recommended fields improve the result but are optional.

5. Custom text with tags (optional)

Section titled “5. Custom text with tags (optional)”

For some mappings you can use custom text instead of replacing the whole text layer, with tokens such as:

{post_title} | My Site

Tokens use the field key in braces. Unknown tokens should not break the site; fix mappings if you see warnings.

6. Save and verify

Section titled “6. Save and verify”
  1. Save or Update the template.
  2. Open Graph: view a matching post on the front end and check page source for og:image, or open the image URL in a new tab.
  3. Sidebar image: check the preview in the template editor sidebar.
  4. If you still see an old image, clear the template cache.

Tips

Section titled “Tips”
  • Map post title (and other required fields) before testing share previews.
  • One template can run Open Graph and Sidebar image together with different settings and mappings if needed.
  • Do not enable conflicting templates for the same view without understanding which template wins (CoverKit picks the first eligible published template in a stable order for Open Graph).
Section titled “Related”