We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As per the Next.js documentation, it's recommend to use the app router as opposed to the pages.
As per my conversation with @wicksipedia we should start to look at moving from the App Router to the Pages Router.
Note we can have both routers on a project at any given time, next will scan for the pages router first then the app router.
So we want to implement this in stages, starting with the least complex routes then moving to the more complex
Tasks
Figure: current app router layout
The text was updated successfully, but these errors were encountered:
@joshbermanssw please speak to @JackDevAU
Sorry, something went wrong.
joshbermanssw
No branches or pull requests
Pain
As per the Next.js documentation, it's recommend to use the app router as opposed to the pages.
Tasks
As per my conversation with @wicksipedia we should start to look at moving from the App Router to the Pages Router.
Note we can have both routers on a project at any given time, next will scan for the pages router first then the app router.
So we want to implement this in stages, starting with the least complex routes then moving to the more complex
Tasks
Figure: current app router layout
The text was updated successfully, but these errors were encountered: