Adobe® LiveCycle® Enterprise Suite 2.

5
Brand & editorial guidelines
11 July 2010

Adobe Confidential
Table of contents
LiveCycle Enterprise Suite 2.5 (ES2.5) Overview 1
Product name & trademarks: The suite 2
Product name & trademarks: The modules 3
Descriptive terms—Software & module 4
Solution Accelerators 5
LiveCycle Naming Progression 7
LiveCycle versioning: Marketing vs. technical descriptors 8
LiveCycle versioning: Marketing vs. technical descriptors (as of Sept. 2010) 9
LiveCycle versioning: Marketing vs. technical descriptors—Examples 10
Speaking to the IT audience 11
LiveCycle Enterprise Suite 2.5 tagline 12
General branding: branded terms 13
General branding: non-branded terms 14
General branding: localization and editorial conventions 15
Non-LiveCycle server products 16
History 17
Design guidelines 19
Adobe LiveCycle Enterprise Suite 2.5 graphic elements 20
Logotypes 21
Color 22
Product identity: cropping & logo usage 23
Product identity: incorrect usage 24
Boxshot & mnemonic 25
Flash Platform signature 26
Adobe logo: Red tag logo 27
Adobe logo: Standard 28
Attribution statements & company name 29
Examples: Datasheet 30
Examples: Webpage 31
Examples: Tradeshow graphics 32
Examples: Novelty items 33
For more information 34
LiveCycle Enterprise Suite 2.5 (ES2.5) Overview

Adobe® LiveCycle® Enterprise Suite 2.5 (ES2.5) software can help you extend the value of existing back-end systems by enabling developers
to build and deploy applications quickly and easily, and by empowering business users to manage application environments based on
their specific needs. With LiveCycle ES2.5, you can make it easier for people to interact with information through intuitive user experiences,
improved efficiencies through business process automation, and enhanced customer service through personalized communications
management.
It will achieve this by focusing on providing solutions for three critical business areas:
•• intuitive user experiences,
•• business process automation, and
•• communications management.
With LiveCycle ES2.5 software, you can build and deploy easy-to-use, personalized, and interactive applications that connect to existing
business applications and automated processes. People interact with these rich Internet applications (RIAs) using the freely available and
ubiquitous Adobe Flash® Player and Adobe AIR® clients, making it easier to achieve high adoption rates.
Additionally, LiveCycle ES2.5 software can help enhance customer satisfaction, increase operational efficiencies, and reduce costs by targeting
communications more effectively and automating the generation of personalized documents.
These solutions are powered by impressive new capabilities that can be tied to two major new themes for LiveCycle ES2.5: streamlined
development and user empowerment.

1 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Product name & trademarks: The suite

To protect our product trademarks, always use the correct product names and legal marks.

When referring to the suite as a whole:

Logotype treatment & headlines:
Use provided logotypes or the full name with legal marks:
Adobe® LiveCycle® Enterprise Suite 2.5
or
Adobe® LiveCycle® ES2.5 - ONLY when character space is limited

1st reference in body text/document:

Adobe® LiveCycle® Enterprise Suite 2.5 (ES2.5) software

Subsequent references can be either:

Adobe LiveCycle ES2.5
LiveCycle ES2.5

Incorrect:
LiveCycle ES 2.5 - There should never be a space between “ES” and “2.5”; it’s always ES2.5.
LiveCycle ES2.5 (Enterprise Suite) - Note that this is the opposite of the correct use shown above.
LiveCycle ES2
LiveCycle ES
LiveCycle

2 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Product name & trademarks: The modules

While the suite will begin using the version “ES2.5,” the modules will remain at “ES2” as shown below.
The next page provides more information on the use of the descriptive terms “software” and “module.”

The complete list of LiveCycle modules* is: When referring to a single module*:
Adobe® LiveCycle® Business Activity Monitoring ES2 Extended
Adobe® LiveCycle® Business Activity Monitoring ES2 Standard Logotype treatment & headlines:
Adobe® LiveCycle® Collaboration Service
Adobe® LiveCycle® ES2 Connector for EMC® Documentum® Use provided logotypes or the full name with legal marks as shown in
Adobe® LiveCycle® ES2 Connector for IBM® Content Manager
Adobe® LiveCycle® ES2 Connector for IBM® FileNet the list to the left.
Adobe® LiveCycle® ES2 Connector for Microsoft® SharePoint®
Adobe® LiveCycle® ES2 Connectors for ECM 1st reference in body text:
Adobe® LiveCycle® Content Services ES2 Use the full name with legal marks as shown in the list to the left.
Adobe® LiveCycle® Data Services ES2
Adobe® LiveCycle® Data Services ES2 Enterprise Edition
Adobe® LiveCycle® Designer ES2 Subsequent references in body text may do any of the following:
Adobe® LiveCycle® Digital Signatures ES2 • Drop the legal marks - i.e. Adobe LiveCycle Workspace ES2
Adobe® LiveCycle® Forms ES2
Adobe® LiveCycle® Foundation • Drop “Adobe” - i.e. LiveCycle Workspace ES2
Adobe® LiveCycle® Launchpad ES2
Adobe® LiveCycle® Mosaic ES2 • Drop “LiveCycle ES2” - i.e. Workspace
Adobe® LiveCycle® Output ES2
Adobe® LiveCycle® PDF Generator ES2 Incorrect:
Adobe® LiveCycle® PDF Generator 3D ES2
Adobe® LiveCycle® Process Management ES2 Adobe LiveCycle [insert module name] Enterprise Suite 2
Adobe® LiveCycle® Production Print ES2 (do not spell out “Enterprise Suite” as part of the module name)
Adobe® LiveCycle® Reader® Extensions ES2
Adobe® LiveCycle® Rights Management ES2 Adobe LiveCycle ES2.5 [insert module name]
Adobe® LiveCycle® Rights Management ES2 Extension for Microsoft® Office
Adobe® LiveCycle® Workbench ES2 (do not change the version on the modules to “2.5”)
Adobe® LiveCycle® Workspace ES2
Additional technologies/services/etc: When referring to multiple modules*:
BlazeDS
Adobe® Enterprise Café • Introduce the modules with the brand: Adobe® LiveCycle® modules
Adobe® LiveCycle® Managed Services
Adobe® LiveCycle® Mobile ES2 • Follow with a list of the modules without “LiveCycle,” i.e. Data
Bundles: Services, Forms, etc.
Adobe® LiveCycle® ES2 Business Transformation Edition
Adobe® LiveCycle® ES2 Enterprise Forms Edition
Adobe® LiveCycle® ES2 Rights-Managed Content Services for Microsoft® Office Edition
*Please note that “modules” is not lead capped in any of these instances.
3 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Descriptive terms—Software & module

“Software” Please note that “software” and

“modules” are not lead capped in any
First prominent mention: Adobe LiveCycle Enterprise Suite 2.5 (ES2.5) should be used in of these instances.
combination with the term “software” to establish the category that LiveCycle ES pertains to, as
shown in the example below:
“Adobe LiveCycle Enterprise Suite 2.5 (ES2.5) software is built on a common server architecture based
on Java 2 Enterprise Edition…”
Second or subsequent mention: Adobe LiveCycle ES2.5 can be used on its own as a collective
noun, in order to make the communication more succinct:
“Adobe LiveCycle ES2.5 includes services for document control and security.”
Exception: If necessary, Adobe LiveCycle ES2.5 can be followed by the term “product.” In references
to a specific product upgrade for example, “product” may be the most accurate term to use.

“Module”
When describing units of software, the preferred descriptor term is “module.” Module connotes a
high level of integration across the LiveCycle ES2.5 solution.
Editorial example:
“Document security is delivered by the Adobe LiveCycle Rights Management ES2 module.”

4 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Solution Accelerators

Solution Accelerators are documented best practices and technical building blocks built to work with LiveCycle ES2.5.
Solution Accelerators are designed to be used by Adobe SI partners and/or Adobe Professional Services to accelerate
development and improve our customer’s time to value.

Getting started guide: An introduction to the Solution Accelerator, including installation and configuration instructions.
Solution guide: Explores a business problem in detail and maps out a comprehensive implementation strategy.
Solution template: An example implementation of a solution for the business problem addressed by the Solution
Accelerator, built using one or more building blocks. The solution template is customizable and can be used as either
an example of a solution or as the basis for rapidly building a customized proof of concept. Solution templates are not
supported or licensed but are bundled with the solution building blocks and modules in a Solution Accelerator edition.
Building blocks: Provides the technology assets that contribute to creation of the solution defined in the Solution
Accelerator. This licensed and supported technology includes technical documentation that explains how assets can be
customized for developing applications for production.

Solution Accelerator

}
Getting started guide
Solution template can iterate outside of technical release cycle.
Solution guide
For example: adding new use cases to the base Correspondence Management to create Correspondence Management for Retail Banking.
Solution template

Building blocks

LiveCycle modules } Building blocks and LiveCycle ES2.5 are developed to similar quality standards and follow same support models.

5 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Solution Accelerators, cont.

Solution Accelerator names:

1. Correspondence Management Solution Accelerator
2. Interactive Statements Solution Accelerator
3. Managed Review & Approval Solution Accelerator
4. Collaborative Selling Solution Accelerator
5. Self & Assisted Service Solution Accelerator
6. Case Management Solution Accelerator
7. Field Force Automation Solution Accelerator

Availability
at LiveCycle ES2.5 release (October 2010) future releases
Correspondence Management Collaborative Selling
Interactive Statements Self & Assisted Service
Managed Review & Approval Case Management
Field Force Automation
Onboarding/Enrollment

Using the “Solution Accelerator” term in text

With Adobe LiveCycle ES2.5 and the Correspondence Management Solution Accelerator, you can automate all kinds of correspondence—from
welcome packages and confirmations to proposals and claim letters—while ensuring communications are accurate, compliant, and secure.

6 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
 LiveCycle Naming Progression
ADOBE LIVECYCLE ENTERPRISE SUITE 2 (ES2) ADOBE LIVECYCLE ENTERPRISE SUITE 2.5 (ES2.5) ADOBE LIVECYCLE ENTERPRISE SUITE 3 (ES3)
Adobe LiveCycle Business Activity Monitoring ES2 Standard Adobe LiveCycle Business Activity Monitoring ES2 Standard Adobe LiveCycle Business Activity Monitoring ES3 Standard
Adobe LiveCycle Business Activity Monitoring ES2 Extended Adobe LiveCycle Business Activity Monitoring ES2 Extended Adobe LiveCycle Business Activity Monitoring ES3 Extended
Adobe LiveCycle ES2 Business Transformation Edition Adobe LiveCycle ES2 Business Transformation Edition Adobe LiveCycle ES3 Business Transformation Edition
Adobe LiveCycle Café Adobe Enterprise Café Adobe Enterprise Café
Adobe LiveCycle Collaboration Service Adobe LiveCycle Collaboration Service Adobe LiveCycle Collaboration Service
Adobe LiveCycle ES2 Connectors for ECM Adobe LiveCycle ES2 Connectors for ECM Adobe LiveCycle ES3 Connectors for ECM
Adobe LiveCycle ES2 Connector for EMC® Documentum® Adobe LiveCycle ES2 Connector for EMC® Documentum® Adobe LiveCycle ES3 Connector for EMC® Documentum®
Adobe LiveCycle ES2 Connector for IBM® Content Manager Adobe LiveCycle ES2 Connector for IBM® Content Manager Adobe LiveCycle ES3 Connector for IBM® Content Manager
Adobe LiveCycle ES2 Connector for IBM® FileNet Adobe LiveCycle ES2 Connector for IBM® FileNet Adobe LiveCycle ES3 Connector for IBM® FileNet
Adobe LiveCycle ES2 Connector for Microsoft® SharePoint® Adobe LiveCycle ES2 Connector for Microsoft® SharePoint® Adobe LiveCycle ES3 Connector for Microsoft® SharePoint®
Adobe LiveCycle Content Services ES2 Adobe LiveCycle Content Services ES2 Adobe LiveCycle Content Services ES3
Adobe LiveCycle Data Services ES2 (previously Flex™ Data Services) Adobe LiveCycle Data Services ES2 Adobe LiveCycle Data Services ES3
Adobe LiveCycle Data Services ES2 Enterprise Edition Adobe LiveCycle Data Services ES2 Enterprise Edition Adobe LiveCycle Data Services ES3 Enterprise Edition
BlazeDS (Open Source version of LiveCycle Data Services) BlazeDS (Open Source version of LiveCycle Data Services) BlazeDS (Open Source version of LiveCycle Data Services)
Adobe LiveCycle Designer ES2 Adobe LiveCycle Designer ES2 Adobe LiveCycle Designer ES3
Adobe LiveCycle Digital Signatures ES2 Adobe LiveCycle Digital Signatures ES2 Adobe LiveCycle Digital Signatures ES3
Adobe LiveCycle ES2 Enterprise Forms Edition Adobe LiveCycle ES2 Enterprise Forms Edition Adobe LiveCycle ES3 Enterprise Forms Edition
Adobe LiveCycle Forms ES2 Adobe LiveCycle Forms ES2 Adobe LiveCycle Forms ES3
Adobe LiveCycle Foundation Adobe LiveCycle Foundation Adobe LiveCycle Foundation
Adobe LiveCycle Launchpad Adobe LiveCycle Launchpad ES2 Adobe LiveCycle Launchpad ES3
Adobe LiveCycle Managed Services Adobe LiveCycle Managed Services Adobe LiveCycle Managed Services
Adobe LiveCycle Mobile Adobe LiveCycle Mobile ES2 Adobe LiveCycle Mobile ES3
Adobe LiveCycle Mosaic ES2 Adobe LiveCycle Mosaic ES2 Adobe LiveCycle Mosaic ES3
Adobe LiveCycle Output ES2 Adobe LiveCycle Output ES2 Adobe LiveCycle Output ES3
Adobe LiveCycle PDF Generator ES2 Adobe LiveCycle PDF Generator ES2 Adobe LiveCycle PDF Generator ES3
Adobe LiveCycle PDF Generator 3D ES2 Adobe LiveCycle PDF Generator 3D ES2
Adobe LiveCycle Process Management ES2 Adobe LiveCycle Process Management ES2 Adobe LiveCycle Process Management ES3
Adobe LiveCycle Production Print ES2 Adobe LiveCycle Production Print ES2 Adobe LiveCycle Production Print ES3
Adobe LiveCycle Reader Extensions ES2 Adobe LiveCycle Reader Extensions ES2 Adobe LiveCycle Reader Extensions ES3
Adobe LiveCycle ES2 Rights-Managed Content Services for Microsoft Office Edition Adobe LiveCycle ES2 Rights-Managed Content Services for Microsoft® Office Edition Adobe LiveCycle ES3 Rights-Managed Content Services for Microsoft Office Edition

Adobe LiveCycle Rights Management ES2 Adobe LiveCycle Rights Management ES2 Adobe LiveCycle Rights Management ES3
Adobe LiveCycle Rights Management ES2 Extension for Microsoft® Office Adobe LiveCycle Rights Management ES2 Extension for Microsoft® Office Adobe LiveCycle Rights Management ES3 Extension for Microsoft® Office

Adobe LiveCycle Workbench ES2 Adobe LiveCycle Workbench ES2 Adobe LiveCycle Workbench ES3
Adobe LiveCycle Workspace ES2 Adobe LiveCycle Workspace ES2 Adobe LiveCycle Workspace ES3
7 Adobe
Adobe LiveCycleWorkspace
LiveCycle Enterprise Suite
ES22.5Mobile
Guidelines | Adobe Confidential | 11 merged
July 2010 with Adobe LiveCycle Mobile
LiveCycle versioning: Marketing vs. technical descriptors

Individual modules will continue to use the “ES2” version number for all marketing purposes, and Please note that the term solution
component will no longer be used
will retain their specific version number for technical instances, such as splash screens, help screens, when describing a “product” such as
and documentation where technical versioning is currently used. For example, in marketing it would LiveCycle Forms ES2; the term should
be LiveCycle Mosaic ES2, but in technical uses it might be LiveCycle Mosaic 9. be LiveCycle module.

The next page has a complete list of marketing vs. technical version numbers; examples are on page 10.
Whole version numbers
When modules are at a full release, always use the whole number—9 not 9.0. The only exception
to this is when required to satisfy customer requirements (for example: contracts, technical
documentation), provide customer support, or meet specific legal obligations.
Dot releases (.x)
For marketing use, the suite will carry the “2.5” dot release version. Please see pages 2 and 3 for
guidance on using the naming correctly. No other dot releases will be shown in marketing, even
though there may be others before the next full release.
In-product assets or technical support communications may show the individual module’s dot
release versioning (i.e. LiveCycle Mosaic 9.5).
See page 10 for examples.

8 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
LiveCycle versioning: Marketing vs. technical descriptors (as of Sept. 2010)
MARKETING BRANDING - Use in public communications (website, mktg collateral, etc) TECHNICAL DESCRIPTORS - Use in documentation or splashscreens (downloads)
Adobe® LiveCycle® Enterprise Suite 2.5 Adobe® LiveCycle® Enterprise Suite 2.5
Adobe LiveCycle Business Activity Monitoring ES2 Standard Adobe® LiveCycle® Business Activity Monitoring ES2 Standard [insert BAM versioning here]
Adobe LiveCycle Business Activity Monitoring ES2 Extended Adobe® LiveCycle® Business Activity Monitoring ES2 Extended [insert BAM versioning here]
Adobe LiveCycle ES2 Business Transformation Edition NA
Adobe Enterprise Café Adobe® Enterprise Café
Adobe LiveCycle Collaboration Service Adobe® LiveCycle® Collaboration Service
Adobe LiveCycle ES2 Connectors for ECM Adobe® LiveCycle® 9 Connectors for ECM
Adobe LiveCycle ES2 Connector for EMC® Documentum® Adobe® LiveCycle® 9 Connector for EMC® Documentum®
Adobe LiveCycle ES2 Connector for IBM® Content Manager Adobe® LiveCycle® 9 Connector for IBM® Content Manager
Adobe LiveCycle ES2 Connector for IBM® FileNet Adobe® LiveCycle® 9 Connector for IBM® FileNet
Adobe LiveCycle ES2 Connector for Microsoft® SharePoint® Adobe® LiveCycle® 9.5 Connector for Microsoft® SharePoint®
Adobe LiveCycle Content Services ES2 Adobe® LiveCycle® Content Services 9
Adobe LiveCycle Data Services ES2 Adobe® LiveCycle® Data Services 3.1
Adobe LiveCycle Data Services ES2 Enterprise Edition Adobe® LiveCycle® Data Services 3.1 Enterprise Edition
BlazeDS BlazeDS
Adobe LiveCycle Designer ES2 Adobe® LiveCycle® Designer 9
Adobe LiveCycle Digital Signatures ES2 Adobe® LiveCycle® Digital Signatures 9
Adobe LiveCycle ES2 Enterprise Forms Edition NA
Adobe LiveCycle Forms ES2 Adobe® LiveCycle® Forms 9
Adobe LiveCycle Foundation Adobe® LiveCycle® Foundation
Adobe LiveCycle Launchpad ES2 Adobe® LiveCycle® LaunchPad 9
Adobe LiveCycle Managed Services Adobe® LiveCycle® Managed Services
Adobe LiveCycle Mobile ES2 Adobe® LiveCycle® Mobile 9.5
Adobe LiveCycle Mosaic ES2 Adobe® LiveCycle® Mosaic 9.5
Adobe LiveCycle Output ES2 Adobe® LiveCycle® Output 9
Adobe LiveCycle PDF Generator ES2 Adobe® LiveCycle® PDF Generator 9
Adobe LiveCycle PDF Generator 3D ES2 Adobe® LiveCycle® PDF Generator 3D 9
Adobe LiveCycle Process Management ES2 Adobe® LiveCycle® Process Management 9
Adobe LiveCycle Production Print ES2 Adobe® LiveCycle® Production Print 9
Adobe LiveCycle Reader Extensions ES2 Adobe® LiveCycle® Reader® Extensions 9
Adobe LiveCycle ES2 Rights-Managed Content Services for Microsoft Office Edition NA
Adobe LiveCycle Rights Management ES2 Adobe® LiveCycle® Rights Management 9
Adobe LiveCycle Rights Management ES2 Extension for Microsoft® Office Adobe® LiveCycle® Rights Management 9 Extension for Microsoft® Office
Adobe LiveCycle Workbench ES2 Adobe® LiveCycle® Workbench 9.5
9 Adobe
AdobeLiveCycle
LiveCycle Enterprise
Workspace Suite 2.5
ES2 Guidelines | Adobe Confidential | 11 July 2010 Adobe® LiveCycle® Workspace 9
LiveCycle versioning: Marketing vs. technical descriptors—Examples

Examples (mockups) of splash/log-in screens showing version number used for marketing purposes, followed by technical version number:

.5

2010

2010

10 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Speaking to the IT audience

When speaking to the Line of Business, we should focus on the three business solutions outlined in the introduction: intuitive user
experiences, business process automation, and communications management. However, when discussing the LiveCycle Enterprise Suite
with a technical audience at the module level, we still employ groupings, so we can articulate what modules are available in particular IT
areas. These should be used when presenting to a technical audience or matriculating technical audiences through Adobe.com.
Enterprise RIA:
Collaboration Service
Data Services
Mosaic
Business process management:
Business Activity Monitoring
Process Management
Content Services
Forms automation:
Reader Extensions
Forms
Document and information security:
Rights Management
Digital Signatures
Communications management:
Output
PDF Generator
PDF Generator 3D
Production Print

11 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
LiveCycle Enterprise Suite 2.5 tagline

There is currently no tagline in development.

Please note that the tagline that was used for LiveCycle ES (Engaging beyond the Enterprise™) will no
longer be used.

12 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
General branding: branded terms

What do we mean by branded?

Branded terms are terms that we legally protect through the use of registered trademarks. They are Brand names, consistent with Adobe’s
global branding policy, should not be
terms with which we want to create unique and proprietary associations (products and/or services) translated.
with Adobe. There are occasionally unique situations where a term is branded but because of legal
 ll non-branded terms can be
A
reasons, cannot be protected by the use of registered trademark. Terms are branded because they translated into local languages as
either represent proprietary technology that Adobe has patented, or a proprietary solution we have needed.
developed that is unique to our product and service offering.
US and General International Related Adobe Branded Terms
•• Adobe® Reader®: Adobe’s brand of universal client
•• Adobe® PDF: Adobe’s PDF technology solution
•• Adobe® Acrobat®: Adobe’s desktop solution for the enterprise
•• A
dobe® LiveCycle® Enterprise Suite 2.5 (ES2.5): Adobe’s brand for its line of enterprise
server and design tool software, and the prefix applied to individual server product names
(eg: Adobe LiveCycle Forms ES2) and individual design tool names (eg: Adobe LiveCycle
Designer ES2)
•• A
dobe® Professional Services: Consulting and solution delivery for Intelligent Document
Platform
•• Adobe® Enterprise Support: Maintenance and support

13 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
General branding: non-branded terms

Non-branded terms are terms that we do not seek to protect legally by trademarks.

We anticipate usage of some of these terms outside Adobe by partners, competitors, etc. Also, the
terms are industry-accepted, and too descriptive to be potentially available to own as proprietary
trademarks. The first letters of words in non-branded terms are not capitalized unless the terms are
featured on a diagram or in a display title. Additionally, there are no legal attributions (™ or ® symbols)
to appear alongside these terms.
The following are non-branded terms:
•• universal client: Reference to Adobe Reader or a web browser
NOTE: exceptions to the rules for capitalizing non-branded terms are as follows:
•• Product components: Examples of components that ship with LiveCycle ES products include
the following:
•• Adobe JMX Monitor
•• Adobe PDF Distiller
•• Adobe User Management
•• Adobe Assembler
•• Adobe Administrator
The above are capitalized but they are non-branded terms. The exception to this rule is Adobe
LiveCycle Configuration Manager, also a LiveCycle module, but one that carries the LiveCycle ES2
brand.

14 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
General branding: localization and editorial conventions

Localization guidelines
•• Brand names, consistent with Adobe’s global branding policy, should not be translated.
•• All non-branded terms can be translated into local languages as needed.

Branding editorial conventions

•• Th
e first letters of words in terms are capitalized irrespective of where they appear in
communications.
•• L egal attributions in the form of the symbols: ™ or ® appear immediately after the brand name in its
first and/or most significant mention.
•• A
legal attribution paragraph must be included at the end of a document to attribute all of the
trademarks referred in the document

Adobe® LiveCycle® Enterprise Suite 2.5 (ES2.5)

See pages 2 and 3 for details on the correct use of the product name in first and subsequent mentions.

15 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Non-LiveCycle server products

The following server products do not run on the J2EE architecture, therefore not branded under the LiveCycle
ES2 name. (Please note this list is for illustrative purposes only; it is not meant to be a current list of brands.)
•• Adobe Assembler
•• BlazeDS
•• Adobe Central Output Server
•• Adobe Central Pro Output Server
•• Adobe Document Server
•• Adobe Form Client
•• Adobe Graphics Server
•• Adobe Output Designer
•• Adobe Output Manager
•• Adobe Output Pak for Oracle
•• Adobe Output Pak for MySAP.com
•• Adobe Distiller Server
•• Adobe Web Output Pak

16 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
History

As a brief history, LiveCycle Enterprise Suite first introduced the concept of the “intelligent document” back in 2004 by leveraging PDF and
XML to advance data capture processes above paper and HTML. Some of the benefits delivered to customers using PDF forms have been:
•• Forms look the way the author intends—printing is easy and users can store records of the transaction. (This is also important for
regulatory compliance for ACORD and other regulated forms.)
•• PDF forms can be saved locally and completed offline.
•• They can be deployed to users that have various client platforms.
•• They can be made extremely secure.
•• The data can be routed dynamically to backend systems like HTML forms, but the actual form (data and presentation) can also be
maintained for archives.
•• PDF forms can look like the familiar paper version of a legacy form but be dynamic—changing format depending on user input.
The only drawback to PDF-based intelligent documents is that they maintain the document/paper metaphor, while some process
interactions require more cinematic and media-rich interfaces in order to effectively guide users through a transaction or process.

17 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
History, cont.

The next generation of LiveCycle, LiveCycle Enterprise Suite 2, then introduced the concept of “customer engagement applications,” which
added needed functionality when capturing information from customers— and doing it in a more engaging manner. LiveCycle began to
address the issues associated with process automation that appropriately engaged users within processes, and offered new application
development tools, frameworks, and servers that overcame these limitations and optimized experiences for users.
When applications are not designed with a user’s needs in mind, organizations experience:
•• user abandonment of a process when users give up due to confusion and frustration—reverting to costly paper-based processing;
•• process delays through incomplete information and error handling;
•• deflections and workarounds within a process as users prefer “just picking up the phone,” resulting in overloaded call centers;
•• missed sales opportunities; and
•• poor customer service and customer attrition.

18 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Design guidelines
Adobe LiveCycle Enterprise Suite 2.5 graphic elements

Adobe LiveCycle Enterprise Suite 2.5 continues to use the LiveCycle ES2 assets. It has
four fundamental elements: a product logotype, the product identity, a box shot and a
mnemonic. These elements should be used consistently across all marketing materials
for these products.

Logotype Download these elements

from the Marketing Hub, under
Products and Services >
LiveCycle > ES2.

Please note that each LiveCycle

module has a logotype posted to the
Marketing Hub. For the purposes of
the guidelines, we’re using one as an
Product identity Box shot Mnemonic
example.

20 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Logotypes

For marketing purposes, the suite logotype has been updated to use “2.5”. It will not
be updated in product.
The module logotypes will continue to use “2”.

Logotypes may be used in two color variations - all black or all white - which may be used Download the logotypes
from the Marketing Hub, under
interchangeably based on the placement. Products and Services >
LiveCycle > ES2 > Logotypes.

Please note that each LiveCycle

module has a logotype posted to the
Marketing Hub. For the purposes of
the guidelines, we’re using one as an
example.

Do not create your own logotype.

21 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Color

Adobe Livecycle Enterprise Suite 2.5 has been assigned a blue hue. All imagery, inside and outside
the product, derives from this hue. Consistent application of color—along with appropriate imagery
and clear typography—aids in product identification.

LiveCycle Enterprise Suite 2.5 color palette

COLOR PANTONE CMYK RGB WEB #

LiveCycle Blue DIC 2588 C 76 M 9 Y 3 K 0 R 15 G 156 B 215 0f9cd8
Gray Cool Gray 7 C0 M 0 Y 0 K 50 R 153 G 153 B 153 999999

Black Process Black C 73 M 67 Y 65 K 78 R 31 G 31 B 31 1f1f1f

22 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Product identity: cropping & logo usage

The LiveCycle Enterprise Suite 2.5 product identity is inspired by the idea of different
enterprise entities exchanging information as it flows throughout an organization.

Primary cropping Extreme Horizontal Cropping Extreme Vertical Cropping Download the imagery
from the Marketing Hub, under
Products and Services >
LiveCycle > ES2 > Identity.

The product identity is designed for

maximum headline type readability
in the upper left corner. Visual “quiet
space” in the lower right corner is
intended to accommodate the Adobe
logo.

Please make sure any cropped graphic

has sufficient resolution at actual size
when it is in layout. Print generally
requires 300 dpi and web 72 dpi.

Do not attempt to change, flip or alter

the identity in any way.

Square Cropping Round Cropping

23 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Product identity: incorrect usage

It is important to maintain consistency in the usage of the imagery in order to

communicate a unified brand message. Below are examples of incorrect usage of the
product identity.

Don’t add texture Don’t add a color over the “ Don’t re-crop the imagery Don’t re-color the imagery. Don’t ghost back the image.
to the imagery. white space” of the imagery. so that it loses the spirit of
the original.

Livecycle ES

Don’t reverse type out of Don’t contrast the imagery. Don’t distort the imagery. Don’t change the Don’t collage the imagery.
critical color areas so type orientation of the imagery.
is difficult to read.

24 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Boxshot & mnemonic

The boxshot is used to represent the product in marketing materials.

The mnemonic should be used when the imagery or boxshot is not appropriate due to
size or space limitations (i.e. on giveaways or when you need visual representation of
a list of products in limited space).

Mnemonics Download the boxshot & mnemonic

Each mnemonic is available in the primary full-color version, which includes a drop shadow; a full-color without the drop shadow for use in PPT and from the Marketing Hub, under
other applications where the drop shadow does not reproduce well; and a spot color version, to be used ONLY in novelty items such as hats and shirts Products and Services >
where a 4-color process and gradient can not be used. LiveCycle > ES2 > Boxshot or
Mnemonic respectively.

Mnemonic Do’s

The mnemonic should always be

LiveCycle ES2 LiveCycle ES2.5 LiveCycle LiveCycle LiveCycle LiveCycle BlazeDS
(same as ES2) Collaboration Data Services Launchpad Mosaic visually tied to the product name.
Service
When scaling the mnemonics in
Illustrator, make sure the “Scale
strokes & effects” option is checked.

Clear space Minimum size

Mnemonic Don’ts
.5x X .5x .5x X .5x
.25” Do not embed the mnemonic within
.5x .5x any main content or body text areas.
.75”
Do not change the color, design, or
letter configuration.

Do not create your own mnemonic to

.5x
represent a new program or identity -
.5x work with the brand and XD teams.

25 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Flash Platform signature

The Flash Platform signature is for Adobe use only. It should be used when you need
a visual represenation of the platform.

Download the signature

from the Marketing Hub, under
Products and Services >
Flash Platform > logo.

Do not create your own signature.

Do not alter the signature in any

way (do not recolor, re-arrange
mnemonics or placement of the
logotype, etc)

Minimum size

.5”

26 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Adobe logo: Red tag logo

The red tag logo is reserved for Adobe use only. It should be used as an
introduction of the Adobe brand on a communication, not as a signature to
close a communication. Its use must allow the the top or bottom to bleed off
the edge of the layout like a tag, layered on top of photography, illustration, Red tag logo at the Red tag logo at the
top of the page bottom of the page
or color fields in the layout.

The red tag logo should only occur once per piece. For instance, on a multi-page piece the tag would Find more information about using
the Adobe logo in the Corporate
go on the cover, but the standard logo would be used for the back cover. Brand Guidelines.
Size & clear space Don’ts
To standardize the use of the tag, three sizes are provided for most uses - 50 pixels high for web Do not alter the logo in any way.
banners and email headers, 7/8” high for printed materials, and 72 pixels high for web pages. These Do not animate, color, rotate, skew,
apply effects, or separate the elements.
sizes should be considered the minimum size for print/online uses. For printed communication, add
Never attempt to set the logo yourself,
.125” to the top or bottom of the red field to cover bleed. change the font, or alter the size,
Top placement Bottom placement proportions, or space between the
Adobe logo and the red field.

Don’t run the Don’t crop or

50 px 7/8” 72 px
tag horizontally extend the tag

50 px 7/8” 72 px

Minimum clear space

50 pixel logo used for: 7/8” logo used for:
• email newsletter • 5 x 7” postcard Don’t remove Don’t move the
.25x .25x “Adobe” logo within the tag
• web banner • 6 x 9” booklet
X
.25x • 8.5 x 11” format
72 pixel logo used for:
• A4 format
• web page
• A3 format
• 11 x 17” format
.25x
X
• PowerPoint presentation Don’t recolor Don’t apply
the logo or tag any effects
.25x .25x For formats larger than 11x17”
Top placement Bottom placement or A3, scale the red tag logo
proportionally to the piece.
27 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Adobe logo: Standard

The standard logo should be used for three main purposes: 1) to close a piece (i.e. back
of datasheet or brochure); 2) where there isn’t a top or bottom edge from which to hang
the tag (i.e. a golf ball, pen, middle of a document or web page); or 3) by 3rd-parties,
under license only (partner communications, co-marketing, sponsorships, etc).

Color Clear Space & minimum size Find more information about using
the Adobe logo in the Corporate
Clear space Minimum size
The primary use for the Adobe logo is the Brand Guidelines.
.5x X .5x
2-color version—black and Pantone 485. 9.525 mm Don’t
(0.375”)
When color or printing prohibits this, it may be .5x
Do not alter the logo in any way.
used in all black, or reversed out to white. The Do not animate, color, rotate, skew,
registration mark should be black or white to or apply effects to the logo. Do not
separate the elements. Never attempt
match “Adobe”, not red. to set the logo yourself, change the
font, or alter the size or proportions.
The “A” inside the logo should always be .5x
transparent, letting the background color Don’t recolor any Don’t remove
show through. part of the logo the “Adobe”
The horizontal logo
The logo can appear on color, illustration, or
photographic backgrounds, as long as the The horizontal logo should ONLY be used in
legibility and the integrity of the logo is not very small spaces, such as on pens, to retain
diminished. legibility. Don’t put color Don’t apply
behind the “A” any effects

2-color

Don’t move Don’t make a

1-color “Adobe” pattern or texture

Adobe Authorized Service Rep

28 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Attribution statements & company name

Please include a copyright notice and an attribution statement, which may appear in small—but still For more information on copyright
notices and attribution statements,
legible—print when using any Adobe trademarks in any published materials. please visit the Adobe Legal website.
The format for Adobe’s copyright notice is as follows:
© [Year of Publication] Adobe Systems Incorporated. All rights reserved. Company name

The format for the attribution statement should be: When using the company name,
please follow these guidelines:
List of Adobe marks used, beginning with “Adobe” and “the Adobe logo,” if used, followed by Correct:
any other marks in alphabetical order] are either registered trademarks or trademarks of Adobe Adobe
Systems Incorporated in the United States and/or other countries. Adobe Systems

For example: Adobe Systems Incorporated

Incorrect:
Adobe, the Adobe logo, Acrobat, Adobe AIR, AIR, LiveCycle, and Reader are either registered
Adobe Systems, Inc.
trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other
Adobe Incorporated
countries.
Adobe® Systems Incorporated (The
The attribution statement typically is included with other legal lines, such as a copyright notice, at logo gets a registration mark, but the
company name in text does not.)
the bottom of a web page or, if in printed material, at the end of the document or on the copyright
page of a book or manual.
Third-party trademark attribution
If you are referencing any third-party trademarks, or a module that includes a third-party trademark
in the name, be sure to give proper attribution. More details on third-party attribution can be found
on the Adobe legal website.

29 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Examples: Datasheet

Please note that datasheets will not be updated from LiveCycle ES2 to LiveCycle ES2.5.

Adobe LiveCycle ES2 Datasheet

Adobe® LiveCycle® Production Print ES2

Create the perfect mix of personalized print and
electronic communications
Organizations have invested heavily in personalized document generation over the years with
transactional documents such as statements, invoices, contracts, and packing slips as the mainstay
of print operations. Unfortunately, these systems were never designed to address today’s complex
multichannel communication requirements. These systems can—and must offer much more.
Yesterday’s print centers have the potential to transform themselves into centralized document
service hubs ready to support the growing and diverse multichannel content needs of the enterprise.

And yet, companies are under pressure to address several immediate and longer term output
concerns, including:
• Controlling production costs
Product summary
• Working with aging and inflexible output systems
Adobe LiveCycle Enterprise Suite
2 (ES2) is a software suite that • Delivering consistent communications across multiple channels
extends the value of existing
back-end systems by engaging • Addressing the increased need for protected electronic content delivery
users with collaborative rich
Internet applications (RIAs) and • Supporting enterprise architecture standards
guided forms, streamlining
internal processes, managing • Supporting corporate initiatives to streamline business processes from end to end
correspondence, and strengthening
• Developing and managing efficient electronic delivery channels
information and document security.
The Adobe LiveCycle Production Print ES2 module is uniquely designed to address all of these
With Adobe LiveCycle Production
concerns. Ideally suited to perform high-volume print and electronic jobs via multiple delivery
Print ES2, you can:
• Create personalized transactional channels, Production Print ES2 provides allows you to replace or augment your legacy applications
documents such as statements, with innovative tools that streamline processes and save money. And because it shares the same
contracts, letters, packing slips, or award-winning template design software as the rest of the Adobe LiveCycle Enterprise Suite 2 (ES2)
welcome kits family, you can not only achieve consistent multichannel communications, but also redefine the
• Generate documents dynamically
meaning of personalized communications with best-of-breed electronic business process solutions.
by merging data from multiple
back-end systems with With LiveCycle Production Print ES2, you can:
predesigned templates
• Standardize on award-winning • Decrease time and costs associated with high-volume print operations
Adobe LiveCycle Designer ES2
• Reduce mailing costs by collecting and merging jobs for more efficient processing
software to create and manage
document templates • Standardize on a single document design tool, Adobe LiveCycle Designer ES2, that spans
• Increase throughput and job interactive, on-demand, and high-volume document applications
flexibility with postprocessing
support for document collection, • Deliver protected multichannel output according to user profiles and preferences
sorting, and splitting
• Output documents in a range • Provide an enterprise production platform with the power and flexibility to replace outdated
of print or electronic formats processes or integrate with enterprise resource planning (ERP) and customer relationship
to help deliver multichannel management systems (CRM) systems
communications with ease
• Integrate with other Adobe LiveCycle ES2 modules to build end-to-end business processes

30 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Examples: Webpage

The example below is a mockup only. The final page will follow the naming guidance
on page 2.

Adobe LiveCycle Enterprise Suite 2.5

31 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Examples: Tradeshow graphics

When creating booth graphics, the red tag logo may appear more than once in the booth, but it
should only be used once per “area” within the booth. For example, in the demo station area,
only one panel has the red tag logo.
When using a logotype on tradeshow graphics, it is recommended to not use any versioning.

DEMO STATION THEATER

32 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
Examples: Novelty items

Promotional products should make use of solid colors, mnemonics, product name lockups and the
Adobe corporate logo. A mnemonic can be used as a set of typographic characters outside of its
colored rectangular stamp if manufacturing considerations require.
When using a logotype on novelty items, it is recommended to not use any versioning.

Novelty elements

Manufacturing as well as design

considerations should determine
when to use solid colors and
ES

E® L
IVE
C YC
L E®
mnemonics in lieu of primary imagery.
OB
AD
On items requiring silkscreening
or stitching it may be wise to avoid
primary graphics.

Wearables recommendations

Manufacturing concerns can impact

quality reproduction of the primary
imagery on clothing and hats. Also, as
a wearable, a more discreet approach
is preferable. It is more likely to be
worn if it has broader compatibility
with a wide range of clothing styles,
fabrics and colors.

The Adobe logo and product logotype

may be recolored to create a tone-on-
tone effect on novelty items.

ADOBE® LIVECYCLE® ES

33 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010
For more information

All of the assets detailed in this document are available for download from the Marketing Hub:
http://www.adobe.com/brandcenter/marketing_hub/entry.html

All use of Adobe assets must be sent for approval to: brandapproval@adobe.com

For brand questions, please e-mail: askbrand@adobe.com

For product/marketing questions, please e-mail: Sydney Sloan, ssloan@adobe.com

©2010 Adobe Systems Incorporated. All rights reserved.

Adobe, the Adobe logo, Acrobat, Adobe AIR, AIR, Distiller,
Flash, Flex, LiveCycle, and Reader are registered trademarks or
trademarks of Adobe Systems Incorporated in the United States
and/or other countries. All other trademarks are the property of
34 Adobe LiveCycle Enterprise Suite 2.5 Guidelines | Adobe Confidential | 11 July 2010 their respective owners.