Templates are stored in iWebPress in a virtual file system that emulates a file-system. Within the root, the templates themselves are stored in webroot, printroot, or mailroot as appropriate. Web templates are divided further into themes and issues folders and within themes into individual 'theme' folders.

• webroot/
  • themes/
    • themeName/
      • archiveTemplate
      • assignmentsTemplate
      • imagesTemplate
      • printTemplate
      • rssTemplate
      • searchTemplate
      • sectionsTemplate
      • usersTemplate
  • issues/
    • issue/
      • sections/
        • sectionName/
          • assignmentsTemplate
          • sectionsTemplate
      • assignments/
        • aid
        • ...

Customization of the web output can be as simple as making one theme, which will render everything or as fine-tuned as customizing the template for every single assignment, a specific section in a specific issue, a specific issue, or a section in general.

Just as the template engine 'knows' what template to grab depending on page requested, it also 'knows' to search from the most specific to the least specific template when it is rendering. We spoke before of themes, but web-templates can also be thought of as individual templates, which is applicable when we discuss overriding them. If we want to customize the appearance of a single article, we place that customized template in issues/issues/assignments/assignmentID. Likewise, to customize all the articles in a section or the section itself, we would place a template in issues/issue/sections/sectionName/assignmentsTemplate or issues/issue/sections/sectionName/assignmentsTemplate. This is automated in the Web Publishing Panel and is covered in much greater depth in the Web Publishing