Source
Structured content, localisation & export — found from sitemap — Storyblok
Checked for Storyblok on 13 Oct 2026
- Page
- https://www.storyblok.com/docs/concepts/content-modeling
- Checked
- 13 Oct 2026, 09:01 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e676bbd8ed54ca43886991fc8e733e5df98bb77eb4af39a69fbc62789db77f38
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Content model data types Report an error
“Storyblok represents content with three basic data types: Fields: Individual content inputs Blocks: Configurable content elements Stories: Complete content entries”
-
Schemas Report an error
“Storyblok manages these data types with two schemas: Components: Block schemas Content types: Story schemas”
-
Content types subset of components Report an error
“Content types are a subset of components, so a single component can potentially model both a part of a story or a whole story.”
-
Reference fields Report an error
“References: use Storyblok’s reference fields to create relationships between content pieces. This prevents repetition of data, ensures consistency, and empowers editors to create complex data schemas.”
-
Slug characters Report an error
“Slugs: story slugs accept a-z or A-Z, 0-9, underscores (_), and hyphen-minus (-). To accept any Latin, Greek, Han, Katakana, and Hiragana scripts as well, open Settings → Space and activate Allow special characters in slugs.”
-
Story identifiers Report an error
“uuid: the unique identifier of a story in a space. When the model links stories, reference them with uuid. id: the legacy numeric identifier of a story. The API response returns an id for existing integrations. Prefer uuid when you create a new project. _uid: the unique identifier of a single block inside a story.”
-
Field validation Report an error
“Fields for content inputs and configurations, using validation to ensure compliance”
-
Nestable blocks Report an error
“Nestable blocks to define reusable components, multiplying efficiency in design and development”
-
Datasources Report an error
“Datasources: define a “glossary” using datasources to manage common terms, options, and variables that need to remain consistent across the project.”
-
Preview testing Report an error
“Test each component as it is added by creating sample stories. Use the preview function to see how content renders on the frontend.”
-
Block library organization Report an error
“The Block Library displays all the building blocks the team has created to keep track of the project’s growth. Create folders and tags to better organize and filter blocks in the library.”
-
Preview space Report an error
“Use a preview space to test changes before applying them to production.”
-
Visual editor block selection Report an error
“_uid: the unique identifier of a single block inside a story. The Visual Editor uses it to open the matching block when an editor selects an element in the preview.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Head of Content Structured content, localisation & export
- The Head of Content Structured content, localisation & export
- The Head of Content Publishing, distribution & integrations
- The Data Protection Officer Structured content, localisation & export
- The Data Protection Officer Structured content, localisation & export
- The Data Protection Officer Publishing, distribution & integrations
- The Localisation Lead Structured content, localisation & export
- The Localisation Lead Publishing, distribution & integrations
- 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 Publishing, distribution & integrations
- The SME Marketer Structured content, localisation & export
- The Web Engineer Structured content, localisation & export
- The Web Engineer Publishing, distribution & integrations
- The Web Engineer Structured content, localisation & export
- The Web Engineer Publishing, distribution & integrations