Hi, To maintain the content we could use Apache CMS ( http://www.apache.org/dev/cms.html) as we do for Apache DeltaSpike and OpenEJB projects. Content (mardown pages) can be edited from within the browser directly or using svn. Another possibility is to use like we do for Apache Camel, Karaf & ServiceMix Scalate (= templating engine - http://scalate.fusesource.org/) to generate site contain + manual. I can provide you more info if required. In both cases, we could easily move content from Wiki.
Regards, Charles On Thu, Nov 1, 2012 at 10:58 PM, Sheng Liang <sheng.li...@citrix.com> wrote: > >About the links on the side... I appreciate them. The wiki is in need > >of TLC, and until we get the ok for themes and content templates, the > >wiki is not the first place people will go for info. > > I agree the wiki is in need of TLC, but it still has the most accurate > information and the most up-to-date content because it is easy for > developers to contribute. So while we make wiki look better, we have to > continue to direct developers to wiki. Form should follow function. > > Sheng > > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
