Published on

Export custom content from Google Docs and Notion to your CMS

I am happy to announce that we added a major new feature to Cloudpress called Raw Content Blocks. Let me tell you what they are and why they are amazing.

When you export content from Google Docs and Notion to your underlying CMS, Cloudpress will convert the content to the correct format for your CMS. In the case of WordPress, we will convert it to the correct Gutenberg blocks. For Contentful, we will convert it to Rich Text or Markdown. For Sanity, we’ll convert it to Portable Text. Etc.

Cloudpress does a pretty good job of supporting as much of the native formatting for your CMS as we can. However, sometimes this is not possible.

Suppose you work with WordPress and want to add a Gutenberg block to your content that allows users to sign up for an email newsletter. Neither Google Docs nor Notion is familiar with this concept, so there is no corresponding piece of content you can add to your source document.

If you wanted to add content like this, you would have had to edit the content in your CMS manually. This is not ideal as it requires extra work from you. And if you ever re-exported the source document, Cloudress would override your changes.

This is where Raw Content Blocks come in.

They allow you to add content in the native (or raw) format for your underlying CMS. When Cloudpress exports the content, it will send this raw content to your CMS as-is.

This allows you to add custom Gutenberg blocks to your content. Or custom Portable Text blocks for Sanity and custom Rich Text for Contentful.

The video below demonstrates this feature by exporting a custom Gutenberg block from Google Docs to WordPress.

Raw content blocks are available for Google Docs and Notion and work with all our supported CMSs.

Our updated documentation has more details on this feature and links to detailed documentation on how to use it with each supported CMS. We also have a dedicated YouTube playlist with demos for each CMS.

Jerrie Pelser
Founder and CEO of Cloudpress. I understand many of the frustrations of creating content in a collaborative environment and strive to make the content publishing workflow for customers as seamless as possible.