How to Retrieve Drupal Nodes in Draft State in Gatsby Development Mode

When working with Gatsby and Drupal, it's essential to ensure that your website's content appears exactly as intended, even when dealing with unpublished draft content. But how can you achieve this without compromising your development process?
In this blog post, we'll unveil a simple yet powerful technique to fetch and display draft nodes using Gatsby seamlessly.
Using NODE_ENV to Filter Nodes
Using this simple code example, you can include nodes on Draft state only in development "gatsby develop".
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
exports.createPages = ({ graphql, actions }) => {
const { createPage } = actions
const status = process.env.NODE_ENV === 'production' ? '["1"]' : '["0", "1"]'
return graphql(`
{
drupal {
articles: nodeQuery(
filter: {
conditions: [
{ operator: IN, field: "status", value: ${status} }
{ operator: EQUAL, field: "type", value: ["article"] }
]
}
sort: [{ field: "created", direction: DESC }]
) {
entities {
entityId
entityLabel
... on Drupal_Node {
status
path {
alias
}
}
}
}
}
}
`).then((result) => {
if (result.errors) {
throw result.errors
}
const { articles } = result.data.drupal
articles.entities.forEach((article) => {
createPage({
path: article.path.alias,
component: path.resolve(`./src/templates/article.js`),
context: {
slug: article.path.alias,
id: article.entityId,
},
})
})
})
}
This code sets a value to the status constant based on the process.env.NODE_ENV value and then uses that value to fetch Published nodes on production and Draft + Published nodes while running in development mode.
Wrapping Up
The objective of fetching only published content on production is to hide those nodes while executing the build process and avoid deploying unpublished content.
Efficiently managing content visibility during the development process is crucial for any Gatsby and Drupal project. Using our code example, you can effortlessly include draft nodes only when running in development mode, ensuring a crystal-clear preview of your unpublished content. With this technique, you'll control what is displayed in production while seamlessly testing and refining your website's user experience. Unlock the power of Gatsby and Drupal while keeping unpublished content under wraps, and propel your development workflow to new heights.

About the author

The (Non-Technical and Technical) History of Drupal Up to 2025
By Jesus Manuel Olivas, May 1, 2025Discover Drupal’s journey from its humble beginnings to 2025, exploring the platform's evolution from both a developer and editorial perspective. Learn how key innovations like Drupal Console and Drupal Decoupled have shaped code workflows and content delivery, transforming digital experiences across industries.

From Drupal Console to Drupal Decoupled: Contributing to Making Drupal Community Stronger
By Jesus Manuel Olivas, April 25, 2025Explore our journey from Drupal Console to Drupal Decoupled and how these projects reflect Octahedroid’s practical approach to open-source contributions, aiming to solve real developer and enterprise challenges.
Take your project to the next level!
Let us bring innovation and success to your project with the latest technologies.