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
Is your feature request related to a problem? Please describe.
There is currently no support for pages other than react rendered pages. It would be great if we can utilize serverside and static page rendering for RSS/Atom feeds and sitemaps.
Describe the solution you'd like
It would be great if RSS/Atom feeds and sitemaps can be implemented using getStaticProps and getStaticPaths to fully utilize Next.js capabilities of static page rendering and server side rendering.
Describe alternatives you've considered
Have a separate script to build the rss feeds and sitemaps outside of next.js and statically generate them deploy time. This doesn't work for content dynamically updated after deploy, causing those files to be outdated until the next deploy.
Additional context
Not relevant.
The text was updated successfully, but these errors were encountered:
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.
vercel
locked as resolved and limited conversation to collaborators
Jan 28, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request
Is your feature request related to a problem? Please describe.
There is currently no support for pages other than react rendered pages. It would be great if we can utilize serverside and static page rendering for RSS/Atom feeds and sitemaps.
Describe the solution you'd like
It would be great if RSS/Atom feeds and sitemaps can be implemented using
getStaticProps
andgetStaticPaths
to fully utilize Next.js capabilities of static page rendering and server side rendering.Describe alternatives you've considered
Have a separate script to build the rss feeds and sitemaps outside of next.js and statically generate them deploy time. This doesn't work for content dynamically updated after deploy, causing those files to be outdated until the next deploy.
Additional context
Not relevant.
The text was updated successfully, but these errors were encountered: