![woocommerce themes woocommerce themes](https://i.pinimg.com/originals/a5/31/6a/a5316aba7a856d986fb817e6e6a8c87f.png)
It just is the initial step of moving towards our vision of ‘Store Editing’ where merchants are able to completely customize the layout of their stores using all the opportunities available through the block and site editors.” “We’re essentially wrapping the rendered PHP template in a dynamic block. “This initial iteration will be a straight port of the existing PHP templates and have a placeholder for the rendering of the template in the editor,” said Ethier. Top-level templates like single-product.html, archive-product.html, taxonomy-product-cat.html, and taxonomy-product-tag.html will be available to any block-enabled theme soon. It will take some time, but you will not see block themes showcasing WooCommerce shops without the plugin first laying the groundwork.īlock templates are a high priority. The team is making progress and has a few things shooting through the pipeline. WooCommerce is a heavy plugin with a history entrenched in the pre-block era of WordPress and has an ecosystem of third-party add-ons it must be careful not to break. However, the answer is more complex than that. “Whether or not we will land it in the first iteration is still unknown.” “That’s definitely the target we’re shooting for,” he said. He agreed that the block system could make it easier for things to simply work without specialized theme support. I reached out to Darren Ethier, an engineering team lead within Automattic who works on the intersection between WooCommerce and Gutenberg. The same should be said for any other element of creating an online shop. If a user wants a cart item in their nav menu, it should be as simple as adding a block via the site editor. The long-term goal of plugins like WooCommerce should be to work without theme support. One of the things I love about the block system is that it creates a standard for all themes and plugins to build from. When it gets to that stage, theme authors will follow. However, I have no doubt that we will see more block theme authors catering to WooCommerce users as we move forward.Īll of this is a long-winded way of saying the responsibility of WooCommerce working in a block world is on WooCommerce itself.
WOOCOMMERCE THEMES FREE
It can be a maintenance nightmare at times, particularly when it comes to free themes. Like with any third-party plugin that outputs something on the front-end (e.g., bbPress, Easy Digital Downloads, etc.), it is the theme author’s choice of whether they want to take on the burden of supporting integrations with projects that are not their own. I imagine that some will and others will not. I cannot say whether any of their authors have plans to do so in the future. When looking at some of the recent block themes that other developers have released, I have yet to see any integrate with the WooCommerce plugin. It is still crucial that we make a distinction between the two.
![woocommerce themes woocommerce themes](https://athemes.com/wp-content/uploads/zakra-free-agency-wordpress-theme.jpg)
So, there is likely some crossover among developers. Granted, WooCommerce is owned by Automattic, one of the largest contributors of resources and people. It is unrelated to the core WordPress and Gutenberg projects. But that seemingly never happens because WooCommerce always seems to be the “afterthought.” Bradįirst, I want to make sure all of our readers are on the same page. And, if theme authors and WP core developers always, Always, ALWAYS started simultaneously with one or two WooCommerce folks on board, it would absolutely shorten the time needed for store owners to receive the benefits of FSE (and remove some of their pagebuilders!) and for WordPress to get more Shopify business over to WooCommerce. (Yes, WC can be run, but w/out a cart header, shoppers don’t know where to click after an item is in their cart). Why not get everyone on the same page immediately? That way theme authors can address putting the cart elements in the header template. However there does seem to be a behavioral pattern of WooCommerce elements being a bit of an “afterthought” that simply brings up the rear about a year or year-and-six-months afterwards. Again, one should not expect perfection at a “developmental” stage. I’ve taken Blockbase and all the other FSE themes for a spin on LocalWP, and none of them have any WooCommerce elements in them. Where is a persistent cart header? Where are the templates for /single-product? There’s all kinds of elements which can be developed right along side of other teams working on FSE, but it seems to (again, consistently) not happen. It’s a bit like it’s an afterthought to simply scramble in the elements of a solid WooCommerce store. At what point are FSE theme developers going to start integrating and considering WooCommerce for their themes? WooCommerce has almost always seemed to lag behind all other considerations.