Adobe Experience manager

Get new posts delivered straight to your inbox.

Subscriber count: 4,300

Stitcher radio

Search results

Adobe Experience manager

Design good websites by following principles of technical writing style

Mar 1, 2007 • general

Designing good websites involves following the same principles of technical writing — be invisible in style. In this Edgework podcast, Joshua Porter explains that good web design isamazon good web design often invisible. Users shouldn't be concentrating on the design. Like Amazon, you focus on the content. You focus on the fact that it works.

I strive for the same in my technical writing. I want the user to focus on the content, not my literary style. I remember reading Armies of the Night by Norman Mailer and being awestruck by the literary flow. But while I was impressed, I preferred books that gripped me with the story rather than the style.

Technical writing doesn't call attention to itself for its style. Its style is invisible. Its purpose is to teach the user how to do something. You don't read to be impressed by literary acrobatics.

I hadn't thought how the same invisibility principle might apply to good web design. But it does. Sure you want to make a good impression, and graphic design counts. But the most popular websites are popular because they simply work. Google, Craigslist, Flickr, Digg, Amazon — you don't dwell on the visual design of these sites.

Often the simpler a site, the better. Porter even quotes Alexander Pope about how "he did not have time to make his letter shorter." In other words, shorter, simpler, invisible design is often harder than long, complicated, flashy designs.

follow us in feedly


Get new posts delivered straight to your inbox.

Subscriber count: 4,300

About Tom Johnson

Tom Johnson

I'm a technical writer based in the California San Francisco Bay area. In this blog, I write about topics related to technical communication — Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, academics, and more. I'm interested in simplifying complexity, API documentation, visual communication, information architecture and findability, and more. If you're a technical writer of any kind (progressional, transitioning, student), be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.