Skip to content

Case study 03 · Prensa Ibérica · End-to-end

The brief was simple: reproduce the map. The real problem wasn’t.

I replaced a difficult-to-maintain static asset with a responsive, data-driven map whose content could be updated from structured data.

Role
Product Design + Front-End
System
42DS
Data
Google Sheets → CSV
Build
Leaflet · IGN · JavaScript

REAL PROJECT EVIDENCE / CODE

The map itself is the evidence.

This standalone view keeps the original Leaflet implementation, IGN tiles, real marker data, publication-specific icons, popups and Spain-wide bounds logic. I removed the surrounding newspaper chrome so the development is easier to inspect.

Crónicas Prensa Ibérica / Leaflet + IGN
Interactive development
Original locations + custom publication markersPan · zoom · popup

The brief

The requested interface was not the real problem.

The previous solution was based on static images. It was hard to maintain and poorly adapted to mobile. The initial request was essentially to reproduce it; I proposed changing the underlying solution instead.

Constraint

Use an interactive map without adding a paid mapping platform.

Google Maps or similar paid services were not desirable, so the solution had to rely on open technologies. That constraint led to a Leaflet-based implementation using IGN mapping resources.

The hidden work

Before the map, there had to be reliable data.

The information was fragmented across different editorial teams. I gathered locations, media types, relationships and other useful fields, then structured maintenance around Google Sheets and CSV rather than around image editing.

Product decision

Make maintenance part of the design.

Editorial maintenance was initially expected to sit with the newsrooms, but the more efficient data workflow made it possible for Product to assume that work when resources were limited.

AI-assisted build

Use AI to extend execution capability, not to avoid product decisions.

JavaScript was not my original specialization. AI support helped me implement a substantially more complex interactive experience while I remained responsible for the product structure, data model, behaviour and integration with 42DS.