CMS · Integration

Writegarden + Strapi for client content.

Connect Writegarden articles to a Strapi collection, map content fields, and review and publish through your existing website.

How it works

How it works with Strapi

Connect the client Strapi instance and select an article collection.
Map the title, slug, body, excerpt and SEO fields supported by the connector.
Review the draft in Strapi, complete the author and category, then publish and rebuild the website.

Capabilities

What ships with this integration.

Article collection and supported field mapping
Markdown article bodies for Strapi rich-text fields
SEO title and description through mapped text fields
Editorial review in Strapi before publishing
Website rebuild after publication to update pages, sitemap and RSS

Frequently asked

Questions.

Is the Strapi connector available now?

Yes. Connect your Strapi instance, select an article collection and map the supported fields to start publishing with Writegarden.

Does it map every Strapi component automatically?

The connector uses supported field mapping. Complete author, category and SEO components in Strapi where required; arbitrary components and relations are not mapped automatically.

Does publishing to Strapi update a static website immediately?

A static website needs a successful rebuild after the Strapi entry is published. Configure a deploy webhook and verify that the public URL, metadata, sitemap and RSS have updated.

Can agencies use it for several client sites?

Plan a separate Writegarden organisation and CMS connection for each client. Verify the schema and publishing workflow for one site before rolling out to others.

Other integrations