Brasth Document Sync for Google Docs

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:

• Self-managed Google OAuth setup wizard.
• Server-side Google Drive document browser for My Drive and shared drives.
• Advanced Google Docs URL and raw file ID linking.
• Background sync through WP-Cron with source status and diagnostic logs.
• One-way Google Docs to WordPress sync for posts, pages, and enabled public custom post types.
• Media import for images exported from Google Docs.
• Gutenberg block markup for common headings, paragraphs, lists, tables, and images.
• Uninstall cleanup for settings, encrypted user tokens, and scheduled events.

External Services

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:

• Google OAuth 2.0 endpoints, to authorize a user’s Google account and refresh access tokens.
• Google Drive API, to list visible Google Docs, shared drives, folders, document metadata, and HTML ZIP exports.
• Google Docs API, to read document structure when the large-document fallback is needed.

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:

• Google Privacy Policy: https://policies.google.com/privacy
• Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
• Google APIs Terms of Service: https://developers.google.com/terms

Brasth Document Sync does not send Google data to a Brasth Document Sync vendor-hosted service in this release.

Privacy

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 DOCSYNC_WP_FULL_UNINSTALL or return true from the docsync_wp_full_uninstall filter to remove Brasth Document Sync post metadata. Synced posts and imported media are not deleted automatically.

Source And Build Instructions

Human-readable frontend source is included in resources/. Built assets are included in build/.

To rebuild the admin assets from source:

1. Install PHP dependencies with composer install.
2. Install frontend dependencies with pnpm install --frozen-lockfile.
3. Build assets with pnpm build.

The build uses Vite and writes build/manifest.json, build/manifest.post-sync.json, and hashed CSS/JS assets. Runtime React is provided by WordPress through wp-element.