ArchivesSpace - Storyblok Integration and Automation

Common Integration Use Cases Between ArchivesSpace and Storyblok

1. Publish archival collection summaries from ArchivesSpace to Storyblok

Direction: ArchivesSpace → Storyblok

Archivists can maintain authoritative collection descriptions, finding aids, and metadata in ArchivesSpace, then push approved public-facing summaries into Storyblok for website publishing. This allows communications and web teams to present archival content on the public site without manually re-entering data.

• Reduces duplicate content entry across teams
• Ensures public content stays aligned with archival records
• Speeds up publication of new or updated collections

2. Sync collection highlights and featured items for campaign pages

Direction: ArchivesSpace → Storyblok

Selected collection highlights, notable artifacts, or exhibit-ready records can be sent from ArchivesSpace into Storyblok to support marketing campaigns, landing pages, and digital exhibits. Storyblok editors can then assemble rich pages using approved archival content blocks.

• Supports faster creation of exhibit and campaign pages
• Improves consistency between archival data and public storytelling
• Enables non-technical teams to build pages from trusted content

3. Update public collection pages when archival records change

Direction: ArchivesSpace → Storyblok

When archivists revise collection descriptions, access notes, dates, or scope statements in ArchivesSpace, those changes can automatically update corresponding Storyblok content entries. This keeps public-facing pages accurate without requiring manual review by web editors for every metadata change.

• Minimizes stale or conflicting information on the website
• Improves governance over authoritative content
• Reduces maintenance effort for content teams

4. Create editorial workflows for public archival stories

Direction: Storyblok → ArchivesSpace

Storyblok can be used to draft public narratives, exhibit introductions, or interpretive content that references archival collections. Once approved, key references or related content identifiers can be sent back to ArchivesSpace to document how specific collections are being presented publicly.

• Creates a traceable link between interpretation and source records
• Supports editorial review and compliance processes
• Helps archivists understand how collections are being promoted externally

5. Link digital exhibits in Storyblok to authoritative archival records

Direction: Bi-directional

Storyblok can host digital exhibit pages while ArchivesSpace provides the authoritative collection metadata and item references behind those exhibits. The integration can store cross-links in both systems so editors can navigate from a public exhibit page to the source archival record and back again.

• Improves discoverability for researchers and visitors
• Strengthens provenance and source transparency
• Supports richer digital exhibit experiences

6. Automate metadata-driven content blocks for the website

Direction: ArchivesSpace → Storyblok

Structured fields from ArchivesSpace such as collection title, dates, extent, creator, and access restrictions can populate reusable Storyblok content blocks. This is especially useful for institutions managing many collection pages or departmental archive listings.

• Standardizes page structure across the site
• Improves scalability for large archival catalogs
• Reduces manual formatting and copy errors

7. Maintain a public archive portal with controlled editorial flexibility

Direction: Bi-directional

ArchivesSpace remains the system of record for archival metadata, while Storyblok provides the flexible content layer for public navigation, contextual text, and calls to action. The integration allows Storyblok editors to enhance the user experience without altering the underlying archival authority data.

• Balances governance with content agility
• Supports both structured data and editorial storytelling
• Enables cross-functional collaboration between archivists and web teams