<!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, 6 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.21 The trunk/Identity/Themes/Models/Default Directory</title>
<meta name="description" content="CentOS Artwork Repository: 2.21 The trunk/Identity/Themes/Models/Default Directory">
<meta name="keywords" content="CentOS Artwork Repository: 2.21 The trunk/Identity/Themes/Models/Default 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_24.html#SEC114" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#SEC116" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_78.html#SEC405" 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_78.html#SEC405" 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="Filesystem-trunk-Identity-Themes-Models-Default"></a>
<a name="SEC115"></a>
<h2 class="section"> 2.21 The <tt>`trunk/Identity/Themes/Models/Default'</tt> Directory </h2>
<a name="SEC116"></a>
<h3 class="subsection"> 2.21.1 Goals </h3>
<p>Default Design Models for CentOS Themes provide design models for the
following components:
</p>
<dl compact="compact">
<dt> <strong>Distribution</strong></dt>
<dd><p>Design models for CentOS Distribution (e.g., Anaconda, Firstboot, Gdm,
Grub, Gsplash, Kdm, Ksplash, Rhgb and Syslinux, etc.).
See section <a href="repository_27.html#SEC125">The <tt>`trunk/Identity/Themes/Models/Default/Distro'</tt> Directory</a>, for
more information.
</p>
</dd>
<dt> <strong>Concept</strong></dt>
<dd><p>Design models to illustrate Artistic Motifs Concepts.
See section <a href="repository_26.html#SEC120">The <tt>`trunk/Identity/Themes/Models/Default/Concept'</tt> Directory</a>, for
more information.
</p>
</dd>
<dt> <strong>Promotion</strong> </dt>
<dd><p>Design models for CentOS Promotion stuff (e.g., installation media,
posters, etc.). See section <a href="repository_37.html#SEC175">The <tt>`trunk/Identity/Themes/Models/Default/Promo'</tt> Directory</a>, for more information.
</p></dd>
</dl>
<a name="SEC117"></a>
<h3 class="subsection"> 2.21.2 Description </h3>
<p>This directory implements the concept of <em>Default Design Models
for CentOS Themes</em>. Default Design Models for CentOS Themes provide
the common structural information (e.g., image dimensions, translation
markers, trademark position, etc.) the <code>centos-art</code> script
uses to produce images when no other design model is specified.
</p>
<p>Deisgn models in this directory do use the <em>CentOS Release
Brand</em>. The CentOS Release Brand is a combination of both The CentOS
Type and The CentOS Release Schema used to illustrate the major
release of CentOS Distribution the image produced belongs to.
See section <a href="repository_18.html#SEC70">The <tt>`trunk/Identity/Models/Tpl/Brands'</tt> Directory</a>, for more
information.
</p>
<a name="SEC118"></a>
<h3 class="subsection"> 2.21.3 Usage </h3>
<p>The CentOS Project maintains near to four different major releases of
CentOS Distribution. Each major release of CentOS Distribution has
internal differences that make them unique and, at the same time, each
CentOS Distribution individually is tagged into the one unique visual
manifestation (i.e., Distribution). So, how could we implement the
monolithic visual structure in one visual manifestation that has
internal difference?
</p>
<p>To answer this question we broke the question in two parts and later
combined the resultant answers to build a possible solution.
</p>
<dl compact="compact">
<dt> <strong>How to remark the internal differences visually?</strong></dt>
<dd>
<p>Merge both The CentOS Project Release Schema into The CentOS Project
Trademark to build The CentOS Project Release Trademark. The CentOS
Project Release Trademark remarks two things: first, it remarks the
image is from The CentOS Project and second, it remarks which major
release of CentOS Distribution does the image belongs to.
See section <a href="repository_18.html#SEC70">The <tt>`trunk/Identity/Models/Tpl/Brands'</tt> Directory</a>, for more
information on how to develop and improve The CentOS Project Brand.
</p>
</dd>
<dt> <strong>How to remark the visual resemblance?</strong></dt>
<dd>
<p>Use a common artistic motifs as background for all CentOS Distribution
images. See section <a href="repository_39.html#SEC185">The <tt>`trunk/Identity/Themes/Motifs'</tt> Directory</a>, for more
information.
</p>
</dd>
<dt> <strong>So, combining answers above, we could conclude that:</strong></dt>
<dd>
<p>In order to implement the CentOS Monolithic Visual Structure on CentOS
Distribution visual manifestations, a CentOS Release Trademark and a
background information based on one unique artistic motif should be
used in all remarkable images The CentOS Distribution visual
manifestation is made of.
</p></dd>
</dl>
<blockquote class="orange"><img src="/home/centos/artwork/trunk/Identity/Widgets/Img/icon-admonition-star.png" alt="Important"><h3>Important</h3><p> Remarking the CentOS Release Schema inside each
major release of CentOS Distribution --or similar visual
manifestations-- takes <em>high attention</em> inside The CentOS
Project corporate visual identity. It should be very clear for
everyone which major release of CentOS Distribution is being used.
</p></blockquote>
<p>Other recommendations have been discussed in CentOS Developers mailing
list (<a class="mailto" href="mailto:centos-devel@centos.org">centos-devel@centos.org</a>). One of them is producing one
unique visual style for <em>each</em> major release of CentOS
Distribution. That is, if we have four different major releases of
CentOS Distribution, we need to provide four different visual styles
to cover each CentOS Distribution artistic needs. Even such schema
could be produced inside CentOS Artwork Repository, using it could
introduce visual isolation to different visual manifestations of The
CentOS Project.
</p>
<p>As previously said, The CentOS Project maintains near to four
different major releases of CentOS Distribution in parallel and that
fact creates a complete different perspective since the structural
point of view. If one unique visual style is used for <em>each</em>
major release of CentOS Distribution, which one of those different
visual styles would be used to cover other visual manifestations, like
The CentOS Web sites and The CentOS Promotion stuff?
</p>
<p>Some persons may end up asking themselves, why the CentOS Distribution
I am using has this visual style and the CentOS Web sites a different
one? Isn't them all part of the same project?
</p>
<p>Creating a linear and uniform visual style for all visual
manifestations of The CentOS Project does create a strong feeling of
integrity, order and property on persons interacting with the project
through its manifestations. Every single detail, in every
manifestation The CentOS Project expresses out its existence say what
The CentOS Project is.
</p>
<p>I don't think The CentOS Project as an ambiguous project, but a direct
and very pragmatic project where its community makes the central axis
of movement. A manifestation of freedom to people to use computers and
share as natural right. A manifestation of people kindness whose make
the best they know to do in favor of themselves as manifestation of
everyone else. In such feeling there is no space for contradictions
or ununiform visual structures, but very uniform visual structures
that can be altered by anyone to fit personal needs.
</p>
<p>I strongly believe that The CentOS Project, as social organization,
should be that way uniform and provide the means to let everyone do
customzations in their own basis whenever it be clear that once such
uniformity has been changed by someone differnt to The CentOS Project,
it is no longer a visual manifestation of The CentOS Project, but a
modified visual manifestation of The CentOS Project.
</p>
<a name="SEC119"></a>
<h3 class="subsection"> 2.21.4 See also </h3>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="repository_22.html#SEC100">2.18 The <tt>`trunk/Identity/Themes'</tt> Directory</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="repository_23.html#SEC105">2.19 The <tt>`trunk/Identity/Themes/Models'</tt> Directory</a></td><td> </td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="repository_39.html#SEC185">2.35 The <tt>`trunk/Identity/Themes/Motifs'</tt> Directory</a></td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#SEC118" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="repository_26.html#SEC120" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC115" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_78.html#SEC405" title="Next chapter"> >> </a>]</td>
</tr></table>
<p>
<font size="-1">
This document was generated on <i>March, 6 2011</i> using <a class="www" href="http://texi2html.cvshome.org/"><i>texi2html 1.76</i></a>.
</font>
<br>
</p>
</body>
</html>