Sorted On Wednesday, April 6, 2016, Chris Mattmann <chris.mattm...@gmail.com> wrote:
> All of this is looking great, Tom. There’s real > substance here and something for us to build on. > > — > Chris Mattmann > chris.mattm...@gmail.com <javascript:;> > > > > > > > > On 4/6/16, 7:33 PM, "Tom Barber" <tom.bar...@meteorite.bi <javascript:;>> > wrote: > > >Alright here's a summary of today's experimentation: > > > >Created a basic documentation page to test out a few things. Tabs work > >quite well, and kbd tags on the radix page look pretty good to attract > >users. Clearly that whole section would need more work, its just a test > bed > >of ideas currently. > > > >http://buggtb.github.io/oodt-website/documentation.html > > > >Community page is also tabular, the about page is basically a 1:1 copy of > >the existing stuff, the team page is cool because the PMC list is > generated > >directly from the Apache Phonebook (I noticed the one on the main site is > >already out of date! ;) ) > > > >http://buggtb.github.io/oodt-website/community.html > > > > > >Downloads page, again, this uses a configuration parameter to dynamically > >generate the links to the correct version and the previous releases down > >the right hand side, this is great for the release process as all someone > >has to do is when a VOTE is accepted and the mirrors are live, is paste > >about 3 lines of code into the site and check it in, at which point the > >downloads page is up to date once more (although we could probably write a > >plugin to automate this as well ;)) > > > >http://buggtb.github.io/oodt-website/download.html > > > > > >Anyway, like I said, work in progress, I'm soliciting feedback more than > >anything else. In reality the site docs wouldn't live directly under the > >components menu heading but it was a good place to put them for now, also > >it wouldn't take much to have them use the same stylesheets as the main > >site and also link back to the main site as well, making them feel more > >integrated. > > > >It needs more diagrams and colour, to break it up still, but I think as a > >POC it's coming along alright. > > > >Regards, > > > >Tom > > > >On Wed, Apr 6, 2016 at 6:03 PM, Lewis John Mcgibbney < > >lewis.mcgibb...@gmail.com <javascript:;>> wrote: > > > >> Bingo > >> > >> On Wednesday, April 6, 2016, Tom Barber <tom.bar...@meteorite.bi > <javascript:;>> wrote: > >> > >> > Thanks Lewis! I think with stuff like this its hard to fully explain > over > >> > email without a 10000 word essay. > >> > > >> > Anyway, I said I'd leave it but I got bored so I wondered what else > >> Jekyll > >> > could do to help us and here's a couple of things I came up with: > >> > > >> > https://github.com/buggtb/oodt-website/blob/gh-pages/_config.yml#L29 > >> > > >> > The downloads page on the CMS is manually updated, but you know me, I > >> love > >> > a bit of automation, so in Jekyll we could dump the release info in > here > >> > and watch it magically build: > >> > > >> > > https://dl.dropboxusercontent.com/u/8503756/oodt-website/download.html > >> > > >> > That way it should be dead simple to keep the download page up to > date. > >> > > >> > I then wondered about other stuff so I looked at the PMC list, it'll > get > >> > stale easily, so what could I do to sort that out: > >> > > >> > > >> > > >> > https://github.com/buggtb/oodt-website/blob/gh-pages/_plugins/pcm_generator.rb > >> > > >> > Greps the new ASF phone book and extracts our PMC members, as I'm a > >> giving > >> > kind of guy, I'll parametrize it and Joshua or whatever can use it as > >> well > >> > when its done. > >> > > >> > Currently the PMC list is on the download page, ignore that it was > just > >> for > >> > testing. > >> > > >> > Anyway there you go. Couple more nuggets that could make the website > >> > maintenance a whole lot simpler. > >> > > >> > Tom > >> > > >> > > >> > > >> > On Wed, Apr 6, 2016 at 11:39 AM, Lewis John Mcgibbney < > >> > lewis.mcgibb...@gmail.com <javascript:;> <javascript:;>> wrote: > >> > > >> > > Hi Tom, > >> > > > >> > > On Wed, Apr 6, 2016 at 12:59 AM, Tom Barber < > tom.bar...@meteorite.bi <javascript:;> > >> > <javascript:;>> > >> > > wrote: > >> > > > >> > > > > >> > > > When I took over the chair from SK, my unofficial aim was to use > this > >> > > chair > >> > > > period to try and get the business users involved, my day job > >> requires > >> > me > >> > > > to drive users to our product and get them interested enough to > test > >> > it, > >> > > > whilst OODT isn't commercial, ultimately the goal is the same, to > >> gain > >> > > > users and community members, we need users, and we need users who > >> don't > >> > > > just work in the scientific domain. Whilst the odd person might > swing > >> > by > >> > > > the mailing list, in reality, 99% of users will land on the > homepage, > >> > and > >> > > > that is the determining factor as to whether they bother to > >> investigate > >> > > > further. Which is why I spend a lot of time prioritising stuff > that > >> > > doesn't > >> > > > really make a lot of sense to the rest of you! :) > >> > > > > >> > > > > >> > > For the record its worth me stating here that I totally understand > your > >> > > PoV. When you showed me your BI workflow examples way back > @ApacheCon I > >> > > realized that your use cases were different. It's very refreshing to > >> see > >> > > software re-purposed or presented in a different manner. An eye > opener > >> so > >> > > to speak. > >> > > Look forward to seeing what kind of roadmap we come up with > @ApacheCon > >> > this > >> > > year again. > >> > > Ta > >> > > > >> > > >> > >> > >> -- > >> *Lewis* > >> > > -- *Lewis*
