Hi Harald, Thanks for the contribution !
The documentation changes, once committed, would be immediately reflected in the staging site http://openejb.staging.apache.org/<http://openejb.staging.apache.org/documentation.html> And when happy, a 'publish site' can be done to push the changes to live site. Just did a publish, and the changes are reflected now in live. As for the move to Markdown based CMS, looks like using Confluence has had it's set of problems ( http://www.apache.org/dev/cms.html#confluence-limitations) and the markdown approach was being recommended ( http://www.apache.org/dev/cms.html#markdown) -Vishwa On Tue, Dec 4, 2012 at 6:54 PM, Harald Wellmann <[email protected]>wrote: > Could somebody please explain the documentation update process or > provide a link to an existing process description? > > I made some changes and additions via the anonymous CMS interface, > they have been committed to Subversion, but they do not yet appear on > the live site (http://openejb.apache.org/documentation.html). Is this > expected? > > BTW, what's the rationale for using this homegrown CMS? Doesn't ASF > have a free license of Confluence (which is a lot easier to use, > IMHO)...? > > Best regards, > Harald >
