@subsection Goals

@itemize

@item ...

@end itemize

@subsection Description

It applies to all major releases of CentOS distribution.

@subsubsection One theme for all major releases

Sometimes, specific visual manifestations are formed by common

components which have internal differences. That is the case of CentOS

distribution visual manifestation.  

Since a visual style point of view, the CentOS distributions share

common artwork components like Anaconda ---to cover the CentOS

distribution installation---, BootUp ---to cover the CentOS

distribution start up---, and Backgrounds ---to cover the CentOS

distribution desktop---.  Now, since a technical point of view, those

common artwork components are made of software improved constantly.

So, we need to find a way to keep one unique name and one unique

visual style in artwork components that have internal difference and

also remark internal difference as well.

@quotation

@strong{Important} Remarking the CentOS release schema inside each

major release of CentOS distribution ---or similar visual

manifestation--- takes @emph{high attention} inside The CentOS Project

corporate visual identity. It should be very clear for people which

major release of CentOS distribution they are using.

@end quotation

In order to remark the CentOS release schema, the CentOS Artwork SIG

uses a release-specific brand design named ``The CentOS Release

Brand''. The CentOS release brand is compossed by the CentOS logotype

@emph{and} the CentOS major release number (as specified in CentOS

release schema definition). In this solution, the CentOS release brand

is set inside all release-specific artworks (e.g., distribution,

installation media, etc.) in remarkable way.   The CentOS release

brand is the design component that lets us remark the CentOS release

schema inside the monolithic corporate visual identity structure we

propose to use.

@subsubsection One theme for each major release

Other way we've been using to remark CentOS release schema is

applying one unique theme for @emph{each} major release of CentOS

distribution.  That is, if we have 4 major releases of CentOS

distribution, we need to provide 4 different themes to cover each

CentOS distribution available.

Inside CentOS Artwork Repository, you can create many themes and that

is very convenient. But using one unique theme for @emph{each} major

release of CentOS distribution would bring visual isolation among

distributions, websites and promotion visual manifestations. If the

CentOS project would maintain just one CentOS distribution (and many

experienced graphic designers ready to create beautiful artworks) this

model would be nice. Indeed, this model looks quite similar to that

one used by Fedora project, doesn't it. But no, the CentOS project

maintains near to 4 major releases of CentOS distribution in parallel,

and that fact makes a huge difference since the corporate visual

identity point of view.

If we use one unique theme for @emph{each} major release of CentOS

distribution, which one of those themes, does we use to cover other

CentOS visual manifestations, like websites and promotion stuff? 

In whatever case you choose some release-specific distribution user

will be visually isolated from other CentOS visual manifestations like

websites and promotion stuff, even if the CentOS brand is present in

all visual manifestations. In such a case, probably, users will end up

asking themselves, why my CentOS distribution has this design and the

CentOS website another one? Isn't them on the same project? With luck

the CentOS brand will exonerate user form visual isolation.

@subsection Usage

@subsection See also

@menu

@end menu