On a large static build, the content loaders should read exported records from disk when they are present, so that the build makes no API requests.
An export is a folder of files in the same shape as the site's own /api responses. When one is present at a configured path, each Core Data loader reads its model's records and related lists from those files instead of calling the API. Otherwise it falls back to the API, with the cap on requests in flight from #810. The collections, the record service, the detail pages and the API routes do not change. Only the loaders' source of data does.
Done when a build of a site from a hand-made export completes with zero requests to the API. For a small site the export can be produced by hand from the live API until the export job exists, see performant-software/core-data-cloud#678.
Part of #710.
On a large static build, the content loaders should read exported records from disk when they are present, so that the build makes no API requests.
An export is a folder of files in the same shape as the site's own
/apiresponses. When one is present at a configured path, each Core Data loader reads its model's records and related lists from those files instead of calling the API. Otherwise it falls back to the API, with the cap on requests in flight from #810. The collections, the record service, the detail pages and the API routes do not change. Only the loaders' source of data does.Done when a build of a site from a hand-made export completes with zero requests to the API. For a small site the export can be produced by hand from the live API until the export job exists, see performant-software/core-data-cloud#678.
Part of #710.