Skip to main content
Webedia Elephant · Engineering

The team blog for
building the modern web.

Engineering notes from the Webedia Elephant team.

Read the articlesAbout the team

Latest articles

All articles →
Isometric editorial workflow: article cards from several source sites converge on a blue compass-like Polaris hub, where an editor routes them through a localization prism to destination websites.Editorial Platform

Polaris: one editorial pool for every market

How Polaris helps writers and editors discover, understand, localize, review, and deliver articles across Webedia brands—without replacing each website’s CMS.

Paul-Émile Miny ·
Isometric illustration: one glowing blue admin dashboard connected by identical cables and adapter rings to five very different database machines — a modern server, an aged terminal, a database cylinder, a jukebox, and an old industrial boiler.Architecture

One admin for all our brands: a research project

Every Webedia brand rebuilds the same back-office on a different database. Admin international is our research bet — today a working proof of concept: one shared, extensible admin any brand plugs into, no database migration required.

Paul-Émile Miny ·
Diagram comparing Cloud NAT (higher cost, higher latency) to a self-managed NAT gateway (high performance, full control, cost efficient, low latency), with call-outs showing 40% lower cost and latency dropping from 40s to 8s.Infrastructure

Cutting our NAT bill by 40% and our latency by 6×: from Cloud NAT to a self-managed gateway

How we reduced our NAT and firewall costs and improved performance by migrating from Cloud NAT to a self-managed gateway.

Matthieu Courtois ·
The GitLab logo above the words CI/CD on a blue backgroundCI/CD

The shared GitLab CI templates

A plain-language tour of the reusable GitLab CI/CD components in the transverse templates repo — what each one does, from GCP auth to deploy notifications and AI code review.

Sébastien Rommens ·
Isometric pipeline: a container of source files feeds a factory that builds and compresses a folder of static assets, then fans out to clouds and browsers.Infrastructure

How this blog ships: Astro + Tailwind + Bun, deployed to GitLab Pages

The exact build of the blog you are reading — why we picked Astro, how Tailwind styles it, how Bun builds a static site, and how GitLab CI publishes it to Pages. No Node, no nginx, no running server in prod.

Paul-Émile Miny ·

Got something to share? Write with us.

Open a merge request →View on GitLab