webcomponents / webcomponents.github.io

WebComponents.org is where community-members document Web Components best practices
http://webcomponents.org
734 stars 126 forks source link

Add presentations for talks given at Polytechnic event at Google Seattle, November 15, 2014 #173

Closed JanMiksovsky closed 9 years ago

JanMiksovsky commented 9 years ago

Here are two talks I gave at the Polytechnic event at Google's office in Seattle. These talks did not use the stock slide decks provided for the event. Instead, both are live code demos written from scratch for the event.

  1. The first talk is an intro to web components. It walks through the significance of the relevant specs through code examples. For this talk, it was fun to show native components first in Chrome, then tackle webcomponents.js only later in the talk when discussing older browsers!
  2. The second talk is a more advanced one covering some patterns for component reuse. This covers four examples in live code. The third example, a monthly calendar component, introduces a new, general pattern for highly reusable components.
JanMiksovsky commented 9 years ago

Ping?

zenorocha commented 9 years ago

Done! Sorry for the delay @JanMiksovsky :)

JanMiksovsky commented 9 years ago

Thanks for getting to this.

I noticed that, because it took over a month for these talks to get included, the first of these talks has its debut at the very bottom of the first page of Presentations — and the other talk never even made the first page. One unfortunate aspect of the design of webcomponents.org is that presentations are shown in reverse order of presentation date, not the date the presentation was added to the site. Five other talks, all of which took place after these two (and one of which was similarly submitted in a PR), now appear above the two talks in this PR. Surely talks on the first Presentations page get the most views, and having talks start out in 6th or 7th place means a lost chance for me to get some views on them. That's a bummer.

I can't really complain. I appreciate the hard, unpaid work involved in maintaining a community site like this. And, to be sure, no promises are made about how quickly things will get handled. That's fine. Still, I think it's reasonable for me to simply raise this point for the consideration of the site's maintainers.