Blame Manuals/Repository/Docbook/Introduction/Repoconvs/extending.docbook

054a7b
<sect1 id="intro-repoconvs-extending">
054a7b
054a7b
    <title>Extending Repository Organization</title>
054a7b
        
054a7b
    <para>
3abc34
        Occasionly, you may find that new components of &TC;;
3abc34
        corporate visual identity need to be added to the repository
3abc34
        in order to work them out. If that is the case, the first
3abc34
        question we need to ask ourselves, before start to create
3abc34
        directories blindly all over, is: <emphasis>What is the right
3abc34
        place to store it?</emphasis>
054a7b
    </para>
054a7b
        
054a7b
    <para>
3abc34
        The best place to find answers is in &TC;; (see page
3abc34
        http://wiki.centos.org/Help), but going there with hands empty
3abc34
        is not good idea. It may give the impression you don't really
3abc34
        care about. Instead, consider the following suggestions
054a7b
        to find your own comprehension in order to make your own
054a7b
        propositions based on it.
054a7b
    </para>
054a7b
        
054a7b
    <para>
054a7b
        When extending respository structure it is very useful to bear
3abc34
        in mind &TCPCVIS;, &TC;; and &TCDRS;.  The rest is a matter of
3abc34
        choosing appropriate names.  It is also worth to know that
3abc34
        each directory in the repository responds to a conceptual idea
3abc34
        that justifies its existence.
054a7b
    </para>
054a7b
        
054a7b
    <para>
054a7b
        To build a directory structure inside the repository, you need
054a7b
        to define the conceptual idea first and later create the
054a7b
        directory, remembering that there are locations inside the
054a7b
        repository that define conceptual ideas you probably would
054a7b
        prefer to reuse.  For example, the 
054a7b
        class="directory">trunk/Identity/Images/Themes</filename>
054a7b
        directory stores theme artistic motifs, the 
054a7b
        class="directory">trunk/Identity/Models/Themes</filename>
054a7b
        directory stores theme design models, the 
054a7b
        class="directory">trunk/Manuals</filename> directory stores
054a7b
        documentation files, the 
054a7b
        class="directory">trunk/Locales</filename> stores translation
054a7b
        messages, and the 
054a7b
        class="directory">trunk/Scripts</filename> stores automation
054a7b
        scripts.
054a7b
    </para>
054a7b
        
054a7b
    <para>
054a7b
        To better illustrate this desition process, you can consider
054a7b
        to examin the 
054a7b
        class="directory">trunk/Identity/Images/Themes/TreeFlower/3</filename>
054a7b
        directory structure as example.  This directory can be read
054a7b
        as: the theme development line of version <quote>3</quote> of
054a7b
        <quote>TreeFlower</quote> artistic motif.  Additional, we can
054a7b
        say that <quote>TreeFlower</quote> artistic motif is part of
054a7b
        themes, as themes are part of The CentOS Project corporate
054a7b
        visual identity.
054a7b
    </para>
054a7b
        
054a7b
    <para>
054a7b
        The relationship between conceptual ideas can be stablished by
054a7b
        reading each repository documentation entry individually, from
054a7b
        <filename class="directory">trunk</filename> directory to a
054a7b
        deeper directory in the path. For reading repository
054a7b
        documentation entries we use the help
054a7b
        functionality of <command>centos-art.sh</command> script.
054a7b
    </para>
054a7b
        
054a7b
</sect1>