Overview
Keeping your demo library accurate and consistent is essential—especially as your product evolves or multiple teams build in parallel.Â
Walnut’s Update demos feature allows you to push changes from a template to all connected demos instantly. Instead of updating each demo manually, you can make adjustments once at the template level and propagate them across every connected demo with a single action.
This ensures your entire library stays:
- Accurate and up to date as product screens or messaging change
- Consistent across teams and workflows
- Aligned with your brand and workspace standards
- Scalable to maintain as your demo library grows
Where to Find Update Demos
You can access Update demos from the template's Demo Launcher.
- Open any template.
- Click the Create & Share Demo button in the top-right corner.
- In the Existing Demos list, click Update demos.
Walnut will then apply the latest version of your template to all connected demos shown in the Existing Demos list.
What Happens When You Use Update Demos
When you click Update demos, Walnut:
- Applies all updates from the template—such as new screens, edited content, structural changes, and section/guide adjustments—to every demo listed under Existing Demos for that template.
- Ensures each connected demo automatically reflects the latest version of the template.
- Preserves demo-specific settings (titles, share links, permissions), while syncing all template-driven elements.
When to Use Update Demos
Use Update demos whenever a shared template has been updated and multiple demos rely on it. Common scenarios include:
- Product UI changes (new layouts, updated screens, or redesigned pages)
- Revised flows, steps, or narrative sequences
- Messaging or copy updates across key screens
- Structural improvements (new sections, guides, navigation changes)
- Brand style adjustments applied at the template level
- Fixes to bugs or inconsistencies in a widely used template
If multiple teams rely on the same template, Update demos ensures every downstream demo receives the latest approved version without needing to be rebuilt or edited manually.
Best Practices
- Review before updating: Use preview mode to confirm that template changes look correct before pushing them to all connected demos.
- Update after major releases: Run Update demos after significant product or messaging changes so all demos stay aligned.
- Communicate changes: Let internal stakeholders know when a widely used template has been updated so they understand what changed in their demos.