@subsection Goals

The @file{trunk/Identity} directory exists to organize CentOS

corporate identity artworks. 

@subsection Description

The CentOS Project corporate identity is the ``persona'' of the

organization known as The CentOS Project.  The CentOS Project

corporate identity plays a significant role in the way the CentOS

Project, as organization, presents itself to both internal and

external stakeholders. In general terms, the CentOS Project corporate

visual identity expresses the values and ambitions of the CentOS

Project organization, its business, and its characteristics.  

The CentOS Project corporate identity provides visibility,

recognizability, reputation, structure and identification to the

CentOS Project organization by means of corporate design, corporate

communication, and corporate behaviour.

The CentOS Project settles down its corporate visual identity on a

``monolithic corporate visual identity structure''. In this structure

The CentOS Project uses one unique name (The CentOS Brand) and one

unique visual style (The CentOS Default Theme) in all its

manifestations. 

@table @strong

@item The CentOS Brands

The CentOS brand is the name or trademark that conncects the producer

with their products. In this case, the producer is The CentOS Project

and the products are the CentOS distributions, the CentOS web sites,

the CentOS promotion stuff, etc. 

@xref{Filesystem trunk Identity Brands}, for more information.

@item The CentOS Themes

The CentOS themes are a set of image files connected all together by

one unique visual style. Each theme is organized in different visual

manifestations, in order to cover each visual manifestation of The

CentOS Project (i.e., distributions, websites, promotion stuff, etc.).

@xref{Filesystem trunk Identity Themes}, for more information.

@end table

Inside a monolithic corporate visual identity structure, internal and

external stakeholders use to feel a strong sensation of uniformity,

orientation, and identification with the organization. No matter if

you are visiting websites, using the distribution, or acting on social

events, the one unique name and one unique visual style conect them

all to say: Hey! we are all parts of the CentOS project.  And,

probably, some vister will say: Can I join the party?  Yes you can, it

is free. :)

@subsection Usage

To produce identity artworks, use the following commands:

@table @samp

@item centos-art render 'path/to/dir' 

When @samp{path/to/dir} refers to one renderable directory under

@file{trunk/Identity}, this command renders identity artworks using

both related design models and related translation files.

@item centos-art render 'path/to/dir' --filter='pattern' 

When @samp{path/to/dir} refers to one renderable directory under

@file{trunk/Identity}, this command renders identity artworks using

both related design models and related translation files that match

the regular expression passed in @samp{--filter='pattern'} argument.

To control the number of files produced by @command{centos-art}

command, you need to look into the translation path and provide a

regular expression pattern that matches the translation path, or

paths, related to the file, or files, you want to produce.  

The regular expression pattern you provide to @command{centos-art}

command is applied to the translation path from its very beginning.

It is not the same to say @samp{5/en/01-welcome} that

@samp{01-welcome}, the frist expression matches but the last one does

not.

When using @samp{--filter='pattern'} you don't need to specify the

file extension. It is removed from translation path before applying

the pattern, so it doesn't count here.

@end table

@subsection File name convenctions

As file name convenction, inside CentOS Artwork Repository, both

text-based and image-based file name produced by @command{centos-art.sh}

script has the same name of their translation files without

the @samp{.sed} extension. The file extension is set as follow:

@subsubsection When text-based files are rendered

Text-based files end up having the same extension of their design

template file.

@subsubsection When image-based files are rendered

Image-based files always end up having the @file{.png} extension. 

@quotation

@strong{Tip} Once @file{.png} images are created, other image formats

may be created using the @command{renderFormats} post-rendering

action, inside the image-based related pre-rendering configuration

script.

@xref{Filesystem trunk Scripts Bash}, for more information.

@end quotation

@subsection See also

@menu

@comment --- Removed(* Filesystem trunk Translations::) ---

@end menu

@subsection References

@itemize

@item @url{http://en.wikipedia.org/Corporate_identity} (and related

links).

@end itemize