​
Introduction

The Cloudpress Google Docs Add-on allows you to configure various aspects of how content is exported to your Content Management System (CMS). This document explains these configuration options.

​
Open the Add-On settings

Open any document in the Google Docs editor, then open the Cloudpress Add-on by clicking on the Cloudpress icon in the side panel. Open the Google Docs Add-on in the sidebar Click on the three dots menu icon in the top right corner, then click Settings. Open the Add-on settings

​
Available settings

Available settings for the Add-on

​
1. Personal Access Token

The personal access token is required for the Add-on to communicate with the Cloudpress application. You can obtain your personal access token from your User Profile. Refer to the following documentation for more information:

​
2. Suggestions

Determines how Cloudpress should handle suggestions from other collaborators (which you have yet to accept or decline) when exporting the document. Let’s take the following example where a collaborator has suggested replacing the word “correct” with “wrong”. Collaborator suggesting a change
  • Export without suggestions: All suggestions from collaborators are ignored. In the example above, Cloudpress will export the text “This is correct”.
  • Export with suggestions inline: All suggestions from collaborators are exported along with the original text. In the example above, Cloudpress will export the text “This is wrongcorrect”.
  • Export with suggestions accepted: All suggestions are deemed to be accepted and exported instead of the original text. In the example above, Cloudpress will export the text “This is wrong”.

​
3. Use property table

The setting allows you to use a property table to set additional fields in your CMS when exporting content. This is useful when you want Cloudpress to update additional field values on your behalf, for example, the author or category of a blog post. You can find a detailed explanation of this feature in our documentation on setting additional field values with the Google Docs Add-on.

​
4. Auto-detect embeds

When this option is enabled, Cloudpress will attempt to convert standalone links in a single paragraph to the appropriate embed in your CMS. For example, if you have a paragraph containing only a link to a tweet, Cloudpress will convert it to the correct embed when exporting the document to your CMS.

​
5. Convert single-cell tables to code blocks

This option is useful when you want to include programming code snippets in your content. When enabled, Cloudpress will convert any single-cell table (i.e. a table with one row and one column) to a code block when exporting the document to your CMS.

​
6. Treat single-cell tables with a dotted border as raw content

Enabling this option will treat a single-cell table with a dotted border as raw content. This means that the content inside that table will be sent to your CMS as-is. This allows you to export content to your CMS that is not supported by Google Docs, for example exporing a custom Gutenberg block to WordPress. Please refer to our documentation on exporting custom content.