| [reply] |
Personally, I would just have a set / static header.txt & footer.txt file(s) and have the user modify the content. Thus, if I wanted to change the navigation/banners/layout, as long as I had the new templates written to properly display the included content files, things would propagate seamlessly.
Server Side Includes would be a must for this application. Each user would have their index.html file, and all it would consist of would be SSI calls to include:
header.txt
content.txt
footer.txt
Its really not that complicated. But takes some getting used to. This way meta tags cant really be used, and I would take into consideration the notes from the node above as well..
I hope this sheds some light on the subject,
_14k4 - webmaster@860.org (www.poorheart.com)
| [reply] [d/l] |
The main issue I have with that is that the user that will be maintaining this site doesn't have a clue about web design nor the desire to learn HTML. I have to make it so they can change individual elements and blocks of text without messing up the layout.
| [reply] |
I should have been a little more clear about what I meant by user-maintainable web sites. What I meant was that the person I designed the site for would be able to maintain the content of the site. They would not be able to add new pages, name the files, etc. I would design the entire thing and they basically could change any text or graphics that were necessary to update.
| [reply] |