Though the page you linked to also has non-semantic markup, tables for nothing, etc, etc... from the <body> tag to the end of the second menu line it's what, 2.3k? With semantic markup there's no reason for that to be more than half that. H1, two UL, done. NONE of the DIV apart from #container should even be in there, NONE of the tables are doing anything that needs a table to be done, even the strong tag and extra DIV's shouldn't be there, much less the use of the deprecated CENTER tag (which has NO PLACE in modern markup).
Also that ASP form crap that doesn't do anything but waste bandwidth is a great argument for switching to PHP. :lol: -- also funny it's designed to exactly 1024 so it's NOT 1024 friendly.
To make each page unique you have to make the markup for each page unique - it's just a matter of minimizing how much content you have to change.
The way I prefer to handle that would just have a class on it thus:
Another approach some people use (I dislike it because of the amount of CSS involved) puts a class on every link and the parent wrapper (either your width wrapping div or body) and uses inheritance to set it up. This might be easier for you to code the server side logic for since all you need to do is swap the class on BODY.
On that one you just change the class on BODY to the current page, and the CSS will handle the rest.
In either case though you still have to swap out some markup server-side, but that's what server-side scripting is FOR. The trick is to minimize how much has to be changed server-side for each page.