I'm curious, if you're going to be using that system, why not just use the database?
I once built a site (although it was in ASP at the time) that's content was run completely from XML, and it worked exceptionally well. Each section of the site (each page) was in a separate xml file - ie. news.xml, links.xml, and so on...and they looked something like...
Code: Select all
<news>
<newsItem>
<newsTitle>Blah</newsTitle>
<newsBody>.........</newsBody>
</newsItem>
<newsItem>
<newsTitle>More Blah</newsTitle>
<newsBody>.........</newsBody>
</newsItem>
</news>
And that worked very easily with M$'s DOM, but I haven't messed that much with PHP's XML stuff, so...
Another idea would be to drop the database (and even php) completely and just use XSL. With that, it can be hosted on pretty much any server, with all the processing left to the client, but the client's have to be new. Or, take the middle road, and use XML/XSL, but have the server process the XSL and send plain HTML/XHTML to the client. With the middle road, you can keep older clients, but have a nice site backbone prepared if you ever want to go full-on XML.