Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Gatsby 5 starter for a recipe website with Flotiq headless CMS and Tailwind CSS.
Flotiq Gatsby Recipe 1 is a Gatsby 5 starter that produces a recipe website backed by the Flotiq headless CMS and styled with Tailwind CSS. It is a boilerplate project that connects Flotiq content objects to Gatsby's GraphQL layer and includes ready-made deployment setups for Heroku, Netlify, and Cloudflare Workers.
Flotiq Gatsby Recipe 1 is an open-source Gatsby starter that creates a static recipe website using Flotiq as the headless CMS and Tailwind CSS for styling. It accepts a Flotiq API key plus an optional Google Analytics measurement ID through environment variables, and it renders recipe content managed in the Flotiq editor into Gatsby pages. The project is maintained by Flotiq and is licensed under the MIT license, with source code available on GitHub.
gatsby-source-flotiq plugin to fetch content, and the Flotiq editor at editor.flotiq.com to manage recipes, ingredient lists, and instructions.tailwind.config.js, with global styles in src/style and component classes used throughout templates.flotiq-components-react library provides pre-built components designed to match Flotiq content objects, included in the src/components directory.flotiq start from the Flotiq CLI clones the repository, installs npm dependencies, writes the .env.development file, imports four example content objects, and launches gatsby develop..flotiq directory defines the required content types, and flotiq import .flotiq [apiKey] adds four example recipe objects to a fresh Flotiq account.netlify.toml, static.json, and wrangler.toml.src folder separates assets, components, layouts, pages, sections, global style, and templates, making it clear where static pages and generated page templates live.Flotiq Gatsby Recipe 1 suits developers and content teams that want a working Gatsby + headless CMS setup without building from scratch. Food bloggers can manage recipes in Flotiq and publish a styled site. Front-end developers learning Gatsby can study how a source plugin feeds content objects into GraphQL queries. Agencies can use the Flotiq CLI to spin up client projects with sample data and deploy them to Netlify or Cloudflare quickly.
src/templates/index.js, gatsby-node.js, and the GraphiQL explorer at localhost:8000/___graphql to see how recipe content is queried and rendered.The quickest path uses the Flotiq CLI: install it with npm install -g flotiq-cli, then run flotiq start [projectName] https://github.com/flotiq/flotiq-gatsby-recipe-1.git [flotiqApiKey]. This command clones the template, installs dependencies, populates .env.development with the API key, imports four example objects, and starts the development server. For manual setup, copy the environment variable structure, run flotiq import .flotiq [apiKey] to add sample data, and start with gatsby develop.
Flotiq Gatsby Recipe 1 is a starter template for building recipe websites with Gatsby 5, the Flotiq headless CMS, and Tailwind CSS. It includes example content types, pre-built components, and deployment configurations so you can start with a full project rather than an empty boilerplate.
The starter requires Node.js version 18 or higher because it is built on Gatsby 5. Running an older Node version will cause installation or build errors, so upgrade your local Node environment before using the template.
After cloning the repository, run flotiq import .flotiq [flotiqApiKey] with a read-and-write API key. This adds four example recipe objects to your Flotiq account. This step is optional if you used the flotiq start CLI command, which imports the data automatically.
Content is managed in the Flotiq editor. Since Gatsby generates static pages, you must rebuild the site after changing content objects: rerun gatsby develop in development or gatsby build in production. If a content type definition changes, run gatsby clean first. For automated rebuilds, Flotiq provides plugins for Gatsby Cloud and Netlify, or you can configure a webhook.
The README includes one-click deploy buttons for Heroku, Netlify, and Cloudflare Workers. Heroku uses app.json, Netlify uses netlify.toml, and Cloudflare Workers uses wrangler.toml plus worker-index.js. The Cloudflare Workers deployment uses a starter API key; you can replace it by adding a secret named GATSBY_FLOTIQ_API in your GitHub repository.
