Product Design Case Study

Redesigning Otaghak's magazine, from scratch

A full redesign of Otaghak's blog and destination guides to bring them in line with the platform's visual identity.

Role
Product Designer
Scope
Full redesign
Duration
2โ€“4 weeks
Status
In development
Desktop view of Otaghak's redesigned magazine
Mobile view of Otaghak's redesigned magazine

Why it needed a redesign

01

Otaghak's magazine โ€” the blog and destination guides โ€” had grown page by page over time and drifted from the rest of the product. Typography, spacing, and card patterns no longer matched the booking experience, so moving from a stay listing to an article felt like leaving the platform.

Core design challenge

Rebuild the magazine and destination guides on Otaghak's actual design system โ€” same type, same components, same visual language as the booking product.

Process

02
01
Research & benchmarking
Reviewed how other travel platforms structure destination and blog content, and audited exactly where Otaghak's magazine had drifted from its own design system.
02
Wireframes & information architecture
Restructured how destination guides, articles, and booking widgets relate to each other on the page, instead of treating content as a separate silo.
03
Full UI design
Rebuilt every screen with Otaghak's existing components โ€” typography, cards, buttons, color โ€” so the magazine reads as part of the same product.

The result

03
otaghak.com/magazine
Full desktop page of Otaghak's redesigned magazine
Scroll to see the full page

Quick facts up front

Active listings, attractions, restaurants, and guides summarized in a stat strip right under the hero photo.

Content tied to booking

Articles, a trip planner, and a booking widget live on the same page instead of separate destinations.

Reused components throughout

Cards, buttons, and filters match the same patterns already used across Otaghak's booking flows.

Full mobile page of Otaghak's redesigned magazine

Mobile keeps the same stat strip, quick links, and booking card as desktop, restructured into a single scrollable column.

Current status

04

Not yet launched โ€” currently in development.

1

Core pages designed

The destination guide template and article layout are finalized.

2

Component-driven

Built entirely from Otaghak's existing design system โ€” no new components required.

3

In development

Frontend implementation is currently underway.

Takeaways

05
Consistency as the brief
When the goal is matching an existing identity, most of the work is auditing drift, not inventing something new.
Design system as a shortcut
Rebuilding entirely from existing components is what made a full redesign possible in under a month.
Content needs commerce nearby
Placing booking widgets inside content pages, not just at the end, keeps browsing and booking connected.