The Web Project Guide: Implement the Design | Implement the Back-End Functionality

I began my life as a content strategist by, weirdly enough, handling all site QA for Blend. It was an invaluable experience: I gained confidence in not just what a site should include, but how it is actually implemented, which allows me to better understand the technical considerations that come into every content decision.

This month, Deane provides a look at the code side of things: what happens when we’ve helped shape strategic content and UX design and determined the who and the what. This month’s chapters provide a bit of context to the craft of coding, and help understand why certain things have to be the way they are. They demystify the development process, and for that I think they’re really well done.

CHAPTER 19: Implement the Design
To take visual design and turn it into a fully-functional (and responsive) web design is a mix of programming, math, and human interaction.

CHAPTER 20: Implement the Back-End Functionality
This is a deceptively simple step for what amounts to actually building the inner workings of the website. You need to examine the site functionality, break it into manageable iterations, and plan their execution.

There are only four chapters remaining. The next two focus on migration and launch, while the last two will focus on site governance and ongoing site maintenance. And then … it’s complete? (Not really, though. We’ll certainly need to do some major book-wide editing.)

As always, to keep up to date with chapter launches, sign up for our emails.