Storyblok content structure changes in Shopware
CMS and development teams can share Storyblok content structures between designated workspaces. FroggShop can export these definitions, compare differences and control their restoration.
Share structures, not pages
The export covers components and their groups: it describes the elements editorial teams use to compose their content.
Moving these structures does not publish pages or automatically migrate all their content. Stories have a separate process.
Compare before restoring
Restoration compares the source file with the target space and takes identifier mappings into account. Creations, updates and deletions follow explicit permissions.
A dry-run mode allows teams to examine differences before applying changes.
Preserve existing content
A structural change can affect existing pages. The project must define the target space, permissions, prior backup and content to check after intervention.
The mechanism does not provide automatic rollback after failure. Service errors and concurrent changes require a suitable recovery procedure.
What is the scope of your project?
Tell us about your needs and the tools you use. We can clarify the possibilities, conditions, alternatives and scope of work suited to your project.
Discuss your needs