Abhishek Kumar

WooCommerce core does not provide AJAX add-to-cart on the single product page or for variable products listed on archive pages (it redirects to the single view). This plugin adds an unobtrusive AJAX workflow for:
<ul>
<li>Simple products (single product page button becomes AJAX)</li>
<li>Variable products on archive & block-based Product Collection (opens an accessible modal to choose attributes, then adds via AJAX)</li>
<li>Classic themes and modern block/FSE themes (2025 and later) with Product Collection blocks</li>
</ul>
Highlights: 
* Works with WooCommerce fragments (mini-cart updates automatically) 
* Accessible modal (focus trap, ESC to close, restore focus) 
* Nonce-secured AJAX endpoints; sanitized and validated input 
* Settings page to enable/disable variable product archive functionality 
* Block theme compatibility (intercepts “Select options” buttons) with slug/product_id fallback 
* Performance-minded (loads minified bundles built via Webpack; falls back to source if missing) 
* Translations auto-loaded from WordPress.org (no manual POT/PO generation required)
Privacy: This plugin does not send any data to external services. It only uses WooCommerce cart/session APIs.
<h3>Development</h3>
Build commands:
<ol>
<li>Install dependencies: 
npm install</li>
<li>Production build (minified + source maps): 
npm run build</li>
<li>Watch during development: 
npm run watch</li>
<li>Lint JS: 
npm run lint</li>
</ol>
Translations: WordPress.org language packs auto-load this plugin’s strings. The former POT/PO/MO tooling and i18n loader file were removed (WP 4.6+). Do not add a load_plugin_textdomain() call; simply keep the Text Domain header accurate.
WooCommerce is a registered trademark of Automattic Inc. This plugin is not affiliated with or endorsed by Automattic/WooCommerce.

Ajaxified Cart

AJAX add-to-cart for WooCommerce: simple & variable products on archives/blocks via accessible modal and instant cart refresh.

Khokan Sardar

WordPress full-site-editing structure — patterns, templates, template parts, global styles, and navigation — lives in the database. Moving some of it from staging to production today means either a full database sync (which is destructive to production-only data like orders, users, and form entries) or tedious manual copy-paste.
SiteCargo packs exactly what you choose into a portable, reviewable bundle and applies it to another site with stable identity, ID remapping, and media handling — never touching the data you didn’t select.
It is currently a WP-CLI tool (an admin user interface is on the roadmap).
<h4>How it works</h4>
<ul>
<li>Export the entity types you choose into a self-describing bundle (a folder containing a manifest, one JSON file per entity, and the referenced media).</li>
<li>Diff a bundle against a target site to preview exactly what would be created, updated, or left unchanged — without writing anything.</li>
<li>Apply the bundle to the target: standalone posts (patterns, navigation) are matched by a stable identifier so re-applying updates the same item instead of duplicating it; templates, parts, and global styles are matched by theme and slug. Numeric IDs baked into block markup (images, reusable-block and navigation references) are remapped to the target site, and referenced media is imported and de-duplicated by content hash.</li>
</ul>
<h4>Supported entity types</h4>
<ul>
<li>Patterns (<code>wp_block</code>)</li>
<li>Templates (<code>wp_template</code>)</li>
<li>Template parts (<code>wp_template_part</code>)</li>
<li>Global styles (<code>wp_global_styles</code>)</li>
<li>Navigation menus (<code>wp_navigation</code>)</li>
</ul>
Only templates/parts that have been customized in the database are exported; unedited theme-file templates already ship with the theme.
<h4>External services</h4>
This plugin does not connect to any external service, send any data off-site, or phone home. Bundles are plain files on your own server that you move between environments however you like.

SiteCargo

Selectively promote WordPress full-site-editing structure and content between environments — without a full database migration.

Ajaxified Cart vs SiteCargo