-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible to add sourcesNodes in the gatsby-node.js? #1285
Comments
Hey @wcastand Thanks for reporting this issue !
No there isn't, it was an oversight from our side 😅 It will be fixed in 2.2.0 by this commit, meanwhile you can try it out in yarn add docz@next # or docz@2.2.0-alpha.1
It should be possible to use You would probably need to shadow the useDbQuery hook and/or the Layout component. |
I did it an other way but thank for the quick fix ! i'll probably have to use this in the final project. I checked and the gatsby-node.js now has all the hooks so no reason for it to not work anymore. I think we can close this for now :) |
@wcastand curious what your solution for this was - I'm looking into sourcing content from a CMS (looking at maybe Takeshape or something) and would like to pull in the source to my docz / gatsby installation with the ultimate goal of allowing a customer to update content from the CMS. having trouble finding any examples of this. |
@colbyfayock @wcastand I'm trying to do the same thing -- I'm admittedly new to Gatsby and Docz, but everything works great from my filesystem. Would love to source my MDX files from a CMS like Takeshape or DatoCMS but I'm not sure what hooks or components to shadow in order to make that happen. |
Bug Report
I'm trying to add data to the graphql source with a gatsby-config.js. but the console.log doesn't appear.
i just took a look into .docz/gatsby-node.js and seems that we can only extend
onCreateWebpackConfig
andonCreateBabelConfig
. Is there a reason for this?how can i add more data to my website and is it possible to use
StaticQuery
after ?The text was updated successfully, but these errors were encountered: