Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Click-through demos

Summary

This page focuses on how to create click-through demos.

What is click-through demo

There are certain times when slides, video or other such media just will not do. When you are with a customer or on a trade show stage, a live product demonstration is far superior to slides or videos. Live demos, however, can be fraught with challenges, from technical issues to poor content or delivery. Click-through demos ensure every demo presentation, with groups small or large, is done perfectly every time, eliminating technical and content challenges. Click-through demos are reliable, easy to present and give the audience an absolutely life-like demonstration EVERY TIME.

Who can create click-through demos

Everyone can download DemoEasel and record and edit demos, you don't need license to create and edit demos, however, in order to generate demo packages, license is required. The Technical marketing team purchased licenses, the team will be happy to generate packages for you. The priority will be for customer facing demos, which can be reused by other team members.

Click-through demo consumers in GitLab

Different teams and individuals in GitLab can use it

How to create GitLab click-through demo

Define the use case

Demos should highlight the value of the product, it should demonstrate how it solves a market challenge. Focusing on features, no matter how they robust, will not be relevant to the customers if they don't understand how it solves their challenges.

To plan a winning demo

Prepare your environment

Close all opened windows, keep only Chrome window with GitLab instance opened. You should have a stable demo flow configured with the right demo data, ready for screen capturing. Prepare your browser, hide bookmarks and notifications. Hide OS notifications. Use the following script to resize Chrome to the required resolution. Open Script Editor in your MacBook and paste this script to it

set theApp to "Google Chrome"
set appHeight to 1080
set appWidth to 1920

tell application "Finder"
set screenResolution to bounds of window of desktop
end tell

set screenWidth to item 3 of screenResolution
set screenHeight to item 4 of screenResolution

tell application theApp
activate
reopen
set yAxis to (screenHeight - appHeight) / 2 as integer
set xAxis to (screenWidth - appWidth) / 2 as integer
set the bounds of the first window to {xAxis, yAxis, appWidth + xAxis, appHeight + yAxis}
end tell

Run the script. This will resize your browser to 1080*1920. If necessary, you can modify those parameters in the script for different screen resolution.

Capture the demo

Download and install DemoEasel. Open DemoEasel, click New Demo, read and follow the tips that presented , then click Start Capture. Navigate through your flow. DemoEasel will capture all screens and clicks. To finish recording, click the DemoEasel icon on the bottom dock to bring its UI, then Click Abstract Demo. DemoEasel will automatically recognize the recorded window (Chrome) and will suggest Auto Cropping, accept this option. Define a name for your demo, click OK.

Edit and Optimize

Once a demo has been captured we can use DemoEasel's editor to optimize and document it so that others can easily present the demo. Select from the demo list the demo you want to edit, click Edit the Demo button. The editor provides some basic and advanced capabilities. As for the beginning, it is essential for you to get familiar with the following items:

For more info, read the Getting Started.html in your DemoEasel folder.

Package and Share

There are two types of packages we use at GitLab: browser(HTML5) and simulation (Windows/MacOS executables). The Technical Marketing produces and upload browser demo packages to the demo page in handbook so employees and customers can learn the product and use cases. Since it supports iPAD, we use the browser to demo GitLab in demo booths in events.

For customer facing demos or keynotes, it is recommended to use the simulation version as it has better performance and actually gives the audience live demonstration experience.

For transparency, when we present a click-through demo, we announce at the beginning that this is a product simulation, not a live demo.

While everyone can contribute and create click-through demos, we would like to keep on consistency of the messages, ensure demos released in high quality and with the same look and feel, and due to license restrictions, the Technical Marketing team will review the demos, provide feedbacks and will generate the final demo packages for you.

To request the team to review and generate demo packages

The team will review the demo and might have some improvement suggestions. Once the demo will be ready for release, the team will produce demo packages, will provide you a link to it, and will close the Issue.