Introduction
SeeAMess is a lean, headless CMS, built to replace Optimizely CMS 12 without its weight. It can run on top of a live Optimizely site while a team moves over: it reads Optimizely’s database and never writes to it.
What you get
Section titled “What you get”| Part | What it is |
|---|---|
| Engine | The CMS: one Rust binary with the roles authoring, projector, delivery, media, jobs and editor. PostgreSQL and a blob store hold all state. |
| Editor | The editorial and administration UI, one React application. The engine serves it at /editor/. |
| SDKs | Optional SDKs in Rust or .NET: content types in code, typed clients, extension hosts. The engine needs neither. |
| Optimizely adapter | seeamess-migrate, a .NET tool with assess, sync (the overlay), import, graph and verify. |
SeeAMess is headless: it serves JSON, and your front-end renders it. A front-end written against Optimizely’s Content Delivery API v3 keeps working, because SeeAMess also answers in that shape.
Design in one paragraph
Section titled “Design in one paragraph”Authoring is the only writer. Every command is one transaction that writes a new immutable version and appends an event to an outbox. The Projector turns those events into one pre-built JSON document per content and locale. Delivery serves a request with one indexed lookup of that document, and never joins, merges languages or checks version status. Every command and query passes through one authorization interface. Extensions run outside the core process. See Architecture and modules.