diff --git a/Identity/Manual/Directories/trunk/Identity.texi b/Identity/Manual/Directories/trunk/Identity.texi index b241877..d35acfb 100644 --- a/Identity/Manual/Directories/trunk/Identity.texi +++ b/Identity/Manual/Directories/trunk/Identity.texi @@ -5,54 +5,57 @@ CentOS Project Corporate Identity}. @subsection Description -The CentOS Project corporate identity is the ``persona'' of the +The CentOS Project Corporate Identity is the ``persona'' of the organization known as The CentOS Project. The CentOS Project -corporate identity plays a significant role in the way the CentOS +Corporate Identity plays a significant role in the way the CentOS Project, as organization, presents itself to both internal and external stakeholders. In general terms, the CentOS Project corporate visual identity expresses the values and ambitions of the CentOS Project organization, its business, and its characteristics. -The CentOS Project corporate identity provides visibility, +The CentOS Project Corporate Identity provides visibility, recognizability, reputation, structure and identification to The CentOS Project organization by means of @emph{Corporate Design}, @emph{Corporate Communication}, and @emph{Corporate Behaviour}. @subsubsection Corporate Design -The CentOS Project corporate design is applied to every single visual +The CentOS Project Corporate Design is applied to every single visual manifestations The CentOS Project as organization wants to express its existence. Examples of the most relevant visual manifestations inside The CentOS Project are @emph{The CentOS Distribution}, @emph{The CentOS Web} and @emph{The CentOS Stationery}. -The CentOS Project corporate design is organized in the following +The CentOS Project Corporate Design is organized in the following work-lines: @table @strong @item The CentOS Brand -The CentOS Brand is the name or trademark that connects the producer -with their products. In this case, the producer is The CentOS Project -and the products are The CentOS Project visual manifestations. +The CentOS Brand provides the one unique name or trademark that +connects the producer with their products. In this case, the producer +is The CentOS Project and the products are The CentOS Project visual +manifestations. @xref{Directories trunk Identity Brands}, for more information. -@item The CentOS Colors +@item The CentOS Palettes -The CentOS Fonts provides the color information used along The CentOS -Project visual manifestations. +The CentOS Palettes provide the @emph{Corporate Color} information +used along The CentOS Project visual manifestations. @xref{Directories trunk Identity Palettes}, for more information. + @item The CentOS Fonts -The CentOS Fonts provides the typography information used along The -CentOS Project visual manifestations. +The CentOS Fonts provide the @emph{Corporate Typography} information +used along The CentOS Project visual manifestations. @xref{Directories trunk Identity Fonts}, for more information. + @item The CentOS Themes -The CentOS Themes provides structural information and visual style -information, as well, used along The CentOS Project visual +The CentOS Themes provide the @emph{Corporate Structure} and the +@emph{Corporate Visual Style} used along The CentOS Project visual manifestations. @xref{Directories trunk Identity Themes}, for more information. @@ -60,28 +63,29 @@ manifestations. @subsubsection Corporate Communication -The CentOS Project corporate communication is based on community -communication. In that sake, the following media are available for -corporate communication: +The CentOS Project Corporate Communication is based on @emph{Community +Communication}. In that sake, the following media are available: @itemize +@item The CentOS Chat (@code{#centos}, @code{#centos-social}, +@code{#centos-devel} on irc.freenode.net) @item The CentOS Mailing Lists (@url{http://lists.centos.org/}). @item The CentOS Forums (@url{http://forums.centos.org/}). @end itemize @subsubsection Corporate Behaviour -The CentOS Project corporate behaviour is based on community -behaviour. +The CentOS Project Corporate Behaviour is based on @emph{Community +Behaviour}. @subsubsection Corporate Structure -The CentOS Project corporate structure is based on a @emph{monolithic} -corporate visual identity structure. In this structure, we use one -unique name (The CentOS Brand) and one unique visual style (The CentOS -Theme) in all The CentOS Project visual manifestations. +The CentOS Project Corporate Structure is based on a @emph{Monolithic +Corporate Visual Identity Structure}. In this structure, one unique +name and one unique visual style is used in all visual manifestation +of The CentOS Project. -Inside a monolithic corporate visual identity structure, internal and +In a monolithic corporate visual identity structure, internal and external stakeholders use to feel a strong sensation of uniformity, orientation, and identification with the organization. No matter if you are visiting web sites, using the distribution, or acting on @@ -89,13 +93,14 @@ social events, the one unique name and one unique visual style connects them all to say: @emph{Hey! we are all part of The CentOS Project}. -Other corporate structures have been considered as well, but they -introduce visual contradictions we need to be aware of. In that sake, -lets describe the idea of: @emph{Producing one different visual style -for each major release of The CentOS Distribution}. +Other corporate structures for The CentOS Project have been considered +as well, but they could introduce visual contradictions we need to be +aware of. In that sake, lets describe the idea of: @emph{Producing +one different visual style for each major release of The CentOS +Distribution}. The CentOS Project maintains near to four different major releases of -The CentOS Distribution parallely in time and that fact makes one part +The CentOS Distribution, parallely in time. This fact makes one part of The CentOS Project structural design, but just one part, not the complete structural design. In order to produce the correct corporate structure for The CentOS Project we need to concider all the visual @@ -104,28 +109,24 @@ manifestations The CentOS Project is made of, not just one of them. If one different visual style is used for each major release of The CentOS Distribution, which one of those different visual styles would be used to cover the remaining visual manifestations The CentOS -Project is made of. Would we end up with four different visual styles, -one for each distribution? In that case, why The CentOS Distribution -we use shows one visual style, The CentOS Web sites another and The -CentOS Stationery even another completly different one? Isn't them -all part of the same project? +Project is made of (e.g., The CentOS Web, Stationery)? -Probably you be thinking, that's right, but The CentOS Brand connects +Probably you are thinking, that's right, but The CentOS Brand connects them all already, why would we need to join them up into the same visual style too, isn't it more work to do, and harder to maintain? -Harder to maintain, more work to do, it is probably. Specially when -you consider that The CentOS Project has proven stability and -consistency through time and that, certainly, didn't come through -swinging magical wangs or something but hardly working out to automate -tasks and so providing maintainance through time. Said that, we -consider that The CentOS Project visual structure should be consequent -with such stability and consistency tradition. It is true The CentOS -Brand does connect all the visual manifestations it is present on, but -that connection would be stronger if one unique visual style backups -it. In fact, whatever thing you do to strength the visual connection -among The CentOS Project visual manifestations would be very good in -favor of The CentOS Project recognition. +Harder to maintain, more work to do, probably. Specially when you +consider that The CentOS Project has proven stability and consistency +through time and that, certainly, didn't come through swinging magical +wangs or something but hardly working out to automate tasks and +providing maintainance through time. Said that, we consider that The +CentOS Project Visual Structure should be consequent with such +stability and consistency tradition. It is true The CentOS Brand does +connect all the visual manifestations it is present on, but that +connection would be stronger if one unique visual style backups it. +In fact, whatever thing you do to strength the visual connection among +The CentOS Project visual manifestations would be very good in favor +of The CentOS Project recognition. Obviously, having just one visual style in all visual manifestations for eternity would be a very boring thing and would give the idea of a @@ -142,11 +143,12 @@ Artwork Repository. @subsection Usage -The @file{trunk/} directory structure is organized in +The @file{trunk/Identity/} directory structure is organized in @emph{renderable} and @emph{non-renderable} directories. Generally, -renderable directories contain two non-renderable directories inside, -one to store design templates (the @file{Tpl/} directory), and other -to store the content produced (the @file{Img/} directory). +renderable directories are stored under @file{trunk/Identity/Images} +and @file{trunk/Identity/Themes/Motifs} directories. These directories +contain the image files used to implemente The CentOS Project +Corporate Identity. In order to produce content inside rendereble directories, you can use the following command: @@ -158,39 +160,39 @@ centos-art render trunk/Identity/Path/To/Dir @quotation @strong{Warning} If the @command{centos-art} command-line is not found in your workstation, it is probably because you haven't -prepared it for using The CentOS Artwork Repository yet. +prepared your workstation for using The CentOS Artwork Repository yet. @xref{Directories trunk Scripts Functions Verify}, for more information. @end quotation -This command takes one design template from the template directory and -creates an instance of it in order to apply translation messages on -it, if any. Later, using the design template instance, the command -renders the final content based on whether the design template -instance is a SVG file or a Docbook file. If the design template -instace is a SVG file, the final content produced is a PNG image. On -the other hand, if the design template instance is a Docbook file, the -final content produced is a XHTML file. Final content is stored in the -image directory using the design template directory paths as referece. -The rendition flow described so far is known as the +This command takes one design template (a.k.a., design model) from the +template directory and creates an instance of it in order to apply +translation messages, if any. Later, using the translated design +template instance, the command renders the final content based on +whether the design template instance is a SVG file or XHTML. If the +design template instace is a SVG file, the final content produced is a +PNG image. On the other hand, if the design template instance is a +XHTML file, the final content produced is a XHTML file. The rendition +flow described so far is known as the @command{centos-art.sh} script @emph{base-rendition} flow. -Besides the base-rendition flow, the @command{centos-art} provides the +Besides the base-rendition flow, the @command{centos-art} provides @emph{post-rendition} and @emph{last-rendition} flows. The post-rendition flow is applied to files produced as result of base-rendition flow under the same directory structure. For example, you can use post-rendition action to convert the PNG base output into -different outputs (e.g., JPG, PDF, etc.) before passing to process the -next file in the same directory structure. The last-rendition flow is -applied to all files produced as result of both base-rendition and -post-rendition flows in the same directory structure, just before -passing to process a different directory structure. For example, the -@file{Preview.png} image from Ksplash component is made of three -images. In order to build the @file{Preview.png} image through -@command{centos-art} we need to wait for all the three images the -@file{Preview.png} image is made of to be rendered, so we can combine -them all together into just one image (i.e., the @file{Preview.png} -image). This is something we can't do using post-rendition flow. +different outputs formats (e.g., JPG, PDF, etc.) before passing to +process the next file in the same directory structure. The +last-rendition flow, on the other hand, is applied to all files +produced as result of both base-rendition and post-rendition flows in +the same directory structure, just before passing to process a +different directory structure. For example, the @file{Preview.png} +image from Ksplash component is made of three images. In order to +build the @file{Preview.png} image through @command{centos-art.sh} we +need to wait for all the three images the @file{Preview.png} image is +made of to be rendered in order to combine them all together into just +one image (i.e., the @file{Preview.png} image). This is something we +can't do using post-rendition flow. Inside @file{trunk/Identity} directory structure, you can find that base-rendition, post-rendition and last-rendition flows can be @@ -199,13 +201,13 @@ directory-specific rendition exists to automatically process specific renderable directories in very specific ways. Using directory-specific rendition speeds up production of different components like Syslinux, Grub, Gdm, Kdm and Ksplash that require intermediate formats or even -several independent files, in order to reach its final construction. -Directory-specific rendition is a way to programmatically describe how -specific art works are built in and organized inside The CentOS -Artwork Repository. Such descriptions have been added to -@command{centos-art} command-line to let you produce them all with -just one single command, as fast as your machine can be able to handle -it. +several independent files, in order to reach the final content +construction. Directory-specific rendition is a way to +programmatically describe how specific art works are built in and +organized inside The CentOS Artwork Repository. Such descriptions +have been added to @command{centos-art.sh} command-line to let you +produce them all with just one single command, as fast as your machine +can be able to handle it. @xref{Directories trunk Scripts Functions Identity}, for more information about the @command{identity} functionality of @@ -214,7 +216,7 @@ information about the @command{identity} functionality of @subsection See also See @url{http://en.wikipedia.org/Corporate_identity} (and related -links), for general information on corporate identity. +links), for general information on Corporate Identity. Specially useful has been, and still be, the book @emph{Corporate Identity} by Wally Olins (1989). This book provides many conceptual