5 Free Ways to Bulletproof Your WordPress Site: Eric’s presentation from WordCamp Seattle that can also be watched on WordPress.tv Some of the interesting parts include backup, security, performance and general tips including improving search and usability, all with links to relevant plugins and tools. If you are new to WordPress or want to refresh your blog, this is a good read through. Thanks Linked In messages.
An avid fan of business, education, technology and finance. I lead a lean, highly focussed and capable team of Java Back End developers and Front End developers through a maze of complex software wizardry to fulfill the web maintenance needs of a large chemical manufacturer. As per Myers-Briggs Personality Types, I am an ESTJ. I pride in a project completed on time and according to plan. My hobbies include all kinds of technology, anything that I can taste and anything that goes fast or flies in the air. I like to read business books and comics in my spare time.
Obviously Powered by WordPress. © 2003-2013
Thanks for bring this to my attention… Over the last couple of years I have had 3 of my web sites (including WordPress blogs) hacked! It is very annoying, presents a bad picture to your readers and kills you in Google.
Thanks again, Gary.
yeah I agree this is a great article,
although, as far as accessibility and section 508 guidelines go, speaking from a blind users point of view who uses screen reading software on a daily basis to use computers, wordpress in general doesn’t really follow section 508 guidelines very well. The admin interface alone doesn’t play well with screen readers, same with the default theme that comes with wordpress, so how can we expect these types of things to help when wordpress itself is part of the problem? 🙂 not to mention, just about every plugin I’ve ever downloaded doesn’t pass section 508 guidelines, or W3C XHTML validation, and its much harder to design a site that follows W3C XHTML validation, not to mention all section 508 guidelines, which are much harder to follow then valid XHTML.