Skip to content

Instantly share code, notes, and snippets.

@jogjayr

jogjayr/nodevember.md

Last active October 29, 2017 19:55
Show Gist options
  • Save jogjayr/4d3c6875d7181f7c648892ad201c3609 to your computer and use it in GitHub Desktop.
Save jogjayr/4d3c6875d7181f7c648892ad201c3609 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
nodevember.md

Abstract

Do you have an internal UI component library you struggle to tame? I will describe how to package, distribute, and effectively use UI components, with a focus on Angular, Typescript, Webpack, and Artifactory.

Summary

Your component library doesn't have to become a hard-to-manage hydra. An internal component library can help improve visual consistency, quality, and consistency, and DRY out your code. And yet there are so many decisions to make: Angular or React, TypeScript or ES6 or Flow, dependency management, packaging, distribution, documentation, developer on-boarding, and so much more.

Here are some of the things we learned at Skyhigh Networks 1.5 years into our component-driven journey.

  • Approaches to packaging and distributing components and applications using Webpack, NPM/yarn, and Artifactory.
  • Documenting components and on-boarding newcomers
  • TypeScript tips to make component APIs more accessible
  • Empowering non-frontend-developers to build UIs
  • Working with distributed teams
  • The surprising impact of standardized components on productivity
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment