I’ve recently become a bit of a WordPress convert.
Previously I’ve seen WordPress as a bit of a website ‘cop-out’ where you let something else do all the hard work, opting to code everything myself. In smaller projects, this was appropriate as WordPress wouldn’t necessarily be suitable for them. However, I’ve been involved in some larger website projects lately and it’s become a large part of my development arsenal.
The other day I was involved in a project that’s structure was mapped out and everything was pre-planned. I had the website up and running (albeit unstyled) to match the planned structure within a couple of hours. As you can imagine this made me a very happy guy!
I’m now looking into new ways I can use WordPress on existing projects that I feel may benefit.
One of the issues I’m facing is the errors. I’m normally up against coding errors, where I can in-fact jump into the code, identify the error and blast it, whereas WordPress gives me configuration errors, plugins that don’t allow me access to the administration screen and third party issues. Some may not be as easily fixed as I’m used to.
However, I’ll plough on and get to know the software more, which is more like where I’m tripping up.
Powered by Facebook Comments