FAQs
No, your suggestions won’t show up when published 😀, don’t be shy.
It is possible to use Pantheon Content Publisher with a personal account ( @gmail.com email address) but you can only connect documents to the playground site.You can’t create your own Content Collection with your @gmail.com address.
Separately from that, as a @gmail.com user, you can be invited to collaborate on documents belonging to a Google Workspace organization and publish them, but you won’t be able to create and publish new documents there.
Generally, the architecture and application have been designed to work similarly on mobile and desktop. This said, the authoring functionalities offered within Google Docs via the Pantheon Content Publisher add-on are currently not available on mobile devices. Google might eventually port the add-on technology to its iOS and Android apps.
The Pantheon Content Publisher is a multi-tenant architecture. Each tenant’s content store is isolated securely. However, this doesn’t prevent your website from relying on a single-tenant architecture, as the architecture is decoupled. Pantheon Content Publisher is designed to work seamlessly with both single-tenant architectures (STA) and multi-tenant architectures (MTA) when it comes to the Website stack (front-end layer, CMS, database, and cache).
There is technically no limitation regarding the website technology used in front of Content Publisher. The only technical requirement is to be able to connect to the Pantheon Content Publisher Delivery APIs, which can be orchestrated by using our Drupal Module, WordPress plugin or our JavaScript SDK.
Currently, we only support Google Docs as a content authoring tool. We hope to support other options, including Office 365. Stay tuned and voice your interest on our roadmap portal!
A content collection is a place where content is managed and published. Collections allow to keep projects' documents organized. Users might create different collections for different content types, projects or use cases.
A collection allows to granularly define:
- Access control: who can publish to your collection.
- Metadata field configuration: additional fields enriching your Google Documents.
- Content organization: a “content tree” for your documents to organize them in sections and sub-sections
- Privacy: who can view your Collection and its content.
- Destination: where your content is being delivered.
By design, Content Publisher only provides structured markup to the website and does not control design elements such as font size, color, background color, or other visual aspects.
The design of web pages built with Content Publisher relies entirely on the website consuming the content, and accessibility compliance should be handled on the consuming website. However, some content-related accessibility practices may need to be handled at the time of content creation.
For example, alternative text for images can be provided using Image Options in Google Docs, and our table-to-responsive-grid conversion feature can be used for in-document layouts, as using HTML tables for layout is not accessible for screen reader users.
Visit the W3C Web Accessibility Initiative for an introduction to website accessibility.
Content Publisher is a service that converts Google Docs to structured data, and then stores it on the cloud. A Drupal module or a WordPress plugin complets the connection, allowing you to push your docs directly to the CMS.
Content Publisher removes copy and paste between Google Docs and the CMS, so it removes the WYSIWYG from the process. The Google Document remains the collaboration and content creation interface, and Content Publisher is a direct conduit to the CMS.
If you encounter any issues, please reach out to us, we can assist, or point you in the right direction if any code changes are needed to allow Content Publisher to work on your site.
No. PDFs should be pasted or rebuilt in Google Docs first.
No. All changes can be previewed and pushed at your convenience. Content can be changed in the WordPress CMS, but changes are not pushed back to the Google Doc. For Drupal, changes can only be made in Google Docs.
Images can be placed in the doc like you normally would. It is also possible to connect to an external DAM or media library, but this would require you to build the integration. We would like to make this available in the future.
The Google Docs remain on your drive. You create a dedicated folder (a “collection”) that Content Publisher has access to.
Known Issues
Content Publisher creates remote entities indexed through the Search API rather than traditional database-stored content. This approach works well with most Drupal features like Views, search, and basic content management. However, some Drupal modules and functions that rely on direct database queries or assume standard entity storage may encounter integration issues.
The content of the Google Docs page is sent to the CMS as a single field. Pages with complex page layouts, tables, or other mixed content may not render as expected. We're committed to working with the community to identify and resolve these challenges as we build out the Content Publisher ecosystem. If you encounter integration issues, please reach out so we can help troubleshoot and improve compatibility.
Content Publisher applies only the standard global styling that’s present in the theme files. So, if a page depends on custom inline or dynamic CSS that isn’t part of the main theme, it’s likely to render without the intended styles. There are different ways to work around this, such as the Asset Injector modules for Drupal.
By default, Elementor stores and renders content differently from standard WordPress. As a result, Content Publisher requires an Elementor Pro template that uses post content and will not work with sites that don’t.
Other plugins (particularly page builder plugins) that bypass standard WordPress post content should be tested thoroughly. We will continue to improve theme compatibility.
Content Publisher creates remote entities that don't have database tables. When running Pathauto's Bulk Generation to create URL aliases, you must exclude Content Publisher entities to avoid database errors.
To use Pathauto bulk generation:
- Go to /admin/config/search/path/bulk-generate
- Uncheck any Content Publisher entity types before running the operation
- Run bulk generation only for your standard Drupal content
For Content Publisher content: To create aliases for Content Publisher pages, you must manually edit and save each node individually in Drupal, which will trigger Pathauto to generate the alias.