FAQ
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 their 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. We don’t have yet a strong requirement to use a Pantheon site.
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!
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.