code4lib / 2016.code4lib.org Goto Github PK

Go through and make sure all functionality is available via keyboard, color contrast, alt tags, aria-stuff?

I took a stab at this in the pinterest-esque... branch. If we like, I'll merge this with master.

Note there are 2 widths which you can view at /proposed-talks.html and proposed-talks-fluid.html

Feedback welcome!

This was omitted, but we need to display whether it's a half or full day and whether it's AM or PM.

Go through all pages and clean up oddities with mobile display.

See: http://oli.jp/2011/github-pages-workflow/

Voting open on Nov 17th and close Dec 2nd 5pm Pacific. Not sure how this ties in with #146

Currently is an image.

People have therefore been hacking the form to put all the presenter names in the 'first presenter' field. Currently I don't really see a problem with this, but wanted to put it out there just in case.

I'd like to hear more info about the vision for the 'schedule' page.

currently the two pre-conference-specific pages are http://2016.code4lib.org/propose-a-workshop.html and http://2016.code4lib.org/proposed-workshops.html neither of which is an appropriate url for finalized workshop info.

I guess we'll want a new page with the final workshops where we can post:

• schedule
• locations (both street maps and internal building maps since there will be multiple sites)
• workshop summaries
• links to resources for pre-downloading and pre-installing

Let me know if there was some other plan already in place to accommodate this content! If not maybe someone could create a stub and we could start pre-populating to the extent possible?

Talk to @cbeer about how he wants the data for the die-bold-o-tron.

This variable {{ site.data.path }} outputs /2016.code4lib.org/. So

<link rel="stylesheet" href="{{ site.data.path }}prototype/bootstrap/dist/css/bootstrap.css">

produces:

<link rel="stylesheet" href="/2016.code4lib.org/prototype/bootstrap/dist/css/bootstrap.css">

Which, of course, doesn't load anything and the page just loads HTML. All of the links in header and footer break locally too.

@roastduckalamode am I missing something?

It's the 11th annual conference, not the 13th.

I'm going to go ahead and take this one - unless the majority of people think this isn't needed.

When the targeted sponsorship section is viewed on a screen wide enough to have three columns, the blurbs of the sponsorship become difficult to read. Also, when I finish one, I sometimes have to scroll back up to read the text of the next one, which feels wonky.

I'd propose we have one column, no matter the viewing width. Also, that would allow us to add anchors to make it possible to link directly to each targeted sponsorship, which would be nice.

Thoughts?

See the prototype:
http://code4lib.github.io/2016.code4lib.org/prototype/

(It's the blue transparent image that looks like a "4")

Is there any easy way to add in anchors so that we can link directly to a single, expanded workshop description? The voting form doesn't allow us to make these expandable so we'd like to provide direct links instead to reduce visual clutter.

Currently our only option may be to copy everything back over to the wiki so we can link to the descriptions :(

Society Hill Sheraton - get pricing as well.

Here are content ideas!

Create some form of parser to harvest presentation / presenter submissions

Here are content ideas!

The Sponsorship committee will mostly handle this content. See 2014 prospectus for ideas.

Absolute paths should be made relevant... won't matter when we go to 2016.code4lib.org but right now it's breaking with this url: http://code4lib.github.io/2016.code4lib.org/schedule.html

Look into GitHub Project Pages for this.

@roastduckalamode @sdellis Someone just gave great feedback that that pages listing talks and workshops should have a link to submit a talk as well. Makes sense to me. Maybe at the top, just before the listing? A big ole button?

@jtidal I see where you are going with the speaker2.html page, but it's very rough around the edges... the title bar says "Start Bootstrap" to start. If you are going for a "non-stripey" simple white page, you can use the existing template and jekyll includes. I merged it, but please fix and resubmit.

We should shut down the link at that point!

Is anyone else having this problem? It makes it hard to test people's changes when I have to wait nearly three minutes for it to generate...

Regenerating: 2 file(s) changed at 2015-09-17 18:20:07 ...done in 178.773342 seconds.

Creating this so I don't forget

Here are content ideas!

Here are some content ideas!

Stub/Mock out Schedule pages with a TBA fallback page we can use until sched is announced.

Here are some content ideas.

This TODO taken from LPC email thread 'followups from yesterday' Nov 30.

There a 2 pull requests (#179 & #163), each with some new logos. Do these need to be merged and logos put somewhere?

Here are content ideas!

Smaller images for speaker and about pages

Hey all-

Do you want to embed the 2016 Tshirt voting form (built with form+, an extension of Google Forms that allows users to upload files) into the Code4Lib site? Otherwise we will send out the direct link to the form+ form. See a sample form here: http://goo.gl/Rk6rtG

The form results go into a Google sheet, which I will share with the appropriate folks if you want to display received submissions so far on the site as well.

If this could be decided yay/nay before Monday Dec. 7, noon Eastern, that'd be extra rad.

Thanks,
Christina

Here are some content ideas!

I've preloaded a branch for this

We can keep the image of Independence Hall on this page (things to do!), but I would start with an image of the Society Hill Sheraton so as to avoid confusion.

From @jtidal
I ran the site through the WAVE accessibility tool, and there are several contrast errors: http://wave.webaim.org/report#/http%3A%2F%2F2016.code4lib.org%2F (click on contrast in the upper left hand corner)

after all https://code4lib.github.io/2016.code4lib.org/ serves just fine.

using a custom url is nice. but so is privacy and security

Reasoning is that people may click 'speakers' to find out how to become one.

Downside is that these would then be in two places (currently on 'schedule' page).

Remove the "#" and replace with actual links.

Not sure exactly where it should go yet, but maybe in the "attend" section. Anyway, here's the link:

https://docs.google.com/forms/d/120Dw1JjLxPJB9VTGl0mUY7Ot6yg6YNY1RZUISJFzdwk/viewform?c=0&w=1