Blame Manual/repository-html/repository_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
-->
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>
aaf678
<title>CentOS Artwork Repository: 1.13 The Filesystem/trunk/Identity/Models/Tpl/Promo/Web Directory</title>
ee1f37
aaf678
<meta name="description" content="CentOS Artwork Repository: 1.13 The Filesystem/trunk/Identity/Models/Tpl/Promo/Web Directory">
aaf678
<meta name="keywords" content="CentOS Artwork Repository: 1.13 The Filesystem/trunk/Identity/Models/Tpl/Promo/Web 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
aaf678
[ < ]
aaf678
[ > ]
ee1f37
   
aaf678
[ << ]
aaf678
[ Up ]
aaf678
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
56a476
[Top]
56a476
[Contents]
5cb5a7
[Index]
56a476
[ ? ]
ee1f37
aaf678
aaf678
aaf678

1.13 The <tt>`Filesystem/trunk/Identity/Models/Tpl/Promo/Web'</tt> Directory

aaf678
ee1f37
aaf678
aaf678

1.13.1 Goals

aaf678
aaf678

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

aaf678
web environment.
aaf678

ee1f37
aaf678
aaf678

1.13.2 The CentOS web environment

982d5c
aaf678

Inside CentOS corporate identity, the CentOS web environment is

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

aaf678

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

aaf678

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

    The CentOS project is attached to a monolithic corporate visual

    aaf678
    identity (see section The <tt>`Filesystem/trunk/Identity'</tt> Directory), where all visual manifestations
    aaf678
    have one unique name and one unique visual style. This way, the CentOS
    aaf678
    web environment has one unique name (the CentOS brand) and one unique
    aaf678
    visual style (the CentOS default theme) for all its visual
    aaf678
    manifestations, the web applications in this case.
    aaf678

    aaf678

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

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

    aaf678

    This visual style diversity complicates our goal of one unique visual

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

    aaf678

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

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

    aaf678

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

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

    ee1f37
    aaf678
    aaf678

    1.13.2.1 Design model (without ads)

    ee1f37
    ee1f37
    aaf678
    aaf678

    1.13.2.2 Design model (with ads)

    aaf678
    aaf678
    aaf678
    aaf678

    1.13.2.3 HTML definitions

    aaf678
    aaf678
    aaf678
    aaf678

    1.13.2.4 Controlling visual style

    aaf678
    aaf678

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

    aaf678
    following compenents:
    aaf678

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

    1.13.2.5 Producing visual style

    aaf678
    aaf678

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

    aaf678
    files:
    aaf678

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

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

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

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

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

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

    aaf678
    aaf678
    aaf678

    1.13.2.6 Navigation

    aaf678
    aaf678

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

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

    aaf678
    aaf678
    aaf678

    1.13.2.7 Development and release cycle

    ee1f37
    aaf678

    The CentOS web environment development and relase cycle is described

    aaf678
    below: 
    aaf678

    aaf678
    aaf678
    Download
    aaf678
    aaf678

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

    aaf678
    want to use inside CentOS web environment.
    aaf678

    aaf678
    Important

    Important

    The source location from which web application are

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

    aaf678
    aaf678
    aaf678
    Prepare
    aaf678
    aaf678

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

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

    aaf678

    When preparing the structure keep in mind that different web

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

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

    Once web applications have been organized inside the version

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

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

    The command above creates the following structure:

    aaf678

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

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

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

    aaf678
    Info

    Tip

    Use the diff command of Subversion between

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

    aaf678
    aaf678
    aaf678
    Build packages
    aaf678
    aaf678

    When web application has been customized, build the web application

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

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

    When the customized web application has been packaged, make packages

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

    aaf678
    info

    Note

    The [webenv-test] repository is not shipped inside

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

    aaf678
    aaf678

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

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

    aaf678

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

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

    aaf678
    aaf678
    Release for production
    aaf678
    aaf678

    When customized web application packages are considered ready for

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

    aaf678
    info

    Note

    The [webenv] repository is not shipped inside CentOS

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

    aaf678
    aaf678
    aaf678
    aaf678
    aaf678
    aaf678

    1.13.2.8 The [webenv-test] repository

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

    1.13.2.9 The [webenv] repository

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

    1.13.2.10 Priority configuration

    aaf678
    aaf678

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

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

    aaf678
    aaf678
    aaf678

    1.13.3 Usage

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

      1.13.4 See also

      ee1f37
      aaf678
      aaf678
      1.11 The <tt>`Filesystem/trunk/Identity/Models/Img/Promo/Web'</tt> Directory  
      aaf678
      aaf678
      ee1f37
      ee1f37
      ee1f37
      aaf678
      [ < ]
      aaf678
      [ > ]
      ee1f37
         
      aaf678
      [ << ]
      aaf678
      [ Up ]
      aaf678
      [ >> ]
      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>