Occasionly, you may find that new components of The CentOS Project corporate visual identity need to be added to the repository in order to work them out. If that is the case, the first question we need to ask ourselves, before start to create directories blindly all over, is: What is the right place to store it? The best place to find answers is in The CentOS Community (see page http://wiki.centos.org/Help), but going there with hands empty is not good idea. It may give the impression you don't really care about. Instead, consider the following suggestions to find your own comprehension in order to make your own propositions based on it. When extending respository structure it is very useful to bear in mind The CentOS Project corporate visual identity structure, The CentOS Mission and The CentOS Release Schema. The rest is a matter of choosing appropriate names. It is also worth to know that each directory in the repository responds to a conceptual idea that justifies its existence. To build a directory structure inside the repository, you need to define the conceptual idea first and later create the directory, remembering that there are locations inside the repository that define conceptual ideas you probably would prefer to reuse. For example, the trunk/Identity/Images/Themes directory stores theme artistic motifs, the trunk/Identity/Models/Themes directory stores theme design models, the trunk/Manuals directory stores documentation files, the trunk/Locales stores translation messages, and the trunk/Scripts stores automation scripts. To better illustrate this desition process, you can consider to examin the trunk/Identity/Images/Themes/TreeFlower/3 directory structure as example. This directory can be read as: the theme development line of version 3 of TreeFlower artistic motif. Additional, we can say that TreeFlower artistic motif is part of themes, as themes are part of The CentOS Project corporate visual identity. The relationship between conceptual ideas can be stablished by reading each repository documentation entry individually, from trunk directory to a deeper directory in the path. For reading repository documentation entries we use the help functionality of centos-art.sh script.