Skip to content
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.

Sign up for GitHub

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

docs/clarify recommendations for using data client #154

Merged
merged 3 commits into from
Jan 27, 2025
Merged

docs/clarify recommendations for using data client #154

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9b71d7c
document prerender callout for data client
thescientist13 Dec 21, 2024
4e511f4
grammar
thescientist13 Jan 25, 2025
f1054be
remove caveate that data client requires prerender flag
thescientist13 Jan 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions src/pages/docs/content-as-data/data-client.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,9 @@ tocHeading: 2

# Data Client

To access your content as data with Greenwood, there are three pre-made APIs you can use, based on your use case. These are isomorphic in that they will consume live data during development, and statically build out each query at build time to its own JSON file that can be fetched client side.
To access your content as data with Greenwood, there are three pre-made APIs you can use, based on your use case. These are isomorphic in that they will consume live data during development, and statically build out each query at build time to its own JSON file that will be fetched client side without needing a. This way, you can serialize and / or hydrate from this data as needed based on your needs.

This way, you can serialize and / or hydrate from this data as needed based on your application's needs.

> These features works best when used for build time templating combining our [**prerender**](/docs/reference/configuration/#prerender) and [**static** optimization](/docs/reference/configuration/#optimization) configurations.
> This feature works best when used for build time templating when combined with the [**static** optimization](/docs/reference/configuration/#optimization) setting.

## Content

Expand Down
Loading