I’ve decided it’s time to write a new series of posts all about how websites work: some of the theory behind what developers do. Hopefully this will help you understand some of the terms developers might use when talking to you, or – if you’re building your own site without a developer – it might […]

At last! We’ve completed work on the new version of this site. There’s a new portfolio, all new HTML5/CSS3 design, and all sorts of whizzy things under the hood to improve performance and to make it easier to roll out some improvements for clients over the coming months. Hurrah!

There’s been a lot of talk in the press recently – for very sad and very serious reasons – about website moderation, anonymity, and so on. One of the main things we’re asked about – usually after the fact, when it needs to be considered up front – is how to control this kind of thing. What do you do about spam, swearing, and – as has been in the news so much – threats, insults and antisocial networking?

I got asked the other day how I did something. This is rare. Normally people are wowed by the design and take the tech for granted, which is great: if it runs smoothly enough to take it for granted I’ve done my job well.

Bugs. They happen on every site. It’s impossible to avoid them. But with the right reporting, you can get them fixed quickly and cleanly, and your developer will thank you for it.