From e41a32c35859272c11d8005122ceacb463e7dde0 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: May 01 2011 16:44:13 +0000 Subject: Update repository documentation manual. --- diff --git a/Manual/Directories/chapter-menu.texi b/Manual/Directories/chapter-menu.texi index f2debef..1a4fc33 100644 --- a/Manual/Directories/chapter-menu.texi +++ b/Manual/Directories/chapter-menu.texi @@ -6,31 +6,31 @@ * Directories trunk Identity Brushes:: * Directories trunk Identity Fonts:: * Directories trunk Identity Images:: +* Directories trunk Identity Images Themes:: +* Directories trunk Identity Images Themes Models:: +* Directories trunk Identity Images Themes Models Default:: +* Directories trunk Identity Images Themes Models Default Concept:: +* Directories trunk Identity Images Themes Models Default Distro:: +* Directories trunk Identity Images Themes Models Default Distro 5:: +* Directories trunk Identity Images Themes Models Default Distro 5 Anaconda:: +* Directories trunk Identity Images Themes Models Default Distro 5 Firstboot:: +* Directories trunk Identity Images Themes Models Default Distro 5 Gdm:: +* Directories trunk Identity Images Themes Models Default Distro 5 Grub:: +* Directories trunk Identity Images Themes Models Default Distro 5 Gsplash:: +* Directories trunk Identity Images Themes Models Default Distro 5 Kdm:: +* Directories trunk Identity Images Themes Models Default Distro 5 Ksplash:: +* Directories trunk Identity Images Themes Models Default Distro 5 Rhgb:: +* Directories trunk Identity Images Themes Models Default Distro 5 Syslinux:: +* Directories trunk Identity Images Themes Models Default Posters:: +* Directories trunk Identity Images Themes Motifs:: +* Directories trunk Identity Images Themes Motifs Flame:: +* Directories trunk Identity Images Themes Motifs Modern:: +* Directories trunk Identity Images Themes Motifs Pipes:: +* Directories trunk Identity Images Themes Motifs TreeFlower:: * Directories trunk Identity Models:: * Directories trunk Identity Models Brands:: * Directories trunk Identity Palettes:: * Directories trunk Identity Patterns:: -* Directories trunk Identity Themes:: -* Directories trunk Identity Themes Models:: -* Directories trunk Identity Themes Models Default:: -* Directories trunk Identity Themes Models Default Concept:: -* Directories trunk Identity Themes Models Default Distro:: -* Directories trunk Identity Themes Models Default Distro 5:: -* Directories trunk Identity Themes Models Default Distro 5 Anaconda:: -* Directories trunk Identity Themes Models Default Distro 5 Firstboot:: -* Directories trunk Identity Themes Models Default Distro 5 Gdm:: -* Directories trunk Identity Themes Models Default Distro 5 Grub:: -* Directories trunk Identity Themes Models Default Distro 5 Gsplash:: -* Directories trunk Identity Themes Models Default Distro 5 Kdm:: -* Directories trunk Identity Themes Models Default Distro 5 Ksplash:: -* Directories trunk Identity Themes Models Default Distro 5 Rhgb:: -* Directories trunk Identity Themes Models Default Distro 5 Syslinux:: -* Directories trunk Identity Themes Models Default Posters:: -* Directories trunk Identity Themes Motifs:: -* Directories trunk Identity Themes Motifs Flame:: -* Directories trunk Identity Themes Motifs Modern:: -* Directories trunk Identity Themes Motifs Pipes:: -* Directories trunk Identity Themes Motifs TreeFlower:: * Directories trunk Identity Webenv:: * Directories trunk Locales:: * Directories trunk Manual:: diff --git a/Manual/Directories/chapter-nodes.texi b/Manual/Directories/chapter-nodes.texi index bf37f6b..4d6b09d 100644 --- a/Manual/Directories/chapter-nodes.texi +++ b/Manual/Directories/chapter-nodes.texi @@ -33,6 +33,111 @@ @cindex Directories trunk Identity Images @include Directories/trunk/Identity/Images.texi +@node Directories trunk Identity Images Themes +@section The @file{trunk/Identity/Images/Themes} Directory +@cindex Directories trunk Identity Images Themes +@include Directories/trunk/Identity/Images/Themes.texi + +@node Directories trunk Identity Images Themes Models +@section The @file{trunk/Identity/Images/Themes/Models} Directory +@cindex Directories trunk Identity Images Themes Models +@include Directories/trunk/Identity/Images/Themes/Models.texi + +@node Directories trunk Identity Images Themes Models Default +@section The @file{trunk/Identity/Images/Themes/Models/Default} Directory +@cindex Directories trunk Identity Images Themes Models Default +@include Directories/trunk/Identity/Images/Themes/Models/Default.texi + +@node Directories trunk Identity Images Themes Models Default Concept +@section The @file{trunk/Identity/Images/Themes/Models/Default/Concept} Directory +@cindex Directories trunk Identity Images Themes Models Default Concept +@include Directories/trunk/Identity/Images/Themes/Models/Default/Concept.texi + +@node Directories trunk Identity Images Themes Models Default Distro +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Anaconda +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Anaconda} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Anaconda +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Anaconda.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Firstboot +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Firstboot} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Firstboot +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Firstboot.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Gdm +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Gdm} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Gdm +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gdm.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Grub +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Grub} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Grub +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Grub.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Gsplash +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Gsplash} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Gsplash +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gsplash.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Kdm +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Kdm} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Kdm +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Kdm.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Ksplash +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Ksplash} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Ksplash +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Ksplash.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Rhgb +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Rhgb} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Rhgb +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Rhgb.texi + +@node Directories trunk Identity Images Themes Models Default Distro 5 Syslinux +@section The @file{trunk/Identity/Images/Themes/Models/Default/Distro/5/Syslinux} Directory +@cindex Directories trunk Identity Images Themes Models Default Distro 5 Syslinux +@include Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Syslinux.texi + +@node Directories trunk Identity Images Themes Models Default Posters +@section The @file{trunk/Identity/Images/Themes/Models/Default/Posters} Directory +@cindex Directories trunk Identity Images Themes Models Default Posters +@include Directories/trunk/Identity/Images/Themes/Models/Default/Posters.texi + +@node Directories trunk Identity Images Themes Motifs +@section The @file{trunk/Identity/Images/Themes/Motifs} Directory +@cindex Directories trunk Identity Images Themes Motifs +@include Directories/trunk/Identity/Images/Themes/Motifs.texi + +@node Directories trunk Identity Images Themes Motifs Flame +@section The @file{trunk/Identity/Images/Themes/Motifs/Flame} Directory +@cindex Directories trunk Identity Images Themes Motifs Flame +@include Directories/trunk/Identity/Images/Themes/Motifs/Flame.texi + +@node Directories trunk Identity Images Themes Motifs Modern +@section The @file{trunk/Identity/Images/Themes/Motifs/Modern} Directory +@cindex Directories trunk Identity Images Themes Motifs Modern +@include Directories/trunk/Identity/Images/Themes/Motifs/Modern.texi + +@node Directories trunk Identity Images Themes Motifs Pipes +@section The @file{trunk/Identity/Images/Themes/Motifs/Pipes} Directory +@cindex Directories trunk Identity Images Themes Motifs Pipes +@include Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texi + +@node Directories trunk Identity Images Themes Motifs TreeFlower +@section The @file{trunk/Identity/Images/Themes/Motifs/TreeFlower} Directory +@cindex Directories trunk Identity Images Themes Motifs TreeFlower +@include Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texi + @node Directories trunk Identity Models @section The @file{trunk/Identity/Models} Directory @cindex Directories trunk Identity Models @@ -53,111 +158,6 @@ @cindex Directories trunk Identity Patterns @include Directories/trunk/Identity/Patterns.texi -@node Directories trunk Identity Themes -@section The @file{trunk/Identity/Themes} Directory -@cindex Directories trunk Identity Themes -@include Directories/trunk/Identity/Themes.texi - -@node Directories trunk Identity Themes Models -@section The @file{trunk/Identity/Themes/Models} Directory -@cindex Directories trunk Identity Themes Models -@include Directories/trunk/Identity/Themes/Models.texi - -@node Directories trunk Identity Themes Models Default -@section The @file{trunk/Identity/Themes/Models/Default} Directory -@cindex Directories trunk Identity Themes Models Default -@include Directories/trunk/Identity/Themes/Models/Default.texi - -@node Directories trunk Identity Themes Models Default Concept -@section The @file{trunk/Identity/Themes/Models/Default/Concept} Directory -@cindex Directories trunk Identity Themes Models Default Concept -@include Directories/trunk/Identity/Themes/Models/Default/Concept.texi - -@node Directories trunk Identity Themes Models Default Distro -@section The @file{trunk/Identity/Themes/Models/Default/Distro} Directory -@cindex Directories trunk Identity Themes Models Default Distro -@include Directories/trunk/Identity/Themes/Models/Default/Distro.texi - -@node Directories trunk Identity Themes Models Default Distro 5 -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Anaconda -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Anaconda} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Anaconda -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Firstboot -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Firstboot} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Firstboot -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Firstboot.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Gdm -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Gdm} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Gdm -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gdm.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Grub -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Grub} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Grub -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Grub.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Gsplash -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Gsplash} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Gsplash -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gsplash.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Kdm -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Kdm} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Kdm -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Kdm.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Ksplash -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Ksplash} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Ksplash -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Ksplash.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Rhgb -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Rhgb} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Rhgb -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Rhgb.texi - -@node Directories trunk Identity Themes Models Default Distro 5 Syslinux -@section The @file{trunk/Identity/Themes/Models/Default/Distro/5/Syslinux} Directory -@cindex Directories trunk Identity Themes Models Default Distro 5 Syslinux -@include Directories/trunk/Identity/Themes/Models/Default/Distro/5/Syslinux.texi - -@node Directories trunk Identity Themes Models Default Posters -@section The @file{trunk/Identity/Themes/Models/Default/Posters} Directory -@cindex Directories trunk Identity Themes Models Default Posters -@include Directories/trunk/Identity/Themes/Models/Default/Posters.texi - -@node Directories trunk Identity Themes Motifs -@section The @file{trunk/Identity/Themes/Motifs} Directory -@cindex Directories trunk Identity Themes Motifs -@include Directories/trunk/Identity/Themes/Motifs.texi - -@node Directories trunk Identity Themes Motifs Flame -@section The @file{trunk/Identity/Themes/Motifs/Flame} Directory -@cindex Directories trunk Identity Themes Motifs Flame -@include Directories/trunk/Identity/Themes/Motifs/Flame.texi - -@node Directories trunk Identity Themes Motifs Modern -@section The @file{trunk/Identity/Themes/Motifs/Modern} Directory -@cindex Directories trunk Identity Themes Motifs Modern -@include Directories/trunk/Identity/Themes/Motifs/Modern.texi - -@node Directories trunk Identity Themes Motifs Pipes -@section The @file{trunk/Identity/Themes/Motifs/Pipes} Directory -@cindex Directories trunk Identity Themes Motifs Pipes -@include Directories/trunk/Identity/Themes/Motifs/Pipes.texi - -@node Directories trunk Identity Themes Motifs TreeFlower -@section The @file{trunk/Identity/Themes/Motifs/TreeFlower} Directory -@cindex Directories trunk Identity Themes Motifs TreeFlower -@include Directories/trunk/Identity/Themes/Motifs/TreeFlower.texi - @node Directories trunk Identity Webenv @section The @file{trunk/Identity/Webenv} Directory @cindex Directories trunk Identity Webenv diff --git a/Manual/Directories/trunk/Identity.texi b/Manual/Directories/trunk/Identity.texi index ad28eca..eca5563 100644 --- a/Manual/Directories/trunk/Identity.texi +++ b/Manual/Directories/trunk/Identity.texi @@ -50,8 +50,8 @@ visual manifestations were defined: The CentOS Distribution visual manifestation exists to cover all actions related to artwork production and rebranding required by the -The CentOS Distribution (@pxref{Directories trunk Identity Themes -Models Default Distro}) in order to comply with its upstream +The CentOS Distribution (--- @strong{Removed}(pxref:Directories trunk Identity Images Themes +Models Default Distro) ---) in order to comply with its upstream redistribution guidelines. The CentOS Distribution is made of software packages. Inside the @@ -256,7 +256,7 @@ This work line provides theme design models and theme artistic motifs for The CentOS Project. If you are interested in creating brand new visual styles for The CentOS Project this is the place for you. -@xref{Directories trunk Identity Themes}, for more information. +@xref{Directories trunk Identity Images Themes}, for more information. @item Webenv diff --git a/Manual/Directories/trunk/Identity/Images/Themes.texi b/Manual/Directories/trunk/Identity/Images/Themes.texi new file mode 100644 index 0000000..58ffe57 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes.texi @@ -0,0 +1,89 @@ +@subheading Goals + +The @file{trunk/Identity/Themes/} directory exists to organize +production of CentOS themes. + +@subheading Description + +Initially, we start working themes on their trunk development line +(e.g., @file{trunk/Identity/Images/Themes/TreeFlower/}), here we +organize information that cannot be produced automatically (i.e., +background images, concepts, color information, screenshots, etc.). + +Later, when theme trunk development line is considered ``ready'' for +implementation (e.g., all required backgrounds have been designed), +we create a branch for it (e.g., +@file{branches/Identity/Images/Themes/TreeFlower/1/}). Once the +branch has been created, we forget that branch and continue working +the trunk development line while others (e.g., an artwork quality +assurance team) test the new branch for tunning it up. + +Once the branch has been tunned up, and considered ``ready'' for +release, it is freezed under @file{tags/} directory (e.g., +@file{tags/Identity/Images/Themes/TreeFower/1.0/}) for packagers, +webmasters, promoters, and anyone who needs images from that CentOS +theme the tag was created for. + +Both branches and tags, inside CentOS Artwork Repository, use +numerical values to identify themselves under the same location. +Branches start at one (i.e., @samp{1}) and increment one unit for each +branch created from the same trunk development line. Tags start at +zero (i.e., @samp{0}) and increment one unit for each tag created from +the same branch development line. + +@quotation +@strong{Convenction} Do not freeze trunk development lines using tags +directly. If you think you need to freeze a trunk development line, +create a branch for it and then freeze that branch instead. +@end quotation + +The trunk development line may introduce problems we cannot see +immediatly. Certainly, the high changable nature of trunk development +line complicates finding and fixing such problems. On the other hand, +the branched development lines provide a more predictable area where +only fixes/corrections to current content are commited up to +repository. + +If others find and fix bugs inside the branched development line, we +could merge such changes/experiences back to trunk development line +(not visversa) in order for future branches, created from trunk, to +benefit. + +Time intervals used to create branches and tags may vary, just as +different needs may arrive. For example, consider the release schema +of CentOS distribution: one major release every 2 years, security +updates every 6 months, support for 7 years long. Each time a CentOS +distribution is released, specially if it is a major release, there is +a theme need in order to cover CentOS distribution artwork +requirements. At this point, is where CentOS Artwork Repository comes +up to scene. + +Before releasing a new major release of CentOS distribution we create +a branch for one of several theme development lines available inside +the CentOS Artwork Repository, perform quality assurance on it, and +later, freeze that branch using tags. Once a the theme branch has been +frozen (under @file{tags/} directory), CentOS Packagers (the persons +whom build CentOS distribution) can use that frozen branch as source +location to fulfill CentOS distribution artwork needs. The same +applies to CentOS Webmasters (the persons whom build CentOS websites), +and any other visual manifestation required by the project. + +@subheading Usage + +In this location themes are organized in ``Models'' ---to store common +information--- and ``Motifs''---to store unique information. At +rendering time, both motifs and models are combined to produce the +final CentOS themes. CentOS themes can be tagged as ``Default'' or +``Alternative''. CentOS themes are maintained by CentOS community. + +@itemize +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---. +@end itemize + +@subheading See also + +@itemize +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models.texi new file mode 100644 index 0000000..5de87ce --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models.texi @@ -0,0 +1,46 @@ +@subheading Goals + +This section describes design models from The CentOS Themes. + +@subheading Description + +Theme models let you modeling characteristics (e.g., dimensions, +translation markers, position of each element on the display area, +etc.) common to all themes. Theme models let you reduce the time +needed when propagating artistic motifs to different visual +manifestations. + +Theme models serves as a central pool of design templates for themes +to use. This way you can produce themes with different artistic motifs +but same characteristics. + +@subsubheading Default Design Model + +Default Design Models for CentOS Themes provide the common structural +information (e.g., image dimensions, translation markers, trademark +position, etc.) the @command{centos-art} script uses to produce images +when no other design model is specified. + +@subsubheading Alternative Design Models + +CentOS alternative theme models exist for people how want to use a +different visual style on their installations of CentOS distribution. +As the visual style is needed for a system already installed +components like Anaconda are not required inside alternative themes. +Inside alternative themes you find post-installation visual style only +(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative +themes are maintained by CentOS Community. + +@subheading Usage + +@itemize +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default) ---. +@end itemize + +@subheading See also + +@itemize +@item @ref{Directories trunk Identity Images Themes}. +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default.texi new file mode 100644 index 0000000..5fb45b7 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default.texi @@ -0,0 +1,79 @@ +@subheading Goals + +This section describes the default design model of The CentOS Themes. + +@subheading Description + +The @file{trunk/Identity/Themes/Models/Default} directory implements +the concept of @emph{Default Design Model} for The CentOS Themes. The +CentOS Themes Default Design Model provides the common structural +information (e.g., image dimensions, translation markers, trademark +position, etc.) the @command{centos-art} script uses to produce images +when no other design model is specified. + +Deisgn models in this directory do use the @emph{CentOS Release +Brand}. The CentOS Release Brand is a combination of both The CentOS +Type and The CentOS Release Schema used to illustrate the major +release of The CentOS Distribution the image produced belongs to. --- +@strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) +---, for more information. + +The CentOS Project maintains near to four different major releases of +CentOS Distribution. Each major release of CentOS Distribution has +internal differences that make them unique and, at the same time, each +CentOS Distribution individually is tagged into the one unique visual +manifestation (i.e., Distribution). So, how could we implement the +monolithic visual structure in one visual manifestation that has +internal difference? + +To answer this question we broke the question in two parts and later +combined the resultant answers to build a possible solution. + +@table @strong +@item How to remark the internal differences visually? + +Merge both The CentOS Project Release Schema into The CentOS Project +Trademark to build The CentOS Project Release Trademark. The CentOS +Project Release Trademark remarks two things: first, it remarks the +image is from The CentOS Project and second, it remarks which major +release of CentOS Distribution does the image belongs to. +--- @strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) ---, for more +information on how to develop and improve The CentOS Project Brand. + +@item How to remark the visual resemblance? + +Use a common artistic motifs as background for all CentOS Distribution +images. --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---, for more +information. + +@item So, combining answers above, we could conclude that: + +In order to implement the CentOS Monolithic Visual Structure on CentOS +Distribution visual manifestations, a CentOS Release Trademark and a +background information based on one unique artistic motif should be +used in all remarkable images The CentOS Distribution visual +manifestation is made of. +@end table + +@quotation +@strong{Important} Remarking the CentOS Release Schema inside each +major release of CentOS Distribution ---or similar visual +manifestations--- takes @emph{high attention} inside The CentOS +Project corporate visual identity. It should be very clear for +everyone which major release of CentOS Distribution is being used. +@end quotation + +@subheading Usage + +@itemize +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Concept) ---. +@end itemize + +@subheading See also + +@itemize +@item @ref{Directories trunk Identity Images Themes} +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Models) --- +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Motifs) --- +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Concept.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Concept.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Concept.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro.texi new file mode 100644 index 0000000..e45a608 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro.texi @@ -0,0 +1,111 @@ +@subheading Goals + +This section organizes default design models for different major +releases of CentOS Distribution. + +@subheading Description + +In order to better understatand how this visual manifestation is +organized, it is necessary to consider what The CentOS Distribution is +and how it is released. + +@subsubheading The CentOS Distribution + +The CentOS Distribution is an Enterprise-class Linux Distribution +derived from sources freely provided to the public by a prominent +North American Enterprise Linux vendor. The CentOS Distribution +conforms fully with the upstream vendors redistribution policy and +aims to be 100% binary compatible. (The CentOS Project mainly changes +packages to remove upstream vendor branding and artwork.) + +The CentOS Distribution is developed by a small but growing team of +core developers. In turn the core developers are supported by an +active user community including system administrators, network +administrators, enterprise users, managers, core Linux contributors +and Linux enthusiasts from around the world. + +@subsubheading The CentOS Distribution Release Schema + +The upstream vendor has released 4 versions of their +@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds +the freely available SRPMS for. The upstream vendor releases security +updates as required by circumstances. The CentOS Project releases +rebuilds of security updates as soon as possible. Usually within 24 +hours (our stated goal is with 72 hours, but we are usually much +faster). + +The upstream vendor also releases numbered update sets for major +versions of their EL product from 2 to 4 times per year. There are new +ISOs from the upstream vendor provided for these update sets. Update +sets will be completed as soon as possible after the upstream vendor +releases their version @dots{} generally within 2 weeks. The CentOS +Project follows these conventions as well, so CentOS-3.9 correlates +with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6, +CentOS-5.1 correlates to EL 5 update 1, etc. + +One thing some people have problems understanding is that if you have +any CentOS-3 product and update it, you will be updated to the latest +CentOS-3.x version. + +The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 +product, you will be updated to the latest CentOS-4.x version, or to +the latest CentOS-5.x version if you are updating a CentOS-5 system. +This is exactly the same behavior as the upstream product. Let's +assume that the latest EL4 product is update 6. If you install the +upstream original EL4 CDs (the ones before any update set) and upgrade +via @command{yum}, you will have latest update set installed (EL4 +update 6 in our example). Since all updates within a major release +(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest +version when updates are performed (thus mimicking upstream behavior), +only the latest version is maintained in each main tree on The CentOS +Mirrors (@url{http://mirrors.centos.org/}). + +There is a CentOS Vault (@url{http://vault.centos.org/}) containing +old CentOS trees. This vault is a picture of the older tree when it +was removed from the main tree, and does not receive updates. It +should only be used for reference. + +The CentOS Distribution visual style is controlled by image files. +These image files are packaged inside The CentOS Distribution and made +visible once such packages are installed and executed. The way to go +for changing The CentOS Distribution visual style is changing all +those image files to add the desired visual style first and later, +repackage them to make them available inside the final iso files of +CentOS Distribution. + +@subheading Usage + +Sometimes, between major releases, image files inside packages can be +added, removed or just get the name changed. In order to describe such +variations, the design models directory structure is organized in the +same way the variations are introduced (i.e., through The CentOS +Distribution Release Schema). So, each major release of The CentOS +Distribution has its own design model directory structure. + +When a new package/component is added to one or all the major releases +of The CentOS Distribution, a design model directory structure for +that component needs to be created. Later, it is filled up with +related design models. Design models are created for each image file +inside the component that need to be rebuilt in order to set the +visual style and brand information correctly. + +When a package is removed from one or all major releases of The CentOS +Distribution, the design model directory structure releated to that +package/component is no longer used. However, it could be very useful +for historical reasons. Also, someone could feel motivation enough to +keep himself documenting it or supporting it for whatever reason. + +@itemize +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro +5) ---. +@end itemize + +@subheading See also + +@itemize +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Models Default) ---. +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Models) ---. +@item @ref{Directories trunk Identity Images Themes}. +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5.texi new file mode 100755 index 0000000..156678c --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5.texi @@ -0,0 +1,35 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Syslinux) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Anaconda) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Rhgb) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Gdm) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Kdm) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Grub) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Gsplash) ---. +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Models Default Distro 5 Ksplash) ---. +@end itemize + +@subheading See also + +@itemize +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Models Default Distro) ---. +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Models Default) ---. +@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Models) ---. +@item @ref{Directories trunk Identity Images Themes}. +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Anaconda.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Anaconda.texi new file mode 100644 index 0000000..c10b6dd --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Anaconda.texi @@ -0,0 +1,14 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@subheading Usage + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Firstboot.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Firstboot.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Firstboot.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gdm.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gdm.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gdm.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Grub.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Grub.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Grub.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gsplash.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gsplash.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Gsplash.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Kdm.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Kdm.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Kdm.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Ksplash.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Ksplash.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Ksplash.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Rhgb.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Rhgb.texi new file mode 100755 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Rhgb.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Syslinux.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Syslinux.texi new file mode 100755 index 0000000..d6bb628 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Distro/5/Syslinux.texi @@ -0,0 +1,23 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@itemize +@item ... +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Posters.texi b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Posters.texi new file mode 100644 index 0000000..e226b31 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Models/Default/Posters.texi @@ -0,0 +1,22 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Motifs.texi b/Manual/Directories/trunk/Identity/Images/Themes/Motifs.texi new file mode 100644 index 0000000..85ff9ea --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Motifs.texi @@ -0,0 +1,165 @@ +@subheading Goals + +The @file{trunk/Identity/Images/Themes} directory exists to: + +@itemize +@item Organize CentOS themes' artistic motifs. +@end itemize + +@subheading Description + +The artistic motif of theme is a graphic design component that +provides the visual style of themes, it is used as pattern to connect +all visual manifestations inside one unique theme. + +Artistic motifs are based on conceptual ideas. Conceptual ideas bring +the motivation, they are fuel for the engines of human imagination. +Good conceptual ideas may produce good motivation to produce almost +anything, and art works don't escape from it. + +@table @samp +@item TreeFlower +CentOS like trees, has roots, trunk, branches, leaves and flowers. Day +by day they work together in freedom, ruled by the laws of nature and +open standards, to show the beauty of its existence. +@item Modern +Modern, squares and circles flowing up. +@end table + +If you have new conceptual ideas for CentOS, then you can say that you +want to create a new artistic motif for CentOS. To create a new +artistic motif you need to create a directory under +@file{Identity/Images/Themes/} using a name coherent with your +conceptual idea. That name will be the name of your artistic motif. If +possible, when creating new conceptual ideas for CentOS, think about +what CentOS means for you, what does it makes you feel, take your +time, think deep, and share; you can improve the idea as time goes on. + +Once you have defined a name for your theme, you need to create the +motif structure of your theme. The motif structure is the basic +direcotry structure you'll use to work your ideas. Here is where you +organize your graphic design projects. + +To add a new motif structure to CentOS Artwork Repository, you need to +use the @command{centos-art} command line in the +@file{Identity/Images/Themes/} directory as described below: + +@example +centos-art add --motif=ThemeName +@end example + +The previous command will create the basic structure of themes for +you. The basic structure produced by @command{centos-art} command is +illustrated in the following figure: + +@example +trunk/Identity/Images/Themes/$ThemeName/ +|-- Backgrounds +| |-- Img +| `-- Tpl +|-- Info +| |-- Img +| `-- Tpl +|-- Palettes +`-- Screenshots +@end example + +@subheading Usage + +When designing artistic motifs for CentOS, consider the following +recommendations: + +@itemize +@item Give a unique (case-sensitive) name to your Motif. This name is +used as value wherever theme variable (@b{$THEME}) or translation marker +(@b{=THEME=}) is. Optionally, you can add a description about +inspiration and concepts behind your work. + +@item Use the location @file{trunk/Identity/Images/Themes/$THEME/} to +store your work. If it doesn't exist create it. Note that this require +you to have previous commit access in CentOS Artwork Repository. + +@item The CentOS Project is using the blue color (@b{#204c8d}) as base +color for its corporate visual identity. Use such base corporate color +information as much as possible in your artistic motif designs. + +@item Try to make your design fit one of the theme models. + +@item Feel free to make your art enterprise-level and beautiful. + +@item Add the following information on your artwork (both in a visible +design area and document metadata): + +@itemize + +@item The name (or logo) of your artistic motif. + +@item The copyright sentence: @b{Copyright (C) YEAR YOURNAME} + +@item The license under which the work is released. All CentOS Art +works are released under +@url{http://creativecommons.org/licenses/by-sa/3.0/,Creative Common +Share-Alike License 3.0} +(@url{http://creativecommons.org/licenses/by-sa/3.0/}). + +@end itemize +@end itemize + +@subheading See also + +@menu +* Directories trunk Identity Images Themes:: +* Directories trunk Identity:: +* Directories trunk:: +@end menu + +The @file{Backgrounds/} directory is used to organize artistic motif +background images and the projects used to build those images. + +Background images are linked (using the @b{import} feature of +Inkscape) inside almost all theme art works. This structure let you +make centralized changes on the visual identity and propagate them +quickly to other areas. + +In this configuration you design background images for different +screen resolutions based on the theme artistic motif. + +You may create different artistic motifs propositions based +on the same conceptual idea. The conceptual idea is what defines a +theme. Artistic motifs are interpretations of that idea. + +Inside this directory artistic motifs are organized by name (e.g., +TreeFlower, Modern, etc.). + +Each artistic motif directory represents just one unique artistic +motif. + +The artistic motif is graphic design used as common pattern to connect +all visual manifestations inside one unique theme. The artistic motif +is based on a conceptual idea. Artistic motifs provide visual style +to themes. + +Designing artistic motifs is for anyone interested in creating +beautiful themes for CentOS. When building a theme for CentOS, the +first design you need to define is the artistic motif. + +Inside CentOS Artwork Repository, theme visual styles (a.k.a., +artistic motifs) and theme visual structures (a.k.a., design models) +are two different working lines. When you design an artistic motif +for CentOS you concentrate on its visual style, and eventualy, use the +@command{centos-art} command line interface to render the visual +style, you are currently producing, against an already-made theme +model in order to produce the final result. Final images are stored +under @file{Motifs/} directory using the model name, and the model +directory structure as reference. + +The artistic motif base structure is used by @command{centos-art} to +produce images automatically. This section describes each directory of +CentOS artistic motif base structure. + +The @file{Backgrounds/} directory is probably the core component, +inside @file{Motifs/} directory structure. Inside @file{Backgrounds/} +directory you produce background images used by almost all theme +models (e.g., Distribution, Websites, Promotion, etc.). The +@file{Backgrounds/} directory can contain subdirectories to help you +organize the design process. diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texi b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texi new file mode 100644 index 0000000..3cfae8b --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texi @@ -0,0 +1,120 @@ +@subheading Goals + +This section describes the @emph{Flame} artistic motif. This section +may be useful for anyone interested in reproducing the @emph{Flame} +artistic motif, or in creating new artistic motifs for The CentOS +Project corporate visual identity. + +@subheading Description + +The @emph{Flame} artistic motif was built using the flame filter of +Gimp 2.2 in CentOS 5.5. + +The flame filter of Gimp can produce stunning, randomly generated +fractal patterns. The flame filter of Gimp gives us a great oportunity +to reduce the time used to produce new artistic motifs, because of its +``randomly generated'' nature. Once the artistic motif be created, it +is propagated through all visual manifestations of CentOS Project +corporate visual identity using the @file{centos-art.sh} script +(@pxref{Directories trunk Scripts}) inside the CentOS Artwork +Repository. + +To set the time intervals between each new visual style production, we +could reuse the CentOS distribution major release schema. I.e., we +could produce a new visual style, every two years, based on a new +``randomly generated'' flame pattern, and publish the whole corporate +visual identity (i.e., distribution stuff, promotion stuff, websites +stuff, etc.) with the new major release of CentOS distribution all +together at once. + +Producing a new visual style is not one day's task. Once we have +defined the artistic motif, we need to propagate it through all visual +manifestations of The CentOS Project corporate visual identity. When +we say that we could produce one new visual style every two years we +really mean: to work two years long in order to propagate a new visual +style to all visual manifestations of The CentOS Project corporate +visual identity. + +Obviously, in order to propagate one visual style to all different +visual manifestations of The CentOS Project corporate visual identity, +we need first to know which the visual manifestations are. To define +which visual manifestations are inside The CentOS Project corporate +visual identity is one of the goals the CentOS Artwork Repository and +this documentation manual are both aimed to satisfy. + +Once we define which the visual manifestation are, it is possible to +define how to produce them, and this way, organize the automation +process. Such automation process is one of the goals of +@file{centos-art.sh} script. + +With the combination of both CentOS Artwork Repository and +@file{centos-art.sh} scripts we define work lines where translators, +programmers, and graphic designers work together to distribute and +reduce the amount of time employed to produce The CentOS Project +monolithic corporate identity. + +From a monolithic corporate visual identity point of view, notice that +we are producing a new visual style for the same theme (i.e., +@emph{Flame}). It would be another flame design but still a flame +design. This idea is very important to be aware of, because we are +somehow ``refreshing'' the theme, not changing it at all. + +This way, as we are ``refreshing'' the theme, we still keep oursleves +inside the monolithic conception we are trying to be attached to +(i.e., one unique name, and one unique visual style for all visual +manifestations). + +Producing artistic motifs is a creative process that may consume long +time, specially for people without experienced knowledge on graphic +design land. Using ``randomly generated'' conception to produce +artistic motifs could be, practically, a way for anyone to follow in +order to produce maintainable artistic motifs in few steps. + +Due to the ``randomly generated'' nature of Flame filter, we find that +@emph{Flame} pattern is not always the same when we use @emph{Flame} +filter interface. + +Using the same pattern design for each visual manifestation is +essential in order to maintain the visual connection among all visual +manifestations inside the same theme. Occasionally, we may introduce +pattern variations in opacity, size, or even position but never change +the pattern design itself, nor the color information used by images +considered part of the same theme. + +@quotation +@strong{Important} +When we design background images, which are considered part of the +same theme, it is essential to use the same design pattern always. +This is what makes theme images to be visually connected among +themeselves, and so, the reason we use to define the word ``theme'' +as: a set of images visually connected among themeselves. +@end quotation + +In order for us to reproduce the same flame pattern always, +@emph{Flame} filter interface provides the @samp{Save} and @samp{Open} +options. The @samp{Save} option brings up a file save dialog that +allows you to save the current Flame settings for the plug-in, so that +you can recreate them later. The @samp{Open} option brings up a file +selector that allows you to open a previously saved Flame settings +file. + +The Flame settings we used in our example are saved in the file named +@file{800x600.xcf-flame.def}, inside the @file{Backgrounds/Xcf} +directory structure. + +@ifhtml +@subheading Screenshots + +@image{trunk/Identity/Images/Themes/Flame/1/Concept/motif-thumb-250,,,,jpg} +@image{trunk/Identity/Images/Themes/Flame/2/Concept/motif-thumb-250,,,,jpg} +@image{trunk/Identity/Images/Themes/Flame/3/Concept/motif-thumb-250,,,,jpg} +@end ifhtml + +@subheading See also + +@itemize +@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---. +@item @xref{Directories trunk Identity Images Themes}. +@item @xref{Directories trunk Identity}. +@item @xref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texi b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texi new file mode 100644 index 0000000..df12723 --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texi @@ -0,0 +1,24 @@ +@subheading Goals + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@ifhtml +@subheading Screenshots + +@image{trunk/Identity/Images/Themes/Modern/1/Concept/motif-thumb-250,,,,jpg} +@end ifhtml + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texi b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texi new file mode 100755 index 0000000..80f2bcc --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texi @@ -0,0 +1,28 @@ +@subheading Goals + +@itemize +@item ... +@end itemize + +@subheading Description + +@itemize +@item ... +@end itemize + +@subheading Usage + +@itemize +@item ... +@end itemize + +@ifhtml +@subheading Screenshots + +@image{trunk/Identity/Images/Themes/Pipes/1/Concept/motif-thumb-250,,,,jpg} +@end ifhtml + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texi b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texi new file mode 100644 index 0000000..9c31afb --- /dev/null +++ b/Manual/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texi @@ -0,0 +1,19 @@ +@subheading Goals + +@subheading Description + +@ifhtml +@subheading Screenshots + +@image{trunk/Identity/Images/Themes/TreeFlower/1/Concept/motif-thumb-250,,,,jpg} +@image{trunk/Identity/Images/Themes/TreeFlower/2/Concept/motif-thumb-250,,,,jpg} +@image{trunk/Identity/Images/Themes/TreeFlower/3/Concept/motif-thumb-250,,,,jpg} +@image{trunk/Identity/Images/Themes/TreeFlower/4/Concept/motif-thumb-250,,,,jpg} +@end ifhtml + +@subheading Usage + +@subheading See also + +@menu +@end menu diff --git a/Manual/Directories/trunk/Identity/Themes.texi b/Manual/Directories/trunk/Identity/Themes.texi deleted file mode 100644 index 1951e39..0000000 --- a/Manual/Directories/trunk/Identity/Themes.texi +++ /dev/null @@ -1,89 +0,0 @@ -@subheading Goals - -The @file{trunk/Identity/Themes/} directory exists to organize -production of CentOS themes. - -@subheading Description - -Initially, we start working themes on their trunk development line -(e.g., @file{trunk/Identity/Images/Themes/TreeFlower/}), here we -organize information that cannot be produced automatically (i.e., -background images, concepts, color information, screenshots, etc.). - -Later, when theme trunk development line is considered ``ready'' for -implementation (e.g., all required backgrounds have been designed), -we create a branch for it (e.g., -@file{branches/Identity/Images/Themes/TreeFlower/1/}). Once the -branch has been created, we forget that branch and continue working -the trunk development line while others (e.g., an artwork quality -assurance team) test the new branch for tunning it up. - -Once the branch has been tunned up, and considered ``ready'' for -release, it is freezed under @file{tags/} directory (e.g., -@file{tags/Identity/Images/Themes/TreeFower/1.0/}) for packagers, -webmasters, promoters, and anyone who needs images from that CentOS -theme the tag was created for. - -Both branches and tags, inside CentOS Artwork Repository, use -numerical values to identify themselves under the same location. -Branches start at one (i.e., @samp{1}) and increment one unit for each -branch created from the same trunk development line. Tags start at -zero (i.e., @samp{0}) and increment one unit for each tag created from -the same branch development line. - -@quotation -@strong{Convenction} Do not freeze trunk development lines using tags -directly. If you think you need to freeze a trunk development line, -create a branch for it and then freeze that branch instead. -@end quotation - -The trunk development line may introduce problems we cannot see -immediatly. Certainly, the high changable nature of trunk development -line complicates finding and fixing such problems. On the other hand, -the branched development lines provide a more predictable area where -only fixes/corrections to current content are commited up to -repository. - -If others find and fix bugs inside the branched development line, we -could merge such changes/experiences back to trunk development line -(not visversa) in order for future branches, created from trunk, to -benefit. - -Time intervals used to create branches and tags may vary, just as -different needs may arrive. For example, consider the release schema -of CentOS distribution: one major release every 2 years, security -updates every 6 months, support for 7 years long. Each time a CentOS -distribution is released, specially if it is a major release, there is -a theme need in order to cover CentOS distribution artwork -requirements. At this point, is where CentOS Artwork Repository comes -up to scene. - -Before releasing a new major release of CentOS distribution we create -a branch for one of several theme development lines available inside -the CentOS Artwork Repository, perform quality assurance on it, and -later, freeze that branch using tags. Once a the theme branch has been -frozen (under @file{tags/} directory), CentOS Packagers (the persons -whom build CentOS distribution) can use that frozen branch as source -location to fulfill CentOS distribution artwork needs. The same -applies to CentOS Webmasters (the persons whom build CentOS websites), -and any other visual manifestation required by the project. - -@subheading Usage - -In this location themes are organized in ``Models'' ---to store common -information--- and ``Motifs''---to store unique information. At -rendering time, both motifs and models are combined to produce the -final CentOS themes. CentOS themes can be tagged as ``Default'' or -``Alternative''. CentOS themes are maintained by CentOS community. - -@itemize -@item @xref{Directories trunk Identity Themes Models}. -@item @xref{Directories trunk Identity Themes Motifs}. -@end itemize - -@subheading See also - -@itemize -@item @ref{Directories trunk Identity}. -@item @ref{Directories trunk}. -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models.texi b/Manual/Directories/trunk/Identity/Themes/Models.texi deleted file mode 100644 index 3ce12c8..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models.texi +++ /dev/null @@ -1,46 +0,0 @@ -@subheading Goals - -This section describes design models from The CentOS Themes. - -@subheading Description - -Theme models let you modeling characteristics (e.g., dimensions, -translation markers, position of each element on the display area, -etc.) common to all themes. Theme models let you reduce the time -needed when propagating artistic motifs to different visual -manifestations. - -Theme models serves as a central pool of design templates for themes -to use. This way you can produce themes with different artistic motifs -but same characteristics. - -@subsubheading Default Design Model - -Default Design Models for CentOS Themes provide the common structural -information (e.g., image dimensions, translation markers, trademark -position, etc.) the @command{centos-art} script uses to produce images -when no other design model is specified. - -@subsubheading Alternative Design Models - -CentOS alternative theme models exist for people how want to use a -different visual style on their installations of CentOS distribution. -As the visual style is needed for a system already installed -components like Anaconda are not required inside alternative themes. -Inside alternative themes you find post-installation visual style only -(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative -themes are maintained by CentOS Community. - -@subheading Usage - -@itemize -@item @xref{Directories trunk Identity Themes Models Default}. -@end itemize - -@subheading See also - -@itemize -@item @ref{Directories trunk Identity Themes}. -@item @ref{Directories trunk Identity}. -@item @ref{Directories trunk}. -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default.texi deleted file mode 100644 index 46899fc..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default.texi +++ /dev/null @@ -1,79 +0,0 @@ -@subheading Goals - -This section describes the default design model of The CentOS Themes. - -@subheading Description - -The @file{trunk/Identity/Themes/Models/Default} directory implements -the concept of @emph{Default Design Model} for The CentOS Themes. The -CentOS Themes Default Design Model provides the common structural -information (e.g., image dimensions, translation markers, trademark -position, etc.) the @command{centos-art} script uses to produce images -when no other design model is specified. - -Deisgn models in this directory do use the @emph{CentOS Release -Brand}. The CentOS Release Brand is a combination of both The CentOS -Type and The CentOS Release Schema used to illustrate the major -release of The CentOS Distribution the image produced belongs to. --- -@strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) ----, for more information. - -The CentOS Project maintains near to four different major releases of -CentOS Distribution. Each major release of CentOS Distribution has -internal differences that make them unique and, at the same time, each -CentOS Distribution individually is tagged into the one unique visual -manifestation (i.e., Distribution). So, how could we implement the -monolithic visual structure in one visual manifestation that has -internal difference? - -To answer this question we broke the question in two parts and later -combined the resultant answers to build a possible solution. - -@table @strong -@item How to remark the internal differences visually? - -Merge both The CentOS Project Release Schema into The CentOS Project -Trademark to build The CentOS Project Release Trademark. The CentOS -Project Release Trademark remarks two things: first, it remarks the -image is from The CentOS Project and second, it remarks which major -release of CentOS Distribution does the image belongs to. ---- @strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) ---, for more -information on how to develop and improve The CentOS Project Brand. - -@item How to remark the visual resemblance? - -Use a common artistic motifs as background for all CentOS Distribution -images. @xref{Directories trunk Identity Themes Motifs}, for more -information. - -@item So, combining answers above, we could conclude that: - -In order to implement the CentOS Monolithic Visual Structure on CentOS -Distribution visual manifestations, a CentOS Release Trademark and a -background information based on one unique artistic motif should be -used in all remarkable images The CentOS Distribution visual -manifestation is made of. -@end table - -@quotation -@strong{Important} Remarking the CentOS Release Schema inside each -major release of CentOS Distribution ---or similar visual -manifestations--- takes @emph{high attention} inside The CentOS -Project corporate visual identity. It should be very clear for -everyone which major release of CentOS Distribution is being used. -@end quotation - -@subheading Usage - -@itemize -@item @xref{Directories trunk Identity Themes Models Default Distro}. -@item @xref{Directories trunk Identity Themes Models Default Concept}. -@end itemize - -@subheading See also - -@itemize -@item @ref{Directories trunk Identity Themes} -@item @ref{Directories trunk Identity Themes Models} -@item @ref{Directories trunk Identity Themes Motifs} -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Concept.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Concept.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Concept.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi deleted file mode 100644 index bbd5d46..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi +++ /dev/null @@ -1,111 +0,0 @@ -@subheading Goals - -This section organizes default design models for different major -releases of CentOS Distribution. - -@subheading Description - -In order to better understatand how this visual manifestation is -organized, it is necessary to consider what The CentOS Distribution is -and how it is released. - -@subsubheading The CentOS Distribution - -The CentOS Distribution is an Enterprise-class Linux Distribution -derived from sources freely provided to the public by a prominent -North American Enterprise Linux vendor. The CentOS Distribution -conforms fully with the upstream vendors redistribution policy and -aims to be 100% binary compatible. (The CentOS Project mainly changes -packages to remove upstream vendor branding and artwork.) - -The CentOS Distribution is developed by a small but growing team of -core developers. In turn the core developers are supported by an -active user community including system administrators, network -administrators, enterprise users, managers, core Linux contributors -and Linux enthusiasts from around the world. - -@subsubheading The CentOS Distribution Release Schema - -The upstream vendor has released 4 versions of their -@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds -the freely available SRPMS for. The upstream vendor releases security -updates as required by circumstances. The CentOS Project releases -rebuilds of security updates as soon as possible. Usually within 24 -hours (our stated goal is with 72 hours, but we are usually much -faster). - -The upstream vendor also releases numbered update sets for major -versions of their EL product from 2 to 4 times per year. There are new -ISOs from the upstream vendor provided for these update sets. Update -sets will be completed as soon as possible after the upstream vendor -releases their version @dots{} generally within 2 weeks. The CentOS -Project follows these conventions as well, so CentOS-3.9 correlates -with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6, -CentOS-5.1 correlates to EL 5 update 1, etc. - -One thing some people have problems understanding is that if you have -any CentOS-3 product and update it, you will be updated to the latest -CentOS-3.x version. - -The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 -product, you will be updated to the latest CentOS-4.x version, or to -the latest CentOS-5.x version if you are updating a CentOS-5 system. -This is exactly the same behavior as the upstream product. Let's -assume that the latest EL4 product is update 6. If you install the -upstream original EL4 CDs (the ones before any update set) and upgrade -via @command{yum}, you will have latest update set installed (EL4 -update 6 in our example). Since all updates within a major release -(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest -version when updates are performed (thus mimicking upstream behavior), -only the latest version is maintained in each main tree on The CentOS -Mirrors (@url{http://mirrors.centos.org/}). - -There is a CentOS Vault (@url{http://vault.centos.org/}) containing -old CentOS trees. This vault is a picture of the older tree when it -was removed from the main tree, and does not receive updates. It -should only be used for reference. - -The CentOS Distribution visual style is controlled by image files. -These image files are packaged inside The CentOS Distribution and made -visible once such packages are installed and executed. The way to go -for changing The CentOS Distribution visual style is changing all -those image files to add the desired visual style first and later, -repackage them to make them available inside the final iso files of -CentOS Distribution. - -@subheading Usage - -Sometimes, between major releases, image files inside packages can be -added, removed or just get the name changed. In order to describe such -variations, the design models directory structure is organized in the -same way the variations are introduced (i.e., through The CentOS -Distribution Release Schema). So, each major release of The CentOS -Distribution has its own design model directory structure. - -When a new package/component is added to one or all the major releases -of The CentOS Distribution, a design model directory structure for -that component needs to be created. Later, it is filled up with -related design models. Design models are created for each image file -inside the component that need to be rebuilt in order to set the -visual style and brand information correctly. - -When a package is removed from one or all major releases of The CentOS -Distribution, the design model directory structure releated to that -package/component is no longer used. However, it could be very useful -for historical reasons. Also, someone could feel motivation enough to -keep himself documenting it or supporting it for whatever reason. - -@itemize -@item @xref{Directories trunk Identity Themes Models Default Distro -5}. -@end itemize - -@subheading See also - -@itemize -@item @ref{Directories trunk Identity Themes Models Default}. -@item @ref{Directories trunk Identity Themes Models}. -@item @ref{Directories trunk Identity Themes}. -@item @ref{Directories trunk Identity}. -@item @ref{Directories trunk}. -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi deleted file mode 100755 index 19e11c5..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi +++ /dev/null @@ -1,35 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Syslinux}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Anaconda}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Rhgb}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Gdm}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Kdm}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Grub}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Gsplash}. -@item @xref{Directories trunk Identity Themes Models Default Distro 5 Ksplash}. -@end itemize - -@subheading See also - -@itemize -@item @ref{Directories trunk Identity Themes Models Default Distro}. -@item @ref{Directories trunk Identity Themes Models Default}. -@item @ref{Directories trunk Identity Themes Models}. -@item @ref{Directories trunk Identity Themes}. -@item @ref{Directories trunk Identity}. -@item @ref{Directories trunk}. -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi deleted file mode 100644 index c10b6dd..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Anaconda.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@subheading Usage - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Firstboot.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Firstboot.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Firstboot.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gdm.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gdm.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gdm.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Grub.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Grub.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Grub.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gsplash.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gsplash.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Gsplash.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Kdm.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Kdm.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Kdm.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Ksplash.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Ksplash.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Ksplash.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Rhgb.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Rhgb.texi deleted file mode 100755 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Rhgb.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Syslinux.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Syslinux.texi deleted file mode 100755 index d6bb628..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5/Syslinux.texi +++ /dev/null @@ -1,23 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@itemize -@item ... -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Posters.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Posters.texi deleted file mode 100644 index e226b31..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Posters.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Motifs.texi b/Manual/Directories/trunk/Identity/Themes/Motifs.texi deleted file mode 100644 index 4b91b89..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Motifs.texi +++ /dev/null @@ -1,165 +0,0 @@ -@subheading Goals - -The @file{trunk/Identity/Images/Themes} directory exists to: - -@itemize -@item Organize CentOS themes' artistic motifs. -@end itemize - -@subheading Description - -The artistic motif of theme is a graphic design component that -provides the visual style of themes, it is used as pattern to connect -all visual manifestations inside one unique theme. - -Artistic motifs are based on conceptual ideas. Conceptual ideas bring -the motivation, they are fuel for the engines of human imagination. -Good conceptual ideas may produce good motivation to produce almost -anything, and art works don't escape from it. - -@table @samp -@item TreeFlower -CentOS like trees, has roots, trunk, branches, leaves and flowers. Day -by day they work together in freedom, ruled by the laws of nature and -open standards, to show the beauty of its existence. -@item Modern -Modern, squares and circles flowing up. -@end table - -If you have new conceptual ideas for CentOS, then you can say that you -want to create a new artistic motif for CentOS. To create a new -artistic motif you need to create a directory under -@file{Identity/Images/Themes/} using a name coherent with your -conceptual idea. That name will be the name of your artistic motif. If -possible, when creating new conceptual ideas for CentOS, think about -what CentOS means for you, what does it makes you feel, take your -time, think deep, and share; you can improve the idea as time goes on. - -Once you have defined a name for your theme, you need to create the -motif structure of your theme. The motif structure is the basic -direcotry structure you'll use to work your ideas. Here is where you -organize your graphic design projects. - -To add a new motif structure to CentOS Artwork Repository, you need to -use the @command{centos-art} command line in the -@file{Identity/Images/Themes/} directory as described below: - -@example -centos-art add --motif=ThemeName -@end example - -The previous command will create the basic structure of themes for -you. The basic structure produced by @command{centos-art} command is -illustrated in the following figure: - -@example -trunk/Identity/Images/Themes/$ThemeName/ -|-- Backgrounds -| |-- Img -| `-- Tpl -|-- Info -| |-- Img -| `-- Tpl -|-- Palettes -`-- Screenshots -@end example - -@subheading Usage - -When designing artistic motifs for CentOS, consider the following -recommendations: - -@itemize -@item Give a unique (case-sensitive) name to your Motif. This name is -used as value wherever theme variable (@b{$THEME}) or translation marker -(@b{=THEME=}) is. Optionally, you can add a description about -inspiration and concepts behind your work. - -@item Use the location @file{trunk/Identity/Images/Themes/$THEME/} to -store your work. If it doesn't exist create it. Note that this require -you to have previous commit access in CentOS Artwork Repository. - -@item The CentOS Project is using the blue color (@b{#204c8d}) as base -color for its corporate visual identity. Use such base corporate color -information as much as possible in your artistic motif designs. - -@item Try to make your design fit one of the theme models. - -@item Feel free to make your art enterprise-level and beautiful. - -@item Add the following information on your artwork (both in a visible -design area and document metadata): - -@itemize - -@item The name (or logo) of your artistic motif. - -@item The copyright sentence: @b{Copyright (C) YEAR YOURNAME} - -@item The license under which the work is released. All CentOS Art -works are released under -@url{http://creativecommons.org/licenses/by-sa/3.0/,Creative Common -Share-Alike License 3.0} -(@url{http://creativecommons.org/licenses/by-sa/3.0/}). - -@end itemize -@end itemize - -@subheading See also - -@menu -* Directories trunk Identity Themes:: -* Directories trunk Identity:: -* Directories trunk:: -@end menu - -The @file{Backgrounds/} directory is used to organize artistic motif -background images and the projects used to build those images. - -Background images are linked (using the @b{import} feature of -Inkscape) inside almost all theme art works. This structure let you -make centralized changes on the visual identity and propagate them -quickly to other areas. - -In this configuration you design background images for different -screen resolutions based on the theme artistic motif. - -You may create different artistic motifs propositions based -on the same conceptual idea. The conceptual idea is what defines a -theme. Artistic motifs are interpretations of that idea. - -Inside this directory artistic motifs are organized by name (e.g., -TreeFlower, Modern, etc.). - -Each artistic motif directory represents just one unique artistic -motif. - -The artistic motif is graphic design used as common pattern to connect -all visual manifestations inside one unique theme. The artistic motif -is based on a conceptual idea. Artistic motifs provide visual style -to themes. - -Designing artistic motifs is for anyone interested in creating -beautiful themes for CentOS. When building a theme for CentOS, the -first design you need to define is the artistic motif. - -Inside CentOS Artwork Repository, theme visual styles (a.k.a., -artistic motifs) and theme visual structures (a.k.a., design models) -are two different working lines. When you design an artistic motif -for CentOS you concentrate on its visual style, and eventualy, use the -@command{centos-art} command line interface to render the visual -style, you are currently producing, against an already-made theme -model in order to produce the final result. Final images are stored -under @file{Motifs/} directory using the model name, and the model -directory structure as reference. - -The artistic motif base structure is used by @command{centos-art} to -produce images automatically. This section describes each directory of -CentOS artistic motif base structure. - -The @file{Backgrounds/} directory is probably the core component, -inside @file{Motifs/} directory structure. Inside @file{Backgrounds/} -directory you produce background images used by almost all theme -models (e.g., Distribution, Websites, Promotion, etc.). The -@file{Backgrounds/} directory can contain subdirectories to help you -organize the design process. diff --git a/Manual/Directories/trunk/Identity/Themes/Motifs/Flame.texi b/Manual/Directories/trunk/Identity/Themes/Motifs/Flame.texi deleted file mode 100644 index 22ca756..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Motifs/Flame.texi +++ /dev/null @@ -1,120 +0,0 @@ -@subheading Goals - -This section describes the @emph{Flame} artistic motif. This section -may be useful for anyone interested in reproducing the @emph{Flame} -artistic motif, or in creating new artistic motifs for The CentOS -Project corporate visual identity. - -@subheading Description - -The @emph{Flame} artistic motif was built using the flame filter of -Gimp 2.2 in CentOS 5.5. - -The flame filter of Gimp can produce stunning, randomly generated -fractal patterns. The flame filter of Gimp gives us a great oportunity -to reduce the time used to produce new artistic motifs, because of its -``randomly generated'' nature. Once the artistic motif be created, it -is propagated through all visual manifestations of CentOS Project -corporate visual identity using the @file{centos-art.sh} script -(@pxref{Directories trunk Scripts}) inside the CentOS Artwork -Repository. - -To set the time intervals between each new visual style production, we -could reuse the CentOS distribution major release schema. I.e., we -could produce a new visual style, every two years, based on a new -``randomly generated'' flame pattern, and publish the whole corporate -visual identity (i.e., distribution stuff, promotion stuff, websites -stuff, etc.) with the new major release of CentOS distribution all -together at once. - -Producing a new visual style is not one day's task. Once we have -defined the artistic motif, we need to propagate it through all visual -manifestations of The CentOS Project corporate visual identity. When -we say that we could produce one new visual style every two years we -really mean: to work two years long in order to propagate a new visual -style to all visual manifestations of The CentOS Project corporate -visual identity. - -Obviously, in order to propagate one visual style to all different -visual manifestations of The CentOS Project corporate visual identity, -we need first to know which the visual manifestations are. To define -which visual manifestations are inside The CentOS Project corporate -visual identity is one of the goals the CentOS Artwork Repository and -this documentation manual are both aimed to satisfy. - -Once we define which the visual manifestation are, it is possible to -define how to produce them, and this way, organize the automation -process. Such automation process is one of the goals of -@file{centos-art.sh} script. - -With the combination of both CentOS Artwork Repository and -@file{centos-art.sh} scripts we define work lines where translators, -programmers, and graphic designers work together to distribute and -reduce the amount of time employed to produce The CentOS Project -monolithic corporate identity. - -From a monolithic corporate visual identity point of view, notice that -we are producing a new visual style for the same theme (i.e., -@emph{Flame}). It would be another flame design but still a flame -design. This idea is very important to be aware of, because we are -somehow ``refreshing'' the theme, not changing it at all. - -This way, as we are ``refreshing'' the theme, we still keep oursleves -inside the monolithic conception we are trying to be attached to -(i.e., one unique name, and one unique visual style for all visual -manifestations). - -Producing artistic motifs is a creative process that may consume long -time, specially for people without experienced knowledge on graphic -design land. Using ``randomly generated'' conception to produce -artistic motifs could be, practically, a way for anyone to follow in -order to produce maintainable artistic motifs in few steps. - -Due to the ``randomly generated'' nature of Flame filter, we find that -@emph{Flame} pattern is not always the same when we use @emph{Flame} -filter interface. - -Using the same pattern design for each visual manifestation is -essential in order to maintain the visual connection among all visual -manifestations inside the same theme. Occasionally, we may introduce -pattern variations in opacity, size, or even position but never change -the pattern design itself, nor the color information used by images -considered part of the same theme. - -@quotation -@strong{Important} -When we design background images, which are considered part of the -same theme, it is essential to use the same design pattern always. -This is what makes theme images to be visually connected among -themeselves, and so, the reason we use to define the word ``theme'' -as: a set of images visually connected among themeselves. -@end quotation - -In order for us to reproduce the same flame pattern always, -@emph{Flame} filter interface provides the @samp{Save} and @samp{Open} -options. The @samp{Save} option brings up a file save dialog that -allows you to save the current Flame settings for the plug-in, so that -you can recreate them later. The @samp{Open} option brings up a file -selector that allows you to open a previously saved Flame settings -file. - -The Flame settings we used in our example are saved in the file named -@file{800x600.xcf-flame.def}, inside the @file{Backgrounds/Xcf} -directory structure. - -@ifhtml -@subheading Screenshots - -@image{trunk/Identity/Images/Themes/Flame/1/Concept/motif-thumb-250,,,,jpg} -@image{trunk/Identity/Images/Themes/Flame/2/Concept/motif-thumb-250,,,,jpg} -@image{trunk/Identity/Images/Themes/Flame/3/Concept/motif-thumb-250,,,,jpg} -@end ifhtml - -@subheading See also - -@itemize -@item @xref{Directories trunk Identity Themes Motifs}. -@item @xref{Directories trunk Identity Themes}. -@item @xref{Directories trunk Identity}. -@item @xref{Directories trunk}. -@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Motifs/Modern.texi b/Manual/Directories/trunk/Identity/Themes/Motifs/Modern.texi deleted file mode 100644 index df12723..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Motifs/Modern.texi +++ /dev/null @@ -1,24 +0,0 @@ -@subheading Goals - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@ifhtml -@subheading Screenshots - -@image{trunk/Identity/Images/Themes/Modern/1/Concept/motif-thumb-250,,,,jpg} -@end ifhtml - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Motifs/Pipes.texi b/Manual/Directories/trunk/Identity/Themes/Motifs/Pipes.texi deleted file mode 100755 index 80f2bcc..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Motifs/Pipes.texi +++ /dev/null @@ -1,28 +0,0 @@ -@subheading Goals - -@itemize -@item ... -@end itemize - -@subheading Description - -@itemize -@item ... -@end itemize - -@subheading Usage - -@itemize -@item ... -@end itemize - -@ifhtml -@subheading Screenshots - -@image{trunk/Identity/Images/Themes/Pipes/1/Concept/motif-thumb-250,,,,jpg} -@end ifhtml - -@subheading See also - -@menu -@end menu diff --git a/Manual/Directories/trunk/Identity/Themes/Motifs/TreeFlower.texi b/Manual/Directories/trunk/Identity/Themes/Motifs/TreeFlower.texi deleted file mode 100644 index 9c31afb..0000000 --- a/Manual/Directories/trunk/Identity/Themes/Motifs/TreeFlower.texi +++ /dev/null @@ -1,19 +0,0 @@ -@subheading Goals - -@subheading Description - -@ifhtml -@subheading Screenshots - -@image{trunk/Identity/Images/Themes/TreeFlower/1/Concept/motif-thumb-250,,,,jpg} -@image{trunk/Identity/Images/Themes/TreeFlower/2/Concept/motif-thumb-250,,,,jpg} -@image{trunk/Identity/Images/Themes/TreeFlower/3/Concept/motif-thumb-250,,,,jpg} -@image{trunk/Identity/Images/Themes/TreeFlower/4/Concept/motif-thumb-250,,,,jpg} -@end ifhtml - -@subheading Usage - -@subheading See also - -@menu -@end menu