Blame Manuals/en/Html/Repository/repository_17.html

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

3.14 trunk/Identity/Themes/Models/Default/Distro

4c79b5
4c79b5
1a6d31
4c79b5

3.14.1 Goals

4c79b5
4c79b5
    4c79b5
  • ...
  • 4c79b5
    4c79b5
    4c79b5
    1a6d31
    4c79b5

    3.14.2 Description

    4c79b5
    bc3531

    It applies to all major releases of CentOS distribution.

    4c79b5

    4c79b5
    1a6d31
    bc3531

    3.14.2.1 One theme for all major releases

    bc3531
    bc3531

    Sometimes, specific visual manifestations are formed by common

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

    bc3531

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

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

    bc3531
    Important

    Important

    Remarking the CentOS release schema inside each

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

    bc3531
    bc3531

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

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

    bc3531
    1a6d31
    bc3531

    3.14.2.2 One theme for each major release

    bc3531
    bc3531

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

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

    bc3531

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

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

    bc3531

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

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

    bc3531

    In whatever case you choose some release-specific distribution user

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

    4c79b5
    1a6d31
    4c79b5

    3.14.3 Usage

    4c79b5
    4c79b5
    1a6d31
    4c79b5

    3.14.4 See also

    4c79b5
    4c79b5
    4c79b5
    4c79b5
    1a6d31
    [ < ]
    1a6d31
    [ > ]
    4c79b5
       
    4c79b5
    [ << ]
    1a6d31
    [ Up ]
    1a6d31
    [ >> ]
    4c79b5
    4c79b5

    4c79b5
     <font size="-1">
    1a6d31
      This document was generated on October, 2 2010 using texi2html 1.76.
    4c79b5
     </font>
    4c79b5
     
    4c79b5
    4c79b5

    4c79b5
    </body>
    4c79b5
    </html>