Known issue when editing Cloudpress exported content in Webflow
Learn more about known issues affecting the Cloudpress to Webflow integration and how you should guard against them.
Introduction
The Cloudpress integration works seamlessly for the most part, but there is a known issue with editing rich text fields in the Webflow designer that may break the formatting of your content. This document discusses this issue and describes how to mitigate it.
Description of the issue
If you add items like tables or embeds to a document, Cloudpress will export those items correctly to Webflow. However, if you subsequently edit the rich text field manually inside the Webflow designer, the formatting of these items may break, resulting in wrongly formatted text.
To demonstrate this is action, here is a sample table as defined in a Notion document.
When this document is exported to Webflow, the table will be added to the rich text field.
The table does not appear correctly in the Webflow rich text editor, but if you publish the page, the table will be displayed correctly.
However, if you make any changes to the rich text field, the table display will be messed up:
The reason this happens is due to a limitation with the Webflow API that we use to export content. It does not allow us to correctly mark special blocks of code where you will normally use the HTML Embed Code Editor when you add these items manually.
How to migigate it
You must not edit the rich text field to update the content created by Cloudpress. Instead, make changes to the original document and re-export it to Webflow.