Publications

Essay · 10 min read

An Editorial System That Outlives Its CMS

Mehdi Ayache BerberosSouth East Asia
Editorial notes, modular cards and typography arranged as a system
A system begins when each decision can be named, reused and moved.

A publication should belong to its author—not to the editor that happened to store it. This page is both an essay and a working inventory of the components required to publish with clarity.

Content is the permanent layer

Interfaces change. CMS products change. The durable object is a versioned document whose meaning remains intact when its source moves from local files to Matrix.

That requires three simple rules:

  • prose remains portable CommonMark;
  • complex presentation becomes a typed block;
  • raw executable markup never enters the document.

The same object can serve a web page, an RSS feed, structured metadata or an LLM-readable index. Inline concepts such as ArticleDocument remain readable without controlling the design.

The design system does not decorate the content. It protects the content from accidental inconsistency.

Mehdi Ayache Berberos

A small contract with a long life

The renderer understands a discriminated set of blocks. Matrix will later deliver this same contract through an API; it will not dictate the interface.

article-document.ts
type ArticleDocument = {
  version: 1
  blocks: ArticleBlock[]
}

type ArticleBlock =
  | { id: string; type: 'richText'; markdown: string }
  | { id: string; type: 'figure'; image: MediaAsset }
  | { id: string; type: 'code'; language: string; code: string }
A portable content contract: versioned, explicit and independent from the CMS.
A quiet architectural grid illustrating modular publishing
A wide figure can escape the reading column without escaping the system. · Temporary development image
One document, several consumers
ConsumerReceivesResponsibility
WebsiteRendered blocksReading experience
Search enginesMetadata and JSON-LDDiscovery
LLM indexClean semantic textComprehension
MatrixVersioned document contractEditorial management

The editor still feels simple

The underlying model should never punish the writer. Ordinary composition remains familiar:

  1. write the thought;
  2. choose a meaningful block only when needed;
  3. preview the actual reading experience.
  • headings, emphasis and links
  • ordered and unordered lists
  • tables, code and quotations
  • future editorial workflow in Matrix

Portability is not a technical afterthought. It is part of authorship.


Original

A system keeps the memory.

The interface keeps the moment.

الترجمة العربية

النظام يحفظ الذاكرة.

والواجهة تحفظ اللحظة.

CommonMarkA strongly defined, highly compatible specification for Markdown.commonmark.org

Built once, allowed to evolve

This is not an imitation of a generic publishing platform. It is a compact editorial language for one body of work—consistent enough to scale, flexible enough to remain personal.

Notes

  1. Portability here means that the content contract remains usable without the original authoring interface.

  2. External links open separately and user-authored raw HTML is excluded from rendering.