Hi everyone,
short update: https://issues.apache.org/jira/browse/INFRA-24152
We made some progress migrating the website to Hugo but work has stalled
because of higher priorities. The blog is now available through the
archive https://blogsarchive.apache.org/#ofbiz until we finished the
migration.
I'll keep you updated.
Best regards,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 01.03.23 um 13:44 schrieb Michael Brohl:
Hi everyone,
just a short update: we will start working on the migration of the
website beginning mid March.
I hope that we can roll out the new website in April. I'll keep you
updated.
Best regards,
Michael
Am 11.02.23 um 12:32 schrieb Michael Brohl:
See also https://issues.apache.org/jira/browse/INFRA-24152 for the
infra migration Jira issue.
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 07.02.23 um 19:06 schrieb Michael Brohl:
Dear community,
In the course of getting Wiebke to be able to help with our blog, it
turned out that Apache Roller will be discontinued as the platform
for blogs by infra [1].
There is an offer and already a pull request [2] to export the
existing blog posts for a migration to Hugo [3].
Hugo is a static site generator which will generate individual pages
from every markdown blog posts file which is provided in the PR.
That means we need to (at least)
- setup a Hugo project
- build up templates for the blog posts which also include header
and footer for full page rendering
(hence, we have to take over some of the templates/html
code/javascrip/CSS to Hugo as well)
- generate the post pages and include them in the website under /blog.
These are quite some steps we have to take anyway and I ask myself
if we should not switch over to Hugo for the whole website as well.
That should be not too difficult because we already have some kind
of templates (in php) and there is already some sectioning with
header, content, footer etc.
The advantages would be
- to truly separate content from the templates (it is now mixed
php/content)
- blog posts can be generated from OFBiz commits and, together with
page content, be send in by pull requests
- content automation (no need to change the copyright year manually,
automated taxonimies for the blog etc.)
- easy process for a git supported writing process for pages and
blog posts and a fast and automatable publishing process (git hooks
or GitHub integration).
Coincidence: I am on a journey to migrate the ecomify websites to
Hugo we have at least some knowledge there (maybe others as well?).
To sum up, I propose to migrate our blog and also the Apache OFBiz
website to be an integrated, Hugo based website.
Opinions?
Best regards,
Michael Brohl
ecomify GmbH - www.ecomify.de
[1] https://issues.apache.org/jira/browse/INFRA-22461
[2] https://github.com/apache/ofbiz-site/pull/8/files
[3] https://gohugo.io/