Storyblok Components can map 1:1 to React Components
Template and Component files to support different page types
Mix Storyblok content types with your other sources through GraphQL queries
Usage at Spork Bytes
Data from our REST API populates Gatsby GraphQL nodes
Storyblok root content is used to create standard pages and blog posts
Other Storyblok content can be queried alongside our API data to build custom pages such as “The Restaurants” page or partner landing pages
Used Storyblok content to build part of our Get Started form
Downsides
No support for Gatsby Image processing of Storyblok images in deeply nested component structures. See gatsby-storyblok-image for how to handle one-off images.
That’s all I can think of…it’s seriously a great CMS
Example Pages
Spork Bytes Homepage - HomePage root content type. Fully-managed Storyblok content mixed with REST API data.
Blog Post - BlogPost root content type. The post is managed in Storyblok and "See more of our blog" is dynamically built per-post from Storyblok BlogPosts.