Adapt Next.js "Getting Started" guide to Next.js App Router folder structure #99
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.
The App Router folder structure is the default option when creating a new Next.js project nowadays. However, the Tiptap Next.js "Getting Started" guide only mentions the Pages Router folder structure.
I suggest the "Getting Started" guide mention the App Router folder structure by default, and the Pages Router folder structure as an alternative option.
Changes Overview
Mention both the App router folder structure (default option) and the Pages Router folder structure (alternative option) in the Next.js "Getting Started" guide.
Implementation Approach
Modify the markdown file.
Testing Done
npm run lint
. No issues found.npm run dev
). Visit the site: http://localhost:3000/editor/getting-started/install/nextjs . Check the changed content.Verification Steps
npm run dev
)Additional Notes
None
Checklist
Related Issues
None