  <h1 align="center">Creating New Sub-categories</h1>
  <ul class="toc">
    <li><a href="#size">Size of the category you're considering subdividing</a></li>
    <li><a href="#templates">Categories specified by templates </a></li>
    <li><a href="#overlaps">Prevent overlaps</a></li>
    <li><a href="#placement">Placement of the category</a></li>
    <li><a href="#naming">Naming Categories</a> 
      <ul>
        <li><a href="#template-exist">Does a template exist?</a></li>
        <li><a href="#preferred">Preferred Terms</a></li>
        <li><a href="#redundancy">Path name redundancy</a></li>
      </ul>
    </li>
  </ul>
  <p>As a general rule, you should discuss proposed sub-categories with your fellow 
    editors in the <a href="/ddp/02003/">fora</a>, before 
    you create them. Some factors to be considered are given below:</p>
  <h3><b><a name="size"></a></b>Size of the category you're considering subdividing</h3>
  <p> Adding a subcategory introduces an extra level for the browser to navigate. 
    If the current category is manageable as it stands, a subcategory is probably 
    unnecessary. When there are over twenty links in a category, a sub-category 
    should be considered, however there are no firm rules as to when to subcategorise. 
  </p>
  <h3><b><a name="templates"></a></b>Categories specified by templates </h3>
  <p>If a template exists for the area in which you are working, you may find 
    that the decision as to whether a category should be created has already been 
    made for you. It may be stated that when a given number or type of site(s) 
    exist a category should be created. This practice is usually followed to allow 
    for the category to be @linked to from further up the tree. For instance, 
    the <a href="http://dmoz.org:8080/Arts/Music/Bands_and_Artists/">Bands_and_Artists</a> 
    guidelines require you to create a category for a tribute band's site even 
    if you can only locate one such site. This is so the category can be @linked 
    to from <a href="http://dmoz.org:8080/Arts/Music/Bands_and_Artists/Tribute_Bands/">Arts/Music/Bands_and_Artists/Tribute_Bands/</a> 
    .</p>
  <h3><b><a name="overlaps"></a></b>Prevent overlaps</h3>
  <p>Before you create a category you should ensure that it doesn't already exist 
    elsewhere in the directory. Use the search function, browse related categories, 
    and if necessary, ask in the fora. If you find that the category does already 
    exist, then consider linking to it with an @link.</p>
  <h3><b><a name="placement"></a></b>Placement of the category</h3>
  <p>Certain types of sites belong in trees specific to the site's purpose. For 
    instance, sites whose primary purpose is to sell goods belong in<a href="http://dmoz.org:8080/Shopping/"> 
    /Shopping</a>. This means that if you're contemplating creating a category 
    for shopping sites, you know straight away that it does not belong outside 
    the /Shopping hierarchy. </p>
  <h3><b><a name="naming"></a></b>Naming Categories </h3>
  <p>When deciding what you are going to name categories that you create, there 
    are a number of factors that you should consider. </p>
  <blockquote> 
    <h4> <b><a name="template-exist"></a></b>Does a template exist?</h4>
  </blockquote>
  <p> In some category trees there is a predefined method that dictates the placement 
    and names of categories created under them. For example, the entire /Regional 
    hierarchy is governed by such as a template, as are many categories in /Arts, 
    such as Bands_and_Artists and Celebrities. </p>
  <p>If a category-specific template exists it should be adhered to. If you wish 
    to deviate from said template, you should start a discussion in the appropriate 
    top-level forum. </p>
  <blockquote> 
    <h4><b><a name="Preferred"></a></b>Preferred Terms</h4>
  </blockquote>
  <p>The entire directory is covered by the <a href="http://dmoz.org:8080/preferredterms.html">Preferred 
    Terms list</a>, which suggests names for standard categories. For example, 
    it is preferred that categories which are created to house on-line message 
    boards, mailing lists, chat rooms, etc. are named 'Chats and Forums'. This 
    is a uniform term that can be applied in the majority of situations. </p>
  <p>The Preferred Terms list is designed to aid you when creating categories, 
    and where a preferred term exists, it is suggested that you use it.</p>
  <blockquote> 
    <h4><b><a name="redundancy"></a></b>Path name redundancy</h4>
  </blockquote>
  <p>When you name a category, you must consider it in context, i.e. the name 
    of its parent, and grand-parent category. This means that you should try not 
    to repeat the name of the parent category in its subcategories. The main reason 
    is usability; categories with long, rambling names are difficult to navigate, 
    difficult to subdiide further, and inefficient. For example, consider the 
    following scenario:</p>
  <p>/Widgets/<br>
    exists and it requires subdividing. You need a category for specific types 
    of widgets, so you create:<br>
    /Widgets/Blue_Widgets/<br>
    however, 'widgets' is redundant, as it can be inferred by the category's placement 
    that 'widgets' is the subject in question. Thus, to eliminate redundancy, 
    this may be renamed: <br>
    /Widgets/Blue/ </p>
  <p>Equally, the category:<br>
    Widgets/People_that_have_Invented_Widgets/ <br>
    Could be shortened considerably to:<br>
    Widgets/Inventors </p>
  <p>However, repetition is only redundant if it is unnecessary. In some cases, 
    repeating the name of the parent will clarify a category's purpose, and improve 
    readability. An example of this is the following category:<br>
    <a href="http://dmoz.org:8080/Society/Crime/Murder/Serial_Murder/Serial_Killers">Society/Crime/Murder/Serial_Murder/Serial_Killers<br>
    </a>If pathname redundancy is taken to the extreme, this category would be 
    named: <br>
    Society/Crime/Murder/Serial/Killers <br>
    It was decided however, that the former name was clearer and would make more 
    sense to the user, thus it was favoured.</p>
