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.

Steveorevo

SpectrOMTech

ServerPress

Dave Jesch

This plugin provides the ability to configure WPSiteSync with an HTTP Authentication username and password to be used when communicating with a Target server that is set up with Authentication.
Usage Scenarios:
If you’re using WPSiteSync with a staging server but want to limit access to the staging server via HTTP Authentication, this is the plugin for you.
This add-on plugin for WPSiteSync allows you to configure an HTTP Authentication username and password that will be used in communicating with the Target server; allowing you to PUSH and PULL changes from your local site to your password protected staging site.
This plugin works the same whether your Source Site is a local install via DesktopServer or other local development environment, or a publicly hosted site. For more information on DesktopServer and local development tools, please visit our web site at: <a href="https://serverpress.com/get-desktopserver/" rel="nofollow ugc">https://serverpress.com/get-desktopserver/</a>
How it Works:
The WPSiteSync for HTTP Authentication add-on plugin sends the username and password with each API request made to the Target site. This allows you to configure your Target site with .htaccess rules that will limit access to user that have the password.
Support:
<blockquote>
Support Details: We are happy to provide support and help troubleshoot issues. Visit our Contact page at <a href="http://serverpress.com/contact/" rel="nofollow ugc">http://serverpress.com/contact/</a>. Users should know however, that we check the WordPress.org support forums once a week on Wednesdays from 6pm to 8pm PST (UTC -8).
</blockquote>
ServerPress, LLC is not responsible for any loss of data that may occur as a result of using this tool. We strongly recommend performing a site and database backup before testing and using this tool. However, should you experience such an issue, we want to know about it right away.
We welcome feedback and Pull Requests for this plugin via our public GitHub repository located at: <a href="https://github.com/ServerPress/wpsitesync-httpauth" rel="nofollow ugc">https://github.com/ServerPress/wpsitesync-httpauth</a>

WPSiteSync for HTTP Authentication

It does what it says it does

It allowed me to configure my target site with .htaccess rules that will limit access to the user that has that password.

This worked like a charm.

Adds support for sites protected with HTTP Authentication via .htaccess rules.

Brasth Document Sync for Google Docs vs WPSiteSync for HTTP Authentication