This is one thing the old site never had, a proper, always up-to-date sitemap. It just wasn't feasible, but since we now have an actual database of items, it becomes a simple task to generate and automatically maintain a sitemap.
Basically we need to output an xml file with the appropriate content, so there's nothing ground breaking in this. Pocketbase doesn't offer this feature, so we'll have to implement it. The existing go based sitemap generators are either abandoned or don't have the necessary features available. So We need to roll our own sitemap generator, that supports both page and image links, but has to be extensible later on.
The generated sitemap should exist on disk or in a database for quick access
The generation should happen via cron in off hours as it's heavy operation
The generated file should be served through the /sitemap.xml url
This is one thing the old site never had, a proper, always up-to-date sitemap. It just wasn't feasible, but since we now have an actual database of items, it becomes a simple task to generate and automatically maintain a sitemap.
Info about sitemaps: https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview
Basically we need to output an xml file with the appropriate content, so there's nothing ground breaking in this. Pocketbase doesn't offer this feature, so we'll have to implement it. The existing go based sitemap generators are either abandoned or don't have the necessary features available. So We need to roll our own sitemap generator, that supports both page and image links, but has to be extensible later on.
/sitemap.xmlurl