Maintain content contract tests
Connect
SPIRITT
Kontent.aiKontent.ai
Build around your content foundation
SPIRITT builds useful experiences from your Kontent.ai content foundation. Turn structured items and language variants into working portals, validate frontend contracts and carry editorial gaps through an owned acceptance workflow.
What you can do with Kontent.ai.
Structured content becomes an app
Use your real content types and delivered items to build catalogs, resource libraries and private content tools.
Localization with exact references
Compare supported language variants against the approved market plan and route missing material to its owner.
Content contracts stay visible
Inspect type elements and item values before building interfaces, then turn mismatches into actionable editorial work.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for content delivery apps with Kontent.ai.
02
Connect Kontent.ai
Connect your Kontent.ai account and choose the account access your mission needs. Keep other connected apps scoped to the same work.
03
Delegate an outcome
Describe the result, the Kontent.ai records to use, and the rules for changes or delivery. SPIRITT builds the workflow and follows the result through.
Hand over a mission.
Choose a mission. Make it yours.
Put Kontent.ai to work.
Build around your content foundation
Questions
Kontent.ai, with SPIRITT.
01Can SPIRITT build a site or app from Kontent.ai?+
Yes. Content items, type definitions and language variants can power real interfaces, with access and rendering rules appropriate to the content audience.
02Can it write or publish CMS content?+
The evidenced connection provides content reads, not creation, translation writes or publication. SPIRITT can deliver apps and coordinate the editorial work around the source.
03Can it compare language variants?+
Yes. Languages and specific item variants can be retrieved using their real identifiers, so localization checks do not rely on guessed language codes.
04Can it inspect the content model?+
It can list content types and retrieve specific element definitions. Those reads help validate frontend contracts before building against the data.
05Does it support large libraries?+
Item retrieval supports continuation tokens, and content types are paginated. SPIRITT keeps retrieval scoped and accounts for incomplete results explicitly.
06Can it recheck editorial fixes automatically?+
Yes. A scheduled workflow can re-read named items and variants, compare them with acceptance criteria and update tasks in a separately connected project tool.