I think this can be the first step in making the entire site deployment process more automated and keeps us moving forward with supported technologies.
However, I note that the Hugo documentation states: "Hugo ships with an internal Disqus template". I am concerned that the Discus connection may not meet with the Apache Foundation's approach to privacy and data sharing. I know there are problems with surveys and polls hosted by 3rd parties. So: +1 for moving to site to git. -1 for using Hugo unless it can be deployed without 3rd party data sharing or unless there is approval from Apache legal. Claude On Sat, Feb 15, 2020 at 1:28 PM Roy Lenferink <[email protected]> wrote: > Hi Jena community, > > I noticed Jena is still serving its site from SVN with help of the Apache > CMS. At the Apache Celix > project we decided to move away from the CMS and move towards git for > serving our website [1]. > This because the CMS was introduced in 2010 and is currently not accepting > any new projects. With > the move to Hugo we're sure that we still can update the site when the ASF > CMS will be > decommissioned. > > The master branch contains the actual website sources whereas the > generated website is served > from the asf-site branch. Hugo is being used as static website generator. > Content is written in > Markdown. > > I had a look at Jena its site and it was quite easy to migrate Jena its > site to use Hugo as well. An > example of Hugo its output is (for demo purposes only) available on [2]. > These are the existing > markdown files with a slightly changed header. > > Moving to git can enlarge the visibility of how projects are functioning. > Next to that, new contributors > can simply create a pull request against the website repository if they > find anything they want to > improve. I've updated the 'Improve this page' to 'Edit this page' which > will open the GitHub webpage > to edit the currently viewed page (currently returning a 404 because the > apache/jena-site repository > does not exist). > > If the community is interested in this move what I propose: > - Someone from the PMC to request a new git repository for the website > (e.g. jena-site) via [4] > - Me creating the pull request from the repository I am temporarily using > for the website contents [5] > to the official jena-site repository > - Create a Jenkins job to automatically build the site after changes > happen on the master branch. > - When the pull request is reviewed and merged ask INFRA to move over from > the current svnpubsub > to the gitpubsub approach and remove Jena from the Apache CMS. > > Next to that Jena is also providing javadocs on its site. My proposal for > this is to serve them from a > separate branch (e.g. release-docs). This way people who only want to > clone the site can clone the > the master branch using --single-branch and will not be bothered with > cloning all the javadocs. > > All the URLs are still the same so the SEO score is not influenced in any > way. > > I'd like to hear everyone's opinion on this :) > > Best regards, > Roy > > [1] https://github.com/apache/celix-site > [2] http://jena.roylenferink.nl/ > [3] http://celix.apache.org/contributing/releasing.html > [4] https://gitbox.apache.org/setup/newrepo.html > [5] https://github.com/rlenferink/jena-site > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
