Hey all, Long time lurker, first time talker:
I actually set this up for the Mahout project. If the repo is only website code, then you can do it with git pages. If the website is just one directory, then you just set it up to do execute a build script in travis CI which builds the site then copies the HTML files to where they go. Happy to help if needed. However, back to original proposal of "email us changes", I might recommend another mailing list like commits@d.a.o for the automated stuff (which I also think is sometimes a standard practice) bc depending how many commits you're getting, that can get real spammy real fast. just my .02 On Wed, May 29, 2019 at 5:16 PM Joan Touzet <woh...@apache.org> wrote: > Also +1 for Git, and if it's like the project in which we're involved, > an asf-site branch can def. be used to autopublish a website. > > -Joan > > On 2019-05-29 8:43, Myrle Krantz wrote: > > On Wed, May 29, 2019 at 1:46 PM Naomi Slater <n...@tumbolia.org> wrote: > > > >> Git imo. so we can work on GitHub (assuming this is in fact possible for > >> the website) > >> > > > > +1 Git. I use svn when I have to, but I'm not super comfortable with it > > yet. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: diversity-unsubscr...@apache.org > For additional commands, e-mail: diversity-h...@apache.org > >
