Hello, I made the Jekyll branch work with the staging environment: https://logging.staged.apache.org/
When you change something in the sources, it will be automatically deployed to Staging. We also have a "news section", aka blog: https://logging.staged.apache.org/blog/ To add or change a project, you made want to edit: https://github.com/apache/logging-site/blob/jekyll/_data/projects.yml You can edit it directly in Github UI if you prefer to try it out. It will take a few seconds to build and deploy. I want to move the Team members to a data file as well. If no objections, I'd like to move this to asf-site Kind regards, Christian On Tue, Oct 10, 2023, at 23:10, Christian Grobmeier wrote: > Hello, > > Based on recent comments, I made a branch for using Jekyll on the > leading site. It's a branch, we can discard it. The migration took me > 1.5h, excluding this e-mail - not much wasted. > > https://github.com/apache/logging-site/tree/jekyll > > This is not yet auto-deployed, but if nobody opposes it, I will move > on, merge, and autodeploy. > > Here is some info: > > Jekyll supports data files like this: > https://github.com/apache/logging-site/blob/jekyll/_data/projects.yml > > In the future, one could modify those data files directly from GitHub > UI to update a status or a team member. It would be autodeployed then. > The code for the output is also simple: > > https://github.com/apache/logging-site/blob/jekyll/index.html > > The amount of HTML has decreased. In addition, I was able to use > Flexbox, which is built-in to browsers (no more slow Bootstrap in this > case) > > We also can make use of SCSS now, which can use advanced CSS (in this > case only nesting): > https://github.com/apache/logging-site/blob/jekyll/css/site.scss#L44 > > The current team list could be moved to a data file, too, but I left it > as adoc to showcase that this Jekyll page can work with adoc as well: > https://github.com/apache/logging-site/blob/jekyll/team-list.adoc > > If you want to work with Jekyll, you can run the scripts: > > ./run-docker-build.sh (only one time; Docker needs to be installed) > ./run-jekyll.sh (when you want to work) > > This way, you can build locally and check. However, you don't need to > do this to update tiny things quickly. > > Please let me know if you want to object; otherwise, I would love to > move this forward. > > If we, at some later point in time, move on to something like Antora, I > will gladly help to migrate; however, since we are using adoc for this > website as well, it should be straightforward. > > As soon as I have a go for this, I will prepare a blog section > announcing the latest releases and preparing everything for some > announcements we had in mind on the PMC list. > > Kind regards, > Christian
