CMS · Integration

Writegarden + Strapi for client content.

The Strapi connector is in development. The planned workflow connects Writegarden articles to a Strapi collection so agencies can review content and publish through their existing website.

Coming soon Strapi publishing is coming soon. Writegarden publishes natively to WordPress and Webflow today, and to any other platform via signed webhooks.

Planned workflow

The planned publishing workflow

  1. Connect the client Strapi instance and select an article collection.

  2. Map the title, slug, body, excerpt and SEO fields supported by the connector.

  3. Review the draft in Strapi, complete the author and category, then publish and rebuild the website.

Capabilities

Planned capabilities.

  • 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?

It is in development. Contact us to discuss your Strapi schema and a pilot; availability will be confirmed after the publishing workflow is validated.

Will it map every Strapi component automatically?

Do not assume arbitrary components or relations are mapped. The initial workflow needs supported field mapping and editorial completion of author, category and SEO components where required.

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.

Writegarden + Strapi for client content.

Discuss a Strapi pilot →