Quack,


### A pinch of history

As a short introduction for those who do not know me as I rarely post
here: I'm part of Red Hat OSPO Comminfra Team (previously OSPO was
called OSAS) and currently hosting and taking care of the website.


This topic has been discussed many times: neither people writing the
site neither us for the maintenance are happy with the current state of
affair. But we had not real plan and picking a random tool which might
lead to similar problems and without any way to support it properly was
not very appealing. Moreover we tried migrating to Middleman 4, the
obvious path to modernization, but this happened to be more complicated
than expected and this new version had terrible performance problems. As
you now version 3 is already slow, and that's quite an understatement.
In the meanwhile a few things have changed, and people taking care of
the website too, so let's talk about the current situation.
(very short version of the history around this)


### Why now?

What has changed:

* several projects moved to Jekyll, a software we were already
investigating at the time and is being used by Google Pages (they
created it in fact), and they were very happy with the result; we
believe it has the necessary features, it is well maintained because
Google uses it heavily, and it's very fast

* we've tried Jekyll ourselves, we're happy too, and we do have the
Ansible playbooks and tooling to deploy it now

* over time the website had some waves of cleanup (still needs quite
some love though) and recently the blog moved to WordPress to get
comment support and a more friendly interface (see OVIRT-2652) which
allowed more cleanup (see #2030)

With the blog separated and a lot of custom Ruby code removed, the
tooling ready, I believe we can now work on migrating the content.

We may realize Jekyll is not the right tool, but people seemed to like
the idea at the time and current experience seem to indicate it should
improve things and be maintainable. The goal here is to experiment and
switch to production only if we're happy with it.


### Early work

I have started a branch called 'jekyll_migration' to put my work on it.
This is very early work (I just started), I already hit various
difficulties, and I can't commit 100% of my time on it so it will
require some time.

Several of my changes happened to not be really specific to the
migration, and the current site would benefit from these
fixes/cleanups/simplifications… thus I'll extracts these changes and
create separate PRs for master.

If you wish to help, then you can contact me directly or reply to this
thread. You may also create PRs to this topic branch, but please do not
push anything directly.


Regards.
\_o<

_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ERLDSOGZQGLPNIDDYRG6G4FTKENS427C/