-
Notifications
You must be signed in to change notification settings - Fork 129
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
Create sitemap / RSS #168
Comments
This is mainly for public projects so moving to future (but it would be nice to have for GA if possible). |
I've added RSS to the issue; we could make two issues when the time comes. RSS won't be useful for many projects, but some which regularly add pages will want it and it feels it's table stakes. |
#843 removed client-side access to the search index. It was the closest thing we had to a sitemap.xml/rss list of contents, but now only For the game in question I can replace this with an ad hoc data loader, but it feels like it belongs to this more generic question. |
I think we should transpile Then you could say Also this would allow you to register additional files to download. Edit: This is now done in #843. |
I wrote a postbuild script to add a simple sitemap to pangea, with the proper headers that reference it. https://github.com/Fil/pangea/blob/e179717808c66526d5e17a933245f7fe6b91851b/package.json#L7-L8 It would still be nice to have an easier method to push static/public files, but I think we don't have to have native support for RSS or sitemaps (a helper would be nice, but it can all be done in userland); this issue can now be folded under #169. |
For more discussion, see #1199 (reply in thread) |
Like vitepress, build an items array from the list of pages, with a
transformItems
hook that allows the user to modify the array before passing it to https://www.npmjs.com/package/sitemap (with options).Ref. https://vitepress.dev/guide/sitemap-generation
It seems sensible to adopt the same approach here.
To build a sitemap, we need to know the full URL (including domain name and subdirectory, ref. #42).
The text was updated successfully, but these errors were encountered: