dwindown cb91d0841c plan: Complete implementation plan for Level 1 meta compatibility
**Implementation Plan Created: IMPLEMENTATION_PLAN_META_COMPAT.md**

Following all documentation guidelines:
- ADDON_BRIDGE_PATTERN.md (3-level strategy)
- ADDON_DEVELOPMENT_GUIDE.md (hook system)
- ADDON_REACT_INTEGRATION.md (React exposure)
- METABOX_COMPAT.md (compatibility requirements)

**Key Principles:**
1.  Zero addon dependencies in core
2.  Listen to WP/WooCommerce hooks (NOT WooNooW-specific)
3.  Community does NOTHING extra
4.  Do NOT support specific plugins
5.  Do NOT integrate plugins into core

**3 Phases:**

Phase 1: Backend API Enhancement (2-3 days)
- Add get_order_meta_data() / get_product_meta_data()
- Add update_order_meta_data() / update_product_meta_data()
- Expose meta in API responses
- Add filters: woonoow/order_allowed_private_meta
- Add filters: woonoow/order_updatable_meta
- Add filters: woonoow/order_api_data
- Add actions: woonoow/order_updated

Phase 2: Frontend Components (3-4 days)
- Create MetaFields.tsx component (generic field renderer)
- Create useMetaFields.ts hook (registry access)
- Update Orders/Edit.tsx to include meta fields
- Update Products/Edit.tsx to include meta fields
- Support all field types: text, textarea, number, select, checkbox

Phase 3: PHP Registry System (2-3 days)
- Create MetaFieldsRegistry.php
- Add action: woonoow/register_meta_fields
- Auto-register fields to allowed meta lists
- Localize to JavaScript (window.WooNooWMetaFields)
- Initialize in Plugin.php

**Testing Plan:**
- WooCommerce Shipment Tracking plugin
- Advanced Custom Fields (ACF)
- Custom metabox plugins
- Meta data save/update
- Field registration

**Timeline:** 8-12 days (1.5-2 weeks)

**Success Criteria:**
 Plugins using standard WP/WooCommerce meta work automatically
 No special integration needed
 Meta fields visible and editable
 Zero coupling with specific plugins
 Community does NOTHING extra

Ready to start implementation!
2025-11-20 12:17:35 +07:00

WooNooW

WooNooW is a modern experience layer for WooCommerce — enhancing UX, speed, and reliability without data migration.
It keeps WooCommerce as the core engine while providing a modern React-powered interface for both the storefront (cart, checkout, myaccount) and the admin (orders, dashboard).

Three Admin Modes:

  • Normal Mode: Traditional wp-admin integration (/wp-admin/admin.php?page=woonoow)
  • Fullscreen Mode: Distraction-free interface (toggle in header)
  • Standalone Mode: Complete standalone app at yoursite.com/admin with custom login

🔍 Background

WooCommerce is the most used ecommerce engine in the world, but its architecture has become heavy and fragmented.
With Reactbased blocks (Checkout, Cart, Product Edit) and HPOS now rolling out, many existing addons are becoming obsolete or unstable.
WooNooW bridges the gap between Woos legacy PHP system and the new modern stack — so users get performance and simplicity without losing compatibility.


🚀 Key Principles

  • No Migration Needed Woo data stays intact.
  • Safe Activate/Deactivate revert to native Woo anytime, no data loss.
  • Hybrid by Default SSR + React islands for Cart/Checkout/MyAccount.
  • Full SPA Toggle optional Reactonly mode for max performance.
  • HPOS Mandatory optimized datastore and async operations.
  • Compat Layer hook mirror + slot rendering for legacy addons.
  • Async Mail & Tasks powered by Action Scheduler.

🧱 Tech Stack

Layer Technology
Backend PHP 8.2+, WordPress, WooCommerce (HPOS), Action Scheduler
Frontend React 18 + TypeScript, Vite, React Query, Tailwind (optional)
Build & Package Composer, NPM, ESM scripts, Zip automation
Architecture Modular PSR4 classes, RESTdriven SPA islands

🧩 Project Structure

woonoow/
├── admin-spa/
│   ├── src/
│   │   ├── components/
│   │   │   ├── filters/
│   │   │   │   ├── DateRange.tsx
│   │   │   │   └── OrderBy.tsx
│   │   │   └── CommandPalette.tsx
│   │   ├── hooks/
│   │   │   └── useShortcuts.tsx
│   │   ├── lib/
│   │   │   ├── api.ts
│   │   │   ├── currency.ts
│   │   │   ├── dates.ts
│   │   │   ├── query-params.ts
│   │   │   ├── useCommandStore.ts
│   │   │   └── utils.ts
│   │   ├── pages/
│   │   │   └── orders/
│   │   │       ├── partials
│   │   │       │   └── OrderForm.tsx
│   │   │       ├── Orders.tsx
│   │   │       ├── OrdersNew.tsx
│   │   │       └── OrderShow.tsx
│   │   ├── routes/
│   │   │   └── Dashboard.tsx
│   │   ├── types/
│   │   │   └── qrcode.d.ts
│   │   ├── App.tsx
│   │   ├── index.css
│   │   └── main.tsx
│   └── vite.config.ts
├── includes/
│   ├── Admin/
│   │   ├── Assets.php
│   │   └── Menu.php
│   ├── Api/
│   │   ├── CheckoutController.php
│   │   ├── OrdersController.php
│   │   ├── Permissions.php
│   │   └── Routes.php
│   ├── Compat/
│   │   ├── HideWooMenus.php
│   │   └── HooksShim.php
│   └── Core/
│       ├── DataStores/
│       │   ├── OrderStore_HPOS.php
│       │   └── OrderStore.php
│       ├── Mail/
│       │   ├── MailQueue.php
│       │   └── WooEmailOverride.php
│       ├── Bootstrap.php
│       └── Features.php
├── woonoow.php
└── docs (project notes, SOP, etc.)

⚙️ Development Workflow

  1. LocalWP / Docker setup with WordPress + WooCommerce.
  2. Activate plugin: WooNooW should appear in the admin menu.
  3. Build SPAs:
    npm run build
    
  4. Package zip:
    npm run pack
    
  5. Upload dist/woonoow.zip into WordPress → Plugins → Add New → Upload.

🧭 Vision

“WooCommerce, reimagined for now.”

WooNooW delivers modern speed and UX while keeping WooCommerces ecosystem alive.
No migration. No lockin. Just Woo, evolved.


Description
No description provided
Readme 5.8 MiB
Languages
TypeScript 65.1%
PHP 33.1%
HTML 0.9%
CSS 0.7%
JavaScript 0.1%