On 19/02/2020 06.52, Roy Lenferink wrote:
Hi Daniel / Rich,
To be honest, I completely forgot the .asf.yaml was able to do such things, my
bad.
Currently the .asf.yaml supports both Jekyll and Pelican. My previous
experience with Jekyll is that
it is really slow at incrementally generating content when file changes are
made (running on the
Ubuntu bash shell on Windows). Also it requires ruby, rubygems, etc. to be
installed.
After your message I tried Pelican as well [1], I have to say, it is fairly
easy to install (note: I already
had pip installed). However, one big disadvantage would be that Pelican its
output is a bit of a mess.
Pelican is storing all its generated content in a single folder (e.g.
/output/pages), which kinda
breaks every link from an external website to community.a.o, e.g. the
http://community.apache.org/newcommitter.html link will be broken as well. IMO
we need to try to
minimize impact when moving over. Of course we can work with RewriteRules and
adding a 'Slug' to
pages but that just adds extra maintenance.
With Hugo I was able to keep all current URLs working. Generating the comdev
site is done in ~226
ms. Hugo contains incremental builds as well (useful for development), which it
serves from memory
instead of writing the generated files to disk (compared to Pelican).
Installing Hugo is just as easy
as downloading the specified release, extracting the tarball and you're good to
go ;)
Fair enough :) Sounds like we'd want Infra adding Hugo as a supported
platform then? We could have things be auto-built and -deployed then.
GitHub statistics:
Jekyll: 39.7k stars / 8.7k forks / 893 contributors [2]
Hugo: 41.7k stars / 4.7k forks / 606 contributors [3]
Pelican: 9.4k stars / 1.6k forks / 347 contributors [4]
@ Daniel, maybe I can help Infra to possibly support Hugo builds as well ? :)
[1] https://github.com/rlenferink/comdev-site/tree/feature/conversion-to-pelican
[2] https://github.com/jekyll/jekyll
[3] https://github.com/gohugoio/hugo/
[4] https://github.com/getpelican/pelican
On 2020/02/18 19:47:30, Daniel Gruno <humbed...@apache.org> wrote:
There are pelican auto-builds and auto-publishing via .asf.yaml files
already, as well as custom build steps being introduced on builbot 2.
see https://s.apache.org/asfyaml for starters...
On 18/02/2020 13.45, Rich Bowen wrote:
I would like to hear more about Hugo, since it's not one that I've heard
of before.
There are a zillion different content frameworks out there, and I have
no preference for any of them except that the underlying file format is
standard-ish. Markdown, or something similar that can be easily
converted to the next framework-du-jour when Hugo is no longer the
latest hotness.
I would also strenuously encourage you to include Infra in any such
discussion, before we forge our own new path, while Infra is already
looking at a CMS replacement.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
