This part of the site would be where the "regular" content would go, being the only stuff on the page (when it's actually implemented) which would be static. When I finish the "real" site coding (as this is mostly a mockup to test the page layout), everything except the actual page's content will be generated entirely with PHP, from the title tag right on down to the menu.
This will make it extraordinarily easy for me to implement sitewide changes later, which means it'll be easier to adapt to any new RPGs for the lineup. Instead of having to go through ALL of the pages and change each and every piece of work, I'll instead be able to implement changes based entirely on two files, which is very, very needed, as my operation will be an entirely one-man thing.
Of course, there will be a special navigation menu for the subsections of the site, which will fall under the Sub-Nav Menu, to my left. If you're in a certain subsection of the site (D&D3E, for example), you'd be presented with links to other areas of the D&D3E section, to make navigation easier. I imagine it'd be a pain to have to go through an extra page every time you wanted to switch from one category of a subsection to another, so I tossed that in.
In addition, you'll notice the ad spaceholder. I'm not intending to advertise, if I can help it. If I have to to keep the bills on the site paid, I will, as quite frankly, I'm not willing to shell out more than fifty bucks a month on the site. Devoting time I have no problem with. But devoting all of what little hard-earned cash I have left after food, clothing, and shelter is another. It's small, it's unobtrusive, and it's above the fold, meaning advertisers will love me.
Finally, another thing: Site compatability. This site will be entirely compliant with pretty much ANY browser you can think of. Sure, it might not LOOK pretty, but anything which can view basic HTML will be able to view my page. Hell, you'll notice (if you look at this page without CSS) I've even got a little indicator of WHY the page looks crappy with the older browsers.
For those that don't know this nifty little technique I've developed, what I essentially did was create a division with the DIV tag, then IDed it with "nocss". In my CSS file (text file version here), you'll see that any DIV tags IDed with "nocss" are put 500 pixels above the page's starting. Hence, people with CSS-compliant browsers don't see the little error text, while those wothout CSS-compliant browsers get the little warning served to them first thing on the page. Nifty little nag for convincing the person to update. ^_^
Now, for those of you WITH browsers which aren't pre-2000, this page's width is perfectly aligned at 800 pixels wide, which means all you semi-older browsers with high/true screen color capacities of only 800x600 can view the site without problems. Sorry folks with anything lower, I had to draw the line somewhere. I chose 800x600. My own computer and moniter are well over two years old, and it's display goes up to 1280x1024 in 16-bit color. I think it's fair to assume you can manage 800x600. :P