Follow
About Proofing Interactive Content

Interactive content provides multiple methods of engaging viewers. Agencies can measure the success of their campaigns using analytics gathered from responses to this content.

In Flare, this topic is in a different place: Proofing/Creating Proofs within Workfront.

Examples of interactive content include:

  • Websites
  • Embedded or streaming videos
  • Interactive banners 
  • HTML5 animations
  • Microsites
  • Interactive emails

This article provides the following about proofing interactive content:

About Creating Proofs for Interactive Content

You can create a proof for interactive content in one of the following ways:
  • Create a proof from a ZIP file containing the interactive content.
    Workfront unpacks the content from the ZIP file and stores it on a Workfront server. Because it is stored this way, you can rely on the content staying the same throughout the proof review cycle.
  • Specify the URL for the content.
    This is the simplest way to create a proof for interactive content. With this approach, an external server unknown to Workfront stores and hosts the content.
    We recommend this method for a large websites because it is difficult to gather all of the files that make up a large website. But, because the proof's content is stored externally, Workfront cannot protect it from changes made by the developers working on it, so you might not be able to rely on the content staying the same throughout the proof review cycle.

About Preparing Interactive Content in a ZIP file for Proofing

When you bundle interactive content in a ZIP file for proofing, make sure that it includes the following specifications:

  • All assets, such as CSS, JavaScript, videos, sounds, and images should be included in the bundle file.
  • Interactive content should include the main file (index.html, index.htm). If this file is not placed in the root location, the tool automatically searches the folder to find it. The main file does not need to be named index.html/index.htm, however, there can be only one .html/.htm file placed in the main location.
  • The file must contain at least one static file webpage.
  • The maximum bundle size is 500 MB.
  • In the case of ZIP files created in iOS, the tool automatically identifies the folder where the content is located
  • Interactive projects are supported only as ZIP archives. Standard ZIP file submissions will fail.
  • The website must be secure (HTTPS).
    This is not a requirement when using the Desktop Proofing Viewer. For more information, see "Understanding the Desktop Proofing Viewer."
  • The website must be allowed to be viewed in an iframe.
    This is not a requirement when using the Desktop Proofing Viewer. For more information, see "Understanding the Desktop Proofing Viewer."

Creating an Interactive Proof

After you prepare your ZIP bundle file, create an interactive proof.

For more information, see the section "Generating a Proof for Interactive Content in a ZIP File" in the article "Generating Proofs in Workfront."

Or, if you are using Workfront Proof, the section Generating a Proof for Interactive Content in the article Generating Proofs in Workfront Proof.

About Reviewing Interactive Proofs

We recommend that you use the standalone Desktop Proofing Viewer as the default viewer for interactive proofs. However, if your organization's policies do not allow use of the Desktop Proofing Viewer app, your Workfront administrator can configure your system so that you can review interactive content, bundled in a ZIP archive file, in the Web Proofing Viewer. For more information, see "Reviewing and Managing Interactive Proofs."

This article last updated on 2019-02-26 20:38:51 UTC