Migration to JBake

[tarilabs]

Context and Problem statement

jugmilano.it is a static website, currently generated with Jekyll and customized templates.
Sometimes, modifications/contributions are needed from folks not familiar with Ruby/Jekyll.
Faced challenges:

• quick corrections of the YAML remotely via smartphone was challenging while on holiday 🏖️ 🍹
• folks mentioned is sometimes difficult to install Ruby/chruby/jekyll just to test locally
• folks mentioned is sometimes tedius to spin a docker container just to test locally

This proposed changes migrates FROM Jekyll TO JBake.

• JBake is Java/JVM based analogous of Jekyll
• Build is automated using Maven (another familiar build tool for JVM devs)

Goals

• Migrate from Jekyll by avoiding as much as possible modification to content files.
  • achieved by customizing markdown engine processing .md files' front-matter (ref)
• Preserve as much git history as possible
  • except of few files, content was rearranged preserving attribution and git history
• Instrument website build via Maven
• CI/CD for publishing on GH Pages via GHA
• Quick utility for "previewing" and testing the website locally

Non-goals

• Additional CI/CD or infra changes (can be addressed in subsequent PR/changes)
• Modification to layout/styles/pages (can be addressed in subsequent PR/changes)

Testing these changes

Checkout this PR and follow 2 commands in README.md.

[lucamolteni]

OMG thanks