1. Select a one2edit™ Project folder.
2. Choose Create Projects from the Action Menu.

NOTE: While this workshop assumes that you have already uploaded your InDesign® documents to your one2edit™ Asset Space, it is possible to upload and extract .zip files directly in the Documents step of the Project-Creation Assistant.

1. Steps: This is a breadcrumb navigation for the steps taken when importing documents. During the import process, you can navigate to a previous step by clicking on it here.
2. Asset Browser: You select your uploaded InDesign® file(s) here. You may also upload files here, if you have not already done so.
3. Selected Documents / Import List: The documents which are dragged to this area will be linked as projects within one2edit™.

… via Drag-and-Drop

1. Browse to the folder containing your document(s).
2. Drag and drop the InDesign® file(s) to the Selected Documents list.
3. The selected document(s) appear in the Selected Documents list.

NOTE: Multiple INDD files from a single folder can be selected and dragged at the same time.

NOTE: If a file is dragged to the Selected Documents list, but does not appear there, it may already be linked to a project in one2edit™.

… via Button press

1. Browse to the folder containing your first document(s).
2. Select the InDesign® file(s)
3. Click the Add selected Documents button
4. The selected document(s) appear in the Selected Documents list.

NOTE: Multiple INDD files from a single folder can be selected and added at the same time.

Once all documents have been added to the Selected Documents list, click Continue.

In this step, we are going to set up a Content Group. Please keep in mind that any Content Groups set up here will be present in ALL of the imported documents.

Be default, an initial Content Group will be present for adaption.

Clicking New Group in the action menu will add more Content Groups, if required.

NOTE: At least one Content Group must be present in order to proceed.

Rename a Content Group by double-clicking its name and typing in the name that matches the Content Group(s) in your workflow templates.

NOTE: The name needs to match the Content-Group/Workflow-track names in any workflow templates that you intend to use with these projects.

Continue to set up the content group options as you normally would in any master document.

In this example, we are setting up a translation group for US English document, and segmenting the document according to the one2edit™ Default segmentation rules.

Drag and drop Content Rules from the Content Rules (Policies) dialog, as you would when setting up a Content Group in any master document.

NOTE: Open the Content Rules dialog via Settings > Content Rules in the main navigation menu, or by double-clicking in one of the two Content Rules fields.

Drag and drop Text Rule sets from the Text Rules dialog, as you would when setting up a Content Group in any master document.

NOTE: Open the Text Rules dialog via Settings > Text Rules in the main navigation menu, or by double-clicking in the Text Rule Sets field.

The Includes and Excludes sections are for filters to select what content is automatically added to your Content Group.

Click the + (plus) button on either section to add a filter to it. Multiple filters can be added to each section, and the filters will be AND-ed together.

1. Include: Anything that matches these filters is added to the Content Group. In this example, we are including everything from a document layer named 'text'.
2. Exclude: Anything that matches these filters will be excluded from the Content Group. In this example, we are excluding all delimiters and images.

The net result of the filters in our example is that everything that is not an image or a delimiter on the 'text' layer (i.e. all text items), will be added to the Content Group.

NOTE: If you do not use filters, then all of the document content will be added to the Content Group. If multiple content groups exist without filters, then all of the document content will be added to the first Content Group (i.e. the one on the left).

You can save your Content Group setup as a preset for the next time you use the Project-Creation Assistant.

Simply click Save As in the action menu, as shown.

Then type a name for your preset into the Save as dialog, and click Save.

The next time you use the Project-Creation Assistant, select your preset from the action menu, as shown.

This reduces setup time for future projects that have the same Content-Group requirements.

Once your Content Group(s) are set up, click Continue to move to the next step in the process.

At this step, you can set up version documents for each project, and what workflows to assign to those version documents.

You may also assign workflows directly to the master documents, if no version documents are required.

NOTE: If you click Continue at this point, only the master documents will be created. These masters will contain the Content Groups, but no versions will be created in the projects.

1. Select a project from the section on the left.
2. The workflow-setup area for this project is now displayed on the right.

Use the Add Version button to add version documents to the selected project.

NOTE: Once you create version documents within a project, you may no longer assign a workflow to the master document.

Double-click in the Version field to give the version document with a more appropriate name.

Repeat the above steps to add as many version documents as are required for this project.

NOTE: The Clear Versions button will remove ALL version documents from the selected project.

Click the [No Workflow] button beside a version document to assign it a workflow. This opens the Select Workflow dialog.

NOTE: Any workflows added here will be automatically started when the import process has been completed.

Select a workflow for this version document, and click the Select button.

NOTE: The workflows chosen must contain workflow tracks with the correct Content Group name(s). In this example, the workflows must each contain a workflow track entitled Translation Group, because this is the name we gave our Content Group in the previous steps.

Repeat the above steps to add a suitable workflow to each version document.

If desired, click the Apply to all projects button.

This will duplicate the version-document setup, including names and workflows, across all the projects on the left.

Once all projects have been set up, click Continue.

Finally, check that everything looks OK in this summary.

1. Target: This displays the one2edit™ project folder in which these projects will be created.
2. Count: A summary of the total number of documents being created, and how many workflows will be started.
3. Import: If the numbers all check out, click the Import button to begin the project-creation process.

In our example above, we have 1 Content Group, 2 master documents, 6 version documents (3 per project), and 6 workflows (1 each per version document). These projects will be created in the selected folder entitled 'New Department'.

NOTE: If the Import button is grayed out or does not work, please ensure that you have a target project folder selected. If not, one2edit™ cannot know where you want to create these new projects.

While the project-creation process is running, the Importing bar will be displayed in the dialog.

When the process completes, the dialog will automatically close.

NOTE: Depending on the number of documents and version documents involved, and the complexity of those documents, this process may take a long time.

When the process has completed, you will see:

1. the new master documents
2. the new version documents (complete with started workflows)

in your chosen project folder.

Instead of creating version documents in a project, you may wish to assign a workflow directly to your master document by clicking the [No Workflow] button, as shown.

NOTE: Assigning a workflow to your master document means that it is not possible to create any version documents in that project (unless the workflow on the master document is removed).

NOTE: If you assign a translation workflow to a master document, then there is no source document that can be used to capture translations (i.e. a single InDesign file cannot be bilingual). Therefore, the Commit Translations workflow action will not work, nor will it be possible to export a TMX file from the translation job.