gatsby-source-graphql | Gatsby source plugin for pulling in data from GraphQL APIs | GraphQL library

The gatsby plugin will attempt to retreive the schema from your apollo-server. Ensure that introspection is enabled in production so this step does not fail.

After so much of the build try, I realized that the netlify env key AIRTABLE_API_KEY has been altered, fixing the API key resolved the issue.

Note: Use Netlify-cli tool and try to use netlify build --debug locally

Your gatsby-node.js looks perfect. Your issue is caused by the types of the data context you are sending to the template (videoDetailTemplate). You are telling to GraphQL that both id and editorId are ID types while I guess they should be strings.

I guess changing this line:

This is because your localhost:8000/___graphql is generated on the build-time, at this point, the cart will be always empty since the user has not been allowed to fill it yet.

Your WP GraphiQL API is an asynchronous API that gets the data in real-time, on-demand as the user fills the cart so it will always contain the as soon as the requests are done. To "connect" both, you will need to perform some fetch/post request to your API.

You can read for further information in Build Time and Client Runtime Data Fetching.

I started creating a minimal reproduction and adding everything back one by one, but decided to play more with my first setup for a little...and I'm glad I did.

This Gatsby install is part of a Project Template we use which includes backend code, front-end, pipeline deployment scripts, etc. The structure is similar to:

ProjectTemplate folder

• client folder
• server folder
• other folders

The Gatsby install lives in the client folder but occasionally I need to go into the root folder to do certain things.

I accidentally installed gatsby-source-graphql into the root folder instead of the client folder. That's all. I should have picked this up when I ran gatsby info --clipboard as it's clearly not listed as a dependency.

File System Route API is the new brand was developed by Gatsby (^2.26.0) to create pages dynamically, removing the GraphQL query of the gatsby-node.js and using a syntax notation in the /pages folder ({},[],(), etc).

Following your use-case, you will need to infer and modify the schema by prefixing the "all" keyword (maybe using createNodeFactory and createNodeHelpers from gatsby-node-helpers package, without knowing exactly your data schema and structure it's difficult to guess a sample code), but the idea is:

What you are trying to implement is called webhook, however, due to Gatsby's limitations (being a static site generator) the site must be rebuilt to gather the new data in order to create your new static pages based on your updated content.

If you think of how Gatsby works (in the build-time it fetches all data-sources and generates a static HTML with all your JavaScript bundle and logic behind) you will see that you can't bypass a new data fetching without rebuilding the site.

A webhook will create a connection between your CMS and your site, there you trigger a build once the new data is created, updated, or deleted.

If your content comes from an outer API, and you don't care about SEO, you can create an API request once the user enters your site to populate it with your content, however, you'll lose all the advantages that Gatsby provides.

There only two files missing from the Tutorials folder: step-by-step-guide-how-to-buy-agoras.md and step-by-step-guide-how-to-store-agoras.md.

I think that the issue is with the formatting of the frontmatter in these files, not with gatsby-source-git.

As you can see, hat sets them apart from the other files is that they both have colon inside a value:

• title: Agoras: How to Store
• description: Agoras: How to Buy

You need to add quotes around those:

• title: "Agoras: How to Store"
• description: "Agoras: How to Buy"

Your query probably failed at parsing these, hence the files didn't appear. Let me know if this fixes your issue!

Can you try something like title = {title} passing it in as a props of helmet rather than as the title tag you have like above