Diversifying Revenue, the 50% Coding / 50% Marketing Lifecycle, Active Install Clawback, and Turbo Admin

WordPress Design & Development Around the Web for the Week of October 3

Diversifying Revenue Streams as a Solo Devpreneur

Web Developer, Entrepreneur, Organizer, and The Man in the Arena Carl Alexander has shared his journey creating Ymir, writing a book, freelancing, and how much he actually makes from all that to live each month. TL:DR; Not as much as you’d think. This kind of transparency into the entrepreneurship side of WordPress can be so valuable and helpful for everyone to see. I suspect many of us can relate to this, especially in the WordPress space where our abilities as developers, designers, and builders are often taken for granted or undervalued. Carl’s answer is creating a Github sponsored page, which is a great way to show appreciation for a developer’s work, especially the free plugins that they maintain. Aurooba Ahmed has made a list of developers you can sponsor as well.

The 50% Coding 50% Marketing Lifecycle

We see it all the time: some application or website comes out with half the features of a similar idea you’ve been toiling away on for months, maybe years, but they get all the traction because they market the heck out of their brand. Chances are they also probably hired a small marketing team or agency to help them, and for many of us, we don’t have that luxury. Enter the 50:50 concept from Jon Yongfook of Bannerbear. It sounds like it would be complicated but it’s really simple.

Oh Look, Somebody Took Something Away and Didn’t Communicate About It Well, That Tracs

This week’s #WPDrama has surrounded the abrupt removal of the install growth charts for security reasons on WordPress.org and the Trac ticket created in response to that from Post Status member Mark Zahra which highlighted the frustration felt across the plugin community. I cannot stress enough that all of these frustrations could have been avoided by good communication with the community right after the removal. Instead, everyone was left to piece together different conversations on Twitter and Make WordPress Slack to understand what might be the future for getting similar or even better analytics into the Plugin Directory. As of this writing, there still is no response from the team that removed this feature or what a process might look like for future analytics improvements. Again, an open-source project the size of WordPress should have a team just to help write a synopsis of major changes so anyone can understand the why, when, where, and what’s next.