Blame Manual/Repository/trunk/Identity.texi

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