Source
Structured content, localisation & export — found from sitemap — Storyblok
Checked for Storyblok on 13 Oct 2026
- Page
- https://www.storyblok.com/docs/apps/shared-components
- Checked
- 13 Oct 2026, 09:02 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c4b001bcbd8f57043420b211eff8aed1f566d1be8398ed4b40615e04fb81c241
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Shared components purpose Report an error
“The Shared Components app takes the component definitions of a space from a parent space you nominate, so a set of sites that share components and layout is maintained in one place.”
-
Shared components single parent schemas Report an error
“Maintain component schemas in a single parent space.”
-
Shared components inherit all definitions Report an error
“Inherit every component definition from that parent space.”
-
Shared components setup Report an error
“During installation, set the ID of the parent space in the space settings. From then on, the space takes all its component definitions from that parent.”
Scores citing this record
- The Head of Content Structured content, localisation & export
- The Head of Content Structured content, localisation & export
- The Data Protection Officer Structured content, localisation & export
- The Data Protection Officer Structured content, localisation & export
- The Localisation Lead Structured content, localisation & export
- The Skeptic Structured content, localisation & export
- The Skeptic Structured content, localisation & export
- The SME Marketer Structured content, localisation & export
- The SME Marketer Structured content, localisation & export
- The Web Engineer Structured content, localisation & export
- The Web Engineer Structured content, localisation & export