New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore how to inject the Mini Cart
block into headers
#42385
Comments
We are waiting on WordPress/gutenberg#50103 to get started with this experiment and rely on auto-inserting blocks for injecting the |
I'll be AFK for the next two weeks, so I'm unassigning myself from this issue in case anyone else wants to work on it while I'm away. |
the issue's title is more generic than the description, the latest is more focus on core patterns.
WP6.2.2 / Gutenberg 16.1.0 / Woo 7.8.1 / Woo Blocks 10.5.0 We can only add it outside the navigation component. |
Hi there, @Marc-pi , thanks for reaching out to us! That's true; currently, inserting the mini-cart block within the navigation block is not possible. In this issue, we are exploring all possible venues for auto-inserting this block in the header (both inside and outside the navigation block): after verifying what's possible, new issues/PRs will be created to implement the enhancements. |
Auto-inserting blocks exploration
|
PS: while working on this issue I noticed the mini-cart block wasn't still being registered via a metadata file so I went ahead and made the change: woocommerce/woocommerce-blocks#10168 . @Aljullu I hope you don't mind I tagged you for reviewing this one since you have a lot of experience with this block =) |
Just noting a new tracking issue created for the Auto-Inserting Blocks API and what's being targeted for WordPress 6.4. At WCUS 2023 Contributor Day, I also did a rough POC for the API so it respected the |
Instead of creating our own WooCommerce Blocks header patterns, we would like to explore the possibility of injecting the
Mini Cart
block into existing Core and WP header patterns (more context here: p1682448941652889-slack-C02FL3X7KR6)There are some explorations already around this, check:
The text was updated successfully, but these errors were encountered: