A headless Magento payment option is more than a button in the checkout
PWA Studio 10’s payment-extension example shows why frontend support, backend configuration and order handling have to agree.
THE NOESIS JOURNAL
Headless Magento
Read the article: A headless Magento payment option is more than a button in the checkout
PWA Studio 9 makes a useful case for keeping storefront changes explicit
February’s extension work can reduce copying, but a merchant still needs to understand which custom behaviours the project owns.
A headless storefront needs to know when its remembered information is out of date
PWA Studio 8’s caching work is a useful starting point for a January review of prices, baskets and signed-in data.
A headless checkout is complete only when the awkward order works too
PWA Studio 8’s completed cart and checkout provides a useful starting point for testing the whole buying conversation.
Headless Magento customisation should not become a permanent copy of the framework
PWA Studio 7’s extension points offer a useful way to discuss what your storefront owns and what it inherits.