Overview
Walnut empowers global teams to create, localize, and scale interactive demos in their primary language — without duplicating work or rebuilding assets.
No matter where your teams operate globally, Walnut enables them to:
- Create demos in their native language
- Translate guide content for regional audiences
- Localize captured UI text
- Generate narration in any language
- Maintain a single scalable demo framework
Global teams perform best when they can create, collaborate, and present in the language they’re most fluent in. Walnut supports this end-to-end with Guides Translation, Story Capture narration, template language controls, and AI Mode — which accepts prompts in any language and generates content in that same language.
🌏 The result: Every region can build locally, refine naturally, and scale globally from a single template foundation.
In This Guide:
- Global Teams Demo Creation Workflow (Recommended)
- Build in Your Primary Language
- Set a Source Language (Guide Builder Language)
- Guides Translation (Narrative Localization)
- Story Capture (Multilingual Narration)
- Template Default Language Controls
- AI Mode (UI + Narrative Localization)
- Best Practices for Global Teams
Global Teams Demo Creation Workflow (Recommended)
Use this workflow when regional teams or partners need to create demo content in their preferred language while maintaining governance and consistency across the organization.
- Start with Story Capture. Record narration in your primary language while clicking through your product. Walnut uses your audio narration to automatically generate a structured guided narrative — creating a strong first draft of your demo flow.
- Create or refine guide content. Edit the generated steps, write new ones from scratch, or use AI-assisted guide creation to build structured step content.
- Use AI Mode. Refine, standardize, or translate guide and UI content. AI Mode accepts prompts in any language and generates output in that same language, allowing regional teams to work naturally.
- Choose a Source Language. This defines the builder language of the template — the language your team authors in — and becomes the foundation for all Guides Translation.
- Enable Guides Translation. Translations are generated from the selected Source Language, ensuring terminology stays consistent across regions without duplicating demos.
- Set a Default Language. This determines which language viewers see first when opening the demo.
⚠️ Important Distinction:
Source Language = Builder language (internal creation)
Default Language = Viewer language (external delivery)
1. Build in Your Primary Language
Walnut templates can be created in any spoken or written language. Teams are not required to build in English first.
This means:
- Dutch teams can write guides in Dutch
- French teams can build in French
- Nordic partners can create localized demo flows
- Product marketing can define regional messaging from the start
You can also use AI Mode to build and refine content in your team’s preferred language. AI Mode accepts prompts in any language and generates output in that same language — making it easy for regional teams to draft, edit, and standardize content naturally.
To ensure long-term consistency, you can set a Source Language inside your template. This is the language your team builds in — the language used for guide steps, titles, and annotations — and it becomes the foundation from which all Guides Translation are generated.
How to Set a Source Language (Guide Builder Language)
You can set a Source Language inside your template. This is the language your team builds in — the language used for guide steps, titles, and annotations — and it becomes the foundation from which all Guides Translation are generated.
Once the Source Language is set:
- All Guides Translation will be generated from the selected source language.
- Terminology stays aligned across regions.
- Regional teams can confidently build in their preferred language first, then scale outward.
How to Set Your Source Language:
- Open your Template.
- Navigate to the Guides panel.
-
Click the globe icon to open Guides Translation.
- In the Source language dropdown, select the language your team is authoring in (e.g., French, Dutch, Spanish).
⚠️ Important:
Source Language = Builder language (internal creation).
All translations are generated from this foundation to help keep terminology consistent across regions.
2. Guides Translation (Narrative Layer Localization)
Guides Translation let you dynamically translate guided steps and annotation copy without cloning demos or maintaining multiple versions.
How It Works:
- Create your guided demo once.
- Enable up to three languages (included in the standard language package).
- Add unlimited languages with the Unlimited Languages add-on.
- Viewers can toggle languages directly in the demo player.
- Walnut can auto-detect browser language for seamless localization.
This localizes the narrative layer of your demo — including guide steps, annotations, and instructional content.
💡 Best Practice: Use Guides Translation to scale one approved experience across markets without rebuilding demos for each region.
🌍 Accessibility & Localization: Offering demos in a viewer’s preferred language improves accessibility, comprehension, and engagement — especially for embedded demos on global marketing pages. Localized experiences can also reduce drop-off and increase completion.
👉 Learn more in Win With Embedded Demos: Drive Engagement, Accessibility, and Discoverability.
3. Story Capture (Multilingual Narration)
Story Capture allows teams to record spoken narration while capturing screens — in any language. Walnut can use that narration to generate a strong first draft of a guided demo narrative.
Why It’s Powerful for Global Teams:
- Record narration in your primary language.
- Automatically generate guided steps from spoken instructions.
- Create first-draft demo flows quickly (especially for new regions or new team members).
- Improve consistency across teams by standardizing structure and step flow.
Story Capture supports multilingual voice input, allowing regional teams to build confidently in their own language while maintaining one scalable demo framework.
4. Template Default Language Controls
The Default Language controls which language viewers see first when they open the demo.
This setting affects the audience experience, not how your team builds the template.
- Ensure the correct language displays on region-specific pages
- Align demo language with marketing site language
- Support partner distribution across multiple countries
Source Language = Builder language (internal creation)
Default Language = Viewer language (external delivery)
5. AI Mode (UI + Narrative Localization)
AI Mode is Walnut’s built-in assistant for refining, translating, and standardizing demo content. It accepts prompts in any language and can generate outputs in that same language — so every region can work naturally in their primary language.
AI Mode Works in Any Language:
- Prompt AI Mode in French, Dutch, Swedish, or any language your team uses.
- Generate refined outputs in the same language (or translate into a target language).
- Standardize tone and terminology across global teams.
Localizing HTML Captures (UI Layer)
AI Mode can translate and refine text content inside HTML captures — not just guide annotations. This allows you to produce localized demos without recapturing your product in multiple languages.
This is especially useful when:
- You want localized UI text for partners and regional sales teams
- Your product localization is still in progress, but your go-to-market needs localized demos now
- You need market-specific terminology (even when the underlying UI is shared)
Best Practice: Capture once, localize many times.
💡 Combine AI Mode UI localization (captured text) with Guides Translation (annotation narrative) for a fully localized end-to-end experience.
Refining Annotation Content (Narrative Layer)
AI Mode can improve annotation quality across languages — so guide steps remain clear, consistent, and aligned to your brand voice across every region.
- Shorten long steps
- Rewrite for clarity and action-orientation
- Adjust tone for enterprise vs. SMB audiences
- Simplify for non-native speakers
- Standardize terminology across regions
- Generate region-specific messaging that local teams can finalize
Best Practices for Global Teams
- Assign a “language owner” per region: one person responsible for final review and terminology consistency.
- Scale from core templates: localize with translations instead of duplicating templates and demos.
- Organize assets with folders: Create a clear structure by product line, region, or use case to prevent duplication and maintain visibility across teams. As your library grows, structured organization becomes essential for global scale. 👉 See the Scaling Your Walnut Workspace: Governance, Organization & Content Best Practices guide for a recommended frameworks.
FAQs
Do we need separate demos for each language?
- Not usually. Most teams keep one core demo and localize it with Guides Translation plus default language controls. If you need localized UI text too, use AI Mode to localize HTML capture text.
How do we keep language versions consistent across teams?
- Keep steps short, use a simple glossary, and use AI Mode to standardize phrasing. Then have a local language owner validate nuance and brand voice.