Check out my blog post WooCommerce – The Leading Open eCommerce Framework featured on UpCity. In this article I discuss where WooCommerce and open-source fits into the overall eCommerce Platform segment and popular proprietary systems. I also discuss community events and some technical tips.
Recently a client brought in an interesting request to split their store off onto a subdomain, for example https://store.mywebsite.com. There are both advantages and disadvantages to this idea. I thought I’d share those insights with my audience. Pros The plugin load gets split, so each site runs less plugins or customization risks above the core […]
During a recent Amazon Pay webinar I attended entitled Optimizing Your Mobile Checkout, I couldn’t help but notice their prioritization of credit card fields. This stuck out to me because I’ve observed all manner of credit card gateway user interfaces. Research data is telling us to pay particular attention to these fields. Of the presenter’s […]
After working with dozens upon dozens of WooCommerce sites, here’s some of my best tips…
Somebody call the cops, because it’s got to be illegal to look that good!
Check out these good looking and effective WooCommerce powered websites…
Recently I’ve been assessing WooCommerce sites based in California as part of a new client outreach effort. Through this process and its first 100 subjects I’ve discovered more data on where people host their WooCommerce sites, what errors are showing up (SSL, JS/console, ADA, state compliance), performance metrics, who they use for hosting/registrations/email, what all plugins they use, and which theme they selected. I’m compiling this data into something more useful. For the time being, here’s the data on theme usage.
There’s an irritating message we see whenever a site has modified WooCommerce template files and the WooCommerce plugin updates one or more minor versions. There can be one or more default WooCommerce template file(s) that had been copied into the child theme and the HTML code tailored for the design. It’s not unusual to see up to 10 of these conflicts on a custom designed site. I’ve even seen sites with dozens! On sites affected by this development strategy every WooCommerce core update causes fear and the responsibility to test the update on staging prior to updating on production.
How much should your developer be charging you? This is a complex question to answer because the range is quite wide and there are many factors that contribute, such as location cost-of-living, skill level, how sharp the developer is and how busy his/her schedule is. I’ll provide you with United States oriented research I’ve come-up with.
Join WooCommerce Los Angeles Meetup back at WeWork Santa Monica Broadway on Wednesday, June 5th at 6:30pm for a demonstration session on database cleaning.
Awhile back I voluntarily moved into a role developing a customized enterprise WooCommerce platform to power a couple dozen properties. I eventually came to understand this as a Skunkworks – a project “developed by a small and loosely structured group of people who research and develop a project primarily for the sake of radical innovation”, Wikipedia. The company did not adopt the solution. It was a categorical failure to them, yet a personal success for me to learn from.