|
 |
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
|
728c6d |
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
|
728c6d |
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
|
|
728c6d |
|
|
|
728c6d |
<head>
|
|
|
728c6d |
<title>CentOS Artwork Repository: 2.4 The trunk/Identity Directory</title>
|
|
|
d1db00 |
|
|
|
728c6d |
<meta name="description" content="CentOS Artwork Repository: 2.4 The trunk/Identity Directory" />
|
|
|
728c6d |
<meta name="keywords" content="CentOS Artwork Repository: 2.4 The trunk/Identity Directory" />
|
|
|
728c6d |
<meta name="resource-type" content="document" />
|
|
|
728c6d |
<meta name="distribution" content="global" />
|
|
|
728c6d |
<meta name="generator" content="texi2html 1.76" />
|
|
|
728c6d |
<meta name="copyright" content="2009-2011 Alain Reguera Delgado" />
|
|
|
ee1f37 |
|
|
|
728c6d |
<link href="/home/centos/artwork/trunk/Identity/Manual/repository.css" rel="stylesheet" type="text/css" media="screen projection"/>
|
|
|
ee1f37 |
|
|
|
728c6d |
</head>
|
|
|
ee1f37 |
|
|
|
728c6d |
<body>
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
728c6d |
Start page body definitions.
|
|
|
728c6d |
-->
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
ee1f37 |
|
|
|
1075b9 |
[ < ]
|
|
|
52772c |
[ > ]
|
|
|
ee1f37 |
|
|
|
1075b9 |
[ << ]
|
|
|
1075b9 |
[ Up ]
|
|
|
ed9de5 |
[ >> ]
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
1075b9 |
[Top]
|
|
|
1075b9 |
[Contents]
|
|
|
ed9de5 |
[Index]
|
|
|
1075b9 |
[ ? ]
|
|
|
ee1f37 |
|
|
|
1075b9 |
|
|
|
52772c |
|
|
|
52772c |
2.4 The <tt>`trunk/Identity'</tt> Directory
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.1 Goals
|
|
|
aaf678 |
|
|
|
52772c |
The <tt>`trunk/Identity'</tt> directory structure implements The
|
|
|
52772c |
CentOS Project Corporate Identity.
|
|
|
06d106 |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.2 Description
|
|
|
063806 |
|
|
|
52772c |
The CentOS Project corporate identity is the "persona" of the
|
|
|
52772c |
organization known as The CentOS Project. The CentOS Project
|
|
|
52772c |
corporate identity plays a significant role in the way the CentOS
|
|
|
52772c |
Project, as organization, presents itself to both internal and
|
|
|
52772c |
external stakeholders. In general terms, the CentOS Project corporate
|
|
|
52772c |
visual identity expresses the values and ambitions of the CentOS
|
|
|
52772c |
Project organization, its business, and its characteristics.
|
|
|
52772c |
|
|
|
52772c |
The CentOS Project corporate identity provides visibility,
|
|
|
52772c |
recognizability, reputation, structure and identification to The
|
|
|
52772c |
CentOS Project organization by means of Corporate Design,
|
|
|
52772c |
Corporate Communication, and Corporate Behaviour.
|
|
|
52772c |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.2.1 Corporate Design
|
|
|
ee1f37 |
|
|
|
52772c |
The CentOS Project corporate design is applied to every single visual
|
|
|
52772c |
manifestations The CentOS Project as organization wants to express its
|
|
|
52772c |
existence. Examples of the most relevant visual manifestations inside
|
|
|
52772c |
The CentOS Project are The CentOS Distribution, The
|
|
|
52772c |
CentOS Web and The CentOS Stationery.
|
|
|
52772c |
|
|
|
52772c |
The CentOS Project corporate design is organized in the following
|
|
|
52772c |
work-lines:
|
|
|
06d106 |
|
|
|
06d106 |
|
|
|
52772c |
The CentOS Brand
|
|
|
52772c |
The CentOS Brand is the name or trademark that connects the producer
|
|
|
52772c |
with their products. In this case, the producer is The CentOS Project
|
|
|
52772c |
and the products are The CentOS Project visual manifestations.
|
|
|
52772c |
|
|
|
1075b9 |
See section The <tt>`trunk/Identity/Brands'</tt> Directory, for more information.
|
|
|
06d106 |
|
|
|
06d106 |
|
|
|
52772c |
The CentOS Colors
|
|
|
52772c |
|
|
|
52772c |
The CentOS Fonts provides the color information used along The CentOS
|
|
|
52772c |
Project visual manifestations.
|
|
|
52772c |
|
|
|
1075b9 |
See section The <tt>`trunk/Identity/Colors'</tt> Directory, for more information.
|
|
|
52772c |
|
|
|
52772c |
The CentOS Fonts
|
|
|
52772c |
|
|
|
52772c |
The CentOS Fonts provides the typography information used along The
|
|
|
52772c |
CentOS Project visual manifestations.
|
|
|
52772c |
|
|
|
1075b9 |
See section The <tt>`trunk/Identity/Fonts'</tt> Directory, for more information.
|
|
|
52772c |
|
|
|
52772c |
The CentOS Themes
|
|
|
06d106 |
|
|
|
52772c |
The CentOS Themes provides structural information and visual style
|
|
|
52772c |
information, as well, used along The CentOS Project visual
|
|
|
52772c |
manifestations.
|
|
|
52772c |
|
|
|
1075b9 |
See section The <tt>`trunk/Identity/Themes'</tt> Directory, for more information.
|
|
|
06d106 |
|
|
|
06d106 |
|
|
|
06d106 |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.2.2 Corporate Communication
|
|
|
52772c |
|
|
|
52772c |
The CentOS Project corporate communication is based on community
|
|
|
52772c |
communication. In that sake, the following media are available for
|
|
|
52772c |
corporate communication:
|
|
|
52772c |
|
|
|
52772c |
|
|
|
52772c |
The CentOS Mailing Lists (http://lists.centos.org/).
|
|
|
52772c |
The CentOS Forums (http://forums.centos.org/).
|
|
|
52772c |
|
|
|
52772c |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.2.3 Corporate Behaviour
|
|
|
52772c |
|
|
|
52772c |
The CentOS Project corporate behaviour is based on community
|
|
|
52772c |
behaviour.
|
|
|
52772c |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.2.4 Corporate Structure
|
|
|
ee1f37 |
|
|
|
52772c |
The CentOS Project corporate structure is based on a monolithic
|
|
|
52772c |
corporate visual identity structure. In this structure, we use one
|
|
|
52772c |
unique name (The CentOS Brand) and one unique visual style (The CentOS
|
|
|
52772c |
Theme) in all The CentOS Project visual manifestations.
|
|
|
52772c |
|
|
|
52772c |
Inside a monolithic corporate visual identity structure, internal and
|
|
|
52772c |
external stakeholders use to feel a strong sensation of uniformity,
|
|
|
52772c |
orientation, and identification with the organization. No matter if
|
|
|
52772c |
you are visiting web sites, using the distribution, or acting on
|
|
|
52772c |
social events, the one unique name and one unique visual style
|
|
|
52772c |
connects them all to say: Hey! we are all part of The CentOS
|
|
|
52772c |
Project.
|
|
|
52772c |
|
|
|
52772c |
Other corporate structures have been considered as well, but they
|
|
|
52772c |
introduce visual contradictions we need to be aware of. In that sake,
|
|
|
52772c |
lets describe the idea of: Producing one different visual style
|
|
|
52772c |
for each major release of The CentOS Distribution.
|
|
|
52772c |
|
|
|
52772c |
The CentOS Project maintains near to four different major releases of
|
|
|
52772c |
The CentOS Distribution parallely in time and that fact makes one part
|
|
|
52772c |
of The CentOS Project structural design, but just one part, not the
|
|
|
52772c |
complete structural design. In order to produce the correct corporate
|
|
|
52772c |
structure for The CentOS Project we need to concider all the visual
|
|
|
52772c |
manifestations The CentOS Project is made of, not just one of them.
|
|
|
52772c |
|
|
|
52772c |
If one different visual style is used for each major release of The
|
|
|
52772c |
CentOS Distribution, which one of those different visual styles would
|
|
|
52772c |
be used to cover the remaining visual manifestations The CentOS
|
|
|
52772c |
Project is made of. Would we end up with four different visual styles,
|
|
|
52772c |
one for each distribution? In that case, why The CentOS Distribution
|
|
|
52772c |
we use shows one visual style, The CentOS Web sites another and The
|
|
|
52772c |
CentOS Stationery even another completly different one? Isn't them
|
|
|
52772c |
all part of the same project?
|
|
|
52772c |
|
|
|
52772c |
Probably you be thinking, that's right, but The CentOS Brand connects
|
|
|
52772c |
them all already, why would we need to join them up into the same
|
|
|
52772c |
visual style too, isn't it more work to do, and harder to maintain?
|
|
|
52772c |
|
|
|
52772c |
Harder to maintain, more work to do, it is probably. Specially when
|
|
|
52772c |
you consider that The CentOS Project has proven stability and
|
|
|
52772c |
consistency through time and that, certainly, didn't come through
|
|
|
52772c |
swinging magical wangs or something but hardly working out to automate
|
|
|
52772c |
tasks and so providing maintainance through time. Said that, we
|
|
|
52772c |
consider that The CentOS Project visual structure should be consequent
|
|
|
52772c |
with such stability and consistency tradition. It is true The CentOS
|
|
|
52772c |
Brand does connect all the visual manifestations it is present on, but
|
|
|
52772c |
that connection would be stronger if one unique visual style backups
|
|
|
52772c |
it. In fact, whatever thing you do to strength the visual connection
|
|
|
52772c |
among The CentOS Project visual manifestations would be very good in
|
|
|
52772c |
favor of The CentOS Project recognition.
|
|
|
52772c |
|
|
|
52772c |
Obviously, having just one visual style in all visual manifestations
|
|
|
52772c |
for eternity would be a very boring thing and would give the idea of a
|
|
|
52772c |
visually dead project. So, there is no problem on creating a brand new
|
|
|
52772c |
visual style for each new major release of The CentOS Distribution, in
|
|
|
52772c |
order to refresh The CentOS Distribution visual style; the problem
|
|
|
52772c |
does is in not propagating the brand new visual style created for the
|
|
|
52772c |
new release of CentOS Distribution to all other visual manifestations
|
|
|
52772c |
The CentOS Project is made of, in a way The CentOS Project could be
|
|
|
52772c |
recognized no matter what visual manifestation be in front of us. Such
|
|
|
52772c |
lack of uniformity is what introduces the visual contradition we are
|
|
|
52772c |
precisely trying to solve by mean of themes production in the CentOS
|
|
|
52772c |
Artwork Repository.
|
|
|
52772c |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.3 Usage
|
|
|
52772c |
|
|
|
52772c |
The <tt>`trunk/'</tt> directory structure is organized in
|
|
|
52772c |
renderable and non-renderable directories. Generally,
|
|
|
52772c |
renderable directories contain two non-renderable directories inside,
|
|
|
52772c |
one to store design templates (the <tt>`Tpl/'</tt> directory), and other
|
|
|
52772c |
to store the content produced (the <tt>`Img/'</tt> directory).
|
|
|
52772c |
|
|
|
52772c |
In order to produce content inside rendereble directories, you can use
|
|
|
52772c |
the following command:
|
|
|
52772c |
|
|
|
52772c |
centos-art render trunk/Identity/Path/To/Dir
|
|
|
52772c |
|
|
|
728c6d |
 Warning If the centos-art command-line
|
|
|
52772c |
is not found in your workstation, it is probably because you haven't
|
|
|
52772c |
prepared it for using The CentOS Artwork Repository yet.
|
|
|
ed9de5 |
See section The <tt>`trunk/Scripts/Functions/Verify'</tt> Directory, for more
|
|
|
52772c |
information.
|
|
|
52772c |
|
|
|
52772c |
|
|
|
52772c |
This command takes one design template from the template directory and
|
|
|
52772c |
creates an instance of it in order to apply translation messages on
|
|
|
52772c |
it, if any. Later, using the design template instance, the command
|
|
|
52772c |
renders the final content based on whether the design template
|
|
|
52772c |
instance is a SVG file or a Docbook file. If the design template
|
|
|
52772c |
instace is a SVG file, the final content produced is a PNG image. On
|
|
|
52772c |
the other hand, if the design template instance is a Docbook file, the
|
|
|
52772c |
final content produced is a XHTML file. Final content is stored in the
|
|
|
52772c |
image directory using the design template directory paths as referece.
|
|
|
52772c |
The rendition flow described so far is known as the
|
|
|
52772c |
base-rendition flow.
|
|
|
52772c |
|
|
|
52772c |
Besides the base-rendition flow, the centos-art provides the
|
|
|
52772c |
post-rendition and last-rendition flows. The
|
|
|
52772c |
post-rendition flow is applied to files produced as result of
|
|
|
52772c |
base-rendition flow under the same directory structure. For example,
|
|
|
52772c |
you can use post-rendition action to convert the PNG base output into
|
|
|
52772c |
different outputs (e.g., JPG, PDF, etc.) before passing to process the
|
|
|
52772c |
next file in the same directory structure. The last-rendition flow is
|
|
|
52772c |
applied to all files produced as result of both base-rendition and
|
|
|
52772c |
post-rendition flows in the same directory structure, just before
|
|
|
52772c |
passing to process a different directory structure. For example, the
|
|
|
52772c |
<tt>`Preview.png'</tt> image from Ksplash component is made of three
|
|
|
52772c |
images. In order to build the <tt>`Preview.png'</tt> image through
|
|
|
52772c |
centos-art we need to wait for all the three images the
|
|
|
52772c |
<tt>`Preview.png'</tt> image is made of to be rendered, so we can combine
|
|
|
52772c |
them all together into just one image (i.e., the <tt>`Preview.png'</tt>
|
|
|
52772c |
image). This is something we can't do using post-rendition flow.
|
|
|
52772c |
|
|
|
52772c |
Inside <tt>`trunk/Identity'</tt> directory structure, you can find that
|
|
|
52772c |
base-rendition, post-rendition and last-rendition flows can be
|
|
|
52772c |
combined to build directory-specific rendition. The
|
|
|
52772c |
directory-specific rendition exists to automatically process specific
|
|
|
52772c |
renderable directories in very specific ways. Using directory-specific
|
|
|
52772c |
rendition speeds up production of different components like Syslinux,
|
|
|
52772c |
Grub, Gdm, Kdm and Ksplash that require intermediate formats or even
|
|
|
52772c |
several independent files, in order to reach its final construction.
|
|
|
52772c |
Directory-specific rendition is a way to programmatically describe how
|
|
|
52772c |
specific art works are built in and organized inside The CentOS
|
|
|
52772c |
Artwork Repository. Such descriptions have been added to
|
|
|
52772c |
centos-art command-line to let you produce them all with
|
|
|
52772c |
just one single command, as fast as your machine can be able to handle
|
|
|
52772c |
it.
|
|
|
52772c |
|
|
|
ed9de5 |
See section The <tt>`trunk/Scripts/Functions/Identity'</tt> Directory, for more
|
|
|
52772c |
information about the identity functionality of
|
|
|
52772c |
centos-art command-line interface.
|
|
|
52772c |
|
|
|
728c6d |
|
|
|
52772c |
|
|
|
52772c |
2.4.4 See also
|
|
|
ee1f37 |
|
|
|
52772c |
See http://en.wikipedia.org/Corporate_identity (and related
|
|
|
52772c |
links), for general information on corporate identity.
|
|
|
52772c |
|
|
|
52772c |
Specially useful has been, and still be, the book Corporate
|
|
|
52772c |
Identity by Wally Olins (1989). This book provides many conceptual
|
|
|
52772c |
ideas we've used as base to build The CentOS Artwork Repository.
|
|
|
52772c |
|
|
|
728c6d |
|
|
|
ee1f37 |
|
|
|
52772c |
[ < ]
|
|
|
1075b9 |
[ > ]
|
|
|
ee1f37 |
|
|
|
1075b9 |
[ << ]
|
|
|
52772c |
[ Up ]
|
|
|
ed9de5 |
[ >> ]
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
728c6d |
|
|
|
728c6d |
The content of left column ends here.
|
|
|
728c6d |
-->
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
Start page footer definitions.
|
|
|
728c6d |
-->
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
728c6d |
|
|
|
ee1f37 |
</body>
|
|
|
728c6d |
|
|
|
ee1f37 |
</html>
|