@sanity/client 5.4.3-dev.4 → 6.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -65,7 +65,7 @@ export async function updateDocumentTitle(_id, title) {
65
65
  - [UMD](#umd)
66
66
  - [Specifying API version](#specifying-api-version)
67
67
  - [Performing queries](#performing-queries)
68
- - [Get started with Content Source Maps](#get-started-with-content-source-maps)
68
+ - [Fetching Content Source Maps](#fetching-content-source-maps)
69
69
  - [Listening to queries](#listening-to-queries)
70
70
  - [Fetch a single document](#fetch-a-single-document)
71
71
  - [Fetch multiple documents in one go](#fetch-multiple-documents-in-one-go)
@@ -405,15 +405,17 @@ client.fetch(query, params).then((bikes) => {
405
405
 
406
406
  Perform a query using the given parameters (if any).
407
407
 
408
- ### Get started with Content Source Maps
408
+ ### Fetching Content Source Maps
409
+
410
+ Content Source Maps annotate fragments in your query results with metadata about its origin: the field, document, and dataset it originated from.
409
411
 
410
412
  > **Note**
411
413
  >
412
414
  > [Content Source Maps][content-source-maps-intro] are available [as an API][content-source-maps] for select [Sanity enterprise customers][enterprise-cta]. [Contact our sales team for more information.][sales-cta]
413
415
 
414
- [Visual editing][visual-editing] is available in [`@sanity/preview-kit/client`][preview-kit-client]. It offers both a turn-key solution and a flexible API for custom experiences.
416
+ A high level API using Content Source Maps for [Visual editing][visual-editing] is also available in [`@sanity/preview-kit/client`][preview-kit-client]. It offers both a turn-key solution and a flexible API for custom experiences.
415
417
 
416
- This guide is for developers who want to build custom use cases beyond, or in addition to, [visual editing][visual-editing]. Read the [Content Source Maps introduction][content-source-maps-intro] before diving in, and keep the [Content Source Maps reference][content-source-maps] handy.
418
+ Read the [Content Source Maps introduction][content-source-maps-intro] before diving in, and keep the [Content Source Maps reference][content-source-maps] handy.
417
419
 
418
420
  Enabling Content Source Maps is a two-step process:
419
421