Add docs for experimental live collections

[ascorbic]

Description (required)

Adds docs for live collections. It's not certain which release this will be in, so I've not included the since value and won't add this to a milestone just yet

Related issues & labels (optional)

• Closes #
• Suggested label:

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	4a7b8e4
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/6853eb66f61b6c000870353b
😎 Deploy Preview	https://deploy-preview-11782--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/reference/experimental-flags/live-content-collections.mdx	Localization added, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[sarah11918]

Looking really great, Matt! 🙌

Just left some broad stroke comments after reading through for a first pass with some comments!

[sarah11918]

Just noting here that we want to make all code blocks copy/paste and it's working code. We try not to put multiple options in a code sample that would make it not run as-is.

There's a lot going on in this whole snippet. Can ALL of it happen together in a working function? e.g. "throw an Astro error or handle it yourself" If these can't be done together, then instead one of them could be commented out entirely e.g.

// Or handle errors yourself
// return Astro.redirect('/500');

And, the same goes for e.g. defining entries in multiple places. I know it's convenient to throw everything in one block, but I think we might need another pattern here if this, as a whole, isn't functioning code.

[sarah11918]

2nd pass! This is looking great and probably doesn't require anything more than a Yan review after this! Would be perfectly happy with that state! 🙌

[sarah11918]

Will note on Talking and Doc'ing that someone suggested documenting the LiveLoader type would be helpful! Would anyone like to add this?

[yanthomasdev]

Great work! A few nits from me 🙌

[yanthomasdev]

Suggested change

	// This could be a network error, not found error, or Zod validation error
	// This could be a network error, not found error or Zod validation error

[ascorbic]

I've had it hammered into me to use Oxford comma for Astro stuff, so isn't this right as it stands? I think I'll reword this anyway though

[sarah11918]

Yes, I'm not sure why Yan would remove an Oxford comma. Chalk it up to exam week brain, unless there's something I'm missing? 😄

So fine as is, I think!

[ascorbic]

It's probably the thing I find hardest to remember when writing Astro stuff! Even harder than using US spelling, because at least that's obvious.