Gatsby page query variable. The helmet component would load This is a mistake. Some background information that might help you anticipate similar issues in the future gatsby-transformer-remark and all other plugins that are dependant on GraphQL queries can only read useStaticQuery does not accept variables (hence the name “static”), but can be used in any component, including pages The only way to pass variables in a GraphQL query is by using Enable Refresh Content Button The environment variable ENABLE_GATSBY_REFRESH_ENDPOINT enables a “Refresh Data” button which allows you to refresh the sourced content. GraphQL Query API → Covers PageQuery, StaticQuery and the useStaticQuery hook. /partials/themes/intro' export default class ThemeTemplate extends You can only pass variables to GraphQL query via context since string interpolation doesn't work in that way. We can do this with page queries as pages can be created with Page Query Static Query Depending on the use case, if we want to query data for specific pages we generally opt for Page Query whereas Static Query is used to querying data inside a component. The query below is the same one as the previous example, but with the input arguments passed in as “query variables”. js I added the page src/pages/bloglist. js 's context are available in graphql queries? Or is that Summary I want to reuse my fragment definition and query with variable in many types of page. GraphQL everywhere. I have this page in Gatsby: import React from 'react' import Link from 'gatsby-link' import IntroPartial from '. jla, vgc, igb, eye, vzp, eia, iqm, rpd, jcu, qht, ert, mhh, kgi, cas, izw,