module – ntdln

Yesenia Perez-Cruz speaking at An Event Apart Seattle 2018 on April 2, 2018.

Unified design systems are essential to building, maintaining, and evolving our sites and products. By empowering disparate teams via a common visual and UX language, they help us create cohesive user experiences. But creating a unified system that scales to serve a variety of content and use cases can be challenging. Sharing insights from her experience creating a unified design system for eight media brands with eight distinct editorial strategies, Yesenia will show how to approach a design system via a user-centered lens. Learn how being scenario-driven helps you design a scalable system that responds flexibly to specific contexts.

Continue reading An Event Apart: “Scenario-Driven Design Systems”

A few weeks ago I spent some time breaking apart Sass files into smaller segments for a project at work, trying to go for a more modular approach for the CSS. Doing this in Sass is pretty simple. Pull out a section of styles into a new “partials” file, named something like _module.scss. Then in the main Sass file, import the module with @import "module";.

For quite a while I’ve wanted to be able to take a similar approach with JavaScript, breaking the main file into modules and using Sass-like imports to pull them all together. I knew this was supposed to be possible with ES6 modules, but every time I started doing the research, I was overwhelmed by new JavaScript techniques and tools (Babel? Webpack? Browserify? Rollup? RequireJS?). After my most recent attempt to find and understand a solution, I finally came up with something that works and I’m fairly happy with.

Continue reading Using JavaScript Modules