You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For NextJS SSG all Paths should be known
When integrating AEM with NextJS it would be really beneficial to make use of SSG. For this to work all Paths need to be fetched upfront. Describe the solution you'd like
The best way to achieve this is a similar function to fetchModel but rather fetchPages. A good example how this is solved is from the guys at builder.io. Their builder-client offers this functionality in conjunction with revalidation. Here is an example repo https://stackblitz.com/edit/nextjs-builder?file=pages%2F[[...page]].tsx
Describe alternatives you've considered
Alternatively one could leverage SSR which is fine but always brings unwanted requests to publisher for static content.
The text was updated successfully, but these errors were encountered:
For NextJS SSG all Paths should be known
When integrating AEM with NextJS it would be really beneficial to make use of SSG. For this to work all Paths need to be fetched upfront.
Describe the solution you'd like
The best way to achieve this is a similar function to
fetchModel
but ratherfetchPages
. A good example how this is solved is from the guys at builder.io. Their builder-client offers this functionality in conjunction with revalidation. Here is an example repohttps://stackblitz.com/edit/nextjs-builder?file=pages%2F[[...page]].tsx
Describe alternatives you've considered
Alternatively one could leverage SSR which is fine but always brings unwanted requests to publisher for static content.
The text was updated successfully, but these errors were encountered: