code4lib / 2017.code4lib.org Goto Github PK

PR forthcoming; we've got an updated link from CONCENTRA for the donation page.

schedule/index.html is still dates/events from last year

http://2017.code4lib.org/schedule/timeline.html

Call for Conference Proposals: 10/13 – 11/7 (presentation link: https://goo.gl/forms/GbM0jmSdXFkRdHAr2, panel link: https://goo.gl/forms/q2KbVcO4ntkh6bPp1)

Vote for Conference Proposals: 11/16 – 12/7 (link coming)

In addition to the call for proposals we have a call for panels (form: https://goo.gl/forms/q2KbVcO4ntkh6bPp1)

Can a button be added under "Call for Proposals" for "Call for Panels".

Thank you.

Change the link to go directly to the schedule page.

"What's Going On?" is not final language, feel free to propose alternatives, but it feels better than "Schedule". If there's a better way to present all active "happenings" on the homepage, please present a mockup or PR.

There's a major accessibility issue with the links for voting, etc. on the index page within the photo. The color contrast needs to be made better. I couldn't even see them until I moused over them. Hover color too needs to be changed.

I couldn't manage to get it any smaller without it looking funny. I'll leave it to someone with better image manipulation skills than me.

You can find the original TIFF here: https://www.dropbox.com/sh/4rx1yo0t0iwajga/AAAY5psitRhnS9eFqzMNPF9Sa?dl=0&lst=

Found 2 minor issues both concerning the Venue's dropdown

the orange background color (on rollover) doesn’t pass

the darker orange (Venues

I feel like and SVG guru now. Here is a quick rundown, all of this relates #36

1. I added documentation in the readme on how to utilize the svgs in this branches readme. I only edit the sponsors page. But once this AND the prospectus branch are merged, we'll want to convert the prospectus icons to svgs as well
2. Note: to change the colors of the badges we have to use a rather a new(er) CSS feature: variables. Variables are not supported by (surprise, surprise) IE or Edge, but look to be supported by all other major browsers and mobile. Either way, the old blue colors are defined as fallbacks. If we want to adjust the fallbacks we can, but I wasn't sure of the final color palette, so leaving this for now.
3. If anyone wants to adjust the color palette, you can in /assets/css/main.scss (under the SVGs header)

Kinda fun side note, in terms of space savings:
PNGs = 209kb
Original SVG files = 340kb
New SVG file = 16kb!

If anyone is insterested in the structure of the SVG file, check out /assets/img/badges/badges.svg, I gave descriptive ids to all the paths so you should be able to read the make-up of the file easily.

...are a-coming.

For the speaker image circle to work, the image dimensions should be 1:1. Some need to be cropped.

Looks like it should now link to /schedule/ rather than /schedule/timeline

Passel of sponsor names and logos coming shortly.

The git history is left over from 2016 and is making the repo gigantic.

The official code4lib logo uses blue for the curly bracket.

A total of 11 scholarships are being awarded this year; various pages should reflect the count.

need buttons (& maybe one sentence teaser?) on:

• home page
• schedule/timeline.html

https://vote.code4lib.org/election/41

Github pages now uses jekyll 3.2

https://github.com/blog/2228-simpler-github-pages-publishing

I think this just makes more sense & simplifies things, since this repo is entirely a GitHub Pages site & we can do the more traditional "push to feature branch, merge to master" workflow.

LPC and B&S have finalized the registration fee and cancellation policy, so I'll update and activate /attend/.

This may touch on issue #93, but would only be a subset of it.

Currently, it's nearly impossible to tell what's a link or not.

The workshops don't have times
change all times to pst

The voting period has closed.

It looks like in the cleanup work the entirely of the _data/path.yml file was wiped out—it now contains just a single reference to the site root '/'. That actually works a lot of places but I noticed it broke some footer links:

<li class="list-item tci"><a href="{{ site.data.path }}schedule">Schedule</a></li>
<li class="list-item tci"><a href="{{ site.data.path }}attend.html">Attend</a></li>

in this instance, the "Schedule" link is fine since it gets redirected to the directory index but "attend.html" doesn't exist anymore and breaks. I'll send a PR referencing this & fixing the footer links but I wanted to point out the larger issue because ``{{site.data.path}}` references are littered throughout the code base and probably nonfunctional in a some other places.

As I'm poking around the cleaned up site, I see a few places the old salmon-colored background remains:

• venue/reception.html bottom
• index.html bottom "Welcome to Los Angeles"

maybe this was intentional but it looked like a holdover from the old sites styles, doesn't fit the new scheme.

• Working document can be found here: https://docs.google.com/document/d/195m1tGq1y_Mkrr0UpEz8Hdge0vqknRSETqvZhhxtd2k/edit
• It is almost ready to go. They have a couple decisions to make regarding:
  • The number of table sponsorships (dependent on floor plan of the venue)
  • The number and dollar amount of the main reception sponsorships

The first registration wave has closed, so time to update the website.

Schedule say "Thursday, March 10th". It is actually the 9th.
http://2017.code4lib.org/schedule/

Please add a link to the prospectus (perhaps with "Sponsor Code4Lib" as the button text).

logo can be found here: https://www.jetbrains.com/company/press

We want to display the activities that have already occurred, such as talk proposals and voting.

More sponsor and logo updates... FOR GREAT JUSTICE!

Repeating the same quotes as last year feels a bit weak, it'd be great if we had a process for collecting new ones for each conference, or if we only recycled a few.

Just a few things I've noticed, a lot of people are about to hit this page:

• PR #103 fixes a missing period & the election URL results
• "Only the top ten (highlighted) have been accepted so far" how are the proposals highlighted? I didn't notice any indicator
• would be nice to colorize the lanyard colors (red, yellow, green)
• can we link up something in the Hotel Fees section such as the housing link that's in the registration form?

The contract has been signed, so we can finally add some information.

Dates: March 6-9, 2017
Venue: UCLA Luskin Conference Center

People thinking about attending want to know:

• When is the conference?
• Where is the conference?
• When can I register for the conference?
• How much does it cost?
• How do I register?
• Where can I stay? (hotel locations, cost, group code)

People who are attending want to know:

• What is the schedule?
• How do I get to the venue? (from the hotel, the airport, my AirBnB)
• Where can I eat?

People who want to give a talk/workshop/poster want to know:

• When is the submission period?
• How do I submit?

Organizations who want to sponsor want to know:

• What is code4lib all about?
• What do I get for my contribution?
• What is left for me to sponsor?

Two overflow hotels to add.

Color contrast for time and length on individual talk / workshop pages not accessible

Clean out data, links, and other references to the 2016 event and give ourselves a clean slate to work with.

Award notifications were sent out on 10 January; upon confirmation from the awardees that they will accept the scholarships, the page should be updated.

Also noting that when this is done, it will be a good opportunity to clean up the duplicate lists of sponsors on that page.

I've loaded this up in the workshops branch, but if anyone on the preconf crew wants to adjust the description /about/propose-a-workshop.html feel free.

Is there a reason the toggles in the conf.yml file are on/off strings & not booleans? See:

https://github.com/code4lib/2017.code4lib.org/blob/master/_data/conf.yml#L7-L16

I'd say search: true etc. is better. The conditionals all over the place like {% if site.data.conf.toggles.livestream == "on" %} seem a bit more verbose & error prone (e.g. == "On" will be false) than just {% if site.data.conf.toggles.livestream %}. If we do change this the conditions everywhere need to be updated which is actually a good reason to just keep it the way it is now.