How it works
Start by connecting your content. Migrate only if the new model earns it.
Most content platforms ask for a migration before they demonstrate any value. Narraxio is designed the other way round: connect what exists, see it structured, work with it, and decide about migration later — or never.
After connecting a repository
What a first read-only scan of the demonstration repository reports back.
- 183
- Pages
- 714
- Content assets
- 11
- Reusable content models
- 86
- Headlines
- 142
- Calls to action
- 27
- Repeated claims
- 18
- Likely duplicate passages
- 9
- Types with no clear author
Stage one
Git-connected mode.
Your source files remain the source of truth. Narraxio indexes them, reasons over them and proposes changes back through the workflow your team already uses.
- 01
Connect the repository
A GitHub App installation with least-privilege access, authorized repository by repository. Read-only to begin with.
- 02
Discover the content
Supported files are parsed and repeated structures identified — the content model your developers already built, written down for the first time.
- 03
Review the model
Confirm the proposed content types and source bindings. Nothing is written back until a human agrees the model is right.
- 04
Build the graph
Assets, relationships, imported provenance and search indexes are created, and the first inventory is there to look at.
- 05
Ask, edit and create
AI Studio works from the graph and Brand Brain rather than from an empty prompt box.
- 06
Preview
See proposed content rendered the way a visitor will, not as a diff of a TypeScript object.
- 07
Approve
Workflow states and guardrails, with review policies that differ by content type and risk class.
- 08
Publish through Git
An exact patch, a branch, a pull request — and your existing CI/CD does the deployment it has always done.
Repository discovery
northwind-web
└ apps/storefront/src/content/features.ts
Narraxio discovers
- Feature
- SubFeature
- headline
- lede
- points[]
Structured content assets
Each one addressable, each one bound back to the exact field it came from.
In Git-connected mode your source files remain the source of truth. Narraxio indexes them; it does not take them over.
Diagram: a file in the demonstration repository is parsed by Narraxio, which discovers the Feature and SubFeature types and their headline, lede and points fields, and turns them into structured content assets bound back to their original location.
Schema discovery
export type Feature = {
slug: string
title: string
eyebrow: string
headline: string
lede: string
points: { title: string; body: string }[]
included: SubFeature[]
}Proposed content types
- Feature8 recordsBindable
- SubFeature42 recordsBindable
- Solution7 recordsBindable
- Integration13 recordsBindable
- FAQ24 recordsBindable
- Plan5 recordsRead only
A human confirms the proposed model before anything is bound. Structures the serializer cannot change deterministically stay read-only rather than being attempted hopefully.
Source binding
- repository
- northwind-group/northwind-web
- branch
- main
- file
- apps/storefront/src/content/features.ts
- export
- features
- object
- feature[slug=scan]
- field
- headline
Bindings resolve through the syntax tree rather than by line number, and are re-verified against the latest revision before any write.
Discovery proposes. A human confirms. Only then is anything bound — and write support is enabled per structure rather than repository-wide.
Publishing
An approved edit becomes a pull request.
Validation, preview, approval, a deterministic patch, a branch and a pull request mapped back to the Narraxio change. Your CI/CD does the deployment it has always done, and no new service sits on your rendering path.
Write access is a separate grant from read access, made per repository and per structure — so connecting a repository never by itself gives Narraxio the ability to change anything in it.
Publishing through Git
- 1Edit in Narraxio
- 2Validate schema and facts
- 3Preview
- 4Approve
- 5Generate exact patch
- 6Branch and pull request
- 7Existing CI/CD deploys
Never a direct push to a protected branch. A pull request is the design, not a limitation of it.
Flow: a content edit made in Narraxio is validated against its schema and source facts, previewed, approved, turned into an exact source patch, committed to a branch and opened as a pull request, after which the customer’s existing CI/CD pipeline deploys it.
Stage two
Native Narraxio delivery.
Later, and only for the content types you choose, Narraxio can become the system of record — delivering through immutable release snapshots or a versioned API.
Choose the content types
Move the marketing copy and leave the routing configuration in code. The decision is per content type, not all or nothing.
Keep the identifiers
Assets that move to native delivery keep their IDs, relationships and everything already recorded about them.
Build against a release
An immutable numbered snapshot, or the versioned delivery API. The published site never depends on our control plane being up.
Leave if it stops earning it
Content can be exported back into source structures. A platform you cannot leave is a platform nobody prudent adopts.
Native delivery is optional. Git-connected mode is not a trial of it — it is a complete product, and a customer can stay there indefinitely.
In full
The eight stages, end to end.
Discover
Connect a repository and find the content hidden across files, exports, frontmatter and configuration — including the copy nobody remembers writing.
Structure
Turn pages, sections, fields, claims and reusable records into addressable Content Assets with stable identifiers and exact source bindings.
Understand
Connect each asset to the brand, product, source fact, audience, page and other content that explain why it exists and what depends on it.
Create
Brainstorm, draft, rewrite and repurpose with the full company context retrieved automatically instead of pasted into a prompt.
Govern
Keep authorship, AI involvement, source facts, review and approval as separate events rather than as one overwritten field.
Publish
Push approved changes back through Git as an exact patch and pull request, or deliver content through versioned APIs and snapshots.
Measure
Connect assets and variants to exposure, engagement and conversion so content is judged on outcomes rather than on taste.
Activate
Campaign and advertising systems consume the same governed content intelligence, and feed performance back into the graph.
Give 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