-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
feat: add Content Layer loader #11334
Conversation
|
20bee9a
to
1f0affc
Compare
1f0affc
to
14330f7
Compare
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.
This PR is blocked because it contains a minor
changeset. A reviewer will merge this at the next release if approved.
This comment was marked as outdated.
This comment was marked as outdated.
839838e
to
3fcdc59
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Snapshots have been released for the following packages:
Publish Log
Build Log
|
881f3c7
to
e93ad3e
Compare
e93ad3e
to
6bb89bc
Compare
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.
Let's get the party started!
This is the work-in-progress branch implementing the Content Layer RFC.
Testing
There is an example site in the content-layer fixture, which shows the use of a custom loader and the
file()
loader. Currently the API for end user looks like this:The
blog
collection shows a custom loader. These can be defined like this:The API is currently defined like this:
Currently there is no support for loading md or mdx files using
glob()
, or for defining renderers.Querying is currently limited to
getCollection
andgetDataEntryById
, with no filter options.To test this, install the experimental version with
npm install astro@experimental--content-layer
Docs