Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Date: Sat, 21 Jan 2012 08:36:00 -0500 (EST)
From: confluence@apache.org
To: ooo-commits@incubator.apache.org
Message-ID: <1112915.40834.1327152960100.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)

Change Comment:
---------------------------------------------------------------------
Color fix

Edited by Andrea Pescetti:
---------------------------------------------------------------------
{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.4 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 \\=
 | 279C |
| !87C2E6.png|border=3D1! | 135 194 230 \\ | 41 16&nbsp; 0 10 \\ | 87C2E6 \=
\ | 2905C |
| !CFE7F5.png|border=3D1! | 207 231 245 | 16 &nbsp; 6&nbsp; 0&nbsp; 4 \\ | =
CFE7F5 | 657C |
| !ECF5FB.png|border=3D1! | 236 245 251 \\ | 6&nbsp;&nbsp; 2&nbsp; 0&nbsp; =
2 \\ | ECF5FB | 656C |
| White | 255 255 255 \\ | 0&nbsp; 0&nbsp; 0&nbsp; 0 \\ | FFFFFF | Process =
White \\ |
| Black | 0 &nbsp; 0 &nbsp; 0 \\ | 0&nbsp;&nbsp; 0&nbsp;&nbsp; 0 100 \\ | 0=
00000 | Process Black \\ |

!OOo_colors.png|border=3D1!

The above are usage cases, desirable and undesirable within the range of th=
e pallet.&nbsp; It should be noted that the Pantone equivalents are a black=
 art.&nbsp; CMYK to Pantone translation is a hit and miss affair that is de=
pendant as much on the process and print media as the actual ink, so any pr=
int jobs should be matched visually in the first instance with the Printer'=
s swatches on the actual media.&nbsp;


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}

h3. {color:#0e85cd}Modifications/Additions to the Logo{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 resizi{co=
lor}{color:#000000}ng shoul{color}{color:#000000}d{color} {color:#000000}be=
 proportional (if the{color} !wire gulls.png|align=3Dright,border=3D1! {col=
or:#000000}wire gulls are scaled to 45% horizontally, they should be scaled=
 to 45% vertically). General colour usage guidelines apply: under most circ=
umstances, the wire gulls will probably be rendered in black or RGB 14:133:=
205 (or its CMYK or Pantone variants and screened to approximately 30%, but=
 a different colour might be appropriate in some contexts (for instance, a =
piece promoting a{color} {color:#000000}specific OpenOffice.org component).=
{color}
{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}&=
nbsp;

{color:#0e85cd}{*}The Orb{*}{color} is a very recent bug added during the m=
aturation of the 3.X series.&nbsp; Very usable as is and is up on the visua=
l design page. !opb.png|align=3Dright!


{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 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}&nbsp;Readability of the copy by the target audience.{colo=
r}

{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}

These are only the barest of styles. Additional styles should probably be c=
reated for picture/table captions, page numbers, cover page titles, and so =
on. Community input needs to be solicited before any recommendations can be=
 made on these. The fonts chosen are all available, mature open source font=
s. Because the fonts used in legacy OpenOffice.org logos ( Frutiger Bold Co=
ndensed and&nbsp; Frutiger Condensed) are not open source or even freely av=
ailable, the decision was made to avoid using this font on the heads and su=
bheads.

Bitstream Vera Sans was chosen as the heads/subheads font for several reaso=
ns:
There was a great deal of discussion about using Bitstream Vera Sans in cre=
ating the next version logo, this is a font that is similar in look to Frut=
iger Condensed, it is freely available, and so on. The 78% scale width was =
intended to enhance its similarity to Frutiger Condensed.

Bitstream Vera Serif was chosen for the body text for the following reasons=
: it is a freely-available open source font, as a serif font it has higher =
readability and clarity (a lower case =E2=80=9Cl=E2=80=9D will never be mis=
taken for an uppercase =E2=80=9CI=E2=80=9D, for example), it is distinct fr=
om more commonly used serif fonts (such as Times, Garamond, or Schoolbook),=
 and it allows the heads, subheads, and logo to stand out.

It should be noted that the Bitstream family of typefaces are under a restr=
ictive license.&nbsp; While this is not in fact an issue under Apache polic=
y, from a consistency point of view a Typeface with a license that is more =
in line with Apache philosophies would be preferable. &nbsp; &nbsp;


Font sizes for the different text styles (headings 20 pt, subheadings 16 pt=
, body text 12 pt, for example) are not currently designated because of the=
 great variety of pieces that could be created. (For instance, a trifold br=
ochure would obviously need to use a different font size than an 8.5 x 11 m=
ulti-page manual for body copy.) However, it may be desirable to create bas=
e =E2=80=9Cstandards=E2=80=9D that can then be used as a reference point fo=
r proportional changes.

h3. {color:#0e85cd}Main Headlines{color}

Main headlines (the top-level headlines) should have the following
characteristics:
Font: Sans Serif, bold
colour: {color:#000000}RGB 14:133:205 (or its CMYK or Pantone equivalents){=
color}
Font Effects: Small capitals
Scale Width:100%
Alignment: Centered
Indents: None
Spacing: 0.5 inches (or 1.27 cm) below
Line Spacing: Single
Position: Normal


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

Subheads should be progressively smaller the deeper they go. In general, th=
ey
should have the following characteristics:
Font: Sans Serif, oblique (not bold)
colour: {color:#000000}RGB 14:133:205 (or its CMYK or Pantone equivalents){=
color}
Font Effects: None
Scale Width: 100%
Alignment: Left
Indents: 0.25 inches (0.64 cm) - or match body text
Spacing: 0.25 inches (0.64 cm) below, same space above (except when followi=
ng
main headlines, when there should be no additional space above)
Line Spacing: Single
Position: Normal


h3. {color:#0e85cd}Body Text{color}

Body text makes up the bulk of a printed piece. (You=E2=80=99re reading =E2=
=80=9Cbody text=E2=80=9D
right now.) In general, body text paragraphs should have the following
characteristics:
Font: Serif
colour: Black
Font Effects: None
Scale Width: 100%
Alignment: Left
Indents: 0.25 inches (0.64 cm)
Spacing: 0.25 inches below
Line Spacing: 1.5 Lines
Position: Normal

h2. {color:#0e85cd}Colour Usage{color}


h3. {color:#0e85cd}Colour according to output{color}

One of the most persistent problems plaguing the art project has been the c=
onsistent use of colour. This is largely because of the inconsistencies in =
the way that different colours are rendered by different applications, and =
different processes. The following chart is a&nbsp; guide to maintaining co=
nsistent colour usage.&nbsp; The values are for the Apache OpenOffice 3.4 r=
elease:
|| Type of Piece || Expected Output || Colour Model || =E2=80=9CBlue=E2=80=
=9D Values || =E2=80=9CBlack=E2=80=9D Values ||
| Print | Printing press or PostScript printer | Spot (Pantone) | PMS 279C =
| Process Black (100%) |
| Print | Four-colour process (printing press or CMYK colour laser printer)=
 | Process (CMYK) | C: 93 M: 35 Y: 0 K: 20 | Process Black (100%) |
| Print | Non-PostScript printer, RGB colour inkjet printer, general distri=
bution PDF | Process(RGB) | R: 6 G: 52 B: 140 | R: 0 G: 0 B: 0 |
| Computer Display | Web graphic, Impress presentation, PDF for computer di=
splay (not printing), or other computer monitor display | Direct RGB | R: 6=
 G: 52 B: 140 | R: 0 G: 0 B: 0 |


h3. {color:#0e85cd}Component Colours{color}

Apache OpenOffice has 6 components: Writer (word processor), Calc (spreadsh=
eet), Impress (presentation editing), Draw (vector art editor), Math (formu=
la editor), and Base (data=C2=ADbase). In addition to the overall colour sc=
hemes, each component has its own associated colour. When promoting the com=
plete suite, the standard colours should be used. When promoting a specific=
 component, how=C2=ADever, it is often desirable to use the colour associat=
ed with that component for some elements. The following chart lists colours=
 associated with specific com=C2=ADponents:
|| Component || RGB Values || CMYK Values || Pantone Values ||
| Main OOo Icon \\
 !OOoMain.png! | R: 29 \\
G: 68 \\
B: 88 | C: 76 \\
M: 23 \\
Y: 0 \\
K: 65 | 302C |
| Writer \\  !openofficeorg24-writer.png|border=3D0! | R: 95 \\
G: 123 \\
B: 141 | C: 33 \\
M: 13 \\
Y: 0 \\
K: 45 | 8201C |
| Calc \\  !openofficeorg24-calc.png|border=3D0! | R: 157 \\
G: 201 \\
B: 21 | C: 22 \\
M: 0 \\
Y: 90 \\
K: 21 | 583C |
| Draw \\  !openofficeorg24-draw.png! | R: 252 \\
G: 179 \\
B: 48 | C: 0 \\
M: 29 \\
Y: 81 \\
K: 1 | 142C |
| Impress \\  !openofficeorg24-impress.png! | R: 249 \\
G: 101 \\
B: 1 | C: 0 \\
M: 59 \\
Y: 100 \\
K: 2 | 716C |
| Math \\  !openofficeorg24-math.png! | R: 141 \\
G: 168 \\
B: 163 | C: 16 \\
M: 0 \\
Y: 3 \\
K: 34 | 7543C |
| Base \\  !openofficeorg24-base.png! | R: 188 \\
G: 72 \\
B: 1 | C: 0 \\
M: 62 \\
Y: 99 \\
K: 26 | 7414C |

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