The idea behind this is pretty straightforward. For each page, you create a directory. You call it something related to what’s on the page. You can either use a flat directory structure, where every page is on the same level, or a hierarchical directory structure, where a page that serves as a pointer to four other pages is actually closer to the root than those four pages, which are under it. Figure shows a directory structure that matches the pages in the site.

Having one directory per page doesn’t make sense, but it may make sense to have one directory per functional unit involved in creating your site. You could modify the previous diagram by removing the directories for features (a subset of sales), FAQs (a subset of support), and purchase (a subset of sales), and lumping those three in with the pages they modify. If you have a handful of people working on each unit, you can protect your site better by restricting the permissions of the people in each group only to the folder where all their files go. Figure 1.1 shows an even more convoluted directory tree with one page per directory using hierarchical structure.

Fig:

It’s hard to imagine where this model makes sense because it just doesn’t scale. If you rearrange your site, you may as well start over.