Site Architecture

1. Our site uses a traditional tree-structure hierarchy with the home page at the root. However, the hierarchy is intentionally not strict:

   Example 1: We frequently link between branches as needed.

   Example 2: We could not find labels for some of our top-level categories that were ideal across all our audiences, so instead of fixing those labels in our directory structure, the labels we chose to use are simply ignored in the directory structure, and nodes that would be 2 clicks in from the home page in a strict hierarchy are instead only 1 click in. Study Academic Programs and Admissions and Partnerships for details.

2. We use redundant organization schemes to provide different methods of entry to the same content.

   Example 1: Home page topics can be accessed by topic or by audience.

   Example 2: Ideally, when presenting information in a browseable index we also present a method for searching using a search box. Conversely, when presenting information via a search box, we would ideally also present a method for browsing. Example: See Faculty.

3. We use symbolic links to create a template framework which separates page content from its visual and technical structures.
4. We use symbolic links and include files to reuse information while maintaining the robustness of the site structure.
5. We use conditional scripting to reuse information in ways that minimize duplicate data stored on the server.
6. We use cascading style sheets to separate large portions of presentation from structure.
7. We use meta tags to provide useful metadata to user agents.

8. Our site is presented as part of a larger hierarchy within http://www.ucsf.edu in 3 ways:

   1. Our domain name clearly indicates we are a subdomain of ucsf.edu.
   2. Our banner navigation and breadcrumb navigation clearly indicate our relation to UCSF.
   3. We explicitly state our relationship in the lower left corner of our home page.

Go To: Information Architecture or Style Guide