Brasth

<p>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.</p>
<p>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.</p>
<p>Features include:</p>
<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>
<p>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.</p>
<p>This plugin sends requests to these Google services:</p>
<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>
<p>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.</p>
<p>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.</p>
<p>Google’s terms and privacy documents apply to these services:</p>
<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>
<p>Brasth Document Sync does not send Google data to a Brasth Document Sync vendor-hosted service in this release.</p>
<h3>Privacy</h3>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h3>Source And Build Instructions</h3>
<p>Human-readable frontend source is included in <code>resources/</code>. Built assets are included in <code>build/</code>.</p>
<p>To rebuild the admin assets from source:</p>
<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>
<p>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>.</p>


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.

Phases

Anandhu Nadesh

<p><strong>Easy ContentPush</strong> lets you safely and easily migrate content — including ACF fields, media files, featured images, taxonomy terms, and SEO metadata — directly from your staging/dev site to your production site.</p>
<p>A “Push to Live” button appears in the editor sidebar for all supported post types. When you click the button, the plugin instantly transfers the post, including all custom fields and media references, to your live site using a secure REST API endpoint.</p>
<p>This plugin must be installed on both your production site and dev site to push the content. You should configure the plugin settings from the dashboard by providing the ‘Target Site URL’ and ‘Origin Site URL’ in the corresponding fields.</p>
<p><strong>Important:</strong> Your production site should have the same post types, taxonomies, and ACF field groups as your staging/dev site. This plugin does not register or sync post type or field definitions—it only pushes content and metadata.</p>
<h3>Features</h3>
<ul>
<li>Manual “Push to Live” button for posts, pages, and custom post types (CPTs)</li>
<li>One-click transfer of all post content, including ACF Flexible Content, Relationships, Repeaters, and Groups</li>
<li>Seamless handling of featured images and other media (no duplication)</li>
<li>Taxonomy and term synchronization (including custom taxonomies)</li>
<li>Yoast SEO metadata transfer</li>
<li>Respects page templates and parent/child hierarchies</li>
<li>Supports scheduled posts, files, SVGs, and more</li>
<li>Customizable settings panel for site URL and allowed post types</li>
</ul>
<h3>Usage</h3>
<ol>
<li><strong>Install and activate</strong> Easy ContentPush on your development/staging WordPress site.</li>
<li>Go to <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Easy ContentPush</strong> on your dev/staging site and provide the target website URL (where you want to push the content to) in the field named ‘Target Site URL’ in settings page.</li>
<li>Select the post types you want to enable for pushing</li>
<li><strong>Install and activate</strong> Easy ContentPush on your live/production WordPress site</li>
<li>Go to <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Easy ContentPush</strong> on your live/production site and provide the origin website URL (where you want to receive content from – Your development/staging website) in the field named ‘Origin Site URL’ in settings page.</li>
<li>Edit a post, page, or custom post type in development/production website.</li>
<li>Click the <strong>Push to Live</strong> button in the editor’s sidebar meta box.</li>
<li>Your post’s content, ACF data, media references, taxonomy, and SEO metadata will be transferred to your live site instantly, preserving status (draft, scheduled, published, etc.).</li>
</ol>
<p><strong>Note:</strong> Make sure all ACF field groups, post types, and taxonomies exist on both sites for proper mapping.</p>
<h3>Support</h3>
<p>For support, questions, or feature requests, contact anandhu.natesh@gmail.com / anandhu.nadesh@gmail.com<br />
Contributions are welcome on <a href="https://github.com/Macromaniak/easy-content-push" rel="nofollow ugc">GitHub</a>.</p>
<h3>License</h3>
<p>This plugin is licensed under GPLv2 or later. You are free to use, modify, and distribute this plugin under the terms of the license.</p>


Easy ContentPush

Push posts, pages, custom content, ACF fields, media, taxonomies & SEO from staging to production with one click.

Brasth Document Sync for Google Docs vs Easy ContentPush