Extending Repository Organization Occasionly, you may find that new components of &TCPCVI; 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 starting to create directories blindly all over, is: What is the right place to store it? When the repository structure is extended, it is very useful to bear in mind &TCPCVIS;, &TCM; and &TCDRS;. The rest is a matter of choosing appropriate names. It is also worth to know that each directory in the repository responds to one or more concepts that justify its existence. To build a directory structure inside the repository, you need to define the concept behind it first and later create the directory, remembering that there are locations inside the repository that define concepts you probably would prefer to reuse. For example, the trunk/Identity/Images/Themes directory stores artistic motifs of different themes, the trunk/Identity/Models/Themes directory stores design models for themes, the trunk/Manuals directory stores documentation, the trunk/L10n stores translation messages, and the trunk/Scripts stores automation scripts. Using this information and the one provided in , it is possible for you to find out good places for extending &TCAR;.