So I took a look and I really like the Apache Beam website.
On Wed, 28 Apr 2021 at 08:15, Myrle Krantz <my...@apache.org> wrote: > > Hey all, > > Dave Fisher is currently migrating other pieces of apache.org to CMS. I'm > thrilled with how much easier treasurer is to change now. I suggest > putting in an infra ticket to get the D&I site added to his work agenda. > > Best, > Myrle > > On Mon, Apr 19, 2021 at 3:26 PM Matt Sicker <boa...@gmail.com> wrote: > > > I haven’t forgotten this, but I still need to check out various sites again > > to find which design(s) look nice. I do remember liking some of the sites > > for projects that have participated in Outreachy here, though I’ll get back > > to you about that. That’s a good idea, and it’s also how I learned to make > > websites long ago (also why I’m no good at designing them). > > > > On Tue, Apr 13, 2021 at 11:05 Sam Ruby <ru...@intertwingly.net> wrote: > > > > > While I'm basically in the same boat as you are, I have been able to > > > successfully steal^wcopy and mimic from another site. Is there an ASF > > > hosted site that you generally like the look and feel of? > > > > > > - Sam Ruby > > > > > > On Tue, Apr 13, 2021 at 10:44 AM Matt Sicker <boa...@gmail.com> wrote: > > > > > > > > Yeah, I know what tools exist to generate static sites. I do not, > > > however, > > > > have any non-trivial graphic design knowledge, nor do I have any > > existing > > > > templates to go off. I do know how to fiddle with CSS and read MDN > > > > documentation, but that basically means I can design a dynamic widget > > for > > > > the site more so than the site itself. :D > > > > > > > > On Tue, Apr 13, 2021 at 09:13 Shane Curcuru <a...@shanecurcuru.org> > > > wrote: > > > > > > > > > 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 > > > > > > > > > >
