Blame Manuals/Filesystem/filesystem-html/filesystem_21.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
-->
010b2d
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>
d05905
<title>CentOS Artwork Repository - Filesystem: 3.18 trunk/Identity/Themes/Models/Default/Distro</title>
ee1f37
d05905
<meta name="description" content="CentOS Artwork Repository - Filesystem: 3.18 trunk/Identity/Themes/Models/Default/Distro">
d05905
<meta name="keywords" content="CentOS Artwork Repository - Filesystem: 3.18 trunk/Identity/Themes/Models/Default/Distro">
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
db14a4
[ < ]
ee1f37
[ > ]
ee1f37
   
db14a4
[ << ]
db14a4
[ Up ]
193ea4
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
db14a4
[Top]
db14a4
[Contents]
193ea4
[Index]
db14a4
[ ? ]
ee1f37
ee1f37
ee1f37
ee1f37

3.18 trunk/Identity/Themes/Models/Default/Distro

ee1f37
ee1f37
ee1f37
ee1f37

3.18.1 Goals

ee1f37
ee1f37
    ee1f37
  • ...
  • ee1f37
    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.18.2 Description

    ee1f37
    ee1f37

    It applies to all major releases of CentOS distribution.

    ee1f37

    ee1f37
    ee1f37
    ee1f37

    3.18.2.1 One theme for all major releases

    ee1f37
    ee1f37

    Sometimes, specific visual manifestations are formed by common

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

    ee1f37

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

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

    ee1f37
    Important

    Important

    Remarking the CentOS release schema inside each

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

    ee1f37
    ee1f37

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

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

    ee1f37
    ee1f37
    ee1f37

    3.18.2.2 One theme for each major release

    ee1f37
    ee1f37

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

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

    ee1f37

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

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

    ee1f37

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

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

    ee1f37

    In whatever case you choose some release-specific distribution user

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

    ee1f37
    ee1f37
    ee1f37

    3.18.3 Usage

    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.18.4 See also

    ee1f37
    ee1f37
    ee1f37
    ee1f37
    ee1f37
    [ < ]
    db14a4
    [ > ]
    ee1f37
       
    db14a4
    [ << ]
    ee1f37
    [ Up ]
    193ea4
    [ >> ]
    ee1f37
    ee1f37

    ee1f37
     <font size="-1">
    010b2d
      This document was generated on February, 28 2011 using texi2html 1.76.
    ee1f37
     </font>
    ee1f37
     
    ee1f37
    ee1f37

    ee1f37
    </body>
    ee1f37
    </html>