This directory organizes CentOS Distribution default design models in the following categories:

Syslinux
     Contains design models for syslinux, the program used to boot the CentOS Distribution installation media. See Filesystem trunk Identity Themes Models Default Distro Syslinux, for more information.

Anaconda
     Contains design models for Anaconda, the program used to install CentOS Distribution.  See Filesystem trunk Identity Themes Models Default Distro Anaconda, for more information.

Firstboot
     Contains design models for the first boot program used to configure the maching onece installed.  See Filesystem trunk Identity Themes Models Default Distro Firstboot, for more information.

Rhgb
     Contains design models for CentOS Graphical Boot, the program used to show the boot process from Grub to Display Manager.  See Filesystem trunk Identity Themes Models Default Distro Rhgb, for more information.

Gdm
     Contains design models for GNOME Display Manager, the program used to log into the manchine once installed and configured. See Filesystem trunk Identity Themes Models Default Distro Gdm, for more information.

Kdm
     Contains design models for KDE Display Manager, the program used to log into the manchine once installed and configured. See Filesystem trunk Identity Themes Models Default Distro Kdm, for more information.

Grub
     Contains design models for GRUB (Grand Unified Boot Loader), the program used to boot the machine into an operating system. See Filesystem trunk Identity Themes Models Default Distro Kdm, for more information.

Gsplash
     Contains design models for GNOME splash, the program used to show the progress information while user's graphical session is loading. See Filesystem trunk Identity Themes Models Default Distro Gsplash, for more information.

Ksplash
     Contains design models for KDE splash, the program used to show the progress information while user's graphical session is loading. See Filesystem trunk Identity Themes Models Default Distro Ksplash, 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., a CentOS 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.

How to visually remark the internal differences?

     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, the image is from The CentOS Project and second, the major release of CentOS Distribution the image belongs to.

     See Filesystem trunk Identity Models Tpl Brands, for more information on how to develop and improve The CentOS Project Brand.

How to remark the visual resemblance?

     Use a common artistic motif as background for all CentOS Distribution images.

     See Filesystem trunk Identity Themes Motifs, for more information.

So, combining answers above, we could conclude that:

     In order to implement the CentOS Monolithic Visual Structure (see Filesystem trunk Identity) on CentOS Distribution visual manifestations, a CentOS Release Trademark and a common background (based on one unique artistic motif) should be used.

     Important Remarking the CentOS release schema inside each major release of CentOS Distribution ---or similar visual manifestation--- takes high attention inside The CentOS Project corporate visual identity. It should be very clear for everyone which major release of CentOS Distribution they are using.

Other recommendation that have being discussed is that of producing one unique visual style for each major release of CentOS Distribution.  That is, if we have 4 different major releases of CentOS Distribution, we need to provide 4 different visual styles to cover each CentOS Distribution art work needs.  Even such schema could be produced inside CentOS Artwork Repository, using one unique theme for each major release of CentOS Distribution would introduce visual isolation to CentOS Distribution, as visual manifestation of The CentOS Project.

As previously said, The CentOS Project maintains near to 4 different major releases of CentOS Distribution in parallel, and that fact creates a complete different perspective since the structural point of view. Consider the following: If we use one unique visual style for each major release of CentOS Distribution, which one of those visual styles does we use to cover other CentOS visual manifestations, like web sites and promotion stuff?

Some persons may end up asking themselves, why the CentOS Distribution I am using has this visual style tnd he CentOS web sites a different one?  Isn't them all part of the same project?  Furtunely, the presence of the CentOS Brand could exonerate those persons form complete visual isolation.