Blame Manuals/Repository/en_US/Introduction/history.texinfo

b32b45
This section records noteworthy changes of CentOS Artwork Repository
b32b45
through years.
b32b45
b32b45
@subheading 2008
b32b45
b32b45
The CentOS Artwork Repository started at CentOS Developers mailing
b32b45
(@email{centos-devel@@centos.org}) during a discussion about how
b32b45
to automate the slide images of Anaconda. In such discussion, Ralph
b32b45
Angenendt rose up his hand to ask: Do you have something to show?
b32b45
    
b32b45
To answer the question, Alain Reguera Delgado suggested a bash script
b32b45
which combined SVG and SED files in order to produce PNG images in
b32b45
different languages ---together with the proposition of creating a
b32b45
Subversion repository where translations and image production could be
b32b45
distributed inside The CentOS Community---.
b32b45
    
b32b45
Karanbirn Sighn considered the idea intresting and provided the
b32b45
infrastructure necessary to support the effort.  This way the CentOS
b32b45
Artwork SIG (@url{https://projects.centos.org/trac/artwork/}) and the
b32b45
CentOS Artwork Repository
b32b45
(@url{https://projects.centos.org/svn/artwork/}) were officially
b32b45
created.
b32b45
    
b32b45
Once the CentOS Artwork Repository was available, Alain Reguera
b32b45
Delagdo uploaded the bash script for rendering Anaconda slides; Ralph
b32b45
Angenendt documented it very well; and people started to download
b32b45
working copies of CentOS Artwork Repository to produce slide images in
b32b45
their own languages.
b32b45
b32b45
@subheading 2009
b32b45
b32b45
The rendition script was at a very rustic state where only slide
b32b45
images could be produced, so it was redesigned to extend the image
b32b45
production to other areas, not just slide images.  In this
b32b45
configuration, one SVG file was used as input to produce a translated
b32b45
instance of it which, in turn, was used to produce one translated PNG
b32b45
image as output.  The SVG translated instance was created through SED
b32b45
replacement commands. The translated PNG image was created from the
b32b45
SVG translated instance using Inkscape command-line interface.
b32b45
    
b32b45
The rendition script was named @command{render.sh}.
b32b45
    
b32b45
The repository directory structure was prepared to receive the
b32b45
rendition script using design templates and translation files in the
b32b45
same location.  There was one directory structure for each artwork
b32b45
that needed to be produced. In this configuration, if you would want
b32b45
to produce the same artwork with a different visual style or
b32b45
structure, it was needed to create a new directory structure for it
b32b45
because both the image structure and the image visual style were
b32b45
together in the design template.
b32b45
    
b32b45
The rendition script was moved to a common place and linked from
b32b45
different directory structures. There was no need to have the same
b32b45
code in different directory structures if it could be in just one
b32b45
place and then be linked from different locations.
b32b45
    
b32b45
The concepts about corporate identity began to be considered. As
b32b45
referece, it was used the book ``Corporate Identity'' by Wally Olins
b32b45
(1989) and Wikipedia
b32b45
(@url{http://en.wikipedia.org/Corporate_identity}). This way, the
b32b45
rendition script main's goal becomes to: automate production of a
b32b45
monolithic corporate visual identity structure, based on the mission
b32b45
and the release schema of The CentOS Project.
b32b45
    
b32b45
The directory structures started to be documented inside the
b32b45
repository using text files without markup.  Later, documentation in
b32b45
flat text files was moved to LaTeX format and this way ``The CentOS
b32b45
Artwork Repository Manual'' started to take form.
b32b45
b32b45
@subheading 2010
b32b45
b32b45
The rendition script changed its name from @command{render.sh} to
b32b45
@command{centos-art.sh} and became a collection of functionalities
b32b45
where rendition was just one among others (e.g., documenting and
b32b45
localizing).
b32b45
b32b45
The @command{centos-art.sh} was created to organize automation of most
b32b45
frequent tasks inside the repository.  There was no need to have links
b32b45
all around the repository if a command-line interface could be created
b32b45
(through symbolic links, in the @file{~/bin} directory) and be called
b32b45
anywhere inside the repository as it would be a regular command.
b32b45
b32b45
Inside @command{centos-art.sh}, functionalities started to get
b32b45
identified and separated one another. For example, when images were
b32b45
rendered, there was no need to load functionalities related to
b32b45
documentation manual. This layout moved us onto common functionalities
b32b45
and specific functionalities inside @command{centos-art.sh} script.
b32b45
Common functionalities are loaded when @command{centos-art.sh} script
b32b45
is initiated and are available to specific functionalities.
b32b45
b32b45
The @command{centos-art.sh} script was redesigned to handle
b32b45
command-line options trough @command{getopt} option parser.
b32b45
b32b45
The repository directory structure was updated to improve the
b32b45
implementation of concepts related to corporate visual identity.
b32b45
Specially in the area related to themes which were divided into
b32b45
``design models'' and ``artistic motifs'' to eliminate the content
b32b45
duplication produced by having both image structure and image visual
b32b45
style in the same file.  Now, themes are produced as result of
b32b45
arbitrary combinations of both design models (structures) and artistic
b32b45
motifs (visual styles).
b32b45
b32b45
In the documentation area, the documentation files in LaTeX format
b32b45
were migrated to Texinfo format.  In this configuration, each
b32b45
directory structure in the repository has a documentation entry
b32b45
associated in a Texinfo structure which can be read, edited and
b32b45
administered (e.g., renamed, deleted, copied) interactively throuch
b32b45
@command{centos-art.sh}. Additionally, the @command{texi2html} program
b32b45
was used to produced XHTML output customized by CSS from The CentOS
b32b45
Webenv.
b32b45
b32b45
@subheading 2011
b32b45
b32b45
The @command{centos-art.sh} script was redesigned to start translating
b32b45
SVG and other XML-based files (e.g., XHTML and Docbook files) through
b32b45
the @command{xml2po} program and shell scripts files (e.g., Bash
b32b45
scripts) through GNU @command{gettext} tools.  This configuration
b32b45
provided a stronger interface for graphic designers, translators and
b32b45
programmers to produce localized content.  The SED files are no longer
b32b45
used to handle translations.
b32b45
b32b45
Improve option parsing through @command{getopt}.
b32b45
b32b45
Consolidate the @code{render}, @code{help} and @code{locale}
b32b45
functionalities as the most frequent tasks performed inside the
b32b45
repository. Additionally, the @code{prepare} and @code{tuneup}
b32b45
functionalities are maintained as useful tasks.
b32b45
b32b45
The @command{centos-art.sh} script is updated to organize
b32b45
functionalities in two groups: ``the administrative functionalities''
b32b45
and ``the productive functionalities''.  The administrative
b32b45
functionalities cover actions like: copying, deleting and renaming
b32b45
directory structures inside the repository.  Also, preparing your
b32b45
workstation for using @command{centos-art.sh} script, making
b32b45
backups of the distribution theme currently installed,  installing
b32b45
themes created inside repository and restoring themes from backup.  On
b32b45
the other hand, the productive functionalities cover actions like:
b32b45
content rendition, content localization, content documentation and
b32b45
content maintainance.