Juke AI
Contents
| Content Studio+ feature. Juke AI requires a valid Content Studio+ subscription and the application for each skill that editors will use. |
Juke AI brings a collection of AI-assisted skills to Content Studio. The Content Operator provides a chat interface for working with individual fields, while the AI Translator translates localized content into a layer’s language.
AI-generated content can contain mistakes. Review generated or translated values before saving and publishing them.
Content Operator
The Content Operator requires the Juke AI Content Operator application. It lets editors prompt Juke from the Content Editor and insert generated values into supported fields.
| Juke AI is in early development stages. Errors may occur, and responses will improve over time. See Known issues for more details. |
Interface
Launch the Juke chat interface from the Juke icon in the Content Editor toolbar or beside an active form field.
The icon opens a dialog where you can communicate with Juke.
Field context
To focus Juke on a specific value, select a supported form field. The field is added to the chat context automatically.
Click the x beside the field to remove it from the context.
| The Content Operator currently works with TextLine, TextArea, and HtmlArea fields in the main content type form. |
Mentions
Fields may also be mentioned directly in the chat. Pressing @ inside the chat’s input will list all available fields in the scope of the current context. Select a field from the list to make it a part of your prompt.
| If no context is set, you can mention fields at the root level of the content. |
Sample prompts:
-
Expand the list in
@Article bodyfrom 3 to 5 items and turn it into a numbered list -
Create
@Display Namebased on@Article body
Retry
If the response is unsuitable or the request fails, use the Retry icon to process the instruction again.
Insert
When Juke returns a field value, click the Insert icon beside the value to update the form.
If Juke provides multiple field values, you may use the Insert all icon to insert all values into the form with a single click.
Finally, the Copy to buffer icon will copy the text to your clipboard, allowing you to paste it manually later.
Variants
Juke can provide multiple variants for a field. Use the arrow icons beside the response to review the suggestions, then insert the preferred value.
Sample prompts:
-
Give 3 variants of
@Teaserand@Display Name -
Make 2 suggestions for
@Abstract
General instructions
You may provide a standard prompt for Juke. These instructions may be specified at a project or site level.
For instance, you may want Juke to use a consistent tone of voice or provide other relevant details about the content you are working on. This helps Juke produce more relevant responses every time.
Add the Juke AI Content Operator application to a project or site to provide custom instructions for that scope.
| Working with application settings requires the Owner project role or higher. |
Known issues
Known limitations in the current version:
-
Not optimized for general chat
-
Only works with text-based fields
-
Single ItemSet or OptionSet occurrences may not be available as context
-
Only works with fields in the main content type form
-
Only available in the Content Editor
-
Initial greeting is hardcoded (not AI generated)
-
The AI Translator cannot be invoked from the Content Operator chat
AI Translator
The AI Translator is a Juke skill for translating content during localization. It requires the Juke AI Content Translator application.
When an editor localizes an inherited item or changes an item’s language, the AI Translator detects the change and opens the translation dialog. The dialog identifies the target language and allows the editor to start the translation.
Click btn:[Translate] to translate the detected values. Progress is reported for each value, and successful results are inserted into the open content form. Close the dialog when translation finishes, review the translated content, and then save or publish it through the normal workflow.
The translator handles the display name and supported text inputs, including TextLine, TextArea, and HtmlArea fields. Text in supported X-data and page components can also be translated when their schemas are available. Non-text values and unsupported inputs are left unchanged.
| The Localize action stops the item’s Content inheritance before the Translator opens. Translation does not change name, parent, or sort inheritance. See Content inheritance for details. |
Translation instructions
Expand Translation instructions in the translation dialog to provide guidance for the current item. Instructions can specify terminology, tone, words to avoid, contextual information, or text that must remain unchanged.
Project owners can also configure general instructions on the Translator application at project or site level. These are included when content in that scope is translated, and editors can supplement them for an individual translation.
| Changing project or site application settings requires the Owner project role or higher. |