@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{trunk Identity Brands}, for more information.

@item The CentOS Themes

The CentOS themes are a set of image files connected by one unique

visual style. The CentOS themes implements CentOS project corporate

visual identity in each visual manifestation of CentOS project (e.g.,

distributions, websites, promotion stuff, etc.).

@xref{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 Renderable directories

Inside @file{trunk/Identity}, renderable directories should have one

of the following directory layouts:

@subsubsection Layout 1: Simple image rendering

This directory layout contains one @file{Img/} directory (to store

final images), one @file{Tpl/} directory to store design templates,

and the translation entry is empty (there isn't translation files in

this configuration).  In this configuration, one design template

produces one untranslated PNG image, just as it is in the template.

@verbatim

trunk/Identity/path/to/dir

|-- Img

|   |-- anaconda_header_fig1.png

|   |-- anaconda_header_fig2.png

|   `-- anaconda_header_summary.png

`-- Tpl

    |-- anaconda_header_fig1.svg

    |-- anaconda_header_fig2.svg

    `-- anaconda_header_summary.svg

@end verbatim

@subsubsection Layout 2: Simple image rendering (extended)

This directory layout contains one @file{Img/} directory (to store

final images), one @file{Tpl/} directory to store design templates,

and the translation entry is empty (there isn't translation files in

this configuration).  When images are rendered, the @file{Img/}

directory structure is created automatically using the @file{Tpl/}

directory structure as reference.  In this configuration, one design

template produces one untranslated PNG image, just as it is in the

template.

@verbatim

trunk/Identity/path/to/dir

|-- Img

|   |-- Corporate

|   |   `-- monolithic.png

|   `-- Distro

|       `-- Anaconda

|           `-- Header

|               |-- fig1.png

|               |-- fig2.png

|               `-- summary.png

`-- Tpl

    |-- Corporate

    |   `-- monolithic.svg

    `-- Distro

        `-- Anaconda

            `-- Header

                |-- fig1.svg

                |-- fig2.svg

                `-- summary.svg

@end verbatim

@subsubsection Layout 3: Language specific image rendering

This directory layout extends previous one in order to produce

language-specific images.  This directory layout contains one

@file{Img/} directory (to store final images), one @file{Tpl/}

directory to store design templates, and the translation entry

contains translation files inside (organized by language codes). 

@verbatim

trunk/Translations/Identity/path/to/dir

|-- en

|   |-- Corporate

|   |   `-- monolithic.sed

|   `-- Distro

|       `-- Anaconda

|           `-- Header

|               |-- fig1.sed

|               |-- fig2.sed

|               `-- summary.sed

`-- es

    |-- Corporate

    |   `-- monolithic.sed

    `-- Distro

        `-- Anaconda

            `-- Header

                |-- fig1.sed

                |-- fig2.sed

                `-- summary.sed

@end verbatim

When images are rendered, the @file{Img/} directory structure is

created automatically using the translation entry structure as

reference (see above).  

@verbatim

trunk/Identity/path/to/dir

|-- Img

|   |-- en

|   |   |-- Corporate

|   |   |   `-- monolithic.png

|   |   `-- Distro

|   |       `-- Anaconda

|   |           `-- Header

|   |               |-- fig1.png

|   |               |-- fig2.png

|   |               `-- summary.png

|   `-- es

|       |-- Corporate

|       |   `-- monolithic.png

|       `-- Distro

|           `-- Anaconda

|               `-- Header

|                   |-- fig1.png

|                   |-- fig2.png

|                   `-- summary.png

`-- Tpl

    |-- Corporate

    |   `-- monolithic.svg

    `-- Distro

        `-- Anaconda

            `-- Header

                |-- fig1.svg

                |-- fig2.svg

                `-- summary.svg

@end verbatim

In this configuration, one language-specific file is applied to one

design tempalate to produce one translated PNG image. The relation

between language-specific translation file and design template is done

removing the language-specific directory from translation path, and

the one design template path that matches it is used.  

If no design template is found for one translation file, the final PNG

image for that translation file is not produced and the next

translation file in the list is evaluated.

For example, in this configuration the following translation files:

@verbatim

trunk/Translations/Identity/path/to/dir/en/Corporate/monolithic.sed

trunk/Translations/Identity/path/to/dir/es/Corporate/monolithic.sed

@end verbatim

match the same design template file:

@verbatim

trunk/Identity/path/to/dir/Tpl/Corporate/monolithic.svg

@end verbatim

in order to produce the following PNG image files:

@verbatim

trunk/Identity/path/to/dir/Img/en/Corporate/monolithic.png

trunk/Identity/path/to/dir/Img/es/Corporate/monolithic.png

@end verbatim

@subsubsection Layout 4: Release and language specific image rendering

This directory layout extends previous one in order to produce

language-specific images for different major releases of CentOS

distribution (as CentOS release schema describes).

This directory layout contains one @file{Img/} directory (to store

final images), one @file{Tpl/} directory to store design templates,

and the translation entry contains translation files inside (organized

by language codes and major release numbers). 

@verbatim

trunk/Translations/Identity/path/to/dir

|-- 5

|   |-- en

|   |   |-- Corporate

|   |   |   `-- monolithic.sed

|   |   `-- Distro

|   |       `-- Anaconda

|   |           `-- Header

|   |               |-- fig1.sed

|   |               |-- fig2.sed

|   |               `-- summary.sed

|   `-- es

|       |-- Corporate

|       |   `-- monolithic.sed

|       `-- Distro

|           `-- Anaconda

|               `-- Header

|                   |-- fig1.sed

|                   |-- fig2.sed

|                   `-- summary.sed

`-- 6

    |-- en

    |   |-- Corporate

    |   |   `-- monolithic.sed

    |   `-- Distro

    |       `-- Anaconda

    |           `-- Header

    |               |-- fig1.sed

    |               |-- fig2.sed

    |               `-- summary.sed

    `-- es

        |-- Corporate

        |   `-- monolithic.sed

        `-- Distro

            `-- Anaconda

                `-- Header

                    |-- fig1.sed

                    |-- fig2.sed

                    `-- summary.sed

@end verbatim

When images are rendered, the @file{Img/} directory structure is

created automatically using the translation entry structure as

reference (see above).  

@verbatim

trunk/Identity/path/to/dir

|-- Img

|   |-- 5

|   |   |-- en

|   |   |   |-- Corporate

|   |   |   |   `-- monolithic.png

|   |   |   `-- Distro

|   |   |       `-- Anaconda

|   |   |           `-- Header

|   |   |               |-- fig1.png

|   |   |               |-- fig2.png

|   |   |               `-- summary.png

|   |   `-- es

|   |       |-- Corporate

|   |       |   `-- monolithic.png

|   |       `-- Distro

|   |           `-- Anaconda

|   |               `-- Header

|   |                   |-- fig1.png

|   |                   |-- fig2.png

|   |                   `-- summary.png

|   `-- 6

|       |-- en

|       |   |-- Corporate

|       |   |   `-- monolithic.png

|       |   `-- Distro

|       |       `-- Anaconda

|       |           `-- Header

|       |               |-- fig1.png

|       |               |-- fig2.png

|       |               `-- summary.png

|       `-- es

|           |-- Corporate

|           |   `-- monolithic.png

|           `-- Distro

|               `-- Anaconda

|                   `-- Header

|                           |-- fig1.png

|                           |-- fig2.png

|                           `-- summary.png

`-- Tpl

    |-- Corporate

    |   `-- monolithic.svg

    `-- Distro

        `-- Anaconda

            `-- Header

                |-- fig1.svg

                |-- fig2.svg

                `-- summary.svg

@end verbatim

In this configuration, one language-specific file,  is applied to one

design tempalate to produce one translated PNG image for each major

release specified in the translation entry.  The relation among

release-specific and language-specific translation files, and design

template is done removing the release-specific and language-specific

directories from translation path, and looking for the one design

template path that matches.  

If no design template matches the translation file, the final PNG

image for that translation file is not produced and the next

translation file in the list is evaluated.

For example, in this configuration, the following translation files:

@verbatim

trunk/Translations/Identity/path/to/dir/5/en/Corporate/monolithic.sed

trunk/Translations/Identity/path/to/dir/5/es/Corporate/monolithic.sed

trunk/Translations/Identity/path/to/dir/6/en/Corporate/monolithic.sed

trunk/Translations/Identity/path/to/dir/6/es/Corporate/monolithic.sed

@end verbatim

match the same design template file:

@verbatim

trunk/Identity/path/to/dir/Tpl/Corporate/monolithic.svg

@end verbatim

in order to produce the following PNG image files:

@verbatim

trunk/Identity/path/to/dir/Img/5/en/Corporate/monolithic.png

trunk/Identity/path/to/dir/Img/5/es/Corporate/monolithic.png

trunk/Identity/path/to/dir/Img/6/en/Corporate/monolithic.png

trunk/Identity/path/to/dir/Img/6/es/Corporate/monolithic.png

@end verbatim

@subsubsection Layout 5: Brands specific image rendering

@xref{trunk Identity Brands}, for more information about themes

specific image rendering and directory layout.

@subsubsection Layout 6: Themes specific image rendering

@xref{trunk Identity Themes}, for more information about themes

specific image rendering and directory layout.

@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{trunk Scripts Bash Config}, for more information.

@end quotation

@subsection See also

@menu

* trunk Translations::

@end menu

@subsection References

@itemize

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

links).

@end itemize