-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
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
Is it possible to build a site with an AMP site with Next.js that pulls data from a headless CMS? #7492
Comments
|
Thank you @ijjk. On #2, if all of the website's content is served from a CMS (so I would have to use getInitialProps for every page?), but a part of the website is best kept static (e.g. public blog posts) while others are dynamic (e.g. member only content), then are there any workarounds today to implement this in hybrid mode? It seems that the autoExport feature would detect getInitialProps on every page in this case. |
It is not currently supported to have a page auto exported when it has |
I'm going to close this issue as it doesn't follow the issue template. |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
I am looking to build a website with full AMP support, that pulls all of its data from a headless CMS such as Contentful or Prismic. I also recently learned that Next.js announced support for AMP. Is it feasible to build this with Next.js?
Regarding Next.js support for static exports, if a part of the site should not be static (e.g. for member only content, etc), is it possible for me to build this in a hybrid way - i.e. most of the website using next.js static export, and the rest dynamic?
Thank you.
The text was updated successfully, but these errors were encountered: