<!--#include virtual="/doran/header-1.inc"-->

	<title>Server Side Includes - Templates</title>

<!--#include virtual="/doran/header-2.inc"-->

        <a class="nav" href="./index.html">Server Side Includes</a>
        > Templates

<!--#include virtual="/doran/header-3.inc"-->

<h1>Server Side Includes</h1>

<h2>Templates</h2>

<div align="center"><b><a href="./">Introduction</a> | <a href="./examples.html">Examples</a> | Templates | <a href="./setup.html">Server Setup</a></b></div><br />

<table cellpadding="10" border="0">
  <tr>
    <td valign="top" align="left">

These different "views" of this page (or portions thereof) and the associated code help show how a template incorporating Server Side Includes can be used to isolate page content from the banner, common navigation, and overall web site "look and feel" code.
<ol>
  <li>First we look at the "end product" -- the page as it appears now in your browser.</li>
  <li>If we <a href="./view.htm">view source</a> for this page the code you see hides the fact that SSI is being used.</li>
  <li>But, if we could see the <a href="./code.htm">actual code</a> as it exists on the server, the SSI would be apparent.</li>
  <li>Having seen that, we can now take a second look at <a href="./view2.htm">view source</a>.</li>
  <li>This view shows <a href="./content.html">the page's unique content</a> minus the SSI headers and footer.</li>
  <li>And here is a <a href="./template.html">template</a> minus "content" and containing only the SSI headers and footer.</li>
</ol>
The payoff is that by moving everything except the unique content out of individual files (and into header and footer includes), you have gained the ability to quickly and easily make global changes to the common elements of every page on your web site.  Now that's power!    :-)
    </td>
  </tr>
</table>

<!--#include virtual="/doran/footer.inc"-->