Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Bertrand Delacretaz
Hi, On Wed, Feb 19, 2020 at 1:52 PM Roy Lenferink wrote: > ...With Hugo I was able to keep all current URLs working... I think keeping existing URLs (or redirecting from them) is an important requirement that we missed earlier. The comdev site has been around for quite some time so we have lots

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Rich Bowen
To be completely clear, I'm NOT saying "don't use Hugo", I'm just wanting to be sure that we aren't going down a road that will make contribution across the Foundation even more of a patchwork. It sounds, from other responses, that Hugo already has wider adoption here, which is awesome. On 2/

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Daniel Gruno
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 co

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Roy Lenferink
Thanks Bertrand! At Celix we are using Hugo as well, which indeed works pretty well :) https://github.com/apache/celix-site On 2020/02/19 09:49:50, Bertrand Delacretaz wrote: > On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink wrote: > > ...An example (for demo purposes only) of Hugo its output is

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Roy Lenferink
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 o

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Bertrand Delacretaz
On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink wrote: > ...An example (for demo purposes only) of Hugo its output is available here: > http://comdev-site.roylenferink.nl/ Nice, thank you very much for working on this, I think it's long overdue! Us being geeks, it'll be hard to agree on tools, IMH

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread 适兕
hugo is great ,fast ,and simple . content just focus markdown. Tomasz Urbaszek 于2020年2月19日周三 下午5:23写道: > We are using Hugo for https://airflow.apache.org and it works pretty well > :) > > T. > > On Tue, Feb 18, 2020 at 8:47 PM Daniel Gruno wrote: > > > There are pelican auto-builds and auto-pub

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-19 Thread Tomasz Urbaszek
We are using Hugo for https://airflow.apache.org and it works pretty well :) T. On Tue, Feb 18, 2020 at 8:47 PM Daniel Gruno 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.a

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-18 Thread Daniel Gruno
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

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-18 Thread Rich Bowen
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 co

Re: Move community.a.o site from CMS/SVN to Hugo/Git

2020-02-18 Thread Roy Lenferink
Forgot to mention: An example (for demo purposes only) of Hugo its output is available here: http://comdev-site.roylenferink.nl/ On 2020/02/18 19:07:09, Roy Lenferink wrote: > Hi fellow comdev-ers, > > The e-mail from a few days ago asking to change the year from 2018 -> 2020 > triggered me a