Connect what you already have
One model, two representations.
Canonical content types map onto the shapes found in source without requiring the source files to be rewritten — so the same asset is a Narraxio record and a TypeScript object at once.
Content Types
- Canonical type definitions
- Source schema mapping
- Typed and nested values
- One type, many source formats
How it helps
What Content Types gives you
No migration required
The mapping is a layer. Your files keep their shape, their imports and their build.
Typed values preserved
Arrays stay arrays, nested objects stay nested. Nothing is flattened into a string for the convenience of the editor.
One type across sources
The same canonical type can be backed by TypeScript in one repository and MDX in another, which is what makes cross-brand search coherent.
Models & Sources
The rest of Models & Sources
Discover the content model before asking anyone to rebuild it.
Schema Discovery
Find the repeated structures your code already uses as a content model.
Learn moreSource Bindings
Repository, file, export, object and field — the address that makes write-back safe.
Learn moreImports
TypeScript, JavaScript, JSON, Markdown, MDX and YAML to begin with.
Learn moreContent Migrations
Move selected content from code-backed to Narraxio-delivered, keeping IDs.
Learn moreGive your content a memory. Give your AI the full picture.
Connect a repository read-only and see what has been sitting inside it — every headline, claim and near-duplicate paragraph, with the file and field each one came from.
Keep Git and your existing stack Read-only to start Narraxio runs on Narraxio