Translations

Any article you write in Asky can become a set of language versions that live alongside the original. Asky translates the whole piece, not just the body: the title, the meta description, your CMS fields, and the internal links, so each language arrives as a finished, publishable draft rather than a rough machine translation.

Accessing Translations

Go to Content Library in the sidebar, open a draft, and click Translations in the editor toolbar.

The menu lists the original and every language you have made from it. New translation starts another one. Any draft with a title and a body can be translated, and it does not need to be published first.

A finished translation shows no progress label. Once you send it to your CMS the row shows its publishing status instead, using the same statuses as the Content Library.

Creating a Translation

What Gets Translated

Everything is translated together as one document rather than field by field, so terminology stays consistent between the headline, the body, and your CMS fields. The result then goes through a second editing pass that reads it against the original and fixes what machine translation usually gets wrong: idioms taken literally, phrasing that is correct but not what a native speaker would write, and link text that reads awkwardly in the new language. Your brand name is carried through as context, so product and brand names are not translated into something else.

Internal Links

An article that links to your own pages should link to the right language version of those pages. Asky finds the internal links in the draft, looks for the translated version of each one on your site, and shows you the whole list before anything runs.

• Edit any target URL to point somewhere else
• Skip a row to leave that link exactly as it is
• Reset an edited row back to the suggested URL

Links Asky cannot find a translated version for are flagged with a warning and keep their original URL. If the list is empty, or most rows are unresolved, run a scan from Pages so Asky has an up-to-date picture of your site.

External links are never rewritten, and link rewriting applies to the article body rather than to custom CMS fields.

Editing a Translation

A finished translation is an ordinary draft. Open it from the Translations menu and edit the title, meta description, slug, body, and CMS fields exactly as you would the original. Content edits are independent: changing the original afterwards does not change a translation, and the other way round.

The one setting that is shared is the CMS collection. Changing it on any language applies it to every language in the family, and Asky warns you before it does.

Translations always branch off the original article, so a translation cannot itself be translated. Start every language from the source draft.

Publishing Translations

When a draft has translations, the publish button opens Review & publish translations instead of the single-draft flow. Every language gets a row, and every ready row defaults to Save as draft. Switch a row to Publish now, or Re-publish if it is already live, or Skip, then confirm. Rows that are still translating cannot be published until they finish, and rows that failed have to be retried first.

Webflow

Webflow keeps every language as a locale variant of one CMS item, so Asky maps each language onto one of your site locales. The match is usually automatic. Where it is not, pick the locale from the dropdown on that row and Asky remembers the choice for next time. Use Refresh locales after adding a locale in Webflow.

Two situations need a decision from you:

• The language matches no Webflow locale. The row publishes as its own separate CMS item, flagged as unlinked. Add the locale in Webflow, click Refresh locales, and publish again if you want the languages joined.
• The locale exists in Webflow but not on the item Asky already published. Webflow’s API cannot add a locale to an item that already exists, so open that item in the Webflow Designer, add the locale there, and publish again. Choosing Publish unlinked on the row is the alternative: it publishes as a separate item instead.

See Webflow for connecting and configuring the integration.

WordPress

WordPress.com and self-hosted WordPress have no native link between language versions, so each language publishes as a separate post and Asky says so in the dialog. Use a WordPress multilingual plugin if you need the posts joined.

Sanity

Sanity keeps each language as a separate document and links them for you, so Studio’s language switcher works. See Sanity for the details, including what happens on projects that use field-level localization instead.

When a Translation Fails

A failed translation stays in the Translations menu, marked Failed, with the reason on hover. Click Retry there, or Retry translation on the draft itself. If a translation is still running after about ten minutes, a Restart translation button appears on the draft.

Deleting Translations

Deleting a translation removes only that language, and frees it so you can translate the article into it again.

Deleting the original does not delete its translations. They stay in your library as separate articles, unless you tick Delete all language versions in the delete dialog and type DELETE to confirm.

Deleting never removes anything from your CMS. Anything already published stays live, and a fresh translation of the same language publishes as a new item rather than replacing the old one.

Limitations

Next Steps

• Write the article you want to translate in Creating Content
• Set your default tone and spelling in Brand Profile
• Connect a CMS: Webflow, WordPress or Sanity