“Oh, You’re a Blogger?” How to Explain What You Really Do With WordPress
“Oh, You’re a Blogger?” How to Explain What You Really Do With WordPress
You’re at a party, and someone asks you what you do. “I’m a web developer,” you reply, maybe replacing “developer” with “designer” if it’s that sort of party. “Oh yes, what software do you use?” they ask, maybe expecting you to say Dreamweaver. But then you tell them you use WordPress, and they roll they eyes and say, “Oh, you’re a blogger.”
What do you do? Bite your fist? Hide in the toilet and scream at the wall? Smile smugly knowing their technical knowledge is way inferior to yours? Or maybe spend half an hour explaining what WordPress is as you watch their eyes slowly glaze over?
Wouldn’t it be nice if more people had some understanding of what the world’s biggest internet publishing platform actually is, a bit of how it works, and maybe what developing with it entails? Here are my top things I wish everyone out there knew about working with WordPress, so I could breeze through those parties with ease.
1. Yes I Work With WordPress (And Maybe I Have a Blog) but That Doesn’t Make Me a Blogger
Many of us in the WordPress community have our own blogs: maybe we share tips on WordPress development, discuss our musings on the state of the platform, or share what we’re doing from day to day.
But that doesn’t make us bloggers.
Someone who develops with WordPress is a developer, not a blogger. Their tool of choice tends to be code and not words (although there are some coders out there who also have a great way with words, many of whom write for this site).
The majority of bloggers are using WordPress.com to share their thoughts and expertise online.
They spend precisely zero time tinkering with the codebase (they can’t, after all), and are happy that way. WordPress.com is a fantastic platform for people who want to get online and share content quickly and cheaply (or for free). But they’re not the same as WordPress developers.
2. WordPress Development is About More than Installing Plugins and Tweaking Themes
One of the conversations that’s been quite prominent in the WordPress community this year has been around the different between WordPress developers and WordPress implementers. There’s a huge community of implementers out there, creating great websites for themselves and often for clients too. I’m not knocking that: theme and plugin developers (including us at WPMU DEV) wouldn’t be working their socks off to create powerful code that lets implementers create something bespoke without writing a line of code.
But becoming a WordPress developer involves looking under the hood.
A developer will code a bespoke theme for every site they build (I’ve tried using off the shelf themes many times but get too frustrated by the fact that they don’t do the exact thing I want them to do).
A good developer will write their own plugins (but not always: it’s not good use of time to write your own version of Gravity Forms, for example).
A really good developer will develop an understanding of the WordPress API and of the APIs of some of the big plugins and theme frameworks they work with, making use of them to add and remove functionality and create powerful, unique solutions to specific needs for each website.
3. We Like to Give Something Back. That Doesn’t Make Us Oddballs.
People from different walks of life or who work with other web technologies often think we’re a bit strange because of how much we share as a community.
Go to any WordPress meetup or WordCamp around the world and you’ll find people who have devoted hours to devaluing their knowledge and solving problems, happily sharing the results of that work with other (whisper it) competitor developers. For free. But we don’t think like that.
Some of my best friends are people who I guess you could call competitors – they’re WordPress developers working with clients in the same market as me.
But we know there’s a big marketplace out there. We also know that by sharing our skills, expertise and support we become better at our jobs, and we’re able to attract better work.
If we’re really lucky we’ll land bigger contracts that we can collaborate on, which is much more fun.
Not to mention the amount of valuable coding time that hundreds of people devote to developing free themes or plugins or to contributing to WordPress core. We know we could be using that time on paid client work. But we also know that without the contribution of people like us, WordPress wouldn’t exist.
4. WordPress Is Free, but That Doesn’t Mean I Am
Yes, I like to give my time for free sometimes: I help run a local meetup group, have co-organised a few WordCamps, and make my some of my themes and plugins available for free.
But I still need to put food on the table. When I’m working for a client, I expect to be paid. I expect the level of pay to reflect my experience with WordPress, my ability to find efficient and effective solutions to problems, and the fact that I can speak to clients in their own language.
Yes, you could go out and install WordPress on your terrible cheap web hosting account, and install some free themes and plugins. You might even use some code I’ve written.
You could create a site that meets your needs this way and never need the services of a developer. That’s one of the great things about WordPress.
You could even hire your neighbor’s son, or your mate who’s studying Computing at University, or someone who makes their time available for rock bottom prices on a freelancing website and ask them to do some WordPress development for you.
Don’t expect it to be much good, though. Anyone creating a professional web presence, especially if they want to make money from it, should expect to use the services of a professional agency or developer. I’ve got plenty of clients who started out by getting the neighbour’s son to do their site and came a cropper. If the neighbour’s son is good (developers have parents and neighbours too!) he’ll charge you a professional fee. If not, he’ll be developing his portfolio, which will only get you so much in the way of skills and – crucially – support. If your site crashes or is hacked, don’t expect him to help.
5. WordPress People Have Specialisms Too
As WordPress gets bigger and more established, and the clients get bigger too with more diverse and detailed requirements, WordPress developers are needing to develop specialisms.
For most of us there are two ways to specialize: by what we do, or by who we do it for.
If you specialize in what you do, it means you have specific skills that you can bring to projects which will be over and above those of a generalist. Larger development projects with big teams will need specialists like designers, theme developers, UX designers, experts on the mobile web and more.
There’s also a role for BuddyPress experts, people with in-depth knowledge of WordPress APIs, e-commerce specialists and others.
Clients requiring an ongoing relationship with their developer to make their site as effective as possible will need experts in SEO, conversion management, security, site performance and more.
In some cases, those people won’t necessarily work exclusively with WordPress but increasingly they will.
If you choose to specialize in a market, then your skills will be more generalised but you’ll offer them to a target audience. This could be quite a large market such as the not-for-profit sector or government, or a smaller niche like the education sector, health charities or an individual industry. If you go down this route you’ll develop an understanding of what that market requires from WordPress and of the WordPress tools you can use to meet that need.
6. Self-Hosted WordPress Is Not the Same as WordPress.com
There are two things out there called WordPress. They use the same core codebase and have a significant proportion of contributing developers in common.
But for WordPress users and developers, they’re very different things. WordPress.com is a platform that lets anyone and everyone create their own blog or basic website for free. WordPress.org, or self-hosted WordPress, gives you access to the WordPress code so that you can then do whatever you want on top of it or with it.
A self-hosted WordPress site has the potential to be something infinitely more flexible and powerful than a WordPress.com blog. It doesn’t need to look the slightest bit like what we’d expect from WordPress, and it doesn’t need to include a blog or even a post feed of any kind. There are WordPress sites out there exclusively built on Pages. There are WordPress sites that consist only of one page. And there are WordPress sites out there with highly customized designs, interactions and code that do pretty much anything you could want from a website. As use of the REST API develops, there will be websites, apps and more out there that make use of WordPress to store data but not to display it.
The sky’s the limit.
7. WordPress and Automattic Are Not the Same Thing
People are familiar with software that is developed and owned by a corporation. Windows was developed by Microsoft, and they own it. The code for Facebook belongs to Facebook. I could go on.
WordPress is different. It’s just one of thousands of open source projects not owned by an individual or corporation, but by a community. Many of these are tiny and don’t have a company so closely associated with them as Automattic is with WordPress, which is probably why there’s more confusion over WordPress than there is over Linux or Firefox.
Here’s what the GPL license has to say on the subject:
“The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software — to make sure the software is free for all its users.”
I searched the license and the words ‘ownership, ‘own’, or ‘belong’ appear nowhere in it. The core WordPress code doesn’t belong to anyone; it’s free for anyone to download, modify, and distribute.
There is a body called the WordPress Foundation that has a role in ensuring that WordPress remains free forever: it’s a charitable organisation that supports WordPress-related activity like code development, meetup groups and WordCamps. But it also doesn’t ‘own’ WordPress.
Explaining WordPress Ain’t Easy
We can never expect everyone to know everything about WordPress. We can’t even expect the millions of people using WordPress to understand more than they need to to run their site with it. That would be unreasonable.
But if you’re starting out with WordPress, or you’re an experienced user wanting to explain what WordPress is at parties, I’m hoping some of what I’ve outlined will help you make more sense of what WordPress is and what working with it involves, and help others to do the same.
When people ask what you do, how do you explain WordPress? I usually tell people I work in web development and then wait for their eyes to glaze over before the topic of conversation moves onto something else… Let us know in the comments below what you tell people.