First of all, the conference was an overall fantastic event, most importantly in terms of the community backing and fostering it. Hats off to the organizers, volunteers, speakers, sponsors and everyone else who made it happen!
This year, the conference kept the 3-day format from the year before, with “CascadiaCSS Day,” “CascadiaJS Browser Day,” and “CascadiaJS Node Day.” There were tons of great sessions, so we’ve just picked our favorites from each day to mention here.
Day 1: CascadiaCSS Day
James talked about PostCSS, a Node.js module that uses plugins to transform CSS, and showed how it can be used along with (not instead of) Sass, for preparing and optimizing CSS files.
Day 2: CascadiaJS Browser Day
Day 3: CascadiaJS Node Day
Stephan told us about Greenkeeper, an exciting tool — new to me — that helps automate the management of front-end dependencies. It responds to updates in the npm registry for packages used by your project, automatically creates a branch in your repository where it updates the package, and prepares a pull request with the updated package for you to evaluate. (If you’re a Drupal developer, think of the Update Manager module combined with the Security-news mailing list, with recommended updates automatically prepared for your triage and review.) This type of tooling seems pretty crucial for staying stable and secure on front-end projects with increasing numbers of dependencies.
Bill gave a fun, Simpsons-themed, whirlwind history of cryptography, with some quick snippet examples of how to work with modern cryptographic functionality in Node.js.
We’ll Be Back
Ciao, CascadiaFest. See you next year!