Sanity and Transglot, keep structured content in sync.
Choose Sanity in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.
Choose Sanity in the project’s CMS settings. Add a Sanity API token, plus your project id and dataset.
connect
02
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads documents, per type, in one dataset. Map the source and target locales to your project.
map
03
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
審核
04
Publish to Sanity
Use Publish to CMS to send the translated values to the mapped target locales. Check the publish result in the project’s CMS settings.
deliver
Publish translated values back to the target locales you map in Sanity.
傳輸內容
您可以翻譯並交付的內容。
文件透過 GROQ 查詢從 Content Lake 匯出。本地化欄位遵循 localeString 和 localeText 慣例,因此發布時僅修補目標語言鍵值。Portable Text 主體以每個欄位一個可翻譯字串的形式來回傳輸,並重建為實際區塊。
您可以翻譯並交付的內容。
表面
預期結果
來源與範圍
文件,按類型,在單一數據集中
翻譯輸出
Publish translated values back to the target locales you map in Sanity.
注意事項
Only the content types and fields you select are synced. Source content stays in its source locale.