Posted by Jon on 09/27/27 11:38

All,

I'm working in a fairly robust content management system for our company's
websites, and have a question regarding the file and directory structure of
the site.

Currently, I'm populating all content from each page using data in a MySQL
DB, and php to call the DB and push out the info. Fairly standard right?
Well, my question lies in the best approach to take regarding the file
structure. Basically, as of now, I can make the entire website essentially
ONE page, as I'm simply filling in content based on the link the visitor
clicks on. I build the links on the fly using PHP and contentIDs from the
DB, so even though each page is "different", it's all the same file.

My question is really the disadvantages of this. Though it's very easy
because I can make code changes on one page, I'm looking for some major
algorithmic disadvantage here that I cannot seem to come up with as of now.
The only problem I've found is regarding what happens if the visitor hits
the page without a query string being passed. In the past, I've ran a check
on this as each page had a separate file (instead of just one index.php
page, it would be something like /members/index.php). Outside of this, I'm
not sure where the problem with his method lies. Can anyone shed some light
on a major disadvantage I may be missing here?

[Back to original message]