On 04/27/2011 10:08 AM, Robbie Gemmell wrote:
You currently have to edit all the web page files in two places, with the source files being the core content and the generation step adding all the headers, footer, menu information to produce the final page which is published to /site so that the webserver pulls down the changes and publishes them.
Ok, that explains it. Apologies again for failing to adhere to correct process! I have checked in a change that applies my change directly to the source to re-synchronise.
Since we don't actually have anything too complicated and we are just storing the pages as html source anyway rather than some base format that gets converted, ideally I would prefer to just be able to edit the live site files for *everything* and do away with the generation step entirely. To do that would probably require a bit of re engineering though to make things more maintainable though. I dont believe we have access to PHP on the main ASF webserver but it does have Server Side Includes enabled which could also be used to allow including the menus, header, footer etc from a central copy rather than requiring per-page maintenance. The downside with any improvements along this line though is that you then probably need to test your updates using an webserver rather than just viewing the files locally.
What about just using frame elements? Is that considered bad form these days?
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
