The hourglass model and its limits
Gatsby's role in a site build is often pictured as an hourglass. The generator sits at the narrow waist. At the top, a wide funnel of inputs: markdown files, a headless CMS or other API, a hosted database, or essentially anything else. At the bottom, a wide funnel of outputs: static files that can be deployed to Netlify, GitHub Pages, ZEIT, S3, or wherever else.
Gatsby does plenty of useful things, and its React foundation is part of the appeal for many developers, but the crucial piece is how it consumes arbitrary data sources.
Turning the hourglass into a pipe
Widening that shape until it becomes a pipe means building a tool that links arbitrary data sources to arbitrary static site generators. That is the aim of Sourcebit, from Stackbit. It uses a two-sided plugin model: Sources such as Contentful or Sanity on one end, and Targets such as Jekyll or Hugo on the other. The goal is to connect any data source with any site-building tool that needs that data.
Contributors to all projects in both the data-source and site-builder arenas stand to gain if this succeeds, Gatsby included.



