Re: OODT Website

2017-09-16 Thread lewis john mcgibbney
ht > > place? > > > > > > > > > Sent with BlackBerry Work > > > (www.blackberry.com) > > > > > > From: lewis john mcgibbney <lewi...@apache.org<mailto:lew > i...@apache.org > > >> > > > Date: Friday, Sep 15,

Re: OODT Website

2017-09-16 Thread Tom Barber
@apache.org > >> > > Date: Friday, Sep 15, 2017, 4:08 AM > > To: dev@oodt.apache.org <dev@oodt.apache.org<mailto:dev@oodt.apache.org > >> > > Subject: OODT Website > > > > ... is looking really good. REALLY REALLY GOOD. > > > > The use c

Re: OODT Website

2017-09-16 Thread lewis john mcgibbney
wi...@apache.org>> > Date: Friday, Sep 15, 2017, 4:08 AM > To: dev@oodt.apache.org <dev@oodt.apache.org<mailto:dev@oodt.apache.org>> > Subject: OODT Website > > ... is looking really good. REALLY REALLY GOOD. > > The use cases for OODT go far beyond Science

RE: OODT Website

2017-09-15 Thread Mallder, Valerie
.org<mailto:dev@oodt.apache.org>> Subject: OODT Website ... is looking really good. REALLY REALLY GOOD. The use cases for OODT go far beyond Science Data Systems... the technologies which OODT plugs in to (and delegates to) make this possible. Whoever has been hammering away on the Website ge

OODT Website

2017-09-15 Thread lewis john mcgibbney
... is looking really good. REALLY REALLY GOOD. The use cases for OODT go far beyond Science Data Systems... the technologies which OODT plugs in to (and delegates to) make this possible. Whoever has been hammering away on the Website gets the thumbs up from me. Lewis --

Re: OODT website instructions

2016-12-25 Thread Sean Kelly
Thanks Tom! Well done. --k Tom Barber <mailto:tom.bar...@meteorite.bi> 2016-12-25 at 4.31 p Hey folks, Happy Christmas! I've taken the downtime to write a wiki page for the OODT website should anyone want to edit it: https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+th

OODT website instructions

2016-12-25 Thread Tom Barber
Hey folks, Happy Christmas! I've taken the downtime to write a wiki page for the OODT website should anyone want to edit it: https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site Its pretty straightforward as its a simple jekyll site, there is a bit of a hop to get

Re: OODT Website Changes (Redux)

2016-04-07 Thread Lewis John Mcgibbney
> > > >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.

Re: OODT Website Changes (Redux)

2016-04-07 Thread Tom Barber
lright 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

Re: OODT Website Changes (Redux)

2016-04-07 Thread Lewis John Mcgibbney
uite 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

Re: OODT Website Changes (Redux)

2016-04-06 Thread Chris Mattmann
> >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/docu

Re: OODT Website Changes (Redux)

2016-04-06 Thread Tom Barber
://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

Re: OODT Website Changes (Redux)

2016-04-06 Thread Lewis John Mcgibbney
; 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

Re: OODT Website Changes (Redux)

2016-04-06 Thread Tom Barber
Thanks Lewis! I think with stuff like this its hard to fully explain over email without a 1 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

Re: OODT Website Changes (Redux)

2016-04-06 Thread Lewis John Mcgibbney
Hi Tom, On Wed, Apr 6, 2016 at 12:59 AM, Tom Barber 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

Re: OODT Website Changes (Redux)

2016-04-06 Thread Tom Barber
+++ > > > > > > > > > > > > > > > > > > > > > > On 4/5/16, 7:06 PM, "Tom Barber" <tom.bar...@meteorite.bi > <javascript:;>> > > wrote: > > > > >Okay, spent an hour

Re: OODT Website Changes (Redux)

2016-04-05 Thread Lewis John Mcgibbney
ript:;>> > wrote: > > >Okay, spent an hour hacking around ideas tonight, just to get a feel for > >things. > > > >http://buggtb.github.io/oodt-website/ > > > >I've only messed around with a frontpage and basic blog listing. You can > >see what i'm trying to d

Re: OODT Website Changes (Redux)

2016-04-05 Thread Mattmann, Chris A (3980)
hour hacking around ideas tonight, just to get a feel for >things. > >http://buggtb.github.io/oodt-website/ > >I've only messed around with a frontpage and basic blog listing. You can >see what i'm trying to do in breaking it up a bunch, I still want to do >make the text easier to d

Re: OODT Website Changes (Redux)

2016-04-05 Thread Tom Barber
Okay, spent an hour hacking around ideas tonight, just to get a feel for things. http://buggtb.github.io/oodt-website/ I've only messed around with a frontpage and basic blog listing. You can see what i'm trying to do in breaking it up a bunch, I still want to do make the text easier to digest

Re: OODT Website Changes (Redux)

2016-04-05 Thread Mattmann, Chris A (3980)
ng markdown is having to learn a new language syntax for >> styling the text. I have no objection to having a static site. I just want >> it to be easy to use and not require that you have to spend time learning >> something new. If it takes too much time to do (because you have to learn

Re: OODT Website Changes (Redux)

2016-04-05 Thread Tom Barber
may find that people will put it on > their todo list but never end up getting to it because they are too busy > working on higher priority tasks in their day jobs. I think your primary > goal (when choosing what you want to do) should be to add as little work as > possible to people's plates. That

Re: OODT Website Changes (Redux)

2016-04-05 Thread Chris Mattmann
YG editors out there that >have the option to do a "save as" to markdown format that would be optimal. >But I don't know if there are any. > > > >Sent with Good (www.good.com <http://www.good.com>) > >From: Tom Barbe

Re: OODT Website Changes (Redux)

2016-04-05 Thread Lewis John Mcgibbney
to people's plates. That's all. If there are any WYSIWYG editors >>> out there that have the option to do a "save as" to markdown format that >>> would be optimal. But I don't know if there are any. >>> >>> >>> >>> Sent with Good (www.good

Re: OODT Website Changes (Redux)

2016-04-05 Thread Tom Barber
re are any. >> >> >> >> Sent with Good (www.good.com) >> >> From: Tom Barber <tom.bar...@meteorite.bi> >> Sent: Saturday, April 2, 2016 7:17:42 PM >> To: dev@oodt.apache.org >> Subject: Re: OODT Website Changes

Re: OODT Website Changes (Redux)

2016-04-03 Thread Tom Barber
t there that have the option to do a "save as" to markdown format that > would be optimal. But I don't know if there are any. > > > > Sent with Good (www.good.com) > > From: Tom Barber <tom.bar...@meteorite.bi> > Sent: Saturd

RE: OODT Website Changes (Redux)

2016-04-02 Thread Mallder, Valerie
with Good (www.good.com) From: Tom Barber <tom.bar...@meteorite.bi> Sent: Saturday, April 2, 2016 7:17:42 PM To: dev@oodt.apache.org Subject: Re: OODT Website Changes (Redux) Also, (playing devils advocate) if it's a word doc why can't you just copy and paste it into

Re: OODT Website Changes (Redux)

2016-04-02 Thread Tom Barber
a >> WYSIWYG editor. You can also copy-paste from a Word doc into the post. Just >> my opinion. >> >> >> >> Sent with Good (www.good.com) >> >> From: Tom Barber <tom.bar...@meteorite.bi> >> Sent: Saturday, April 2,

Re: OODT Website Changes (Redux)

2016-04-02 Thread Tom Barber
t; > > > Sent with Good (www.good.com) > > From: Tom Barber <tom.bar...@meteorite.bi> > Sent: Saturday, April 2, 2016 6:45:21 PM > To: dev@oodt.apache.org > Subject: OODT Website Changes (Redux) > > Alright folks, > > Most peope who have been

RE: OODT Website Changes (Redux)

2016-04-02 Thread Mallder, Valerie
in a WYSIWYG editor. You can also copy-paste from a Word doc into the post. Just my opinion. Sent with Good (www.good.com) From: Tom Barber <tom.bar...@meteorite.bi> Sent: Saturday, April 2, 2016 6:45:21 PM To: dev@oodt.apache.org Subject: OODT Website Changes

OODT Website Changes (Redux)

2016-04-02 Thread Tom Barber
Alright folks, Most peope who have been on the list for a while know we moved from the most static of static websites to Apache CMS a while ago to allow for more regular updating and maintenance of the website. Lewis then put a bunch of work into creating a template for the CMS website and we

Re: OODT Website

2014-11-10 Thread Verma, Rishi (398M)
: Re: OODT Website Thanks Chris, If one of the guys can give me some pointers about whats missing, I'd love to push this one through, as I can do webdev slowly with 1 arm whilst bouncing a baby ;) Tom On 08/11/14 17:05, Mattmann, Chris A (3980) wrote: Hey Tom, We tried to start

Re: OODT Website

2014-11-10 Thread Lewis John Mcgibbney
Date: Saturday, November 8, 2014 at 12:24 PM To: Chris Mattmann chris.a.mattm...@jpl.nasa.gov, dev@oodt.apache.org dev@oodt.apache.org Subject: Re: OODT Website Thanks Chris, If one of the guys can give me some pointers about whats missing, I'd love to push this one through, as I can

Re: OODT Website

2014-11-09 Thread Tom Barber
...@jpl.nasa.gov mailto:chris.a.mattm...@jpl.nasa.gov, dev@oodt.apache.org mailto:dev@oodt.apache.org dev@oodt.apache.org mailto:dev@oodt.apache.org Subject: Re: OODT Website Thanks Chris, If one of the guys can give me some pointers about whats missing, I'd love to push

Re: OODT Website

2014-11-09 Thread Lewis John Mcgibbney
++ -Original Message- From: Tom Barber tom.bar...@meteorite.bi Date: Saturday, November 8, 2014 at 12:24 PM To: Chris Mattmann chris.a.mattm...@jpl.nasa.gov, dev@oodt.apache.org dev@oodt.apache.org Subject: Re: OODT Website Thanks

OODT Website

2014-11-08 Thread Tom Barber
Alright chaps, Just wondered what the state of play was with the OODT website and what we need to do to get it over the line. Cheers Tom -- *Tom Barber* | Technical Director meteorite bi *T:* +44 20 8133 3730 *W:* www.meteorite.bi | *Skype:* meteorite.consulting *A:* Surrey Technology

Re: OODT Website

2014-11-08 Thread Mattmann, Chris A (3980)
++ -Original Message- From: Tom Barber tom.bar...@meteorite.bi Date: Friday, November 7, 2014 at 3:41 PM To: dev@oodt.apache.org dev@oodt.apache.org Subject: OODT Website Alright chaps, Just wondered what the state of play was with the OODT website

Re: OODT Website

2014-11-08 Thread Mattmann, Chris A (3980)
++ -Original Message- From: Tom Barber tom.bar...@meteorite.bi Date: Saturday, November 8, 2014 at 12:24 PM To: Chris Mattmann chris.a.mattm...@jpl.nasa.gov, dev@oodt.apache.org dev@oodt.apache.org Subject: Re: OODT Website Thanks Chris, If one of the guys can give me some pointers about

Re: OODT Website

2014-11-08 Thread Lewis John Mcgibbney
at 12:24 PM To: Chris Mattmann chris.a.mattm...@jpl.nasa.gov, dev@oodt.apache.org dev@oodt.apache.org Subject: Re: OODT Website Thanks Chris, If one of the guys can give me some pointers about whats missing, I'd love to push this one through, as I can do webdev slowly with 1 arm whilst