Help       Feedback       Q&A       Sign in with Facebook or Google or Microsoft
workbench for expert-guided collaborative authoring

TurboWriter Help System

Creating a Content Library

You can create a content library for storing, organizing, and sharing content across any number of TurboWriter projects, using either of the following types of storage:

  • Google Docs (recommended and highlighted below)
  • Files uploaded to the cloud

You can also store HTML by activating Source in the editbox (recommended), or store rendered content instead.

The following sections describe each approach.

Using Google Docs for a Content Library
To create a content library using Google Docs:
  1. Create a Google Docs acccount
  2. For each content item:
    1. In Google Docs, create a new document
    2. In TurboWriter, go to the editbox containing the desired content and click the Source button
    3. Copy-and-paste from the editbox into the Google Docs document
    4. Give the Google Docs document a name
  3. Use Google Docs folders to organize your documents
  4. Share folders or individual documents using the Google Docs sharing feature
  5. To access a content item from the library:
    1. In Google Docs, open the document
    2. In TurboWriter, go to the editbox where you wish to place the content and click the Source button
    3. Copy-and-paste from the Google Docs document into the TurboWriter editbox
Using Files Uploaded to the Cloud for a Content Library

Instead of creating a Google Docs document on the cloud for each content item, you can create a file on your computer for each content item.

You can then upload, store, organize, share, and retrieve those files on the cloud using Google Drive.

Alternatively, a number of other cloud-based file storage services can be used to keep your files on the cloud instead. Such services are available from Adobe, Apple, Dropbox, Microsoft, and others. Some of those services are integrated into desktop apps from the same vendor.

To create a content library using files uploaded to the cloud:

  1. Create an account in the cloud service you want to use
  2. For each content item:
    1. Create a file using the appropriate app for the service you're using. If no specific app is applicable (for example, for Google Drive), use a text editor such as TextEdit in plain text mode (Mac) or Notepad (Windows)
    2. In TurboWriter, go to the editbox containing the desired content and click the Source button
    3. Copy-and-paste from the editbox into the app
    4. Save the file onto your computer, using a name that identifies the particular content item
    5. Upload the file to the cloud service
  3. Use folders within the cloud service to organize your files
  4. Share folders or individual files using the service's sharing feature
  5. To access a content item from the library:
    1. Download the file from the service to your computer
    2. Open the file with same app that was used to create the file
    3. In TurboWriter, go to the editbox where you wish to place the content and click the Source button
    4. Copy-and-paste from the app into the TurboWriter editbox
    5. Close the file and delete it from your computer

Storing Rendered Content Instead of HTML

Instead of using copy-and-paste for HTML content from and to a TurboWriter editbox with Source activated, you can copy-and-paste rendered content from the editbox into your content library without Source activated. Alternatively, if you are a project owner or manager and have access to the View Documents menu, you can click the link to open a separate window to print, then copy-and-paste rendered content from that window into your content library. You can then copy-and-paste the rendered content from your library into a different editbox without activating Source.

You may not notice a difference in appearance between storing rendered content versus HTML content. Since storing rendered content saves the step of clicking Source, that approach may be preferable for your purposes.

However, when you copy-and-paste rendered content, rather than from the editbox with Source activated, the rendered content is still stored in HTML even though that underlying HTML is not automatically visible. The underlying HTML of the rendered content that you store in your content library, and later copy-and-paste into a different editbox, may not be identical to the HTML in the original editbox. You can view the underlying HTML of the rendered content by activating Source in the destination editbox.