Working with WordPress
Most people know that WordPress runs up to 25% of the internet, (some say 18%, some say 25%). A lot of it, in other words. This can mean anything from a blog some kid set up last week and never wrote on again, all the way through to large well known sites like Disney or BBC America. In fact, if you Google it you’ll find quite a few surprises when it comes to who runs their site on WordPress.
These days WordPress is super flexible and very powerful. It’s also secure, if you do your job on the admin side, and don’t just make the fancy templates and sexy looking favicons without thinking about the back door risks. Wordfence and if necessary using two stage authentication will take care of you. Not accepting dumb password structures, and maybe hiding the fact your site uses WordPress might also be worth looking into. Run regular backups too, unless you want to be an idiot. Once per week, unless you have lots of users and activity, then it’s once a day.
For most of us freelance or jobbing webdevs, WordPress is a standard, and we work with it to greater and lesser degrees, depending on client, project and budget demands. Yep, I agree it’s not always the best platform for some things, but in general, it absolutely kicks all other Open Source CMS into touch. Why? Because of the dev community online. Because so many of us work with it, there are a ton of people willing to share their knowledge and experience for free. This means if you have a problem, there is someone out there who already fixed it AND wrote about what they did. This is how to give back to the community, by sharing your own fixes and tricks. Best resources imho? See below.
Author: Pen ListerPen Lister is Academic Lead at Agilis, and has fifteen plus years in tech and new media, the last ten years spent lecturing at a London University. She’s now living in Malta, doing a PhD in augmented reality learning.
Copyright: This content is published courtesy of the kind permission of our guest bloggers in a non-exclusive rights arrangement, and articles may appear on our blog teams own websites in original or abridged form. All copyright is protected by author ownership.