Blame Manual/repository-html/repository_26.html

ee1f37
ee1f37
<html>
ee1f37
ee1f37
ee1f37
Permission is granted to copy, distribute and/or modify this document
ee1f37
under the terms of the GNU Free Documentation License, Version 1.2 or
ee1f37
any later version published by the Free Software Foundation; with no
ee1f37
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
ee1f37
copy of the license is included in the section entitled GNU Free
ee1f37
Documentation License.  
ee1f37
-->
406f69
ee1f37
ee1f37
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
ee1f37
            Karl Berry  <karl@freefriends.org>
ee1f37
            Olaf Bachmann <obachman@mathematik.uni-kl.de>
ee1f37
            and many others.
ee1f37
Maintained by: Many creative people <dev@texi2html.cvshome.org>
ee1f37
Send bugs and suggestions to <users@texi2html.cvshome.org>
ee1f37
ee1f37
-->
ee1f37
<head>
f66721
<title>CentOS Artwork Repository: 2.21 The trunk/Identity/Themes/Models/Default/Distro Directory</title>
ee1f37
f66721
<meta name="description" content="CentOS Artwork Repository: 2.21 The trunk/Identity/Themes/Models/Default/Distro Directory">
f66721
<meta name="keywords" content="CentOS Artwork Repository: 2.21 The trunk/Identity/Themes/Models/Default/Distro Directory">
ee1f37
<meta name="resource-type" content="document">
ee1f37
<meta name="distribution" content="global">
ee1f37
<meta name="Generator" content="texi2html 1.76">
ee1f37
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
ee1f37
<style type="text/css">
ee1f37
ee1f37
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
ee1f37
ee1f37
a.summary-letter {text-decoration: none}
ee1f37
pre.display {font-family: serif}
ee1f37
pre.format {font-family: serif}
ee1f37
pre.menu-comment {font-family: serif}
ee1f37
pre.menu-preformatted {font-family: serif}
ee1f37
pre.smalldisplay {font-family: serif; font-size: smaller}
ee1f37
pre.smallexample {font-size: smaller}
ee1f37
pre.smallformat {font-family: serif; font-size: smaller}
ee1f37
pre.smalllisp {font-size: smaller}
ee1f37
span.sansserif {font-family:sans-serif; font-weight:normal;}
ee1f37
ul.toc {list-style: none}
ee1f37
-->
ee1f37
</style>
ee1f37
ee1f37
ee1f37
</head>
ee1f37
ee1f37
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
ee1f37
ee1f37
f66721
[ < ]
f66721
[ > ]
ee1f37
   
f66721
[ << ]
f66721
[ Up ]
f66721
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
56a476
[Top]
56a476
[Contents]
f66721
[Index]
56a476
[ ? ]
ee1f37
f66721
f66721
f66721

2.21 The <tt>`trunk/Identity/Themes/Models/Default/Distro'</tt> Directory

aaf678
982d5c
f66721
f66721

2.21.1 Goals

982d5c
b130a0
    b9dbd3
  • ...
  • b130a0
    b130a0
    b130a0
    f66721
    f66721

    2.21.2 Description

    ee1f37
    f66721

    It applies to all major releases of CentOS distribution.

    f66721

    aaf678
    f66721
    f66721

    2.21.2.1 One theme for all major releases

    f66721
    f66721

    Sometimes, specific visual manifestations are formed by common

    f66721
    components which have internal differences. That is the case of CentOS
    f66721
    distribution visual manifestation.  
    f66721

    f66721

    Since a visual style point of view, the CentOS distributions share

    f66721
    common artwork components like Anaconda --to cover the CentOS
    f66721
    distribution installation--, BootUp --to cover the CentOS
    f66721
    distribution start up--, and Backgrounds --to cover the CentOS
    f66721
    distribution desktop--.  Now, since a technical point of view, those
    f66721
    common artwork components are made of software improved constantly.
    f66721
    So, we need to find a way to keep one unique name and one unique
    f66721
    visual style in artwork components that have internal difference and
    f66721
    also remark internal difference as well.
    f66721

    f66721
    Important

    Important

    Remarking the CentOS release schema inside each

    f66721
    major release of CentOS distribution --or similar visual
    f66721
    manifestation-- takes high attention inside The CentOS Project
    f66721
    corporate visual identity. It should be very clear for people which
    f66721
    major release of CentOS distribution they are using.
    f66721

    f66721
    f66721

    In order to remark the CentOS release schema, the CentOS Artwork SIG

    f66721
    uses a release-specific brand design named "The CentOS Release
    f66721
    Brand". The CentOS release brand is compossed by the CentOS logotype
    f66721
    and the CentOS major release number (as specified in CentOS
    f66721
    release schema definition). In this solution, the CentOS release brand
    f66721
    is set inside all release-specific artworks (e.g., distribution,
    f66721
    installation media, etc.) in remarkable way.   The CentOS release
    f66721
    brand is the design component that lets us remark the CentOS release
    f66721
    schema inside the monolithic corporate visual identity structure we
    f66721
    propose to use.
    f66721

    b130a0
    f66721
    f66721

    2.21.2.2 One theme for each major release

    b130a0
    f66721

    Other way we've been using to remark CentOS release schema is

    f66721
    applying one unique theme for each major release of CentOS
    f66721
    distribution.  That is, if we have 4 major releases of CentOS
    f66721
    distribution, we need to provide 4 different themes to cover each
    f66721
    CentOS distribution available.
    f66721

    f66721

    Inside CentOS Artwork Repository, you can create many themes and that

    f66721
    is very convenient. But using one unique theme for each major
    f66721
    release of CentOS distribution would bring visual isolation among
    f66721
    distributions, websites and promotion visual manifestations. If the
    f66721
    CentOS project would maintain just one CentOS distribution (and many
    f66721
    experienced graphic designers ready to create beautiful artworks) this
    f66721
    model would be nice. Indeed, this model looks quite similar to that
    f66721
    one used by Fedora project, doesn't it. But no, the CentOS project
    f66721
    maintains near to 4 major releases of CentOS distribution in parallel,
    f66721
    and that fact makes a huge difference since the corporate visual
    f66721
    identity point of view.
    f66721

    f66721

    If we use one unique theme for each major release of CentOS

    f66721
    distribution, which one of those themes, does we use to cover other
    f66721
    CentOS visual manifestations, like websites and promotion stuff? 
    f66721

    f66721

    In whatever case you choose some release-specific distribution user

    f66721
    will be visually isolated from other CentOS visual manifestations like
    f66721
    websites and promotion stuff, even if the CentOS brand is present in
    f66721
    all visual manifestations. In such a case, probably, users will end up
    f66721
    asking themselves, why my CentOS distribution has this design and the
    f66721
    CentOS website another one? Isn't them on the same project? With luck
    f66721
    the CentOS brand will exonerate user form visual isolation.
    f66721

    f66721
    f66721
    f66721

    2.21.3 Usage

    f66721
    f66721
    f66721
    f66721

    2.21.4 See also

    ee1f37
    ee1f37
    ee1f37
    ee1f37
    f66721
    [ < ]
    f66721
    [ > ]
    ee1f37
       
    f66721
    [ << ]
    f66721
    [ Up ]
    f66721
    [ >> ]
    ee1f37
    ee1f37

    ee1f37
     <font size="-1">
    406f69
      This document was generated on March, 1 2011 using texi2html 1.76.
    ee1f37
     </font>
    ee1f37
     
    ee1f37
    ee1f37

    ee1f37
    </body>
    ee1f37
    </html>