Cant we deploy what we have now manually as rob said and then figure out automation if neeeed?
I don’t see the neee to automate but that doesn’t need to be a single task. If we want automation we can do that on a second time. On Tue, Mar 19, 2019 at 7:35 AM Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > I envisaged people would run the site 'build', and check in the > resulting output, e.g. as the Apex project Michael linked to does. > > Though perhaps a little work, it doesnt seem like a massive burden to > run the site build. I'd expect it to be something folks should do when > making updates to the site anyway, to check changes actually work > before committing them. > > On Mon, 18 Mar 2019 at 19:45, Justin Bertram <jbert...@apache.org> wrote: > > > > I added the drop-shadow the the "Active" in the main logo. Let me know > what > > you think. > > > > I agree with Robbie about removing the PMC and committer details. It's an > > unnecessary maintenance burden, and a stale website is a bad look. Here's > > what I propose: > > * Fold the board reports and the PMC/committers links under the > "Apache" > > navigation menu. > > * Make the PMC/committers link point to > > https://people.apache.org/phonebook.html?pmc=activemq > > > > Robbie, the issue I see with propagating changes in the website is that > > there's an intermediate step where Jekyll needs to render the HTML from > the > > markdown, includes, scss, etc. I don't understand how that step is going > to > > happen. Ideally it would be an automatic process so that we could check > in > > markdown changes via GitHub and those changes would be made live > > automatically. > > > > > > Justin > > > > On Mon, Mar 18, 2019 at 12:53 PM Robbie Gemmell < > robbie.gemm...@gmail.com> > > wrote: > > > > > About propagation of changes, what often happens with sites now is > > > that the website (or main) repository contains an 'asf-site' branch > > > that in turn has a 'content' sub-directory within it comprising the > > > live site. Anything outwith that can comprise the site source. The > > > repo is monitored by gitpubsub and whenever changes are committed, the > > > contents dir gets synced to the actual webservers automatically. No > > > build jobs etc needed. > > > > > > Robbie > > > > > > On Mon, 18 Mar 2019 at 15:38, Justin Bertram <jbert...@apache.org> > wrote: > > > > > > > > I agree we need up-to-date information for > > > > http://activemq.apache.org/activemq-website/team/. Bruce, where's > the > > > > official data on who is a PMC member and who is a committer? > > > > > > > > I fixed the CMS download issue. > > > > > > > > What are the details about the Slack channel? This is the first I've > > > heard > > > > of it. > > > > > > > > I added the drop-shadow on the "MQ" because on the ActiveMQ 5 project > > > page > > > > the background behind the image is the same color as the "MQ" and > > > therefore > > > > it was disappearing. I added the drop-shadow to make it visible. It > > > > wouldn't be hard to add a drop-shadow to the whole thing, but I > didn't > > > > think the drop-shadow on just the "MQ" looked any stranger than it > being > > > a > > > > different color in the first place. > > > > > > > > One thing I'm not really clear on yet is how modifications from the > > > > activemq-website repo will be propagated to the actual website. I've > read > > > > about some Apache buildbot thing that might help here, but I don't > know > > > > much about it yet. Anybody else have any clue on how that's supposed > to > > > > work? > > > > > > > > BTW, I'm working up a PR right now, but I wanted to get as much of it > > > right > > > > as I could before I sent it. > > > > > > > > > > > > Justin > > > > > > > > On Sat, Mar 16, 2019 at 6:00 PM Michael André Pearce > > > > <michael.andre.pea...@me.com.invalid> wrote: > > > > > > > > > A few bits we need to work on: > > > > > > > > > > I think we need to update this, it was extracted from current site, > > > but is > > > > > out of date. > > > > > http://activemq.apache.org/activemq-website/team/ > > > > > > > > > > Seems we are missing cms download page > > > > > http://activemq.apache.org/activemq-website/projects/cms/download/ > > > > > > > > > > On the contact side, there is now a slack channel this should be > added, > > > > > and have the same visibility as IRC (could be added later, but > just to > > > note) > > > > > > > > > > > > > > > With the hero sections on the logo side, where drop shadow has been > > > added > > > > > to the letters in MQ for Apache Active MQ, it looks a bit odd just > > > having > > > > > MQ drop shadowed, would it be easy to drop shadow it all. > > > > > > > > > > > > > > > > > > > > > <snipped> > > > > -- Clebert Suconic
