- Google Docs
- Notion
Introduction
When exporting content to your CMS, Cloudpress will convert the rich content from Google Docs or Notion into the correct format for your CMS, and update the default content field in your CMS. Sometimes, it may happen that you want to export content to additional rich text fields in your CMS. Let’s take the following example of CMS Collection definition for Authors in Webflow.We use Webflow as an example in this document, but the same technique works
for all other CMSs we support.

Using the @@split
processing directive
As mentioned above, the @@split
processing directive allows you to split the contents of your document across multiple fields in your CMS. To use it, simple add the @@split
directive to your document at the point where you want to split your content to a separate field.
The split directive must also contain a fieldname
property with the name of the field in your CMS that should contain the content following the split directive. You can use multiple @@split
directives in a single document with each instance of the @@split
directive splitting the content to a separate field.

fieldname
as byline
. When Cloudpress exports this document, it will export the content above the @@split
directive to the default content field (in this case, the Bio field) and the content below the directive to the Byline field.

This document also uses a property
table that
allows us to export additional fields like the
slug
and headshot
photo.Finding the field name
The@@split
directive requires you to specify the Field Name in your CMS. You can find the available fields by navigating to your CMS connection inside Cloudpress.

- Click on the Model Inspector tab of your CMS Connection.
- The field names are listed in the Field Name column. You can copy the field name to the clipboard by clicking the button to the right of the field.