✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	665dfbb
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/68cc234b6348fc0008a07e0a
😎 Deploy Preview	https://deploy-preview-12155--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.

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Tracked Files

Will note that on Talking and Doc'ing last week, we briefly discussed where on the page this information makes sense to add because to this is does not fall under any of the existing 3 topics (Defining the collection, querying the collection generating routes from the collection) but is also not really "on the same hierarchy level" as those broad topics.

This is related to the file loader, but instead something (more advanced?) that you do with a collection entry, and in fact, maybe is in some way related to the <h3> "defining a custom ID" in that sense.

I think @delucis will be overseeing this PR, alongside and dependent upon his feature fix PR. So I wouldn't treat this as "ready to review" since it's not even correct content yet. It's just a cut and paste placeholder from the way collections worked pre-v5 right now (e.g. there is no type for collections anymore), but should be considered more like feature documentation to accompany the incoming PR.

We'll need to document how it's supposed to work with the content layer API now powering collections: does this only affect the file() loader loading a single JSON file, or also glob() if there are multiple JSON files for each entry? (The example here looks like the file is a single author, not an "authors" file? If we mean for this to be strictly a "one JSON file collection" then I think we might want the code example to show multiple author entries in the single file, and not be named after one author?) Does this only work for local JSON entries? (not remote JSON files that might be using a custom loader instead of our built-in loaders, but still loading and parsing JSON?)

There were a lot of things that were unclear about how this worked for new content collections when they were released in v5, which is why this section was removed at that time! It wasn't actually deleted by accident, but we didn't have confirmation for how this content needed to be updated at the time, so we could not include it. We instead went with the assumption that if this is still a thing, it will make itself an issue at some future date. THE FUTURE IS NOW! 😄

does this only affect the file() loader loading a single JSON file, or also glob() if there are multiple JSON files for each entry?

Does affect both :)

@delucis I think your core PR got merged, and I remember you wanted to look into this PR too. Any updates?

Update the PR with a rework of the docs!

Since this is schema related, we could consider a short line (or tip?) somewhere within /en/guides/content-collections/#defining-the-collection-schema with an inline link about using [JSON schemas for your collections](#collection-json-schemas) in your editor.

Well the one thing here is that this is potentially a bit confusing: these schemas are NOT exactly the same thing a those schemas. They’re derived from them, but I was wondering if there could be some confusion about that, i.e. a JSON Schema is a specific file format used for validating JSON files, vs your collection schema which is a Zod schema you write.

Well the one thing here is that this is potentially a bit confusing:

None of this feels particularly ergonomic 😄 Happy just to have it documented, and we'll look at a larger pass at this page (e.g. we've talked about splitting up the two loaders into individual sections) to correspond to v6!