<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
<html>
<!--This manuals documents relevant information regarding the deployment,
organization, and administration of CentOS Artwork Repository.
Copyright C 2009-2011 Alain Reguera Delgado
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.
-->
<!-- Created on March, 22 2011 by texi2html 1.76 -->
<!--
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
Olaf Bachmann <obachman@mathematik.uni-kl.de>
and many others.
Maintained by: Many creative people <dev@texi2html.cvshome.org>
Send bugs and suggestions to <users@texi2html.cvshome.org>
-->
<head>
<title>CentOS Artwork Repository: 2.4 The trunk/Identity Directory</title>
<meta name="description" content="CentOS Artwork Repository: 2.4 The trunk/Identity Directory">
<meta name="keywords" content="CentOS Artwork Repository: 2.4 The trunk/Identity Directory">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.76">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">
<!--
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
a.summary-letter {text-decoration: none}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: serif; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: serif; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.sansserif {font-family:sans-serif; font-weight:normal;}
ul.toc {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="repository_10.html#SEC27" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#SEC29" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_7.html#SEC12" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="repository_7.html#SEC12" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_80.html#SEC416" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="repository_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="repository_80.html#SEC416" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="repository_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Directories-trunk-Identity"></a>
<a name="SEC28"></a>
<h2 class="section"> 2.4 The <tt>`trunk/Identity'</tt> Directory </h2>
<a name="SEC29"></a>
<h3 class="subsection"> 2.4.1 Goals </h3>
<p>The <tt>`trunk/Identity'</tt> directory structure implements <em>The
CentOS Project Corporate Identity</em>.
</p>
<a name="SEC30"></a>
<h3 class="subsection"> 2.4.2 Description </h3>
<p>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.
</p>
<p>The CentOS Project corporate identity provides visibility,
recognizability, reputation, structure and identification to The
CentOS Project organization by means of <em>Corporate Design</em>,
<em>Corporate Communication</em>, and <em>Corporate Behaviour</em>.
</p>
<a name="SEC31"></a>
<h4 class="subsubsection"> 2.4.2.1 Corporate Design </h4>
<p>The CentOS Project corporate design is applied to every single visual
manifestations The CentOS Project as organization wants to express its
existence. Examples of the most relevant visual manifestations inside
The CentOS Project are <em>The CentOS Distribution</em>, <em>The
CentOS Web</em> and <em>The CentOS Stationery</em>.
</p>
<p>The CentOS Project corporate design is organized in the following
work-lines:
</p>
<dl compact="compact">
<dt> <strong>The CentOS Brand</strong></dt>
<dd><p>The CentOS Brand is the name or trademark that connects the producer
with their products. In this case, the producer is The CentOS Project
and the products are The CentOS Project visual manifestations.
</p>
<p>See section <a href="repository_12.html#SEC37">The <tt>`trunk/Identity/Brands'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>The CentOS Colors</strong></dt>
<dd>
<p>The CentOS Fonts provides the color information used along The CentOS
Project visual manifestations.
</p>
<p>See section <a href="repository_13.html#SEC42">The <tt>`trunk/Identity/Colors'</tt> Directory</a>, for more information.
</p></dd>
<dt> <strong>The CentOS Fonts</strong></dt>
<dd>
<p>The CentOS Fonts provides the typography information used along The
CentOS Project visual manifestations.
</p>
<p>See section <a href="repository_14.html#SEC47">The <tt>`trunk/Identity/Fonts'</tt> Directory</a>, for more information.
</p></dd>
<dt> <strong>The CentOS Themes</strong></dt>
<dd>
<p>The CentOS Themes provides structural information and visual style
information, as well, used along The CentOS Project visual
manifestations.
</p>
<p>See section <a href="repository_26.html#SEC117">The <tt>`trunk/Identity/Themes'</tt> Directory</a>, for more information.
</p></dd>
</dl>
<a name="SEC32"></a>
<h4 class="subsubsection"> 2.4.2.2 Corporate Communication </h4>
<p>The CentOS Project corporate communication is based on community
communication. In that sake, the following media are available for
corporate communication:
</p>
<ul class="toc">
<li> The CentOS Mailing Lists (<a class="www" href="http://lists.centos.org/">http://lists.centos.org/</a>).
</li><li> The CentOS Forums (<a class="www" href="http://forums.centos.org/">http://forums.centos.org/</a>).
</li></ul>
<a name="SEC33"></a>
<h4 class="subsubsection"> 2.4.2.3 Corporate Behaviour </h4>
<p>The CentOS Project corporate behaviour is based on community
behaviour.
</p>
<a name="SEC34"></a>
<h4 class="subsubsection"> 2.4.2.4 Corporate Structure </h4>
<p>The CentOS Project corporate structure is based on a <em>monolithic</em>
corporate visual identity structure. In this structure, we use one
unique name (The CentOS Brand) and one unique visual style (The CentOS
Theme) in all The CentOS Project visual manifestations.
</p>
<p>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 web sites, using the distribution, or acting on
social events, the one unique name and one unique visual style
connects them all to say: <em>Hey! we are all part of The CentOS
Project</em>.
</p>
<p>Other corporate structures have been considered as well, but they
introduce visual contradictions we need to be aware of. In that sake,
lets describe the idea of: <em>Producing one different visual style
for each major release of The CentOS Distribution</em>.
</p>
<p>The CentOS Project maintains near to four different major releases of
The CentOS Distribution parallely in time and that fact makes one part
of The CentOS Project structural design, but just one part, not the
complete structural design. In order to produce the correct corporate
structure for The CentOS Project we need to concider all the visual
manifestations The CentOS Project is made of, not just one of them.
</p>
<p>If one different visual style is used for each major release of The
CentOS Distribution, which one of those different visual styles would
be used to cover the remaining visual manifestations The CentOS
Project is made of. Would we end up with four different visual styles,
one for each distribution? In that case, why The CentOS Distribution
we use shows one visual style, The CentOS Web sites another and The
CentOS Stationery even another completly different one? Isn't them
all part of the same project?
</p>
<p>Probably you be thinking, that's right, but The CentOS Brand connects
them all already, why would we need to join them up into the same
visual style too, isn't it more work to do, and harder to maintain?
</p>
<p>Harder to maintain, more work to do, it is probably. Specially when
you consider that The CentOS Project has proven stability and
consistency through time and that, certainly, didn't come through
swinging magical wangs or something but hardly working out to automate
tasks and so providing maintainance through time. Said that, we
consider that The CentOS Project visual structure should be consequent
with such stability and consistency tradition. It is true The CentOS
Brand does connect all the visual manifestations it is present on, but
that connection would be stronger if one unique visual style backups
it. In fact, whatever thing you do to strength the visual connection
among The CentOS Project visual manifestations would be very good in
favor of The CentOS Project recognition.
</p>
<p>Obviously, having just one visual style in all visual manifestations
for eternity would be a very boring thing and would give the idea of a
visually dead project. So, there is no problem on creating a brand new
visual style for each new major release of The CentOS Distribution, in
order to refresh The CentOS Distribution visual style; the problem
does is in not propagating the brand new visual style created for the
new release of CentOS Distribution to all other visual manifestations
The CentOS Project is made of, in a way The CentOS Project could be
recognized no matter what visual manifestation be in front of us. Such
lack of uniformity is what introduces the visual contradition we are
precisely trying to solve by mean of themes production in the CentOS
Artwork Repository.
</p>
<a name="SEC35"></a>
<h3 class="subsection"> 2.4.3 Usage </h3>
<p>The <tt>`trunk/'</tt> directory structure is organized in
<em>renderable</em> and <em>non-renderable</em> directories. Generally,
renderable directories contain two non-renderable directories inside,
one to store design templates (the <tt>`Tpl/'</tt> directory), and other
to store the content produced (the <tt>`Img/'</tt> directory).
</p>
<p>In order to produce content inside rendereble directories, you can use
the following command:
</p>
<pre class="verbatim">centos-art render trunk/Identity/Path/To/Dir
</pre>
<blockquote class="orange"><img src="/home/centos/artwork/trunk/Identity/Widgets/Img/icon-admonition-alert.png" alt="Warning"><h3>Warning</h3><p> If the <code>centos-art</code> command-line
is not found in your workstation, it is probably because you haven't
prepared it for using The CentOS Artwork Repository yet.
See section <a href="repository_79.html#SEC408">The <tt>`trunk/Scripts/Functions/Verify'</tt> Directory</a>, for more
information.
</p></blockquote>
<p>This command takes one design template from the template directory and
creates an instance of it in order to apply translation messages on
it, if any. Later, using the design template instance, the command
renders the final content based on whether the design template
instance is a SVG file or a Docbook file. If the design template
instace is a SVG file, the final content produced is a PNG image. On
the other hand, if the design template instance is a Docbook file, the
final content produced is a XHTML file. Final content is stored in the
image directory using the design template directory paths as referece.
The rendition flow described so far is known as the
<em>base-rendition</em> flow.
</p>
<p>Besides the base-rendition flow, the <code>centos-art</code> provides the
<em>post-rendition</em> and <em>last-rendition</em> flows. The
post-rendition flow is applied to files produced as result of
base-rendition flow under the same directory structure. For example,
you can use post-rendition action to convert the PNG base output into
different outputs (e.g., JPG, PDF, etc.) before passing to process the
next file in the same directory structure. The last-rendition flow is
applied to all files produced as result of both base-rendition and
post-rendition flows in the same directory structure, just before
passing to process a different directory structure. For example, the
<tt>`Preview.png'</tt> image from Ksplash component is made of three
images. In order to build the <tt>`Preview.png'</tt> image through
<code>centos-art</code> we need to wait for all the three images the
<tt>`Preview.png'</tt> image is made of to be rendered, so we can combine
them all together into just one image (i.e., the <tt>`Preview.png'</tt>
image). This is something we can't do using post-rendition flow.
</p>
<p>Inside <tt>`trunk/Identity'</tt> directory structure, you can find that
base-rendition, post-rendition and last-rendition flows can be
combined to build <em>directory-specific</em> rendition. The
directory-specific rendition exists to automatically process specific
renderable directories in very specific ways. Using directory-specific
rendition speeds up production of different components like Syslinux,
Grub, Gdm, Kdm and Ksplash that require intermediate formats or even
several independent files, in order to reach its final construction.
Directory-specific rendition is a way to programmatically describe how
specific art works are built in and organized inside The CentOS
Artwork Repository. Such descriptions have been added to
<code>centos-art</code> command-line to let you produce them all with
just one single command, as fast as your machine can be able to handle
it.
</p>
<p>See section <a href="repository_71.html#SEC352">The <tt>`trunk/Scripts/Functions/Identity'</tt> Directory</a>, for more
information about the <code>identity</code> functionality of
<code>centos-art</code> command-line interface.
</p>
<a name="SEC36"></a>
<h3 class="subsection"> 2.4.4 See also </h3>
<p>See <a class="www" href="http://en.wikipedia.org/Corporate_identity">http://en.wikipedia.org/Corporate_identity</a> (and related
links), for general information on corporate identity.
</p>
<p>Specially useful has been, and still be, the book <em>Corporate
Identity</em> by Wally Olins (1989). This book provides many conceptual
ideas we've used as base to build The CentOS Artwork Repository.
</p>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#SEC35" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="repository_12.html#SEC37" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_7.html#SEC12" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC28" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_80.html#SEC416" title="Next chapter"> >> </a>]</td>
</tr></table>
<p>
<font size="-1">
This document was generated on <i>March, 22 2011</i> using <a class="www" href="http://texi2html.cvshome.org/"><i>texi2html 1.76</i></a>.
</font>
<br>
</p>
</body>
</html>