Are you working in Dreamweaver? The template in DW will be similar to, but not the same as the one I describe. DW's template works by allowing editable content within the template, mine does not. My template is rarely or never edited. It just lives on the server and is used as a boilerplate to insert data related to the requested URI. All of the insertion points have PHP function calls.
This is why I suggest getting a few static pages in place (a couple for each type of page) then course through them and identify the unique bits of data (including heading and navigation). These are the bits that will go into your data table (or includes modules).
I looked at the source code of the site you sent me, and have to say, it was a lot of work to put that together. But there are issues that will come back and bite you squarely on the tookus: namely, uppercase first letters and underscore separators. One of the things I learned very early on was to stick to lowercase. SE's have told us not to use underscores as word separators. Use dashes instead, else the term is seen as one long word that makes no sense.
It's a bit late to change that now, but for your next site, drop the practice altogether. Go with lowercase on everything relating to URL's, fragment id's and class names. In the OOP world, uppercase first letter is used to denote an object class, if I'm not mistaken. Let them (the OOP programmers) have their convention, and not try to create one of your own around uppercase.
In your next project would become:
I also noted there is no quoted source for the information on the site (and there are several errors and inconsistencies in just the pages I looked at, but that is not the discussion here).
One thing is certain about templates... if they are not valid, none of your pages will be, either. Once you create a static page, check it in the W3C validator and correct any detected errors. I would recommend going with the HTML5 doctype to help clear out some of the old HTML (XHTML) clutter and simplify the markup. HTML5 is Strict, but allows either HTML 4 or XHTML markup. This means <br> and <br /> are both valid, as are all the other self-closing elements like <img>, <input>, <hr>, and so on. HTML5 permits dropping of TYPE attributes on <script>, <link rel="stylesheet"> and <style>. It is also the markup language being used by FB, so their content will ring up less validation issues. (There will always be issues with FB, but that's no matter. Only they parse these parts of the page.) Just make your markup valid, before you create the template from it.