Brasth

Brasth Document Sync for Google Docs helps editorial teams use Google Docs as the source of truth while publishing clean WordPress content. Site owners provide their own Google OAuth web client, each WordPress user connects their own Google account, and authorized users can browse accessible Google Docs, link a document to a post or page, and sync content into WordPress.
The plugin exports Google Docs as HTML ZIP packages, imports embedded images into the WordPress Media Library, rewrites image URLs, sanitizes the resulting HTML, and converts common document structures to Gutenberg block markup. If Google blocks a large HTML ZIP export, Brasth Document Sync retries through the Google Docs API fallback before changing post content.
Features include:
<ul>
<li>Self-managed Google OAuth setup wizard.</li>
<li>Server-side Google Drive document browser for My Drive and shared drives.</li>
<li>Advanced Google Docs URL and raw file ID linking.</li>
<li>Background sync through WP-Cron with source status and diagnostic logs.</li>
<li>One-way Google Docs to WordPress sync for posts, pages, and enabled public custom post types.</li>
<li>Media import for images exported from Google Docs.</li>
<li>Gutenberg block markup for common headings, paragraphs, lists, tables, and images.</li>
<li>Uninstall cleanup for settings, encrypted user tokens, and scheduled events.</li>
</ul>
<h4>External Services</h4>
Brasth Document Sync connects to Google services only after a site administrator saves a self-managed Google OAuth client ID and client secret and a WordPress user connects their Google account.
This plugin sends requests to these Google services:
<ul>
<li>Google OAuth 2.0 endpoints, to authorize a user’s Google account and refresh access tokens.</li>
<li>Google Drive API, to list visible Google Docs, shared drives, folders, document metadata, and HTML ZIP exports.</li>
<li>Google Docs API, to read document structure when the large-document fallback is needed.</li>
</ul>
Data sent to Google can include OAuth client details supplied by the site owner, OAuth authorization codes, refresh-token requests, connected-user access tokens, Drive file IDs, folder IDs, shared-drive IDs, search text entered in the Drive browser, pagination tokens, and document export/read requests.
Data received from Google can include the connected Google account email address, OAuth tokens, Google Docs titles, metadata, modified time, version identifiers, document export content, and image content URLs needed to import media into WordPress.
Google’s terms and privacy documents apply to these services:
<ul>
<li>Google Privacy Policy: https://policies.google.com/privacy</li>
<li>Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy</li>
<li>Google APIs Terms of Service: https://developers.google.com/terms</li>
</ul>
Brasth Document Sync does not send Google data to a Brasth Document Sync vendor-hosted service in this release.
<h3>Privacy</h3>
Brasth Document Sync stores site-level Google OAuth client settings, encrypted per-user Google tokens, connected Google account email addresses, linked Google document metadata, source sync status, diagnostic sync events, and imported attachment metadata in the WordPress database.
During document browsing and sync, Brasth Document Sync communicates with Google OAuth, Google Drive API, and Google Docs API as described in the External Services section. Imported Google Docs images are stored in the WordPress Media Library. Synced WordPress posts and imported media remain on the site until a user with sufficient permission changes or deletes them.
Uninstall removes plugin settings, encrypted user Google tokens, and scheduled cron events. Linked post metadata is retained by default; define <code>DOCSYNC_WP_FULL_UNINSTALL</code> or return true from the <code>docsync_wp_full_uninstall</code> filter to remove Brasth Document Sync post metadata. Synced posts and imported media are not deleted automatically.
<h3>Source And Build Instructions</h3>
Human-readable frontend source is included in <code>resources/</code>. Built assets are included in <code>build/</code>.
To rebuild the admin assets from source:
<ol>
<li>Install PHP dependencies with <code>composer install</code>.</li>
<li>Install frontend dependencies with <code>pnpm install --frozen-lockfile</code>.</li>
<li>Build assets with <code>pnpm build</code>.</li>
</ol>
The build uses Vite and writes <code>build/manifest.json</code>, <code>build/manifest.post-sync.json</code>, and hashed CSS/JS assets. Runtime React is provided by WordPress through <code>wp-element</code>.

Brasth Document Sync for Google Docs

Sync Google Docs into WordPress posts and pages with self-managed Google OAuth, a Drive browser, background sync, and Gutenberg output.

OptiPub

OptiPub synchronizes content from the OptiPub platform to your WordPress installation. Creates custom post types for Resources, Videos, FAQs and Authors with automated sync every 5 minutes via WP-Cron.
Features: Custom post types (Resources, Videos, FAQs, Authors), automated content synchronization via WP-Cron, secure API authentication with encrypted token storage, multiple publication support, widget integration with custom content, tag and category management, static and dynamic pages sync, redirect handling, theme template integration, and file copying utilities.
<h3>Source Code for Minified Files</h3>
This plugin includes one minified JavaScript file (<code>public/js/video.js</code>) which is a third-party library. The source code for this minified file is publicly available:
Video.js v4.6.3 (Location: <code>public/js/video.js</code>) 
* Source Code Repository: https://github.com/videojs/video.js/tree/v4.6.3 
* License: Apache 2.0 
* Documentation: https://docs.videojs.com/
All other JavaScript and CSS files in this plugin (<code>public/js/archive-filters.js</code>, <code>public/js/gtm.js</code>, <code>public/js/init.js</code>, <code>public/js/login-forms.js</code>, <code>public/js/navigation-collapse.js</code>, and <code>public/css/subscribers.css</code>) are provided in their original, unminified source code format and are fully human-readable.
<h3>External services</h3>
This plugin connects to the following external services:
<h4>Google Tag Manager</h4>
Provides tag management and analytics functionality when GTM containers are configured in OptiPub. Sends the container ID to www.googletagmanager.com on every page load. Data collection is controlled by your GTM configuration.
<ul>
<li>Service Provider: Google LLC </li>
<li>Terms of Use: https://www.google.com/analytics/tag-manager/use-policy/ </li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
<h4>YouTube</h4>
Embeds YouTube videos when video content is configured to use YouTube as the player. Sends video IDs to youtube.com/embed only when displaying YouTube video content. Data collection is controlled by YouTube’s privacy policy.
<ul>
<li>Service Provider: Google LLC (YouTube) </li>
<li>Terms of Use: https://www.youtube.com/static?template=terms </li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
<h4>Wistia</h4>
Embeds Wistia videos when video content is configured to use Wistia as the player. Sends video IDs to fast.wistia.net only when displaying Wistia video content. Data collection is controlled by Wistia’s privacy policy.
<ul>
<li>Service Provider: Wistia, Inc. </li>
<li>Terms of Use: https://wistia.com/terms </li>
<li>Privacy Policy: https://wistia.com/privacy</li>
</ul>
<h4>OptiPub API</h4>
Synchronizes content (publications, resources, videos, FAQs, authors, tags, categories, redirects) from the OptiPub platform to WordPress. Sends authenticated API requests with encrypted tokens to your configured OptiPub domain (typically <code>https://<domain>.app.optipub.com</code>) via WP-Cron at configured intervals (default: every 5 minutes). Also creates edit links to OptiPub content management pages in WordPress admin.
<ul>
<li>Service Provider: OptiPub </li>
<li>Terms of Use & Privacy Policy: Please refer to your OptiPub service agreement for terms of use and privacy policy.</li>
</ul>
<h3>Third Party Libraries</h3>
This plugin includes one minified JavaScript library for video functionality:
<ul>
<li>Video.js v4.6.3 – Used for video player functionality
<ul>
<li>Source Code Repository: https://github.com/videojs/video.js/tree/v4.6.3</li>
<li>License: Apache 2.0</li>
<li>Location in Plugin: <code>public/js/video.js</code></li>
<li>Documentation: https://docs.videojs.com/</li>
</ul>
</li>
</ul>
The source code for this minified library is publicly available at the GitHub repository link above. This plugin does not include any custom build process – the minified file is used directly from the Video.js project.
<h3>Development Documentation</h3>
Technical documentation for developers working with the OptiPub plugin. Topics covered:
<ul>
<li>OptiPub Introduction</li>
<li>Prepare</li>
<li>Installation</li>
<li>Activation</li>
<li>OptiPub Admin Page (Save Changes Button, Clear Data Button)</li>
<li>Cron Job & Troubleshooting</li>
<li>Plugin Configurations (wp-config.php, Configuring WP-Cron)</li>
<li>Deactivation & Rescheduling the cron job</li>
<li>Uninstallation</li>
<li>Theme dependencies</li>
</ul>
<h3>OptiPub Introduction</h3>
OptiPub syncs OptiPub Resources to a WordPress installation. The plugin schedules the WP-Cron event <code>optipub_sync</code> to sync Publications, Resources, Videos, FAQs, Authors, Pages, Custom Content, Tags, Categories and Redirects.
The plugin creates Custom Post Types (CPTs): <code>Resources</code>, <code>Videos</code>, <code>FAQs</code> and <code>Authors</code>. Resources synced to these post types store OptiPub metadata and properties in the <code>wp_postmeta</code> table. OptiPub Tags are saved as WordPress Tags. OptiPub Resource Categories are saved as WordPress Categories.
WordPress Widgets can be created with OptiPub Custom Content from the <code>OptiPub Admin</code> page.
<h3>Prepare</h3>
From WordPress Admin: Settings > General, select timezone (recommended: ‘New York’) and click [Save Changes].
OptiPub syncs with UTC but displays dates in EST. If you don’t select ‘New York’, website dates may differ from OptiPub dates. WordPress automatically converts <code>post_date</code> and <code>post_modified</code> to the selected timezone. Configure this before syncing data.
<h3>Bitnami permissions and configurations (Optional)</h3>
Note: This section is only required if you’re using Bitnami WordPress. Skip this if you’re using a standard WordPress installation.
Increase upload file size: 
1. <code>sudo -i</code> 
2. <code>sudo nano /opt/bitnami/php/etc/php.ini</code> 
3. Update <code>upload_max_filesize</code>, e.g. <code>upload_max_filesize = 128M</code> 
4. Restart: <code>sudo /opt/bitnami/ctlscript.sh restart</code>
Set permissions before activation (required for proper activation and uninstallation – vendor files need deletion permissions):
Note: These commands apply to all WP plugins. Modify paths to target only OptiPub if needed.
<ol>
<li><code>sudo find /home/bitnami/apps/wordpress/htdocs/wp-content/plugins/ -type d -exec chmod 775 {} \;</code></li>
<li><code>sudo find /home/bitnami/apps/wordpress/htdocs/wp-content/plugins/ -type f -exec chmod 664 {} \;</code></li>
<li><code>sudo chown -R bitnami:daemon /home/bitnami/apps/wordpress/htdocs/wp-content/plugins/</code></li>
</ol>
This sets user/group to <code>bitnami:daemon</code>, file permissions to 664 (read/write for user/group, read for others), and folder permissions to 775 (read/write/execute for user/group, read/execute for others).
<h3>Activation</h3>
Activate from Plugins page. After activation, a green OptiPub Admin menu item appears in the left sidebar.
<h3>Activation Processes</h3>
During activation, three processes execute:
<ol>
<li>Override <code>WP_CRON_LOCK_TIMEOUT</code> constant – Locates <code>wp-config.php</code> and overrides the constant. See <a href="#plugin-constants" rel="nofollow ugc">WP_CRON_LOCK_TIMEOUT</a>. Note: May fail in Bitnami if permissions aren’t set first.</li>
<li>Generate <code>OPTIPUB_KEY</code> encryption key – Generates a random key stored in <code>wp-config.php</code> as <code>OPTIPUB_KEY</code>. Used to encrypt/decrypt the API token during cron job execution.</li>
<li>Change permalink structure – Changes permalink structure to <code>/%postname%/</code> to accommodate static pages with multiple slugs (e.g., <code>https://www.energyandcapital.com/pubs-detailed/bab</code> where <code>pubs-detailed/bab</code> is defined in <code>/pages</code> OptiPub API).</li>
</ol>
<h3>OptiPub Admin Page</h3>
The green menu icon opens the Admin Page for migrating data from the OptiPub API.
OptiPub Sync Options: 
1. OptiPub Domain – HTTPS URL of the OptiPub API 
2. API Token – The provided API Token from OptiPub will be used to authenticate with the API. Encrypted and stored in database, decrypted for API calls 
3. Open Graph Image Link – Backup/default image URL. Access with: 
 <code>function get_optipub_opengraph_image() { 
 return get_option(\OptiPub\Base\Constants::OPTIPUB_OPENGRAPH_IMAGE_LINK); 
 }</code> 
4. WP Auth Token – Create a WP Auth Token to authenticate subscriber logins through OptiPub 
5. Home Page Template – Template name from OptiPub: 
 – OptiPub > Administration > Templates – create template with <code>.php</code> extension (e.g., <code>optipub_home_page.php</code>) 
 – OptiPub > Content > Pages – create page with path <code>/</code> using the template 
 – Optional: OptiPub > Content > Redirects – create redirect from <code>domain.com/home</code> to <code>https://www.domain.com/</code> 
6. Publication Dropdown – Generated after <code>OptiPub Domain</code> and <code>API Token</code> are provided and <code>Save changes</code> is clicked 
7. Publication Domain Id – Publication domain ID (integer) used to retrieve redirects
Copy Files To Theme (feature complete – documentation under construction) 
View more documentation in the plugin ‘OptiPub Admin’ page
<ol>
<li>Files copied to <code>[theme-directory]/inc/optipub</code></li>
<li>Select file categories and click [Copy Files]</li>
<li>Reference from current location or use as integration guide</li>
</ol>
If copying <code>Helper Functions</code>, copy content from <code>[theme-directory]/inc/optipub/php/add_to_bottom_of_functions.php.txt</code> to your theme’s <code>functions.php</code>. <code>include</code> statements and filter/action calls are commented out. Review functions before uncommenting.
Custom Content Widget Sidebars (feature complete – documentation under construction) 
View more documentation in the plugin ‘OptiPub Admin’ page
Create custom content macro in OptiPub > Content > Custom Content. Custom Content syncs to WordPress as options.
Click [Create New Widget]: 
– Title – WordPress Admin Console 
– Sidebar ID – Display widget in theme templates 
– File Name – WordPress Sidebar Widget content file 
– Description – WordPress Admin Console 
– Custom Content – OptiPub custom content macro name 
– Class Name – CSS class for styling 
– Before Widget – HTML before widget 
– After Widget – HTML after widget 
– Before Title – HTML before title (displays Title if used) 
– After Title – HTML after title (displays Title if used)
How OptiPub Custom Content creates WordPress Sidebar Widgets:
Widget files created at: 
 <code>[theme-directory]/inc/optipub/widget-templates/</code>File Name<code></code>
Default content: 
 <code><?php echo get_option('{$custom_content_name}'); ?></code>
Include in theme templates: 
 <code>if (is_active_sidebar('sidebar-id')) { 
 dynamic_sidebar('sidebar-id'); 
}</code>
<h3>Save Changes Button</h3>
Validates API Domain and token, then stores <code>Optipub Domain</code>, <code>Api Token</code>, <code>Publication</code>, <code>Publication Domain</code>, <code>Header Pencil Ad Macro</code>, <code>Article bottom Ad Macro</code>, <code>Signup Sidebar Macro</code> in <code>wp_options</code> table.
Schedules cron job to run every 5 minutes if <code>Optipub Domain</code>, <code>Api Token</code>, and <code>Publication</code> are provided correctly.
After saving, an API call fetches publication metadata. Fetched metadata appears in the WordPress admin left menu. New CPT links appear in green to differentiate from other CPTs.
<h3>Clear Data Button</h3>
Clears all imported posts (articles, resources, reports, etc.). Publication metadata remains, but imported posts are deleted. Stops and reschedules the cron job. Use to reset the plugin after errors.
Important Note: The clear button stops the current cron job, deletes all posts imported from the API, and reschedules the cron job.
<h3>Cron Job</h3>
Syncs content from the OptiPub API. Scheduled to run every <code>CRON_INTERVAL_IN_SECONDS</code> after <code>OptiPub Domain</code>, <code>API key</code>, and <code>Publication</code> are selected.
First run: Loads all content for Custom Post Types, dynamic pages (nav menu pages like Videos, FAQs, Authors), static pages (from <code>/contents/pages</code> endpoint), and Widget contents (from <code>/custom-contents</code> endpoint).
Subsequent runs: Loads only new or updated content using the <code>updated_at</code> attribute and last cron run timestamp.
<h3>Troubleshooting the Cron Job</h3>
WP-CLI commands: 
– <code>wp cron event list</code> – Lists all cron jobs (<code>optipub_sync</code> is the plugin cron job) 
– <code>wp cron event delete optipub_sync</code> – Deletes the cron job. Use <code>Save changes</code> to reschedule.
<h3>Plugin Configurations</h3>
Constants control plugin behavior: Cron Job scheduling, error handling, widgetized areas, template directory paths.
Constants defined in two places: 
1. <code>wp-config.php</code> – WordPress environment variables 
2. <code>Plugin Constants</code> ([plugin-directory]/inc/Base/Constants.php) – Plugin runtime configuration
<h3>wp-config.php</h3>
WP_CRON_LOCK_TIMEOUT – Defines cron job execution period (default: 60 seconds, can be changed to 3600 seconds for 60 minutes). Plugin attempts to write this during activation. If it fails, cron job won’t schedule and error appears:
<pre><code>Could not activate Cron Job since WP_CRON_LOCK_TIMEOUT is smaller than the expected value of: 3000 (e.x);
</code></pre>
<h3>Configuring WP-Cron</h3>
WP-Cron documentation: https://developer.wordpress.org/plugins/cron/
Configuration in <code>[plugin-directory]/inc/Base/Constants.php</code>:
<ol>
<li>
CRON_INTERVAL_IN_SECONDS – Default: 60 – Interval in seconds for <code>optipub_sync</code> wp-cron job. Creates a lock option in <code>wp_options</code> table; cron won’t run again until it finishes and deletes the option.
</li>
<li>
WP_CRON_LOCK_TIMEOUT – Default: 3600 – Changes WP-Cron timeout in <code>wp-config.php</code>: 
 <code>define( 'WP_CRON_LOCK_TIMEOUT', 3600 );</code> 
Plugin updates this during Activation, when clearing plugin data, or when changing Publication.
NOTE: WP-Cron checks for scheduled jobs on every page load. For more consistent intervals, create a system cron job (requires server access).
Crontab in Linux:
PHP Command:
<pre><code>* * * * * HTTP_HOST=www.domain.com $(which php) /opt/bitnami/wordpress/wp-cron.php >> /path/to/file.log 2>&1
</code></pre>
Configure <code>HTTP_HOST</code> to your site domain.
WP-CLI:
<pre><code>* * * * * sudo wp cron event run optipub_sync
</code></pre>
Note: Cannot log output and less reliable than PHP command.
</li>
</ol>
<h3>Deactivation</h3>
Deactivate from Plugins page. Deactivation pauses execution, temporarily disables custom post types and admin page, and stops cron job schedule. Cron job won’t reschedule on reactivation. If cron is running during deactivation, it finishes its job, then gets deleted on next run.
<h3>Rescheduling the cron job</h3>
After deactivation clears the cron job, reschedule via Save Changes button (even without data changes).
<h3>Uninstallation</h3>
Uninstall from WP Plugin page. Deactivate first to enable delete option.
Uninstallation removes all plugin directory files. During uninstall, database commands delete all plugin-created content. Details in <code>uninstall.php</code> file.
<h3>Theme dependencies</h3>
Content loaded by the plugin is displayed via custom WP theme templates. Theme must provide templates for dynamic pages and widgets, and register/display widgets. Page templates in theme root directory. Widget templates in theme <code>widget-templates</code> directory.
Templates in plugin <code>/templates</code> directory are not used by the plugin but serve as guides for retrieving content from the WP Database. Only <code>optipub_admin.php</code> in <code>/templates</code> is used (decorates the Admin page).
Theme must know Widget area IDs to register them in <code>functions.php</code>. IDs are documented above and found in plugin <code>Constants.php</code> class.
template-parts/archives/ 
 optipub-filters.php 
 optipub-pagination_params.php
template-parts/videos/ 
 mv display.php videos_handler.php

Sync OptiPub content to WordPress with automated cron jobs and custom post types.

Brasth Document Sync for Google Docs vs OptiPub