Tramway — Editorial Content Platform

We developed an internal platform called Tramway to help publishing professionals collaborate, plan, organise and schedule their content for publication on multiple platforms (web and print). The client was Groupe Saint-Paul, Fribourg — a media group that publishes newspapers, magazines, and digital content across French-speaking Switzerland.

The Problem

Before Tramway, editorial teams relied on a patchwork of tools — spreadsheets, emails, and disconnected workflows — to coordinate content across print editions and web channels. There was no unified view of what was planned, in progress, or published. Deadlines were frequently missed and content duplication was common.

What We Built

Tramway provided a single workspace where editors, journalists, and layout designers could create, review, and schedule articles for both web and print. The platform included a rich content editor built with Editor.js, tailored to the needs of publishing professionals. Articles could be tagged, categorised, and assigned to specific print editions or web sections. A scheduling calendar gave teams full visibility over upcoming publications across all channels.

Team & Process

Team of six people, three from Mimacom and three internal colleagues. We worked together using agile methods with sprint meetings every two weeks to define requirements, discuss priorities and complete tasks. We did code reviews with each other before each merge, ensuring consistent quality across the codebase.

Technical Stack

We built the REST API using Strapi (based on the Koa framework) and the frontend application using Vue.js with TypeScript. Vuetify provided the component library for a consistent UI. For the database we used PostgreSQL, and Meilisearch powered fast full-text search across articles and metadata.

Content Editor

A key feature was the browser-based content editor built on Editor.js. We customised it extensively to support the editorial workflow — inline annotations, image blocks with caption management, and structured content blocks that could map cleanly to both web rendering and print layout templates.

DevOps & Deployment

We had a solid CI/CD setup using GitLab pipelines with automated testing and deployment to three environments (dev, test, prod). The application was containerised with Docker, and we automated documentation publishing as part of the pipeline prior to each deployment.

My Contributions

I contributed across the full stack — building API endpoints, implementing frontend views and components, integrating the Editor.js-based content editor, and improving the CI/CD pipelines. I also participated in architectural decisions around data modelling and search indexing strategies.