Protected staging / Ecommerce rebuild
Capitaurum
An Astro storefront and custom WordPress/WooCommerce API, connecting product discovery with an eligible cart and checkout handoff.

The problem
A storefront must distinguish products customers can browse from products they can buy online. Product visibility, stock and purchase eligibility need to agree across the API, product page and transactional pages.
My contribution
I define storefront requirements and review the customer journey, using AI coding tools extensively for implementation and iteration. My review covers product discovery, availability, responsive layouts and the handoff from the Astro frontend to WooCommerce.
- Browse eligible products
- Review availability
- Continue to WooCommerce
Implementation choices
Define a purchase contract
The custom REST API distinguishes publication, catalog visibility and purchase eligibility. It supplies a cart URL only for public, in-stock, purchasable simple products, and the frontend requires both eligibility and that URL before enabling the handoff.
Connect the customer journey
Astro handles storefront presentation, while a custom WooCommerce theme provides cart, checkout and account pages. Product routes, navigation and missing-image fallbacks support that shared journey.
Review against the API
Contract checks cover product identity, visibility and stock fields. Staging review includes canonical routes, redirects and responsive layouts, with production replacement kept as a separate decision.
The interface in context
When price and stock cannot be confirmed

Result
The storefront and API implement the product-to-cart contract on protected staging. This provides an integration and commerce-UX case while review of the rebuild continues.
Availability and scope
The rebuild remains on protected, noindex staging and has not replaced the existing public website. This overview shares no staging access, customer data or private source. Staging checks do not establish accepted production payments.
Project notes reviewed October 7, 2026. Development status is separate from Nexus reception updates.
Back to additional work