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. 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). 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 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 GNU gettext multi-lingual message production tool set and xml2po command. 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;. 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). 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. 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.