MediaPot - Collaborative News Production Platform

The Challenge

Professional desks and citizen groups rarely share tooling. Good on-the-ground material often dies in email threads because there's no safe path to verify it and fold it into a story.

MediaPot was meant to close that gap without lowering editorial standards.

The Solution

The product connects both sides in one interface. Multimedia checks (video and audio analysis from partner services) sit next to verification steps before anything goes to publish. The UI has to stay usable while backends disagree on payload shape.

Photo by John on Unsplash

Technical Architecture

Angular on the front. Partner capabilities arrive over REST from several microservices. I built an adapter layer so the UI sees normalized models even when upstream APIs use different field names or error shapes. That layer saved us from rewriting screens every time a partner tweaked their contract.

My Role & Contributions

Tech lead and hands-on front-end dev. I owned service integration across partners and built the core application shell. A lot of the job was translation: aligning technical contacts on each side so data actually flowed end to end.

Photo by Boitumelo on Unsplash

Challenges & Learnings

Multi-partner projects punish vague interfaces. We learned to nail contracts early. Inconsistent APIs were the main drag; the adapter pattern was the fix that stuck. I'd do the contracts even earlier next time.

Impact & Results

Shipped platform where pros and citizen contributors can work in one loop. Stories could include verified UGC without a parallel shadow process. Feedback highlighted the modern newsroom feel and the verification path, which was the risky part we had to get right.