[IronPython] Website Update Help

2011-06-10 Thread Jeff Hardy
Hi, I'm wondering if there's anyone out there willing to help update the website, in particular replacing the big "IronPython Tools" banner with something else. Updating it isn't too hard and I'll offer any assistance that may be necessary. - Jeff ___ Us

Re: [IronPython] Website Update Help

2011-06-10 Thread Jimmy Schementi
I can do it. ~Jimmy On Jun 10, 2011, at 12:36 PM, Jeff Hardy wrote: > Hi, > I'm wondering if there's anyone out there willing to help update the > website, in particular replacing the big "IronPython Tools" banner > with something else. Updating it isn't too hard and I'll offer any > assistanc

Re: [IronPython] Website Update Help

2011-06-10 Thread Jeff Hardy
On Fri, Jun 10, 2011 at 9:49 AM, Jimmy Schementi wrote: > I can do it. Thanks. Make sure you check my fork to make sure it's in sync with yours. Any objections to using https://github.com/IronLanguages/iron-websites as the main fork, and doing all of the updates from there? - Jeff > > ~Jimmy >

Re: [IronPython] Website Update Help

2011-06-10 Thread Jimmy Schementi
On Jun 10, 2011, at 12:56 PM, Jeff Hardy wrote: > On Fri, Jun 10, 2011 at 9:49 AM, Jimmy Schementi wrote: >> I can do it. > > Thanks. Make sure you check my fork to make sure it's in sync with yours. > > Any objections to using https://github.com/IronLanguages/iron-websites > as the main fork,

Re: [IronPython] Website Update Help

2011-06-10 Thread Jeff Hardy
> Since our sites are all HTML, might be nice just to use GitHub pages rather > than the current GoDaddy hosting, though changing the nameservers through > Microsoft will be a pain. I was considering that as well, but I'm not sure we can have two sets of pages from one account. I'll poke github

Re: [IronPython] Website Update Help

2011-06-10 Thread Jimmy Schementi
On Jun 10, 2011, at 1:26 PM, Jeff Hardy wrote: >> Since our sites are all HTML, might be nice just to use GitHub pages rather >> than the current GoDaddy hosting, though changing the nameservers through >> Microsoft will be a pain. > > I was considering that as well, but I'm not sure we can ha