Blame Manuals/Filesystem/filesystem-html/filesystem_14.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.11 trunk/Identity/Models/Tpl/Promo/Web</title>
ee1f37
d05905
<meta name="description" content="CentOS Artwork Repository - Filesystem: 3.11 trunk/Identity/Models/Tpl/Promo/Web">
d05905
<meta name="keywords" content="CentOS Artwork Repository - Filesystem: 3.11 trunk/Identity/Models/Tpl/Promo/Web">
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 ]
7ba52f
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
db14a4
[Top]
db14a4
[Contents]
7ba52f
[Index]
db14a4
[ ? ]
ee1f37
ee1f37
ee1f37
ee1f37

3.11 trunk/Identity/Models/Tpl/Promo/Web

ee1f37
ee1f37
ee1f37
ee1f37

3.11.1 Goals

ee1f37
ee1f37

Organize scalable vector graphics (svg) to help describe the CentOS

ee1f37
web environment.
ee1f37

ee1f37
ee1f37
ee1f37

3.11.2 The CentOS web environment

ee1f37
ee1f37

Inside CentOS corporate identity, the CentOS web environment is

ee1f37
considered a promotion component. The CentOS web environment is formed
ee1f37
by a central web application --to cover base needs (e.g., per-major
ee1f37
release information like release notes, lifetime, downloads,
ee1f37
documentation, support, security advisories, bugs, etc.)-- and many
ee1f37
different free web applications --to cover specific needs (e.g.,
ee1f37
wiki, mailing lists, etc.)--. 
ee1f37

ee1f37

The CentOS web environment is addressed to solve the following issues:

ee1f37

ee1f37
    ee1f37
  • One unique name and one unique visual style to all web
  • ee1f37
    applications used inside the web environment.
    ee1f37
    ee1f37
  • One-step navigation to web applications inside the environment.
  • ee1f37
    ee1f37
  • High degree of customization to change the visual style of all
  • ee1f37
    web applications with few changes (e.g, updating just two or three
    ee1f37
    images plus common style sheet [CSS] definitions).
    ee1f37
    ee1f37
    ee1f37

    The CentOS project is attached to a monolithic corporate visual

    db14a4
    identity (see section trunk/Identity), where all visual manifestations
    ee1f37
    have one unique name and one unique visual style. This way, the CentOS
    ee1f37
    web environment has one unique name (the CentOS brand) and one unique
    ee1f37
    visual style (the CentOS default theme) for all its visual
    ee1f37
    manifestations, the web applications in this case.
    ee1f37

    ee1f37

    Since a maintainance point of view, achiving the one unique visual

    ee1f37
    style inside CentOS web environment is not a simple task. The CentOS
    ee1f37
    web environment is built upon many different web applications which
    ee1f37
    have different visual styles and different internal ways to customize
    ee1f37
    their own visual styles. For example: MoinMoin, the web application
    ee1f37
    used to support the CentOS wiki (http://wiki.centos.org/) is
    ee1f37
    highly customizable but Mailman (in its 2.x.x serie), the web
    ee1f37
    application used to support the CentOS mailing list, doesn't
    db14a4
    support(1) a customization system that separates
    ee1f37
    presentation from logic, similar to that used by MoinMoin.
    ee1f37

    ee1f37

    This visual style diversity complicates our goal of one unique visual

    ee1f37
    style for all web applications. So, if we want one unique visual style
    ee1f37
    for all web applications used, it is innevitable to modify the web
    ee1f37
    applications in order to implement the CentOS one unique visual style
    ee1f37
    customization in them. Direct modification of upstream applications is
    ee1f37
    not convenient because upstream applications come with their one
    ee1f37
    visual style and administrators take the risk of loosing all
    ee1f37
    customization changes the next time the application be updated (since
    ee1f37
    not all upstream web applications, used in CentOS web environment,
    ee1f37
    separate presentation from logic).
    ee1f37

    ee1f37

    To solve the "one unique visual style" issue, installation and

    ee1f37
    actualization of web applications --used inside CentOS web
    ee1f37
    environment-- need to be independent from upstream web applications
    ee1f37
    development line; in a way that CentOS web environment administrators
    ee1f37
    can install and update web applications freely without risk of loosing
    ee1f37
    the one unique visual style customization changes. 
    ee1f37

    ee1f37

    At the surface of this issue we can see the need of one specific yum

    ee1f37
    repository to store CentOS web environment customized web applications.
    ee1f37

    ee1f37
    ee1f37
    ee1f37

    3.11.2.1 Design model (without ads)

    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.2 Design model (with ads)

    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.3 HTML definitions

    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.4 Controlling visual style

    ee1f37
    ee1f37

    Inside CentOS web environment, the visual style is controlled by the

    ee1f37
    following compenents:
    ee1f37

    ee1f37
    ee1f37
    Webenv header background
    ee1f37
    trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png
    ee1f37
    ee1f37
    ee1f37
    CSS definitions
    ee1f37
    trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css
    ee1f37
    ee1f37
    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.5 Producing visual style

    ee1f37
    ee1f37

    The visual style of CentOS web environment is defined in the following

    ee1f37
    files:
    ee1f37

    ee1f37
    trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Xcf/1024x250.xcf
    ee1f37
    trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png
    ee1f37
    trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250-bg.png
    ee1f37
    trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Tpl/1024x250.svg
    ee1f37
    ee1f37

    As graphic designer you use <tt>`1024x250.xcf'</tt> file to produce

    ee1f37
    <tt>`1024x250-bg.png'</tt> file. Later, inside <tt>`1024x250.svg'</tt> file,
    ee1f37
    you use the <tt>`1024x250-bg.png'</tt> file as background layer to draw
    ee1f37
    your vectorial design. When you consider you artwork ready, use the
    ee1f37
    centos-art.sh script, as described below, to produce the
    ee1f37
    visual style controller images of CentOS web environment.
    ee1f37

    ee1f37
    centos-art render --entry=trunk/Identity/Themes/Motifs/$THEME/Backgrounds --filter='1024x250'
    ee1f37
    ee1f37

    Once you have rendered required image files, changing the visual style

    ee1f37
    of CentOS web environment is a matter of replacing old image files
    ee1f37
    with new ones, inside webenv repository file system structure. The
    ee1f37
    visual style changes will take effect the next time customization line
    ee1f37
    of CentOS web applications be packaged, uploded, and installed from
    ee1f37
    [webenv] or [webenv-test] repositories.
    ee1f37

    ee1f37
    ee1f37
    ee1f37

    3.11.2.6 Navigation

    ee1f37
    ee1f37

    Inside CentOS web environment, the one-step navegation between web

    ee1f37
    applications is addressed using the web environment navigation bar.
    ee1f37
    The web environment navigation bar contains links to main applications
    ee1f37
    and is always visible no matter where you are inside the web
    ee1f37
    environment.
    ee1f37

    ee1f37
    ee1f37
    ee1f37

    3.11.2.7 Development and release cycle

    ee1f37
    ee1f37

    The CentOS web environment development and relase cycle is described

    ee1f37
    below: 
    ee1f37

    ee1f37
    ee1f37
    Download
    ee1f37
    ee1f37

    The first action is download the source code of web applications we

    ee1f37
    want to use inside CentOS web environment.
    ee1f37

    ee1f37
    Important

    Important

    The source location from which web application are

    ee1f37
    downloaded is very important. Use SRPMs from CentOS [base]
    ee1f37
    and [updates] repositories as first choise, and third party
    ee1f37
    repositories (e.g. RPMForge, EPEL, etc.) as last resource.
    ee1f37

    ee1f37
    ee1f37
    ee1f37
    Prepare
    ee1f37
    ee1f37

    Once web application source code has been downloaded, our duty is

    ee1f37
    organize its files inside <samp>`webenv'</samp> version controlled repository.
    ee1f37

    ee1f37

    When preparing the structure keep in mind that different web

    ee1f37
    applications have different visual styles, and also different ways to
    ee1f37
    implement it. A convenient way to organize the file system structure
    ee1f37
    would be create one development line for each web application we use
    ee1f37
    inside CentOS web environment. For example, consider the following
    ee1f37
    file system structure:
    ee1f37

    ee1f37
    https://projects.centos.org/svn/webenv/trunk/
    ee1f37
    |-- WebApp1/
    ee1f37
    |   |-- Sources/
    ee1f37
    |   |   `-- webapp1-0.0.1/
    ee1f37
    |   |-- Rpms/
    ee1f37
    |   |   `-- webapp1-0.0.1.rpm
    ee1f37
    |   |-- Srpms/
    ee1f37
    |   |   `-- webapp1-0.0.1.srpm
    ee1f37
    |   `-- Specs/
    ee1f37
    |       `-- webapp1-0.0.1.spec
    ee1f37
    |-- WebApp2/
    ee1f37
    `-- WebAppN/
    ee1f37
    ee1f37
    ee1f37
    Customize
    ee1f37
    ee1f37

    Once web applications have been organized inside the version

    ee1f37
    controlled repository file system, use subversion to create the CentOS
    ee1f37
    customization development line of web applications source code.  For
    ee1f37
    example, using the above file system structure, you can create the
    ee1f37
    customization development line of <tt>`webapp1-0.0.1/'</tt> with the
    ee1f37
    following command:
    ee1f37

    ee1f37
    svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv
    ee1f37
    ee1f37

    The command above creates the following structure:

    ee1f37

    ee1f37
    https://projects.centos.org/svn/webenv/trunk/
    ee1f37
    |-- WebApp1/
    ee1f37
    |   |-- Sources/
    ee1f37
    |   |   |-- webapp1-0.0.1/
    ee1f37
    |   |   `-- webapp1-0.0.1-webenv/
    ee1f37
    |   |-- Rpms/
    ee1f37
    |   |   `-- webapp1-0.0.1.rpm
    ee1f37
    |   |-- Srpms/
    ee1f37
    |   |   `-- webapp1-0.0.1.srpm
    ee1f37
    |   `-- Specs/
    ee1f37
    |       `-- webapp1-0.0.1.spec
    ee1f37
    |-- WebApp2/
    ee1f37
    `-- WebAppN/
    ee1f37
    ee1f37

    In the above structure, the <tt>`webapp1-0.0.1-webenv/'</tt> directory is

    ee1f37
    the place where you customize the visual style of
    ee1f37
    <tt>`webapp1-0.0.1/'</tt> web application. 
    ee1f37

    ee1f37
    Info

    Tip

    Use the diff command of Subversion between

    ee1f37
    CentOS customization and upstream development lines to know what you
    ee1f37
    are changing exactly.
    ee1f37

    ee1f37
    ee1f37
    ee1f37
    Build packages
    ee1f37
    ee1f37

    When web application has been customized, build the web application

    ee1f37
    RPM and SRPM using the source location with <samp>`-webenv'</samp> prefix. 
    ee1f37

    ee1f37
    https://projects.centos.org/svn/webenv/trunk/
    ee1f37
    |-- WebApp1/
    ee1f37
    |   |-- Sources/
    ee1f37
    |   |   |-- webapp1-0.0.1/
    ee1f37
    |   |   `-- webapp1-0.0.1-webenv/
    ee1f37
    |   |-- Rpms/
    ee1f37
    |   |   |-- webapp1-0.0.1.rpm
    ee1f37
    |   |   `-- webapp1-0.0.1-webenv.rpm
    ee1f37
    |   |-- Srpms/
    ee1f37
    |   |   |-- webapp1-0.0.1.srpm
    ee1f37
    |   |   `-- webapp1-0.0.1-webenv.srpm
    ee1f37
    |   `-- Specs/
    ee1f37
    |       |-- webapp1-0.0.1.spec
    ee1f37
    |       `-- webapp1-0.0.1-webenv.spec
    ee1f37
    |-- WebApp2/
    ee1f37
    `-- WebAppN/
    ee1f37
    ee1f37
    ee1f37
    Release for testing
    ee1f37
    ee1f37

    When the customized web application has been packaged, make packages

    ee1f37
    available for testing and quality assurance. This can be achives using
    ee1f37
    a [webenv-test] yum repository. 
    ee1f37

    ee1f37
    info

    Note

    The [webenv-test] repository is not shipped inside

    ee1f37
    CentOS distribution default yum configuraiton. In order to use
    ee1f37
    [webenv-test] repository you need to configure it first.
    ee1f37

    ee1f37
    ee1f37

    If some problem is found to install/update/use the customized version

    ee1f37
    of web application, the problem is notified somewhere (a bugtracker
    ee1f37
    maybe) and the customization face is repated in order to fix the
    ee1f37
    problem. To release the new package add a number after <samp>`-webenv'</samp>
    ee1f37
    prefix. For example, if some problem is found in
    ee1f37
    <tt>`webapp1-0.0.1-webenv.rpm'</tt>, when it be fixed the new package will
    ee1f37
    be named <tt>`webapp1-0.0.1-webenv-1.rpm'</tt>. If a problem is found in
    ee1f37
    <tt>`webapp1-0.0.1-webenv-1.rpm'</tt>, when it be fixed the new package
    ee1f37
    will be named <tt>`webapp1-0.0.1-webenv-2.rpm'</tt>, and so on.
    ee1f37

    ee1f37

    The "customization -- release for testing" process is repeated

    ee1f37
    until CentOS quality assurance team considers the package is ready for
    ee1f37
    production.
    ee1f37

    ee1f37
    ee1f37
    Release for production
    ee1f37
    ee1f37

    When customized web application packages are considered ready for

    ee1f37
    production they are moved from [webenv-test] to [webenv] repository.
    ee1f37
    This action is commited by CentOS quality assurance team.
    ee1f37

    ee1f37
    info

    Note

    The [webenv] repository is not shipped inside CentOS

    ee1f37
    distribution default yum configuraiton. In order to use [webenv]
    ee1f37
    repository you need to configure it first.
    ee1f37

    ee1f37
    ee1f37
    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.8 The [webenv-test] repository

    ee1f37
    ee1f37
    /etc/yum.repos.d/CentOS-Webenv-test.repo
    ee1f37
    ee1f37
    [webenv-test]
    ee1f37
    name=CentOS-$releasever - Webenv-test
    ee1f37
    mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test
    ee1f37
    #baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/
    ee1f37
    gpgcheck=1
    ee1f37
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
    ee1f37
    enabled=1
    ee1f37
    priority=10
    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.9 The [webenv] repository

    ee1f37
    ee1f37
    /etc/yum.repos.d/CentOS-Webenv.repo
    ee1f37
    ee1f37
    [webenv]
    ee1f37
    name=CentOS-$releasever - Webenv
    ee1f37
    mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv
    ee1f37
    #baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/
    ee1f37
    gpgcheck=1
    ee1f37
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
    ee1f37
    enabled=1
    ee1f37
    priority=10
    ee1f37
    ee1f37
    ee1f37
    ee1f37

    3.11.2.10 Priority configuration

    ee1f37
    ee1f37

    Both [webenv] and [webenv-test] repositories update packages inside

    ee1f37
    CentOS [base] and CentOS [updates] repositories.
    ee1f37

    ee1f37
    ee1f37
    ee1f37

    3.11.3 Usage

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

      3.11.4 See also

      ee1f37
      ee1f37
      db14a4
      3.9 trunk/Identity/Models/Img/Promo/Web  
      ee1f37
      ee1f37
      ee1f37
      ee1f37
      ee1f37
      ee1f37
      [ < ]
      db14a4
      [ > ]
      ee1f37
         
      db14a4
      [ << ]
      ee1f37
      [ Up ]
      7ba52f
      [ >> ]
      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>