Knowledge & Communication
One source of truth, many tailored renderings.
Content gets trapped in its format. A deck is a deck, a feed is a feed, and reshaping either for a new audience means starting over. This initiative treats content as structured data first: define it once in a canonical model, then render it for whoever needs it, in whatever shape they need.
Why it matters
The same information serves an analyst, a manager, and a feed reader very differently. When content lives as JSON instead of as a fixed document, you can branch, filter, and re-render it without losing a single source of truth. Author once, present everywhere.
How we approach it
- A canonical model underneath, with multiple render targets on top (HTML, PDF, Atom, JSON Feed, Markdown).
- Audience-aware branching so one source splits into tailored outputs.
- The same data renders identically across CLI, API, and UI.
Verso & Neurowire
Verso
Early accessPresentations defined in JSON, rendered in HTML, built for multiple audiences. One deck branches into different narrative threads while keeping a unified design.
Neurowire
SaaS soonTurn any blog into a modern feed. Normalizes sites, RSS and Atom into one model, then publishes Atom, JSON Feed, Markdown and styled pages. Freemium SaaS on the way.