Hi I am nearly done with the customization of the Sitemap and have some additional thoughts:
1. We created Sitemaps for Coveo which supports cove:metadata elements but their child elements do not have a ‘coveo’ prefix and that is why being able to commit the prefix when writing out the tags in the Extension would be welcomed (see here: https://docs.coveo.com/en/2656/index-content/index-xml-sitemap-metadata#coveo-specific-custom-metadata) 2. It would be great if the SitemapStorage would be exposed as a service to be able to write our own Sitemap Servlet 3. Sitemap Indexes include any sitemaps in a given sitemap root even if they are not part of the Google Sitemaps. It would be great if sitemaps would be stored in a folder with the name from the Generator and then allow the Servlet to have a list of all names that are part of sitemap indexes 4. I have an idea for a Query Based Generator - we are using queries for Coveo sitemaps I can create a POC but I don’t want to spend my time on it if nobody is interested. Cheers - Andy > On Jun 27, 2024, at 1:54 PM, Andreas Schaefer <[email protected]> wrote: > > Hi > > I am working on an implementation of Apache Sling Sitemaps for a client and > ran into two major issues: > > 1. As of now the Extension Prefix is added to all XML elements but in my case > this is causing an issue > 2. Sitemap Storage is not available outside the package > > For 1. I need to remove the prefix for sub elements and so I had to write a > filter for the sitemap output. > > For 2. I wanted to obtain the Sitemap content from a Servlet of our own but > Sitemap.copySitemap() is not available. > > I would like to have these enhancements: > > 1. Able to call XmlStreamWriter.writeStartElement() and provide an empty > prefix to remove it > 2. Either be able to: > 1. Register a (OutputStream) Filter with the Sitemap Servlet or Storage > to adjust the sitemap output OR > 2. Create a Sitemap Storage Interface containing ‘copySitemap()’ and > register it as a service > > Let me know what you think - Andy
