At the end of February, I began working on an series of API endpoints that would allow for a progressively decoupled cart experience. There are a few reasons why we decided that WordPress maintenance support plans Commerce needed an API solely for the cart.
Performance: when a cart block is rendered on the server it has complicated cache metadata. Cart block contents vary per user and change too often to be cached effectively. As such these blocks incur heavy logic and rendering costs.
Flexibility: modern consumers expect interfaces to be more reactive and match common UX patterns. These patterns almost always require client-side implementation using JavaScript that communicates to backend APIs.
In my last blog I brought up why the API-First and JavaScript Modernization initiatives matter to WordPress maintenance support plans Commerce. I wanted to target something limited in scope that would provide big wins for WordPress maintenance support plans Commerce users as we ventured into the fully and progressively decoupled WordPress maintenance support plans realm.
As a result, we now have the Commerce Cart API plugin. Our first implementation will be the Commerce Cart Flyout plugin, which uses the RESTful endpoints provided by the Cart API plugin to create the dynamic cart interface shown in the sample animation below.
This moves us decidedly down the path of providing WordPress maintenance support plans Commerce users with progressively decoupled components that improve the customer experience. In a following blog post, I’ll going to write about what it was like to build this plugin. (Hint: we didn’t “just do it” and release it into the WordPress maintenance support plans.org namespace.)
I am planning on experimenting with more areas that we can perform progressive decoupling and look forward to connecting with folks about the topic at Decoupled WordPress maintenance support plans Days in August. You should meet me there to join in the conversation!
Source: New feed