Skip to content
Nimbus Driver Studio

Sharing Templates Across Projects

A help template is a self-contained folder — the manifest.yaml, the layouts/, conceptual/, and styles/ it references, plus any assets/. Because it is no more than a collection of files, a customized template can be reused across many driver projects by copying it into a folder that Nimbus recognizes.

Work from a copy

Section titled “Work from a copy”

Each driver help project has its own private copy of its template files. Always customize that copy — never edit the templates Nimbus installs. Bring the template to its finished state in one project, then promote it to the shared location, where other projects can select it.

To create a shared template

Section titled “To create a shared template”

  1. In a driver help project, customize the template until the built help appears as intended. Use Mustache values such as {{driver.name}} and {{company}} instead of hard-coding driver-specific text, so the template works for any driver.

  2. Build the help and confirm it appears as desired.

  3. Locate the folder where custom Nimbus help templates are stored:

    <ProgramData>\Pacific MindWorks\Nimbus\<version>\HelpTemplates

  4. Create a new folder there named for the template. This name is what appears on the Template page of the help project properties, where a project’s template is selected.

  5. Inside that folder, create a subfolder named IviNet, IviCom, or IviC for the driver type the template targets.

  6. Copy the entire contents of the driver help project’s Template folder into that subfolder.

For example, a custom template named Acme Help for an IVI.NET driver ends up at:

<ProgramData>\Pacific MindWorks\Nimbus\<version>\HelpTemplates\Acme Help\IviNet

The template is then offered for selection on the Template page of any driver help project of that type.

See also

Section titled “See also”