-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
docs(tutorial): finishing touches #32833
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
**Want to see how it all fits together?** Check out the commit history in the [GitHub repo for the finished example site](https://github.com/gatsbyjs/tutorial-example). | ||
|
||
</Announcement> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely not blocking, but you can put something like this into its own MDX file to turn it into a component, then import it places like this and in the other parts, e.g. import CommitHistoryCallout from './commit-history-callout.mdx
Another thought I had when looking at this: if you have 1-to-1 commits with each step, you could link directly to that commit in GitHub
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh nice, I'd never thought about importing from other MDX files.
Also I thought about adding links to the exact commits, but I've been rebasing and force-pushing the demo site when I make tweaks to the Tutorial content, which messes up all the commit hashes. I figured it would be less work to maintain to use a generic link to the repo. (Unless maybe there's some git trick for updating branches when you rebase?)
Description
Adds finishing touches to the new Gatsby Tutorial, as well as assorted copy edits / typo fixes.
Finishing touches include:
ch32545
Documentation
/docs/tutorial/*