Velocity powered by Wavelink

This page refers to an older version of the product.
View the current version of the User Guide.

Configuring Project Settings

A project includes your host profile and all of the settings and scripts that you want associated with a specific host.

You can create global themes that change styles across all screens, though this does not change a screen's status from "Predictive" to "Template." Only manual changes performed an individual screen's elements will force the creation of a template from the Velocity Console.

Additionally, you can associate external resources such as HTML and grammar files that you can reference from scripts.

You cannot edit theme elements on a Web host profile.

Modern Theme

On the Screens page, you configure each element on a screen-by-screen or template-by-template basis. When you modify elements on the Settings > Modern Theme tab, the elements are configured globally.

For more information about the elements and how to configure them, see Configuring Screens.

Native Theme


Allows you to set the font size for the Native mode.



External files such as HTML, CSS, JavaScript, and grammar files are associated with a project at this screen. All files added here can then be referenced from a script and applied to a specific scope.

The resources added here are associated with a directory and bundled with your project during deployment. This way you don't have to reference absolute or relative directories, but can instead list a file name that the Velocity Client then locates when executing.

When a script in Velocity references a file external to your project, such as a CSS file, it must be added as a resource to the project. If you're using Speakeasy and add a grammar file, then you can load this file via a script and use voice-to-text phrase recognition.

You can also add HTML resources, and then reference them with file://.

Add. Associates a resource file with your project.

Delete. Removes a resource file from your project. This does not delete the file itself, it just prevents the file from being included in the project when it is exported or deployed.

This page refers to an older version of the product.
View the current version of the User Guide.

The topic was:



Not what I expected