Applying an Editorial visual direction
You are being asked to apply an Editorial visual direction to a web interface. This document gives you framing and recommendations for that direction. It does not tell you what page, product, or feature to build — apply the guidance below to whatever interface you are already working on, at whatever scope that work requires.
What “Editorial” means here
Editorial design borrows the conventions of print publications — magazines, newspapers, and printed journals — and applies them to a screen. The defining move is treating typography and layout as the primary structuring devices, the way a print art director would, rather than treating them as a neutral container for content. Text is set on a considered grid, imagery is integrated as part of the story rather than as generic decoration, and the whole composition should feel authored: like someone made deliberate editorial choices about what is emphasised, what is quiet, and how the reader’s eye should move.
“Authored” is the operative word, and it is more literal than it sounds. A published article carries furniture — a kicker above the headline, a deck summarising it below, a byline naming who wrote it, captions crediting the images. Those parts are most of what separates a page that reads as written and edited from one that reads as a template someone filled. Well-set text without them still feels assembled.
The style is quiet by discipline. The craft’s own formulation is that typography should disappear so the words can do their job. That is what separates Editorial from directions where type is the spectacle: if a reader finishes and remembers the typeface, it was probably Art Deco or Maximalist, not this. It is also what separates it from Swiss, its closest neighbour — Swiss uses a single neutral sans where you pair two contrasting families, shows off its grid where you merely use one, and is deliberately anonymous where your page is signed.
Recommendations
- Pair a distinctive display or serif typeface for headlines with a clean, functional sans-serif (or a second serif with a clearly different character) for body text and interface labels. The contrast between the two should be legible at a glance.
- Control line length, and match it to the column count. A single column of body text reads best between 45 and 75 characters per line, with 66 as the target — roughly a 33em column. If you set multiple columns, tighten each to 40–50 characters: a narrow column running at a wide measure is harder to read than either extreme alone.
- Build a real column grid for long-form content, and give it a vertical counterpart: derive your spacing from the body line-height so type aligns across columns and down the page, rather than picking margins by eye.
- Include the article furniture. A kicker or a deck, and a byline. Set each distinctly from both the headline and the body — a deck is conventionally one size down from the headline, often italic or lighter; a byline sits below the headline or deck. This is the cheapest, highest-leverage thing on this list.
- Treat images as content: give them intentional placement (full-bleed, art-directed crops, or a defined position within the grid) and pair them with a caption or credit line set in a visually distinct style from body text.
- Break long passages with subheads. They give the reader a way to navigate and to re-enter after looking away.
- Use thin rules and generous, purposeful spacing to separate sections — a masthead from an article, one article from another — the way a printed page uses margins and rules rather than boxes.
- Keep colour restrained: let typography, imagery, and layout carry the visual interest, and use no more than one accent colour for links, emphasis, or interactive states.
- Vary pacing deliberately. A large pull quote, a wide image, or a section break can serve the same purpose a print spread uses to give the reader’s eye a place to rest.
Avoid
- Sans-only or serif-only pairings that erase the contrast between headline and body voice.
- A page with no kicker, deck, or byline. However well the text is set, it will read as assembled rather than authored.
- Multi-column layouts that keep a single-column measure, running each column too long for its width.
- Unbroken walls of text with no typographic pacing, section breaks, subheads, or pull quotes.
- Treating images as generic background decoration rather than captioned, art-directed content.
- More than one accent colour competing with the reading experience.
- Styling captions identically to body text, which erases the distinction between narrative copy and supporting material.
- Display typography that asks to be looked at rather than read through.
- Showing off the grid as a visible structural device — use it, do not exhibit it.
- Vertical spacing picked by eye rather than derived from the body line-height.
A working order
Editorial layout is a process before it is a result, and the order matters more than any single decision. This is the sequence a working editorial designer follows.
- Gather every asset first — images, logo, the real text — into one file before making a single layout decision. Composition on placeholder content is composition you will redo.
- Read the content and digest it. Do not pour paragraphs into a fixed column. Find the one phrase or figure that deserves to become a hero-scale typographic element, and pull it out of the sentence it is buried in.
- State the page’s goal — the one action it should drive — before you place anything. That goal decides what gets visual priority.
- Collect references from more than one medium. A print poster among the web references is what stops the result from resembling any single source.
- Restrict the toolkit to five things: one or two type families, one or two accent colours plus neutrals, one grid, images in bounded containers, and white space. Nothing else.
- Declare a closed spacing scale and a grid, then never deviate. A working scale is 10 / 20 / 40 / 80 / 160px, with a 12-column grid and fixed 40px side margins. Every gap, margin, and padding is a member of that scale — no arbitrary values.
- Check both axes. Each new element is aligned against its neighbours vertically and horizontally, not just against the grid. Anything off by a pixel gets corrected.
- Add depth with placement, not effects. One image behind the text, one in front, and a locked palette — rather than a shadow.
- Place compound blocks as single units. A paragraph plus its CTA moves together, positioned by one of three strategies: a fixed internal proportion, alignment to another element, or a fixed distance from a structural element such as the nav.
- Cut before you accommodate. If a composition is overloaded, remove elements rather than shrink everything to fit.
Then, and only then, translate downward to mobile — never design mobile first and scale up, because it is far easier to simplify a rich layout than to enrich a sparse one.
- Collapse navigation into a menu control.
- Invert orientation: what runs horizontally on desktop runs vertically on mobile.
- Shrink headlines, but hold body text at a 16px floor, and let CTAs stay the same size or grow rather than shrink.
- Rebuild the grid with at least six columns, specifically so a 2/3–1/3 asymmetry survives. Four columns collapse every block to the same edge and the composition goes symmetrical without you deciding it.
How to check your own work
Before considering the result finished, look at it and ask:
- Do headlines and body text clearly read as two different typographic voices?
- If I measure a line of body text, does it fall roughly within a comfortable reading length? And if I set columns, did I tighten the measure to suit them, or leave it at the single-column width?
- Can I point at a kicker or deck, and at a byline? If not, the page is not yet editorial, whatever else is right about it.
- Does every image have a caption or credit treated as distinct from body copy?
- Do the vertical gaps resolve to multiples of the body line-height, or did I pick them by eye?
- Does the page have a clear rhythm — passages of dense reading broken up by rules, spacing, images, subheads, or pull quotes — rather than one undifferentiated block of content?