We have two websites using the Apache CMS which has been deprecated. I have migrated both of these sites away from the CMS.
(1) The project website - https://openoffice.apache.org <https://openoffice.apache.org/> The new repository is https://github.com/apache/openoffice-project <https://github.com/apache/openoffice-project> Staging is https://openoffice.staged.apache.org/ <https://openoffice.staged.apache.org/> This site uses Pelican and Markdown. It automatically builds and pushes to staging when changes are submitted. Buildbot is used along with Infra’s preferred .asf.yaml methods. The content is caught up to the 4.1.8 release. The README.md still needs work. There are 46 pages and many are out of date. Committers are enabled to make edits and the site will update in less than one minute. (2) The user site - https://www.openoffice.org <https://www.openoffice.org/> The new repository is https://github.com/apache/openoffice-org <https://github.com/apache/openoffice-org> Staging is https://openoffice-org.staged.apache.org <https://openoffice-org.staged.apache.org/> This site uses JBake, Groovy, HTML, and Markdown. The README.md explains how it is built using Jenkins. The content is not yet caught up to the 4.1.8 release. There are approximately 20,000 pages of which about 300 are Markdown. Why and Product markdown pages should be easier to translate since the special class attributes have been removed to a post processing step. Regards, Dave
