31212
« Last post by mouser on June 13, 2006, 02:19 AM »
this is very close to the concept, and you've grasped the main idea.
to be more specific, the idea is to have:
1) a Content Directory Tree, which is someplace not in public_html
2) a set of Template and Site Building instructions, again not in public_html
3) a tool for BUILDING (regenerating) the html site from the content+templates
so it wouldnt be a dynamically generated "wrapper" but rather a way of building static html (or php) pages on demand when they need updating, from a set of content pages and templates.
so for example if you changed the header/banner, you could say "rebuild the entire website now" and it would rebuild all the static pages with the new header, footer, etc.
in more advanced cases, you could say, this page should contain the text of these posts; so when one of these posts change, this page needs to be rebuilt. so there has to be a kind of table telling it what needs rebuilding and when.
the tool also needs to provide some nice functions for things like a navigation bar/menu (which means it has to scan the directories and discover the tree structure of the site from the content directory, and then make this into a nice menu system). but yes the key idea is that the content directory tree IS the site layout.
the advantages are:
the final result is superfast static pages.
the content pages are all outside the public_html directory and can be made safe (ie you can dissallow php,etc), which means its easy to give random people ftp access to "their section" of content.
it lets you write page content easily by hand in flat files
it still allows for the possibility of a more sophisticated wsywig/gui/usermanagement cms front end to be layered on top, creating content pages in the content directory (as you mention above), thought this is not my immediate concern.