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
Add support for sitemaps #920
Comments
Thank you @SharadKumar! This is a great idea. We can definitely add this. Some notes for anyone looking into this: We can probably do this many different ways because we wrap the Next.js build, so we can do custom stuff before and after. One possibility is to generate a sitemap from the Next.js manifest file that's output from |
I just came across Blitz last night @flybayer! I think you guys are on to the right philosophy and there is a significant desire and proven demand (RoR) to have a more applicable layer of a framework on top of NextJS type core. NextJS has done a great job in adding similar abstractions over React, yet giving you the core as is. Having said that, despite so much community behind NextJS and their /examples... simple, early stage, and essential things like sitemaps are not trivial. I think thats where the value of Blitz type frameworks come in. If we can have Authentication, Authorization (Hasura does well), DB (Prisma + event-driven Subscriptions similar to Hasura again), and Forms (Redwood type approach perhaps), plus various plugins and essential elements like Sitemaps... all in one framework, aligned to work together. That is a fantastic story for a very wide range of developers to focus on their core business logic and follow DRY principle. Thank you. |
Yes!! That's the dream we are making a reality! 😍 |
Has anyone found a solution for this? Are there any third-party tools or scrips that can accomplish this? |
After the pivot, this will be dependent on the host framework and/or one of its plug-ins (e.g. next-sitemap) |
What do you want and why?
Given the static and dynamic routes, I should be able to generate static sitemap(s).
Possible implementation(s)
#818
Additional context
The text was updated successfully, but these errors were encountered: