Sanity Translate Service is a robust document translation tool designed to integrate seamlessly with Sanity.io's content management platform. This Go application serves as a middleware, facilitating the translation of documents stored within Sanity using the DeepL API for language processing.
- Document Translation: Translates documents from one language to another using DeepL API, while preserving formatting.
- Field-Specific Translation: Offers the flexibility to translate individual fields within a document.
- Sanity Integration: Directly interfaces with Sanity's data mutation and query APIs to fetch and update documents.
- CORS Support: Configurable CORS policy for cross-origin resource sharing.
- Input Flexibility: Supports translation of specified document elements or fields.
- API Endpoint: Exposes a POST endpoint for translating documents via HTTP requests.
SanityTranslator is designed to operate seamlessly with Sanity V3 and is fully compatible with the latest version of the Sanity.io Internationalization Plugin. This ensures that the tool leverages the most up-to-date features for content translation and internationalization offered by Sanity.
Please be aware that using SanityTranslator to translate a document will overwrite any previously created document with the same identifier. Exercise caution and ensure that you have appropriate backups or versioning in place before you translate and overwrite existing content.
- Go (version 1.15+ recommended)
- Sanity.io project with an associated project ID, version, and token
- DeepL API account with an authorization token
- Clone the repository to your local machine.
- Set your Sanity and DeepL API credentials as environment variables:
export SANITY_PROJECT_ID="your_sanity_project_id"
export SANITY_VERSION="your_sanity_version"
export SANITY_TOKEN="your_sanity_token"
export DEEPL_TOKEN="your_deepl_auth_key"- Navigate to the project directory and build the application:
go build- Run the application:
./SanityTranslatorSend a POST request to the /sanity_translate_document endpoint with the JSON payload specifying the document slugs and the target language.
For example:
{
"FromLang": "it",
"FromSlug": "/it/this-is-the-slug-from",
"ToLang": "de",
"ToSlug": "/de/this-is-the-slug-to",
"InputElements": [
"title",
"subtitle",
"intro",
"metadata.metaKeyword",
"metadata.metaDescription",
"metadata.metaTitle",
"text.000.title",
"text.000.intro ",
"text.000.text",
"text.000.children.000.text",
]
}Here how a working CURL request look like:
curl --location 'localhost:8001/sanity_translate_document' \
--header 'Content-Type: application/json' \
--data '{
"FromLang": "it",
"FromSlug": "/it/this-is-the-slug-from",
"ToLang": "de",
"ToSlug": "/de/this-is-the-slug-to",
"InputElements": [
"title",
"intro",
"metadata.metaKeyword",
"metadata.metaDescription",
"metadata.metaTitle",
"text.000.title",
"text.000.intro ",
"text.000.children.000.text"
]
}'The service will fetch the specified document from Sanity, translate the designated elements, and create a new translated document in the target language.
This endpoint allows for targeted updates within documents, enhancing flexibility and efficiency.
Send a POST request to the /sanity_translate_field endpoint with the JSON payload specifying the document slugs and the target language.
For example:
{
"FromLang": "en",
"FromSlug": "/en/this-is-the-slug-from",
"ToSlugs": [
"/it/this-is-the-slug-to-1",
"/de/this-is-the-slug-to-2",
"/fr/this-is-the-slug-to-3"
],
"MappingFields": [
{
"SanityPath": "text[0].intro"
},
{
"SanityPath": "text[1].intro"
},
{
"SanityPath": "text[2].intro"
},
{
"SanityPath": "text[3].intro"
}
]
}Here how a working CURL request look like:
curl --location 'localhost:8001/sanity_translate_field' \
--header 'Content-Type: application/json' \
--data '{
"FromLang": "en",
"FromSlug": "/en/this-is-the-slug-from",
"ToSlugs": [
"/it/this-is-the-slug-to-1",
"/de/this-is-the-slug-to-2",
"/fr/this-is-the-slug-to-3"
],
"MappingFields": [
{
"SanityPath": "text[0].intro"
},
{
"SanityPath": "text[1].intro"
},
{
"SanityPath": "text[2].intro"
},
{
"SanityPath": "text[3].intro"
}
]
}'To properly test the Sanity Translate Service, you need to have a test document set up in your Sanity.io project. The document should conform to a specific schema expected by the tool. Here is an example of a document schema named test that is necessary for the testing process:
import { RobotIcon } from '@sanity/icons'
export default {
name: 'test',
type: 'document',
title: 'Test',
icon: RobotIcon,
preview: {
select: {
slug: 'slug'
},
prepare(selection) {
const {slug} = selection
return {
title: slug["current"]
}
}
},
fields: [
{
name: 'slug',
type: 'slug',
title: 'Slug'
},
{
name: 'title',
type: 'string',
title: 'Title'
},
{
name: 'intro',
type: 'string',
title: 'Intro'
},
{
title: 'Test Array',
name: 'testArray',
type: 'array',
of: [
{type: 'string'}
]
},
{
title: 'Portable Test',
name: 'portableTest',
type: 'array',
of: [
{type: 'block'},
]
},
{
name: 'language',
type: 'string',
readOnly: true,
hidden: true
}
]
}Ensure you have created a document within your Sanity.io project using this schema before running tests. The document should contain at least the slug, title, and intro fields populated with data, as the translation service will attempt to access and modify these fields.
These tests have been developed to work within my Sanity Studio, so in case you want to run them, or you modify the tests according with your document ids, or you suggest a way to abstract the test logic through a proper pull request.
To contribute to the development of Sanity Translate Service, you can:
- Fork the repository.
- Create a new feature branch.
- Commit your changes.
- Submit a pull request.
This project is licensed under the MIT License - see the LICENSE file for details.
- Write tests for translator_field.go