Guide Translations

Overview

Walnut’s Guide Translations feature helps you create localized guided demo experiences by supporting multiple language versions of your guide content inside a single template.

This makes it easier to deliver demos to global audiences without rebuilding the same experience from scratch for each language.

You can either use Walnut’s built-in translation workflow to generate translated guide content automatically, or manage translations manually through CSV export and import.

In This Guide

This guide covers the main ways to create translated guide experiences in Walnut and what viewers can expect once those translations are live.

See It in Action

To see Guide Translations in action, explore this Walnut demo.

Before You Start

Before you begin, decide how you want to manage translations for your guide content.

• Use Walnut’s built-in translation workflow if you want a faster way to generate translated guide content.
• Use custom translations via CSV if you want more control over wording, terminology, tone, or localization quality.

How It Works

Walnut supports two main translation workflows for guides:

• Translation generated through Walnut’s translation workflow
• Custom translation managed through CSV export and import

Both approaches let you create language-specific versions of guide content within the same demo experience.

Create Translations with Walnut’s Translation Workflow

This workflow is the fastest way to create translated guide content directly inside the Editor.

How to Create Guide Translations

1. Open the relevant template or demo and go to the Guides panel.
2. Click the Globe icon in the Guides menu.
3. Select one or more languages from the multi-select dropdown.
4. Walnut generates translated versions of the guide content for the selected languages.

This workflow is especially useful when you want to localize guides quickly across a small set of supported languages.

Create Custom Translations with CSV

If you want more control over the final wording, you can manage guide translations outside Walnut and then import them back in.

How to Create Custom Guide Translations

1. Export the guide content to a CSV file.
2. Open the CSV and update the translation fields with your custom language versions.
3. Import the updated CSV back into Walnut.

After import, Walnut applies the translated content to the relevant guides.

If the file contains formatting or validation issues, Walnut reports the errors and provides a CSV output you can review and correct before reimporting.

How Translations Work During Demo Playback

Once translations are added, Walnut can present the demo in the most appropriate available language for the viewer.

What Happens When a Viewer Opens the Demo

1. When the demo opens, Walnut detects the viewer’s browser locale and attempts to present the guide content in the matching available language.
2. The demo creator can choose whether viewers are allowed to switch languages during playback.
3. If language switching is enabled, viewers can change the guide language from the demo toolbar.

Important to Note

• Walnut uses a translation service to generate translated guide content in the built-in translation workflow.
• The Basic package allows up to three languages per template.
• The Advanced Translations package expands support to many more languages per template.
• If you need broader language support, reach out to your CSM for packaging details.

Summary

Guide Translations help you turn one guided demo into a more scalable global experience.

If speed matters most, Walnut’s built-in translation workflow is the fastest path. If accuracy, tone, or terminology matter more, the CSV workflow gives you tighter control.

Either way, the feature makes it easier to support multilingual audiences without rebuilding the same demo over and over.