Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Date: Sun, 15 Jan 2012 23:56:00 -0500 (EST)
From: confluence@apache.org
To: ooo-commits@incubator.apache.org
Message-ID: <129191.39722.1326689760026.JavaMail.confluence@thor>
Subject: [CONF] Apache OpenOffice Community > Branding Style Guide
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated

Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/dis=
play/OOOUSERS)
Page: Branding Style Guide (https://cwiki.apache.org/confluence/display/OOO=
USERS/Branding+Style+Guide)


Edited by Graham Lauder:
---------------------------------------------------------------------
{toc:outline=3Dtrue\|indent=3D25px\|maxLevel=3D3}

h2. {color:#0e85cd}Introduction{color}

This style guide is loosely based on the original OOo style guide produced =
by Bernhard Dippold and Steven Shelton back in 2005, with added elements fr=
om the Visual Design pages of the UI project, updated to reflect our being =
part of the ASF community.

This guide is produced for a number of reasons, but the main one is to achi=
eve a consistent look to present to the world across all media, whether pri=
nt or electronic.
The aim is to achieve a high level of brand recognition with a brand that r=
eflects the values and strengths of the project and product.&nbsp; This is =
achieved by ubiquity, consistency, uniqueness, quality and recognisability


The challenge faced by the Community is to achieve quality and consistency =
when pieces are being produced by volunteer artists, most often working alo=
ne . Not only are there issues in matching fonts, text styles, and other el=
ements of design, but there are also technical issues surrounding different=
 colour standards for different media.

For this reason this Style Manual will be here to assist artists in creatin=
g promotional pieces that will have a unified look and feel, as well as ren=
der and print consistently.  Each change in version and style would require=
 the manual to be up dated, so specific pages will be added for each new re=
lease and completed in a timely manner well before feature freeze that allo=
ws any new style elements to be integrated into the release and so any styl=
e updates will speak to marketing materials for that release.

h2. {color:#0e85cd}Pallet{color}

h3. {color:#0e85cd}Short Term Pallet for 3.5 release{color}

Pallet is yet to be defined, however for the first ApacheOO release, consen=
sus is that retention of the latest Oracle OOo colour pallet is the best co=
urse.

[OOo3 Visual design|http://www.openoffice.org/ui/VisualDesign/OOo3_refresh.=
html] covers most of the colour elements.

|| colour || RGB \\ || CMYK \\ || Hex \\ || Pantone \\ ||
| !0E85CD.png|border=3D1! | 14 133 205 \\ | 93 35&nbsp; 0 20 \\ | 0E85CD \\=
 | |
| !87C2E6.png|border=3D1! | 135 194 230 \\ | 41 16&nbsp; 0 10 \\ | 87C2E6 \=
\ | |
| !CFE7F5.png|border=3D1! | 207 231 245 | 16 &nbsp; 6&nbsp; 0&nbsp; 4 \\ | =
CFE7F5 | |
| !ECF5FB.png|border=3D1! | 236 245 251 \\ | 6&nbsp;&nbsp; 2&nbsp; 0&nbsp; =
2 \\ | ECF5FB | |
| White | 255 255 255 \\ | 0&nbsp; 0&nbsp; 0&nbsp; 0 \\ | FFFFFF | |
| Black | 0 &nbsp; 0 &nbsp; 0 \\ | 0&nbsp;&nbsp; 0&nbsp;&nbsp; 0 100 \\ | 0=
00000 | |

!OOo_colors.png|border=3D1!

The above are usage cases, desirable and undesirable within the range of th=
e pallet.

h3. {color:#0e85cd}Future Pallet{color}

For ApacheOO 4.0 (If we retain the present version sequencing) there will n=
eed to be a new Pallet drafted to give the brand a new lift.  Historically =
the pallet has changed through various shades of blue from the beginning of=
 the OOo project with each new release bugs have come and gone and new desi=
gn elements introduced.  There is no reason that the 4.0 release should not=
 have a entirely new brand, new bugs, new style, to signal a new beginning.

h2. {color:#0e85cd}Logo{color}


h3. {color:#0e85cd}Logo Usage{color}

{color:#000000}It is recommended to use the logo without modifying it, alth=
ough you will probably have to scale it down to the appropriate size. Remem=
ber the proportionality of the logo when you rescale it and use the appropr=
iate logo for your purpose (with or without the version designation) as pre=
viously discussed.  Any modifications to fit a specific use case that has n=
ot been anticipated should be discussed on the marketing list{color}

{color:#000000}Please bear in mind that the logo is a complete package: all=
 of the elements are essential.{color}

{color:#000000}h3.{color} {color:#000000}Modifications/Additions to the Log=
o{color}

{color:#000000}Modifications of the logo are discouraged as being in confli=
ct with the basic purpose of having a logo: to reinforce a recognizable, me=
morable =E2=80=9Cbrand.=E2=80=9D Except under very special circumstances, t=
he logo should not be modified to display with different fonts, colours, or=
 elements than those currently included in the adopted version.{color}

h3. {color:#0e85cd}Bugs{color}

{color:#0e85cd}{*}The bird or "Seagull"*{color} {color:#000000}element of t=
he OpenOffice.org logo may be used as a =E2=80=9Cbug=E2=80=9D (design eleme=
nt to be incorporated into background images, icons, bullets, etc.){color} =
!gulls3.png|align=3Dright,border=3D1!
{color:#000000}in either black, gray, or RGB 14:133:205 (or its CMYK or Pan=
tone variants). It should not be used in any other colour except when refer=
ring to a specific component of the suite, in which case it should be rende=
red in the colour that matches the icons of that component. (For instance, =
the =E2=80=9CImpress=E2=80=9D bird bug could be rendered in RGB as R249, G1=
01, B1; =E2=80=9CCalc=E2=80=9D as R157, G201, B21; and so on. See the secti=
on on =E2=80=9Ccolour Usage=E2=80=9D for more details.) However, the comple=
te logo should be included somewhere within the piece.{color}

{color:#0e85cd}*=E2=80=9Cwire gulls=E2=80=9D or =E2=80=9Cwireframe gulls=E2=
=80=9D*{color} {color:#000000}have been used in the background of the splas=
h screen from OpenOffice.org 2.{color}

{color:#000000}This design is available from{color} {color:#000000}[here|ht=
tp://marketing.openoffice.org/art/galleries/marketing/design_elements]{colo=
r}{color:#000000}&nbsp; in both raster and vector formats. While the wire g=
ulls are not part of the official logo and should not be used as a =E2=80=
=9Cbug=E2=80=9D, they do make an attractive background for both print and w=
eb pieces. Artists are encouraged to use the wire gulls in this manner. The=
 wire gulls may be cropped and scaled (and will likely have to be cropped o=
r scaled in most usage), but as with the OpenOffice.org logo, any resizing =
should be proportional (if the wire gulls are scaled to 45% horizontally, t=
hey should be scaled to 45% vertically). General colour usage guidelines ap=
ply: under most circumstances, the wire gulls will probably be rendered in =
black or RGB 14:133:205 (or its CMYK or Pantone variants and screened to ap=
proximately 30%, but a different colour might be appropriate in some contex=
ts (for instance, a piece promoting a specific OpenOffice.org component).{c=
olor}

{color:#000000}Be aware of rendering problems when printing the wire gulls:=
 at 100% of its normal size (704 x 546 pixels), the line width of the graph=
ic=E2=80=99s smallest line is 0.01 pixel and the thickest line is 1.0 pixel=
.  Scaling the graphic down significantly will make these lines nearly impo=
ssible to print on a press or printer, and may cause the lines to be invisi=
ble or =E2=80=9Cfuzzy=E2=80=9D when displayed on a computer screen.{color} =
!wire gulls.png|align=3Dright,border=3D1!

{color:#000000}Future bugs may come into common use as part of the new Apac=
he OpenOffice branding, however these must reflect the project and product =
and must be approved by the community before they are added to the style gu=
ide.{color}


h2. {color:#0e85cd}Text{color}

{color:#000000}Because of the many different uses of text in promotional an=
d marketing pieces (ranging from full-featured brochures over simple web ba=
nners to Impress presentations), guidelines for the use of styles in text a=
re, for the most part, just those: guidelines. They are to be considered wh=
en creating a design, but are nothing like canons that must be followed. Be=
fore deviating from the guidelines, however, any artist working on an OpenO=
ffice.org piece should consider the following factors:{color}
{color:#000000}\*How consistent with other Apache OpenOffice pieces the art=
 will look;{color}
{color:#000000}\*The nature of the piece (in general, text-heavy pieces sho=
uld be;{color}
{color:#000000}more consistent);{color}
{color:#000000}\*The goal of the project to create a unified, professional =
image;{color}
{color:#000000}\*The =E2=80=9Clook=E2=80=9D of the piece; and{color}
{color:#000000}\* Readability of the copy by the target audience.{color}

{color:#000000}It may or may not be appropriate for a designer to vary from=
 the standards based upon these factors. In the end, the decision is ultima=
tely that of the designer, but more consistent and attractive pieces are li=
kely to have greater distribution and impact.{color}

Change your notification preferences: https://cwiki.apache.org/confluence/u=
sers/viewnotifications.action