Blame Manuals/Repository/repository-html/repository_15.html

4c79b5
4c79b5
<html>
ccb7a3
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
-->
acd47b
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>
c2a1bc
<title>CentOS Artwork Repository: 3.12 trunk/Identity/Models/Tpl/Promo/Web</title>
4c79b5
c2a1bc
<meta name="description" content="CentOS Artwork Repository: 3.12 trunk/Identity/Models/Tpl/Promo/Web">
c2a1bc
<meta name="keywords" content="CentOS Artwork Repository: 3.12 trunk/Identity/Models/Tpl/Promo/Web">
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
1e9202
@import "/home/centos/artwork/trunk/Identity/Models/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
2dc146
[ < ]
2dc146
[ > ]
4c79b5
   
4c79b5
[ << ]
4c79b5
[ Up ]
c2a1bc
[ >> ]
4c79b5
   
4c79b5
   
4c79b5
   
4c79b5
   
4c79b5
[Top]
4c79b5
[Contents]
c2a1bc
[Index]
4c79b5
[ ? ]
4c79b5
c2a1bc
2dc146
c2a1bc

3.12 trunk/Identity/Models/Tpl/Promo/Web

4c79b5
4c79b5
2dc146
4c79b5

3.12.1 Goals

4c79b5
c2a1bc

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

c2a1bc
web environment.
c2a1bc

2dc146
2dc146
c2a1bc

3.12.2 The CentOS web environment

2dc146
c2a1bc

Inside CentOS corporate identity, the CentOS web environment is

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

c2a1bc

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

c2a1bc

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

    The CentOS project is attached to a monolithic corporate visual

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

    c2a1bc

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

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

    c2a1bc

    This visual style diversity complicates our goal of one unique visual

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

    c2a1bc

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

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

    c2a1bc

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

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

    4c79b5
    2dc146
    c2a1bc

    3.12.2.1 Design model (without ads)

    c2a1bc
    c2a1bc
    c2a1bc
    c2a1bc

    3.12.2.2 Design model (with ads)

    c2a1bc
    c2a1bc
    c2a1bc
    c2a1bc

    3.12.2.3 HTML definitions

    c2a1bc
    c2a1bc
    c2a1bc
    c2a1bc

    3.12.2.4 Controlling visual style

    c2a1bc
    c2a1bc

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

    c2a1bc
    following compenents:
    c2a1bc

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

    3.12.2.5 Producing visual style

    c2a1bc
    c2a1bc

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

    c2a1bc
    files:
    c2a1bc

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

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

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

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

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

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

    c2a1bc
    c2a1bc
    c2a1bc

    3.12.2.6 Navigation

    c2a1bc
    c2a1bc

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

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

    c2a1bc
    c2a1bc
    c2a1bc

    3.12.2.7 Development and release cycle

    c2a1bc
    c2a1bc

    The CentOS web environment development and relase cycle is described

    c2a1bc
    below: 
    c2a1bc

    c2a1bc
    c2a1bc
    Download
    c2a1bc
    c2a1bc

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

    c2a1bc
    want to use inside CentOS web environment.
    c2a1bc

    c2a1bc
    Important

    Important

    The source location from which web application are

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

    c2a1bc
    c2a1bc
    c2a1bc
    Prepare
    c2a1bc
    c2a1bc

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

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

    c2a1bc

    When preparing the structure keep in mind that different web

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

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

    Once web applications have been organized inside the version

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

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

    The command above creates the following structure:

    c2a1bc

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

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

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

    c2a1bc
    Info

    Tip

    Use the diff command of Subversion between

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

    c2a1bc
    c2a1bc
    c2a1bc
    Build packages
    c2a1bc
    c2a1bc

    When web application has been customized, build the web application

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

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

    When the customized web application has been packaged, make packages

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

    c2a1bc
    info

    Note

    The [webenv-test] repository is not shipped inside

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

    c2a1bc
    c2a1bc

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

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

    c2a1bc

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

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

    c2a1bc
    c2a1bc
    Release for production
    c2a1bc
    c2a1bc

    When customized web application packages are considered ready for

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

    c2a1bc
    info

    Note

    The [webenv] repository is not shipped inside CentOS

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

    c2a1bc
    c2a1bc
    c2a1bc
    c2a1bc
    c2a1bc
    c2a1bc

    3.12.2.8 The [webenv-test] repository

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

    3.12.2.9 The [webenv] repository

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

    3.12.2.10 Priority configuration

    c2a1bc
    c2a1bc

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

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

    c2a1bc
    c2a1bc
    4c79b5

    3.12.3 Usage

    4c79b5
    bc3531
      bc3531
    • ...
    • bc3531
      bc3531
      4c79b5
      c2a1bc
      4c79b5

      3.12.4 See also

      4c79b5
      c2a1bc
      c2a1bc
      3.10 trunk/Identity/Models/Img/Promo/Web  
      c2a1bc
      c2a1bc
      4c79b5
      4c79b5
      4c79b5
      c2a1bc
      [ < ]
      c2a1bc
      [ > ]
      4c79b5
         
      4c79b5
      [ << ]
      2dc146
      [ Up ]
      c2a1bc
      [ >> ]
      4c79b5
      4c79b5

      4c79b5
       <font size="-1">
      acd47b
        This document was generated on February, 26 2011 using texi2html 1.76.
      4c79b5
       </font>
      4c79b5
       
      4c79b5
      4c79b5

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