All, The ASF infra has advised recently that they're deprecating and removing Roller support, our project blog is based on Roller.
Given this hasn't received any objections on this thread, I've spent some time in the last two months exploring options that solve most of our website and blog requirements. I explored several other top-level ASF project websites and found they had built their website/blog/article using something like Pelican, Hugo, Jekyll and recently Docusaurus. Among these Jekyll is the oldest and most stable platform that Github supports out of the box. Most of these TLP websites use a CI/CD based staging->publishing pipeline, using Github Actions, Gitpod, Netlify etc. Among these various options, Docusaurus seems to satisfy many of the requirements and integrates with Netlify CMS (to support our marketing contributors who aren't necessarily git-experts; https://www.netlifycms.org/docs/docusaurus/). If there aren't any objections I would like to set up a staging/beta website (as per https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories this can be configured, using default it would be on cloudstack.staged.apach.org). Example TLP website source repos: Docusaurus: https://github.com/apache/apisix-website https://github.com/apache/shenyu-website https://github.com/apache/incubator-kvrocks-website Jekyll: https://github.com/apache/openwhisk-website https://github.com/apache/nuttx-website Hugo: https://github.com/apache/kyuubi-website https://github.com/apache/hop-website https://github.com/apache/dubbo-website Regards. ________________________________ From: Rohit Yadav <rohit.ya...@shapeblue.com> Sent: Monday, December 19, 2022 14:57 To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: [DISCUSS] CloudStack Website build and modernisation All, For 4.17.2.0 release publication on the website, I had to manually edit the website [0] build as I couldn't get middleman to work on either Ubuntu 20.04, 22.04 (after spending a good hour to fix the ruby/gems build system). Any pointers on getting middleman/gems to work? As our website is dated, and in the past ASF infra has advised against setting up a dynamic CMS such as Wordpres for us I'm looking into alternatives that are ASF infra approved [1] and looking into Pelican and Jekyll. I'm also exploring what other ASF TLP websites are using for inspiration. I also found several apache projects such as apisix [2]<https://github.com/apache/apisix-website> having complex website build systems that use Netlify or other means of publishing websites. My high-level proposal is that we; (a) explore/investigate and migrate to a build system that is compliant with ASF infra policies and easy for anybody (esp PMCs and release managers) to setup/iterate locally, (b) integrate PR builds using Github actions or community CI/QA server (https://qa.cloudstack.cloud/) and, (c) we update the project website to use a modern library (something like Ant Design which we use with the ACS UI, or bootstrap, bulma, etc). Any suggestions, comments, or advice on this? [0] https://github.com/apache/cloudstack-www [1] https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Staticwebsitecontentgeneration [2] https://github.com/apache/apisix-website Regards.
