Over the last 30 days, we focused on a specific problem: reducing the time and coordination required to create, update, and launch websites.
To do that, we added multiple structured document types to Promenad and exposed each of them through XML APIs. These APIs are consumed by a website filler script that maps tokens directly into templates. The website itself does not store content. Promenad does.
This approach turns Promenad into a headless CMS that can support one or many websites from a single system.
Why XML and Token-Based Filling
The goal was not to build another page editor.
We wanted a system where:
-
Templates define layout and structure
-
Content exists independently of presentation
-
Websites can be generated or updated without manual editing
By exposing content through XML, websites can request only the data they need in a predictable format. Tokens act as explicit placeholders, making it clear what content belongs where and eliminating ambiguity during rendering.
This allows teams to template sites using modern AI tools, then populate them deterministically by printing tokens—without rewriting or restructuring content later.
Promenad as the Content System of Record
Website content now lives alongside other operational documents in Promenad.
This matters because Promenad already tracks:
-
Creation dates
-
Edits and revisions
-
Launch timing
-
Relationships between documents
When website content is treated as first-class data, teams can see exactly when something changed, why it changed, and what else it affects. There is no need to infer state from a CMS UI or rely on manual change logs.
Faster Collaboration, Fewer Bottlenecks
Traditional CMS workflows serialize work. One person edits. Another reviews. A third publishes.
By separating content from rendering and centralizing it in Promenad, teams can work in parallel. Content updates, structural changes, and launches can move independently while remaining coordinated through the same timeline.
This reduces handoffs, shortens feedback loops, and lowers the risk of publishing outdated or inconsistent information.
This Website Is the First Implementation
The Orca Pings website is the first production site built on this architecture.
It validates that Promenad can function as a headless CMS without losing its broader role as an organizational system. The same content model can now support multiple websites without duplication or fragmentation.
This work establishes a foundation we will reuse. The goal is not novelty—it is repeatability, clarity, and speed.