Caleb Media's New Content Delivery System
Caleb Media has built a new content system that lets us manage updates centrally while allowing each product to publish them through its own website, design, and identity.
As Caleb Media continues building more products, managing content across all of them has started becoming its own engineering problem.
A company announcement might belong on Caleb Media, while a product update belongs on that product's website. Some stories may be relevant to multiple products, but copying and maintaining separate versions of the same content quickly becomes messy.
So we built a new content delivery system around a simple idea:
Create content once, then let each product present it in its own way.
One place to manage content
Caleb Media now has a centralized system for managing articles, product updates, case studies, and other editorial content.
Instead of treating every website as a completely separate publishing system, content can be managed centrally and associated with the products it belongs to.
That gives us one source of truth without forcing every Caleb Media product to use the same website design or page structure.
Every product still feels like itself
Centralized content does not mean centralized design.
A Grydbase update should still look and feel like Grydbase. A Caleb Media announcement should still feel like Caleb Media. Future products should be able to do the same.
The content system supplies the information.
Each product controls how that information is presented.
That separation lets us reuse content infrastructure without turning every website into a copy of the others.
Products, topics, and platforms
The system also separates several different ways content can be organized.
Products identify which Caleb Media products a piece of content relates to.
Tags describe what the content is about, such as engineering, infrastructure, design, or security.
Platforms describe where that content may eventually be used, whether on a website or another publishing channel.
Keeping those concepts separate gives us much more control over where content appears and how other systems can use it.
Built without adding unnecessary infrastructure
Another goal was keeping the system simple.
Editorial content does not need the same infrastructure as an application handling accounts, payments, or live customer data.
The new system is built around version-controlled content rather than introducing another database solely for publishing articles.
That keeps the publishing layer portable, auditable, and relatively lightweight.
Designed for what comes next
The biggest reason for building this was not the content we publish today.
It was making sure the next Caleb Media product does not need another completely separate publishing system.
New products can connect to the same content foundation while keeping their own branding, websites, and user experiences.
It is a relatively small piece of infrastructure, but it removes a growing amount of duplicated work behind the scenes.
As Caleb Media grows, that is exactly the kind of system we want to keep building: shared foundations where they make sense, while allowing each product to remain its own product.