Table of Contents

*****************

CentOS Artwork Repository

1 branches

2 tags

3 trunk

  3.1 trunk/Identity

    3.1.1 Goals

    3.1.2 Description

    3.1.3 Usage

    3.1.4 Renderable directories

      3.1.4.1 Layout 1: Simple image rendering

      3.1.4.2 Layout 2: Simple image rendering (extended)

      3.1.4.3 Layout 3: Language specific image rendering

      3.1.4.4 Layout 4: Release and language specific image rendering

      3.1.4.5 Layout 5: Brands specific image rendering

      3.1.4.6 Layout 6: Themes specific image rendering

    3.1.5 File name convenctions

      3.1.5.1 When text-based files are rendered

      3.1.5.2 When image-based files are rendered

    3.1.6 See also

    3.1.7 References

  3.2 trunk/Identity/Brands

    3.2.1 Goals

    3.2.2 Description

    3.2.3 Usage

    3.2.4 See also

  3.3 trunk/Identity/Fonts

    3.3.1 Goals

    3.3.2 Description

    3.3.3 Usage

    3.3.4 See also

  3.4 trunk/Identity/Icons

    3.4.1 Goals

    3.4.2 Description

    3.4.3 Usage

    3.4.4 See also

  3.5 trunk/Identity/Isolinux

    3.5.1 Goals

    3.5.2 Description

    3.5.3 Usage

    3.5.4 See also

  3.6 trunk/Identity/Models

    3.6.1 Goals

    3.6.2 Description

    3.6.3 Usage

    3.6.4 See also

  3.7 trunk/Identity/Models/Img/Promo/Web

    3.7.1 Goals

    3.7.2 Description

    3.7.3 Usage

    3.7.4 See also

  3.8 trunk/Identity/Models/Tpl/Promo/Web

    3.8.1 Goals

    3.8.2 The CentOS web environment

      3.8.2.1 Design model (without ads)

      3.8.2.2 Design model (with ads)

      3.8.2.3 Controlling visual style

      3.8.2.4 Producing visual style

      3.8.2.5 Development and release cycle

      3.8.2.6 The [webenv-test] repository

      3.8.2.7 The [webenv] repository

      3.8.2.8 Priority configuration

      3.8.2.9 Navigation

    3.8.3 Usage

    3.8.4 See also

  3.9 trunk/Identity/Release

    3.9.1 Goals

    3.9.2 Description

    3.9.3 Usage

    3.9.4 See also

  3.10 trunk/Identity/Themes

    3.10.1 Goals

    3.10.2 Description

    3.10.3 Usage

    3.10.4 See also

  3.11 trunk/Identity/Themes/Models

    3.11.1 Goals

    3.11.2 Description

    3.11.3 Usage

    3.11.4 See also

  3.12 trunk/Identity/Themes/Models/Alternative

    3.12.1 Goals

    3.12.2 Description

    3.12.3 Usage

    3.12.4 See also

  3.13 trunk/Identity/Themes/Models/Default

    3.13.1 Goals

    3.13.2 Description

    3.13.3 Usage

    3.13.4 See also

  3.14 trunk/Identity/Themes/Models/Default/Distro

    3.14.1 Goals

    3.14.2 Description

      3.14.2.1 One theme for all major releases

      3.14.2.2 One theme for each major release

    3.14.3 Usage

    3.14.4 See also

  3.15 trunk/Identity/Themes/Models/Default/Distro/Anaconda

    3.15.1 Goals

    3.15.2 Description

    3.15.3 Usage

    3.15.4 See also

  3.16 trunk/Identity/Themes/Models/Default/Promo

    3.16.1 Goals

    3.16.2 Description

    3.16.3 Usage

    3.16.4 See also

  3.17 trunk/Identity/Themes/Models/Default/Web

    3.17.1 Goals

    3.17.2 Description

    3.17.3 Usage

    3.17.4 See also

  3.18 trunk/Identity/Themes/Motifs

    3.18.1 Goals

    3.18.2 Description

    3.18.3 Usage

    3.18.4 See also

  3.19 trunk/Identity/Themes/Motifs/Modern/Backgrounds

    3.19.1 Goals

    3.19.2 Description

    3.19.3 Usage

    3.19.4 See also

  3.20 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img

    3.20.1 Goals

    3.20.2 Description

    3.20.3 Usage

    3.20.4 See also

  3.21 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl

    3.21.1 Goals

    3.21.2 Description

    3.21.3 Usage

    3.21.4 See also

  3.22 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf

    3.22.1 Goals

    3.22.2 Description

    3.22.3 Usage

    3.22.4 See also

  3.23 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress

    3.23.1 Goals

    3.23.2 Description

    3.23.3 Usage

    3.23.4 See also

  3.24 trunk/Identity/Themes/Motifs/Modern/Palettes

    3.24.1 Goals

    3.24.2 Description

    3.24.3 Usage

    3.24.4 See also

  3.25 trunk/Identity/Themes/Motifs/TreeFlower

    3.25.1 Goals

    3.25.2 Description

    3.25.3 Usage

    3.25.4 See also

  3.26 trunk/Identity/Widgets

    3.26.1 Goals

    3.26.2 Description

    3.26.3 Usage

    3.26.4 See also

  3.27 trunk/Manuals

    3.27.1 Goals

    3.27.2 Description

    3.27.3 Usage

    3.27.4 See also

  3.28 trunk/Scripts

    3.28.1 Goals

    3.28.2 Description

    3.28.3 Usage

    3.28.4 See also

  3.29 trunk/Scripts/Bash

    3.29.1 Goals

    3.29.2 Description

      3.29.2.1 The identity matching list

      3.29.2.2 Adding new features

    3.29.3 Usage

      3.29.3.1 The `centos-art' `check' action

      3.29.3.2 The `centos-art' `search' action

      3.29.3.3 The `centos-art' `path' action

      3.29.3.4 The `centos-art' `locale-art' action

      3.29.3.5 The `centos-art' `license' action

    3.29.4 See also

  3.30 trunk/Scripts/Bash/Config

    3.30.1 Goals

    3.30.2 Description

      3.30.2.1 The `render.conf.sh' identity model

      3.30.2.2 The `render.conf.sh' translation model

    3.30.3 Usage

    3.30.4 See also

  3.31 trunk/Scripts/Bash/Config/Identity

    3.31.1 Goals

    3.31.2 Description

    3.31.3 Usage

    3.31.4 See also

  3.32 trunk/Scripts/Bash/Config/Translations

    3.32.1 Goals

    3.32.2 Description

    3.32.3 Usage

    3.32.4 See also

  3.33 trunk/Scripts/Bash/Functions

    3.33.1 Goals

    3.33.2 Description

    3.33.3 Usage

    3.33.4 See also

  3.34 trunk/Scripts/Bash/Functions/Config

  3.35 trunk/Scripts/Bash/Functions/Config/cli_getActionsIdentity.sh

  3.36 trunk/Scripts/Bash/Functions/Config/cli_getActions.sh

  3.37 trunk/Scripts/Bash/Functions/Config/cli_getActionsTranslations.sh

  3.38 trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh

  3.39 trunk/Scripts/Bash/Functions/Config/repo_renderIdentitySyslinux.sh

    3.39.1 Goals

    3.39.2 Description

    3.39.3 Usage

    3.39.4 See also

  3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh

    3.40.1 Goals

    3.40.2 Description

    3.40.3 Usage

    3.40.4 See also

  3.41 trunk/Scripts/Bash/Functions/Render/Config

    3.41.1 Goals

    3.41.2 Description

    3.41.3 Usage

    3.41.4 See also

  3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh

    3.42.1 Goals

    3.42.2 Description

    3.42.3 Usage

    3.42.4 See also

  3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh

    3.43.1 Goals

    3.43.2 Description

    3.43.3 Usage

    3.43.4 See also

  3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh

    3.44.1 Goals

    3.44.2 Description

    3.44.3 Usage

    3.44.4 See also

  3.45 trunk/Scripts/Bash/Locale

    3.45.1 Goals

    3.45.2 Description

      3.45.2.1 Configuration files

    3.45.3 Usage

      3.45.3.1 The `centos-art' `locale-cli' action

    3.45.4 See also

  3.46 trunk/Scripts/Perl

    3.46.1 Goals

    3.46.2 Description

    3.46.3 Usage

    3.46.4 See also

  3.47 trunk/Scripts/Python

    3.47.1 Goals

    3.47.2 Description

    3.47.3 Usage

    3.47.4 See also

  3.48 trunk/Translations

    3.48.1 Goals

    3.48.2 Description

      3.48.2.1 Translation Entries

      3.48.2.2 Translation Markers

      3.48.2.3 Translation Files

      3.48.2.4 Template Translation Files

      3.48.2.5 Common Translation Files

      3.48.2.6 Specific Translation Files

      3.48.2.7 Translation Rendering

      3.48.2.8 Translation (Pre-)Rendering Configuration Scripts

      3.48.2.9 Translation Rendering Default Functionality

    3.48.3 Usage

    3.48.4 See also

  3.49 trunk/Translations/Identity

    3.49.1 Goals

    3.49.2 Description

    3.49.3 Usage

    3.49.4 See also

  3.50 trunk/Translations/Identity/Brands

    3.50.1 Goals

    3.50.2 Description

      3.50.2.1 Conventional file names

      3.50.2.2 Numeric file names

      3.50.2.3 Translation markers

    3.50.3 Usage

    3.50.4 See also

  3.51 trunk/Translations/Identity/Brands/Tpl

    3.51.1 Goals

    3.51.2 Description

    3.51.3 Usage

    3.51.4 See also

  3.52 trunk/Translations/Identity/Fonts

    3.52.1 Goals

    3.52.2 Description

      3.52.2.1 Translation Markers

    3.52.3 Usage

    3.52.4 See also

  3.53 trunk/Translations/Identity/Models

    3.53.1 Goals

    3.53.2 Description

    3.53.3 Usage

    3.53.4 See also

  3.54 trunk/Translations/Identity/Release

    3.54.1 Goals

    3.54.2 Description

    3.54.3 Usage

    3.54.4 See also

  3.55 trunk/Translations/Identity/Themes

    3.55.1 Goals

    3.55.2 Description

    3.55.3 Usage

    3.55.4 See also

  3.56 trunk/Translations/Identity/Themes/Backgrounds

    3.56.1 Goals

    3.56.2 Description

    3.56.3 Usage

    3.56.4 See also

  3.57 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress

    3.57.1 Goals

    3.57.2 Description

    3.57.3 Usage

    3.57.4 See also

  3.58 trunk/Translations/Identity/Widgets

    3.58.1 Goals

    3.58.2 Description

    3.58.3 Usage

    3.58.4 See also

Index

List of Figures

CentOS Artwork Repository

*************************

This manual describes what the CentOS Artwork Repository is and what

can you do inside it.

   Copyright (C) 2009, 2010 CentOS Artwork SIG. All rights reserved.

   Permission is granted to copy, distribute and/or modify this document

under the terms of the GNU Free Documentation License, Version 1.2 or

any later version published by the Free Software Foundation; with no

Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A

copy of the license is included in the section entitled GNU Free

Documentation License.

1 branches

**********

2 tags

******

3 trunk

*******

3.1 trunk/Identity

==================

3.1.1 Goals

-----------

The `trunk/Identity' directory exists to organize CentOS corporate

identity artworks.

3.1.2 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.

*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.

     *Note trunk Identity Brands::, for more information.

*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.).

     *Note trunk Identity Themes::, for more information.

   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. :)

3.1.3 Usage

-----------

To produce identity artworks, use the following commands:

`centos-art render 'path/to/dir''

     When `path/to/dir' refers to one renderable directory under

     `trunk/Identity', this command renders identity artworks using

     both related design models and related translation files.

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

     When `path/to/dir' refers to one renderable directory under

     `trunk/Identity', this command renders identity artworks using

     both related design models and related translation files that match

     the regular expression passed in `--filter='pattern'' argument.

     To control the number of files produced by `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 `centos-art' command

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

     not the same to say `5/en/01-welcome' that `01-welcome', the frist

     expression matches but the last one does not.

     When using `--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.

3.1.4 Renderable directories

----------------------------

Inside `trunk/Identity', renderable directories should have one of the

following directory layouts:

3.1.4.1 Layout 1: Simple image rendering

........................................

This directory layout contains one `Img/' directory (to store final

images), one `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.

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

3.1.4.2 Layout 2: Simple image rendering (extended)

...................................................

This directory layout contains one `Img/' directory (to store final

images), one `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 `Img/' directory

structure is created automatically using the `Tpl/' directory structure

as reference.  In this configuration, one design template produces one

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

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

3.1.4.3 Layout 3: Language specific image rendering

...................................................

This directory layout extends previous one in order to produce

language-specific images.  This directory layout contains one `Img/'

directory (to store final images), one `Tpl/' directory to store design

templates, and the translation entry contains translation files inside

(organized by language codes).

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

   When images are rendered, the `Img/' directory structure is created

automatically using the translation entry structure as reference (see

above).

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

   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:

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

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

   match the same design template file:

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

   in order to produce the following PNG image files:

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

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

3.1.4.4 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 `Img/' directory (to store final

images), one `Tpl/' directory to store design templates, and the

translation entry contains translation files inside (organized by

language codes and major release numbers).

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

   When images are rendered, the `Img/' directory structure is created

automatically using the translation entry structure as reference (see

above).

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

   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:

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

   match the same design template file:

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

   in order to produce the following PNG image files: