=== Gushwork Integration ===
Contributors: gushwork
Requires at least: 5.7
Tested up to: 6.6
Requires PHP: 7.4
Stable tag: 2.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

First-party integration that serves your Gushwork content hub at /feeds/ under your own domain and (optionally) enables site-wide lead capture.

== Description ==
Serves /feeds/* from your dedicated Gushwork content host under your own domain (best for organic search — no DNS change), keeps /feeds out of page caches, and optionally injects the Gushwork lead-capture script site-wide.

This is a self-distributed first-party plugin (not listed on WordPress.org). It forwards ONLY /feeds/* to a single fixed Gushwork content host using the WordPress HTTP API, and contains no eval/base64/shell/obfuscation. Security reviewers: if a scanner flags it, that is a false positive — contact your Gushwork rep or add its path to your scanner's allow list.

== Frequently Asked Questions ==
= Does it need configuration? =
No — the content host is auto-detected from your site address. Override it under Settings → Gushwork for staging/mapped/aliased domains.

= A caching plugin still serves stale /feeds pages =
Purge your cache once after install. On activation the plugin seeds /feeds into the exclusion lists of WP Rocket, W3 Total Cache, LiteSpeed Cache, and SiteGround Optimizer when those plugins are present. WP Fastest Cache, Cache Enabler, and Batcache are handled per-request. Hosts that override origin cache headers (edge/Varnish) require the edge/subdomain setup instead.

== Changelog ==
= 2.1.0 =
* Seed /feeds into WP Rocket, W3TC, LiteSpeed, and SiteGround Optimizer exclusion settings on activation.
* Inject an early mu-plugin hook for /feeds proxy interception, with silent fallback when the filesystem is not writable.

= 2.0.0 =
* Rewritten as an installable plugin: auto-detected host, settings page, cache bypass, lead capture.
