Next.js v13 introduced the new routing model, App Router, which supports server side components and requires a new project structure. This epic is to track the router migration process from page to app.
[!note]
The specifics of epic may be continuously adjusted/updated during the development as needed (e.g., encountering an unexpected errors, add, update, or remove issues)
Page Meta Tags (in progress - this section still needs to be defined)
Currently meta tags are added to pages using components/shared/PageTitle. However, next/head has been replaced by the new built-in SEO Metadata API, and we need to adjust the way we handle metadata in each route.
Refactor the globally shared PageTitle component
Add to app router
Data Fetching (in progress - this section still needs to be defined)
--- in progress: editing ---
Context
Next.js v13 introduced the new routing model, App Router, which supports server side components and requires a new project structure. This epic is to track the router migration process from
pagetoapp.The issues tracked by this epic as follows:
Problem or idea
This section will be filled later.
Page Meta Tags (in progress - this section still needs to be defined)
Currently meta tags are added to pages using
components/shared/PageTitle. However,next/headhas been replaced by the new built-in SEO Metadata API, and we need to adjust the way we handle metadata in each route.PageTitlecomponentapprouterData Fetching (in progress - this section still needs to be defined)
Resource: Migrating Data Fetching Methods, Data Fetching
approuterProject Reorganization (in progress - this section still needs to be defined)
Colocation, Project Organization Features
We'll restructure and organize the project's folders/files.
Solution or next step