php site hosting several hundred templates

[r4nd0mch4r]

I have to write an app that will:

a) enable users register and enter their info (or their company info)

b) generate a website (template's will be made in advance)
and allow users to enter their own data

It would be generated like this:
app creates a directory with name... /usersdir/ and copies the files there... (index.php, index.css, news.php, news.css....)
and that would be it.

The main idea is that I have predefined choices they can select for the menu in their template (choices like: About our company, News, Portfolio, Where are we, Who are we, Clients, ...)

The select the choices they would like and then enter the contents.

*** Everything would be based on MySQL DB... and every choice would have its own table... example:

table_clients (id_client, id_template, about_the_client)

or another example:

table_news (id_news, id_template, news_contents, date)

---

And when I would type in IE the adress -> http://myportal.com/usersdir/ the application would

1) check which modules are enabled and generated the menu
2) contact the mysql DB in get the neccessary contents...

Is this whole idea any good? Is it a good system or a bad one?
Could it be done better, easier, simpler?

[drew010]

i think its a good idea, the two things i am thinking about in the situation is this:
1. if you are using myportal.com/userdir/ and the folder is a real folder, instead of putting load on the database server, just actually create the pages when they fill out the form and have it write out the html pages so they are there.
or
2. use mod_rewrite on the /userdir/ folder and have mod_rewrite pass the folder to a script and determine if that user exists and if it does serve the page from a script like page.php?user=userdir. that way there are no real folders and less clutter, and the info is always served from the database.
in my opinion depending on how many people will visit the site on average, the second way is the best way to do it.