Skip to main content

Rigi Documentation

Create a project from a template

Important

Settings and actions described below are only available for Rigi subscribers. For details, see the User roles section.

There are two ways to create a project based on another Rigi project:

  • Clone an existing project. For details, see the Clone a project guide.

  • Create a project from a template.

This guide describes the process for creating a template project and using it for new projects.

Advanced – API

You can automate the steps below using the API. For details, see the Use the APIs to clone a project and replace files guide.

I. Create a template project

Template projects in Rigi are based on existing projects. To create a template, you need to remove the unnecessary details from an existing project and save it as an empty template project. To do so, perform the following steps:

  1. Open the project that you would like to use as a template.

  2. (Optional) Assign missing translators:

    assign_missing_translators.png

    1. In the project menu, select Texts > Overview.

    2. Assign the external translators. For details, see the Manage translations in external editors guide.

  3. (Optional) Create a new review pack:

    1. In the project menu, select Review > Packs.

      Delete_packs.png

    2. Delete all packs.

    3. Create one review pack and assign reviewers for target languages. For details, see the Create a review packguide.

      Create_review_pack1.png

    4. Select the Preview tab and delete any existing previews.

      No_previews.png

  4. Delete files:

    Delete_files.png

    1. In the project menu, select Workspace.

    2. Select all the files and click the unlink.png icon to unassign files.

    3. Select all the files and click the Delete.png icon to delete files.

    The workspace is now empty.

  5. Approve the project for translation:

    1. Click the Approve for translation button in the top right-hand corner.

    2. In the popup, click the Approve button.

      Approve_for_translation.png

  6. Update source strings.

    Update.png

    1. In the project menu, select Texts.

    2. Click the Update button or the update.png icon in the Texts project menu section.

    3. In the popup, click the Accept button.

      Update_strings.png

    4. The Text section is now cleared. The languages and assigned external reviewers are still in the project.

  7. Name the template project:

    Template_name.png

    1. In the project menu, select Settings >Project > General.

    2. In the Project name field, enter the newly created template’s name.

    3. Click the Save button.

II. Create a new project based on a template

  1. On the dashboard, locate the template project.

    Clone_project.png

  2. Hover over it and click the Clone.png icon to clone the project.

  3. In the Clone project popup, do the following:

    Clone_project2.png

    1. Enter the new project name.

    2. Select the Select all checkbox.

    3. Click the Clone button.

  4. Open the newly cloned project.

  5. Set the new project up:

    1. Upload and assign files to the workspace. For details, see the Assign source files to the workspace guide.

    2. Approve files for translation.

    3. Download the Rigi tokenized files. For details, see the Prepare a staging server with Rigi tokens guide.

    4. Capture or import the HTML previews. For details, see the Manage HTML previews guides.

    5. In the project menu, select Texts > Overview and click the Update button.

      Update.png

    6. In the Update source strings popup, click the Accept button.

      Update_strings.png

    7. In the project menu, select Review > Packs.

    8. Open the review pack. The tasks are prefilled.

    9. In the Previews tab, click the Add previews button.

    10. In the Add previews to the review pack popup, select the uploaded previews and click the Add previews button.

Now the project can be executed.

When a new project is created from a template, translators are informed about their translation tasks automatically.

In this section: