=== FlxWoo ===
Contributors: rickey29
Tags: woocommerce, checkout, performance, core-web-vitals
Requires at least: 6.0
Tested up to: 6.9
Requires PHP: 8.2
Stable tag: 2.6.0
Requires Plugins: woocommerce
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Improve WooCommerce cart and checkout performance using a modern rendering approach with full fallback support.

== Description ==

**FlxWoo** is a premium WooCommerce extension that improves cart, checkout, and order confirmation page performance by delegating **UI rendering** to an external rendering service, while keeping **WooCommerce fully responsible for all business logic**.

FlxWoo is a **product**, not infrastructure. It provides:

* Optimized checkout UI rendering
* Graceful fallback to native WooCommerce templates
* Admin dashboard for configuration and monitoring

FlxWoo does **not** replace WooCommerce functionality. Payments, shipping, taxes, coupons, validation, and order processing continue to run natively inside WooCommerce.

If the external renderer is unavailable, FlxWoo automatically falls back to standard WooCommerce templates.

**Looking for a free, self-hosted alternative?** See [FlexiWoo](https://github.com/rickey29/flexi) - a free, open-source infrastructure project for developers who want full control over their WooCommerce rendering.

### What FlxWoo Does

- Replaces the **visual rendering** of cart, checkout, and thank-you pages
- Sends read-only WooCommerce data to a configured rendering service
- Displays rendered HTML returned by the service
- Falls back safely to native WooCommerce templates when needed

### What FlxWoo Does NOT Do

- Does not process payments
- Does not calculate totals, shipping, or taxes
- Does not modify carts or orders
- Does not replace WooCommerce checkout logic
- Does not store customer data outside WooCommerce

FlxWoo is designed to be **non-intrusive**, **reversible**, and **safe for production use**.

== How It Works ==

1. A customer visits cart, checkout, or order confirmation pages
2. FlxWoo collects existing WooCommerce data (read-only)
3. Data is sent securely to a configured rendering service
4. Rendered HTML is returned and displayed
5. If rendering fails, WooCommerce templates are used automatically

== Installation ==

### Automatic Installation

1. Go to **Plugins → Add New**
2. Search for **FlxWoo**
3. Click **Install** and **Activate**
4. Ensure WooCommerce is installed and active

### Manual Installation

1. Upload the plugin to `/wp-content/plugins/flx-woo`
2. Activate the plugin
3. Ensure WooCommerce is installed and active

== Configuration ==

After activation:

1. Go to **WooCommerce → FlxWoo**
2. Review connection status
3. (Optional) Configure rendering service URL and timeout
4. Save settings

All configuration is controlled by the site administrator.

== Fallback Behavior ==

FlxWoo includes automatic fallback protection.

If the external rendering service is unavailable:
- Native WooCommerce templates are displayed
- Checkout functionality remains unaffected
- No customer actions are blocked

== Frequently Asked Questions ==

= Will this break my payment gateways? =  
No. All payment processing remains handled by WooCommerce.

= What happens if the rendering service is unavailable? =  
WooCommerce templates are used automatically.

= Does this replace WooCommerce checkout logic? =  
No. FlxWoo only replaces UI rendering.

= Is customer data stored externally? =  
No permanent storage. Data is transmitted temporarily for rendering only.

== Privacy ==

This plugin transmits cart and checkout page data to a configured external rendering service in order to generate HTML output.

No payment credentials or authentication secrets are transmitted.

Site owners are responsible for updating their privacy policy to reflect this behavior.

== Screenshots ==

1. Cart page rendered by FlxWoo
2. Checkout page rendered by FlxWoo
3. Automatic fallback to WooCommerce templates
4. FlxWoo admin settings page

== Changelog ==

= 2.6.0 =
* Consolidated rendering architecture for improved reliability and security
* Unified payment gateway detection with filterable parameter list
* Simplified codebase: removed unused analytics, feature flags, benchmarking, and A/B testing modules
* Removed deprecated UserContext facade
* All rendering requests now include HTTPS enforcement, site ID header, payload/response size limits, SSL verification, and full HTML validation

= 2.5.0 =
* Improved rendering reliability, admin diagnostics, and configuration handling
* Zero-configuration onboarding with auto-generated API keys
* ViewModel architecture for data transformation

== Support ==

Support is handled through the WordPress.org support forum.