What it does
Wavefront writes each approved article as a story of one content type through Storyblok's Management API. Stories are drafts by default, or published.
The story's name is the title and its slug the article's slug. Fields Wavefront doesn't map, and anything an editor added, stay on a revision.
Before you start
- A Storyblok space with a content type for articles
- An account whose role can edit and publish that content type
How to connect Storyblok
- In Storyblok, create a personal access token (My account → Account settings → Personal access tokens), limited to the space.
- In Wavefront, open Settings → Publishing and choose Add destination. Pick Storyblok.
- Choose the region your space is hosted in, then enter the space ID and the token.
- Choose Load fields, pick the content type and map the body, plus any optional fields.
- Optionally set a folder, a live URL pattern, and fixed author story UUIDs.
- Choose Test connection. Wavefront reads the space, the content type and the folder.
What Wavefront sends
- The body as Storyblok rich text, or Markdown on a Markdown or textarea field
- Excerpt, SEO title and description, header image alt text and canonical URL
- The header image as an asset, with the stock photo credit as its copyright
- Categories, tags, author and date on the field types you map
Good to know
- Scheduling, OAuth app connections, story tags and JSON-LD aren't supported.
- Images become Storyblok assets only when a story is published, at most 15 per article.
- Withdraw unpublishes the story and keeps it.