2017 site

[joshuago78]

I am wondering how to go about reusing this repo for the 2017 conference. I believe Github pages will only work for one site per project, so if we want to keep the 2016 site running, then I believe what I should do is clone this repo and set the remote origin to a new repo at https://github.com/code4lib/2017.code4lib.org.git

• Is this correct?
  • If so, can someone add me as a member of code4lib on Github?
  • If not, please fill me in on a better strategy

[bibliotechy]

@joshuago78 I've just sent you an invite to the code4lib organization.

A new repo based on this repo does seem like a reasonable strategy.

[joshuago78]

Thank you @bibliotechy

[queryluke]

@joshuago78 if need a rundown or have any questions about the code, let me know. There are some additional scripts that I wrote to extract Google Form data into yaml files and jekyll templates. It may be a bit stale, but I can update as necessary.

[joshuago78]

@queryluke an overview would be most appreciated. Perhaps we can have a phone call next week. I'm still in the process of putting together a website working group. If you or anyone else on last year's team would like to join in, please let me know.

[queryluke]

@joshuago78 I'm on vacation next week, but I'd be happy to re-enlist in the website working group.

[phette23]

I'd be willing to help out as well.

[sdellis]

Just returning from vacation today, so sorry for the delayed response... I'd be happy to help as well.

[sdellis]

FYI - the newly released Jekyll Admin plugin could come in handy... tested it out locally and it looks cool. One issue we had last year was that people couldn't update their own content without making pull requests. This might simplify things, but not sure how it would work with ghpages hosting.

[queryluke]

@joshuago78 I saw people are signing up for the Website Working Group on the wiki. Do you want us to sign up there?

[joshuago78]

Yes that would be great. Then I will call a meeting for us to outline some tasks.