Remove warnings and clean up getting started docs #1559
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
Co-authored-by: Chris K <55621012+chrisk-7777@users.noreply.github.com>
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit e072179:
|
|
|
chrisk-7777
approved these changes
Jan 19, 2023
1 task
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.
Related Issues
Contains #1549. Relates to #1220 and a comment in #1033.
Summary
docs/getting-started/*.introduction.mdx=>introduction.md2.recipes.mdx.Check List
yarn run prettierfor formatting code and docsFootnotes
Semantic line breaks are a great tool for documentation maintenance. They ensure easier to navigate diffs, better raw docs readability in code editor, and make typos and language errors easier to spot. More info on semantic line breaks here. ↩
There is no need to use MDX, because standard Markdown supports HTML syntax. MDX is only needed for rendering JSX components, like React ones. More info on MDX here. ↩