diff --git a/Manuals/Tcar-ug/Repository/Convenctions/worklines.docbook b/Manuals/Tcar-ug/Repository/Convenctions/worklines.docbook index a49257e..5f57ad2 100644 --- a/Manuals/Tcar-ug/Repository/Convenctions/worklines.docbook +++ b/Manuals/Tcar-ug/Repository/Convenctions/worklines.docbook @@ -3,14 +3,22 @@ Repository Work Lines - To organize content production inside &TCAR;, production has - been divided into individual work lines that relate one - another based on the idea of doing one thing well. Later, the - results produced individually by each work line are combined - to achieve a higher purpose. Work lines, as conceived here, - provide the relayable output components the production cycle - inside &TCAR; needs to let everyone to work syncronized in a - descentralized environment. + The content production inside &TCAR; has been divided into + individual work lines that relate one another based on the + idea of doing one thing well. In this model, the content + produced individually by each work line is combined one + another later to achieve higher purposes (e.g., corporate + identity for &TCP;). The repository work lines, as conceived + here, provide a relaible environment for people to work + syncronized and descentralized. + + + + The action of combining work lines one another inside &TCAR; + is known as the corporate identity production cycle. The rest + of this section describes the work lines available in the + repository and their position inside the corporate identity + production cycle. @@ -18,26 +26,33 @@ Visual Identity - In the production cycle, the first step takes place through - graphic design. It is focused on preparing design models for - all the visual manifestation &TCP; is made of. Here, graphic - designers describe the visual characteristics of each visual - manifestation (e.g., image dimensions, position of text in the - visible area, translation markers, etc.). - Later, once design models have been defined, graphic designers - take care of artistic motifs to define the visual style of - those design models already created (e.g., how they look and - feel). + The visual identity is the first component we work out in + order to produce a new corporate identity. Through this work + line, graphic designers create models and + motifs for all the visual manifestation &TCP; + is made of. Once design models and artistic motifs are set in + place, graphic designers use the render + functionality described in to combine both design models and artistic motifs into + final images. + + + + The main purposes of this work line is define all the visual + manifestations the &TCP; is made of and provide design models + and artistic motifs for them in order to render the set of + images required to transmit the visual style that identifies + &TCP; as unique organization. To know more about &TCPCVI;, + read . - + - Finally, graphic designers use the - render functionality of - centos-art.sh script to combine both design - models and artistic motifs in order to produce the final - images required by each visual manifestaions. + The visual identity work line takes palce in the trunk/Identity directory. + @@ -45,22 +60,36 @@ Localization - The second step in the production cycle is to localize - source files (e.g., SVG, DocBook, Shell scripts). This step - makes possible to produce localized images, localized - documentation and localized automation scripts. - - - - The localization tasks are carried on by translators using the - locale functionality of the - centos-art.sh script which take care of + The content localization is the second component that must be + worked out in the corporate identity production cycle. + Through this work line translators localize source files + (e.g., SVG, DocBook, Shell scripts) which are later use to + produce localized images, localized documentation and + localized automation scripts. To localize source files, + translators use + the locale functionality described in + which takes care of retriving translatable strings from source files and provide a consistent localization interface based on GNU gettext multi-lingual message production tool set and xml2po command. + + The main purpose of this work line is extend the visual + identity (produced in English language) to as many native + languages as possible in order for people which doesn't + understand English languague to feel more confortable with + &TCP; and its messages. To know more about the specific + localization process read . + + + + The localization work line takes palce in the trunk/Locales directory. + + @@ -68,18 +97,37 @@ Documentation - The third step in the production cycle is to document &TCAR;, - what it is and how to use it. This step provides the - conceptual ideas used as base to edificate &TCPCVI; and is - implemented through &TCARUG;. + The documentation work line is the third component that must + be worked out in the corporate identity production cycle. + Through this work line documentors settle down the conceptual + and practical used to edificate &TCAR;. To write + documentation, documentors use the help + functionality described in which provides a consistent interface for building + documentation through different documentation backends (e.g., + Texinfo, DocBook, LaTeX, etc.). + + + + The main purpose of this work line is describe the standard + procedures &TCAR; realies on, as well as conceive a place to + help you understand what &TCAR; is and what can you do with + it. + + + + The documentation work line takes palce in the trunk/Manuals directory. + + + + Packaging + - To write documentation, documentors use the - help functionality of - centos-art.sh script which provide an - consistent interface for building documentation through - different documentation backends (e.g., Texinfo and DocBook). + ... @@ -89,22 +137,25 @@ Automation - The fourth step in the production cycle is to automate - frequent tasks inside &TCAR;. This step closes the production - cycle and provides the production standards needed by all - different work lines to coexist together. Here is where - the centos-art.sh script and all - its functionalities (e.g., render for - rendition, help for documentation, - locale for localization, etc.) are - developed. - + The automation work line is the fifth and last component that + must be worked out in the corporate identity production cycle. + This work line closes the production cycle and provides the + production standards graphic designers, documentors, + translators and packagers need to make their work consistent + and reusable. For this purpose, programmers develop the + centos-art.sh script described in . + + + + The main purpose of this work line is standardize the + interaction of work lines in a reliable way. + - At this point it should be obvious, but we consider worth to - remember that: there is no need to type several tasks, time - after time, if they can be programmed into just one executable - script. + The automation work line takes palce in the trunk/Scripts directory.