To organize content production inside &TCAR;, production has been divided into individual work lines that relate one another. The is based on the idea of doing one thing well and later combine the result of each individual part to achieve a higher purpose. Work lines, as conceived here, provide relayable output components that combine one another to close the production cycle inside &TCAR;. Visual Identity (trunk/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 the look and feel). Furthermore, 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. Localization (trunk/L10n) 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 retriving translatable strings from source files and provide a consistent localization interface based on the ideas behind GNU gettext multi-lingual message production. Documentation (trunk/Manuals) 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 by mean of &TCARUG;. 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, DocBook). Automation (trunk/Scripts) 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 we develop the centos-art.sh script and all its functionalities (e.g., render for rendition, help for documentation, locale for localization, etc.). 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.