Fix and clarify Ghost sourcing page #19411
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
freiksenet
reviewed
Nov 12, 2019
|
Thanks! Added a comment to clarify language. |
Name is not important. Only one per page. Gatsby just looks at the exports which is type graphql |
jbampton
added
the
type: documentation
|
These changes look good to me. @dandv would you mind opening an issue with your larger questions so they don't get lost when this is merged? Thanks for helping out! |
Co-Authored-By: Mikhail Novikov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Ghost sourcing page did not actually output any HTML. This PR fixes that, and attempts to clarify the process.
I still don't understand how
postQueryis used. That symbol can be named whatever, and the posts are still rendered. Anyone?It would also be useful to explain (or point to)