add next steps and pro-tips to getting-started guide#8138
Open
ShifaTikki wants to merge 2 commits intowebpack:mainfrom
Open
add next steps and pro-tips to getting-started guide#8138ShifaTikki wants to merge 2 commits intowebpack:mainfrom
ShifaTikki wants to merge 2 commits intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This file contains hidden or 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.
Summary
In the "Getting Started" guide, I have added a "What's Next?" section and a "Pro Tip" immediately after the conclusion. This helps beginners navigate to core concepts like Entry Points, Output, and Loaders, providing a smoother transition after their first build.
Motivation
Currently, the guide ends abruptly. These navigation links help beginners know exactly where to go next, making the onboarding experience more professional and user-friendly. (Resubmitted with correct commit identity and template).
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged?
Already documented in the PR itself.