Design that starts with your content, not a template

A great deal of web design begins with a layout and then squeezes the business into it. That is why so many sites have a hero image nobody needed and three columns of features nobody read. We work the other way around: what does a visitor want here, what do you need them to do, and what does the content actually consist of once someone writes it.

That matters most on the pages that carry real weight. A services page with forty children needs a different structure from a landing page with one call to action. A site with a busy editorial calendar needs templates its authors can live with for years. Designing for the real content is unglamorous and it is most of the job.

Platforms we design for

We design for the platform the site will actually run on, because the constraints differ and pretending otherwise creates work later. WordPress gives editors the most freedom and needs designs that survive that freedom. Drupal rewards structured content and complex permissions, and its design should reflect that structure rather than fight it. eCommerce is judged on whether it sells, so its design decisions are conversion decisions.

Every design is responsive as a matter of course. Not a separate mobile site, not a desktop layout that collapses awkwardly, but one design that holds up from a small phone to a wide monitor.

What you get

Designs delivered as working, buildable specifications rather than flat pictures: states, breakpoints, and the awkward cases like long headlines, missing images and empty lists. If we are building the site too, that handover is internal and nothing is lost. If your own developers are building it, they get files they can work from without a translation phase.

Pick the platform below to see the specifics, or get a quote if you would rather just describe the project.