Hi, Well in PLC4X I setup everything that we're using maven to build the website and auto-stage it. So, users only have to provide asciidoc content files and as soon as they push, the website is auto updated. Same I did for Edgent and the Apache Training project.
So, if you're interested in something similar? Chris -----Ursprüngliche Nachricht----- Von: Shane Curcuru <a...@shanecurcuru.org> Gesendet: Dienstag, 13. April 2021 16:14 An: dev@diversity.apache.org Betreff: Re: Call for webmasters! Matt Sicker wrote on 4/7/21 2:35 PM: > We need a webmaster! Can someone help out and get the site in a state > where content writers can help contribute? We have plenty of raw > source material in the D&I survey results PDFs and Google Doc that > could be broken down into blog posts and such over time as well as new > content contributed by others. I've heard that Pelican is supported > here at Apache, though I'm not picky as long as content writers can > easily contribute (e.g., via GitHub or some interactive software). > While projects are responsible for their own website maintenance, Apache Infra has several semi-supported toolsets / ways to build static sites that are widely used and easy to get help with; see .asf.yaml docs. https://infra.apache.org/project-site.html Pelican is getting traction on a lot of new sites and sites being migrated off the old Apache CMS, but there are plenty of Jekyll or other Markdown-ish tools being used widely too. The diversity.a.o site is already mirrored to GitHub, but needs some layout structure: https://github.com/apache/diversity-site I agree - once we have better docs as to site structure and expected themes, it will be easier for a lot more people to collaborate. -- - Shane Apache Member The Apache Software Foundation
