Glossary
This is a reference of terms and concepts unique to Pantheon Content Publisher to help content creators, developers, and site administrators understand the platform's specialized vocabulary.
The main platform that allows content creators to publish documents directly from Google Docs to their websites. Content Publisher converts, processes, stores, and enriches Google Docs content, then delivers it through its API to WordPress, Drupal, or Next.js sites.
The Content Publisher interface that appears as a sidebar within Google Docs, providing publishing controls, preview access, and content management tools without leaving the familiar Docs environment. Learn more.
Organizational structures that allow you to group documents into sections and sub-sections, control their order, and manage visibility on your website. Collections drive website navigation and content discoverability.
Your website can use as many content collections as needed to organize different content types and sections.
- Use case #1: Create a "Blog" collection with sub-sections for "Product Updates," "Company News," and "Industry Insights."
- Use case #2: Have a single collection use metadata fields to render content in different sections of a website, similar to taxonomy and tagging.
Access controls that determine who can publish content to your collection.
Metadata fields are a collection-level configuration that helps enrich published content beyond the body content. Default fields include title, description, tags, or image fields. Custom fields can be created by an administrator of the collection.
The API that handles content flowing INTO Content Publisher from external sources. Currently used by the Google Docs connector to bring content from Google Docs into the Content Publisher system. This API is designed to be extensible for future integrations with other content sources beyond Google Docs.
The GraphQL-based API that Content Publisher uses to serve content to your website or other external destinations. Your site requests content from this API to display pages to visitors. While integrations exist for Drupal, WordPress, and Next.js, we plan to enable API use to create custom integrations to other destinations.
Real-time visualization of how your Google Docs content will render on your actual website as you type and edit. The preview updates dynamically and allows you to switch between different screen sizes.
Live Preview shows fully rendered elements including images, structured components, and formatting exactly as they'll appear on your site.
Interactive elements that can be embedded inline within your document content. Examples include Forms, Buttons, or Cards with product information. In Drupal integration, these correspond to single directory components and allow you to insert complex functionality without disrupting editorial flow. We are working on offering similar functionality in WordPress
Automated content enhancement powered by Google Vertex AI that assists with content summaries, metadata suggestions for SEO optimization, and enhanced search capabilities. These include:
- Automatic metadata generation
- SEO optimization suggestions
- Content summarization
- Enhanced search indexing
Content Publisher uses webhooks to communicate with connected websites. Webhooks are notifications sent to a configurable URL to inform the service of a special event.
In Content Publisher’s case, the webhooks are triggered upon article publishing, article updates and article delete actions. They allow the consumer website to “take action” and reflect the changes made on the content collection.
While webhooks might be setup automatically by the different systems we provide, users can still configure the webhooks using the CLI or the Admin Interface.