Forum Moderators: open
One of the requirements is to allow program staff to update the HTML for each of the principal pages. Parts of the overall "template" (items common to each page) however will be pulled from a database.
This is a good candidate for a content management system. Let them edit their content block and then include it in the dynamically generated page. Catch 22 - given the budget, integrating a content management system is simply out of the question.
They will be using Word (possibly FrontPage) to do the editing and they are not expected to get into the actual HTML.
If I simply include the HTML (that they upload) within a template type file, then we will probably have an invalid document. That is the <body> of the template area will then have an entire HTML document in it.
I hate frames. But it seems to be the only sane approach. But I HATE frames.
Does anyone have any alternatives? Hopefully I'm missing something simple (and cheap).
The way I see it, page content should really be going through a site "Editor" before being shown to the public. I don't see why staff can't simply submit files to him/her. Then you can use SSI to your heart's content.
Alternatively, you could provide a simple "remote update" script that strips out unsupported HTML tags, in a similar vein to that used by a BBS like this one.
Either way, SSI files seem to be the easiest solution. A CMS is definitely overkill.
If I utilize SSIs, then we run into the issue of a full html document embedded within another. I don't think that will dependably render in all browsers.
And this is a public site (only certain people will upload html content).
If I utilize SSIs, then we run into the issue of a full html document embedded within another. I don't think that will dependably render in all browsers.
Anyway, it sounds like you need the content editors/owners to forward content to one central webmaster (you?) who knows HTML, does the markup, and uploads the new content. In the government organisation I work for we have lots of webmasters like that, one for each branch, and it works well.
FrontPage 2003 has Dynamic Web Templates...
This sounds promising. I'll check into it. Do you happen to know if any earlier versions had this ability?
content editors/owners to forward content to one central webmaster (you?)
This really isn't an option. One of the purposes is to remove such bottlenecks. They should be able to edit and publish with no IT intervention.
Thanks for the help everyone!
Don't know if I'm allowed to post a link in a case like this or not, so I won't do it. But the Editwrx website is easy to guess! ;)
Have you looked into getting a free content manager? I don't have the slightest idea what's available, but I'd be very surprised if there's not a free one out there somewhere.
>> Dynamic Web Templates
Do you happen to know if any earlier versions had this ability?
