Blame Manual/repository-html/repository_22.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>
b130a0
<title>CentOS Artwork Repository: 1.21 The trunk/Identity/Themes/Models/Default/Distro Directory</title>
ee1f37
b130a0
<meta name="description" content="CentOS Artwork Repository: 1.21 The trunk/Identity/Themes/Models/Default/Distro Directory">
b130a0
<meta name="keywords" content="CentOS Artwork Repository: 1.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
b130a0
[ < ]
b130a0
[ > ]
ee1f37
   
aaf678
[ << ]
aaf678
[ Up ]
b130a0
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
56a476
[Top]
56a476
[Contents]
b130a0
[Index]
56a476
[ ? ]
ee1f37
b130a0
b130a0
b130a0

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

ee1f37
ee1f37
b130a0
aaf678

1.21.1 Goals

ee1f37
ee1f37
    ee1f37
  • ...
  • ee1f37
    ee1f37
    ee1f37
    b130a0
    aaf678

    1.21.2 Description

    ee1f37
    b130a0

    It applies to all major releases of CentOS distribution.

    b130a0

    b130a0
    b130a0
    b130a0

    1.21.2.1 One theme for all major releases

    b130a0
    b130a0

    Sometimes, specific visual manifestations are formed by common

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

    b130a0

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

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

    b130a0
    Important

    Important

    Remarking the CentOS release schema inside each

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

    b130a0
    b130a0

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

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

    b130a0
    b130a0
    b130a0

    1.21.2.2 One theme for each major release

    b130a0
    b130a0

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

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

    b130a0

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

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

    b130a0

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

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

    b130a0

    In whatever case you choose some release-specific distribution user

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

    ee1f37
    aaf678
    aaf678

    1.21.3 Usage

    ee1f37
    ee1f37
    aaf678
    aaf678

    1.21.4 See also

    ee1f37
    ee1f37
    ee1f37
    ee1f37
    aaf678
    [ < ]
    aaf678
    [ > ]
    ee1f37
       
    aaf678
    [ << ]
    b130a0
    [ Up ]
    b130a0
    [ >> ]
    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>