Literary Route Web

Literary Route [Ruta Literaria], a WordPress editorial portal redesigned for editorial independence. 4,500 unique visitors and 15,000 page views in the first two months post-launch.

Type

Client project

Platform

WordPress website

Audience

· Readers
· Writers
· Literary community

Scope

· Homepage
· Interior pages
· Category pages
· Posts

My role

Web Designer

Type

Client project

Audience

· Readers
· Writers
· Literary community

My role

Web Designer

Platform

WordPress website

Scope

· Homepage
· Interior pages
· Category pages
· Posts

Type

Client project

Scope

· Homepage
· Interior pages
· Category pages
· Posts

Platform

WordPress website

My role

Web Designer

Audience

· Readers
· Writers
· Literary community

Literary Route Website

An editorial portal for reviews and collaborative writing.

LR-WEB-2023

THE GOAL

Help an independent literary portal scale its content without losing editorial clarity or visual identity.

Redesign the portal to increase content discoverability and support audience growth — giving new visitors a clear entry point and returning readers faster access to what they need.

Success signals

More content explored per visit, lower drop-off on category pages, and a growing base of returning readers engaging across multiple sections.

SCOPE

I led the redesign end to end: information architecture, visual system, page templates, and full implementation in WordPress.


The project involved ongoing collaboration with the editorial team to ensure the CMS remained manageable for non-technical contributors. The scope covered the live site — not a prototype.

THE PROBLEM

The original site had outgrown its structure. A rigid single-column layout and no content hierarchy made it increasingly difficult for readers to discover what the portal had to offer.

User sentiment

No clear path into the archive beyond the homepage.

Content categories were hard to navigate and compare.

The site didn't reflect the editorial ambition of the team behind it.

RESEARCH APPROACH

Content and navigation decisions were informed by direct collaboration with the editorial team, ongoing review of how content was being added and consumed, and observation of where the existing structure created friction for both contributors and readers.

Methods

Editorial team feedback.

Content audit of existing posts and categories.

Direct observation of contributor workflow.

Competitive review of editorial portals including Ground News, Indie Hoy, and Cambio Colombia.

Perspective

Decisions were informed by observing how the structure created friction across two site versions.

Design Criteria

Surface content across multiple categories without overwhelming the reader.

Reflect the way the editorial team organises and publishes content.

Support contributors who are writers, not developers.

Build credibility and encourage return visits.

Scale with content volume without increasing navigation complexity.

Key Findings:

Content was hard to discover beyond the homepage, readers had no clear path into the archive.

The editorial team needed a structure they could maintain independently without design support.

Category-based organisation reflected how both contributors and readers naturally think about the content.

A consistent visual identity was missing, the site didn't feel like a defined editorial brand.

The original layout couldn't accommodate the growing volume and variety of content types.

Pain-Point Audit

A screen-by-screen review of the original site identified structural and visual friction points across four key page types, homepage, author pages, category pages, and individual posts.

Affinity Map

Research signals grouped into four recurring themes, the patterns that directly shaped the redesign decisions.

SYNTHESIS OUTPUTS

User Types

Two distinct users shaped every structural and visual decision in the redesign.

The reader

About Occasional visitor who arrives through social media or search and reads one article at a time.

Occasional visitor arriving through social media or search.

Reads one article at a time, rarely explores further

Needs clear category navigation, content suggestions after finishing an article, and a reason to return.

The Contributor

About A writer or editor who publishes regularly, not a developer, and not dependent on technical support.

A writer or editor publishing regularly, not a developer

Needs a CMS they can operate independently, an author profile linked to their work, and a consistent page layout to publish into without starting from scratch.

Information Architecture

The site is organised around five content types and a clear primary navigation, designed to reflect how the editorial team publishes and how readers naturally browse by category or author.

Structure principle: readers enter through any category and can navigate laterally across the site without returning to the homepage.

DESIGN PROCESS

The redesign was driven by structure before aesthetics, understanding how content was organised and consumed before making any visual decisions.

Key Design Decisions

Five structural and visual decisions shaped the redesign, each directly tied to a problem identified in the audit.

Together, these decisions transformed a rigid single-column site into a structured editorial platform, one the team can maintain and grow independently.

THE SOLUTION

The redesign replaced a rigid single-column layout with a structured editorial system — organised around content types, built for independent use, and designed to grow with the portal.

User Flow

Primary Flow

The primary reader journey — from entry to content discovery, navigation across page types, and the decision points that keep users engaged or take them off-site.

Core logic

Every page follows the same pattern: primary content on the left, contextual discovery on the right. Readers always know where they are and what to read next.

These four page types form the complete editorial system — each one solving a specific problem identified in the audit, and each one consistent enough to feel like a single, coherent product.

UI DESIGN

The visual system was built to give Ruta Literaria a consistent, recognisable identity — one that could be maintained by a non-technical team without breaking down over time.

Design tokens

A structured set of visual decisions applied consistently across every page type — colours mapped to content categories, an 8-point spacing grid, breakpoints for mobile and desktop, and a defined logotype with button states.

Typography

Open Sans was chosen as the single typeface for the entire system — used across headlines and body text in nine weight and size combinations. The decision prioritised readability for long-form literary content while maintaining a clean, editorial character across all screen sizes.

These decisions form a lightweight but complete design system — one that doesn't require design knowledge to use. The tokens define the boundaries, the typography sets the tone.

OUTCOME

The redesigned portal launched mid-2023. Within the first two months: 4,500 unique visitors and 15,000 page views, documented in the team's public launch announcement.


By week five, the editorial team was publishing independently across all content types — no design support required. The site remains active today.

Before / After Design Comparison

Four page types. One consistent redesign decision: structure, sidebar, and editorial identity applied across the entire site.

Learnings and reflections

Working on a live site means structure has to be right before build. There's no room for mid-project pivots when an active team depends on the system daily.


The biggest gap: no Analytics baseline from the original site. If I were starting this project today, I'd connect tracking before touching a single template.

Literary Route remains one of the most complete web projects in my portfolio, a live site, a real client, and a structure that's still being used today.

THANKS FOR READING

THANKS FOR READING

Literary Route Website

An editorial portal for reviews,
interviews and collaborative writing.

LR-WEB-2023