Content in a React codebase, where it is actually findable.
React projects keep content in two places: structured data modules, which are discoverable and bindable, and string literals inlined in components, which are neither safe nor pleasant to edit from the outside. Narraxio is honest about the difference.
In short: Structured content modules are fully discoverable. Copy hard-coded inside JSX has no stable binding, so it is surfaced where detected but treated as read-only.
What it is
The component library underneath most modern marketing sites, including the ones built with Next.js, Remix and Vite.
What Narraxio reads
- Exported arrays and objects used as content
- TypeScript types and interfaces that describe those shapes
- Content imported into components, traced to its definition
- Component usage, to relate assets to the pages that render them
How it is connected
- Connect the repository and run discovery
- Confirm which exports are content rather than configuration
- Review which files discovery skipped and why
- Decide whether inlined copy should be extracted into a content module first
How you verify it
- Every asset shows the export, object and field it came from
- Skipped files are listed with a reason rather than omitted
- A sample page can be reconciled against its extracted assets
Limits worth knowing
- Copy hard-coded inside JSX has no stable binding and is treated as read-only where it is detected at all
- Conditional or computed strings are not reliably extractable, and are not claimed to be
- Extracting inlined copy into a content module is a code change your developers make, not one Narraxio performs
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