[RSS] Get ready for content collections

[bholmesdev]

Changes

• Expose rssSchema to type-check content collections for RSS feeds
• Deprecate internal import.meta.glob handling and move to a pagesGlobToRssItems() helper. This has a few benefits:
  • Simplifies our items array to accept a single type. Better for JS docs and docs.astro.build.
  • Makes the "only glob src/pages/ entries" requirement more explicit with the function name.
  • Makes handling globs and handling content collections feel equally supported. When import.meta.glob handling was implicit, this felt like the more encouraged solution.
• Refactor internals to use Zod all the way down. This makes error handling on bad config much clearer!

README changes

• Change glob example to a content collections example
• Add rssSchema and pagesGlobToRssItems() reference
• Chore: change import.meta.env.SITE recommendation to new context.site

Testing

• Update testing for new APIs
• Migrate glob testing to separate pagesGlobToRssItems() tests

Docs

• update README
• update docs and tutorial Revamped RSS instructions for content collections docs#2401

[changeset-bot]

🦋 Changeset detected

Latest commit: a3cd5e9

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[bholmesdev]

Updating to keep import.meta.glob() handling around as a deprecated API, and dropping to a non-breaking minor!

[natemoo-re]

Seems like a great refactor! Had a few comments around messaging and maybe found a typo?

[sarah11918]

Quick Docs README review:

I've reviewed the accompanying PR to docs, which I know contains some of the same examples and sections. I'll let you look over those comments, and decide which ones are applicable here. It's OK if this README is more technical than the docs RSS page, which should be more oriented to practical usage.

But, I want to give you a chance to look over that review and
a) see if there's any suggestion there that you'd choose to carry into here.
b) decide whether there's anything you're happy to leave exclusively to docs, and cut from the README. (We favour as little duplication as possible, and keeping the READMES to a minimum, where it makes sense. This document won't often have to stand on its own since readers are far more likely to encounter the docs page, and search only works in docs proper, etc.)

Then, I'll take another last look over this, but I don't see anything that's going to hold this up!

[bholmesdev]

@sarah11918 Made some tweaks based on docs feedback! Seems good-to-go from my end 👍

[sarah11918]

Just re-add that missing "we" and good to go from Docs, @bholmesdev!