I spend a lot of my time creating digital artefacts. Sometimes it’s nice to spend some time working with my hands to create something physical and tangible, and what better project than making one of the tools I use every day quieter and more pleasing to the eye?
It’s been a while since I’ve written in this blog. For the longest time this site has just been a holding page, because I didn’t want to do anything on the redesign until it was perfect. The thing is though, it’s never going to be perfect, for any number of reasons: I’m too much of a perfectionist, I’ve had another great idea which I really should incorporate, I was busy redesigning my billing/project management software instead. I’d let perfect become the enemy of good, or at least of good enough.
One of the first things people find when they’re looking around for information on any subject are forums. Forums are a great resource because they collect a community of knowledgeable people who actively help each other out, in addition to providing a huge searchable archive of information for people who are just looking to find the solution to one problem.
I’ve recently been involved in a project to create a forum for people who are interested in web design and development and all the disciplines (SEO, copywriting, content strategy) that go along with it, and it’s recently launched – without further ado, I present to you: The Web Design Forum.
Responsible developers don’t work live. Working on a local copy of a site and only pushing it live when it’s ready is one of those sensible development practices that everyone should follow, but it can introduce some hitches when working with WordPress. Luckily, wp-config.php is the one core file that’s never overwritten by a WordPress update, so it’s safe to rewrite it to be a bit more useful. The wp-config.php file is generated from wp-config-sample.php by the WordPress install script and anyone who’s worked with WordPress will be familiar with the contents so I won’t list them in full, but you can view the default contents of wp-config-sample.php in the WordPress SVN repository.
I moved my office this week. I didn’t move far (20 miles) and only had one van-load to move, so I scoured the local listings for a man & van service. I don’t know if you’ve ever looked for something similar on Gumtree or the like, but I’ll save you the trouble: an endless list of (often badly-written) ads ending with a first name and a mobile phone number.
The advantages of loading scripts from Google’s CDN are fairly obvious – for a common script such as jQuery, we’re on to a better-than-even chance that the user will already have the script in their browser’s cache from other sites, reducing the total download weight of your site. Even if they don’t, the file will be downloaded from their nearest Google CDN server, which will still be faster than downloading it from your site because it will be downloading in parallel from a different host.
In Part 1 of this guide, we covered how to set up a portable development environment with the basic set of software tools (a web stack, an IDE and a good text editor). Continuing on, we’ll create a project and make it portable. The instructions given are specific to Netbeans because that’s what we set up in Part 1, but can be easily adapted to your IDE of choice. Once again, you’ll need to follow the first part of this guide on both desktop and laptop.
Yarrr this be talk like a pirate day. while ( timbers.length > 0 && owner === ‘me’ ) { shiver() }
– Chris Heilmann on Twitter
Inspired by Elliot Jay Stocks’ recent posts on his iMac plus Air setup, I thought I’d document how to set up a seamless development environment between desktop and laptop. If you intend to set up a similar environment, you’ll need to perform these steps identically on both machines. Part 2 of this series will deal with the basics of setting up a portable project, and Part 3 will cover setting up advanced tools and source control.
Aral Balkan posted the following snippet on Twitter just now:
<span>u</span><span class="hideIf320">ser e</span><span class="capIf320">x</span><span class="hideIf320">perience</span> |
followed by the explanation: