Hearst Magazines: Custom Feeds Redesign
A modular building-block system and drag-and-drop editor that let editorial teams design curated layouts without engineering
Problem
What Hearst’s magazines were missing wasn’t a homepage redesign, it was a system: a layer that could take editorial judgment and turn it into a page, brand by brand, without an engineer in the loop every time. Without it, every magazine ran the same rigid pattern: a header, then a reverse-chronological stream. The brands looked like blogs, editors had no way to curate or differentiate their front pages, and any layout change required engineering intervention.
Approach
Custom Feeds was the answer: instead of hardcoding a homepage, editors composed one from a fixed vocabulary of building blocks, each configurable and stylable without touching code. A Big Story block on Cosmopolitan and the same Big Story block on Esquire were the same underlying definition, rendered through each brand’s own theme; the block was the constant, the theme was what changed. Editors worked entirely through a drag-and-drop editor: a tool built for people who write for a living, not people who code.
Team
Theresa Mershon (Creative Director)
Artem Artemov (Product Design UI/UX Lead)
Ryan Ilano (Custom Feeds Design Lead from H2 2019)
Namie Genkin (Senior Product Designer)
Tracey O’Connor (Senior Product Designer)
Amy Ham Liu (Associate Product Designer)
Daisy Sun (Senior Product Designer)
Responsibilities
- Styling and front-end development: SCSS/CSS committed to the codebase
- Design systems and product design
- Art direction and visual approval
- Visual QA on device, across all layouts and all devices
Achievement
As Design Lead from H2 2019, drove an accelerated launch process that brought roughly half of Hearst’s digital brands onto Custom Feeds. The push was finished before Thanksgiving 2019.
Building blocks
We designed a system of building blocks that could be used to create a wide variety of layouts and styles. These blocks included: Big Story, Big Story with Feed, 4-Across, and 3-Column. Each block had multiple styling options that could be applied to create unique looks for each magazine. The building blocks were designed to be flexible and adaptable, allowing editors to create custom layouts that fit their content and brand.
The building blocks were optimized for performance and accessibility, ensuring that they would work well on all devices and screen sizes. They also had a consistent design language that reflected the overall aesthetic of the magazines, while still allowing for customization and creativity.
Advertisements could be integrated into the custom feeds, each block had layouts that would accomodate standard ad placements programatically. This allowed for a more engaging and less intrusive advertising experience for users, allowing advertisers to reach their target audience while still providing a seamless and enjoyable user experience.
Custom Feed Editor
The editors could create and manage their custom feeds through a graphical editor that allowed them to select and style the building blocks, curate content, and preview their layouts in real-time. The editor was designed to be intuitive and user-friendly, allowing editors to quickly create and publish their custom feeds without needing technical expertise.
The 4-Across Block, Brand by Brand
What this became
The token cascade this system themes against is not Custom Feeds’ own. It belongs to the mediaOS platform, which had already established the three tiers a block layout inherits from, and Custom Feeds is what happens when an editor is handed control of the layer above them.
The block library and that cascade did not stay on the homepage. The same architecture is what the Apple News integration mapped into Apple News Format, which is why onboarding a magazine there was a token configuration exercise rather than a rebuild. That page pairs each screenshot with the same story on the brand’s own site, so you can open one article on both surfaces and see the cascade doing its job in two places at once.
It is also what the accessibility program later audited against. A shared component library is the thing that makes an accessibility pass tractable at 85 sites: fix the block, not the 85 pages.
Scope of ownership
Art direction, visual design, and production SCSS/CSS committed directly to the codebase: design and front-end, no handoff. Owned design systems, art direction and visual approval, and on-device QA; as Design Lead, led a team of four designers through theming, front-end, QA, and brand launches.
Gallery