Travel articles, designing editorial templates and a content ecosystem
Role
Senior Designer
Platform
Web
Duration
3 months
Type
0-1 Feature
Background
In 2024, Chase Travel launched as its own brand and editorial voice. To support this I led the design of article templates that enabled the editorial team to publish on both public (chase.com/travel) and secure travel portals.
Outcome
We launched travel articles to 100% of Chase Travel customers in August 2024, and saw +124% views growth from March 2024 to September 2024 (127K → 285K).
Team
Product manager | Engineering lead | Editorial lead | Team of 3+ engineers
Partnership with chase.com product, design, and engineering team.
So why articles?
By giving Chase Travel the ability to publish editorial content on both public and secure platforms, we could establish brand voice, reach new audiences via SEO, and guide travelers within their booking journey. Previously, the editorial team could only publish one type of article in our secure platform, and one-off articles on our public platform that didn't live in a page archive.
My first challenge: getting the ball rolling
When I joined, the project was stuck in a discovery for a year. My goal was to get designs onto the development roadmap and launched without the luxury of starting from scratch.
Key constraints:
A limited component library from a different design system
Previously agreed-upon design components could not be re-explored
Feasibility gaps across two publishing platforms
My approach:
Audited prior explorations, editorial requirements, and component limitations
Worked with engineering to define what was possible
Broke down the MVP into a multi-release roadmap to launch iteratively
Editorial Flow - Customer
We designed for authors, not just customers
The authors needed to publish to multiple platforms. We aligned designs around the most inflexible system (public) to speed up dev work.
reusable components
For scalability, we built reusable components for authors to compile their articles with. The designs incorporated existing design system patterns and guidelines.
Editorial components for templates
The Solution: Content modules that build into full-page layouts
These layouts were a Travel Guides home page, Category pages, and Featured articles pages. The editorial team could manage the content dynamically through Adobe Experience Manager without having to consult product development teams, and content could be published to both secure and public platforms.
Travel Guides home and Category page article sample layouts
Hotel spotlight article and Hotel Guides article sample layouts
We prioritized public releases first to capitalize on SEO, and built a toggle mechanism to control visibility between platforms for various articles. We launched basic articles first, then the home and category pages, then special components within articles.
Public sample layouts
results
Launched 12 new reusable components for editorial pages
Enabled Chase Travel editors to publish across both platforms
Decreased time to publish by 50%
Increased views growth +124% (127K → 285K)
Metric from March 2024 (before full launch) to September 2024 (after full launch)
Projected 100+ articles published with 5M page views in 2025
Next steps
We plan to incorporate articles into the native platform, build a more streamlined path from articles into search and product details, better distinguish article content in the secure portal, and iterate article type based on data.
