This post is based on an internal workshop I delivered at a previous job, where we used a modified version of gitflow. This post will contain faint reflections of that strategy, and although I’d recommend reading up on gitflow it’s not necessary.
Usually when I build a navigation it is at the end of the source and a skiplink appears at the top of small viewports linking to it. I then enhance it using CSS and JavaScript so that most devices and browsers get something nicer—an off-canvas interaction perhaps.
Advanced Custom Fields is an amazing (and free) WordPress plugin that turns it into a proper CMS and gives developers fine-grained control over how data entered by content administrators is handled and displayed. I love it.
This is a guest post by Toby Osbourn. Toby is one of the most talented and productive web developers I know and I was privileged to work with and learn from him for 6 months. He tweets a lot of interesting, thought-provoking and funny stuff too.
There’s a sentiment among web developers that seems to me to be more prevalent lately, a bit of a reaction against modern tools like CSS preprocessors, task runners and package managers. It’s pretty well summed up by two tweets:
On Thursday 9th October at 6.30pm I’ll be giving a talk on the new responsive images standards. It’s a free talk and will take place at Rumble Labs in Belfast, just round the corner from St. Anne’s Cathedral.
The <img> tag all started with this message and has been with us since HTML 2.0. In that time it hasn’t changed much at all, just put a path to an image in the src attribute and you have an image on the screen.