Publish approved articles
Connect
SPIRITT
Builder.ioBuilder.io
Content updates at operator speed
SPIRITT ships Builder.io content without the click-through. It reads your models, creates and publishes entries from approved copy, patches fields across hundreds of entries, and keeps the Space clean.
What you can do with Builder.io.
Model-aware publishing
Read your models and field schemas, then create entries as drafts or published content that fit them.
Bulk edits without clicks
Filter entries across any model and patch fields in place, from copy to targeting.
A Space under control
Audit folders, assets and user roles, and retire outdated entries cleanly.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for content operations. Share your publishing calendar and approval rules.
02
Connect Builder.io
Connect your Builder.io Space, then add the docs, commerce or analytics apps your content comes from.
03
Delegate an outcome
Name the pages, models and launch timing. SPIRITT creates the entries, publishes on schedule and verifies what went live.
Hand over a mission.
Choose a mission. Make it yours.
Put Builder.io to work.
Content updates at operator speed
Questions
Builder.io, with SPIRITT.
01Can SPIRITT publish content?+
Yes. It creates entries as drafts, published or archived, updates them and deletes the ones you retire.
02Does it respect our content models?+
Yes. It reads your models with their field schemas before creating or editing entries.
03Will updates overwrite other fields?+
Omitted top-level fields stay untouched. Because a supplied data object replaces the existing one, SPIRITT reads the entry first and writes the complete set.
04Can it use our image library?+
Yes. It lists, filters and sorts your existing assets so entries reference the right images.
05Do our webhooks still fire?+
Yes. New entries fire your configured Builder.io webhooks by default, so downstream builds keep running.
06How does it confirm changes went live?+
Content reads are cached, so SPIRITT uses a one-off cache-busting read to verify fresh content after an edit.