-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Revamp Content section 5.0 #9328
Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
… for smaller guides
…ing slug or deleting entirely
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not Matt but I was curious so... 😀 Just two missing imports and an extra space. Otherwise it looks good to me! But again I'm not Matt and I don't know all the technical details.
(By the way, thanks @ascorbic for this feature! I already liked content collections but this one solves my organizational problem ❤️ )
Co-authored-by: Matt Kane <[email protected]> Co-authored-by: Armand Philippot <[email protected]>
OK! If no objections, I'd like to merge this one as a pretty much good enough, acknowledging that for Content Layer API there is still more to document (separately):
|
Co-authored-by: Armand Philippot <[email protected]>
Merging this in! Will do any final polishing on the branch directly! |
New content (& content collections) section for 5.0
This PR:
Re: Content Collections (now, powered by a layer!) for @ascorbic
content-collections.mdx
defining-collections.mdx
working-with-collections.mdx
You can ignore everything else! It's just links etc. around the rest of the site because the original page (and a couple of other related content / markdown pages) have changed. There's also some future proofing for when collections don't have to be in
src/content/
By "review" I mean:
My main goal is to make sure that this guide faithfully and accurately represents both how to get set up and use collections, and the "vision" for collections.
After, outside of this PR:
Those two can be together in the same PR if you want, to get all the API content squared away.
My first priority is to get this PR merged into the beta branch so I can start fixing any conflicts because there were a lot of moving pieces in breaking up the content collections page! The API material can be added later!