MINOS Web Guide - Template Pages

List of Templates

Each main section of the Site has a Template Page. The content within these pages is identical and serves as an example of the correct XHTML for making content in the page: ordered and unordered lists, definition lists, headers, ordinary paragraphs, images, tables, etc. There are some "blank" templates, containing no content, in case you are familiar with XHTML syntax and don't want to have to delete all the sample content.

The Navigation features on each template are nearly identical, except in the navigation. The name of the site's Main Section which each Template belongs to is high-lighted in the top menu bar, producing a "you are here" effect; this is done by inserting a style directive in the page header. Each template also has a different Sidebar Menu, which is specific to that page's site Section. The code for the sidebar is imported via SSI, so the SSI statement is different for each Template. You can delete the include code and insert a custom sidebar menu in it's place - a code snipet for a generic menu is contained in the template directory.

So you should obtain the correct Template. Copy the page appropriate for the Site Section where the page will ultimately reside.

  • NumiTemplate.html for pages in the NuMI Beam Section
  • MinosTemplate.html for pages in the MINOS Experiment Section
  • ArchiveTemplate.html for pages in the Project Archive Section
  • GeneralTemplate.html for pages in other directories, which get referenced from many Sections, such as the Working Groups, Posted Talks, and Meetings

Copy, not Save

You probably noticed that the Template pages listed above are not links. To obtain a Template, COPY it, in AFS space. Do Not save template pages via your Browser (and to discourage that, the page names above are not links). And Do Not edit pages from within a Browser, and then save them to some other location on the site.

Why not save or edit through the Browser? Because we use Server Side Include (SSI) to insert common code snipets into each page. When you view, edit, or save a page through a browser, then the browser expands the SSI code, and erases the include statements. You get additional code in the page that you do not need to edit and don't need to view - thus defeating the entire purpose of using SSIs. Since the Include statements are erased by the browser, how do you know how to put it back right? Choosing View Source within the Browser also shows you expanded code (because the Browser already expanded it!). In short, as soon as a browser fetches the page from the Server, you are not seeing the page's source code as it exists on the Server.

The only way to see a copy of a page as it exists on the Server is to get it from the Server yourself - not have a browser get it for you. So log onto your fnalu account, cd to the web space, and edit the page directly, not through a browser window. If you want to edit locally, then copy the page in AFS space, or fetch it via ftp, or fetch the ZIP file, below, of all the templates. You then get the page source code as it exists on the Server - you can see the one-line SSI statements, and you leave them just as they are. No matter where you place your finished page within the Site, those SSI statements will function correctly.

The afs path to the Templates Directory, for afs copy or ftp, is -


A WebPageTemplates ZIP file has been made if you want a local copy of the page source code. You get all the templates.

Fermi National Accelerator Laboratory Magnet Logo