As I’m starting my career in Web Development, instead of taking the easy (generic) route, I taught myself HTML5 & CSS3, while learning about frameworks such as Foundation and Bootstrap.
My first client, her previous “developer” used a WordPress Theme, plug-ins to automate certain features of her site and in her mind, the guy was a developer, and I am biting my tongue, but does anyone have the right to call themselves a Web Developer if they are using WordPress, click and install themes, automated plug-ins and don’t understand any code?
I’m not into WP myself (or frameworks for that matter) but as I understand it, there are WP developers and there are WP developers.
As in those like you say, who cobble together a site from a theme and various plugins with very little understanding of the code.
But there are also WP developers who do have an in-depth knowledge of html, css php, and sql that would deserve to be called “real developers”. These may be ones who are modifying or creating their themes. Or they may just be using WP for speed and convenience, or perhaps the client wanted WP so they have a CMS they can edit themselves.
I don’t know if there is an appropriate term. “WordPress user” seems close, but could also apply to anyone running WordPress. Maybe “WordPress Expert”?
As an analogy, If I knew how to do magic using Illustrator, that in itself would not make me a Graphic Artist, and I certainly would not want to be seen as one. On the other hand, being skilled in using Illustrator would be an asset.
So the question seems to be what importance is given to using a tool vs. what importance is given to understanding what the tool is doing. Most certainly, to be a WordPress Expert I think one would need to have at least some skill in HTML, CSS, JavaScript and PHP at least within the context of WordPress. But true. that alone does not a developer make.
I have to say that I often rely on WP plugins even if I could develop them myself. There are several reasons like:
Why do you need to reinvent the wheel? My problem might have already been solved with the plugin
Faster deployment as it is already done
Plugins are often updated and maintained by third parties, taking the load from my shoulders
Money. The client might not be paying enough for me to do effort and time might be a constraint too
I could give you more reasons to use a plugin instead of doing the development yourself.
With this, I mean… don’t think that bad of that developer… he might be a real developer but he might also have good reasons to use a plugin instead of doing it himself.
Although, it is true… there are WP “developers” and WP developers…
Some fair points made, although I will say her previous “Developer” used a theme and plug-ins and as the website was up and running in 2 weeks, it all points to a WordPress “Developer” who purchased a theme.
The client is also someone who fancies themselves as a designer, telling me about elements that have an edge (when they don’t) while their choice of header image has become an obsession for the client, who believes it offers impact, when it doesnt!
But, as this is a service role, I understand this is all part of being a freelance web designer and possibly a reason why many choose a different path, such as build templates, saves the hassle of dealing with clients who don’t understand their website should be designed in a way to help their business grow, rather than be a showcase for their personal design tastes.
I’d definitely say it depends on the developer (and as Ralph pointed out, the important part of that judgement would be the “do they understand code” part.
I build websites using pre-purchased themes and plugins sometimes. I don’t find anything wrong with that, and frankly, I really don’t care if anyone else does. If the site meets client requirements, is done quickly, in-budget, is responsive and a generally decent addition to the Internet, I have no problem with it.
I also have no problem with clients that want a custom built website without using any third party themes or UI elements at all, and we can custom code the whole thing. It’s just more expensive and time consuming, but it’s all work to me
At the end of the day, the things I would consider:
The client needs to know what is happening. If the client knows it’s a purchased theme, and how, generally speaking, it’s being built, and they don’t care, fine. It doesn’t really matter how simple it is, people will still pay for it, often times. I’ve literally had clients pay me to update copy on an existing WordPress website - they just didn’t want to be bothered figuring out how to navigate the admin panel. To some people it’s just literally not worth their time or mental energy.
I think that, regardless of the specific project at hand, any “WordPress Developer” should know at least some basics about PHP, HTML, and CSS. I think it’s a genuine help when theme files or plugins need altered, or custom functionality needs bolted on.
