Not sure why the RSS feed endpoint was deleted in commit 406ff44 but it broke my (and presumably others) feed readers. This commit re-adds it back. If it was removed on purpose, then the meta tag in layout.tsx should also be removed or otherwise adjusted so that feed readers for new users don't find and try to add broken links. The /feed.xml endpoint is (or should be) statically built, and so any future accesses once a site build has gone live should be instant and and pulled from a cache rather than be recomputed.
I noticed that localization attempts were going on. While I agree that it should happen, unless the Release Notes object also get localized, the /feed.xml endpoint should probably remain just in English, at least for the immediate future. Since the endpoint is a fake, generated XML file, it could take a query string in the future, or could be put under a [locale] directory with the original /feed.xml redirecting to /en/feed.xml or whatever is desired.
Not sure why the RSS feed endpoint was deleted in commit 406ff44 but it broke my (and presumably others) feed readers. This commit re-adds it back. If it was removed on purpose, then the meta tag in layout.tsx should also be removed or otherwise adjusted so that feed readers for new users don't find and try to add broken links. The
/feed.xml
endpoint is (or should be) statically built, and so any future accesses once a site build has gone live should be instant and and pulled from a cache rather than be recomputed.I noticed that localization attempts were going on. While I agree that it should happen, unless the Release Notes object also get localized, the
/feed.xml
endpoint should probably remain just in English, at least for the immediate future. Since the endpoint is a fake, generated XML file, it could take a query string in the future, or could be put under a[locale]
directory with the original/feed.xml
redirecting to/en/feed.xml
or whatever is desired.This commit re-fixes #22