Fixed 2 critical issues: 1. ✅ Header Missing in Non-Fullscreen Problem: Header was using 'fixed' positioning on mobile, breaking non-fullscreen layout Solution: Changed back to 'sticky' positioning for all modes Before: className="md:sticky ${fullscreen ? 'fixed top-0 left-0 right-0' : ...}" After: className="sticky ${fullscreen ? 'top-0' : 'top-[32px]'}" Also fixed hide animation to only trigger in fullscreen: ${fullscreen && !isVisible ? '-translate-y-full' : 'translate-y-0'} Result: Header now shows correctly in all modes 2. ✅ PageHeader Covered by Submenu Problem: PageHeader had complex top calculations that didn't work Solution: Simplified to always use top-0, rely on z-index for stacking Before: const topClass = fullscreen ? 'top-0' : 'top-[calc(10rem+32px)]'; After: // Always top-0, z-10 ensures it stacks below submenu (z-20) className="sticky top-0 z-10" Result: PageHeader now visible and stacks correctly below submenu How It Works: - Submenu: sticky top-X z-20 (higher z-index, sticks first) - PageHeader: sticky top-0 z-10 (lower z-index, stacks below) - When scrolling, submenu sticks at its position - PageHeader scrolls up until it hits top-0, then sticks below submenu Layout Flow (Non-Fullscreen Mobile): ┌─────────────────────────────────┐ │ Header (sticky top-[32px]) │ ← Now visible! ├─────────────────────────────────┤ │ TopNav │ ├─────────────────────────────────┤ │ Submenu (sticky, z-20) │ ├─────────────────────────────────┤ │ PageHeader (sticky, z-10) │ ← Now visible! ├─────────────────────────────────┤ │ Content │ └─────────────────────────────────┘ Layout Flow (Fullscreen Mobile): ┌─────────────────────────────────┐ │ (Header hidden) │ ├─────────────────────────────────┤ │ Submenu (sticky top-0, z-20) │ ├─────────────────────────────────┤ │ PageHeader (sticky top-0, z-10) │ ├─────────────────────────────────┤ │ Content │ │ ( + ) │ ├─────────────────────────────────┤ │ Bottom Nav │ └─────────────────────────────────┘ Files Modified: - App.tsx: Fixed header positioning and hide logic - PageHeader.tsx: Simplified positioning logic Result: Clean, working layout in all modes! ✨
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, my‑account) 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/adminwith custom login ✨
🔍 Background
WooCommerce is the most used e‑commerce engine in the world, but its architecture has become heavy and fragmented.
With React‑based blocks (Checkout, Cart, Product Edit) and HPOS now rolling out, many existing addons are becoming obsolete or unstable.
WooNooW bridges the gap between Woo’s 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/My‑Account.
- Full SPA Toggle – optional React‑only 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 PSR‑4 classes, REST‑driven 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
- LocalWP / Docker setup with WordPress + WooCommerce.
- Activate plugin:
WooNooWshould appear in the admin menu. - Build SPAs:
npm run build - Package zip:
npm run pack - Upload
dist/woonoow.zipinto WordPress → Plugins → Add New → Upload.
🧭 Vision
“WooCommerce, reimagined for now.”
WooNooW delivers modern speed and UX while keeping WooCommerce’s ecosystem alive.
No migration. No lock‑in. Just Woo, evolved.