Designing a news site around its stories

At 6 a.m. on January 8, I stood in the Times newsroom on Eighth Avenue as the new article pages went live. I had spent the better part of three years helping to build toward that morning. Seeing the work reach readers made me proud of what we had built together, and of the people who had stayed with it through the difficult parts.

The previous major redesign dated to April 2006. Since then, reading on phones and tablets had become a much larger part of the job we needed the site to do. We were changing both the page a reader saw and the machinery that would let us keep improving it.

The new platform initially serves newly published articles and interactives. The homepage and section fronts received lighter visual changes. Product design lead Renda Morton described the story page as the starting point for the larger redesign.1 That choice put the journalism itself at the center of the work.

A calmer page that can respond to the reader

The article pages give the text and photography more room. Larger body type, a clearer reading column and less competition around the story make the page feel calmer to me. Navigation, related coverage and comments still need to be within reach. They should help someone stay with the journalism instead of continually pulling attention away from it.

A reader can scroll through a story on one page and move sideways to another story.2 Opening the comments brings the conversation alongside the article. The story and its photographs must still work in the space beside it. A picture of the page with the comments closed cannot tell us whether that interaction works well.

Working with the advertising technology team means considering positions and formats alongside the reader's experience. Advertisers need a useful presence, and journalism needs the revenue they help provide. I want placements that serve that business without making the story unpleasant to read. Those decisions belong in the design conversation from the beginning.

The story changes the layout

A brief news report and a feature led by a large photograph should have room to be different. Giving both the same narrow opening for an image would make the software easier to describe, at the expense of the photograph. Letting every story invent its own navigation would create a different problem for the reader.

The new article framework makes layout decisions using the type, orientation and size of the leading media, as well as the available screen space and advertising format. Reed Emmons, the development lead, explains that these combinations produce more than a hundred variations.3 The framework serves desktop and tablet readers, while the mobile site has its own implementation.4

In the builders' interview with OpenNews, Eitan Konigsburg describes making page-level information available to individual features so they can respond when, for example, the comments panel opens. Allen Tan explains the move from a fixed template to configurations that accommodate the content and the reader's choices.1

A comments feature can have its own code and still need to tell its neighbors what it is doing. Features that measure and rearrange the page independently can make conflicting decisions about the same space. Adding another one then means checking which assumptions it disturbs.

I'd rather give those features a shared account of the page's condition and make their responsibilities explicit. The comments feature should not need to understand the internals of a photograph viewer to coexist with it. Nor should the photograph viewer have to guess whether space has become available. Sharing that information gives the designer a way to describe how the page should behave as a whole.

Where the common parts belong

Emmons describes the earlier publishing system storing an article's HTML when a producer published it. Scripts and styles could change afterward, leaving the front-end team to support the older page structures. The new rendering system, the software that assembles the page a reader receives, can produce different layouts on demand.3

Where a page is assembled, and which pieces are shared, affects how much work the next design change will require. A redesign budget has to account for maintaining the experience across years of publishing. Improving a page should not require every application that supplies its content to be replaced.

In his January 15 account, Scott Taylor explains how the Times blogs now fit into the new platform while continuing to use WordPress. WordPress supplies the blog content; the surrounding application supplies the page structure, including common elements such as the masthead and navigation. A blog can replace the parts that need to differ and use the shared versions of the rest.5

The people working on a blog should not have to reproduce the newspaper's navigation to publish a distinctive blog. Sharing the navigation should leave them room to decide how to present their own content. I care about that freedom because the next useful form of journalism may ask something of the page that we have not yet designed.

What it took to ship

Ian Adelman and the design team, our newsroom and product partners, engineers, operations, advertising, audience staff and editors all carried parts of this effort. Several of the hardest decisions sat between teams. A layout choice could affect an advertising format; a new interaction could change assumptions in another feature. Working through those seams required people to understand more than the component they owned.

The January 8 article launch and the January 15 blogs integration were separate steps. A lighter change to a section front was different from rebuilding it. A redesign gives us a chance to ask which older features still earn their place, and which deserve to be reconsidered before we carry them forward.

Subscriber access, partner feeds and durable story URLs remain obligations through that work. A page redesign must respect the reader who has already paid, the partner relying on a feed and the person following a link to an old story. Keeping journalism addressable is part of publishing it.

For a redesign review, I want to see dissimilar real stories early, including the awkward ones. Give a long photograph-led feature the space it needs, then try the same surrounding design with a brief report. Open the comments. Look at the parts of the page that did not receive the click. Moving from a static design to a working page should reveal which decisions belong to the story and which require cooperation across the page.

Journalism beyond this launch

The readers whose notes I have read have been mostly kind. Some dislike the changes, and I read those notes too. Much of what I have heard is that the site feels calmer. That is satisfying because giving the story room to hold a reader's attention was what we wanted.

I want a large news site to feel comfortable on a subway phone as well as a newsroom monitor. Speed matters when the connection is weak. Reporters filing over bad hotel Wi-Fi need our publishing tools to work too. Video, audio, interactive graphics and long narratives should be able to find their own forms within a recognizable newspaper.

We are building for journalism that will still matter in ten years, on platforms that may look very different. I want the work we have done to give future teams room to meet those readers. We should be able to give an unusual story an unusual presentation while making it unmistakably part of the Times. I look forward to seeing what our journalists do with that freedom.

Footnotes

  1. Erin Kissane, Eitan Konigsburg, Renda Morton and Allen Tan, Behind the Scenes on the NYT Redesign, OpenNews Source, January 8, 2014. ↩ ↩2

  2. The New York Times, redesign guide announcing the January 8, 2014 launch. ↩

  3. Reed Emmons, The Technology Behind the NYTimes.com Redesign, Times Open, January 8, 2014. ↩ ↩2

  4. OpenNews Source, NYT Redesigns for Mobile, May 7, 2013. ↩

  5. Scott Taylor, Rethinking Blogs at The New York Times, January 15, 2014. ↩