Server-side generation should not be closely tied to the sitemap

[rmtmckenzie]

What is it about?

No response

What's the motivation for this proposal?

Problems you are trying to solve:

• My site has a few pages that cannot be statically generated, but should be included in the sitemap.

Goals you are trying to achieve:

• Allow for overriding the sitemap generation

Any other context or information you want to share:

I have to have some server-side logic for pages that are otherwise fairly static. This means that they cannot be statically generated and are therefore excluded from the sitemap. I do want them to be in the sitemap.xml. and there doesn't seem to be any way other than maintaining the sitemap myself.

---

Proposed Solution / Feature

What do you propose?

It would be wonderful if the sitemap generation could be decoupled from the static site generation, or at least be able to be overridden. This would also be quite useful the otherway - you might want a page to be statically generated but not included in the sitemap.

I'm using cloudflare workers, but I think this is applies generally to all vite-based adapters.

Code examples

      {
        ssg: {
          include: ["/*"],
          exclude: ["/"],
          sitemapInclude: ["/*"],
          sitemapExclude: [],
        }
      }
      
      or 
      
      {
        ssg: {
          include: ["/*"],
          exclude: ["/"],
          sitemap: {
            include: ["/*"],
            exclude: [],
          }
        }
      }

---

Links / References

No response

[wmertens]

Is the dynamic sitemap https://qwik.dev/docs/advanced/sitemaps/ enough to cover your usecase?

[rmtmckenzie]

Oh whoops, totally missed that in the docs - I really don't know how now you've pointed it out. That definitely does what I need. Thanks!

[rmtmckenzie]

It's a bit more work than what I proposed but I can see how the flexibility would be very advantageous.