← All integrations
Frameworks & formats
The config files that turned out to be content.
Translation bundles, navigation definitions, FAQ lists and feature matrices frequently live in JSON or YAML. They are content with a schema, which makes them among the most straightforward sources to import.
i
In short: Nested objects and arrays import with their types intact, and localization bundles are related across locales.
What it is
The two structured data formats most likely to be holding content that nobody classified as content.
What Narraxio reads
- Nested objects and arrays, with typed values preserved
- Repeated shapes, inferred as content types
- Localization bundles, with keys related across locales
- Comments and anchors in YAML, preserved where possible
How it is connected
- Connect the repository and select the data directories
- Confirm the inferred shapes and which files are content rather than configuration
- Relate localization bundles so translations link to their source
- write-back with formatting preserved
How you verify it
- Round-tripping reproduces the file before any write feature is enabled
- Locale keys are related to each other, so missing translations are visible
- Files that failed to parse are listed with the error
Limits worth knowing
- YAML has several ways to express the same value; the serializer preserves the original form or declines the write
- Deciding which files are content and which are configuration is a judgement, and one you make rather than one we make for you
Other integrations
Connect the rest of the stack
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