I still use a PHP script I created many years ago to create sitemaps. I typically need to include a few thousand, up to more than 30k products for the sites I use this on. I use a CRON job to run the script daily (records are typically added each day).
I would like to create these sitemaps in Wappler, but, IMO, we don’t need a new feature to create sitemaps - we need a new feature to write (and read) files.
Google accepts various file formats. Eg it has a link here explaining the format for XML sitemaps. This is the format I use, but others will want to choose different formats, containing different data. Eg in my case, I use two queries - one for a few static pages and one for the many dynamic pages. It would be difficult for Wappler to cater for all the options - and I don’t think it’s necessary. If we can write files with Wappler, we could write sitemaps however we wanted (and of course other files for many other purposes).
There was a thread recently discussing feature requests which had still not been implemented. It was suggested that core functionality was more important, which is a good point. I think being able to read/write files is core functionality. There was a feature request for this made by @s.alpaslan a few years ago. He also created a very useful extension to read/write files - but surely it should part of Wappler.