20140515-202637.jpg

5 Things I’ve Learnt About WordPress Sites

The more observant of you will have noticed I’ve moved. No longer do I blog on a WordPress.com site, but on my own self-hosted website powered by WordPress.org! Admittedly, the place is still a little basic. I’m rocking an oh-so-original Twenty Eleven theme. But the basics are here and I’m looking forward to making this a place you’ll want to visit. If there’s anything you’d like to see, drop a comment!

But what you see here are the results of my efforts this weekend and I’ve already learnt quite a few things. In the spirit of warning anyone following a similar path to me, I present my findings to the board:

Don’t be a hero: I decided that it would be best that I install WordPress manually, using an FTP client and all sorts. I thought it would teach me a thing or two. It did. It taught me not to be an idiot and to use the one-click option my host provided. It was called Softaculous and it managed in two minutes what I couldn’t in sixty.
Get plugged in: There’s a lot of great plugins for WordPress and getting them sooner rather than later can make your life a lot easier. Trust me. I’d recommend Jetpack for a whole host of WordPress extras, Google Analytics for WordPress for a quick and easy install of Google Analytics and Google XML Sitemaps to make your site easier for Google to index.
Find your inner child: Creating a child theme is vital if you’re going to start customising a theme, as any updates will wipe your changes. Doing this looked a little tricky so I cheated; I used a plugin that did it for me. Gotta love those plugins!
Nothing doing: Nothing found for wp-login or wp-admin? When I got that error it was my theme causing the problem. I had to use an FTP client to change the name of the theme’s folder in wp-content/themes, which forced WordPress to default back to Twenty Eleven. That fixed it, and I deleted the offending theme.
Fitting in: The Twenty Eleven theme liked to display the side bar underneath my posts. This was because of a line of code in the header file. Making a copy of “header.php” and pasting into my child theme’s folder and then deleting solves the issue.

I’m still digging around so I’ll share any more tips I discover. Any you’d like to share? Let me know!

Talking rot or making sense? I'd like to hear your two cents!