I work with WordPress nearly every day. This website is powered by WordPress, as are most other websites I manage. Until I am presented with a compelling reason not to, I’ll be staying with WordPress.
As I’ve stated before, I’m a “Made in the USA” fanatic. So, I’m somewhat biased in my opinion of WordPress. Matt and other WordPress developers continue to strengthen my bias, as they continue the development of WordPress. Yes, I know not everyone contributing to WordPress is based in the US. I like that part, too.
If I insist on demanding “Made in the USA” why am I using WordPress, when all of the development isn’t in the USA?
It’s simple really. The bigger the developer pool, the better the software, which is the basic premise of open source, to begin with.
Through many development life cycles, WordPress remains easy to install, easy to use and easy to upgrade. It is lightweight, portable and expandable. It is all these things and it is conscious of current web standards.
While I may be biased towards WordPress, at the end of the day, I gage the viability of any web-based system and its developers, by web standards compliance.
Yes, I absolutely believe the design of a website is important. However, looks only go so far. Every website must also be easy to find, easy to use and must work correctly in the user’s web browser.
If you pay close attention to web standards, you know that even the best efforts, to accommodate such standards, can still result in errors. The basic idea though, is making websites just as visually appealing and easy to use in one web browser, as they are in another.
If a website was developed strictly for Internet Explorer and web standards weren’t considered, those browsing with Apple’s Safari, Google’s Chrome, Mozilla’s Firefox or Opera, may not have the same user experience. This can cause disappointment and can ultimately result in lost business.
I’m pretty happy with the efforts of the WordPress core development team, to maintain web standards compliance. However, I do not feel the same about many of the numerous WordPress Plugin developers.
WordPress Plugins are intended to extend the abilities and functionality of WordPress. Many plugin developers though, neglect web standards altogether or give them very little consideration.
The last thing I want is garbage code in my clean WordPress environment. Yet, time and time again, garbage code is what I get, when I extend WordPress with approved plugins. I end up making numerous modifications to the plugins code, so it can be web standards compliant. Usually, I have to fix the readme.txt file, too.
With all these modifications needing to be made, I’m wondering who should get credit for the Web Standards Compliant WordPress Plugins.
Don’t take this the wrong way. I’m not going to start repackaging each plugin I modify, as my own. However, I may start publicly questioning the legitimacy of the plugin developers and the validity of the WordPress Plugin approval process.
I have done a little of this in the past and the plugin developer, almost always, blames validation issues on the developer of WordPress Themes. This is why I test each plugin, in a clean WordPress environment.
The World Wide Web Consortium (W3C) is an international community that develops standards to ensure the long-term growth of the web.
The W3C works hard to make information about web standards available publicly. So, why is it that WordPress plugin developers can’t manage to build web standards compliant plugins?
If you need help with a WordPress website, contact me over on https://bamajr.com/; my business’ website.