Modify a Publishing profile


Many organizations need to be able to control which outputs particular content can be published to, who can publish it, when it can be published, and what other processes must be triggered before or after publishing.

Author-it allows you to create your own customizable profiles based on any of the publishing formats specific to the actual deliverable rather than the output type. These profiles are fully customizable, and you can create as many additional profiles as you need to suit your requirements and your deliverables.

For example, instead of publishing to HTML, you can define profiles that publish to Sales Presentation, Intranet, Web Based Help, and so on. You define the profiles you need to meet your requirements and your deliverables.

Variables can be assigned to a Publishing Profile, providing a useful means to work around non-translatable variables.

Author-it uses Publishing profiles to determine:

  • Which outputs a book (or books based on specific templates) can be published to

    Example: Any books based on a Presentation template, should only be publishable to HTML or XHTML (for the presentation), and to Word or PDF (for handouts).

  • Which users can publish a book using that profile

    Example: Sales and Marketing can publish sales presentations, but Human Resources cannot publish any documents using that profile.

  • The release states that content must be in for it to be included

    Example: Only "Released" content should be included in content that will be published and distributed to external customers. Content in "Draft" should not be included.

  • The templates, media objects, and/or external files that are used to control formatting and layout

    Example: Publishing content to HTML based profiles - one controlling the look and feel used in by the company website, and the other controlling the online knowledge center.

  • Which variables apply for the publishing output.

    Example: Variables can be assigned to a translation job Publishing Profile as a means of differentiating content that looks like translatable text but in fact must not be translated (such as button names, names of file objects, company names).