Introduction Improvements #569
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
mathewbyrne
commented
Mar 4, 2019
docs/content/introduction.md
Outdated
|
|
||
| First take a look at the [Getting Started]({{< ref "getting-started.md" >}}) tutorial. | ||
| First work your way through the [Getting Started]({{< ref "getting-started.md" >}}) tutorial. |
There was a problem hiding this comment.
TODO there definitely another paragraph here that mentions something about looking at Resolvers, Type Mapping etc, in roughly the order we think it's important to further learn gqlgen concepts.
cgxxv
pushed a commit
to cgxxv/gqlgen
that referenced
this pull request
Mar 25, 2022
Introduction Improvements
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.
This aims to improve our introduction and README sections with the following changes:
README.mdanddocs/content/introduction.mdnow have the same content.README.mdCurrently README and introduction are maintained separately. I couldn't figure out a way to have them read the same source; GitHub MD has no include functionality, and hugo cannot read files outside of it's root directory (/docs).They also use different link syntax (hugo uses<ref >shorttags) making them a little incompatible.Maybe we could lint for this? It's always going to be a bit fuzzy though. Otherwise some compile step that writes both files from a single source?Of course, git can track links. With this we are able to link
README.mdinto the hugo content dir and munge it's contents there.