On 19/02/2020 19:06, Andy Seaborne wrote:
I am finding some conversion issues around boxes and <code>
https://jena.apache.org/tutorials/rdf_api.html#ch-Statements
vs
http://jena.roylenferink.nl/tutorials/rdf_api.html#ch-Statements
The example is doubly boxed and the fint size keeps jumping.
Yes, the Jena site markup is a bit yuk - it is a conversion itself - but
we have the content we have.
I've cleared up some problems - on staging now.
There are changes around whitespace and tables. sometimes better,
sometimes not. And I have seen an odd "Title" change where ":" becomes "-"
Andy
On 15/02/2020 13:28, Roy Lenferink 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
