Manos Psychogyiopoulos shares the story of…
Manos Psychogyiopoulos shares the story of how he started using WooCommerce and why:
“As a WooCommerce developer, I believe that our biggest strength is our WordPress technology and community heritage.”
Manos Psychogyiopoulos shares the story of how he started using WooCommerce and why:
“As a WooCommerce developer, I believe that our biggest strength is our WordPress technology and community heritage.”
π Chris Lema shares why Liquid Web “built him a better review plugin” for WooCommerce: “We built a WooCommerce extension that would help store visitors evaluate the reviewer and understand the context. And that’s what makes the plugin better than the other ones out there. We took our inspiration from UnderArmour.”
If you work with WooCommerce but aren’t familiar with the developer chats, you can read summaries of them at woocommerce.wordpress.com. π Here’s a reminder that the recently launched WooCommerce 3.7Β requires at least PHP 5.6.20 and WordPress 4.9. It also ships with Product Blocks 2.3 for the WordPress Block Editor and comes with new features…
Elliot Taylor and his team at Raison have released a nice WooCommerce plugin called Grow with WooCommerce. The free plugin (available on WordPress.org) allows you to set goals and then offers a month by month summary of how you are doing. WooCommerce reporting and metrics leave room for improvement, and this is a nice improvement….
Corey Maass and Cory Miller share the messiness of building a WordPress product live. They reveal the initial version of Crop.Express, a plugin designed to crop a featured image within the WordPress workflow and discuss their progress and ongoing development.
Ah, Friday. If you’re slacking a bit, or just looking for some good stuff to listen to or watch this weekend, let me help. Here are some of the best things I’ve seen this week: A look at WordPress performance Well, this is actually from WCSF. A lightning talk by Zack Tollman. Yesterday, I shared…
There is a new WordPress.org naming policy that prevents plugins from using the names of companies and other plugins as the first item in the name and slug. For instance, if a reader submitted, “Post Status Extender Widget” to the repo it wouldn’t be acceptedΒ but, “Extender Widget for Post Status” would. Here’s the full text…