feat: Add Astro content loader to integration guides #593
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
I've recently published https://github.com/LekoArts/astro-loaders/tree/main/packages/plausible which is a loader for Astro's content layer: https://docs.astro.build/en/guides/content-collections/
You can think of the content layer as a database that gets filled up during build by requests that people make inside their pages. This Plausible content loader allows people to query the Stats API v2 during build and then use the data inside a SSG page, so no API calls in the browser.
The whole
queryinterface is type-safe as I converted the information in the docs to a Typescript schema.