I gave a talk at WordPress North East last week, and have finally remembered to type up some of the notes to accompany the slides.
The talk was called A responsive workflow for WordPress theme development (catchy, I know), and was a run through of how I deal with responsive projects in WordPress at Peacock Carter.
- Content audit: at a basic level, look through what the client already has (or plans to have) on the website in terms of content, and identify any potentially awkward types: video, large tables of data, etc.
- Wireframes: from here, I start planning where content is going to appear at various breakpoints I’ve identified (there’s a grid in the slides I use for sketching wireframes for each main template I’m planning to design versus each breakpoint I have in mind).
- Mock-ups: from here, I go to visual mock-ups based around the wireframes (which provide a low-fidelity idea of where things go, but not necessarily a to-scale layout). The first three stages are typically not presented to clients, because I present the designs in-browser (mitigating issues with different displays in different browsers, and I will sometimes only create partial visuals and move on to designing in-browser once I have a good idea of where I want to go).
- Implementation: this is generally the first deliverable the client sees: a fully functional, responsive design built as a WordPress theme. I use @toddmotto’s HTML5 blank theme for WordPress as a base (I’ve altered it a little to suit my needs). As per Todd’s theme, I use one stylesheet which contains all of the media queries for the designated breakpoints (highlighted as an example in the slides).
- Testing: obviously, some testing is done before presenting the design to the client, but this step gives me more time to try and break the WordPress theme I’ve built, especially between breakpoints. Consensus during the talk was that respond.js was one of the better ways of dealing with IE without too much hassle, though this isn’t part of my workflow (yet!).
- Minification/production: tying everything off before launch.
Hopefully that’ll help anyone who didn’t make the talk itself (shame on you!). There was also a great talk from Roger at 21 Applications on using WordPress for web application-style projects and for prototyping, and another useful talk on the future of WordPress by our wavy-haired host Steven (@stompweb).
WordPress, the ever-popular open source CMS, spawns hundreds of help guides and books from plugin development to general administration, so I was pretty excited to see Packt’s WordPress Theme Development Beginner’s Guide book (and thanks to Ramon for the tip the book was out!).
WordPress Theme Development: the good
As experienced technical writers, the books flow pretty well, and builds around a fairly believable case study as motivation for building and customising the WordPress theme.
Each task is organised in small numbered steps in Packt’s typical “Beginner’s Guide” format, and the frequent screens and code samples help guide you through things solidly. The book increases in complexity through chapters.
The book strays beyond theming in to basic set up and configuration (such as enabling search engine friendly permalinks), but I think this is likely to be useful for first-time or beginner-level WordPress developers/site owners.
WordPress Theme Development: the not-so-good
As with any technical book, it’s impossible to please everyone, though there were a few areas I felt could have been stronger, including developing WordPress child themes, and more could have been made of what can be done in functions.php (such as controlling the behaviour of the admin bar), but these were perhaps deemed to advanced for the book.
There was also some content I thought was unnecessary “fluff” for the book, such how to validate HTML and CSS as I think readers of the book should be at the stage to know that already, but perhaps I’m presuming too much; again, it’s very hard to judge what content is valid and not for beginners who are at a variety of levels.
How is WordPress Theme Development for a beginner?
I let Matthew, our office manager, read through the book; as someone with a basic grasp of CSS and HTML, and experience using WordPress as an administrator, he seemed like the type of reader that was the target demographic of the book. Here were his initial impressions:
- “Easy to follow in most chapters, with helpful screenshots”
- “Simple guides to WordPress settings I didn’t know about”
- “I feel more confident about creating a theme in WordPress now”
So, how do I feel about this book? Overall, it’s fairly solid for a beginner’s guide if you’re looking to get in to WordPress theme development, and should get you up and developing simple custom WordPress themes in no time at all if you have a basic understanding of HTML, CSS and a little PHP. As with any technical book, it’s likely a useful addition to online documentation and tutorials, but not a sole resource.
I was gifted an ebook by Packt, the publishers, in return for this review.
I recently had to set emails up for a client through 123Reg and had no luck finding 123Reg’s MX records if you wanted to use your own, custom nameservers.
For consistency across our hosting clients, I wanted to point the nameservers for the client’s domain name to our systems, and then alter the MX records for email at our end. There is a guide on 123Reg.co.uk for setting your MX records up using their nameservers, but not any guides if you want to use your own nameservers, so after quite a bit of digging I found them (in this thread on cPanel’s forums).
So, I wrote this quick tip up to prevent the hour of swearing and head-scratching I’ve just endured:
Of course, there are a couple of caveats to using your own nameservers and pointing MX back to 123Reg this way:
- 123Reg could change their MX records and screw your emails up, but I think this is pretty unlikely!
- It’s a good idea to know what you’re doing. 123Reg.co.uk has a (basic) guide to MX records
Sorting out my expenses for Richard Carter Consultancy Ltd which launched last year, I was trying to track down payments to Three UK for mobile in my bank statements and couldn’t find any references to the (so I thought) obvious “THREE”, “THREEUK”, “3UK” or even “3″ as a payee name in my online bank statements.
Three UK’s reference in my bank statements, as it turns out, appears as H3G appended by a customer reference number or similar, which stands for “Hutchison 3G”. In retrospect, fairly obvious when I think about it!
Hopefully this post will help someone wasting 20 minutes of their life looking like I did!
Being a Twitter addict pays off on occasion: Graham had a +1 for a press preview night at the new 360 Champagne Bar in MetroCentre’s Platinum Mall, and not wanting free champagne to go to waste, I was obliged to join him.
I think the cynical side of me (“a champagne bar? In Gateshead?” ) is now a convert: the incoming platinum mall changes – slightly more upmarket shops – and the open air feel to it really work; it’s much more relaxed in feeling than the sometimes raucous Ebony champagne bar in Durham, which can only really be described as a ‘zoo’ on a Saturday night. The staff, I was told, are all based on their ability to bring someone more than pouring champagne: one guy in particular was really quick with card tricks!
Part of my interest (aside from the free champagne, obviously) was in getting the champagne bar’s details on to our student directory websites; as such, 360 Champagne Bar is now online in our Newcastle Uni Students website. Of course, if you want a more sensible review, Graham has duly obliged, with his usual retail twist. (Note to self: link to Graham’s blog).
Photo courtesy of Soult’s Retail View, because I was too lazy to remember to take any whilst I was there.