Sanity Create is a great tool for freestyle writing, but when it's time to put your creative output to work, you'll want to move everything into a structured environment where it can enjoy all of the benefits of treating content as data—Sanity Studio!

For example, you might sketch out a blog post in Create, and then connect your work to a new document in Sanity Studio of a specific content type—like a blogPost, with fields like title, excerpt, body, and tags.

A pretty clever mapping agent—from here on lovingly referred to as "the bot"—will go to work in the background identifying which parts of your rich content in Create corresponds to which document fields in your studio and automatically mapping content appropriately. Subject to your overrides, of course.

You also have the option of marking certain parts of your document as context, to make the bot ignore your "notes to self" and other non-content. You can even include little helpful pointers to the bot, like: // slug: my-cool-post or !! title below. The bot will try to infer meaning and decide what is content and what is context. Anything it gets wrong, you can fix!

• In Create, look for the button in the top right corner labeled Studio Link or, on smaller screens, with an icon resembling three boxes arranged in a diagram (a schema!).

• Click the Studio Link button to reveal the Studio Link panel:

• Find your project in the Select project menu. If not automatically selected for you, find your studio deployment and workspace in the appropriate dropdowns. Then, find the document type you want to map your content to.

• With your document type selected, click the button labeled Connect and start mapping -> to proceed.
• The link panel will change to show a "minimap" of the selected content type, with its fields laid out in a tree structure. Fields with a little arrow on their left can be clicked to expand and reveal their values, or drill down deeper into nested fields.

Note also the bottom right status indicator, which shows the mapping agent already making progress. It will keep working in the background, intelligently mapping your content to corresponding fields.

As your content is mapped, you'll see the minimap tree of document fields starting to fill out with content. You might also notice the colors changing as the mapping agent finishes with a field.

As the content is mapped, you'll notice your screen getting progressively more colorful. Content that was automatically mapped to a field will be tinted green, as will the corresponding field in the link panel minimap, while anything the bot has decided is context will get a light gray color.

The yellow-colored field in the screenshot above indicates a field where an editor has actively overruled the suggested mapping and manually linked a bit of content to a field, while text in black or white (depending on whether or not the dark mode is active) indicates content that the mapping agent hasn't yet analyzed.

While the automatic mapping is quite good (really!), you may at times want to manually adjust how your content in Create matches up with your studio schema. The tools you need to make these changes are at your fingertips.

• To map a content block, like a paragraph or an image, to a specific field, click on the item to reveal its context menu, and find the option to Map to field... as shown below.

• Selecting Map to field... will cause the interface to direct focus to the link panel, where you can select an appropriate field to map your selected content to. In the example below, we mapped the first image in the document to the Cover Image > Asset field. User-defined mappings are shown in yellow, instead of green for auto-mapped or gray for context.

• Similarly, if any content is mapped incorrectly, you can unmap it by clicking the Clear mapping button. Note that unless you explicitly reassign it as context, the mapping agent will try to re-map on its next pass until everything has been neatly categorized with a color.

• For more granular control, you can select specific sentences or phrases and map them individually to Studio fields.

• As also demonstrated in the previous screenshot, leaving some contextual hints for the mapping agent can be quite effective. You can read more about this in the section on content mapping tips and tricks.

With these tools, you can control exactly how your content in Sanity Create will be translated into structured data in Sanity Studio. If you haven't already, this would be a good time to link your work to a new document in your studio.

Once you're happy with your mappings, find the button labeled + Link to a new document near the top of the link panel.

Clicking it should result in a visual confirmation of success, and the button label changing to Open linked document. Click it to open the connected studio with your new document selected.

You'll notice that your new document in the studio is in a read-only state while linked to its counterpart in Create.

Any further changes you make in Create will be synced with the studio document automatically, so you can continue refining and expanding your content without worrying about manually transferring anything.

As mentioned, your document will appear as read-only in your studio while linked to Create. You can think of this as the Create document being the source of truth for both versions while the link persists. In order to edit your document in Sanity Studio, you need to unlink it from its source in Create.

When the time comes, click the Unlink button in the bottom right corner to sever the connection and edit your document in the studio.

Clicking Unlink will cause a dialog to appear, informing you of the consequences. Confirm to dismiss it and unlock the document for editing in the studio.

• Procedural discovery! The bot works procedurally on one bit of content at a time, but it can and will make several passes, so it might re-visit and re-evaluate mappings as it moves through your content. You can use this to your advantage by adding content hints above content blocks to quickly make the bot reconsider its choices.

In the example above, the image was originally judged to be part of the blog post body field, but remapped to the coverImage field after some gentle nudging.

• Provide some context! Mark words, lines, or whole blocks as context to make the mapping agent treat your notes as notes that should not be mapped to any field. The bot will also read you context for clues on how to treat content, so feel free to be conversational. // slug: my-cool-slug or [description below] might do wonders.

Make sure your studio has been configured properly to allow Create to connect. This involves configuring and deploying the relevant studio.

Make sure the relevant types or fields aren't configured to be excluded from content mapping. This, too, involves configuring and deploying the studio in question.

Try leaving some contextual clues to help the bot figure out what's what. There are no hard rules when it comes to what the bot will and will not pick up on, but as a general guideline: If it would be hard for a human co-author to catch your context notes, the bot will probably not do great either. Some examples:

• Partial mapping simple values with a simple inline instruction like slug: my-cool-slug
• Using headings as mapping clues for blocks
• Leave a note in plain text. Note: Use this part for description
• ... and if all else fails, manually adjust the mapping to get it just right

Mapping the title is currently not possible, due to vague unspecified technical limitations. We're working on it!