Pantheon Content Publisher for WordPress
The Pantheon Content Publisher plugin for WordPress provides organizations using WordPress with a simple, streamlined way to allow their users to publish directly from Google Drive and Google Docs on their WordPress websites.
The solution allows editorial teams to work in Google Docs to craft content, collaborate, and get to a final copy, then rely on Pantheon Content Publisher to streamline the publishing of that content to their WordPress-powered websites.
The users can preview how their working documents will look once rendered on the Web. The feature works the same as in other Pantheon Content Publisher setups. See here for more information.
Similarly, Pantheon Content Publisher users can publish from Gdocs, and the document will automatically be published on the WordPress website, as with any other Pantheon Content publisher set up.
See here for more information.
The solution supports both Post and Page entities in WordPress and allows them to adapt to any WordPress configuration. Documents, once posted, are stored in WordPress but are not directly editable (read-only). If you wish to edit them, you can directly follow the link to the source document. You can request it from Google Drive directly if you don’t have access to the document.
For now, the solution is limited to either Post or Page at a given time and both can’t be used simultaneously.
Documents posted through the plugin are accredited to the WordPress system administrator.
The plugin supports the following metadata fields natively:
Default field title | used for the post title, otherwise, it has a fallback to the original GDoc title. |
Default field description | used for Yoast SEO description, if it is set also used for the post excerpt if it is set |
Custom field Categories | Used for Post categories in WordPress. multiple categories can be set as a comma-separated list, ie: Foo, Bar, Baz will set 3 categories: Foo, Bar and Baz |
Custom field | Used for the featured image in WordPress. the image is imported in the WordPress media library and attached to the created post as a featured image the plugin accepts any valid image URL as the value of the FeaturedImage custom meta (eg: https://placehold.jp/150x150.png) |
Before proceeding, first set up a wordpress site using these instructions if you don't already have one.
- Download the Content Publisher WordPress plugin zip file. (in the future, the plugin will be published on WordPress.org plugin directory)
- In your WordPress admin dashboard, go to Plugins > Add New.
- Click on "Upload Plugin" and select the downloaded zip file.
- Click "Install Now" and activate the plugin.
- Navigate to the plugin settings page in the WordPress admin dashboard.
- If you don’t have your Pantheon Content Publisher management token authenticating you to your Google Workspace, you can generate one on Content Publisher Administrative Interface here.
- Paste your management token in the field “Management Token”.
- Choose if you wish to use Post or Page to post your documents (this can be updated later)
- You’re ready to use the solution from the Pantheon Content Publisher Add-on in Google Docs
Watch the following demo for a tour of the solution covering installation and usage.
Pantheon Content Publisher smart components not supported
If you use Smart Components in Pantheon Content Publishers, these will be integrated in your document as links and won’t be rendered on your WordPress website unless you had customized it specifically to support your smart components.
Pantheon Content Publisher metadata
The metadata fields that can be defined in Pantheon Content Publishers are not used by the WordPress plugin, to the exception of the slug, the publish date and the title. Any of these will be ignored.
Pantheon Content Publisher search
The current plugin does not integrate with Pantheon Content Publisher search capabilities. Search on the website totally depends on WordPress native search capabilities.
WordPress user attribution
Content published via Pantheon Content Publisher are attributed to the WordPress site system administrator.