|
 |
9c6e0d |
@subsection Goals
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@itemize
|
|
|
9c6e0d |
@item ...
|
|
|
9c6e0d |
@end itemize
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@subsection Description
|
|
|
9c6e0d |
|
|
|
9c6e0d |
It applies to all major releases of CentOS distribution.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@subsubsection One theme for all major releases
|
|
|
9c6e0d |
|
|
|
9c6e0d |
Sometimes, specific visual manifestations are formed by common
|
|
|
9c6e0d |
components which have internal differences. That is the case of CentOS
|
|
|
9c6e0d |
distribution visual manifestation.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
Since a visual style point of view, the CentOS distributions share
|
|
|
9c6e0d |
common artwork components like Anaconda ---to cover the CentOS
|
|
|
9c6e0d |
distribution installation---, BootUp ---to cover the CentOS
|
|
|
9c6e0d |
distribution start up---, and Backgrounds ---to cover the CentOS
|
|
|
9c6e0d |
distribution desktop---. Now, since a technical point of view, those
|
|
|
9c6e0d |
common artwork components are made of software improved constantly.
|
|
|
9c6e0d |
So, we need to find a way to keep one unique name and one unique
|
|
|
9c6e0d |
visual style in artwork components that have internal difference and
|
|
|
9c6e0d |
also remark internal difference as well.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@quotation
|
|
|
9c6e0d |
@strong{Important} Remarking the CentOS release schema inside each
|
|
|
9c6e0d |
major release of CentOS distribution ---or similar visual
|
|
|
9c6e0d |
manifestation--- takes @emph{high attention} inside The CentOS Project
|
|
|
9c6e0d |
corporate visual identity. It should be very clear for people which
|
|
|
9c6e0d |
major release of CentOS distribution they are using.
|
|
|
9c6e0d |
@end quotation
|
|
|
9c6e0d |
|
|
|
9c6e0d |
In order to remark the CentOS release schema, the CentOS Artwork SIG
|
|
|
9c6e0d |
uses a release-specific brand design named ``The CentOS Release
|
|
|
9c6e0d |
Brand''. The CentOS release brand is compossed by the CentOS logotype
|
|
|
9c6e0d |
@emph{and} the CentOS major release number (as specified in CentOS
|
|
|
9c6e0d |
release schema definition). In this solution, the CentOS release brand
|
|
|
9c6e0d |
is set inside all release-specific artworks (e.g., distribution,
|
|
|
9c6e0d |
installation media, etc.) in remarkable way. The CentOS release
|
|
|
9c6e0d |
brand is the design component that lets us remark the CentOS release
|
|
|
9c6e0d |
schema inside the monolithic corporate visual identity structure we
|
|
|
9c6e0d |
propose to use.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@subsubsection One theme for each major release
|
|
|
9c6e0d |
|
|
|
9c6e0d |
Other way we've been using to remark CentOS release schema is
|
|
|
9c6e0d |
applying one unique theme for @emph{each} major release of CentOS
|
|
|
9c6e0d |
distribution. That is, if we have 4 major releases of CentOS
|
|
|
9c6e0d |
distribution, we need to provide 4 different themes to cover each
|
|
|
9c6e0d |
CentOS distribution available.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
Inside CentOS Artwork Repository, you can create many themes and that
|
|
|
9c6e0d |
is very convenient. But using one unique theme for @emph{each} major
|
|
|
9c6e0d |
release of CentOS distribution would bring visual isolation among
|
|
|
9c6e0d |
distributions, websites and promotion visual manifestations. If the
|
|
|
9c6e0d |
CentOS project would maintain just one CentOS distribution (and many
|
|
|
9c6e0d |
experienced graphic designers ready to create beautiful artworks) this
|
|
|
9c6e0d |
model would be nice. Indeed, this model looks quite similar to that
|
|
|
9c6e0d |
one used by Fedora project, doesn't it. But no, the CentOS project
|
|
|
9c6e0d |
maintains near to 4 major releases of CentOS distribution in parallel,
|
|
|
9c6e0d |
and that fact makes a huge difference since the corporate visual
|
|
|
9c6e0d |
identity point of view.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
If we use one unique theme for @emph{each} major release of CentOS
|
|
|
9c6e0d |
distribution, which one of those themes, does we use to cover other
|
|
|
9c6e0d |
CentOS visual manifestations, like websites and promotion stuff?
|
|
|
9c6e0d |
|
|
|
9c6e0d |
In whatever case you choose some release-specific distribution user
|
|
|
9c6e0d |
will be visually isolated from other CentOS visual manifestations like
|
|
|
9c6e0d |
websites and promotion stuff, even if the CentOS brand is present in
|
|
|
9c6e0d |
all visual manifestations. In such a case, probably, users will end up
|
|
|
9c6e0d |
asking themselves, why my CentOS distribution has this design and the
|
|
|
9c6e0d |
CentOS website another one? Isn't them on the same project? With luck
|
|
|
9c6e0d |
the CentOS brand will exonerate user form visual isolation.
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@subsection Usage
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@subsection See also
|
|
|
9c6e0d |
|
|
|
9c6e0d |
@menu
|
|
|
9c6e0d |
@end menu
|