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 <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. > > > > On 2/18/20 2:07 PM, 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 and I > >> thought how this could be improved. Also, an 'Edit this page' button > >> will already help people to > >> contribute changes to the current website. > >> > >> One way of doing this could be to start using a static website as > >> Hugo. Hugo is a single static binary > >> being able to generate static websites. More or less similar to what > >> the Apache CMS is doing, except > >> it is being used in a quite diverse set of communities (Kubernetes > >> being one of them). Content written > >> for the site will remain in markdown. > >> > >> This afternoon I had half an hour to spare and tried to convert > >> community.a.o from the current CMS > >> style to the style useful for Hugo. This worked out pretty well and > >> not that much changes were > >> needed. > >> > >> I have just created a pull request to the comdev-site repo on GitHub > >> so people are able to review > >> the work I did [1]. > >> > >> What I propose when people are okay with this move: > >> - Request a comdev-site gitbox repository synced with the comdev-site > >> repo on GitHub. > >> - Change 'trunk' to 'master' as that matches a bit more with the git > >> style of working > >> - Merge the PR I created [1] > >> - Create a Jenkins job to have the site automatically generated > >> whenever new commits happen. > >> - Move over serving community.a.o from svn to git. > >> > >> I'd like to hear your opinions on this ;) > >> > >> Best, > >> Roy > >> > >> [1] https://github.com/apache/comdev-site/pull/5 > >> > >> --------------------------------------------------------------------- > >> 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 > >
