[IGNORE IGNORE] Layer model #18092
Closed
[IGNORE IGNORE] Layer model #18092
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
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.
Description
In an effort to explain the GraphQL docs better I drew up what I thought would explain some of the "layers of Gatsby" as I thought of them. These are pretty simplified but generally express what happens in Gatsby in an order that shows data going all the way from a source to being consumed in a component.
I did some hacking to make the Content layer have the data be able to cycle through different data sources that all have the same simple content to express that data can come from anywhere and all ends up looking the same in the GraphQL layer.
I petitioned @fk for some design critiquing and used his input to clean up the design to make it less busy.
Added the component to a handful of guides in the Conceptual section where I think it could do the most help expressing what's happening at different places.
Happy to hear any suggestions on how to improve content of each section, design, or whatever it may be.
Related Issues
Related to #15616 about adding more visual aids to docs (though this is about GraphQL, not themes like that issue mentionos)
This came about while working on the GraphQL workflow in #16981, trying to explain these concepts better