Does any of this sound familiar in your WordPress work?

We’ve been thinking a lot about how people learn WordPress, and what drives success in WordPress development learning.

Over years of teaching WordPress development, we’ve realized something: learning WordPress development is really hard.

I learned a few things today: first, that WordPress has a built-in colorpicker called Iris, and second, that you can use it on the front end of your website if you need custom colorpicker functionality.

One of the hardest things about debugging or extending WordPress plugins is often simply finding where a piece of code lives. A plugin may have many thousands of lines of code across dozens of PHP files, organized however the plugin developers thought made sense to them.

A lot of people have written about how competitive WordPress has become and how difficult it is to make money with WordPress from products such as themes and plugins. Others believe there’s still plenty to be thankful for in WordPress.

“Everyone’s a critic,” as the saying goes, and nowhere more so than around Gutenberg, the upcoming content editor overhaul slated for WordPress 5.0. Gutenberg has been the subject of soaring vision statements, angst-filled comments sections, and dozens (hundreds?) of cautiously-optimistic-to-mixed-to-confused-to-skeptical-to-concerned reviews.

Our article this week on Beaver Builder, WordPress, and hosted builders such as Squarespace has drawn a lot of discussion here and on AWP, for which we’re grateful.

This piece attempts to give clarity on a tricky and open-ended question: “How long does it take to build a website in WordPress?” It’s been updated on May 30, 2017, to discuss the time cost of training and supporting site owners.

David and I searched for quite a while for a good time tracking solution. In fact, at one point we were paying a fair amount every month for a project management/proposal-generating/time-tracking solution that we just used as a glorified time tracker.