Hi, > The initial step is to cull the site down to the core static pages. PHP > is not required there. > > > Conversely, if we want eventual dynamic content delivered via PHP > > Let us decide that when the time comes. The opinion of the people who do > the work will carry the most weight. > As I see it from just viewing the page, there is no dynamic content on it (besides maybe the removed poll). That would mean its not necessary to code it in ugly PHP and regenerate it for each page view. I think, the logical thing is to do it the same way as its done for code: Write sourcecode in an easy language, compile it to static html and upload it once when you add content, then only serve the static pages.
Take a look at http://commonmark.org/ . This might enable writing some parts, like the news items, in nearly the same syntax as you do when editing the wiki at SF, without thinking about the details of html. I guess, the menu parts of the website might not need many changes over time and could stay as is. Greetings, wintertime ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
